B Ons Line Card Configuration

Cisco ONS 15454 DWDM Line Card Configuration Guide, Release 10.x.
x
First Published: 2013-10-14
Last Modified: 2018-08-23
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL
STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED
WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED
WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The following information is for FCC compliance of Class A devices: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC
rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can
radiate radio-frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a
residential area is likely to cause harmful interference, in which case users will be required to correct the interference at their own expense.
The following information is for FCC compliance of Class B devices: This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15
of the FCC rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio
frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that
interference will not occur in a particular installation. If the equipment causes interference to radio or television reception, which can be determined by turning the equipment off and on,
users are encouraged to try to correct the interference by using one or more of the following measures:
Reorient or relocate the receiving antenna.
Increase the separation between the equipment and receiver.
Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
Consult the dealer or an experienced radio/TV technician for help.
Modifications to this product not authorized by Cisco could void the FCC approval and negate your authority to operate the product
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version
©
of the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED "AS IS" WITH ALL FAULTS. CISCO
AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS
FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR
ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output,
network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is
unintentional and coincidental.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL:
www.cisco.com go trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship
between Cisco and any other company. (1721R)
02018 Cisco Systems, Inc. All rights reserved.
CONTENTS
PREFACE Preface xxvii

Revision History xxvii
Document Objectives xxviii
Audience xxviii
Document Organization xxviii
Document Conventions xxix
Related Documentation xxxv
Obtaining Optical Networking Information xxxvi
Where to Find Safety and Warning Information xxxvi
Obtaining Documentation and Submitting a Service Request xxxvi
PREFACE Cisco ONS Documentation Roadmap for Release 10.x.x xxxvii
PREFACE New and Changed Information xxxix
CHAPTER Setting Up Optical Service Channel Cards 1

1
Card Compatibility 2
Class 1 Laser Safety Labels 2
OSCM Card 2
OSCM Card Functions 3
OSCM Card Power Monitoring 3
OSC-CSM Card 4
OSC-CSM Card Functions 5
OSC-CSM Card Power Monitoring 5
Cisco ONS 15454 DWDM Line Card Configuration Guide, Release 10.x.x
iii
Contents
CHAPTER Provisioning Optical Amplifier Cards 7

2
Applications of Amplifiers 8
OPT-PRE Amplifier Card 11
Related Procedures for OPT-PRE Card 12

OPT-BST and OPT-BST-E Amplifier Card 12
Related Procedures for OPT-BST and OPT-BST-E Cards 13
OPT-BST-L Amplifier Card 14
Related Procedures for OPT-BST-L Card 14
OPT-AMP-L Card 15
Related Procedures for OPT-AMP-L Card 16
OPT-AMP-17-C Card 16
Related Procedures for OPT-AMP-17-C Card 17
OPT-AMP-C Card 18
Related Procedures for OPT-AMP-C Card 19
OPT-RAMP-C and OPT-RAMP-CE Cards 19
Related Procedures for OPT-RAMP-C and OPT-RAMP-CE Cards 21

RAMAN-CTP and RAMAN-COP Cards 21
Important Notes Regarding Patchcord Installation 22

RAMAN-CTP and RAMAN-COP Cards Power Monitoring 22
Related Procedures for RAMAN-CTP and RAMAN-COP Cards 23
OPT-EDFA-17, OPT-EDFA-24, and OPT-EDFA-35 Cards 24
OPT-EDFA-17, OPT-EDFA-24, and OPT-EDFA-35 Cards Power Monitoring 26
Related Procedures for OPT-EDFA-17, OPT-EDFA-24, and OPT-EDFA-35 Cards 27
EDRA-1-xx and EDRA-2-xx Cards 27
EDRA Workflow Diagram 28
EDRA-1-xx and EDRA-2-xx Cards Power Monitoring 29
Related Procedures for EDRA-1-xx and EDRA-2-xx Cards 30
Provisioning Multiplexer and Demultiplexer Cards 31

CHAPTER
3
Optical Performance Parameters 32
DWDM Channel Allocation Plan 36
iv
Contents
Safety Labels 39
32MUX-O Card 40
32MUX-O Card Functions 40
Port-Level Indicators for the 32MUX-O Cards 40
32MUX-O Channel Plan 40
Power Monitoring 42
Related Procedures for the 32MUX-O Card 42
32DMX-O Card 42
32DMX-O Card Functions 42
Port-Level Indicators for the 32DMX-O Card 43
Power Monitoring 43
Related Procedures for the 32DMX-O Card 43
4MD-xx.x Card 44
4MD-xx.x Card Functions 44
Port-Level Indicators for the 4MD-xx.x Cards 45
Wavelength Pairs 45
Power Monitoring 45
Related Procedures for the 4MD-xx.x Card 46
12-AD-FS Card 46
16-AD-FS Card 47
Related Procedures for the 12-AD-FS and 16-AD-FS Cards 48
CHAPTER Setting Up Tunable Dispersion Compensating Units 49

4
Safety Labels 49
TDC-CC and TDC-FC Cards 50
Key Features 50
Optical Ports 51
TDC-CC and TDC-FC Card Functions 51
Optical Performance 51
Related Procedures for TDC-CC and TDC-FC Cards 52
Provisioning Protection Switching Module 53

CHAPTER
5
PSM Card 53
Key Features 54
v
Contents
PSM Card-Level Indicators 54

PSM Bidirectional Switching 54
Automatic PSM Reversion 56
Related Procedures for PSM Card 56
CHAPTER Provisioning Optical Add/Drop Cards 59

6
Safety Labels 59
Card Overview 59
DWDM Card Channel Allocation Plan 60
AD-1C-xx.x, AD-2C-xx.x, and AD-4C-xx.x Cards 62
AD-1C-xx.x Card 62
AD-2C-xx.x Card 62
AD-4C-xx.x Card 63
Features of AD-1C-xx.x, AD-2C-xx.x, and AD-4C-xx.x Cards 63
Power Monitoring 63
Related Procedures for AD-1C-xx.x, AD-2C-xx.x, and AD-4C-xx.x Cards 64
AD-1B-xx.x and AD-4B-xx.x Cards 65
AD-1B-xx.x Card 65
AD-4B-xx.x Card 65
Features of AD-1B-xx.x and AD-4B-xx.x Cards 66
Power Monitoring 66
Related Procedures for AD-1B-xx.x and AD-4B-xx.x Cards 67
CHAPTER Provisioning Reconfigurable Optical Add/Drop Cards 69

7
Channel Allocation Plans 71

Safety Labels 74
32WSS and 32WSS-L Cards 74
32WSS and 32WSS-L ROADM Functionality 75
32WSS and 32 WSS-L Power Monitoring 75

32WSS and 32WSS-L Channel Allocation Plan 76
Related Procedures for 32WSS and 32WSS-L Cards 79
32DMX and 32DMX-L Cards 79
vi
Contents
32DMX and 32DMX-L ROADM Functionality 79

32DMX and 32DMX-L Power Monitoring 80
32DMX and 32DMX-L Channel Allocation Plan 80
Related Procedures for 32DMX and 32DMX-L Cards 80
40-DMX-C and 40-DMX-CE Card 81
40-DMX-C and 40-DMX-CE ROADM Functionality 82
40-DMX-C and 40-DMX-CE Power Monitoring 82
40-DMX-C and 40-DMX-CE Channel Plan 82
Related Procedures for 40-DMX-C and 40-DMX-CE Cards 86
40-MUX-C Card 86
40-MUX-C Card Power Monitoring 87
40-MUX-C Card Channel Plan 88
Related Procedures for 40-MUX-C Card 88
40-WSS-C and 40-WSS-CE Card 88
40-WSS-C and 40-WSS-CE ROADM Functionality 90
40-WSS-C and 40-WSS-CE Power Monitoring 90
40-WSS-C and 40-WSS-CE Channel Plan 91
Related Procedures for 40-WSS-C and 40-WSS-CECards 91
40-WXC-C Card 91
40-WXC-C Power Monitoring 93
40-WXC-C Channel Plan 94
Related Procedures for 40-WXC-C Card 94
80-WXC-C Card 94
80-WXC-C Power Monitoring 96
80-WXC-C Channel Plan 97
Related Procedures for 80-WXC-C Card 101
16-WXC-FS Card 102
16-WXC-FS Ports 102
Key Features 103
16-WXC-FS Power Monitoring 104
Task Flow Diagram of 16-WXC-FS Card 105
Related Procedures for 16-WXC-FS Card 105
Single Module ROADM (SMR-C) Cards 106
SMR-C Card Key Features 106
vii
Contents
40-SMR1-C Card 107

40-SMR1-C Power Monitoring 109
40-SMR1-C Channel Plan 109
40-SMR2-C Card 110
40-SMR2-C Power Monitoring 112
40-SMR2-C Channel Plan 113
Related Procedures for 40-SMR1-C and 40-SMR2-C Card 113
17 SMR9 FS, 24 SMR9 FS, 34 SMR9 FS, and SMR20 FS/SMR20 FS CV Cards 113
SMR9 FS Ports 114
SMR20 FS and SMR20 FS CV Ports 115
Key Features 115
Connection Verification 116
Connection Verification Prerequisites 117
Supported Cards 117
Running the Connection Verification 117
PIDs of 17 SMR9 FS, 24 SMR9 FS, 34 SMR9 FS, and SMR20 FS/SMR20 FS CV Cards 118 Related
Procedures for 17 SMR9 FS, 24 SMR9 FS, 34 SMR9 FS, and SMR20 FS/SMR20 FS CV
Cards 119
MMU Card 119
MMU Power Monitoring 120
Related Procedures for MMU Card 120
CHAPTER Provisioning Transponder and Muxponder Cards 121

8
Card Overview 123

Safety Labels 129
Interface Classes 129
TXP_MR_10G Card 140
Related Procedures for TXP_MR_10G Card 141
TXP_MR_10E Card 141
TXP_MR_10E Functions 142
Related Procedures for TXP_MR_10E Card 143
TXP_MR_10E_C and TXP_MR_10E_L Cards 143
Key Features 143
viii
Contents
Faceplates and Block Diagram 144

TXP_MR_10E_C and TXP_MR_10E_L Functions 144
Related Procedures for TXP_MR_10E_C and TXP_MR_10E_L Cards 145
TXP_MR_2.5G and TXPP_MR_2.5G Cards 145
Related Procedures for TXP_MR_2.5G and TXPP_MR_2.5G Cards 147
40E-TXP-C and 40ME-TXP-C Cards 148
Related Procedures for 40E-TXP-C and 40ME-TXP-C Cards 148
MXP_2.5G_10G Card 148
Related Procedures for MXP_2.5G_10G Card 149
MXP_2.5G_10E Card 150
Key Features 150
MXP_2.5G_10E Functions 151
Wavelength Identification 151
Related Procedures for MXP_2.5G_10E Card 152
MXP_2.5G_10E_C and MXP_2.5G_10E_L Cards 153
Key Features 153
MXP_2.5G_10E_C and MXP_2.5G_10E_L Functions 154
Related Procedures for MXP_2.5G_10E_C and MXP_2.5G_10E_L Cards 158
MXP_MR_2.5G and MXPP_MR_2.5G Cards 158
Faceplates and Block Diagram 161
MXP_MR_2.5G and MXPP_MR_2.5G Functions 162
Related Procedures for MXP_MR_2.5G and MXPP_MR_2.5G Cards 163

MXP_MR_10DME_C and MXP_MR_10DME_L Cards 163
Key Features 165
MXP_MR_10DME_C and MXP_MR_10DME_L Functions 167
Related Procedures for MXP_MR_10DME_C and MXP_MR_10DME_L Cards 170
40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards 170
Key Features 172
Related Procedures for 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards 175

GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards 175
Key Features 177
Protocol Compatibility list 179
ix
Contents
Client Interface 180

DWDM Trunk Interface 181
Configuration Management 181
Security 182
Card Protection 182
Related Procedures for Card Protection 182
IGMP Snooping 182
IGMP Snooping Guidelines and Restrictions 183
Fast-Leave Processing 184
Static Router Port Configuration 184
Report Suppression 184
IGMP Statistics and Counters 184
Related Procedure for Enabling IGMP Snooping 185
Multicast VLAN Registration 185
Related Procedure for Enabling MVR 185
MAC Address Learning 185
Related Procedure for MAC Address Learning 186
MAC Address Retrieval 186
Related Procedure for MAC Address Retrieving 186
Link Integrity 186
Related Procedure for Enabling Link Integrity 187
Ingress CoS 187
Related Procedure for Enabling Ingress CoS 187
CVLAN Rate Limiting 187
Advantages of LACP 189

Functions of LACP 189
Modes of LACP 189
Parameters of LACP 189
Unicast Hashing Schemes 190
LACP Limitations and Restrictions 190
x
Contents
Related Procedure for LACP 190

Ethernet Connectivity Fault Management 191
Maintenance Domain 191
Maintenance Association 191
Maintenance End Points 191
Maintenance Intermediate Points 192
CFM Messages 192
CFM Limitations and Restrictions 192
Related Procedure for Ethernet CFM 192
Ethernet OAM 193
Components of the Ethernet OAM 193
Benefits of the Ethernet OAM 193
Features of the Ethernet OAM 193
Ethernet OAM Limitations and Restrictions 194
Related Procedure for Ethernet OAM 194
Resilient Ethernet Protocol 194
REP Segments 195
Characteristics of REP Segments 195
REP Port States 195
Link Adjacency 195
Fast Reconvergence 196
VLAN Load Balancing 196
REP Configuration Sequence 196
REP Supported Interfaces 196
REP Limitations and Restrictions 197
Related Procedures for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards 198
ADM-10G Card 198

Key Features 199
ADM-10G POS Encapsulation, Framing, and CRC 199
POS Overview 200
POS Framing Modes 200
GFP Interoperability 201
LEX Interoperability 201
xi
Contents
Faceplate and Block Diagram 202

Port Configuration Rules 203
Client Interfaces 203
Interlink Interfaces 204
Security 206
Protection 206
Circuit Protection Schemes 206
Port Protection Schemes 206
Circuit Provisioning 206
ADM-10G CCAT and VCAT Characteristics 208
Available Circuit Sizes 209
Related Procedure for VCAT Circuit 209
Intermediate Path Performance Monitoring 210
Related Procedure for IPPM 210
Pointer Justification Count Performance Monitoring 210
Performance Monitoring Parameter Definitions 211
ADM-10G Functions 214
Related Procedures for ADM-10G Card 214
DLP-G775 Displaying the Bandwidth Usage of the STS Timeslots 214
OTU2_XP Card 215
Key Features 216
OTU2_XP Card Interface 218
Trunk Interface 218
OTU2_XP Card Configuration Rules 220
Security 222
ODU Transparency 222
Related Procedures for OTU2_XP Card 223
TXP_MR_10EX_C Card 223
Key Features 224
Related Procedures for TXP_MR_10EX_C Card 224
xii
Contents
MXP_2.5G_10EX_C card 224

Key Features 225
MXP_2.5G_10EX_C Functions 227
Related Procedures for MXP_2.5G_10EX_C Card 229
MXP_MR_10DMEX_C Card 229
Key Features 231
MXP_MR_10DMEX_C Functions 233
Related Procedures for MXP_MR_10DMEX_C Card 235
AR_MXP, AR_XP, and AR_XPE Cards 236
Key Features 237
TXP_MR (Unprotected Transponder) 242
TXPP_MR (Protected Transponder) 243
MXP_DME (Unprotected Data Muxponder) 244
MXPP_DME (Protected Data Muxponder) 245
MXP_MR (Unprotected Multirate Muxponder) 246
MXPP_MR (Protected Multirate Muxponder) 248
MXP-4x2.5-10G (OC48/OTU1 Unprotected Muxponder) 250
MXPP-4x2.5-10G (OC48/OTU1 Protected Muxponder) 251
MXP_MR_S (Unprotected Multirate Muxponder-Static) and MXPP_MR_S (Protected Multirate
Muxponder-Static) 251
RGN (OTU1/OTU2 Regenerator) 251
MXP-VD-10G (Video Muxponder) 253
Scenario 1 253
Scenario 2 254
Scenario 3 255
Scenario 4 255
Scenario 5 256
AR_MXP, AR_XP, and AR_XPE Functions and Features 257

Related Procedures for AR_MXP, AR_XP, and AR_XPE Cards 257
100G-LC-C, 100G-ME-C, 100G-CK-C, 100GS-CK-LC, 100ME-CKC, and 200G-CK-LC Cards 257
xiii
Contents
Key Features 259
Operating Modes for 100G-LC-C, 100G-ME-C, 100G-CK-C, 100GS-CK-LC, 200G-CK-LC,

and 100ME-CKC Cards 259
10x10G-LC Card 262
Operating Modes for 10x10G-LC Card 262
CFP-LC Card 265
Key Features 266
Operating Modes for CFP-LC Card 266
MR-MXP Card 267
Key Features 268
Operating Modes for MR-MXP Card 268
Limitations of Payloads on MR-MXP Card 271
Key Features of 100G-LC-C, 100G-ME-C, 100G-CK-C, 100ME-CKC, 10x10G-LC, 100GS-CK-LC,

200G-CK-LC, CFP-LC, and MR-MXP Cards 271
Functions and Features 281
Related Procedures for 100G-LC-C, 100G-ME-C, 100G-CK-C, 100ME-CKC, 10x10G-LC, CFP-LC,

100GS-CK-LC, 200G-CK-LC, and MR-MXP Cards 282
400G-XP-LC Card 282
Key Features 283
OTN Cross-connect Capability on 400G-XP-LC Cards 287
OTNXC Constraints 287
ODU Utilization Panes 288
OTNXC Exceptions 288
Interoperability 288
PRBS Support on the 400G-XP-LC Card 299

Limitations of PRBS Support on 400G-XP-LC card 300
GCC0 Support on the 400G-XP-LC Card 300
2x150G Support on the 400G-XP-LC Card 301
Limitations of 2x150G Support on the 400G-XP-LC Card 301
Related Procedures for 400G-XP-LC Cards 301
Supported MSM Configurations 302
WSE Card 303
xiv
Contents
Key Features 304

WSE Workflow Diagram 305
Multiple Operating Modes 306
TXP-10G 306
RGN-10G 307
Card Authentication 307
Key Management 307
Payload Encryption 307
AES Secure Packet 308
Functions and Features 308
Scenarios that Affect Traffic 308
Related Procedures for WSE Card 309
MLSE UT 309
Error Decorrelator 309
SFP, SFP+, QSFP+, XFP, CXP, CFP, CFP2 and CPAK Modules 310
NTP-G128 Managing Pluggable Port Modules 310
DLP-G235 Changing the 2.5G Data Muxponder Card Mode 312
DLP-G332 Changing the 10G Data Muxponder Port Mode 313
DLP-G379 Changing the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode 315
DLP-G411 Provisioning an ADM-10G PPM and Port 317
DLP-G452 Changing the OTU2_XP Card Mode 318
DLP-G274 Verifying Topologies for ETR_CLO and ISC Services 319
DLP-G278 Provisioning the Optical Line Rate 321
Transponder and Muxponder Protection Topologies 328
Y-Cable Protection 329
Splitter Protection 332
Switch Criteria 332
Switch Priority 332
Line Conditions on the Trunk 333
Line Conditions on the Client 333
Switch Commands 334
Unidirectional and Bidirectional Switching 334
Other Switch Criteria 334
Switch Stability 335
xv
Contents
Revertive and Nonrevertive Attributes 335
Communications Channels 336
Inherited Port Properties 336
Switch Status Reporting 336
Switch Conditions 337
Protection Switching Performance Requirements 337
Usability Requirements 338
Regeneration Groups 338
Automatic Laser Shutdown 338
Client Signal Failures 338
In-service Upgrade 338
Path Diversion Support for Client Protection 339
NTP-G33 Creating a Y-Cable Protection Group 339
Protection Types 343
NTP-G199 Creating a Splitter Protection Group 345
NTP-G198 Creating 1+1 Protection for Cards 347
DLP-G461 Creating a 1+1 Protection Group for Cards 348
NTP-G98 Provisioning the 2.5G Multirate Transponder Card Line Settings and PM Parameter
Thresholds 349
DLP-G229 Changing the 2.5G or 10G Transponder Card Settings 350
DLP-G230 Changing the 2.5G Multirate Transponder Line Settings 353
DLP-G231 Changing the 2.5G Multirate Transponder Line Section Trace Settings 356
DLP-G367 Changing the Multirate Transponder Trunk Wavelength Settings 357
DLP-G232 Changing the Multirate Transponder SONET or SDH Line Threshold Settings 359
DLP-G320 Changing the 2.5G Multirate Transponder Line RMON Thresholds 364
366
DLP-G306 Provisioning the 2.5G Multirate Transponder Client Port Alarm and TCA Thresholds
368
DLP-G234 Changing the Multirate Transponder OTN Settings 372
NTP-G96 Provisioning the 10G Multirate Transponder Card Line Settings, PM Parameters, and
Thresholds 377
DLP-G365 Provisioning the TXP_MR_10G Data Rate 378
DLP-G712 Provisioning the TXP_MR_10E or TXP_MR_10EX_C Data Rate 379
DLP-G217 Changing the 10G Multirate Transponder Line Settings 380
xvi
Contents
DLP-G218 Changing the 10G or 40G Multirate Transponder Line Section Trace Settings 385
DLP-G319 Changing the 10G Multirate Transponder Line RMON Thresholds for 10G Ethernet
LAN Phy Payloads 388
DLP-G301 Provisioning the 10G Multirate Transponder Trunk Port Alarm and TCA Thresholds
392
DLP-G302 Provisioning the 10G Multirate Transponder Client Port Alarm and TCA Thresholds
393
NTP-G292 Provisioning the 40G Multirate Transponder Card Line Settings, PM Parameters,
and Thresholds 396
DLP-G656 Provisioning the 40E-TXP-C and 40ME-TXP-C Data Rate 397
DLP-G657 Changing the 40G Multirate Transponder Card Settings 398

DLP-G658 Changing the 40G Multirate Transponder Line Settings 400
DLP-G659 Changing the 40G Multirate Transponder SONET, SDH, or Ethernet Line Settings 403
DLP-G692 Changing the 40G Multirate Transponder OTU Settings 408
DLP-G661 Changing the 40G Multirate Transponder Line Thresholds for SONET or SDH Payloads
410
413
414
NTP-G170 Provisioning the ADM-10G Card Peer Group, Ethernet Settings, Line Settings, PM
Parameters, and Thresholds 416
DLP-G403 Creating the ADM-10G Peer Group 417
DLP-G469 Provisioning the ADM-10G Card Ethernet Settings 418
DLP-G397 Changing the ADM-10G Line Settings 419
DLP-G398 Changing the ADM-10G Line Section Trace Settings 425
DLP-G399 Changing the ADM-10G Line Thresholds for SONET and SDH Payloads 427
DLP-G412 Changing the ADM-10G Line RMON Thresholds for the 1G Ethernet Payload
432
DLP-G400 Provisioning the ADM-10G Interlink or Trunk Port Alarm and TCA Thresholds 435
DLP-G401 Provisioning the ADM-10G Client Port Alarm and TCA Thresholds 437
DLP-G402 Changing the ADM-10G OTN Settings 438
NTP-G333 Adding an ADM-10G Card to an Existing Topology 445
NTP-G97 Modifying the 4x2.5G Muxponder Card Line Settings and PM Parameter Thresholds 446
DLP-G222 Changing the 4x2.5G Muxponder Card Settings 447
DLP-G223 Changing the 4x2.5G Muxponder Line Settings 449
xvii
Contents
DLP-G224 Changing the 4x2.5G Muxponder Section Trace Settings 454

DLP-G225 Changing the 4x2.5G Muxponder Trunk Settings 456
DLP-G369 Changing the 4x2.5G Muxponder Trunk Wavelength Settings 458
DLP-G226 Changing the 4x2.5G Muxponder SONET/SDH Line Thresholds Settings 459
DLP-G303 Provisioning the 4x2.5G Muxponder Trunk Port Alarm and TCA Thresholds 463
DLP-G304 Provisioning the 4x2.5G Muxponder Client Port Alarm and TCA Thresholds 465
DLP-G228 Changing the 4x2.5G Muxponder Line OTN Settings 466
NTP-G99 Modifying the 2.5G Data Muxponder Card Line Settings and PM Parameter Thresholds
472
DLP-G236 Changing the 2.5G or 10G Data Muxponder Client Line Settings 473
DLP-G237 Changing the 2.5G Data Muxponder Distance Extension Settings 477
DLP-G238 Changing the 2.5G or 10G Data Muxponder SONET/SDH Settings 479
DLP-G239 Changing the 2.5G or 10G Data Muxponder Section Trace Settings 482
DLP-G370 Changing the 2.5G or 10G Data Muxponder Trunk Wavelength Settings 484
DLP-G240 Changing the 2.5G or 10G Data Muxponder SONET or SDH Line Thresholds 485
DLP-G321 Changing the 2.5G or 10G Data Muxponder Line RMON Thresholds 489
DLP-G307 Provisioning the 2.5G Data Muxponder Trunk Port Alarm and TCA Thresholds 493
DLP-G308 Provisioning the 2.5G Data Muxponder Client Port Alarm and TCA Thresholds 494
NTP-G148 Modifying the 10G Data Muxponder Card Line Settings and PM Parameter Thresholds
497
DLP-G334 Changing the 10G Data Muxponder Distance Extension Settings 499
DLP-G338 Provisioning the 10G Data Muxponder Trunk Port Alarm and TCA Thresholds 501
DLP-G339 Provisioning the 10G Data Muxponder Client Port Alarm and TCA Thresholds 502
DLP-G366 Changing the 10G Data Muxponder OTN Settings 505
NTP-G293 Modifying the 40G Muxponder Card Line Settings and PM Parameter Thresholds 508
DLP-G662 Changing the 40G Multirate Muxponder Card Settings 509
DLP-G666 Changing the 40G Muxponder Line Settings 512
DLP-G735 Provisioning the 40G Muxponder Ethernet Settings 517
DLP-G667 Changing the 40G Muxponder SONET (OC-192)/SDH (STM-64) Settings 519
DLP-G668 Changing the 40G Muxponder Section Trace Settings 520
DLP-G691 Changing the 40G Muxponder OTU Settings 522
DLP-G669 Changing the 40G Muxponder SONET or SDH Line Thresholds 524
DLP-G670 Changing the 40G Muxponder Line RMON Thresholds for Ethernet, 8G FC, or 10G
FC Payloads 527
DLP-G671 Provisioning the 40G Muxponder Trunk Port Alarm and TCA Thresholds 532
xviii
Contents
DLP-G672 Provisioning the 40G Muxponder Client Port Alarm and TCA Thresholds 533
DLP-G673 Changing the 40G Muxponder OTN Settings 537

NTP-G281 Managing the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Channel Group Settings
541
DLP-G611 Creating a Channel Group Using CTC 542

DLP-G612 Modifying the Parameters of the Channel Group Using CTC 544
DLP-G613 Managing Ports in a Channel Group 548
DLP-G614 Deleting a Channel Group 549
DLP-G615 Retrieving Information on Channel Group, REP, CFM, and EFM 550
DLP-G616 Viewing PM Parameters of a Channel Group 551
DLP-G617 Viewing Utilization PM Parameters of a Channel Group 551
DLP-G618 Viewing History PM Parameters of a Channel Group 552
NTP-G283 Managing the Card CFM Settings 553
DLP-G621 Enabling CFM on a Card 554
DLP-G622 Enabling CFM for a Port 555
DLP-G623 Creating a Maintenance Domain Profile 556
DLP-G624 Deleting a Maintenance Domain Profile 556
DLP-G625 Creating a Maintenance Association Profile 557
DLP-G626 Modifying a Maintenance Association Profile 558
DLP-G627 Deleting a Maintenance Association Profile 559
DLP-G628 Mapping Profiles 559
DLP-G629 Creating a MEP 560
DLP-G630 Deleting a MEP 561
DLP-G631 Creating a MIP 562
DLP-G632 Deleting a MIP 563
DLP-G633 Pinging a MEP 563
DLP-G634 Displaying Output of a Traceroute MEP 564
NTP-G285 Managing the Card EFM Settings 565
DLP-G639 Enabling EFM for a Port 566
DLP-G640 Configuring EFM Parameters 567
DLP-G641 Configuring EFM Link Monitoring Parameters 568
DLP-G642 Enabling Remote Loopback for a Port 570
NTP-G287 Managing the Card REP Settings 571
DLP-G713 Provisioning Administrative VLAN for Ports in a REP Segment 572
xix
Contents
DLP-G645 Creating a Segment 573

DLP-G646 Editing a Segment 575
DLP-G647 Activating VLAN Load Balancing 576
DLP-G648 Deactivating VLAN Load Balancing 577
NTP-G165 Modifying the Ethernet, Line and PM Thresholds 577
DLP-G380 Provisioning Ethernet Settings 579
DLP-G684 Provisioning the PDH Ethernet Settings 590
DLP-G685 Provisioning the Electrical Lines 592
DLP-G381 Provisioning Layer 2 Protection Settings 595
DLP-G507 Enabling a Different GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Card as Master Card
597
DLP-G382 Adding SVLANS to NNI Ports 598

DLP-G383 Provisioning the Quality of Service Settings 599
DLP-G470 Provisioning the CoS Settings 600
DLP-G384 Provisioning the QinQ Settings 601
DLP-G221 Enabling MAC Address Learning on SVLANs 603
DLP-G460 Enabling MAC Address Learning on SVLANs for GE_XPE or 10GE_XPE Cards 604
DLP-G385 Provisioning the MAC Filter Settings 605

NTP-G237 Retrieving and Clearing MAC Addresses on SVLANs 606
DLP-G546 Viewing MAC Addresses on a Card 607
NTP-G311 Provisioning the Storm Control Settings 608
NTP-G205 Enabling Link Integrity on a Card 609
DLP-G509 Enabling Link Integrity Using CTC 610
DLP-G289 Provisioning CVLAN Rate Limiting on a Card 611
NTP-G208 Provisioning SVLAN Rate Limiting on a Card 611
DLP-G515 Provisioning SVLAN Rate Limiting Using CTC 612
DLP-G471 Creating SVLAN or CVLAN Profile 613
NTP-G204 Enabling IGMP Snooping on a Card 614
DLP-G511 Enabling IGMP Snooping, Fast Leave, Report Suppression, and Protection 615
NTP-G206 Enabling MVR on a Card 616
DLP-G513 Enabling MVR Using CTC 617
DLP-G386 Provisioning the Trunk Port Alarm and TCA Threshold 618
DLP-G387 Provisioning the Client Port Alarm and TCA Thresholds 619
DLP-G388 Changing the RMON Threshold 621
xx
Contents
DLP-G389 Changing OTN Settings 626
NTP-G314 Adding a Card on FAPS Ring 629
DLP-G687 Adding a Card Facing the Master Card on FAPS Ring 630
DLP-G688 Adding a Card Between Slave Cards on FAPS Ring 631
NTP-G197 Provisioning the OTU2_XP Card Line Settings, PM Parameters, and Thresholds 632
DLP-G453 Changing the OTU2_XP Card Settings 633
DLP-G454 Changing the OTU2_XP Line Settings 635
DLP-G455 Changing the OTU2_XP Line Section Trace Settings 641
DLP-G456 Changing the OTU2_XP Line Thresholds for SONET or SDH Payloads 643
DLP-G457 Provisioning the OTU2_XP Port Alarm and TCA Threshold 647
DLP-G462 Changing the OTU2_XP Line RMON Thresholds 649
DLP-G458 Changing the OTU2_XP OTN Settings 653 DLP-G523 Changing the OTU2_XP
Path Trace Settings 660 DLP-G524 Provisioning the OTU2_XP Path Settings for 10G
Ethernet LAN Phy to WAN Phy
Configuration 661
NTP-G162 Changing the ALS Maintenance Settings 662
NTP-G302 Configuring Loopback on a Card 664
NTP-G299 Configuring Backplane Loopback on a Card 666
NTP-G192 Forcing FPGA Update 668
NTP-G196 Forcing FPGA Update on a Card in Protection Group 669
NTP-G232 Enabling Error Decorrelator 670
NTP-G315 Enabling the Wavelength Drifted Channel Automatic Shutdown Feature 671
NTP-G316 Enabling REP and FAPS on the Same Port 671
NTP-G321 Provisioning Multiple Operating Modes 672
NTP-G322 Modifying the Card Line Settings and PM Parameter Thresholds 673
DLP-G695 Changing the Card Line Settings 674
DLP-G696 Changing the AR_MXP, AR_XP, or AR_XPE Card Ethernet Settings 678
DLP-G697 Changing the AR_MXP, AR_XP, or AR_XPE Card SONET/SDH Settings 680
DLP-G698 Changing the AR_MXP, AR_XP, or AR_XPE Card Section Trace Settings 685
DLP-G699 Enabling Auto-sensing for AR_MXP, AR_XP, or AR_XPE Cards 687 DLP-G700
Changing the AR_MXP, AR_XP, or AR_XPE Card SONET/SDH Line Thresholds 688 DLP-G701
Changing the AR_MXP, AR_XP, or AR_XPE Card Line RMON Thresholds 691 DLP-G702
Provisioning the AR_MXP, AR_XP, or AR_XPE Card with Trunk Port Alarm and TCA
Thresholds 697
xxi
Contents
DLP-G703 Provisioning the AR_MXP, AR_XP, or AR_XPE Card Client Port Alarm and TCA
Thresholds 698
DLP-G704 Changing the AR_MXP, AR_XP, or AR_XPE Card OTN Settings 702
DLP-G734 Viewing the Mapping of ODU Object with Client Port 707
NTP-G235 Provisioning an Operating Mode 708
NTP-G361 Provisioning an Operating Mode on the 400G-XP-LC Card 709
NTP-G362 Manual FPGA Upgrade on the 400G-XP-LC Card 711
NTP-G366 Viewing the ODU Utilization for ODU Circuits 712
NTP-G367 Provisioning Encryption on 400G-XP-LC Card 713
DLP-G817 Configuring GCC2 Settings on 400G-XP-LC Card 714
DLP-G818 Enabling or Disabling Card Authentication and Payload Encryption on 400G-XP-LC

Card 715
DLP-G819 Resetting the Master Key on 400G-XP-LC Card 716
DLP-G820 Changing the Master Key Reset Interval on 400G-XP-LC Card 717
Limitations of Encryption on 400G-XP-LC Card 717
NTP-G236 Modifying the 100G-LC-C, 100G-CK-C, 100G-ME-C, 100ME-CKC, 10x10G-LC,

100GS-CK-LC, , 200G-CK-LC, CFP-LC, WSE, MR-MXP, or 400G-XP-LC Card Line
Settings and PM Parameter Thresholds 718
DLP-G714 Changing the Card Line Settings 719
DLP-G715 Changing the Card Ethernet Settings 733
DLP-G716 Changing the 10x10G-LC and WSE Card SONET/SDH Settings 736
DLP-G717 Changing the 10x10G-LC and WSE Card Section Trace Settings 740
DLP-G718 Changing the 10x10G-LC and WSE Card SONET/SDH Line Thresholds 742
DLP-G719 Changing the Card Line RMON Thresholds 745
DLP-G720 Provisioning the Card with Trunk Port Alarm and TCA Thresholds 751
DLP-G721 Provisioning the Client Port Alarm and TCA Thresholds 752
DLP-G722 Changing the Card OTN Settings 753
DLP-G815 Changing the 400G-XP-LC Card ODU Settings 762
DLP-G770 Enabling PRBS Settings 765
NTP-G351 Retrieving MAC Addresses on MR-MXP Cards 766
NTP-G338 Provisioning an Operating Mode on the WSE Card 767
NTP-G339 Modifying the WSE Card Line Settings and PM Parameter Thresholds 768
DLP-G739 Changing the WSE Card Line Settings 769
DLP-G740 Changing the WSE Card Ethernet Settings 772
xxii
Contents
DLP-G744 Changing the WSE Card Security Thresholds and Setting Authentication Error
Thresholds 774
DLP-G745 Changing the WSE Card Line RMON Thresholds 775
DLP-G746 Provisioning the WSE Card with Port Alarm and TCA Thresholds 779
DLP-G747 Change the WSE Card OTN Settings 780
NTP-G340 Provisioning Encryption on the WSE and MR-MXP Cards 784
DLP-G759 Configuring GCC2 Settings 785
DLP-G748 Enabling or Disabling Card Authentication 786
DLP-G749 Enabling Payload Encryption 786
DLP-G Enabling Payload Authentication 787
DLP-G751 Resetting the Master Key 788
DLP-G752 Changing the Master Key Reset Interval 789
DLP-G753 Setting AES Secure Packet Configuration 790
DLP-G754 Specifying ESP Header and Trailer Locations 791
DLP-G755 Enabling PRBS Generation and Monitoring 792
NTP-G342 Provisioning FIPS and CC Mode 793
DLP-G761 Enabling FIPS and CC Mode 793
DLP-G760 Configuring Management of FIPS and CC Mode Enabled NE 794
NTP-G363 Provisioning LSE on Cards 796
DLP-G803 Installing Locally Significant Certificates on Cards 797
DLP-G804 Switching Between LSC and MIC on Cards 798
DLP-G805 Viewing Certificates 799
APPENDIX Configuring GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards Using PCLI 801
A
Pseudo Command Line Interface Reference 803

APPENDIX
B
Card Features 805

APPENDIX Safety Labels 806
C
Class 1 Laser Product Cards 806

Class 1 Laser Product Label 806
Hazard Level 1 Label 807
Laser Source Connector Label 807
FDA Statement Labels 807
xxiii
Contents
Shock Hazard Label 808
Class 1M Laser Product Cards 808
Class 1M Laser Product Statement 808
Hazard Level 1M Label 809
Laser Source Connector Label 809
FDA Statement Labels 809
Shock Hazard Label 810
Burn Hazard Label 810
Automatic Laser Shutdown 811
Card-Level Indicators 811
Card-level LEDs for Transponder, Muxponder and Control Cards 811
Card-level LEDs on the AIC-I Card 812
Card-level LEDs on the MS-ISC-100T Card 813
Card-level LEDs on the Multiplexer, Demultiplexer and Optical Amplifier Cards 813
Card-level LEDs on OSCM and OSC-CSM Cards 814
Port-Level Indicators 815
Port-level LEDs 815
Port-level LEDs on the TXP_MR_10G and MXP_2.5G_10G Cards 816
Port-level LEDs on the TXPP_MR_2.5G Card 816
Port-level LEDs on the GE_XP, 10DME and 40G Cards 817
Port-level LEDs on the MXP_MR_2.5G and MXPP_MR_2.5G Cards 818
Port-level LEDs on the ADM-10G and OTU2_XP Cards 818
Port-level LEDs on the 100G-LC-C, 10x10G-LC, CFP-LC, 100GS-CK-LC, 200G-CK-LC,
Power-level LEDs on the Control Cards 820

Network-level LEDs on the Control Cards 820
Ethernet Port-level LEDs on the Control Cards 821
SFP LEDs on TNC, TNCE, and TNCS Cards 821
DWDM Interface 822
FEC 823
FEC Modes for the TXP_MR_10E and MXP_2.5G_10E Cards 823
FEC Modes for the AR_MXP, AR_XP and AR_XPE Cards 824
xxiv
Contents
FEC Modes for 100G-LC-C, CFP-LC, 100G-CK-C, 100GS-CK-LC, 200G-CK-LC, and 400G-XP-
LC Cards 824
FEC Threshold Bit Error Correction Values 826
Client-to-Trunk Mapping 826

Timing Synchronization 826
Multiplexing Function 828
SONET/SDH Overhead Byte Processing 828
Client Interface Monitoring 828
Jitter 829
Lamp Test 829
NTP-G335 Performing Lamp Test 829
Onboard Traffic Generation 830
Performance Monitoring 830
Distance Extension 830
Interoperability with Cisco MDS Switches 830
Client and Trunk Ports 830
Automatic Power Control 831
Alarms and Thresholds 831
Card Protection 831
Y-Cable and Splitter Protection 831
Y-Cable Protection Availability on TXP, MXP, and Xponder Cards 832
Setting-up Y-Cable Protection 833
Splitter Protection 835
1+1 Protection 836
Layer 2 Over DWDM Protection 837
Far-End Laser Control 837
Jitter Considerations 838
Termination Modes 838
APPENDIX Card Specifications 841

D
Administrative and Service States 843

APPENDIX
E
SNMP 845
APPENDIX
F
xxv
Contents
APPENDIX CTC Enhancements, Operations, and Shortcuts 847

G
APPENDIX H
Network Element Defaults 849
xxvi
Preface
This section explains the objectives, intended audience, and organization of this publication and describes
the conventions that convey instructions and other information.
This section provides the following information:
5888 Revision History, on page xxvii
5889 Document Objectives, on page xxviii
5890 Audience, on page xxviii
5891 Document Organization, on page xxviii
5892 Document Conventions, on page xxix
5893 Related Documentation, on page xxxv
5894 Obtaining Optical Networking Information, on page xxxvi
5895 Obtaining Documentation and Submitting a Service Request, on page xxxvi
Revision History
Date Notes
August 2018 Updated for R10.9 features.
December 2017 Updated for R10.8 features.
April 2017 Updated for R10.6.2 features.
November 2016 Updated for R10.6.1 features.
January 2016 Updated for R10.5.2 features.
July 2015 Updated for R10.5 features.
December 2014 Updated the key features of the OTU2_XP card in the
chapter, "Provisioning Transponder and Muxponder
Cards".
November 2013 This is the first release of this publication.
xxvii
Preface
Document Objectives
Document Objectives
This document provides background and reference material for Cisco ONS 15454 dense wavelength
division (DWDM) systems.
Audience
To use this publication, you should be familiar with Cisco or equivalent optical transmission hardware and
cabling, telecommunications hardware and cabling, electronic circuitry and wiring practices, and
preferably have experience as a telecommunications technician.
Document Organization
This document is organized into the following chapters:
Chapter Description
Setting Up Optical Service Channel Cards Includes descriptions of OSCM and OSC-CSM cards.
Also provides references to related procedures.
Provisioning Optical Amplifier Cards Includes descriptions of the optical amplifier cards.
Provisioning Multiplexer and Demultiplexer Cards Includes descriptions of the 32-MUX-O, 32DMX-O,
and 4MD-xx.x cards. Also provides references to
related procedures.
Setting Up Tunable Dispersion Compensating Units Explains the Tunable Dispersion Compensating Units
(T-DCU) used in DWDM networks. Also provides
references to related procedures.
Provisioning Protection Switching Module Includes descriptions of the Protection Switching

Module (PSM) card used in DWDM networks. Also
provides references to related procedures.
Provisioning Reconfigurable Optical Add/Drop Cards Includes descriptions of the ROADM cards. Also
provides references to related procedures.
Provisioning Transponder and Muxponder Cards Includes descriptions of transponder (TXP),

muxponder (MXP), Xponder (GE_XP, 10GE_XP,
GE_XPE and 10GE_XPE), and ADM-10G cards.
Configuring GE_XP, 10GE_XP, GE_XPE, and Describes how to provision GE_XP, 10GE_XP,
10GE_XPE Cards Using PCLI GE_XPE, and 10GE_XPE cards using Pseudo
Command Line Interface (PCLI).
xxviii
Preface
Document Conventions
Chapter Description
Pseudo Command Line Interface Reference Describes Pseudo-IOS command line interface (PCLI)
for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE
cards.
Card Features Describes the card features.
Card Specifications Contains hardware specifications for the shelf

assemblies and cards.
Administrative and Service States Describes the administrative and service states for
line cards, optical payload ports, out-of-band optical
service channel (OSC) ports, optical channel network
connections (OCHNCs), and transponder/muxponder
cards and ports.
SNMP Explains Simple Network Management Protocol

(SNMP) as implemented by the Cisco ONS 15454.
CTC Enhancements, Operations, and Shortcuts Describes the Cisco Transport Controller (CTC)
views, menus options, tool options, shortcuts, and
table display options.
Network Element Defaults Describes the defaults for the network element settings
for Cisco ONS 15454 shelf assemblies.
Document Conventions
This document uses the following conventions:
Convention Description
^ or Ctrl Both the ^ symbol and Ctrl represent the Control (Ctrl) key on a keyboard.
For example, the key combination ^D or Ctrl-D means that you hold
down the Control key while you press the D key. (Keys are indicated in
capital letters but are not case sensitive.)
bold font Commands and keywords and user-entered text appear in bold font.
Italic font Document titles, new or emphasized terms, and arguments for which you
supply values are in italic font.
Courier font Terminal sessions and information the system displays appear in courier
font.
Bold Courier font Bold Courier font indicates text that the user must enter.
[x] Elements in square brackets are optional.
... An ellipsis (three consecutive nonbolded periods without spaces) after a
syntax element indicates that the element can be repeated.
xxix
Preface
Preface
Convention Description
| A vertical line, called a pipe, indicates a choice within a set of keywords
or arguments.
[x | y] Optional alternative keywords are grouped in brackets and separated by
vertical bars.
{x | y} Required alternative keywords are grouped in braces and separated by
vertical bars.
[x {y | z}] Nested set of square brackets or braces indicate optional or required
choices within optional or required elements. Braces and a vertical bar
within square brackets indicate a required choice within an optional
element.
string A nonquoted set of characters. Do not use quotation marks around the
string or the string will include the quotation marks.
<> Nonprinting characters such as passwords are in angle brackets.
[] Default responses to system prompts are in square brackets.

!, # An exclamation point (!) or a pound sign (#) at the beginning of a line of
code indicates a comment line.
Reader Alert Conventions

This document uses the following conventions for reader alerts:
Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the manual.
Tip Means the following information will help you solve a problem.
Caution Means reader be careful. In this situation, you might do something that could result in equipment damage
or loss of data.
Timesaver Means the described action saves time. You can save time by performing the action described in the paragraph.
Warning Means reader be warned. In this situation, you might perform an action that could result in bodily injury.
xxx
Preface
Preface
IMPORTANT SAFETY INSTRUCTIONS

This warning symbol means danger. You are in a situation that could
cause bodily injury. Before you work on any equipment, be aware of
the hazards involved with electrical circuitry and be familiar with
standard practices for preventing accidents. Use the statement number
provided at the end of each warning to locate its translation in the
translated safety warnings that accompanied this device. Statement 1071
SAVE THESE INSTRUCTIONS
Waarschuwing BELANGRIJKE VEILIGHEIDSINSTRUCTIES

Dit waarschuwingssymbool betekent gevaar. U verkeert in een situatie die
lichamelijk letsel kan veroorzaken. Voordat u aan enige apparatuur gaat
werken, dient u zich bewust te zijn van de bij elektrische schakelingen
betrokken risico's en dient u op de hoogte te zijn van de standaard
praktijken om ongelukken te voorkomen. Gebruik het nummer van de
verklaring onderaan de waarschuwing als u een vertaling van de
waarschuwing die bij het apparaat wordt geleverd, wilt raadplegen.
BEWAAR DEZE INSTRUCTIES
Varoitus TÄRKEITÄ TURVALLISUUSOHJEITA

Tämä varoitusmerkki merkitsee vaaraa. Tilanne voi aiheuttaa
ruumiillisia vammoja. Ennen kuin käsittelet laitteistoa, huomioi
sähköpiirien käsittelemiseen liittyvät riskit ja tutustu onnettomuuksien
yleisiin ehkäisytapoihin. Turvallisuusvaroitusten käännökset löytyvät
laitteen mukana toimitettujen käännettyjen turvallisuusvaroitusten
joukosta varoitusten lopussa näkyvien lausuntonumeroiden avulla.
SÄILYTÄ NÄMÄ OHJEET
Attention IMPORTANTES INFORMATIONS DE SÉCURITÉ

Ce symbole d'avertissement indique un danger. Vous vous trouvez dans
une situation pouvant entraîner des blessures ou des dommages corporels.
Avant de travailler sur un équipement, soyez conscient des dangers liés aux
circuits électriques et familiarisez-vous avec les procédures couramment
utilisées pour éviter les accidents. Pour prendre connaissance des
traductions des avertissements figurant dans les consignes de sécurité
traduites qui accompagnent cet appareil, référez-vous au numéro de
l'instruction situé à la fin de chaque avertissement.
CONSERVEZ CES INFORMATIONS
xxxi
Preface
Preface
Warnung WICHTIGE SICHERHEITSHINWEISE

Dieses Warnsymbol bedeutet Gefahr. Sie befinden sich in einer Situation,
die zu Verletzungen führen kann. Machen Sie sich vor der Arbeit mit
Geräten mit den Gefahren elektrischer Schaltungen und den üblichen
Verfahren zur Vorbeugung vor Unfällen vertraut. Suchen Sie mit der am
Ende jeder Warnung angegebenen Anweisungsnummer nach der
jeweiligen Übersetzung in den übersetzten Sicherheitshinweisen, die
zusammen mit diesem Gerät ausgeliefert wurden.
BEWAHREN SIE DIESE HINWEISE GUT AUF.
Avvertenza IMPORTANTI ISTRUZIONI SULLA SICUREZZA

Questo simbolo di avvertenza indica un pericolo. La situazione
potrebbe causare infortuni alle persone. Prima di intervenire su
qualsiasi apparecchiatura, occorre essere al corrente dei pericoli
relativi ai circuiti elettrici e conoscere le procedure standard per la
prevenzione di incidenti. Utilizzare il numero di istruzione presente alla
fine di ciascuna avvertenza per individuare le traduzioni delle
avvertenze riportate in questo documento.
CONSERVARE QUESTE ISTRUZIONI
Advarsel VIKTIGE SIKKERHETSINSTRUKSJONER

Dette advarselssymbolet betyr fare. Du er i en situasjon som kan føre til
skade på person. Før du begynner å arbeide med noe av utstyret, må
du være oppmerksom på farene forbundet med elektriske kretser, og
kjenne til standardprosedyrer for å forhindre ulykker. Bruk nummeret
i slutten av hver advarsel for å finne oversettelsen i de oversatte
sikkerhetsadvarslene som fulgte med denne enheten.
TA VARE PÅ DISSE INSTRUKSJONENE
Aviso INSTRUÇÕES IMPORTANTES DE SEGURANÇA

Este símbolo de aviso significa perigo. Você está em uma situação que
poderá ser causadora de lesões corporais. Antes de iniciar a utilização
de qualquer equipamento, tenha conhecimento dos perigos envolvidos
no manuseio de circuitos elétricos e familiarize-se com as práticas
habituais de prevenção de acidentes. Utilize o número da instrução
fornecido ao final de cada aviso para localizar sua tradução nos avisos
de segurança traduzidos que acompanham este dispositivo.
GUARDE ESTAS INSTRUÇÕES
¡Advertencia! INSTRUCCIONES IMPORTANTES DE SEGURIDAD

Este símbolo de aviso indica peligro. Existe riesgo para su integridad
física. Antes de manipular cualquier equipo, considere los riesgos de la
corriente eléctrica y familiarícese con los procedimientos estándar de
prevención de accidentes. Al final de cada advertencia encontrará el
número que le ayudará a encontrar el texto traducido en el apartado
de traducciones que acompaña a este dispositivo.
GUARDE ESTAS INSTRUCCIONES
xxxii
Preface
Preface
Varning! VIKTIGA SÄKERHETSANVISNINGAR

Denna varningssignal signalerar fara. Du befinner dig i en situation som
kan leda till personskada. Innan du utför arbete på någon utrustning måste
du vara medveten om farorna med elkretsar och känna till vanliga
förfaranden för att förebygga olyckor. Använd det nummer som finns i
slutet av varje varning för att hitta dess översättning i de översatta
säkerhetsvarningar som medföljer denna anordning.
SPARA DESSA ANVISNINGAR
xxxiii
Preface
Preface
Aviso INSTRUÇÕES IMPORTANTES DE SEGURANÇA

Este símbolo de aviso significa perigo. Você se encontra em uma
situação em que há risco de lesões corporais. Antes de trabalhar com
qualquer equipamento, esteja ciente dos riscos que envolvem os
circuitos elétricos e familiarize-se com as práticas padrão de prevenção
de acidentes. Use o número da declaração fornecido ao final de cada
aviso para localizar sua tradução nos avisos de segurança traduzidos
que acompanham o dispositivo.
GUARDE ESTAS INSTRUÇÕES
Advarsel VIGTIGE SIKKERHEDSANVISNINGER

Dette advarselssymbol betyder fare. Du befinder dig i en situation med
risiko for legemesbeskadigelse. Før du begynder arbejde på udstyr,
skal du være opmærksom på de involverede risici, der er ved elektriske
kredsløb, og du skal sætte dig ind i standardprocedurer til undgåelse af
ulykker. Brug erklæringsnummeret efter hver advarsel for at finde
oversættelsen i de oversatte advarsler, der fulgte med denne enhed.
GEM DISSE ANVISNINGER
xxxiv
Preface
Related Documentation
Related Documentation
Use this guide in conjunction with the following referenced Release 10.x.x publications:
23 Release Notes for Cisco ONS 15454 DWDM
24 Cisco ONS 15454 DWDM Control Card and Node Configuration Guide
25 Cisco ONS 15454 DWDM Network Configuration Guide
26 Cisco ONS 15454 DWDM Licensing Configuration Guide
27 Cisco ONS 15454 Hardware Installation Guide
28 Cisco ONS 15454 DWDM Troubleshooting Guide
29 Cisco ONS SDH TL1 Command Guide
30 Cisco ONS SONET TL1 Command Guide
31 Cisco Transport Planner - DWDM Operations Guide
32 Regulatory Compliance and Safety Information for Cisco ONS Platforms
33 Electrostatic Discharge and Grounding Guide for Cisco CPT and Cisco ONS Platforms
34 Installing the GBIC, SFP, SFP+, XFP, CXP, and CFP Optical Modules in Cisco ONS
Platforms
35 Installing the Cisco ONS 15454 DWDM Passive Optical Modules
For an update on End-of-Life and End-of-Sale notices, refer to
xxxv
Preface
Obtaining Optical Networking Information
http://www.cisco.com/en/US/products/hw/optical/ps2006/prod_eol_notices_list.html
Obtaining Optical Networking Information

This section contains information that is specific to optical networking products. For information that
pertains to all of Cisco, refer to the Obtaining Documentation and Submitting a Service Request section.
Where to Find Safety and Warning Information

For safety and warning information, refer to the Regulatory Compliance and Safety Information for Cisco
ONS Products document that accompanied the product. This publication describes the international
agency compliance and safety information for the Cisco ONS Products. It also includes translations of the
safety warnings that appear in the ONS system documentation.
Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a
service request, and gathering additional information, see What's New in Cisco Product Documentation.
To receive new and revised Cisco technical content directly to your desktop, you can subscribe to the .
RSS feeds are a free service.
xxxvi
Cisco ONS Documentation Roadmap for
Release 10.x.x
To quickly access publications of Cisco ONS Release 10.x.x, see the Documentation Roadmap.
xxxvii
Cisco ONS Documentation Roadmap for Release 10.x.x
Cisco ONS Documentation Roadmap for Release 10.x.x
xxxviii
New and Changed Information
This table summarizes the new and changed information for Release 10.9, and tells you where the
features are documented.
Table 1: New and Changed Features - R10.9
Feature Description Where Documented
Encryption on The 400G-XP-LC card provides encryption Cisco ONS 15454 DWDM Line
400G-XP-LC card capability on the OTU4 ports. This card provides Card Configuration Guide
confidentiality of the data, which is sent over a fiber
optic communication channel, using Next
Generation Cryptography. The MXP operating
mode supports the encryption feature.
400G-XP-LC • The cross-connect circuit bandwidth supported Cisco ONS 15454 DWDM Line
Enhancements are ODU2, ODU2e, and ODU4. Card Configuration Guide
• The OPM_10x10G slice mode is supported
for OTN cross-connect circuits.
• The new payloads supported for the OTNXC
operating mode are OC192/STM64, OTU2,
OTU2e, and 100G.
• The new payloads supported for the MXP
operating mode are OC192/STM64 and
OTU2e.
• The ODU4 internal ports on the 400G-XP-LC
card support configuration of Pseudo Random
Binary Sequence (PRBS) with all operating
modes.
• The Trunk GCC0 configuration is supported
on the 400G-XP-LC card.
• The 2x150G 8QAM modulation format is
configurable on the 400G-XP MXP trunk
ports.
xxxix

Remote TXP • The transponder node containing a set of Cisco NCS 2000 Series Network
transponders is physically connected to the Configuration Guide
ROADM-A node using the external PPC.
5888 The PPC represent the physical
connection between transponder and
ROADM node add/drop port. The Staic LMP
or UNI need to be created on remote
transponder and ROADM accordingly.
5889 This feature supports the following
transponder cards:
100G-LC-C
100G-CK-C
100GS-CK-C
200G-CK-C
400G-XP-LC with both
MXP/OTNXC operating modes
MCG Restoration In case of a fiber cut in a path, the media

channels Cisco ONS 15454 DWDM Network
in a media channel group (MCHG) are restored Configuration Guide
using another available path. This helps reduce the
network outage time. After restoration, there is also
an option to shrink the media channel group to the
minimum size to maintain all the media channnels
in the same group.

OTN The 400G-XP-LC card supports a new OTN Cisco ONS 15454 DWDM Line
Cross-connect cross-connect (OTNXC) operating mode. This mode Card Configuration Guide
support on allows ODU2e switching between client to trunk 23 OTN Cross-connect
400G-XP-LC ports or trunk to trunk ports within a single
Cards 400G-XP-LC card for 100G and 200G trunk rates. Capability on 400G-XP-LC
Only the 10GE client payloads are supported. Each Cards
10GE is mapped to an ODU2e channel. Each 10G
client port of the 400G-XP-LC card consists of only Cisco ONS 15454 DWDM
one ODU2e and each OTU4C2 ( 200G) trunk port Network Configuration Guide
of the 400G-XP-LC card consists of 20 ODU2es. 5888 NTP-G365
Client-to-trunk cross-connections can be protected Creating,Managing, and
or unprotected. Single card cross-connects or Deleting ODU Circuits for
end-to-end cross-connects can be created in an OTN the 400G-XP-LC Card
ring.
xl

OTDR • Scan performances are improved using specific Cisco ONS 15454 DWDM
Enhancements scan parameters targeted on the characteristics Network Configuration Guide
of the fiber plant such as span length, reflection
23 NTP-G355
contributions, and major events.
Provisioning OTDR for
• OTDR identifies the Fiber End as a fiber TNCS-O Cards
termination event along with reflection or loss
event. Manage the Node
• Automode scan is enhanced with the composite 5888 NTP-G357 Perform
trace. OTDR Scan and OTDR
Event Scan
• Fast Span Trace is displayed to the user for
quick reference before the composite trace.
• OTDR module can perform Optical Return
Loss (ORL) measurement.
• Any ongoing scan operation can be cancelled.
• A progress bar is provided to the user for each
scan in the sector that displays the percentage
of execution of the entire scan operation.
• It is possible to activate automatic scan on
ORL value exceeding the provisioned
threshold.
• The insertion loss due to amplifier cards and
patchcords is displayed in the OTDR
provisioning panel.
• New OTDR alarms and conditions are
introduced to provide more information about
the OTDR functionality.
• Prevention of WSON circuit creation is
extended for new OTDR alarms and
conditions.
• CTC panes for OTDR provisioning are
redesigned for better user experience.
Support for 400G- XP LC card can be configured as a

Regeneration regenerator. The regeneration functionality is
Mode on available only on the trunk ports. The two trunk Cisco ONS 15454 DWDM
400G-XP-LC ports must have the same rate to achieve
Line Card Configuration
regeneration. Regen mode is not supported on the
Guide
client ports.
23 Regeneration
Mode for 400G-XP
LC
xli
PSM support on 400G-XP LC card supports the Protection Switching Cisco ONS 15454 DWDM Line
400G-XP-LC Module (PSM). The switch time for all 10G Card Configuration Guide
payloads is less than 50 ms. The switch time for
• 400G-XP-LC Card
100G trunk rate is higher than the 200G.
OPT-EDFA-35 The OPT-EDFA-35 card is a C-band, DWDM Cisco ONS 15454 DWDM Line
EDFA amplifiers/preamplifiers with +23dBm output Card Configuration Guide
power. The card includes two identical amplification
sections to serve two fiber directions • OPT-EDFA-35
simultaneously. The OPT-EDFA-35 card is
bidirectional and has an operative optical gain range Manage the Node
up to 24 dB and 35 dB. • NTP-G76 Verify Optical Span
Loss Using CTC
• NTP-G77 Manage Automatic
Power Control
Monitor Performance
5888 NTP-G74 Monitor
DWDM Card Performance
5889 DLP-G140 View Power
Statistics for Optical
Amplifier, 40-SMR1-C,
and 40-SMR2-C Cards
Card Support in The GE_XP, 10GE_XP, GE_XPE,10GE_XPE, Cisco ONS 15454 DWDM Series
Cisco NCS 2015 MXP_MR_10DME_C, and OPT-RAMP-CE cards Line Card Configuration Guide,
are supported on the Cisco NCS 2015 chassis. Release 10.x.x
23 GE_XP, 10GE_XP,
GE_XPE, and 10GE_XPE
Cards
24 MXP_MR_10DMEX_C
Card
25 OPT-RAMP-C and
Software The OpenSSH has been upgraded to CiscoSSH 1.4. OPT-RAMP-CE Cards
Enhancements
Cisco ONS 15454 DWDM
Network Configuration Guide,
Release 10.x.x
5888 OpenSSH Version
xlii
Y-cable support for 200G-CK-LC Y-cable protection is supported Cisco ONS 15454 DWDM Line
and 10x10G-LC cards when the 200G-CK-LC card is Card Configuration Guide
configured in TXP-100G operating
• Key Features of 100G-LC-C,
mode and the 100G client CPAK
100G-ME-C, 100G-CK-C,
ports are provisioned with 100GE
100ME-CKC, 10x10G-LC,
payload. This configuration uses
100GS-CK-LC,
the CPAK-100G-LR4 pluggable. 200G-CK-LC, CFP-LC, and
Y-cable protection is supported MR-MXP Cards
when the 10x10G-LC card is
configured in MXP-10x10G
operating mode with 200G-CK-LC
card and the 10x10G-LC card is
provisioned with 10GE,
OC-192/STM-64 payloads. This
configuration uses the
ONS-SC+-10G-LR and
ONS-SC+-10G-SR pluggables.
SSON SSON allows the user to provide Cisco ONS 15454 DWDM Network
more than 96 channels in a span. Configuration Guide
The SSON package is enabled
using a specific package.
The supported SSON circuits are:
• Media Channel
• Media Channel Group
• Carrier
MR-MXP Configuration for 100G 2X10GE+2X40GE payload is Cisco ONS 15454 DWDM Line
and 200G OTU4 supported in MXP-100G operating Card Configuration Guide
mode which comprises of
200G-CK-LC and MR-MXP cards. • MR-MXP Card
This payload is supported only
when the sub OpMode in MR-MXP
card is OPM_2x40G_2x10G.
OTU4 payload is supported in
MXP-CK-100G operating mode
which comprises of 200G-CK-LC
and MR-MXP cards. This payload
is supported only when the sub
OpMode in MR-MXP card is
OPM_100G.
xliii

Third Party Certificates for MR- The MR-MXP card supports the Cisco ONS 15454 DWDM Line
XP Card generation of a Certificate Signing Card Configuration Guide
Request (CSR) and installation of
Locally Significant Certificates
(LSCs) that can be used to
authenticate the peer card
connection.
Support of 400G-XP-LC cards One 400G-XP-LC card can be Cisco ONS 15454 DWDM Line
on Cisco ONS 15454 M2 installed in the Cisco ONS 15454 Card Configuration Guide
M2 DC chassis that is powered by 15454-M2-DC or 15454-
M2-DC-E.
Support for OTU4 traffic on This payload is supported only on Cisco ONS 15454 DWDM Line
400G-XP-LC Cards the ONS-QSFP28-LR4 pluggable. Card Configuration Guide
The payload can be provisioned for
the OPM_100G slice mode for any
trunk configuration.
Interoperability with 400G-XP-LC This line card is interoperable with Cisco ONS 15454 DWDM Line
card the NCS55-6X200-DWDM-S card Card Configuration Guide
supported on NCS 5500 and the
NCS4K-4H-OPW-QC2 Card
supported on NCS 4000.
This table summarizes the new and changed information for Release 10.6.2, and tells you where the
Table 4: New and Changed Features - R10.6.2

400G-XP-LC card enhancements • Support for 16G-Fiber Cisco ONS 15454 DWDM Line
Channel and OTU2 payloads Card Configuration Guide
23 Support for trunk PM
parameters-Second Order
PMD (SOPMD) and
Polarization Depended Loss
(PDL).
xliv
Node recovery enhancements Two enhancements have been Cisco ONS 15454 Network
introduced to recover the node Configuration Guide
without traffic loss.
5888 When provisioning
database loss occurs, the
BAD-DB-DETECTED and
NODE-FACTORY-MODE
critical alarms are raised at
the node level.
5889 When system
database loss occurs on the
active or standby control
card, an INVALID SYSDB
alarm is raised on the
control card.
Steps to clear the alarms have been

documented.
MSM supported configurationsThe following configurations are Cisco ONS 15454 DWDM Line
supported: Card Configuration Guide
• 40 400G-XP-LC cards
provisioned with 10GE
payloads
• 20 400G-XP-LC, 36
200G-CK-LC, and 72
MR-MXP cards provisioned
with 10GE payloads
payloads
payloads along with 36
200G-CK-LC and 72
MR-MXP cards provisioned
with 10GE payloads.
xlv
Duplicate Node Controller (Only on ONS 15454 M6 and NCS Cisco ONS 15454 DWDM Control
2015) When a Card and Node Configuration
TNC/TNC-E/TSC/TSC-E/TNCS/TNCS-O Guide
node controller connects to the
same switch where an NCS 2006 • Duplicate Node Controller
or NCS 2015 node controller exists,
both the node controllers raise the
critical Duplicate Node Controller
(DUP-NC) alarm. The subtending
shelves of both the node controllers
raise the Shelf Communication
Failure (SHELF-COMM-FAIL)
alarm. Both the node controllers
and their subtending shelves shut
down their ports on ASIC towards
the MSM ports in ECU. However,
the traffic is not affected.
MR-MXP Enhancements OC192/STM64 and OTU2 client Cisco ONS 15454 DWDM Line
payloads are supported on the Card Configuration Guide
MR-MXP card in MXP-200G,
MXP-10x10G-100G, • MR-MXP Card
MXP-CK-100G, and MXP-100G
operating modes. OC192/STM64
and OTU2 client payloads are
supported only when the sub
OpMode is OPM_10x10G on the
MR-MXP card.
TCC2 and TCC2P Card Support The nodes with the TCC2/TCC2P Cisco ONS 15454 DWDM Control
cards in releases prior to R10.6.2 Card and Node Configuration
cannot be upgraded to R10.6.2 as Guide
the size of the software package
• TCC2 and TCC2P Cards
exceeds the size of the
TCC2/TCC2P flash drive. Hence,
R10.6.2 does not have the
TCC2/TCC2P software package. If
the user wants to continue with the
ONS 15454 chassis, it is
recommended to use the TCC3
control card. If the user wants to
upgrade to a ONS 15454 M6 or
NCS 2015 chassis, it is
recommended to use the TNCS or
TNCS-O control cards.
xlvi
Multivendor Interoperability The 200G-CK LC can be Cisco ONS 15454 DWDM Line
configured to interoperate with Card Configuration Guide
other vendor devices. The Interop
Mode option is available on the full • Multivendor Interoperability
PID, NCS2K-200G-CK, and on the
licenced PID,
NCS2K-200G-CK-LIC, when
licence L-NCS2K-DQPSK-LH= is
active.
Operating Mode to support 16G To support the 16G FC payload, a Cisco ONS 15454 DWDM Line
FC payload new operating mode, Card Configuration Guide
OPM_6x16G_FC is introduced.
This operating mode can be • Operating Mode
provisioned on any MXP card
configuration slice, with M_100G
and M_200G trunk ports.
ROADM Configurations A new colorless, directional A/D Cisco ONS 15454 DWDM Network
stage is available using the passive Configuration Guide
A/D module, MF-6AD-CFS. This
A/D stage provides modular A/D • Node Reference
capability up to 96 channels that
can be used to insert or extract
colorless channels to or from a
specific ROADM direction.
Third Party Certificates for The WSE card supports the Cisco ONS 15454 DWDM
WSE Card generation of a Certificate Line Card Configuration
Signing Request (CSR) and Guide
installation of Locally Significant
23 WSE Card
Certificates (LSCs) that can be
used to authenticate the peer card 24 NTP-G340
connection. Provisioning Encryption on
the WSE and MR-MXP
Cards
OTDR Enhancements • The OTDR scan starts Cisco NCS 2000 Series
automatically after the LOS Network Configuration Guide
alarm is raised and cleared. 5888 DLP-G793 Configuring
• The default value for the Common OTDR Parameters
automatic OTDR scan to for OTDR Scan on TNCS-
begin is 3 minutes. O Cards
• Location [km] in the
Reflection table or the Manage the Node
Insertion Loss table is 23 DLP-G787 Perform
enhanced with the Accuracy OTDR Event Scan on TNCS-
(km) details.
O Cards
xlvii
400G-XP-LC card The 400G-XP-LC card is a tunable Cisco ONS 15454 DWDM Line
DWDM trunk card that simplifies Card Configuration Guide
the integration and transport of 10 400G-XP-LC Card
Gigabit and 100 Gigabit Ethernet
interfaces and services into
enterprises and service provider
optical networks. The card is a
double- slot unit that provides 400
Gbps of client and 400 Gbps of
trunk capacity. The card supports
six QSFP+ based client ports that
can be equipped with 4x 10 Gbps
optics and four QSFP28 or QSFP+
based client ports that can be
equipped with 100 Gbps QSFP28
and 4x 10 Gbps QSFP+ optics. The
card is capable of aggregating client
traffic to either of the two 200 Gbps
coherent CFP2 trunk ports.
The 400G-XP-LC card is supported
only on Cisco ONS 15454 M6 and
Cisco NCS 2015 platforms.
Passive Optical Modules The following types of modules are Installing the Cisco ONS 15454 M2
supported: and ONS 15454 M6 Passive
• MPO-24 to 20-LC Fan-out Optical Modules
Module
(NCS2K-MF-MPO-20LC=)
• 6 Port Add/Drop Module
(NCS2K-MF-6AD-CFS=)
ONS 15454 M6 ECU60-S ONS 15454 M6 ECU60-S is a new Cisco ONS 15454 Hardware
type of ECU-S introduced for the Installation Guide
ONS 15454 M6 when the shelf is
powered at –60 VDC nominal
input voltage. This module has
eight USB 2.0 ports and two USB
3.0 ports.
xlviii
New MPO Cables Installing the Cisco ONS 15454

DWDM Passive Optical Modules
xlix

The following table lists the MPO
cables that can be used with the
passive modules from Release
10.6.1:
5888 ONS-MPO-
16LC-2—Fan-out cable with
one MPO-24 connector on
one side and 16 LC
connectors on the other side.
The cable is two meters long
and can be used in ROADM
configurations with the
NCS2K-MF-6AD-CFS
module. This cable can also
be used as a fan-out cable to
connect the LC interface
directly to the SMR20 FS
MPO ports.
5889 ONS-12MPO-
MPO-x—Multi-fiber patch
cord with MPO-12 connectors.
The 12 fibers have straight
connections. There are four
variants: two, four, six, and
eight meters. The cables can
interconnect the QSFP+ client
ports of NCS2K-400G-2C2
and NCS4K-4H-OPW-QC2
with the NCS2K-MF-8X10G-
FO passive module.
5890 ONS-12MPO-
XMPO-x—Multi-fiber patch
cord with MPO-12
connectors. The 12 fibers
have crossed fiber
interconnections. The cable
is used to interconnect the
NCS2K-MF-DEG-5-CV and
the NCS2K-MF-UPG-4-CV
passive modules with the
NCS2K-MF-MPO-8LC
adapter.
5891 ONS-16MPO-
MPO-x—Multi-fiber patch
cord with MPO-24 connectors
that has only 16 fibers
connected. Fibers 1, 2, 11, 12,
13, 14, 23, and 24 are not
connected. The cable is used
for interconnections
l

inside the ROADM with
MPO-24 standard. The patch
cord can be used for
interconnections between
SMR20 FS and
NCS2K-MF-M16LC-CV, or
NCS2K-MF-2MPO-ADP or
NCS2K-PPMESH8-5AD. The
patch cord can also be used
for interconnections between
NCS2K-16-AD-CCOFS and
NCS2K-MF-M16LC-CV.
Synchronous Ethernet Synchronous Ethernet (SyncE) Synchronizing Node Timing chapter

provides synchronized timing to of the
multiple remote network elements Cisco ONS 15454 DWDM Control
(NEs) without using an external
circuit for timing. SyncE provides Card and Node Configuration
the required synchronization at the Guide
physical level and uses the Ethernet
Synchronization Message Channel
(ESMC) to enable traceability of
the best clock source. SyncE clocks
are compatible with the clocks used
in the SONET or SDH
synchronization network.
SyncE is supported on TNCS and
TNCS-O controller cards. You
must enable ESMC on an OSC port
to configure it as a clock source.
li
OTDR Enhancements • Two types of OTDR scans are Cisco ONS 15454 Network
available for TNCS-O cards: Configuration Guide
hybrid scan and fast scan. • NTP-G355 Provisioning
When you start a fast scan on OTDR for TNCS-O Cards
a TX or an RX port, an
OTDR_FAST_SCAN_IN Manage the Node
PROGRESS_TX or an
• NTP-G357 Perform OTDR
OTDR_FAST_SCAN_IN
Scan and OTDR Event Scan
PROGRESS_RX alarm is
raised. Fast scan shuts down
the OSC channel.
When you start a hybrid scan
on a TX or an RX port, an
OTDR_HYBRID_SCAN_IN_PROGRESS_TX
or an
OTDR_HYBRID_SCAN_IN_PROGRESS_RX
alarm is raised. Hybrid scan
does not shut down the OSC
channel and takes more time
to complete.
23 New OTDR alarms are
introduced to provide more
information about the OTDR
events. Select an event to
view its details as a graph or
in a tabular format.
24 CTC logs the data of a
maximum of 32 historical
OTDR scans. The history is
maintained for OTDR scans
in the same zone and
direction. The values of the
back reflection and
insertion loss are listed for
each scan along with the
date and timestamp.
lii
Connection Verification • View and troubleshoot patch Cisco ONS 15454 DWDM Line
Enhancements cords that have an excess Card Configuration Guide
insertion loss higher than the
• Supported Cards
threshold value.
• Running the Connection
• View the originating and Verification
destination slots for the
connection verification along Cisco ONS 15454 DWDM Network
with the patch cords in the Configuration Guide
cable view and front panel • Node Reference
view of the card. • NTP-G356 Verify the
• If there is at least one patch Connections in Optical Cables
cord highlighted in yellow and
no patch cords highlighted in
orange on a node, an
IPC-VERIFICATION-DEGRADE
alarm is raised on the node.
• If there is at least one patch
cord highlighted in orange on
the node, an
IPC-VERIFICATION-FAIL
alarm is raised on the node.
• When the insertion loss is
greater than the insertion loss
degrade threshold and less
than the insertion loss fail
threshold, the value of the
insertion loss verification of
the patch cord is degrade. The
corresponding row of the
patch cord in the Connection
Verification pane is
highlighted in yellow.
• When the insertion loss is
greater than the insertion loss
fail threshold, the value of the
insertion loss verification of
the patch cord is fail. The
corresponding row of the
patch cord in the Connection
Verification pane is
highlighted in orange.
• Connectivity verification is
displayed only for an MPO
cable and not for each of the
patch cords in it.
liii

MR-MXP Enhancements The MR-MXP card supports the Cisco ONS 15454 DWDM Line
following enhancements: Card Configuration Guide
• Payload authentication can be 5888 MR-MXP Card
enabled on the MR-MXP card
5889 NTP-G340
to validate the integrity of the
Provisioning Encryption on
received payloads.
the WSE and MR-MXP
• Payload authentication error Cards
thresholds can be set on the
MR-MXP card. Cisco ONS 15454 DWDM
Licensing Configuration Guide
• MR-MXP-K9 and
MR-MXP-K9= PIDs of
MR-MXP card are introduced
and are referred as Encryption
as an appliance PIDs. The card
authentication and payload
encryption are enabled by
default and cannot be disabled
for these PIDs.
LMP Wizard Enhancements Link Management Protocol (LMP)

link can be created between the Cisco ONS 15454 DWDM
DWDM node and non DWDM Network Configuration Guide
node using a wizard in CTC. 23 DLP-G800 Create an
LMP Link Using CTC
24 DLP-G801 Configure
Local UNI Using CTC
TCC2P support The TCC2P card can be used as a
control card in a subtended shelf TCC2 and TCC2P Cards
where the node controller is TCC3
card on ONS 15454 chassis or
TNC/TNCE/TNCS/TNCS-O cards
on ONS 15454 M6 or NCS 20015
chassis. The TCC2P card can also
be used as a node controller in a
stand-alone configuration.
liv

Software Enhancements Several software enhancements are 5888 NTP-G353 Creating
introduced in Release 10.6.1. GMPLS Circuits Using the
Fast Circuit Mode
• Reroute enhancements
5889 DLP-G732 Editing a
• Retuning wavelengths of GMPLS Circuit
existing circuits
5890 NTP-G359
• Changing the channel Changing the Channel
frequency measurement units Frequency Measurement
to THz or GHz Unit
• Fast restoration of circuits 5891 NTP-G135 Editing
Network Element Defaults
• CTC displays the historical
ethernet statistics that are 5892 NTP-G345 Viewing
retrieved from the ethernet Ethernet Statistical PM
controllers on the router. Counts
• Support of 40-SMR1-C cards 5893 Split ROADM Nodes
in a split ROADM
configuration 5894 DLP-G381
Provisioning Layer 2
• When a fault occurs on the
Protection Settings
working path of a FAPs ring,
all the SVLANs, whose 5895 200G-CK-LC
protection is set, are moved to
the protection path of the
FAPS ring. Up to 1024
SVLANs can be protected or
a range of SVLANs can be
protected.
• 200G-CK-LC card supports
additional configurations in
the MXP_200G and
MXP_CK_100G operating
modes.
lv

Security Enhancements • RADIUS authentication is 23 Manage the Node
supported for security super
24 Connect the PC and
user, security user, and root
user. Log into the GUI
• Security policy can be

changed for the security level
that you want to provision:
Retrieve, Maintenance,
Provisioning, Superuser,
Security user, Security super
user, or ROOT15 user.
• RSA-based authentication is
supported for dynamic
challenge response security
feature.
• Node reauthentication is
supported in CTC for Cisco
NCS 2000 and Cisco CRS
nodes.
5888 Text string in the
Shared Secret field is masked
and the shared secret serves as
a password between a
RADIUS client and RADIUS
server.
System Mode Change The System Mode can be changed • Manage the Node
by:
• Cisco ONS 15454 Hardware
• Using CTC Installation Guide
• Using LCD
LMP Protocol Extension for Trunk With LMP extension for trunk Cisco ONS 15454 DWDM Network
Ports ports, traffic is directed to the NCS Configuration Guide
4000 series router from the trunk
• DLP-G790 Create a Static
ports of the NCS 2000 series router.
LMP Connection
ROADM Configurations New layer-2 A/D extensions for Cisco ONS 15454 DWDM Network
ROADM Configuration Guide
• Node Reference
lvi

GMPLS enhancements The enhancements include the Cisco ONS 15454 DWDM
following: Network Configuration Guide
• Explicit Route Object (ERO) 23 Configuring an Explicit
- defines the route(s) to be Route Object
used through a list of specified
24 Recording a Route Object
nodes for a LSP.
• Record Route Object (RRO) 25 Configuring SRLG
Diversity
- enables the user to obtain a
list of used resources.
• SRLG diversity - enables the
user to create a new circuit,
with resources which are not
used in the reference circuit.
Repair Circuits When some nodes change their

network IP, WSON is not able to Cisco ONS 15454 DWDM
restore the correct state of the Network Configuration Guide
involved circuits. The Repair 5888 Repairing a Circuit
Circuits feature enables the user to
fix circuits that WSON is not able
to automatically repair.
CTC Cell Highlight Highlights the recent changes made CTC Enhancements, Operations
by the user. and Shortcuts
lvii
Cisco NCS 2015 AC Shelf The Cisco NCS 2015 AC shelf Cisco NCS 2000 Series Hardware
Assembly assembly has 18 vertical slots Installation Guide
numbered 1 to 18. While slot 2 to
slot 16 is for line cards that provide
10 to 100 Gbps interconnections,
slot 1 and slot 17 is for the TNCS
or TNCS-O cards (timing and
control cards). Slot 18 is for the
external connection unit (ECU).
The NCS 2015 AC shelf is powered
by AC power modules with 1+0,
1+1, 2+0, and 2+2 redundancy. The
NCS 2015 AC shelf contains
backup flash memory that supports
the database (DB) and image
backup in the single mode
operation. The LCD unit is
integrated with the fan tray
assembly. The fiber or cable guide
used in the NCS 2015 AC shelf
provides improved fiber
management. The air in the NCS
2015 AC shelf is drawn in through
a two-inch air inlet at the bottom of
the shelf, and expelled at the
top-rear. A single NCS 2015 AC
shelf supports both ANSI and ETSI
standards.
ONS 15454 M6 ECU-S The ONS 15454 M6 ECU-S is a Cisco ONS 15454 Hardware
new type of ECU introduced for the Installation Guide
ONS 15454 M6. It has 2 USB 3.0
connections and 8 USB 2.0
connections. The Fiber Shuffle or
the MPO-fan-out unit can be
connected to the ONS 15454 M6
ECU-S using the USB 3.0 port.
Node Alias A node alias (up to 128 characters) Cisco ONS 15454 DWDM Control
can be configured for a node. It Card and Node Configuration
shows as a tool tip in the Network Guide
Map and Explorer Tree of the CTC. • NTP-G24 Setting Up Name,
Date, Time, and Contact
Information
lviii
PSM Cards PSM cards support automatic Cisco ONS 15454 DWDM Line
bi-directional traffic reversion. Card Configuration Guide
SNMP support is added for PSM • Provisioning Protection
Cards to retrieve the port status. Switching Module
PSM cards support automatic
Optical Multiplex Section (OMS)
protection when provisioned with
Transponder (TXP) and Muxponder
(MXP) cards.
lix
SMR20 FS CV Cards The SMR20 FS CV cards are

tunable over 96 channels in the
C-band, at 50-GHz spacing on the
ITU-T grid. The cards provide flex
spectrum capability, which allows
the flexibility to allocate the
channel bandwidth and to increase
the network scalability. The cards
support up to 20 directions for each
ROADM node and can be installed
in any service slots in the chassis.
The SMR20 FS CV cards provide
the connection verification
capability using a connectivity
check signal. The correctness and
the quality of the interconnections
(determined by measuring the
insertion loss of the external
passive path) can be validated with
the connection verification feature
in the cards.
lx

Cisco ONS 15454 DWDM Line
Card Configuration Guide
• 17 SMR9 FS, 24 SMR9 FS,
34 SMR9 FS and SMR20 FS
Cards
• Connection Verification
• Supported Cards
• Running the Connection
Verification
Cisco ONS 15454 DWDM Network
Configuration Guide
• Node Reference
• NTP-G356 Verify the
Connections in Optical Cables
Configuration Guide
• DLP-G325 Changing Optical
Amplifier Line Settings
Amplifier Threshold Settings
• DLP-G406 Changing Card
Optical Channel Parameters
for 40-WXC-C, 80-WXC-C,
16-WXC-FS, 17 SMR9 FS,
24 SMR9 FS, 34 SMR9 FS,
or SMR20 FS Cards
• DLP-G407 Changing the
Optical Channel Thresholds
or SMR20 FS Cards
Line Parameters for
40-WXC-C, 80-WXC-C,
or SMR20 FS Cards
Optical Line Thresholds for
40-WXC-C, 80-WXC-C,
or SMR20 FS Cards
• DLP-G772 Viewing
Wavelength Power for
lxi

or SMR20 FS Card
• DLP-G773 Creating a Flex
Spectrum or ITU Circuit for
or SMR20 FS Card
• DLP-G140 View Power
40-SMR2-C,17 SMR9 FS, 24
SMR9 FS, 34 SMR9 FS, and
SMR20 FS Cards
• DLP-G141 View Optical
Power Statistics for
32MUX-O, 32WSS,
32WSS-L,
32DMX-O,32DMX,
32DMX-L, 40-WSS-C,
40-WSS-CE, 40-WXC-C,
80-WXC-C, 16-WXC-FS, 17
SMR9 FS, 24 SMR9 FS, 34
SMR9 FS, SMR20 FS,
SMR20 FS CV, 40-MUX-C,
40-DMX-C, and 40-DMX-CE
Cards
lxii

TNCS-O Cards The TNCS-O cards are provisioned Cisco ONS 15454 DWDM
as active and standby cards in the Control Card and Node
Cisco ONS 15454 M6 or NCS 2015 Configuration Guide
shelves. On the NCS 2015 shelf,
23 TNCS-O Cards
the TNCS-O cards can be installed
in slots 1 and 17. On the ONS 24 NTP-G313 Installing and
15454 M6 shelf, the cards can be Configuring the TNC, TNCE,
installed in slot 1 and 8. If the TSC, TSCE, or TNCS Card
active TNCS-O card fails, system
traffic switches to the redundant Cisco NCS 2000 Series
TNCS-O card. The TNCS-O cards Network Configuration Guide
support only Fast Ethernet (FE) and
5888 NTP-G355
wavelength of 1518 nm in OSC
transmissions. Provisioning OTDR for
TNCS-O Cards
A TNCS-O card has an optical
module that provides Optical Time Manage the Node
Domain Reflectometer (OTDR)
measurement capability and 23 NTP-G357 Perform
standard Optical Service Channel OTDR Scan and OTDR
(OSC) transmission on two ports. Event Scan
OTDR capability lets you monitor
variations in scan values and
thresholds and measure the distance
and magnitude of defects like
insertion loss and reflection loss on
a fiber span across different
measurement ranges.
MR-MXP Enhancements The MR-MXP card supports the

following enhancements:
• Supports 100G operating Cisco ONS 15454 DWDM
modes - MXP-100G, Line Card Configuration
TXP-100G, and 100G_B2B. Guide
• Provides encryption capability 5888 MR-MXP Card
at the optical layer. 5889 Operating
• Supports feature-based Modes for MR-
licensing to support high MXP Card
speed and low speed
5890 NTP-G340
encryption.
Provisioning Encryption on
the WSE and MR-MXP
Cards

lxiii

Squelch Hold Off Timer The Squelch hold off timer can be Cisco ONS 15454 DWDM Line
configured for TXP_MR_10E, Card Configuration Guide
40E-MXP-C, OTU2_XP, 23 DLP-G714 Changing the
100G-LC-C, 100G-CK-C,
Card Line Settings
100ME-CK-C, CFP-LC,
10x10G-LC, and MR-MXP cards 24 DLP-G217 Changing the
for 10GE and 100GE client 10G Multirate Transponder
payloads in TXP and MXP Line Settings
operating modes.
25 DLP-G218 Changing the
10G or 40G Multirate
Transponder Line Section
Trace Settings
26 DLP-G666 Changing the
40G Muxponder Line Settings
Split ROADM Nodes The Split ROADM feature is
enhanced to support chassis Cisco ONS 15454 DWDM
replacement in post-split nodes. Network Configuration Guide
5888 Node Reference
MSM support The following MSM configurations
are supported: Cisco NCS 2000 Series
• Cisco NCS 2015 as the node Hardware Installation Guide
controller with up to 10 NCS
2015 as subtended shelves.
• Cisco NCS 2015 as the node
controller with a mix of up to
15 NCS 2015, NCS 2006, and
ONS 15454 as subtended
shelves.
• Cisco NCS 2006 as the node
controller with a mix of up to
15 NCS 2015, NCS 2006, and
ONS 15454 shelves as
subtended shelves.
• Cisco ONS 15454 as the node
controller with a mix NCS
2015, NCS 2006, and ONS
15454 shelves as subtended
shelves.
Note The ONS 15454 shelves

must have TCC3 cards
installed for the
configurations.
lxiv

Unnumbered Interface (UNI) The UNI is the service control Cisco ONS 15454 DWDM
Support interface between the transport Network Configuration Guide,
network and client equipment. It is Release 10.x.x.
used to utilize the supported 23 Unnumbered Interface
network services. It eliminates the
(UNI) Support
need of managing IP addresses to
24 DLP-G789 Enable
identify the interfaces.
RSVP on an Interface
25 DLP-G790 Create a
Static LMP Connection
26 DLP-G791 Creating
the WSON UNI-C
Circuit
Zoom In/Out of Graphs The ROADM flex spectrum cards Manage the Node
support zoom in or zoom out
• DLP-G785 Zoom In/Out with
functionality on the graphs
Graphs
displayed in CTC.
Power Redundancy The power redundancy mode of an Cisco ONS 15454 DWDM
NCS 2015 chassis can be Network Configuration Guide,
configured using CTC or TL1 Release 10.x.x
commands. The AC power modules
5888 Power Redundancy
support 1+0, 1+1, 2+0, and 2+2
redundancy. The DC power 5889 Power Redundancy
modules support 1+0, 1+1, 2+0, Mode While Upgrading
2+1, 2+2, 3+0, and 3+1 from Release 10.5
redundancy.
5890 NTP-G358
Configuring a Power
Redundancy Mode
lxv

Cisco NCS 2015 Shelf Assembly The Cisco NCS 2015 shelf Cisco NCS 2000 Series Hardware
assembly has 18 vertical slots Installation Guide
numbered 1 to 18. While slot 2 to
slot 16 is for line cards that provide
10 to 100 Gbps interconnections,
slot 1 and slot 17 is for the TNCS
cards (timing and control cards).
Slot 18 is for the external
connection unit (ECU). The NCS
2015 system can be powered by
redundant DC power modules. The
NCS 2015 system contains backup
flash memory that supports the
database (DB) and image backup
in the single mode operation. The
LCD unit is integrated with the fan
tray assembly. The fiber or cable
guide used in the NCS 2015 shelf
provides improved fiber
management. The air in the NCS
2015 chassis is drawn in through a
two-inch air inlet at the bottom of
the chassis, and expelled at the
top-rear. A single NCS 2015 shelf
assembly supports both ANSI and
ETSI standards.
TNCS Card The TNCS cards can be Cisco ONS 15454 DWDM
provisioned as active and standby Control Card and Node
cards in the NCS 2015 shelf. The Configuration Guide
TNCS cards serve as the processor
23 TNCS Card
card for the node. The TNCS cards
can be installed in slots 1 and 17 on 24 NTP-G313 Installing and
the NCS 2015 shelf. If the active Configuring the TNC, TNCE,
TNCS card fails, system traffic TSC, TSCE, or TNCS Card
switches to the redundant TNCS
card.
lxvi

17 SMR9 FS, 24 SMR9 FS, 34 The 17 SMR9 FS, 24 SMR9 FS, 34
SMR9 FS and SMR20 FS Cards SMR9 FS, and SMR20 FS cards
are tunable over 96 channels in the
C-band, at 50-GHz spacing on the
ITU-T grid. The card provides the
flex spectrum capability, which
allows the user the flexibility to
allocate the channel bandwidth, to
increase the network scalability.
The 17 SMR9 FS, 24 SMR9 FS,
and 34 SMR9 FS cards support up
to 9 directions for each ROADM
node. The SMR20 FS card supports
up to 20 directions for each
ROADM node. The cards support
count based licensing and can be
installed in any service slots in the
chassis.
lxvii

Cisco ONS 15454 DWDM Line
Card Configuration Guide
• 17 SMR9 FS, 24 SMR9 FS,
34 SMR9 FS and SMR20 FS
Cards
Configuration Guide
• Node Reference
Configuration Guide
Amplifier Line Settings
Amplifier Threshold Settings
• DLP-G406 Changing Card
Optical Channel Parameters
or SMR20 FS Cards
Optical Channel Thresholds
or SMR20 FS Cards
Line Parameters for
40-WXC-C, 80-WXC-C,
or SMR20 FS Cards
Optical Line Thresholds for
40-WXC-C, 80-WXC-C,
or SMR20 FS Cards
• DLP-G772 Viewing
Wavelength Power for
or SMR20 FS Card
• DLP-G773 Creating a Flex
Spectrum or ITU Circuit for
lxviii

or SMR20 FS Card
• DLP-G140 View Power
40-SMR2-C,17 SMR9 FS, 24
SMR9 FS, 34 SMR9 FS, and
SMR20 FS Cards
5888 17 SMR9 FS, 24 SMR9
FS,
34 SMR9 FS, and SMR20
FS Cards
12-AD-FS and 16-AD-FS Cards The 12-AD-FS card is an add/drop
card that provides contentionless, Cisco ONS 15454 DWDM
colorless, omnidirectional, and flex Line Card Configuration
spectrum capability on 4 channels Guide
over 4 directions. The 16-AD-FS
23 12-AD-FS Card
card provides contentionless,
colorless, omnidirectional, and flex 24 16-AD-FS Card
spectrum capability on 16 channels Cisco ONS 15454 DWDM
over more than 4 directions using Network Configuration Guide
upgrade ports. The cards can be
5888 DLP-G414 Changing
installed in any service slots in the
Cisco ONS 15454 M6 and NCS Optical Line Settings for
2015 chassis. Multiplexer and
Demultiplexer Cards
5889 DLP-G415 Changing
Optical Line Threshold
Settings for Multiplexer and
Demultiplexer Cards
5890 DLP-G781 Switching
the Channels for 12-AD-FS
and 16-AD-FS Cards
5891 DLP-G479 View Optical
Power Statistics for the
PSM, 12-AD-FS, and 16-
AD-FS Cards
lxix
Passive Optical Modules A new generation of passive optical Installing the Cisco ONS 15454
modules can be used to DWDM Passive Optical Modules
accommodate the ROADM nodes
• Components of Cisco ONS
built with the SMR FS and AD-FS
15454 DWDM Passive
cards. Two types of modules are
available: interconnection modules, Optical Modules
and add/drop modules. The
modules are MF-MPO-16LC,
MF-2MPO-ADP, MF-16AE-CFS,
MF-10AD-CFS, and
PPMESH8-5AD. The SMR FS and
AD-FS cards can be interconnected
by the MF-MPO-16LC,
MF-2MPO-ADP, and the
PPMESH8-5AD modules. The
MF-16AE-CFS and
MF-10AD-CFS are only used as
passive add/drop modules in TDM
networks.
Splitter protection on 10x10G-LC Splitter protection can be Cisco ONS 15454 DWDM Line
card implemented on the 10x10G-LC Card Configuration Guide
card in the TXPP-10G mode. The 23 Operating
10x10G-LC card supports up to
Modes for 10x10G-
two splitter protection groups with
one client and two trunk ports. LC Card
24 NTP-G235
Provisioning an Operating
Mode
WSON Full LOGO support The linear impairments in full Cisco ONS 15454 DWDM
coherent networks follow the full Network Configuration Guide
Local Optimization Global 5888 WSON Full
Optimization (LOGO) model that
Coherent Networks
is applicable to 100G full coherent
Control Plane
networks. This enables circuit
5889 GMPLS Control Plane
selection and path validation during
routing process. The linear
impairment is calculated directly
form the source node.
OCHCC circuit creation using All the transponder and muxponder Cisco ONS 15454 DWDM
WSON cards support OCHCC circuit Network Configuration Guide
creation using WSON except
23 Card Support
AR-MXP and AR-XPE cards.
OCHCC circuits can be configured 24 DLP-G705
on the AR-XP card only in the Provisioning GMPLS
TXP-MR, TXPP-MR, MXP-MR-S, Optical Channel Client
and MXPP-MR-S operating modes. Connections
lxx
7% HD-FEC support on The 100GS-CK-LC and Cisco ONS 15454 DWDM Line
100GS-CK-LC and 200G-CK-LC 200G-CK-LC cards support Hard Card Configuration Guide
Decision FEC (HD-FEC) encoding
• 100GS-CK-LC and
with 7% overhead.
200G-CK-LC Cards
• FEC Modes for 100G-LC-C,
CFP-LC, 100G-CK-C,
100GS-CK-LC, and
200G-CK-LC Cards
Interoperability with NCS 4000 The 100GS-CK-LC and Cisco ONS 15454 DWDM
200G-CK-LC cards in Line Card Configuration
MXP-10X10G operating mode Guide
allows 10GE and OC-192 clients
5888 100GS-CK-LC
(multiplexed on 100G trunk) to
and 200G-CK-LC
interoperate with Cisco NCS 4000
Cards
platform.
5889 Key Features
User Login Credentials The user name can be up to 40 Cisco ONS 15454 DWDM Network
characters (up to 39 characters for Configuration Guide
TACACS and RADIUS
• DLP-G54 Create a Local User
authentication).
on a Single Node Using CTC
• DLP-G55 Creating a New
User on Multiple Nodes
• TACACS Access Server
• RADIUS Access Server
lxxi

MR-MXP Cards The MXP-MR card is a mixed rate Cisco ONS 15454 DWDM Line
10G and 40G client muxponder that Card Configuration Guide
is supported on the Cisco ONS 23 MR-MXP Card
15454 M2 and Cisco ONS 15454
24 NTP-G236 Modifying
M6 platforms. The card is equipped
the 100G-LC-C, 100G-CK-
with one CPAK port, two SFP
C, 100G-ME-C, 100ME-
ports, and two QSFP+ ports. The
CKC, 10x10G-LC, 100GS-
card can interoperate with
100GS-CK-LC, 200G-CK-LC, and
CK-LC, , 200G-CK-LC,
10x10G-LC cards through an ONS CFP-LC, WSE, or MR-MXP
Card Line Settings and PM
15454 M6, ONS 15454 M2
backplane. Parameter Thresholds
The MR-MXP card provides the

following features:
• Supports 200G operating
modes such as
MXP_10x10G_100G,
MXP_CK_100G, and
MXP_200G.
• Supports sub OpModes such
as OPM_10x10G and
OPM_100G on the card client
ports.
• Aggregation of 10x10G
clients payloads. The
aggregated payloads are then
forwarded to a 200G
companion trunk card.
• Termination point for a 100G
client payload on the CPAK
port.
lxxii

200G-CK-LC and 200G-CK-LIC The 200G-CK-LC and Cisco ONS 15454 DWDM
Cards 200G-CK-LIC cards transport 100 Line Card Configuration
or 200 gigabits per second across Guide
metro, regional, long-haul, and
5888 100G-LC-C, 100G-ME-
ultra-long-haul DWDM optical
C, 100G-CK-C, 100GS-CK-
networks. The 200G-CK-LIC is the
LC, 100ME-CKC, and
licensed card version of the
200G-CK-LC card. 200G-CK-LC Cards
The 200G-CK-LC card provides the 100G-LC-C, 100G-CK-
the following benefits: C, 100G-ME-C, 100ME-
• Supports 200G operating CKC, 10x10G-LC, 100GS-
modes such as CK-LC, , 200G-CK-LC,
MXP_10x10G_100G, CFP-LC, WSE, or MR-MXP
MXP_CK_100G, and Card Line Settings and PM
MXP_200G. Parameter Thresholds
• Allows choosing 16 QAM and

QPSK as the modulation
formats at the line side.
• Provides Standard G-FEC
(Reed-Solomon), Soft
Decision FEC (SD-FEC)
encoding with 20% overhead.
• Provides Nyquist filtering for
best performance and optimal
band usage.
• Supports feature-based
licensing.
100GS-CK-LC Card Enhancements The 100GS-CK-LC card supports Cisco ONS 15454 DWDM
200G operating modes such as Line Card Configuration
MXP_10x10G_100G, Guide
MXP_CK_100G, and MXP_200G.
23 Operating Modes for
100G-LC-C, 100G-ME-C,
100G-CK-C, 100GS-CK-
LC, 200G-CK-LC, and
100ME-CKC Cards
Licensing The 200G-CK-LIC card supports
feature-based licensing. The Cisco ONS 15454 DWDM
200G-CK-LIC is the licensed card Licensing Configuration Guide
version of the 200G-CK-LC card.
5888 200G-CK-LC Card
The base functionality is enabled
in the licensed card version.
Additional features are provided
through specific feature licenses.
lxxiii

Optical SMU An Optical software maintenance Cisco ONS 15454 DWDM
upgrade (SMU) is a patch that is Network Configuration Guide
provided to the customer to fix an 23 Optical SMU
emergency situation, such as
network failure or traffic loss. The 24 NTP-G347 Managing
user can download and activate a SMUs Using CTC
patch on the node(s) through CTC.
VTXP Enhancements • Pseudo Random Binary Cisco ONS 15454 DWDM

Sequence (PRBS) generation Network Configuration Guide
is supported on VTXP. 5888 NTP-G352 Enabling
• PM statistics for the CRS PRBS Settings for an
PLIM interface can be viewed Interface on the Cisco CRS
in a tabular format in CTC. Router
• Trail trace identifier (TTI) is 5889 NTP-G350 Viewing
supported on VTXP. It is PRBS Statistics for an
possible to individually Interface on the Cisco CRS
manage the Source Access Router
Point Identifier (SAPI), 5890 NTP-G337 Configuring
Destination Access Point Provisioning Parameters for
Identifier (DAPI), and User an Interface on the Cisco
Operator Data fields. CRS-1 Router
Monitor Performance
23 NTP-G349 Viewing PM
Parameters for an Interface
on the Cisco CRS Router
NFV Enhancements • In the Network Functional Cisco ONS 15454 DWDM

View (NFV), all the panes Network Configuration Guide
with the exception of the
5888 DWDM Network
Overview pane are iconised or
Functional View
hidden. The panes are visible
5889 NTP-G353 Creating
on request.
GMPLS Circuits Using the
• Fast circuit creation of Fast Circuit Mode
protected and unprotected
circuits is supported.
• The pre-route option allows
the WSON to detect the
probable path of the circuit.
lxxiv

Software Enhancements Several software enhancements are Cisco ONS 15454 DWDM
introduced in Release 10.3 : Network Configuration Guide
• The TNC/TSC/TNCE/TSCE 23 NTP-G354 Enabling
control cards on the ONS Cooling Profile Using CTC
15454 M6 chassis
Security Reference
automatically detects and
adjusts the cooling profile 5888 User Privileges and
according to the cards present Policies
on the chassis.
• The privilege for Provisioning
Line Card Configuration
user has been extended at
Node View and Network Guide
View. 23 DLP-G722 Changing the
Card OTN Settings
• The Trail Trace Identifier
24 Key Features of 100G-
(TTI) in the path monitoring
LC-C, 100G-ME-C, 100G-
overhead is supported in OTU,
CK-C, 100ME-CKC,
and ODU OTN frames. It is
10x10G-LC, 100GS-CK-LC,
possible to individually
200G-CK-LC, CFP-LC, and
manage the Source Access
Point Identifer (SAPI), MR-MXP Cards
Destination Access Point Cisco ONS 15454 DWDM
Identifier (DAPI), and User Control Card and Node
Operator Data fields. Configuration Guide
• A new squelch option named 5888 DLP-G492 Editing an
LF is supported for 10GE, Optical Side
40GE, and 100GE payloads.
This option is supported on
10x10G-LC, CFP-LC,
100G-LC-C, 100G-CK-LC,
100GS-CK-LC, and
200G-CK-LC cards.
• A side description can be
created or edited for all the
optical and virtual sides of the
node using CTC or TL1.
• PSM is supported on
100GS-CK-LC or
200G-CK-LC cards on their
trunk ports where the
protection switch time of 50
ms is achieved in the
TXP-100G configuration with
20%SD FEC.
lxxv
This table summarizes the new and changed information for Release 10.1.0.1, and tells you where the
Table 9: New and Changed Features - R10.1.0.1

100GS-CK-LC Card The 100GS-CK-LC card is a Cisco ONS 15454 DWDM Line
tunable DWDM trunk card that Card Configuration Guide
simplifies the integration and 23 100G-LC-C, 100G-ME-
transport of the 100 Gigabit C, 100G-CK-C, 100GS-CK-
Ethernet interfaces and services on
LC, and 100ME-CKC Cards
the enterprise or service provider
optical networks.
The 100GS-CK-LC card provides C, 100G-ME-C, 100ME-
the following benefits: CKC, 10x10G-LC, 100GS-
• Allows choosing 100G QPSK CK-LC, CFP-LC, or WSE
as the modulation format at
Parameter Thresholds
the line side.
• Provides 20% SD (Soft
Decision) FEC encoding and
Nyquist filtering for best
performance and optimal band
usage.
• Supports gridless tunability.
5888 Allows client

access either through the
local 100G CPAK interface
or through backplane lines
that allow interconnection
with an adjacent 10x10G-LC
card.
Split ROADM Nodes The split ROADM node feature Cisco ONS 15454 DWDM
allows the ROADM node to have Network Configuration Guide,
separate Network Elements (NEs) Release 10.x.x
for each line side leading to the
23 Node Reference
separation of different ROADM
degrees. When a node split is
configured, each line side is treated
as a separate NE. The whole NE
manageability is not lost in case of
failure. The legacy ROADM
configurations can be migrated to
split ROADM configurations using
CTC and CTP.
lxxvi

Software Enhancements Several software enhancements are 5888 NTP-G346 Resetting
introduced in Release 10.1. the Network Element to
Factory Defaults
5889 DLP-G775 Displaying
the Bandwidth Usage of the
STS Timeslots
5890 TACACS+ Security
5891 DLP-G776
Configure the Node for
TACACS+
Authentication
FLD-OSC The FLD-OSC is a passive unit
used to combine the optical service OSC Combiner/Splitter Module
channel (OSC) wavelengths to form
the DWDM aggregated signal, or
split the OSC wavelengths from the
DWDM aggregated signal. The
passive unit occupies a single slot
in the rack mounting bracket. The
passive unit is introduced due to the
end-of-sale of the OSC-CSM card
in the MSTP platform.

VTXP Enhancements The user can provision an OCH CC Cisco ONS 15454 DWDM
circuit using the Network Network Configuration Guide
Functional View (NFV between the 23 DLP-G705
MSTP transponder or muxponder
Provisioning GMPLS
client interface and the router PLIM
Optical Channel Client
interface ( 10G and 100G ethernet
controller). The OCHTrail circuit Connections
type is no longer directly supported 24 Source and Destination
between the router interfaces and Port Configuration
the MSTP ones; it is indirectly
created by the creation of the OCH
CC circuit.
lxxvii

CTC Enhancements • CTC displays the circuit Cisco ONS 15454 DWDM
constraints of the circuit in the Network Configuration Guide
graphical view of the Circuit
5888 GMPLS Path Constraints
Maintenance perspective of
the NFV. The user can also 5889 DLP-G732 Editing a
modify the circuit constraints GMPLS Circuit
of the circuit being edited in
the NFV. These modified 5890 DLP-G337 Configuring
circuit constraints are applied Provisioning Parameters for
after resignalling of the circuit an Interface on the Cisco
(automatic circuit restoration CRS-1 Router
or manual reroute).
• CTC displays the link
direction in the circuit map for
Link Management Protocol
(LMP) links between the
router PLIM interface and the
OCH ports on the MSTP
node. This is also applicable
to the internal patchcords
between the trunk interface
and the OCH ports of the
MSTP node.
• CTC allows tuning of the
router PLIM interface by
specifying the channel ID,
frequency or the wavelength.
• CTC displays the ethernet
statistics that are retrieved
from the ethernet controllers
on the router. The information
is displayed in a tabular
format.
WSON Enhancements The user can configure optical Cisco ONS 15454 DWDM
validation threshold values for the Network Configuration Guide
protected GMPLS circuits. DLP-G705 Provisioning GMPLS
Optical Channel Client Connections
lxxviii

Non-continuous Loopback Support The loopback and drop facility is Cisco ONS 15454 DWDM
on 100G Cards supported on the 100G-LC-C, Line Card Configuration
10x10G-LC, CFP-LC, and Guide
100G-CK-C cards as follows:
Key Features of 100G-LC-C,
1. Trunk facility loopback (drop) 100G-ME-C, 100G-CK-C, 100ME-
and client facility loopback CKC, 10x10G-LC, 100GS-CK-LC,
(drop) is supported on: and CFP-LC Cards
• 100G-LC-C cards
configured in the TXP
mode (with CXP client
pluggable) for OTU4 and
100GE client payloads.
• 100G-CK-LC configured
in the TXP mode (with
CPAK client pluggable)
for OTU4 and 100GE
client payloads.
2. Backplane facility loopback

(drop) is supported on:
• 100G-LC-C and CFP-LC
mode (with CFP client
• 100G-CK-C and CFP-LC
mode (with CFP client
New ROADM Configurations Four new A/D ROADM Cisco ONS 15454 DWDM Network
configurations are supported for 48 Configuration Guide
channel 100 GHz systems.
ROADM Node
lxxix

VTXP and GMPLS Enhancements • The user can regenerate a Cisco ONS 15454 DWDM
circuit that is created from Network Configuration Guide
UNI interface or VTXP. 23 WSON Full
• The user can configure the Coherent Networks
expected circuit wavelength Control Plane
for VTXP using CTC. 24 DLP-G346
• The user can create a GMPLS Provisioning Optical
UNI circuit when VTXP UNI Channel Client
is enabled in CTC. Connections
• The user can either specify a 25 DLP-G395
mandatory or preferred Creating an Optical
wavelength for routing while Channel Trail
creating the GMPLS circuit
26 DLP-G707
using CTC.
Upgrading a Non-
• The user can upgrade an
GMPLS Circuit to a
existing GMPLS circuit from
GMPLS Circuit
the legacy signaling to the
27 DLP-G708 Creating a
new signaling that supports
GMPLS Optical Channel Trail
the LOGO (Local
28 DLP-G733 Configuring
Optimization Global
Optimization) and GMPLS UNI
regeneration features on the
GMPLS circuit.
lxxx

EDRA-1-xx and EDRA-2-xx Cards The double-slot EDRA-1-xx and Cisco ONS 15454 DWDM
EDRA-2-xx cards are Line Card Configuration
erbium-doped Raman amplifiers Guide
(EDRAs) that support Raman
5888 EDRA-1-xx and EDRA-
amplification on very long
2-xx Cards
unregenerated spans. Each EDRA
card can manage up to 96 channels, 5889 EDRA Workflow
Diagram
50-GHz-spaced from 196.1 GHz
(1528.77nm) to 191.35 GHz 5890 EDRA-1-xx and EDRA-
(1566.72 nm). 2-xx Cards Power
Monitoring
Network Configuration Guide
23 Automatic Raman
Pump Calculation
24 ARPC Workflow
25 EDRA Card Start Up
and Fiber Link Turn Up
26 NTP-G184 Creating
a Provisionable
Patchcord
Thresholds
28 EDRA optical safety
29 DLP-G140 View Power
16WXC-FS Card The double-slot cross connect
16-port Flex Spectrum ROADM
line card (16-WXC-FS) can be used
and 40-SMR2-C Cards
in the core of the network. The card
is used to build ROADM nodes Cisco ONS 15454 DWDM
with 96 channels spaced at 50-GHz, Line Card Configuration
flex spectrum channels, or a
Guide
combination of the two. The card
provides the flex spectrum 5888 16-WXC-FS Card
capability, which allows the user Cisco ONS 15454 DWDM
the flexibility to allocate the
Network Configuration Guide
channel bandwidth, to increase the
network scalability. 23 NTP-G174 Modifying
the Line Settings and PM
Thresholds for 40-WXC-C,
80-WXC-C, or 16-WXC-
FS Cards
24 Node Reference
lxxxi

Passive Optical Modules A new generation of passive optical Installing the Cisco ONS 15454 M2
modules can be used to and ONS 15454 M6 Passive
accommodate ROADM nodes built Optical Modules
with the 16-WXC-FS and EDRA
cards. Three types of modules are
available: patch panel modules,
add/drop modules, and adapter
modules.
100G-CK-C and 100ME-CK-C The 100G-CK-C and 100ME-CKC Cisco ONS 15454 DWDM Line
Cards cards are tuneable over the entire Card Configuration Guide
C-band. The 100G-CK-C card 5888 100G-LC-C, 100G-ME-
works similar to the 100G-LC-C C, 100G-CK-C, 100GS-CK-
card. The 100G-CK-C card has the
LC, and 100ME-CKC Cards
new CPAK client interface
replacing the CXP client interface
of the 100G-LC-C card.
C, 100G-ME-C, 100ME-
CKC, 10x10G-LC, 100GS-
CK-LC, CFP-LC, or WSE
Software Enhancements Several software enhancements are Cisco ONS 15454 DWDM Network
introduced in Release 10.0 Configuration Guide
• LSP Priority
• LSP Setup with Regenerators
• Restoration Based on LSP
Priority
• WSON Full Coherent
Networks Control Plane
• DLP-G705 Provisioning
GMPLS Optical Channel
Client Connections
• DLP-G708 Creating a
GMPLS Optical Channel Trail
• DLP-G733 Configuring
GMPLS UNI
Frame Type on the OSC
lxxxii
CHAPTER 1
Setting Up Optical Service Channel Cards
This chapter describes the optical service channel (OSC) cards for Cisco ONS 15454 dense wavelength
division multiplexing (DWDM) networks. For card safety and compliance information, refer to the
Regulatory Compliance and Safety Information for Cisco ONS Platforms document.
An optical service channel (OSC) is a bidirectional channel connecting two adjacent nodes in a DWDM
ring. For every DWDM node (except terminal nodes), two different OSC terminations are present, one for
the west side and another for the east side. The channel transports OSC overhead that is used to manage
DWDM networks. An OSC signal uses the 1510-nm wavelength and does not affect client traffic. The
primary purpose of this channel is to carry clock synchronization and orderwire channel communications
for the DWDM network. It also provides transparent links between each node in the network. The OSC is
an OC-3/STM-1 formatted signal.
There are two versions of the OSC modules: the OSCM, and the OSC-CSM, which contains the
OSC wavelength combiner and separator component in addition to the OSC module.
The Mesh/Multiring Upgrade (MMU) card is used to optically bypass a given wavelength from one
section of the network or ring to another one without requiring 3R regeneration.
Note On 15454-M2 and 15454-M6 shelves, the TNC and TNCE cards include the functions of the OSCM card.
OSC can be created on the OC3 port (SFP-0) of the TNC, TNCE, and TNCS cards.
The TNC, TNCE, and TNCS cards support two optical service channels (OSC): primary OSC and
secondary OSC.
The primary optical service channel (SFP-0) supports the following interfaces:
23 OC-3/STM-1
24 Fast Ethernet (FE)
25 Gigabit Ethernet (GE).
The secondary optical service channel (SFP-1) supports the following interfaces:
5888 Fast Ethernet (FE)
5889 Gigabit Ethernet (GE).
1
Card Compatibility
Note Unless noted otherwise, the cards described in this chapter are supported on the
Cisco ONS 15454, Cisco ONS 15454 M6, Cisco ONS 15454 M2 platforms.
Note Unless otherwise specified, “ONS 15454” refers to both ANSI and ETSI shelf
assemblies.
23 Card Compatibility, on page 2

24 Class 1 Laser Safety Labels, on page 2
25 OSCM Card, on page 2
26 OSC-CSM Card, on page 4
Card Compatibility
Table 13: Software Release Compatibility for Optical Service Channel Cards in Cisco ONS 15454
Card Name R4.5 - R10.0 R10.5 R10.5.2/10.6.1/10.6.2/10.7/10.8/10.9
OSCM ONS 15454 ONS 15454 ONS 15454
OSC-CSM ONS 15454, ONS 15454 ONS 15454, ONS 15454 ONS 15454, ONS 15454
M2, ONS 15454 M6 M2, ONS 15454 M6 M2, ONS 15454 M6,
NCS 2015
Class 1 Laser Safety Labels

For information about safety labels, see the "Safety Labels" section.
OSCM Card
The OSCM card has reached end of support.
(Cisco ONS 15454 only)
Note For OSCM card specifications, see the OSCM Card Specifications document.
Note On 15454-M2 and 15454-M6 shelves, the TNC and TNCE cards include the functions of the OSCM card.
2
OSCM Card Functions
The OSCM card is used in amplified nodes that include the OPT-BST, OPT-BST-E, or OPT-BST-L booster
amplifier. The OPT-BST, OPT-BST-E, and OPT-BST-L cards include the required OSC wavelength combiner
and separator component. The OSCM cannot be used in nodes where you use OC-N/STM-N cards, electrical
cards, or cross-connect cards. The OSCM uses Slots 8 and 10, which are also cross-connect card slots.
The OSCM supports the following features:
5888 OC-3/STM-1 formatted OSC
5889 Supervisory data channel (SDC) forwarded to the TCC2/TCC2P/TCC3 cards for processing
5890 Distribution of the synchronous clock to all nodes in the ring
5891 100BaseT far-end (FE) User Channel (UC)
5892 Monitoring functions such as orderwire support and optical safety
The OC-3/STM-1 section data communications channel (SDCC or RS-DCC) overhead bytes are used for
network communications. An optical transceiver terminates the OC-3/STM-1, then it is regenerated and
converted into an electrical signal. The SDCC or RS-DCC bytes are forwarded to the active and standby
TCC2/TCC2P/TCC3 cards for processing through the system communication link (SCL) bus on the
backplane. Orderwire bytes (E1, E2, F1) are also forwarded via the SCL bus to the TCC2/TCC2P/TCC3 for
forwarding to the AIC-I card.
The payload portion of the OC-3/STM-1 is used to carry the fast Ethernet UC. The frame is sent to a
packet-over-SONET/SDH (POS) processing block that extracts the Ethernet packets and makes them
available at the RJ-45 connector.
The OSCM distributes the reference clock information by removing it from the incoming OC-3/STM-1
signal and then sending it to the DWDM cards. The DWDM cards then forward the clock information to
the active and standby TCC2/TCC2P/TCC3 cards.
Note Due to memory limitations, TCC2/TCC2P cards are not supported from Release 10.5.2 onwards. As a
result, in a multishelf configuration, the TCC2/TCC2P card cannot be a node controller or a shelf
controller. Upgrade the TCC2/TCC2P card to a TCC3 card.
For more information about the OSCM card, see

http://www.cisco.com/en/US/prod/collateral/optical/ps5724/ps2006/product_data_sheet09186a00801a1641.html.
OSCM Card Functions

The functions of the OSCM card are:
23 OSCM Card Power Monitoring
24 Card-level LEDs on OSCM and OSC-CSM Cards
25 Port-level LEDs
OSCM Card Power Monitoring

Physical photodiode P1 monitors the power for the OSCM card. The returned power level value is
calibrated to the OSC TX port.
3
OSC-CSM Card
Table 14: OSCM VOA Port Calibration
Photodiode CTC Type Name Calibrated to Port

P1 Output OSC OSC TX
For information on the associated TL1 AIDs for the optical power monitoring points, refer the “CTC
Port Numbers and TL1 Aids” section in Cisco ONS SONET TL1 Command Guide.
OSC-CSM Card
The OSC-CSM card has reached end of support.
Note For OSC-CSM card specifications, see the OSC-CSM Card Specifications document.
The OSC-CSM card is used in unamplified nodes. This means that the booster amplifier with the OSC
wavelength combiner and separator is not required for OSC-CSM operation. The OSC-CSM can be
installed in Slots 1 to 6 and 12 to 17. To operate in hybrid mode, the OSC-CSM cards must be
accompanied by cross-connect cards. The cross-connect cards enable functionality on the OC-N/STM-N
cards and electrical cards.
The OSC-CSM supports the following features:
5888 Optical combiner and separator module for multiplexing and demultiplexing the optical service
channel to or from the wavelength division multiplexing (WDM) signal
5889 OC-3/STM-1 formatted OSC
5890 SDC forwarded to the TCC2/TCC2P/TCC3 cards for processing
5891 Distribution of the synchronous clock to all nodes in the ring
5892 100BaseT FE UC
5893 Monitoring functions such as orderwire support
5894 Optical safety: Signal loss detection and alarming, fast transmitted power shut down by
means of an optical 1x1 switch
5895 Optical safety remote interlock (OSRI), a feature capable of shutting down the optical output
power
5896 Automatic laser shutdown (ALS), a safety mechanism used in the event of a fiber cut. For
details on ALS provisioning for the card, see the . For information on using the card to implement
ALS in a network, see the .
The WDM signal coming from the line is passed through the OSC combiner and separator, where the OSC
signal is extracted from the WDM signal. The WDM signal is sent along with the remaining channels to the
COM port (label on the front panel) for routing to the OADM or amplifier units, while the OSC signal is
sent to an optical transceiver.
The OSC is an OC-3/STM-1 formatted signal. The OC-3/STM-1 SDCC or RS-DCC overhead bytes are used for
network communications. An optical transceiver terminates the OC-3/STM-1, and then it is regenerated and
converted into an electrical signal. The SDCC or RS-DCC bytes are forwarded to the active and standby
4
OSC-CSM Card Functions
TCC2/TCC2P/TCC3 cards for processing via the SCL bus on the backplane. Orderwire bytes (E1, E2,
F1) are also forwarded via the SCL bus to the TCC2/TCC2P/TCC3 for forwarding to the AIC-I card.
The payload portion of the OC-3/STM-1 is used to carry the fast Ethernet UC. The frame is sent to a POS
processing block that extracts the Ethernet packets and makes them available at the RJ-45 front panel connector.
The OSC-CSM distributes the reference clock information by removing it from the incoming OC-3/STM-
1 signal and then sending it to the active and standby TCC2/TCC2P/TCC3 cards. The clock distribution is
different from the OSCM card because the OSC-CSM does not use Slot 8 or 10 (cross-connect card slots).
controller. Upgrade the TCC2/TCC2P card to a TCC3 card
Note S1 and S2 (Figure 4-5 on page 4-10) are optical splitters with a splitter ratio of 2:98. The result is that the
power at the MON TX port is about 17 dB lower than the relevant power at the COM RX port, and the
power at the MON RX port is about 20 dB lower than the power at the COM TX port. The difference is due
to the presence of a tap coupler for the P1 photodiode.
For more information about the OSCM card, see

OSC-CSM Card Functions

The functions of the OSC-CSM card are:
23 OSC-CSM Card Power Monitoring
24 Alarms and Thresholds
25 Card-level LEDs on OSCM and OSC-CSM Cards
26 Port-level LEDs
OSC-CSM Card Power Monitoring

Physical photodiodes P1, P2, P3, and P5 monitor the power for the OSC-CSM card. Their function is as
follows:
5888 P1: The returned power value is calibrated to the LINE RX port, including the insertion loss of
the previous filter (the reading of this power dynamic range has been brought backward towards the
LINE RX output).
5889 P2: The returned value is calibrated to the LINE RX port.
5890 P3: The returned value is calibrated to the COM RX port.
5891 P5: The returned value is calibrated to the OSC TX port, including the insertion loss of the
subsequent filter.
5
OSC-CSM Card Power Monitoring
The returned power level values are calibrated to the ports as shown in the following table.
Table 15: OSC-CSM Port Calibration
Photodiode CTC Type Name Calibrated to Port Power PM Parameters
P1 Input Line LINE RX Channel Power Supported
OSC Power
P2 Input Line LINE RX OSC Power Supported
P3 Input Com COM RX Channel Power Supported
P5 Output OSC OSC TX OSC Power Supported
The OSC power on the LINE TX is the same as the power reported from P5.
The PM parameters for the power values are listed at Optics and 8b10b PM Parameter Definitions.
6
CHAPTER 2
Provisioning Optical Amplifier Cards
This chapter describes the optical amplifier cards used in Cisco ONS 15454 dense wavelength
division multiplexing (DWDM) networks and related procedures.
For card safety and compliance information, refer to the Regulatory Compliance and Safety Information
for Cisco ONS Platforms document.
Optical amplifier card architecture includes an optical plug-in module with a controller that manages
optical power, laser current, and temperature control loops. An amplifier also manages communication with
the control card and operation, administration, maintenance, and provisioning (OAM&P) functions such as
provisioning, controls, and alarms.
Note The cards described in this chapter are supported on the Cisco ONS 15454, Cisco ONS 15454 M6,
Cisco ONS 15454 M2 platforms, unless noted otherwise.
Note Unless otherwise specified, “ONS 15454” refers to both ANSI and ETSI shelf assemblies.
Note In this chapter, “RAMAN-CTP” refers to the 15454-M-RAMAN-CTP card. “RAMAN-COP” refers to
the 15454-M-RAMAN-COP card.
23 Applications of Amplifiers, on page 8

24 Card Compatibility, on page 8
25 OPT-PRE Amplifier Card, on page 11
26 OPT-BST and OPT-BST-E Amplifier Card, on page 12
27 OPT-BST-L Amplifier Card, on page 14
28 OPT-AMP-L Card, on page 15
29 OPT-AMP-17-C Card, on page 16
30 OPT-AMP-C Card, on page 18
31 OPT-RAMP-C and OPT-RAMP-CE Cards, on page 19
32 RAMAN-CTP and RAMAN-COP Cards, on page 21
33 OPT-EDFA-17, OPT-EDFA-24, and OPT-EDFA-35 Cards, on page 24
7
Applications of Amplifiers
0 EDRA-1-xx and EDRA-2-xx Cards, on page 27
Applications of Amplifiers
The following amplifiers can be configured as booster or preamplifiers:
0OPT-AMP-C
1OPT-AMP-17C
2OPT-AMP-L
3OPT-BST-E
4OPT-BST
5OPT-EDFA-17
6OPT-EDFA-24
The amplifier functions as a booster amplifier by default. The amplifier role is automatically configured when the
CTP NE update configuration file is loaded in CTC. The amplifier role can also be manually modified.
Note The OPT-BST and OPT-BST-E amplifiers are supported as preamplifiers in sites that are equipped with the
OPT-RAMP-C card. In any other configuration, the OPT-BST and OPT-BST-E cards must be configured
as a booster amplifier.
For more information about the supported configurations and network topologies, see and
Card Compatibility
The following table lists the Cisco Transport Controller (CTC) software compatibility for each optical
amplifier card.
Table 16: Software Release Compatibility for Optical Amplifier Cards
Card Name R4.5 /R4.6 R4.7/R5.0 R6.0 R7.0/R7.2 R8.0
OPT-PRE 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWDM
OPT-BST 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWDM
OPT-BST-E No 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWDM
OPT-BST-L No No No 15454-DWDM 15454-DWDM
OPT-AMP-L No No No 15454-DWDM 15454-DWDM
OPT-AMP-17-C No No No No 15454-DWDM
OPT-AMP-C No No No No No
8
Card Compatibility
Card Name R4.5 /R4.6 R4.7/R5.0 R6.0 R7.0/R7.2 R8.0
OPT-RAMP-C No No No No No
OPT-RAMP-CE No No No No No
RAMAN-CTP No No No No No
RAMAN-COP No No No No No
OPT-EDFA-17 No No No No No
OPT-EDFA-24 No No No No No
Card Name R8.5 R9.0 R9.1 R9.2/R9.2.1 R9.3 - R9.8 R10.0 92.01.6/8.01/.5/7.6R.01/20.5R1.0R
OPT-PRE 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWDM, 15454-DWDM, 15454-DWDWD,-M4,-WDM,54-54,154151
15454-M2, 15454-M2, 15454-M2,M,2,M-425-M4,52-1454151

15454-M6 15454-M6 15454-M6 M,6,M6-45-4-5415454151
SSCCNN
55110022
OPT-BST 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWDM, 15454-DWDM, 15454-DWDWD,-M4,-WDM,54-54,154151
15454-M2, 15454-M2, 15454-M2,M,2,M-425-M4,52-1454151

15454-M6 15454-M6 15454-M6 M,6,M6-45-4-5415454151
SSCCNN
55110022
OPT-BST-E 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWDM, 15454-DWDM, 15454-DWDWD,-M4,-WDM,54-54,154151
15454-M2, 15454-M2, 15454-M2,M,2,M-425-M4,52-1454151

15454-M6 15454-M6 15454-M6 M,6,M6-45-4-5415454151
SSCCNN
55110022
OPT-BST-L 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWWMD-4WD-M54-5445154511
OPT-AMP-L 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWWMD-4WD-M54-5445154511
OPT-AMP-17-C 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWDM, 15454-DWDM, 15454-DWDWD,-M4,-WDM,54-54,154151
15454-M2, 15454-M2, 15454-M2,M,2,M-425-M4,52-1454151

15454-M6 15454-M6 15454-M6 M,6,M6-45-4-5415454151
SSCCNN
55110022
OPT-AMP-C 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWDM, 15454-DWDM, 15454-DWDWD,-M4,-WDM,54-54,154151
15454-M2, 15454-M2, 15454-M2,M,2,M-425-M4,52-1454151

15454-M6 15454-M6 15454-M6 M,6,M6-45-4-5415454151
SSCCNN
55110022
OPT-RAMP-C No 15454-DWDM 15454-DWDM 15454-DWDM, 15454-DWDM, 15454-DWDWD,-M4,-WDM,54-54,154151
15454-M6 15454-M6 15454-M6 M,2,M-425-M4,52-1454151
M6-64-M564-54154151
9
Card Compatibility
OPT-RAMP-CE No No 15454-DWDM 15454-DWDM, 15454-DWDM, 15454-DWDWD,-M4,-WDM,54-54,154151
15454-M6 15454-M6 15454-M6 M,2,M-425-M4,52-1454151
M6-64-M564-54154151
morF(
)8.01R
S CN
5102
RAMAN-CTP No No No No 15454-M2, 15454-M2,M,2,M-425-M4,52-1454151

15454-M6 15454-M6 M,6,M-465-M4,56-1454151
SSCSCNCNN
551510102022
RAMAN-COP No No No No 15454-M2, 15454-M2,M,2,M-425-M4,52-1454151

15454-M6 15454-M6 M,6,M-465-M4,56-1454151
SSCSCNCNN
551510102022
OPT-EDFA-17 No No No No 15454-DWDM, 15454-DWDWD,-M4,-WDM,54-54,154151
15454-M2, 15454-M2,M,2,M-425-M4,52-1454151
15454-M6 15454-M6 M,6,M-465-M4,56-1454151
SSCSCNCNN
551510102022
OPT-EDFA-24 No No No No 15454-DWDM, 15454-DWDWD,-M4,-WDM,54-54,154151
15454-M2, 15454-M2,M,2,M-425-M4,52-1454151
15454-M6 15454-M6 M,6,M-465-M4,56-1454151
SSCSCNCNN
551510102022
OPT-EDFA-35 No No No No No No moorFNN
,8.01R
45451
, 2M
45451
, 6M
S CN
5102
EDRA-1-26 No No No No No 15454-M6 M,6,M-465-M4,56-1454151

SSCSCNCNN
551510102022

SSCSCNCNN
551510102022

SSCSCNCNN
551510102022
10
OPT-PRE Amplifier Card

SSCSCNCNN
551510102022
OPT-PRE Amplifier Card

The OPT-PRE card has reached end of support.
Note For OPT-PRE card safety labels, see Class 1M Laser Product Cards.
The OPT-PRE is a C-band, DWDM, two-stage erbium-doped fiber amplifier (EDFA) with midamplifier
loss (MAL) that can be connected to a dispersion compensating unit (DCU). The OPT-PRE is equipped
with a built-in variable optical attenuator (VOA) that controls the gain tilt and can also be used to pad the
DCU to a reference value. The card is designed to support up to 80 channels at 50-GHz channel spacing.
The OPT-PRE card features include:
0 Fixed gain mode with programmable tilt
1 True variable gain
2 Fast transient suppression
3 Nondistorting low-frequency transfer function
4 Settable maximum output power
5 Fixed output power mode (mode used during provisioning)
6 MAL for fiber-based DCU
7 Amplified spontaneous emissions (ASE) compensation in fixed gain mode
8 Full monitoring and alarm handling with settable thresholds
9 Four signal photodiodes to monitor the input and output optical power of the two amplifier stages through
CTC
10 An optical output port for external monitoring
Note The optical splitter has a ratio of 1:99, resulting in about 20 dB-lower power at
the MON port than at the COM TX port.
You can install the OPT-PRE card in slots 1 to 6 and 12 to 17 in ONS 15454 M12.
You can install the OPT-PRE card in the following slots.
Slots 2 and 3 in ONS 15454 M2
Slots 2 to 7 in ONS 15454 M6
11
Related Procedures for OPT-PRE Card
• Slots 2 to 16 in NCS 2015.
For more information about the OPT-PRE Amplifier card, see

http://www.cisco.com/en/US/prod/collateral/optical/ps5724/ps2006/product_data_sheet0900aecd800e4d24.html
and Card Features, on page 805.
Related Procedures for OPT-PRE Card

The following is the list of procedures and tasks related to the configuration of the OPT-PRE card:
NTP-G30 Install the DWDM Cards
NTP-G34 Install Fiber-Optic Cables on DWDM Cards and DCUs
NTP-G38 Provision OSC Terminations
NTP-G37 Run Automatic Node Setup
NTP-G51 Verify DWDM Node Turn Up
NTP-G76 Verify Optical Span Loss Using CTC
NTP-G74 Monitor DWDM Card Performance
DLP-G140 View Power Statistics for Optical Amplifier, 40-SMR1-C, and 40-SMR2-C Cards
NTP-G77 Manage Automatic Power Control
OPT-BST and OPT-BST-E Amplifier Card

The OPT-BST card has reached end of support.
Note For OPT-BST and OPT-BST-E cards safety labels, see "Class 1M Laser Product Cards". .
The OPT-BST is designed to ultimately support up to 80 channels at 50-GHz channel spacing. The OPT-
BST-E amplifier card is a gain-enhanced version of the OPT-BST card. It is designed to support up to 80
channels at 50-GHz channel spacing. Both the cards are C-band, DWDM EDFA with optical service
channel (OSC) add-and-drop capability. When an OPT-BST or an OPT-BST-E is installed, an OSCM card
is also needed to process the OSC. The OPT-BST cards features include:
Fixed gain mode (with programmable tilt)
Gain range of 5 to 20 dB in constant gain mode and output power mode for an OPT-BST card
Gain range of 8 to 23 dBm with the tilt managed at 0 dBm in constant gain mode and output power
mode for an OPT-BST-E card
Enhanced gain range of 23 to 26 dBm with unmanaged tilt with OPT-BST-E card
True variable gain
Built-in VOA to control gain tilt
12
Related Procedures for OPT-BST and OPT-BST-E Cards
Fast transient suppression

Nondistorting low-frequency transfer function
Settable maximum output power
Fixed output power mode (mode used during provisioning)
ASE compensation in fixed gain mode
Full monitoring and alarm handling with settable thresholds
Optical Safety Remote Interlock (OSRI), a CTC software feature capable of shutting down optical
output power or reducing the power to a safe level (automatic power reduction)
Automatic laser shutdown (ALS), a safety mechanism used in the event of a fiber cut. For information
about using the card to implement ALS in a network, see "Network Optical Safety". .
Note The optical splitters each have a ratio of 1:99. The result is that MON TX and
MON RX port power is about 20 dB lower than COM TX and COM RX port
power.
You can install the OPT-BST and OPT-BST-E cards in slots 1 to 6 and 12 to 17 in ONS 15454 M12.
You can install the OPT-BST and OPT-BST-E cards in the following slots.
Slots 2 to 16 in NCS 2015.
For more information about the OPT-BST and OPT-BST-E Amplifier cards, see
http://www.cisco.com/en/US/prod/collateral/optical/ps5724/ps2006/product_data_sheet0900aecd802be30a.html
Related Procedures for OPT-BST and OPT-BST-E Cards

The following is the list of procedures and tasks related to the configuration of the OPT-BST and OPT-
BST-E cards:
13
OPT-BST-L Amplifier Card
OPT-BST-L Amplifier Card
Note For OPT-BST-L safety labels, see "Class 1M Laser Product Cards".
The OPT-BST-L is an L-band, DWDM EDFA with OSC add-and-drop capability. The card is well suited
for use in networks that employ dispersion shifted (DS) fiber or SMF-28 single-mode fiber. The OPT-BST-
L is designed to ultimately support 64 channels at 50-GHz channel spacing, but in Software R9.0 and
earlier it is limited to 32 channels at 100-GHz spacing. When the system has an OPT-BST-L installed, an
OSCM card is needed to process the OSC. You can install the OPT-BST-L card in Slots 1 to 6 and 12 to 17
of ONS 15454 M12. The card’s features include:
Fixed gain mode (with programmable tilt)
Standard gain range of 8 to 20 dB in the programmable gain tilt mode
True variable gain
20 to 27 dB gain range in the uncontrolled gain tilt mode
OSRI
ALS
Note The optical splitters each have a ratio of 1:99. The result is that MON TX and
MON RX port power is about 20 dB lower than COM TX and COM RX port
power.
For more information about the OPT-BST-L Amplifier card, see Data Sheet and Card Features, on page 805.
Related Procedures for OPT-BST-L Card

The following is the list of procedures and tasks related to the configuration of the OPT-BST-L card:
• NTP-G143 Import the Cisco Transport Planner NE Update Configuration File
14
OPT-AMP-L Card

OPT-AMP-L Card
Note For OPT-AMP-L card safety labels, see "Class 1M Laser Product Cards"..
The OPT-AMP-L is an L-band, DWDM optical amplifier card consisting of a two-stage EDFA with
midstage access loss (MSL) for an external DCU and OSC add-and-drop capability. Using CTC, the card is
provisionable as a preamplifier (OPT-PRE) or booster amplifier (OPT-BST), and is well suited for use in
networks that employ DS or SMF-28 fiber. The amplifier can operate up to 64 optical transmission
channels at 50-GHz channel spacing in the 1570 nm to 1605 nm wavelength range.
When an OPT-AMP-L installed, an OSCM card is needed to process the OSC. You can install the two-
slot OPT-AMP-L card in slots 1 to 6 and 12 to 17 of ONS 15454 M12.
The card has the following features:
Maximum power output of 20 dBm
True variable gain amplifier with settable range from 12 to 24 dBm in the standard gain range and 24
dBm to 35 dbM with uncontrolled gain tilt
Up to 12 dBm MSL for an external DCU
Fast transient suppression; able to adjust power levels in hundreds of microseconds to avoid bit errors
in failure or capacity growth situations
Nondistorting low frequency transfer function
Midstage access loss for dispersion compensation unit
Constant pump current mode (test mode)
Constant output power mode (used during optical node setup)
Constant gain mode
15
Related Procedures for OPT-AMP-L Card
Internal ASE compensation in constant gain mode and in constant output power mode
Full monitoring and alarm handling capability
Optical safety support through signal loss detection and alarm at any input port, fast power down control
(less than one second), and reduced maximum output power in safe power mode. For information on
using the card to implement ALS in a network, see "Network Optical Safety".
Note Before disconnecting any OPT AMP-L fiber for troubleshooting, first make
sure the OPT AMP-L card is unplugged.
For more information about the OPT-AMP-L card, see the Data Sheet.
Related Procedures for OPT-AMP-L Card

The following is the list of procedures and tasks related to the configuration of the OPT-AMP-L card:
NTP-G143 Import the Cisco Transport Planner NE Update Configuration File
NTP-G160 Modify OPT-AMP-L, OPT-AMP-17-C, OPT-AMP-C, OPT-RAMP-C, OPT-RAMP-CE,
15454-M-RAMAN-CTP, 15454-M-RAMAN-COP, OPT-EDFA-17, and OPT-EDFA-24 Card Line
Settings and PM Thresholds
OPT-AMP-17-C Card
Note For OPT-AMP-17-C safety labels, see "Class 1M Laser Product Cards"..
The OPT-AMP-17-C is a 17-dB gain, C-band, DWDM EDFA amplifier/preamplifier with OSC add-and-
drop capability. It supports 80 channels at 50-GHz channel spacing in the C-band (that is, the 1529 nm to
1562.5 nm wavelength range). When the system has an OPT-AMP-17-C installed, an OSCM card is
needed to process the OSC.
16
Related Procedures for OPT-AMP-17-C Card
The card features include:

Fixed gain mode (no programmable tilt)
Standard gain range of 14 to 20 dB at startup when configured as a preamplifier
Standard gain range of 20 to 23 dB in the transient mode when configured as a preamplifier
Gain range of 14 to 23 dB (with no transient gain range) when configured as a booster amplifier
True variable gain
OSRI
ALS
You can install the OPT-AMP-17-C card in slots 1 to 6 and 12 to 17 in ONS 15454 M12.
You can install the OPT-AMP-17-C card in the following slots.
For more information about the OPT-AMP-17-C card, see

http://www.cisco.com/en/US/prod/collateral/optical/ps5724/ps2006/product_data_sheet0900aecd800e4d24.html
Related Procedures for OPT-AMP-17-C Card

The following is the list of procedures and tasks related to the configuration of the OPT-AMP-17-C card:
17
OPT-AMP-C Card
OPT-AMP-C Card
Note For OPT-AMP-C card safety labels, see "Class 1M Laser Product Cards".
The OPT-AMP-C card is a 20-dB output power, C-band, DWDM EDFA amplifier/preamplifier. It
contains mid-stage access loss for a Dispersion Compensation Unit (DCU). To control gain tilt, a VOA is
used. The VOA can also be used to attenuate the signal to the DCU to a reference value. The amplifier
module also includes the OSC add (TX direction) and drop (RX direction) optical filters.
The OPT-AMP-C card supports 80 channels at 50-GHz channel spacing in the C-band (that is, the 1529
nm to 1562.5 nm wavelength range). When the system has an OPT-AMP-C card installed, an OSCM card
is needed to process the OSC.
The card’s features include:
Mid-stage access for DCU
Constant gain mode
ASE compensation in Constant Gain and Constant Output Power modes
Programmable tilt
Gain range with gain tilt control of 12 to 24 dB
Extended gain range (with uncontrolled tilt) of 24 to 35 dB
OSRI
ALS
In ONS 15454 M12, slots 2 to 6 and Slots 12 to 16 are the default slots for provisioning the OPT-AMP-
C card as a preamplifier, and slots 1 and 17 are the default slots for provisioning the OPT-AMP-C card
as a booster amplifier.
18
Related Procedures for OPT-AMP-C Card
You can install the OPT-AMP-C card in the following slots.

For more information about the OPT-AMP-C card, see

http://www.cisco.com/en/US/prod/collateral/optical/ps5724/ps2006/prod_data_sheet0900aecd8072b322.html.
Related Procedures for OPT-AMP-C Card

The following is the list of procedures and tasks related to the configuration of the OPT-AMP-C card:
OPT-RAMP-C and OPT-RAMP-CE Cards
Note For OPT-RAMP-C or OPT-RAMP-CE card safety labels, see "Class 1M Laser Product Cards".
The OPT-RAMP-C card is a double-slot card that improves unregenerated sections in long spans using the
span fiber to amplify the optical signal. Different wavelengths in C-band receive different gain values. To
achieve Raman amplification, two Raman signals (that do not carry any payload or overhead) are required
to be transmitted on the optical fiber because the gain generated by one signal is not flat. The energy of
these Raman signals transfer to the higher region of the spectrum thereby amplifying the signals transmitted
at higher wavelengths. The Raman effect reduces span loss but does not compensate it completely.
19
OPT-RAMP-C and OPT-RAMP-CE Cards
When the Raman optical powers are set correctly, a gain profile with limited ripple is achieved. The
wavelengths of the Raman signals are not in the C-band of the spectrum (used by MSTP for payload
signals). The two Raman wavelengths are fixed and always the same. Due to a limited Raman gain, an
EDFA amplifier is embedded into the card to generate a higher total gain. An embedded EDFA gain block
provides a first amplification stage, while the mid stage access (MSA) is used for DCU loss compensation.
The OPT-RAMP-CE card is a 20 dBm output power, gain-enhanced version of the OPT-RAMP-C card and
is optimized for short spans. The OPT-RAMP-C and OPT-RAMP-CE cards can support up to 80 optical
transmission channels at 50-GHz channel spacing over the C-band of the optical spectrum (wavelengths
from 1529 nm to 1562.5 nm). To provide a counter-propagating Raman pump into the transmission fiber,
the Raman amplifier provides up to 500 mW at the LINE-RX connector. The OPT-RAMP-C or OPT-
RAMP-CE card can be installed in Slots 1 to 5 and 12 to 16, and supports all network configurations.
However, the OPT-RAMP-C or OPT-RAMP-CE card must be equipped on both endpoints of a span.
The Raman total power and Raman ratio can be configured using CTC. The Raman configuration can
be viewed on the Maintenance > Installation tab.
The features of the OPT-RAMP-C and OPT-RAMP-CE card include:
Raman pump with embedded EDFA gain block
Raman section: 500 mW total pump power for two pump wavelengths
EDFA section:
OPT-RAMP-C: 16 dB gain and 17 dB output power
OPT-RAMP-CE: 11 dB gain and 20 dB output power
Gain Flattening Filter (GFF) for Raman plus EDFA ripple compensation
MSA for DC units
VOA for DC input power control
Full monitoring of pump, OSC, and signal power
Fast gain control for transient suppression
Low-FIT (hardware-managed) optical laser safety
Hardware output signals for LOS monitoring at input photodiodes
Optical service channel add and drop filters
Raman pump back-reflection detector
You can install the OPT-RAMP-C and OPT-RAMP-CE cards in the following slots.
Slots 2 to 7 in Cisco 2015 chassis. These cards upgrade to a new bootcode automatically when they are
installed between slots 2 and 7.
After the bootcode upgrade, the cards can be installed in Slots from 2 to 16 in Cisco NCS 2015 chassis.
20
Related Procedures for OPT-RAMP-C and OPT-RAMP-CE Cards
For more information about the OPT-RAMP-C and OPT-RAMP-CE cards, see
http://www.cisco.com/en/US/prod/collateral/optical/ps5724/ps2006/data_sheet_c78-500925.html. and Card
Features, on page 805.
Related Procedures for OPT-RAMP-C and OPT-RAMP-CE Cards

The following is the list of procedures and tasks related to the configuration of the OPT-RAMP-C and
OPT-RAMP-CE cards:
NTP-G201 Configure the Raman Pump on an MSTP Link
RAMAN-CTP and RAMAN-COP Cards
Note The RAMAN-CTP and RAMAN-COP cards are supported in R9.3.02 and later.
Note For RAMAN-CTP and RAMAN-COP cards safety labels, see "Class 1M Laser Product Cards".
The single-slot RAMAN-CTP and RAMAN-COP cards support counter and co-propagating Raman
amplification on very long unregenerated spans.
The cards manage up to 96 ITU-T 50-GHz spaced channels over the C-band of the optical spectrum
(wavelengths from 1528.77 nm to 1566.72 nm). The counter-propagating RAMAN-CTP card is the master
unit. The co-propagating RAMAN-COP card is the slave unit and can be used only when the counter-
propagating unit is present. The RAMAN-CTP card and the RAMAN-COP card must be installed in
adjacent slots for Cisco NCS 2000 Series chassis. For example, you can install in Slots 2 and 3, 4 and 5, or
6 and 7 in ONS 15454 M6. However, these adjacent slots must not be used to install two RAMAN-CTP or
two RAMAN-COP cards.
21
Important Notes Regarding Patchcord Installation
The RAMAN-CTP card can be calibrated either manually or using the Automatic Raman Pump
Amplification (ARPC) procedure from the Card tab in the Provisioning panel in CTC. When the RAMAN-
COP card is used, the RAMAN-CTP card can be calibrated only using the manual option. ARPC is
supported only in the NCS Flex package.
The features of the RAMAN-CTP and RAMAN-COP cards include:
Raman section: 1000 mW total pump power for four pumps and two wavelengths
Embedded distributed feedback (DFB) laser at 1568.77 nm to be used for optical safety and link
continuity (in RAMAN-CTP card only)
Photodiodes to enable monitoring of Raman pump power
Photodiodes to enable monitoring of the DFB laser and signal power (in RAMAN-CTP card only)
Hardware managed automatic laser shutdown (ALS) for optical laser safety
Hardware output signals for loss of signal (LOS) monitoring at input photodiodes
Raman pump back reflection detector to check for excessive back reflection
You can install the RAMAN-CTP and RAMAN-COP cards in the following slots.
Important Notes Regarding Patchcord Installation

Warning Avoid eye or skin exposure to direct or scattered radiation.
Two E-2000 PS PC to F-3000s SM PC patchcords are shipped with the RAMAN-CTP card.
One E-2000 PS PC to E-2000 PS PC patchcord is shipped with the RAMAN-COP card.
Connect the F-3000s SM PC connector to the RAMAN-CTP card before connecting the E2000 PS PC
high optical power connector to the card.
The F-3000s SM PC connector is mechanically and optically compatible with the LC PC connectors and
the LC PC mating adapters. If the connectors are clean, the standard connectors and the F-3000s SM
PC connectors can be used for optical power of 250 mW and higher.
RAMAN-CTP and RAMAN-COP Cards Power Monitoring

(Monitorización de alimentación RAMAN-CTP y tarjetas de
RAMAN-COP)
Fotodiodos físicos P1 a través de P10 controlar la potencia de la tarjeta de RAMAN-CTP
Table 17: RAMAN-CTP Port Calibration
P1 DFB in-fiber Output Power LINE-TX
P2 DWDM RX Input Power LINE-RX

22
Related Procedures for RAMAN-CTP and RAMAN-COP Cards
P3 Pump 1 in-fiber Output Power LINE-RX
P4 Pump 2 in-fiber Output Power LINE-RX
P5 Total Pump in-fiber Output Power LINE-RX
P6 Back-Reflected Pump Power LINE-RX
P7 DWDM TX Input Power COM-RX
P8 Total Co-Pump in-fiber Output LINE-TX

Power
P9 DFB Input Power LINE-RX
P10 ASE Input Power LINE-RX
Physical photodiodes P3 through P6 monitor the power for the RAMAN-COP card.
Table 18: RAMAN-CTP Port Calibration
P3 Pump 1 in-fiber Output Power RAMAN-TX
P4 Pump 2 in-fiber Output Power RAMAN-TX
P5 Total Pump in-fiber Output Power RAMAN-TX
P6 Back-Reflected Pump Power RAMAN-TX
For information on the associated TL1 AIDs for the optical power monitoring points, see the “CTC
Port Numbers and TL1 Aids” section in Cisco ONS SONET TL1 Command Guide, Release 9.8.
For more information about the RAMAN-CTP and RAMAN-COP cards, see
http://www.cisco.com/en/US/prod/collateral/optical/ps5724/ps2006/data_sheet_c78-658538.html and
Card Features, on page 805.
Related Procedures for RAMAN-CTP and RAMAN-COP Cards
Caution During a software upgrade, do not unplug the RAMAN-CTP or RAMAN-COP card fibers or connectors.
The ends of unterminated fibers or connectors emit invisible laser radiation.
The following is the list of procedures and tasks related to the configuration of the RAMAN-CTP and
RAMAN-COP cards:
23
OPT-EDFA-17, OPT-EDFA-24, and OPT-EDFA-35 Cards

NTP-G201 Configure the Raman Pump on an MSTP Link
NTP-G184 Create a Provisionable Patchcord
DLP-G690 Configure the Raman Pump Using Manual Day-0 Installation
Note For OPT-EDFA-17, OPT-EDFA-24, and OPT-EDFA-35 card safety labels, see "Class 1M Laser
Product Cards".
Note OPT-EDFA-35 card is supported only in NCS Flex and NCS SSON packages.
The OPT-EDFA-17, OPT-EDFA-24, and OPT-EDFA-35 cards are C-band, DWDM EDFA
amplifiers/preamplifiers with 20-dBm output powers for the OPT-EDFA-17 and OPT-EDFA-24 cards, and
+23-dBm output power for the OPT-EDFA-35 card. These cards do not contain mid-stage access loss for a
Dispersion Compensation Unit (DCU). The OPT-EDFA-17, OPT-EDFA-24, and OPT-EDFA-35 cards
provide a noise-figure optimized version of the EDFA amplifiers to cope with new modulation formats like
PM-DQPSK, which do not need dispersion compensation. To control gain tilt, a VOA is used. The
amplifier module also includes the OSC add (TX direction) and drop (RX direction) optical filters.
The OPT-EDFA-17, and OPT-EDFA-24 cards share the same hardware platform and firmware
architecture, but differ in their operative optical gain range, which is 17 dB and 24 dB respectively.
The OPT-EDFA-35 card has 2 possible gain range: gain range 1 from 12 to 24, and gain range 2 from 20
to 35 (extended gain range up to 40dB without tilt control).
The OPT-EDFA-17, OPT-EDFA-24, and OPT-EDFA-35 cards are true variable gain amplifiers, offering an
optimal equalization of the transmitted optical channels over a wide gain range. They support 96 channels at 50-
GHz channel spacing in the C-band (that is, 1528.77 nm to 1566.72 nm wavelength range). When an ONS 15454
has an OPT-EDFA-17, OPT-EDFA-24 or OPT-EDFA-35 card installed, an OSCM card is needed to
24
process the OSC. In ONS 15454 M12, slots 1 and 17 are the default slots for provisioning the OPT-EDFA-
17, OPT-EDFA-24, and OPT-EDFA-35 cards as a booster amplifier.
The OPT-EDFA-35 card is managed in a similar way as the OPT-EDFA-17 and OPT-EDFA-24 cards.
For each EDFA unit inside the OPT-EDFA-35 card, the following settings are allowed:
Configuration of PRE or BST role
Configuration of Constant Gain working mode
Configuration of Gain Range
The OPT-EDFA-35 card includes two identical amplification sections to serve two fiber directions
simultaneously, and each section has a switchable gain range that allow its usage over a wide gain range.
The OPT-EDFA-35 card is bidirectional (i.e. is acting on both pairs of fibers entering and exiting in/from
the node).
The main functionalities of the OPT-EDFA-17, OPT-EDFA-24, and OPT-EDFA-35 cards are:
(OPT-EDFA-17 and OPT-EDFA-24) Amplification of the input signal at COM-RX port towards LINE-
TX port through a true-variable gain EDFA block.
(OPT-EDFA-35) 2 EDFA amplifier units embedded into the card, amplification of the input signal at
LINE-1-RX port towards LINE-2-TX port through a true-variable gain EDFA-2 block, and
amplification of the input signal at LINE-2-RX port towards LINE-1-TX port through a true-variable
gain EDFA-1 block.
Multiplexing the OSC to the LINE-TX port
Demultiplexing the OSC from LINE-RX port
Monitoring of the LINE input or output signal with 1% TAP splitters
The features of the OPT-EDFA-17, OPT-EDFA-24, and OPT-EDFA-35 cards are:

Embedded Gain Flattening Filter
Constant output power mode
Constant gain mode
ASE compensation in Constant Gain and Constant Output Power modes
Programmable tilt
Gain range with gain tilt control of 5 to 17 dB (for OPT-EDFA-17 card), 12 to 24 dB (for OPT-EDFA-
24 card), and 12 to 24 dB and 20 to 35 dB (for OPT-EDFA-35)
Extended gain range (with uncontrolled tilt) of 17 to 20 dB (for OPT-EDFA-17 card), 24 to 27 dB (for
OPT-EDFA-24 card), and (for OPT-EDFA-35 card) of upto 27dB (for Gain Range1) and 40dB (for
Gain Range2).
25
OPT-EDFA-17, OPT-EDFA-24, and OPT-EDFA-35 Cards Power Monitoring
Optical Safety Remote Interlock (OSRI)

Automatic Alarm Shutdown (ALS)
You can install the OPT-EDFA-17 and OPT-EDFA-24 cards in slots 1 to 6 and 12 to 17 in ONS 15454 M12.
You can install the OPT-EDFA-17, OPT-EDFA-24, and OPT-EDFA-35 cards in the following slots.
For more information about the OPT-EDFA-17, and OPT-EDFA-24 cards, see
http://www.cisco.com/en/US/prod/collateral/optical/ps5724/ps2006/data_sheet_c78-658542.html and
Card Features.
OPT-EDFA-17, OPT-EDFA-24, and OPT-EDFA-35 Cards Power Monitoring

Physical photodiodes PD1 through PD6 monitor the power for the OPT-EDFA-17 and OPT-EDFA-24 cards.
Table 19: OPT-EDFA-17 and OPT-EDFA-24 Port Calibration
P1 EDFA Input Power COM-RX
P2 EDFA Output Power LINE-TX
P3 EDFA Output Power LINE-TX
P4 OSC ADD Input Power OSC-RX
P5 OSC DROP Output Power LINE-RX
P6 COM-TX Output Power LINE-RX
Physical photodiodes PD1 through PD8 monitor the power for the OPT-EDFA-35 card.
Table 20: OPT-EDFA-35 Port Calibration
P1 EDFA Input Power Line-2-RX
P2 EDFA Output Power Line-1-TX
P3 EDFA Input Power Line-1-RX
P4 EDFA Output Power Line-2-TX
P5 OSC-RX Input Power OSC-2-RX
P6 OSC-TX Output Power OSC-2-TX
26
Related Procedures for OPT-EDFA-17, OPT-EDFA-24, and OPT-EDFA-35 Cards
P7 OSC-TX Output Power OSC-1-TX
P8 OSC-RX Input Power OSC-1-RX
Related Procedures for OPT-EDFA-17, OPT-EDFA-24, and OPT-EDFA-35 Cards

The list of procedures and tasks related to the configuration of the OPT-EDFA-17, OPT-EDFA-24, and
OPT-EFDA-35 cards are:
NTP-G31 Install the DWDM Dispersion Compensating Units
15454-M-RAMAN-CTP, 15454-M-RAMAN-COP, OPT-EDFA-17, OPT-EDFA-24, and OPT-EDFA-
35 Card Line Settings and PM Thresholds
NTP-G107 Remove Permanently or Remove and Replace DWDM Cards
EDRA-1-xx and EDRA-2-xx Cards

(Cisco ONS 15454 M6)
Note For EDRA-1-xx and EDRA-2-xx card safety labels, see the section, Class 1M Laser Product Cards.
The double-slot EDRA-1-xx and EDRA-2-xx cards are erbium-doped Raman amplifiers that support
Raman amplification on long unregenerated spans.
The cards manage up to 96 ITU-T 50 GHz spaced channels over the C-band of the optical spectrum
(wavelengths from 1528.77 nm to 1566.72 nm). You can install the EDRA-1-xx and EDRA-2-xx cards in
the lowest slots to allow high output power. The power output is limited to 21dBm when the cards are
inserted in any slot. The OSC pluggable used with the cards is ONS-SC-OSC-18.0=.
27
EDRA Workflow Diagram
The cards can be used in point-to-point, ring, multi-ring, or mesh topologies and are supported on
flexible nodes in these node configurations:
Optical line amplifier nodes
Terminal nodes
Dynamic gain equaliser nodes
In addition to these node configuration having only EDRA cards as amplifiers, the system also supports
hybrid configurations with OPT-EDFA-17, OPT-EDFA-24, RAMAN-CTP, and RAMAN-COP cards.
These cards support span loss and gain values that are not supported in EDRA cards.
For gain less than 15dB, OPT-EDFA-17 or OPT-EDFA-24 must be used.
For gain greater than 35dB RAMAN-CTP (RAMAN-COP) and OPT-EDFA-17 or OPT-EDFA-24 must
be used.
Note The EDRA-1-xx and EDRA-2-xx cards are not compatible with 15454 -M6-FTA= fan tray assembly. The cards
are compatible only with 15454 -M6-FTA2 fan tray assembly or a subsequent fan tray assembly release.
You can install the EDRA-1-xx and EDRA-2-xx cards in the following slots.
For more information about the EDRA-1-xx and EDRA-2-xx cards, see
http://www.cisco.com/en/US/solutions/collateral/ns340/ns394/ns398/ns406/data_sheet_c78-729313.html.
EDRA Workflow Diagram

This figure shows the workflow diagram of the EDRA card. The diagram depicts the tasks required to
configure the EDRA card.
28
EDRA-1-xx and EDRA-2-xx Cards Power Monitoring
Figure 1: EDRA Card Workflow Diagram
EDRA-1-xx and EDRA-2-xx Cards Power Monitoring

The following table lists the physical photodiodes that monitor the power for the EDRA-1-xx and EDRA-2-
xx cards.
Table 21: EDRA-1-xx and EDRA-2-xx Port Calibration
PD1 Remnant Pump Input power LINE-TX
PD2 OSC Add Input Power OSC-RX
PD3 EDFA1 Input Power LINE-RX
PD4 EDFA1 Output Power COM-TX
PD5 EDFA2 Input Power COM-RX
PD6 EDFA2/LINE-TX Output Power LINE-TX
29
Related Procedures for EDRA-1-xx and EDRA-2-xx Cards
PD7 OSC Drop Output Power LINE-TX
PD11 Pump λ1 in-fibre Output Power LINE-RX
PD15 Total Pump in-fibre Output Power LINE-RX
PD16 Back-Reflected Pump Power LINE-RX
PD17 OTDR2-L Input Power OTDR2-L-RX
Port Numbers and TL1 Aids” section in Cisco NCS 2000 Series TL1 Command Guide.
Related Procedures for EDRA-1-xx and EDRA-2-xx Cards

The list of procedures and tasks related to the configuration of the EDRA-1-xx and EDRA-2-xx cards are:
NTP-G184 Create a Provisionable Patchcord
30
CHAPTER 3
Provisioning Multiplexer and
Demultiplexer Cards
Este capítulo describe el legado multiplexor y demultiplexor tarjetas en división de longitud de onda densa
Cisco ONS 15454 multiplexing (DWDM) redes y procedimientos relacionados.
Para información de seguridad y cumplimiento de la tarjeta, consulte la Regulatory Compliance and
Safety Information for Cisco ONS Platforms document.
Card Compatibility, on page 31

Optical Performance Parameters, on page 32
DWDM Channel Allocation Plan, on page 36
Safety Labels, on page 39
32DMX-O Card, on page 42
4MD-xx.x Card, on page 44
12-AD-FS Card, on page 46
16-AD-FS Card, on page 47
Related Procedures for the 12-AD-FS and 16-AD-FS Cards, on page 48
Card Compatibility
The table below lists the software compatibility for the respective cards.
Table 22: Software Compatibility for Multiplexer and Demultiplexer Cards in Cisco ONS 15454
Release Cards
32MUX-O 32DMX-O 4MD-xx.x 12-AD-FS, 16-AD-FS
R4.5 Yes Yes Yes No
R4.6 Yes Yes Yes No
R4.7 Yes Yes Yes No
31
Provisioning Multiplexer and Demultiplexer Cards
Optical Performance Parameters
R5.0 Yes Yes Yes No
R6.0 Yes Yes Yes No
R7.0 Yes Yes Yes No
R7.2 Yes Yes Yes No
R8.0 Yes Yes Yes No
R8.5 Yes Yes Yes No
R9.0 Yes Yes Yes No
R9.1 Yes Yes Yes No
R9.2 Yes Yes Yes No
R9.2.1 Yes Yes Yes No
R9.3 Yes Yes Yes No
R9.4 Yes Yes Yes No
R9.6.x Yes Yes Yes No
R9.8 Yes Yes Yes No
R10.0 Yes Yes Yes No
R10.5.2 No No No Yes
R10.6.1/10.6.2 No No No Yes
R107./108./109. No No No Yes

The following table lists the optical performance parameters for 40-Gbps cards that provide signal input
to multiplexer and demultiplexer cards.
Table 23: 40-Gbps Interface Optical Performance
Parameter Class A Class B Class I
Type Power OSNR Limited Power OSNR Limited Power OSNR Limited
Limited Limited Limited
Maximum bit 40 Gbps 40 Gbps 40 Gbps

rate
Regeneration 3R 3R 3R
FEC Yes No Yes (E-FEC)
32
Threshold Optimum Average Optimum
Maximum 10–15 10–12 10–15

BER
OSNR 23 dB 9 dB 23 dB 19 dB 20 dB 8 dB
sensitivity
Power –24 dBm –18 dBm –21 dBm –20 dBm –26 dBm –18 dBm
sensitivity
Power –8 dBm –8 dBm –8 dBm
overload
Transmitted Power Range
40-Gbps +2.5 to 3.5 dBm +2.5 to 3.5 dBm —

multirate
transponder/40-Gbps
EC
transponder
(40E-TXP-C
and
40ME-TXP-C)
OC-192 LR — — —
ITU
Dispersion +/–800 ps/nm +/–1,000 ps/nm +/–800 ps/nm

compensation
tolerance
Note • OSNR = optical signal-to-noise ratio

BER = bit error rate
Valores de rango de potencia transmitidos disminuidos por pérdidas de conector y cable de conexión,
son también los valores de potencia de entrada para las tarjetas OADM.
La tabla siguiente enumeran los parámetros de rendimiento óptico que proporcionan la señal de
entrada para los 40 Gbps multiplexor y demultiplexor tarjetas.
33
Table 24: 10-Gbps Interface Optical Performance Parameters
Parameter Class A Class B Class C Class I
Type Power OSNR Power OSNR OSNR Power OSNR

Limited Limited Limited Limited Limited Limited Limited
Maximum 10 Gbps 10 Gbps 10 Gbps 10 Gbps
bit rate
Regeneration 3R 3R 3R 3R
FEC Yes No No Yes (E-FEC)
Threshold Optimum Average Average Optimum
Maximum 10–15 10–12 10–12 10–15

BER
OSNR 23 dB 9 dB 23 dB 19 dB 19 dB 20 dB 8 dB
sensitivity
Power –24 dBm –18 dBm –21 dBm –20 dBm –22 dBm –26 dBm –18 dBm
sensitivity
Power –8 dBm –8 dBm –9 dBm –8 dBm
overload
10-Gbps +2.5 to 3.5 dBm +2.5 to 3.5 dBm — —

multirate
transponder/10-Gbps
FEC
transponder
(TXP_MR_10G)
OC-192 LR — — +3.0 to 6.0 —

ITU dBm
10-Gbps +3.0 to 6.0 dBm +3.0 to 6.0 dBm — +3.0 to 6.0 dBm
multirate
transponder/10-Gbps
FEC
transponder
(TXP_MR_10E)
Dispersion +/–800 ps/nm +/–1,000 ps/nm +/–1,000 +/–800 ps/nm

compensation ps/nm
tolerance
34
Note • OSNR = optical signal-to-noise ratio

BER = bit error rate
Valores de rango de potencia transmitidos disminuidos por pérdidas de conector y cable de conexión,
son también los valores de potencia de entrada para las tarjetas OADM.
The following table lists the optical interface performance parameters for 2.5-Gbps cards that provide
signal input to multiplexer and demultiplexer cards.
Table 25: 2.5-Gbps Interface Optical Performance
Parameter Class D Class E Class F Class G Class H Class J
Type Power OSNR Power OSNR OSNR Power OSNR Power OSNR Power
Limited Limited Limited Limited Limited Limited Limited Limited Limited Limited
Maximum 2.5 Gbps 2.5 Gbps 2.5 2.5 Gbps 1.25 Gbps 2.5
bit rate Gbps Gbps
Regeneration 3R 3R 2R 3R 3R 3R
FEC Yes No No No No No
Threshold Average Average Average Average Average Average
Maximum 10–15 10–12 10–12 10–12 10–12 10–12

BER
OSNR 14 dB 6 dB 14 dB 10 dB 15 dB 14 dB 11 dB 13 dB 8 dB 12 dB
sensitivity
Power –31 –25 –30 –23 –24 –27 –33 –28 –18 –26
sensitivity dBm dBm dBm dBm dBm dBm dBm dBm dBm dBm
Power –9 dBm –9 dBm –9 dBm –9 dBm –7 dBm –17dBm
overload
TXP_MR_25.G –1.0 to 1.0 dBm –1.0 to 1.0 dBm –1.0 to –2.0 to 0 dBm
1.0 dBm
TXPP_MR_25G. –4.5 to –2.5 dBm –4.5 to –2.5 dBm –4.5 to

–2.5dBm
MXP_MR_25G. — +2.0 to +4.0 dBm —
MXPP_MR_25G. — –1.5 to +0.5 dBm —
35
DWDM Channel Allocation Plan
Parameter Class D Class E Class F Class G Class H Class J
Type Power OSNR Power OSNR OSNR Power OSNR Power OSNR Power
2/4 port +2.5 to 3.5 dBm —

GbE
Transponder
(GBIC
WDM
100GHz)
Dispersion –1200 to –1200 to –1200 –1200 to –1000 to +3600 –1000
compensation +5400 ps/nm +5400 ps/nm to +3300 ps/nm ps/nm to
tolerance +3300 +3200
ps/nm ps/nm
Note Transmitted Power Range values decreased by patchcord and connector losses, are also the input power
values for the OADM cards.

ONS 15454 DWDM multiplexer and demultiplexer cards are designed for use with specific channels in the
C band and L band. In most cases, the channels for these cards are either numbered (for example, 1 to 32
or 1 to 40) or delimited (odd or even). Client interfaces must comply with these channel assignments to be
compatible with the ONS 15454 system.
Table 26: DWDM Channel Allocation Plan (C Band) lists the channel IDs and wavelengths assigned to
the C-band DWDM channels.
Note In some cases, a card uses only one of the bands (C band or L band) and some or all of the channels listed in a
band. Also, some cards use channels on the 100-GHz ITU grid while others use channels on the 50-GHz ITU
grid. See the specific card description or the “Hardware Specifications” document for more details.
Table 26: DWDM Channel Allocation Plan (C Band)
Channel Number Frequency (THz) Wavelength (nm) Channel Number Frequency (THz) Wavelength (nm)
1 196.00 1529.55 42 193.95 1545.72
2 195.95 1529.94 43 193.90 1546.119
3 195.90 1530.334 44 193.85 1546.518
4 195.85 1530.725 45 193.80 1546.917
5 195.80 1531.116 46 193.75 1547.316
36
6 195.75 1531.507 47 193.70 1547.715
7 195.70 1531.898 48 193.65 1548.115
8 195.65 1532.290 49 193.60 1548.515
9 195.60 1532.681 50 193.55 1548.915
10 195.55 1533.073 51 193.50 1549.32
11 195.50 1533.47 52 193.45 1549.71
12 195.45 1533.86 53 193.40 1550.116
13 195.40 1534.250 54 193.35 1550.517
14 195.35 1534.643 55 193.30 1550.918
15 195.30 1535.036 56 193.25 1551.319
16 195.25 1535.429 57 193.20 1551.721
17 195.20 1535.822 58 193.15 1552.122
18 195.15 1536.216 59 193.10 1552.524
19 195.10 1536.609 60 193.05 1552.926
20 195.05 1537.003 61 193.00 1553.33
21 195.00 1537.40 62 192.95 1553.73
22 194.95 1537.79 63 192.90 1554.134
23 194.90 1538.186 64 192.85 1554.537
24 194.85 1538.581 65 192.80 1554.940
25 194.80 1538.976 66 192.75 1555.343
26 194.75 1539.371 67 192.70 1555.747
27 194.70 1539.766 68 192.65 1556.151
28 194.65 1540.162 69 192.60 1556.555
29 194.60 1540.557 70 192.55 1556.959
30 194.55 1540.953 71 192.50 1557.36
31 194.50 1541.35 72 192.45 1557.77
32 194.45 1541.75 73 192.40 1558.173
33 194.40 1542.142 74 192.35 1558.578
37
34 194.35 1542.539 75 192.30 1558.983
35 194.30 1542.936 76 192.25 1559.389
36 194.25 1543.333 77 192.20 1559.794
37 194.20 1543.730 78 192.15 1560.200
38 194.15 1544.128 79 192.10 1560.606
39 194.10 1544.526 80 192.05 1561.013
40 194.05 1544.924 81 192.00 1561.42
41 194.00 1545.32 82 191.95 1561.83
The following table lists the channel IDs and wavelengths assigned to the L-band channels.
Table 27: DWDM Channel Allocation Plan (L Band)
1 190.85 1570.83 41 188.85 1587.46
2 190.8 1571.24 42 188.8 1587.88
3 190.75 1571.65 43 188.75 1588.30
4 190.7 1572.06 44 188.7 1588.73
5 190.65 1572.48 45 188.65 1589.15
6 190.6 1572.89 46 188.6 1589.57
7 190.55 1573.30 47 188.55 1589.99
8 190.5 1573.71 48 188.5 1590.41
9 190.45 1574.13 49 188.45 1590.83
10 190.4 1574.54 50 188.4 1591.26
11 190.35 1574.95 51 188.35 1591.68
12 190.3 1575.37 52 188.3 1592.10
13 190.25 1575.78 53 188.25 1592.52
14 190.2 1576.20 54 188.2 1592.95
15 190.15 1576.61 55 188.15 1593.37
16 190.1 1577.03 56 188.1 1593.79
38
Safety Labels
17 190.05 1577.44 57 188.05 1594.22
18 190 1577.86 58 188 1594.64
19 189.95 1578.27 59 187.95 1595.06
20 189.9 1578.69 60 187.9 1595.49
21 189.85 1579.10 61 187.85 1595.91
22 189.8 1579.52 62 187.8 1596.34
23 189.75 1579.93 63 187.75 1596.76
24 189.7 1580.35 64 187.7 1597.19
25 189.65 1580.77 65 187.65 1597.62
26 189.6 1581.18 66 187.6 1598.04
27 189.55 1581.60 67 187.55 1598.47
28 189.5 1582.02 68 187.5 1598.89
29 189.45 1582.44 69 187.45 1599.32
30 189.4 1582.85 70 187.4 1599.75
31 189.35 1583.27 71 187.35 1600.17
32 189.3 1583.69 72 187.3 1600.60
33 189.25 1584.11 73 187.25 1601.03
34 189.2 1584.53 74 187.2 1601.46
35 189.15 1584.95 75 187.15 1601.88
36 189.1 1585.36 76 187.1 1602.31
37 189.05 1585.78 77 187.05 1602.74
38 189 1586.20 78 187 1603.17
39 188.95 1586.62 79 186.95 1603.60
40 188.9 1587.04 80 186.9 1604.03
Safety Labels
For information about safety labels, see the 10.1 Safety Labels.
39
32MUX-O Card
32MUX-O Card
The 32MUX-O card has reached end of support.
Note For 32MUX-O card specifications, see the “32MUX-O Card Specifications” section in the
Hardware Specifications document.
The 32-Channel Multiplexer (32MUX-O) card multiplexes 32 100-GHz-spaced channels identified in the
channel plan. The 32MUX-O card takes up two slots in an ONS 15454 and can be installed in Slots 1 to
5 and 12 to 16.
32MUX-O Card Functions

The 32MUX-O card functions include:
Arrayed waveguide grating (AWG) device that enables full multiplexing functions for the channels.
Each single-channel port is equipped with VOAs for automatic optical power regulation prior to
multiplexing. In the case of electrical power failure, the VOA is set to its maximum attenuation for
safety purposes. A manual VOA setting is also available.
Each single-channel port is monitored using a photodiode to enable automatic power regulation.
Card level indicators—
An additional optical monitoring port with 1:99 splitting ratio is available.
Port-Level Indicators for the 32MUX-O Cards

The 32MUX-O card has five sets of ports located on the faceplate. COM TX is the line output. COM MON
is the optical monitoring port. The xx.x to yy.y RX ports represent the four groups of eight channels
ranging from wavelength xx.x to wavelength yy.y, according to the channel plan.
32MUX-O Channel Plan

The 32MUX-O card is typically used in hub nodes and provides the multiplexing of 32 channels, spaced at
100 GHz, into one fiber before their amplification and transmission along the line. The channel plan is
shown in the following table.
Table 28: 32MUX-O Channel Plan
Channel Number Channel ID Frequency (GHz) Wavelength (nm)
1 30.3 195.9 1530.33
2 31.2 195.8 1531.12
3 31.9 195.7 1531.90
4 32.6 195.6 1532.68
40
32MUX-O Channel Plan
Channel Number Channel ID Frequency (GHz) Wavelength (nm)
5 34.2 195.4 1534.25
6 35.0 195.3 1535.04
7 35.8 195.2 1535.82
8 36.6 195.1 1536.61
9 38.1 194.9 1538.19
10 38.9 194.8 1538.98
11 39.7 194.7 1539.77
12 40.5 194.6 1540.56
13 42.1 194.4 1542.14
14 42.9 194.3 1542.94
15 43.7 194.2 1543.73
16 44.5 194.1 1544.53
17 46.1 193.9 1546.12
18 46.9 193.8 1546.92
19 47.7 193.7 1547.72
20 48.5 193.6 1548.51
21 50.1 193.4 1550.12
22 50.9 193.3 1550.92
23 51.7 193.2 1551.72
24 52.5 193.1 1552.52
25 54.1 192.9 1554.13
26 54.9 192.8 1554.94
27 55.7 192.7 1555.75
28 56.5 192.6 1556.55
29 58.1 192.4 1558.17
30 58.9 192.3 1558.98
31 59.7 192.2 1559.79
32 60.6 192.1 1560.61
41
Power Monitoring
Note The Channel Number column is only for reference purposes. The channel ID is consistent with the ONS
15454 and is used in card identification.
Power Monitoring
Physical photodiodes P1 through P32 monitor the power for the 32MUX-O card. The returned power
level values are calibrated to the ports as shown in the following table.
Table 29: 32MUX-O Port Calibration

P1–P32 ADD COM TX
Related Procedures for the 32MUX-O Card

The following is the list of procedures and tasks related to the configuration of the 32MUX-O card:
32DMX-O Card
The 32DMX-O card has reached end of support.
Note For 32DMX-O card specifications, see the “32DMX-O Card Specifications” section in the
The 32-Channel Demultiplexer (32DMX-O) card demultiplexes 32 100-GHz-spaced channels identified in

the channel plan. The 32DMX-O takes up two slots in an ONS 15454 and can be installed in Slots 1 to 5
and 12 to 16.
32DMX-O Card Functions

The 32DMX-O card functions include:
AWG that enables channel demultiplexing functions.
Each single-channel port is equipped with VOAs for automatic optical power regulation after
demultiplexing. In the case of electrical power failure, the VOA is set to its maximum attenuation for
safety purposes. A manual VOA setting is also available.
The 32DXM-O has four physical receive connectors that accept MPO cables on its front panel for the
client input interfaces. MPO cables break out into eight separate cables.
42
Port-Level Indicators for the 32DMX-O Card
Note In contrast, the single-slot 32DMX card does not have VOAs on each drop port
for optical power regulation. The 32DMX optical demultiplexer module is
used in conjunction with the 32WSS card in ONS 15454 Multiservice
Transport Platform (MSTP) nodes.
Each single-channel port is monitored using a photodiode to enable automatic power regulation.
Card level indicators— Table G-4 on page G-9
Port-Level Indicators for the 32DMX-O Card

The 32DMX-O card has five sets of ports located on the faceplate. MON is the output monitor port.
COM RX is the line input. The xx.x to yy.y TX ports represent the four groups of eight channels ranging
from wavelength xx.x to wavelength yy.y according to the channel plan.
Power Monitoring
Physical photodiodes P1 through P33 monitor the power for the 32DMX-O card. The returned power
level values are calibrated to the ports as shown in Table 30: 32DMX-O Port Calibration.
Table 30: 32DMX-O Port Calibration
P1–P32 DROP DROP TX
P33 INPUT COM COM RX
Port Numbers and TL1 Aids” section in Cisco ONS SONET TL1 Command Guide, Release 9.2.1.
Related Procedures for the 32DMX-O Card

The following is the list of procedures and tasks related to the configuration of the 32DMX-O card:
DLP-G353 Preprovisioning a Slot
NTP-G30 Installing the DWDM Cards
NTP-G143 Importing the Cisco Transport Planner NE Update Configuration File
NTP-G34 Installing Fiber-Optic Cables on DWDM Cards and DCUs
NTP-G140 Installing Fiber-Optic Cables Between Terminal, Hub, or ROADM Nodes
DLP-G315 Installing Fiber-Optic Cables From the 32WSS/32DMX Cards to the Standard Patch Panel
Tray
DLP-G356 Installing Fiber-Optic Cables from the 32WSS/32DMX and 32MUX-O/32DMX-O Cards to
the Deep Patch Panel Tray
NTP-G86 Convert a Pass-Through Connection to Add/Drop Connections
43
4MD-xx.x Card
NTP-G44 Performing the Anti-ASE Hub Node Acceptance Test

NTP-G41 Performing the Terminal or Hub Node with 32MUX-O and 32DMX-O Cards Acceptance Test

DLP-G78 Verifying the 32MUX-O or 40-MUX-C Card Power
DLP-G269 Verifying the 32DMX-O or 40-DMX-C Card Power
DLP-G141 View Optical Power Statistics for 32MUX-O, 32WSS, 32WSS-L, 32DMX-O, 32DMX,
32DMX-L, 40-WSS-C, 40-WSS-CE, 40-WXC-C, 80-WXC-C, 16-WXC-FS, 40-MUX-C, 40-DMX-C,
and 40-DMX-CE Cards
NTP-G175 Modifying Line Card Settings and PM Thresholds for Multiplexer and Demultiplexer Cards
DLP-G415 Changing Optical Line Threshold Settings for Multiplexer and Demultiplexer Cards
DLP-G416 Changing Optical Channel Settings for Multiplexer and Demultiplexer Cards
DLP-G417 Changing Optical Channel Threshold Settings for Multiplexer and Demultiplexer Cards
4MD-xx.x Card
The 4MD-xx.x card has reached end of support.
Note For 4MD-xx.x card specifications, see the section “4MD-xx.x Card Specifications” section in the
The 4-Channel Multiplexer/Demultiplexer (4MD-xx.x) card multiplexes and demultiplexes

four 100-GHz-spaced channels identified in the channel plan.
The card is bidirectional. The demultiplexer and multiplexer functions are implemented in two different
sections of the same card. In this way, the same card can manage signals flowing in opposite directions.
There are eight versions of this card that correspond with the eight sub-bands specified in Table 31: 4MD-
xx.x Channel Sets. The 4MD-xx.x can be installed in Slots 1 to 6 and 12 to 17.
4MD-xx.x Card Functions

The 4MD-xx.x has the following functions implemented inside a plug-in optical module:
Passive cascade of interferential filters perform the channel multiplex/demultiplex function.
Software-controlled VOAs at every port of the multiplex section regulate the optical power of each
multiplexed channel.
Software-monitored photodiodes at the input and output multiplexer and demultiplexer ports for power
control and safety purposes.
Software-monitored virtual photodiodes at the common DWDM output and input ports. A virtual
photodiode is a firmware calculation of the optical power at that port. This calculation is based on the
single channel photodiode reading and insertion losses of the appropriated paths.
44
Port-Level Indicators for the 4MD-xx.x Cards
Port-Level Indicators for the 4MD-xx.x Cards

The 4MD-xx.x card has five sets of ports located on the faceplate. COM RX is the line input. COM TX is
the line output. The 15xx.x TX ports represent demultiplexed channel outputs 1 to 4. The 15xx.x RX ports
represent multiplexed channel inputs 1 to 4.
Wavelength Pairs
The following table shows the band IDs and the add/drop channel IDs for the 4MD-xx.x card.
Table 31: 4MD-xx.x Channel Sets
Band ID Add/Drop Channel IDs
Band 30.3 (A) 30.3, 31.2, 31.9, 32.6
Band 34.2 (B) 34.2, 35.0, 35.8, 36.6
Band 38.1 (C) 38.1, 38.9, 39.7, 40.5
Band 42.1 (D) 42.1, 42.9, 43.7, 44.5
Band 46.1 (E) 46.1, 46.9, 47.7, 48.5
Band 50.1 (F) 50.1, 50.9, 51.7, 52.5
Band 54.1 (G) 54.1, 54.9, 55.7, 56.5
Band 58.1 (H) 58.1, 58.9, 59.7, 60.6
Power Monitoring
Physical photodiodes P1 through P8 and virtual photodiodes V1 and V2 monitor the power for the 4MD-
xx.x card. The returned power level values are calibrated to the ports as shown in the following table.
Table 32: 4MD-xx.x Port Calibration
P1–P4 ADD COM TX
V1 OUT COM COM TX
V2 IN COM COM RX
Port Numbers and TL1 Aids” section in Cisco ONS SONET TL1 Command Guide, Release 9.2.1.
45
Related Procedures for the 4MD-xx.x Card
Related Procedures for the 4MD-xx.x Card

The following is the list of procedures and tasks related to the configuration of the 4MD-xx.x card:
DLP-G353 Preprovisioning a Slot
NTP-G143 Importing the Cisco Transport Planner NE Update Configuration File
NTP-G49 Perform the OADM Node Acceptance Test on a Symmetric Node with OSCM Cards
DLP-G94 Verifying Add and Drop Connections on an OADM Node with OSC-CSM Cards
DLP-G315 Installing Fiber-Optic Cables From the 32WSS/32DMX Cards to the Standard Patch Panel
Tray
DLP-G356 Installing Fiber-Optic Cables from the 32WSS/32DMX and 32MUX-O/32DMX-O Cards to
the Deep Patch Panel Tray
NTP-G41 Performing the Terminal or Hub Node with 32MUX-O and 32DMX-O Cards Acceptance Test
NTP-G44 Performing the Anti-ASE Hub Node Acceptance Test

NTP-G86 Convert a Pass-Through Connection to Add/Drop Connections
DLP-G78 Verifying the 32MUX-O or 40-MUX-C Card Power
DLP-G269 Verifying the 32DMX-O or 40-DMX-C Card Power
and 40-DMX-CE Cards
DLP-G414 Changing Optical Line Settings for Multiplexer and Demultiplexer Cards
DLP-G416 Changing Optical Channel Settings for Multiplexer and Demultiplexer Cards
DLP-G417 Changing Optical Channel Threshold Settings for Multiplexer and Demultiplexer Cards
12-AD-FS Card
The 12-AD-FS card is a single slot add/drop card that provides colorless, contentionless, omnidirectional,
and flex spectrum capability on 12 channels over 4 ROADM directions. The card receives the same
wavelength from transponder cards and forwards it to different ROADM nodes without collision. This
capability is achieved using multicast switches.
Each add/drop port pair in the card is:
• Colorless - forwards any wavelength on a specific port
46
16-AD-FS Card
Contentionless - adds/drops the same wavelength from the same add/drop section to different directions
Omnidirectional - connects to both the add and drop directions
The 12-AD-FS card can be installed in any service slots in the Cisco NCS 2006 and NCS 2015 chassis.
The 12-AD-FS card works only in the Cisco NCS Flex node.
Key Features
Integrates three independent add/drop sections that individually support add/drop of up to four channels over
four ROADM directions. The channels can be forwarded to a direction only within the same section.
Provides add/drop sections, each of which has a 4 channel multiplexer and a 4 channel demultiplexer.
Monitors optical power on the input ports through optical photo diodes and raises alarms when the
threshold is exceeded.
Supports tone detection on the input ports in the add direction.
Provides a multicast switch that does not block any wavelength and that does not have any optical
filtering element.
For more information about the 12-AD-FS card, such as the block diagram and card specifications, see
the data sheet.
16-AD-FS Card
The 16-AD-FS card is a single slot add/drop card that provides colorless, contentionless, omnidirectional,
and flex spectrum capability on 16 channels over 4 ROADM directions. The card receives the same
wavelength from 16 transponder cards and forwards it to different ROADM nodes without collision. This
capability is achieved using multicast switches. 2 or 3 16-AD-FS cards can be connected using upgrade
ports to provide the add/drop capability on 16 channels over 8 or 12 ROADM directions respectively.
Each add/drop port pair in the card is:
Colorless - forwards any wavelength on a specific port
Contentionless - adds/drops the same wavelength from the same add/drop section to different directions
Omnidirectional - connects to both the add and drop directions
The 16-AD-FS card can be installed in any service slots in the Cisco NCS 2006 and NCS 2015 chassis.
The 16-AD-FS card works only in the Cisco NCS Flex node.
Key Features
Has a 16x4 multiplexer and a 4x16 demultiplexer.
Monitors optical power on the input ports through optical photo diodes and raises alarms when the
threshold is exceeded.
Supports tone detection on the input ports in the add direction.
Provides a multicast switch that does not block any wavelength and that does not have any optical
filtering element.
47
Related Procedures for the 12-AD-FS and 16-AD-FS Cards
Has fixed gain EDFA amplifiers in the add/drop directions to compensate for high optical insertion loss.
The gain is -1 dB in the drop direction and -2 dB in the add direction.
For more information about the 16-AD-FS card, such as the block diagram and card specifications, see
the data sheet.
Related Procedures for the 12-AD-FS and 16-AD-FS Cards

The following is the list of procedures and tasks related to the configuration of the 12-AD-FS and 16-AD-
FS cards:
DLP-G414 Changing Optical Line Settings for Multiplexer and Demultiplexer Cards
DLP-G781 Switching the Channels for 12-AD-FS and 16-AD-FS Cards
DLP-G479 View Optical Power Statistics for the PSM, 12-AD-FS, and 16-AD-FS Cards
48
CHAPTER 4
Setting Up Tunable Dispersion
Compensating Units
This chapter explains the Tunable Dispersion Compensating Units (T-DCU) used in Cisco ONS 15454
dense wavelength division multiplexing (DWDM) networks.
The T-DCU unit compensates for chromatic dispersion (CD) of the transmission fiber. The T-DCU
provides two line cards with varied set of tunable wavelengths to compensate for CD.
The T-DCU card provides a selectable set of discrete negative chromatic dispersion values to compensate
for chromatic dispersion of the transmission line. The card operates over the entire C-band (in the range of
1529.0 nm to 1562.5 nm) and monitors the optical power at the input and the output ports. The two types of
T-DCU line cards are:
TDC-CC (Coarse T-DCU)
TDC-FC (Fine T-DCU)
Note Each T-DCU card is marked with a symbol that corresponds to a slot (or slots) on the ONS 15454 shelf
assembly. Cards should be installed in slots that have the same symbols. See the “Card Slot
Requirements” section in the Cisco ONS 15454 Hardware Installation Guide.

TDC-CC and TDC-FC Cards, on page 50
Optical Performance, on page 51
Safety Labels
For information about safety labels, see the “G.1.2 Class 1M Laser Product Cards” section on page G-4.
49
Setting Up Tunable Dispersion Compensating Units
TDC-CC and TDC-FC Cards
TDC-CC and TDC-FC Cards

The TDC-CC card provides 16 values of CD ranging from 0 to -1650 ps/nm with a granularity of 110
ps/nm in the C-band spectrum.
The TDC-FC card provides 16 values of CD ranging from 0 to -675 ps/nm with a granularity of 45 ps/nm
in the C-band spectrum.
You can configure the TDC-CC and TDC-FC cards for the CD value listed in the following table.
Table 33: TDC-CC and TDC-FC Tunable CD Value
Unit Configuration TDC-CC [ps/nm] TDC-FC [ps/nm]
0 0 0
1 -110 -45
2 -220 -90
3 -330 -135
4 -440 -180
5 -550 -225
6 -660 -270
7 -770 -315
8 -880 -360
9 -990 -405
10 -1100 -450
11 -1210 -495
12 -1320 -540
13 -1430 -585
14 -1540 -630
15 -1650 -675
Note The default TDC-CC CD value for Coarse Unit is 0. The default TDC-FC value for Fine Unit is 0.
Key Features
The TDC-CC and TDC-FC cards provide these features:
50
Optical Ports
Single slot card with three LEDs on the front panel.

Two LC-PC-II optical connectors on the front panel.
Operates in slots from slot 1 to 6 and 12 to 17.
Operates over the C-band (wavelengths from 1529 nm to 1562.5 nm) of the optical spectrum.
Allows upto 16 provisionable CD values for chromatic dispersion compensation.
Connects to OPT-PRE, OPT-AMP-C, OPT-RAMP-C, and OPT-RAMP-CE amplifiers and 40-SMR-1
and 40-SMR-2 cards.
Supports performance monitoring and alarm handling for selectable thresholds.
Allows monitoring and provisioning using CTC, SNMP, or TL1.
For more information about the TDC-CC and TDC-FC cards, see
http://www.cisco.com/en/US/prod/collateral/optical/ps5724/ps2006/data_sheet_c78-581114.html
Optical Ports
The T-DCU unit contains the DC-RX (input) and DC-TX (output) ports. The optical signal enters the DC-
RX port, compensates the chromatic dispersion and then exits from the DC-TX port.
TDC-CC and TDC-FC Card Functions

The functions of the TDC-CC and TDC-FC cards are:
G.15 Lamp Test, page G-22
Card level indicators— Table G-1 on page G-8
Optical Performance
The TDC-CC and TDC-FC cards monitor the optical input power and optical output power of the fiber. It
monitors the insertion loss from the input (DC-RX) to the output (DC-TX) port, with the help of the two
photodiodes PD1 and PD2. The TDC-CC and TDC-FC cards report the minimum, average, and maximum
power statistics of each of the monitored ports or channels in the specific card. To view the optical power
statistics of the TDC-CC and TDC-FC cards, refer to the Monitor Performance document. The
performance data is recorded at 15 minutes and 24 hours intervals.
Note You can view the performance monitoring (PM) data of the card using CTC, SNMP, and TL1 interfaces.
Note The PM data is stored on a wrap-around basis at 32 x 15 min. and 2 x 24 hour intervals.
51
Related Procedures for TDC-CC and TDC-FC Cards
Related Procedures for TDC-CC and TDC-FC Cards

The following section lists procedures and tasks related to the configuration of the TDC-CC and TDC-
FC cards:
DLP-G525 View Optical Power Statistics for TDC-CC and TDC-FC cards
NTP-G240 Modifying Line Settings and PM Thresholds for the TDC-CC and TDC-FC Cards
NTP-G242 Modify the CD setting of TDC-CC and TDC-FC Cards
52
CHAPTER 5
Provisioning Protection Switching Module
This chapter describes the Protection Switching Module (PSM) card used in Cisco ONS 15454 dense
wavelength division multiplexing (DWDM) networks. For card safety and compliance information, refer to
the Regulatory Compliance and Safety Information for Cisco ONS Platforms document. .
PSM Card, on page 53
PSM Card
The PSM card performs splitter protection functions. In the transmit (TX) section of the PSM card, the signal
received on the common receive port is duplicated by a hardware splitter to both the working and protect
transmit ports. In the receive (RX) section of the PSM card, a switch is provided to select one of the two input
signals (on working and protect receive ports) to be transmitted through the common transmit port.
The PSM card supports multiple protection configurations:
Channel protection—The PSM COM ports are connected to the TXP/MXP trunk ports.
Line (or path) protection—The PSM working (W) and protect (P) ports are connected directly to the
external line.
Multiplex section protection—The PSM is equipped between the MUX/DMX stage and the
amplification stage.
Standalone—The PSM can be equipped in any slot and supports all node configurations.
The PSM card is a single-slot card that can be installed in any node from Slot 1 to 6 and 12 to 17. The
PSM card includes six LC-PC-II optical connectors on the front panel. In channel protection configuration,
the PSM card can be installed in a different shelf from its peer TXP/MXP card.
Note It is strongly recommended that you use the default layouts designed by Cisco Transport Planner, which
place the PSM card and its peer TXP/MXP card as close as possible to simplify cable management.
53
Key Features
Key Features
The PSM card provides the following features:
Operates over the C-band (wavelengths from 1529 nm to 1562.5 nm) and L-band (wavelengths from
1570.5 nm to 1604 nm) of the optical spectrum.
Implements bidirectional non-revertive protection scheme. For more details on bidirectional switching,
see the PSM Bidirectional Switching.
Release 10.5.2 implements bidirectional revertive protection scheme. For more details on bidirectional
switching, see the PSM Bidirectional Switching.
Note PSM reversion is supported only for Optical Channel (OCH) protection and not
supported for Optical Multiplex Section (OMS) and OTS protection.
Release 10.5.2 supports automatic Optical Multiplex Section (OMS) protection when PSM cards are
provisioned with Multiplexers and De-multiplexer cards.
Supports automatic creation of splitter protection group when the PSM card is provisioned.
Supports switching priorities based on ITU-T G.873.1.
Supports performance monitoring and alarm handling with settable thresholds.
Supports automatic laser shutdown (ALS), a safety mechanism used in the event of a fiber cut. ALS is
applicable only in line protection configuration. For information about using the card to implement
ALS in a network, see the .
PSM Card-Level Indicators

Table G-1 "Card-level indicators" describes the card-level indicators on the card.
PSM Bidirectional Switching

A VOA is equipped after the hardware splitter within the PSM card. The VOA implements bidirectional
switching when there is a single fiber cut in a protection configuration involving two peer PSM cards. The
following figure shows a sample configuration that explains the bidirectional switching capability of the
PSM card.
54
PSM Bidirectional Switching
Figure 2: PSM Bidirectional Switching
In this example, there is a fiber cut in the working path from Station A to Station B. As a result of the fiber
cut, an LOS alarm is raised on the W-RX port of Station B and it immediately switches traffic on to its P-
RX port. Station B simultaneously also stops transmission (for approximately 25 milliseconds) on its W-
TX port, which raises an LOS alarm on the W-RX port of Station A. This causes Station A to also switch
traffic to its P-RX port. In this way, PSM implements bidirectional switching without any data exchange
between the two stations.
Because the two stations do not communicate using signaling protocols (overhead bytes), a Manual or Force
protection switch on the PSM card is implemented by creating a traffic hit. For example, consider that you
perform a Manual or Force protection switch on Station A. The TX VOA on the active path is set to automatic
VOA shutdown (AVS) state for 25 milliseconds. This causes Station B to switch traffic to the other path because
it cannot differentiate between a maintenance operation and a real fail. After 25 milliseconds, the VOA in Station
A is automatically reset. Now Station B does not revert back by itself if the non-revertive switching protection
scheme is used in the PSM card. However, if the automatic reversion feature on the PSM card is enabled, Station
B reverts back to the working path once Wait To Restore (WTR) timer is over. For more details on the automatic
reversion feature, see the Automatic PSM Reversion section.
To effectively implement switching, the Lockout and Force commands must be performed on both the
stations. If these commands are not performed on both the stations, the far-end and near-end PSMs can be
misaligned. In case of misalignment, when a path recovers, traffic might not recover automatically. You
might have to perform a Force protection switch to recover traffic.
Note The order in which you repair the paths is important in the event of a double failure (both the working and
protect paths are down due to a fiber cut) on the PSM card in line protection configuration when the
active path is the working path. If you repair the working path first, traffic is automatically restored.
However, if you repair the protect path first, traffic is not automatically restored. You must perform a
Force protection switch to restore traffic on the protect path.
55
Automatic PSM Reversion
Automatic PSM Reversion

From Release 10.5.2, the PSM cards support automatic bidirectional switching. When the fault on the working
path clears, traffic automatically switches from the protection path to the working path. The reversion takes place
after the Wait To Restore (WTR) timer is over. The key features of automatic PSM reversion are:
Only normal and standalone modes of PSM card support automatic reversion.
Protection cannot be provisioned as revertive if automatic laser shutdown (ALS) is enabled in
standalone mode, and vice versa.
Revertive feature is supported for only OCH protection.
By default, the protection in PSM is non-revertive. To enable the revertive feature, perform step 4 of
DLP-G176 Modify a Splitter Protection Group.
Reversion parameters that include revertive/non-revertive protection, WTR, pulse width, and interval
can be configured only when the working path is active.
WTR time can be set to a duration between 30 seconds to 12 minutes and is configurable only if the
protection is revertive. By default, the timer is set to five minutes.
Reversion Pulse Width is between 10 to 200 seconds and is configurable only if the protection is
revertive. By default, the duration is set to 60 seconds. This parameter value can be calculated using
the following formula:
Minimum reversion pulse width = ROADM delay + 10 seconds
ROADM delay = N x 5 x 2
N=number of filter cards in the network between the source and destination PSM nodes on the
working path.
5 = maximum startup delay in seconds
2=bidirectional communication
For example, if a network has four ROADM nodes with the end nodes having PSM cards on the
working path as depicted below:
[PSM - Node 1 - FILTER 1 ] ==== [FILTER 2 - Node 2 - FILTER 3 ] ==== [FILTER 4 - Node 3
- FILTER 5 ] ==== [FILTER 6 - Node 4 - PSM]
then N = 6
ROADM delay = 6 x 5 x 2= 60
Minimum reversion pulse width = 60 + 10 = 70 seconds
Recovery Pulse Interval for reversion is auto-calculated and the user cannot configure the thresholds.
Related Procedures for PSM Card

The following is the list of procedures and tasks related to the configuration of the PSM card:
NTP-G202 Modify PSM Card Line Settings and PM Thresholds
56
NTP-G242 Create an Internal Patchcord Manually

DLP-G493 Provision Protected Optical Channel Network Connections
DLP-G479 View Optical Power Statistics for the PSM Card
DLP-G176 Modify a Splitter Protection Group
DLP-G459 Delete a Splitter Protection Group
57
58
CHAPTER 6
Provisioning Optical Add/Drop Cards
This chapter describes optical add/drop cards used in Cisco ONS 15454 dense wavelength division
multiplexing (DWDM) networks. For card safety and compliance information, refer to the Regulatory
Compliance and Safety Information for Cisco ONS Products document.
Note The cards described in this chapter are supported on the Cisco ONS 15454, Cisco ONS 15454 M6, Cisco
ONS 15454 M2 platforms, unless noted otherwise.
Chapter topics include:

Card Overview, on page 59
AD-1C-xx.x, AD-2C-xx.x, and AD-4C-xx.x Cards, on page 62
AD-1B-xx.x and AD-4B-xx.x Cards, on page 65
Safety Labels
For information about safety labels, see the section, Class 1M Laser Product Cards .
Card Overview
The card overview section contains card overview, software compatibility, and channel allocation
information for optical add/drop cards.
Optical add/drop cards are divided into two groups:
Band optical add/drop multiplexer (OADM) cards
Channel OADM cards
59
Card Compatibility
Band OADM cards add and drop one or four bands of adjacent channels. The cards in this chapter, including the
4-Band OADM (AD-4B-xx.x) and the 1-Band OADM (AD-1B-xx.x) are utilized only in the C band.
Channel OADM cards add and drop one, two, or four adjacent channels; they include the 4-Channel
OADM (AD-4C-xx.x), the 2-Channel OADM (AD-2C-xx.x), and the 1-Channel OADM (AD-1C-xx.x).
Card Compatibility
The following table lists the CTC software compatibility for each optical add/drop card.
Table 34: Software Release Compatibility for Optical Add/Drop Cards
Card R4.5 - R9.1 R9.2 - R9.8 R10.0 R10.5 R10.5.2 R10.6.1 R10.6.2 R10.7
Name /R10.1/R10.3
AD-1C-xx.x 15454 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2,

-DWDM 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6,
15454 15454 15454 15454 15454 15454 15454
-DWDM -DWDM -DWDM -DWDM -DWDM -DWDM -DWDM
AD-2C-xx.x 15454 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2,

-DWDM 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6,
15454-DWDM 15454 15454 15454 15454 15454-DWDM 15454-DWDM
-DWDM -DWDM -DWDM -DWDM
AD-4C-xx.x 15454 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2,
-DWDM 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6,
15454 15454 15454 15454 15454 15454 15454
-DWDM -DWDM -DWDM -DWDM -DWDM -DWDM -DWDM
AD-1B-xx.x 15454 15454 15454 15454 15454 15454 15454 15454

-DWDM -DWDM -DWDM -DWDM -DWDM -DWDM -DWDM -DWDM
AD-4B-xx.x 15454 15454 15454 15454 15454 15454 15454 15454

DWDM Card Channel Allocation Plan

ONS 15454 DWDM channel OADM and band OADM cards are designed for use with specific channels in
the C band. In most cases, the channels for these cards are either numbered (for example, 1 to 32) or
delimited (odd or even). Client interfaces must comply with these channel assignments to be compatible
with the ONS 15454 system.
Table 35: DWDM Channel Allocation Plan (C Band) lists the channel IDs and wavelengths assigned to
the C-band DWDM channels.
Note In some cases, a card uses only some or all of the channels listed in a band. Also, some cards use channels
on the 100-GHz ITU-T grid while others use channels on the 50-GHz ITU-T grid.
60
DWDM Card Channel Allocation Plan
Table 35: DWDM Channel Allocation Plan (C Band)
1 196.00 1529.55 42 193.95 1545.72
2 195.95 1529.94 43 193.90 1546.119
3 195.90 1530.334 44 193.85 1546.518
4 195.85 1530.725 45 193.80 1546.917
5 195.80 1531.116 46 193.75 1547.316
6 195.75 1531.507 47 193.70 1547.715
7 195.70 1531.898 48 193.65 1548.115
8 195.65 1532.290 49 193.60 1548.515
9 195.60 1532.681 50 193.55 1548.915
10 195.55 1533.073 51 193.50 1549.32
11 195.50 1533.47 52 193.45 1549.71
12 195.45 1533.86 53 193.40 1550.116
13 195.40 1534.250 54 193.35 1550.517
14 195.35 1534.643 55 193.30 1550.918
15 195.30 1535.036 56 193.25 1551.319
16 195.25 1535.429 57 193.20 1551.721
17 195.20 1535.822 58 193.15 1552.122
18 195.15 1536.216 59 193.10 1552.524
19 195.10 1536.609 60 193.05 1552.926
20 195.05 1537.003 61 193.00 1553.33
21 195.00 1537.40 62 192.95 1553.73
22 194.95 1537.79 63 192.90 1554.134
23 194.90 1538.186 64 192.85 1554.537
24 194.85 1538.581 65 192.80 1554.940
25 194.80 1538.976 66 192.75 1555.343
26 194.75 1539.371 67 192.70 1555.747
27 194.70 1539.766 68 192.65 1556.151
61
AD-1C-xx.x, AD-2C-xx.x, and AD-4C-xx.x Cards
28 194.65 1540.162 69 192.60 1556.555
29 194.60 1540.557 70 192.55 1556.959
30 194.55 1540.953 71 192.50 1557.36
31 194.50 1541.35 72 192.45 1557.77
32 194.45 1541.75 73 192.40 1558.173
33 194.40 1542.142 74 192.35 1558.578
34 194.35 1542.539 75 192.30 1558.983
35 194.30 1542.936 76 192.25 1559.389
36 194.25 1543.333 77 192.20 1559.794
37 194.20 1543.730 78 192.15 1560.200
38 194.15 1544.128 79 192.10 1560.606
39 194.10 1544.526 80 192.05 1561.013
40 194.05 1544.924 81 192.00 1561.42
41 194.00 1545.32 82 191.95 1561.83
AD-1C-xx.x, AD-2C-xx.x, and AD-4C-xx.x Cards

AD-1C-xx.x Card
The AD-1C-xx.x card has reached end of support.
The 1-Channel OADM (AD-1C-xx.x) card passively adds or drops one of the 32 channels utilized within
the 100-GHz-spacing of the DWDM card system. Thirty-two versions of this card—each designed only for
use with one wavelength—are used in the ONS 15454 DWDM system. Each wavelength version of the
card has a different part number.
The features of the AD-1C-xx.x card are listed in the section, "Features of AD-1C-xx.x, AD-2C-xx.x,
and AD-4C-xx.x Cards".
For more information about the AD-1C-xx.x card, see
AD-2C-xx.x Card
62
AD-4C-xx.x Card
The 2-Channel OADM (AD-2C-xx.x) card passively adds or drops two adjacent 100-GHz channels within the
same band. Sixteen versions of this card—each designed for use with one pair of wavelengths—are used in the
ONS 15454 DWDM system. The card bidirectionally adds and drops in two different sections on the same card
to manage signal flow in both directions. Each version of the card has a different part number.
AD-4C-xx.x Card
The 4-Channel OADM (AD-4C-xx.x) card passively adds or drops all four 100-GHz-spaced channels
within the same band. Eight versions of this card—each designed for use with one band of wavelengths—
are used in the ONS 15454 DWDM system. The card bidirectionally adds and drops in two different
sections on the same card to manage signal flow in both directions. There are eight versions of this card
with eight part numbers.
Features of AD-1C-xx.x, AD-2C-xx.x, and AD-4C-xx.x Cards

The AD-1C-xx.x, AD-2C-xx.x, and AD-4C-xx.x cards have the following features:
Passive cascaded optical interferential filters perform the channel add and drop functions.
Software-controlled variable optical attenuators (VOA) regulate the optical power of the inserted channel.
Software-controlled VOA regulate the insertion loss of the express optical path.
VOA settings and functions, photodiode detection, and alarm thresholds, are internally controlled.
Virtual photodiodes (firmware calculations of port optical power) at the common DWDM output and
input ports are monitored within the software.
Power Monitoring
Physical photodiodes P1 through P4 and virtual photodiodes V1 and V2 monitor the power for the AD-1C-
Table 36: AD-1C-xx.x Port Calibration
P1 ADD DROP RX
P2 DROP DROP TX
63
Related Procedures for AD-1C-xx.x, AD-2C-xx.x, and AD-4C-xx.x Cards
P3 IN EXP EXP RX
P4 OUT EXP EXP TX
V1 IN COM COM RX
V2 OUT COM COM TX
Physical photodiodes P1 through P10 and virtual photodiodes V1 and V2 monitor the power for the AD-
2C-xx.x card. The returned power level values are calibrated to the ports as shown in the following table.
P1–P2 ADD COM TX
P5 IN EXP EXP RX
P6 OUT EXP EXP TX
V1 IN COM COM RX
V2 OUT COM COM TX
Physical photodiodes P1 through P10 and virtual photodiodes V1 and V2 monitor the power for the AD-
4C-xx.x card. The returned power level values are calibrated to the ports as shown in the following table.
P1–P4 ADD COM TX
P9 IN EXP EXP RX
P10 OUT EXP EXP TX
V1 IN COM COM RX
V2 OUT COM COM TX
Related Procedures for AD-1C-xx.x, AD-2C-xx.x, and AD-4C-xx.x Cards

64
AD-1B-xx.x and AD-4B-xx.x Cards
NTP-G37 Running Automatic Node Setup

NTP-G59 Creating, Deleting, and Managing Optical Channel Network Connections
NTP-G106 Resetting Cards Using CTC
NTP-G119 Powering Down the Node
AD-1B-xx.x and AD-4B-xx.x Cards

AD-1B-xx.x Card
The AD-1B-xx.x card has reached end of support.
The 1-Band OADM (AD-1B-xx.x) card passively adds or drops a single band of four adjacent 100-GHz-
spaced channels. Eight versions of this card with eight different part numbers—each version designed for
use with one band of wavelengths—are used in the ONS 15454 DWDM system. The card bidirectionally
adds and drops in two different sections on the same card to manage signal flow in both directions. This
card can be used when there is asymmetric adding and dropping on each side (east or west) of the node; a
band can be added or dropped on one side but not on the other.
The features of the AD-1B-xx.x card are listed in the section, "Features of AD-1B-xx.x and AD-4B-
xx.x Cards".
For more information about the AD-1B-xx.x card, see
AD-4B-xx.x Card
The AD-4B-xx.x card has reached end of support.
The 4-Band OADM (AD-4B-xx.x) card passively adds or drops four bands of four adjacent 100-GHz-
spaced channels. Two versions of this card with different part numbers—each version designed for use
with one set of bands—are used in the ONS 15454 DWDM system. The card bidirectionally adds and
drops in two different sections on the same card to manage signal flow in both directions. This card can be
used when there is asymmetric adding and dropping on each side (east or west) of the node; a band can be
added or dropped on one side but not on the other.
The features of the AD-4B-xx.x card are listed in the section, "Features of AD-1B-xx.x and AD-4B-
xx.x Cards".
For more information about the AD-4B-xx.x card, see
65
Features of AD-1B-xx.x and AD-4B-xx.x Cards
Features of AD-1B-xx.x and AD-4B-xx.x Cards

The AD-1B-xx.x and AD-4B-xx.x cards have the following features:
Software-controlled VOAs regulate the optical power flowing in the OADM paths.
Output power of the dropped band is set by changing the attenuation of the VOA drop.
The VOA express is used to regulate the insertion loss of the express path.
VOA settings and functions, photodiode detection, and alarm thresholds are internally controlled.
Software-monitored virtual photodiodes (firmware calculation of port optical power) at the common
DWDM output and input ports.
Note The AD-4B-xx.x card has only one virtual photodiode at the common DWDM
output port.
Power Monitoring
Physical photodiodes P1 through P4 and virtual photodiodes V1 and V2 monitor the power for the AD-1B-
Table 39: AD-1B-xx.x Port Calibration
P1 ADD BAND RX
P2 DROP BAND TX
P3 IN EXP EXP RX
P4 OUT EXP EXP TX
V1 IN COM COM RX
V2 OUT COM COM TX
Physical photodiodes P1 through P11 and virtual photodiode V1 monitor the power for the AD-4B-xx.x card.
The returned power level values are calibrated to the ports as shown in the following table.
Table 40: AD-4B-xx.x Port Calibration
P1–P4 ADD COM TX
P9 IN EXP EXP RX
P10 OUT EXP EXP TX
66
Related Procedures for AD-1B-xx.x and AD-4B-xx.x Cards
P11 IN COM COM RX
V1 OUT COM COM TX

NTP-G106 Resetting Cards Using CTC
NTP-G119 Powering Down the Node
67
68
CHAPTER 7
Provisioning Reconfigurable Optical
Add/Drop Cards
This chapter describes the line cards deployed in reconfigurable optical add/drop (ROADM) networks.
These cards perform mesh topology functions.
Note The cards described in this chapter are supported on the Cisco ONS 15454, Cisco ONS 15454 M6,
Cisco ONS 15454 M2 platforms, unless noted otherwise.
Card Compatibility, on page 69

Channel Allocation Plans, on page 71
32WSS and 32WSS-L Cards, on page 74
32DMX and 32DMX-L Cards, on page 79
40-DMX-C and 40-DMX-CE Card, on page 81
40-MUX-C Card, on page 86
40-WSS-C and 40-WSS-CE Card, on page 88
40-WXC-C Card, on page 91
80-WXC-C Card, on page 94
16-WXC-FS Card, on page 102
Single Module ROADM (SMR-C) Cards, on page 106
MMU Card, on page 119
Card Compatibility
The following table lists the Cisco Transport Controller (CTC) software compatibility for the ROADM cards.
69
Provisioning Reconfigurable Optical Add/Drop Cards
Card Compatibility
Table 41: Software Release Compatibility for ROADM Cards
Card R4.7 - R7.0 R8.0 - R9.1 R9.2 - R9.8 R10.0 R10.5 R10.5.2 R10.6.1
Name R6.0 -R7.2 R9.0 /10.1/10.3 /R10.6.2/R10.7/10.8/10.9
32WSS 15454 15454 15454 15454 15454 15454 15454 15454 15454
-DWDM -DWDM -DWDM -DWDM -DWDM -DWDM -DWDM , -DWDM , -DWDM ,
, , 15454-M6 15454-M6 15454-M6
15454-M6 15454-M6
32WSS No 15454 15454 15454 15454 15454 15454 15454 15454

-L -DWDM -DWDM -DWDM -DWDM -DWDM -DWDM -DWDM -DWDM
40 No No 15454 15454 15454 15454-M6, 15454-M6, 15454-M6, 15454-M6,

-WSS -DWDM -DWDM -M6, 15454 15454 15454 15454
-C 15454-DWDM -DWDM -DWDM -DWDM -DWDM
40 No No 15454 15454 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6,

-WSS -DWDM -DWDM 15454 15454 15454 15454 15454
-CE -DWDM -DWDM -DWDM -DWDM -DWDM
32 15454 15454 15454 15454 15454 15454 15454 15454 15454

DMX -DWDM -DWDM -DWDM -DWDM -DWDM -DWDM -DWDM , -DWDM , -DWDM ,
, , 15454-M6 15454-M6 15454-M6
15454-M6 15454-M6
32 No 15454 15454 15454 15454 15454 15454 15454 15454

DMX -DWDM -DWDM -DWDM -DWDM -DWDM -DWDM -DWDM -DWDM
-L
40 No No 15454 15454 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6,

-DMX -DWDM -DWDM 15454 15454 15454 15454 15454
-C -DWDM -DWDM -DWDM -DWDM -DWDM
40 No No 15454 15454 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6,

-DMX -DWDM -DWDM 15454 15454 15454 15454 15454
-CE -DWDM -DWDM -DWDM -DWDM -DWDM
40 No No 15454 15454 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6,

-MUX -DWDM -DWDM 15454 15454 15454 15454 15454
40 No No 15454 15454 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6,

-WXC -DWDM -DWDM 15454 15454 15454 15454 15454
80 No No No No 15454-M6, 15454-M6, 15454-M6, 15454 15454

-WXC 15454 15454 15454-DWDM -DWDM, -DWDM,
-C -DWDM -DWDM 15454 15454-M6,
-M6, NCS NCS 2015
2015
70
Channel Allocation Plans
Card R4.7 - R7.0 R8.0 - R9.1 R9.2 - R9.8 R10.0 R10.5 R10.5.2 R10.6.1
Name R6.0 -R7.2 R9.0 /10.1/10.3 /R10.6.2/R10.7/10.8/10.9
16 No No No No No 15454-M6 15454-M6, 15454-M6, 15454-M6,

-WXC NCS 2015 NCS 2015 NCS 2015
-FS
40 No No No 15454 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2,

-SMR1 -DWDM 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6,
-C 15454 15454 15454 15454 15454
-DWDM -DWDM -DWDM -DWDM -DWDM
40 No No No 15454 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2,

-SMR2 -DWDM 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6,
-C 15454 15454 15454 15454 15454
-DWDM -DWDM -DWDM -DWDM -DWDM
MMU No 15454 15454 15454 15454 15454 15454 15454 15454

17 No No No No No No 15454 15454-M2, 15454-M2,

SMR9 -M2, 15454-M6, 15454-M6,
FS, 24 15454 NCS 2015 NCS 2015
SMR9 -M6, NCS
FS, 34 2015
SMR9
FS,
SMR20
FS,
SMR20
FS CV
12-AD-FS, No No No No No No 15454 15454-M2, 15454-M2,

16-AD-FS -M2, 15454-M6, 15454-M6,
15454 NCS 2015 NCS 2015
-M6, NCS
2015

ROADM cards are designed for use with specific channels in the C band and L band. In most cases, the channels
for these cards are either numbered (for example, 1 to 32 or 1 to 40) or delimited (odd or even). Client interfaces
must comply with these channel assignments to be compatible with the ONS 15454 system.
The following cards operate in the C-band:
32WSS
32DMX
32DMX-C
71
40-MUX-C
40-WXC-C
80-WXC-C
40-SMR1-C
40-SMR2-C
MMU
The following add drop cards utilize the L-band DWDM channels:
32WSS-L
32DMX-L
Table 42: DWDM L-band Channel Allocation Plan at 50 GHz Spacing, on page 72 lists the L-band
channel IDs and wavelengths at ITU-T 50-GHz intervals. This is a comprehensive L-band channel table
that encompasses present and future card capabilities.
Table 42: DWDM L-band Channel Allocation Plan at 50 GHz Spacing
Channel Frequency Wavelength Channel Frequency Wavelength

1
Number (THz) (nm) Number (THz) (nm)
1 190.85 1570.83 41 188.85 1587.46
2 190.8 1571.24 42 188.8 1587.88
3 190.75 1571.65 43 188.75 1588.30
4 190.7 1572.06 44 188.7 1588.73
5 190.65 1572.48 45 188.65 1589.15
6 190.6 1572.89 46 188.6 1589.57
7 190.55 1573.30 47 188.55 1589.99
8 190.5 1573.71 48 188.5 1590.41
9 190.45 1574.13 49 188.45 1590.83
10 190.4 1574.54 50 188.4 1591.26
11 190.35 1574.95 51 188.35 1591.68
12 190.3 1575.37 52 188.3 1592.10
13 190.25 1575.78 53 188.25 1592.52
14 190.2 1576.20 54 188.2 1592.95
15 190.15 1576.61 55 188.15 1593.37
16 190.1 1577.03 56 188.1 1593.79
72
Channel Frequency Wavelength Channel Frequency Wavelength

1
Number (THz) (nm) Number (THz) (nm)
17 190.05 1577.44 57 188.05 1594.22
18 190 1577.86 58 188 1594.64
19 189.95 1578.27 59 187.95 1595.06
20 189.9 1578.69 60 187.9 1595.49
21 189.85 1579.10 61 187.85 1595.91
22 189.8 1579.52 62 187.8 1596.34
23 189.75 1579.93 63 187.75 1596.76
24 189.7 1580.35 64 187.7 1597.19
25 189.65 1580.77 65 187.65 1597.62
26 189.6 1581.18 66 187.6 1598.04
27 189.55 1581.60 67 187.55 1598.47
28 189.5 1582.02 68 187.5 1598.89
29 189.45 1582.44 69 187.45 1599.32
30 189.4 1582.85 70 187.4 1599.75
31 189.35 1583.27 71 187.35 1600.17
32 189.3 1583.69 72 187.3 1600.60
33 189.25 1584.11 73 187.25 1601.03
34 189.2 1584.53 74 187.2 1601.46
35 189.15 1584.95 75 187.15 1601.88
36 189.1 1585.36 76 187.1 1602.31
37 189.05 1585.78 77 187.05 1602.74
38 189 1586.20 78 187 1603.17
39 188.95 1586.62 79 186.95 1603.60
40 188.9 1587.04 80 186.9 1604.03
Channels on the L-band are contiguous, starting at 1577.86 nm. The channels listed in this table begin
with 1570.83 nm for backward compatibility with other ONS products.
73
Safety Labels
Safety Labels
For information about safety labels, see the section, Class 1M Laser Product Cards.
32WSS and 32WSS-L Cards

The two-slot 32-Channel Wavelength Selective Switch (32WSS) and 32-Channel Wavelength Selective
Switch L-Band (32WSS-L) cards perform channel add/drop processing within the DWDM node. The
32WSS or 32WSS-L card can be installed in the following pairs of slots:
Slots 1 and 2
Slots 3 and 4
Slots 5 and 6
Slots 12 and 13
Slots 14 and 15
Slots 16 and 17
The 32WSS or 32WSS-L cards has six types of ports:

ADD RX ports (1 to 32): These ports are used for adding channels (listed in Table 44: Channel Allocation
Plan, on page 76 or Table 45: Channel Allocation Plan, on page 77). Each add channel is associated
with an individual switch element that selects whether that channel is added. Each add port has optical
power regulation provided by a variable optical attenuator (VOA). The 32WSS has four physical
receive connectors that accept multifiber push-on (MPO) cables on its front panel for the client input
interfaces. Each MPO cable breaks out into eight separate cables.
EXP RX port: The EXP RX port receives an optical signal from another 32WSS card in the same
network element (NE).
EXP TX port: The EXP TX port sends an optical signal to the other 32WSS card within the NE.
COM TX port: The COM TX (line input) port sends an aggregate optical signal to a booster amplifier
card (for example, OPT-BST) for transmission outside of the NE.
COM RX port: The COM RX port receives the optical signal from a preamplifier (such as the OPT-
PRE) and sends it to the optical splitter.
DROP TX port: The DROP TX port sends the split-off optical signal containing drop channels to the
32DMX card, where the channels are further processed and dropped.
Aggregate optical signals that enter the EXP RX and COM RX port are processed in two ways:
EXP RX Port Add Channel/Pass-through Processing
The incoming optical signal is received at the EXP RX port from the other 32WSS card within the NE.
The incoming aggregate optical signal is demultiplexed into 32 individual wavelengths, or channels.
Each channel is then individually processed by the optical switch, which performs add/pass-through
74
32WSS and 32WSS-L ROADM Functionality
processing. By using software controls, the switch either selects the optical channel coming in from
the demultiplexer (that is, the pass-through channel) or it selects the external ADD channel. If the
ADD port channel is selected this channel is transmitted and the optical signal coming from the
demultiplexer is blocked.
After the optical switch stage, all of the channels are multiplexed into an aggregate optical signal, which is
sent out on the COM TX port. The output is typically connected to an OPT-AMP-L or OPT-BST-E card (in
the event a booster amplifier is needed) or to an OSC-CSM card (if no amplification is needed).
COM RX Port Optical Splitter Processing
The COM RX port receives the incoming optical signal and directs it to the 32WSS card’s optical splitter.
The splitter optically diverts channels that are designated to be dropped to the DROP TX port. The DROP
TX port is typically connected to the COM RX port of the 32DMX where the drop channels are being
dropped. Channels that are not dropped pass-through the optical splitter and flow out of the 32WSS card
EXP TX port. Typically, this optical signal is connected to the other 32WSS module within the NE.
The COM TX value can be measured by either a physical or a virtual photodiode of the 32WSS card. If the
vendor ID of the 32WSS card is between 1024 (0x400) and 2047 (0x800) the COM TX value is measured by
physical photodiode. If the vendor ID of the 32WSS card is greater than 2048 (0x800), the COM TX value is
measured by the virtual photodiode. For COM TX values measured by virtual photodiode, check the values at the
RX port in the downstream of the COM TX port (COM-RX port on OPT-BST or OSC-CSM card).
For more information about the 32WSS or 32WSS-L card, see
http://www.cisco.com/en/US/prod/collateral/optical/ps5724/ps2006/ps5320/product_data_sheet0900aecd803fc52f.html.
32WSS and 32WSS-L ROADM Functionality

To implement ROADM functionality, the 32WSS (or 32WSS-L) card works in combination with the
32DMX (or 32DMX-L) card. As a ROADM node, the node can be configured to add or drop individual
optical channels using CTC, Cisco Transport Planner, and Cisco Transport Manager (CTM). ROADM
functionality using the 32WSS (or 32WSS-L) card requires two 32DMX (or 32DMX-L) single-slot cards
and two 32WSS (or 32WSS-L) double-slot cards (totalling six slots needed in the chassis).
For other cards’ ROADM functionality, see that card’s description in this chapter. For a diagram of a
typical ROADM configuration, see the section, ROADM Node in the Cisco ONS 15454 DWDM Network
Operations Guide.
Note A terminal site can be configured using only a 32WSS (or 32WSS-L) card and a 32DMX (or 32DMX-L)
card plugged into the east or west side of the shelf.
32WSS and 32 WSS-L Power Monitoring

Physical photodiodes P1 through P69 monitor the power for the 32WSS or 32WSS-L card. The
following table shows how the returned power level values are calibrated to each port.
Table 43: 32WSS or 32WSS-L Port Calibration
P1–P32 ADD (Power ADD) ADD RX
75
32WSS and 32WSS-L Channel Allocation Plan
P33–P64 PASS THROUGH COM TX

2
ADD (Power) COM TX
P65 OUT EXP EXP TX
P66 IN EXP EXP RX
P67 OUT COM COM TX
P68 IN COM COM RX
P69 DROP DROP TX

P33–P64 monitor either ADD or PASSTHROUGH power, depending on the state of the optical switch

The 32WSS card’s channel labels, frequencies, and wavelengths are listed in the following table.
Table 44: Channel Allocation Plan
Band ID Channel Label Frequency (THz) Wavelength (nm)
B30.3 30.3 195.9 1530.33
31.1 195.8 1531.12
31.9 195.7 1531.90
32.6 195.6 1532.68
B34.2 34.2 195.4 1534.25
35.0 195.3 1535.04
35.8 195.2 1535.82
36.1 195.1 1536.61
B38.1 38.1 194.9 1538.19
38.9 194.8 1538.87
39.7 194.7 1539.77
40.5 194.6 1540.46
76
B42.1 42.1 194.4 1542.14
42.9 194.3 1542.94
43.7 194.2 1543.73
44.5 194.1 1544.53
B46.1 46.1 193.9 1546.12
46.9 193.8 1546.92
47.7 193.7 1547.72
48.5 193.6 1548.51
B50.1 50.1 193.4 1550.12
50.9 193.3 1550.92
51.7 193.2 1551.72
52.5 193.1 1552.52
B54.1 54.1 192.9 1554.13
54.9 192.8 1554.94
55.7 192.7 1555.75
56.5 192.6 1556.55
B58.1 58.1 192.4 1558.17
58.9 192.3 1558.98
59.7 192.2 1559.79
60.6 192.1 1560.61
The 32WSS-L card uses 32 banded channels on the ITU-T 100-GHz grid, as shown in the following table.
B77.8 77.8 190 1577.86
78.6 189.9 1578.69
79.5 189.8 1579.52
80.3 189.7 1580.35
77
B81.1 81.1 189.6 1581.18
82.0 189.5 1582.02
82.8 189.4 1582.85
83.6 189.3 1583.69
B84.5 84.5 189.2 1584.53
85.3 189.1 1585.36
86.2 189 1586.20
87.0 188.9 1587.04
B87.8 87.8 188.8 1587.88
88.7 188.7 1588.73
89.5 188.6 1589.57
90.4 188.5 1590.41
B91.2 91.2 188.4 591.26
92.1 188.3 1592.10
92.9 188.2 1592.95
93.7 188.1 1593.79
B94.6 94.6 188 1594.64
95.4 187.9 1595.49
96.3 187.8 1596.34
97.1 187.7 1597.19
B98.0 98.0 187.6 1598.04
98.8 187.5 1598.89
99.7 187.4 1599.75
00.6 187.3 1600.60
B01.4 01.4 187.2 1601.46
02.3 187.1 1602.31
03.1 187 1603.17
04.0 186.9 1604.03
78
Related Procedures for 32WSS and 32WSS-L Cards
Related Procedures for 32WSS and 32WSS-L Cards

The following section lists procedures and tasks related to the configuration of the 32WSS or 32WSS-L cards:
NTP-G152 Creating and Verifying Internal Patchcords
and 40-DMX-CE Cards
NTP-G93 Modifying the WSS Card Line Settings and PM Thresholds
32DMX and 32DMX-L Cards

The single-slot 32-channel demultiplexer (32DMX) or the 32-channel demultiplexer L-band (32DMX-L)
card is an optical demultiplexer. The card receives an aggregate optical signal on its COM RX port and
demultiplexes it into to (32) ITU-T 100-GHz-spaced channels. The 32DMX or 32DMX-L card can be
installed in Slots 1 to 6 and in Slots 12 to 17. The 32DMX-L card is particularly well suited for use in
networks that employ DS fiber or SMF-28 single-mode fiber.
The 32DMX or 32DMX-L card has two types of ports:
COM RX port: COM RX is the input port for the aggregate optical signal being demultiplexed. This port is
supported by a VOA for optical power regulation and a photodiode for optical power monitoring.
DROP TX ports (1 to 32): On its output, the 32DMX provides 32 drop ports that are typically used for
dropping channels within the ROADM node. These ports are connected using four 8-fiber MPO
ribbon connectors. The incoming optical signal to the demultiplexer comes into the COM RX port.
This input port is connected using a single LC duplex optical connector. Each drop port has a
photodiode for optical power monitoring. Unlike the two-slot 32DMX-O demultiplexer, the drop ports
on the 32DMX do not have a VOA per channel for optical power regulation.
For more information about the 32DMX or 32DMX-L card, see

http://www.cisco.com/en/US/prod/collateral/optical/ps5724/ps2006/ps5320/product_data_sheet0900aecd803fc52f.html.
32DMX and 32DMX-L ROADM Functionality

The 32DMX (or 32DMX-L) card works in combination with the 32WSS (or 32WSS-L) card to implement
ROADM functionality. As a ROADM node, the node can be configured to add or drop individual optical
channels using CTC, Cisco Transport Planner, and CTM. ROADM functionality using the 32DMX (or
32DMX-L) card requires two 32DMX (or 32DMX-L) single-slot cards and two 32WSS (or 32WSS-L)
double-slot cards (for six slots total in the chassis).
79
32DMX and 32DMX-L Power Monitoring
For information about the ROADM functionality for other cards, see that card’s description in this chapter.
For a diagram of a typical ROADM configuration, see the section, ROADM Node in the Cisco ONS
15454 DWDM Network Operations Guide.
Note A terminal site can be configured using only a 32WSS (or 32WSS-L) card and a 32DMX or 32WSS-L)
card plugged into the east or west side of the shelf.
32DMX and 32DMX-L Power Monitoring

Physical photodiodes P1 through P33 monitor the power for the 32DMX or 32DMX-L card. The
returned power level values are calibrated to the ports as shown in following table.
Table 46: 32DMX or 32DMX-L Port Calibration
32DMX and 32DMX-L Channel Allocation Plan

The 32DMX card’s channel labels, frequencies, and wavelengths are listed in Table 44: Channel
Allocation Plan, on page 76.
The 32DMX-L card uses 32 banded channels on the ITU-T 100-GHz grid, as shown in Table 45:
Channel Allocation Plan, on page 77.
Related Procedures for 32DMX and 32DMX-L Cards

The following section lists procedures and tasks related to the configuration of the 32DMX or 32DMX-
L cards:
and 40-DMX-CE Cards
80
40-DMX-C and 40-DMX-CE Card
40-DMX-C and 40-DMX-CE Card

(Cisco ONS 15454 and ONS 15454 M6 only)
El demultiplexor de 40 canales de ranura única banda C (40-DMX-C) o ranura única demultiplexor de 40
canales banda C, incluso tarjeta de canales (40-DMX-CE) demultiplexa 40 canales 100-GHz-espacio
identificados en el plan de canal (tabla 49: Plan de asignación de canal, en la Página 84 ) y los envía a
puertos de salida dedicada. Una sola VOA que es común a todos los canales puede regularse la potencia
óptica total. La tarjeta 40-DMX-C es ópticamente pasiva, unidireccional y puede ser instalada en las
ranuras 1 a 6 y 12 a 17.
The 40-DMX-C or 40-DMX-CE has two types of ports:
COM RX port: COM RX es el puerto de entrada de línea para la señal óptica agregada se
demultiplexan. Este puerto es apoyado por una VOA para la regulación de la potencia óptica y un
fotodiodo para por canales de control de potencia óptica.
Note De forma predeterminada, se encuentra la VOA a su atenuación máxima por

razones de seguridad (por ejemplo, falta de energía eléctrica). También existe un
ajuste manual de la VOA.
DROP TX ports (1 to 40): En su salida, la tarjeta C-DMX-40 o 40-DMX-CE proporciona gota 40

puertos que se utilizan normalmente para dejar caer a canales en el nodo ROADM. Estos puertos están
conectados mediante cinco conectores físicos en el panel frontal que aceptan cables de entrada de
cliente MPO. (MPO cables salir en ocho cables separados.) La tarjeta 40-DMX-C también tiene un
conector óptico LC-PC-II para la entrada principal.
La siguiente figura muestra el diagrama de bloques funcional de módulo óptico C-DMX-40 o 40-DMX-CE.
Figure 3: 40-DMX-C or 40-DMX-CE Optical Module Functional Block Diagram
For more information about the 40-DMX-C or 40-DMX-CE card, see

http://www.cisco.com/en/US/prod/collateral/optical/ps5724/ps2006/product_data_sheet0900aecd805ebf1d.html.
81
40-DMX-C and 40-DMX-CE ROADM Functionality
40-DMX-C and 40-DMX-CE ROADM Functionality

La tarjeta 40-DMX-C (o 40-DMX-CE) funciona en combinación con la tarjeta 40-WSS-C (o 40-WSS-CE)
para implementar la funcionalidad ROADM. Como un nodo ROADM, el nodo se puede configurar en el
nivel del canal óptico con CTC, planificador de transporte Cisco y CTM. Funcionalidad ROADM con la
tarjeta 40-DMX-C (o 40-DMX-CE) requiere dos ranura única 40-DMX-C (o 40-DMX-CE) y dos 40-WSS-
C (o 40-WSS-CE) doble ranura tarjetas (para un total de seis ranuras en el chasis).
Para funcionalidad ROADM de otras cartas, vea Descripción de la tarjeta en este capítulo. Para un
diagrama de una configuración típica de ROADM, consulte la sección, nodo ROADM en la guía de
configuración de red de Cisco ONS 15454 DWDM.
40-DMX-C and 40-DMX-CE Power Monitoring

Physical photodiodes P1 through P40 monitor the power at the outputs of the 40-DMX-C or 40-DMX-CE
card. P41 monitors the total multiplexed power at the input, calibrated to the COM-RX port. The
following table shows the returned power level values calibrated to each port.
Table 47: 40-DMX-C or 40-DMX-CE Port Calibration
40-DMX-C and 40-DMX-CE Channel Plan

This table shows the 40 ITU-T 100-GHz-spaced, C-band channels (wavelengths) that are demultiplexed
by the 40-DMX-C card.
Band ID Channel Label Frequency (GHz) Wavelength (nm)

3
Ch. 0 29.5 196 1529.55
B30.3 30.3 195.9 1530.33
31.1 195.8 1531.12
31.9 195.7 1531.90
32.6 195.6 1532.68
33.4 195.5 1533.47
82
B34.2 34.2 195.4 1534.25
35.0 195.3 1535.04
35.8 195.2 1535.82
36.6 195.1 1536.61
37.4 195 1537.40
B38.1 38.1 194.9 1538.19
38.9 194.8 1538.98
39.7 194.7 1539.77
40.5 194.6 1540.56
41.3 194.5 1541.35
B42.1 42.1 194.4 1542.14
42.9 194.3 1542.94
43.7 194.2 1543.73
44.5 194.1 1544.53
45.3 194 1545.32
B46.1 46.1 193.9 1546.12
46.9 193.8 1546.92
47.7 193.7 1547.72
48.5 193.6 1548.51
49.3 193.5 1549.32
B50.1 50.1 193.4 1550.12
50.9 193.3 1550.92
51.7 193.2 1551.72
52.5 193.1 1552.52
53.3 193 1553.33
83
B54.1 54.1 192.9 1554.13
54.9 192.8 1554.94
55.7 192.7 1555.75
56.5 192.6 1556.55
57.3 192.5 1557.36
B58.1 58.1 192.4 1558.17
58.9 192.3 1558.98
59.7 192.2 1559.79
60.6 192.1 1560.61
61.4 192 1561.42

This channel is unused by the 40-WXC-C
This table shows the 40 ITU-T 100-GHz-spaced, C-band channels (wavelengths) that are demultiplexed
by the 40-DMX-CE card.
B30.7 30.7 195.85 1530.72
31.5 195.75 1531.51
32.3 195.65 1532.29
33.1 195.55 1533.07
33.9 195.45 1533.86
B34.6 34.6 195.35 1534.64
35.4 195.25 1535.43
36.2 195.15 1536.22
37.0 195.05 1537.00
37.8 194.95 1537.79
84
B38.6 38.6 194.85 1538.58
39.4 194.75 1539.37
40.1 194.65 1540.16
40.9 194.55 1540.95
41.8 194.45 1541.75
B42.5 42.5 194.35 1542.54
43.3 194.25 1543.33
44.1 194.15 1544.13
44.9 194.05 1544.92
45.7 193.95 1545.72
B46.5 46.5 193.85 1546.52
47.3 193.75 1547.32
48.1 193.65 1548.11
48.9 193.55 1548.91
49.7 193.45 1549.72
B50.5 50.5 193.35 1550.52
51.3 193.25 1551.32
52.1 193.15 1552.12
52.9 193.05 1552.93
53.7 192.95 1553.73
B54.4 54.4 192.85 1554.54
55.3 192.75 1555.34
56.1 192.65 1556.15
56.9 192.55 1556.96
57.8 192.45 1557.77
85
Related Procedures for 40-DMX-C and 40-DMX-CE Cards
B58.6 58.6 192.35 1558.58
59.4 192.25 1559.39
60.2 192.15 1560.20
61.0 192.05 1561.01
61.8 191.95 1561.83
Related Procedures for 40-DMX-C and 40-DMX-CE Cards

The following section lists procedures and tasks related to the configuration of the 40-DMX-C or 40-DMX-
CE card:
and 40-DMX-CE Cards
40-MUX-C Card
The single-slot 40-Channel Multiplexer C-band (40-MUX-C) card multiplexes forty ITU-T 100-GHz-spaced
channels identified in the channel plan in Table 48: Channel Allocation Plan, on page 82. The 40-MUX-C card
can be installed in Slots 1 to 6 and 12 to 17. The 40-MUX-C card is typically used in hub nodes.
The 40-MUX-C card has two types of ports:
COM TX port: COM TX is the line output port for the aggregate optical signal being multiplexed. This
port is supported by both a VOA for optical power regulation and a photodiode for per channel optical
power monitoring.
Note By default, the VOA is set to its maximum attenuation for safety purposes (for
example, electrical power failure). A manual VOA setting is also available.
86
40-MUX-C Card Power Monitoring
DROP RX ports (1 to 40): The 40-MUX-C card provides 40 input optical channels. These ports are
connected using five physical receive connectors on the card’s front panel that accept MPO cables for
the client input interfaces. MPO cables break out into eight separate cables. The 40-DMX-C card also
has one LC-PC-II optical connector for the main output. For the wavelength range, see Table 48:
Channel Allocation Plan, on page 82.
The following figure shows the 40-MUX-C optical module functional block diagram.
Figure 4: 40-MUX-C Optical Module Functional Block Diagram
For more information about the 40-MUX-C card, see

40-MUX-C Card Power Monitoring

Physical photodiodes P1 through P40 monitor the power of the individual input ports to the 40-MUX-C
card. P41 monitors the total multiplexed output power, calibrated to the COM-TX port. The following table
shows the returned power level values calibrated to each port.
Table 50: 40-MUX-C Port Calibration
P1–P40 ADD ADD RX
P41 OUTPUT COM COM-TX
87
40-MUX-C Card Channel Plan
40-MUX-C Card Channel Plan

Table 48: Channel Allocation Plan, on page 82 shows the 40 ITU-T 100-GHz-spaced, C-band
channels (wavelengths) that are multiplexed by the 40-MUX-C card.
Related Procedures for 40-MUX-C Card

The following section lists procedures and tasks related to the configuration of the 40-MUX-C card:
and 40-DMX-CE Cards
40-WSS-C and 40-WSS-CE Card

The double-slot 40-channel wavelength selective switch C-band (40-WSS-C) or the double-slot 40-channel
wavelength selective switch even-channel C-band (40-WSS-CE) card switches 40 ITU-T 100-GHz-spaced
channels identified in the channel plan (Table 48: Channel Allocation Plan, on page 82 or Table 49:
Channel Allocation Plan, on page 84) and sends them to dedicated output ports. The 40-WSS-C or 40-
WSS-CE card is bidirectional and optically passive. The card can be installed in Slots 1 to 6 and 12 to 17
The 40-WSS-C or 40-WSS-CE features include:
Receipt of an aggregate DWDM signal into 40 output optical channels from the Line receive port (EXP
RX) in one direction and from the COM-RX port in the other direction.
Per-channel optical power monitoring using photodiodes.
Signal splitting in a 70%-to-30% ratio, sent to the 40-DMX-C (or 40-DMX-CE) for dropping signals,
then to the other 40-WSS-C (or 40-WSS-CE) card.
Aggregate DWDM signal monitoring and control through a variable optical attenuator (VOA). In the
case of electrical power failure, the VOA is set to its maximum attenuation for safety purposes. A
manual VOA setting is also available.
Within the 40-WSS-C or 40-WSS-CE card, the first AWG opens the spectrum and each wavelength is
directed to one of the ports of a 1x2 optical switch. The same wavelength can be passed through or stopped.
If the pass-through wavelength is stopped, a new channel can be added at the ADD port. The card’s second
AWG multiplexes all of the wavelengths, and the aggregate signal is output through the COM-TX port.
88
40-WSS-C and 40-WSS-CE Card
The 40-WSS-C or 40-WSS-CE has eight types of ports:

ADD RX ports (1 to 40): These ports are used for adding channels. Each add channel is associated with
an individual switch element that selects whether an individual channel is added. Each add port has
optical power regulation provided by a VOA. The five connectors on the card faceplate accept MPO
cables for the client input interfaces. MPO cables break out into eight separate cables. The 40-WSS-C
or 40-WSS-CE card also has one LC-PC-II optical connector for the main input.
COM RX: The COM RX port receives the optical signal from a preamplifier (such as the OPT-PRE)
and sends it to the optical splitter.
COM TX: The COM TX port sends an aggregate optical signal to a booster amplifier card (for example,
the OPT-BST card) for transmission outside of the NE.
EXP RX port: The EXP RX port receives an optical signal from another 40-WSS-C or 40-WSS-CE card
in the same NE.
EXP TX: The EXP TX port sends an optical signal to the other 40-WSS-C or 40-WSS-CE card within
the NE.
DROP TX port: The DROP TX port sends the split off optical signal that contains drop channels to the
40-DMX-C( or 40-DMX-CE) card, where the channels are further processed and dropped.
The following figure shows a functional block diagram of the 40-WSS-C or 40-WSS-CE card.
Figure 5: 40-WSS-C or 40-WSS-CE Block Diagram
For more information about the 40-WSS-C or 40-WSS-CE card, see

89
40-WSS-C and 40-WSS-CE ROADM Functionality
40-WSS-C and 40-WSS-CE ROADM Functionality

The 40-WSS-C (or 40-WSS-CE) card works in combination with the 40-DMX-C (or 40-DMX-CE) card
to implement ROADM functionality. As a ROADM node, the node can be configured at the optical
channel level using CTC, Cisco Transport Planner, and CTM. ROADM functionality using the 40-WSS-C
(or 40-WSS-CE) card requires two 40-WSS-C (or 40-WSS-CE) double-slot cards and two 40-DMX-C (or
40-DMX-CE) single-slot cards (for a total of six slots in the chassis).
For information about ROADM functionality for other cards, see that card’s description in this chapter. For
a diagram of a typical ROADM configuration, see the section, ROADM Node in the Cisco ONS 15454
DWDM Network Operations Guide.
40-WSS-C and 40-WSS-CE Power Monitoring

The 40-WSS-C (or 40-WSS-CE) has physical diodes that monitor power at various locations on the card.
The following table lists the physical diode descriptions.
Table 51: 40-WSS-C or 40-WSS-CE Physical Photodiode Port Calibration
Physical Photodiode CTC Type Name Calibrated to Port(s)
P1 DROP DROP TX
P2 EXP EXP RX
PDi3 4 RX Add i RX ports (that is, channel
input Add i RX power), up to 40
ports and therefore 40 PDs
1
PDi4 TX COM TX port (that is, per channel
output COM TX power) up to 40
channels and therefore 40 PDs
PD5 COM COM TX port (that is, total

output COM TX power)
i indicates any channel from 01 through 40.
Port Numbers and TL1 Aids” section in Cisco ONS SONET TL1 Command Guide .
Additionally, the 40-WSS-C (or 40-WSS-CE) has two virtual diodes. Virtual diodes are monitor points for
each physical photodiode; they are identified with a physical diode relative to the way that the physical
diode is identified with one of the two interlink (ILK) ports. The following table lists the virtual diodes.
Table 52: 40-WSS-C or 40-WSS-CE Virtual Photodiode Port Calibration
Virtual Photodiode CTC Type Name Calibrated to Port(s)
VPD1 COM COM RX port (total input COM

RX power)
VPD2 EXP EXP TX port (total output EXP TX

power)
90
40-WSS-C and 40-WSS-CE Channel Plan
40-WSS-C and 40-WSS-CE Channel Plan

channels (wavelengths) that are switched by the 40-WSS-C card.
channels (wavelengths) that are switched by the 40-WSS-CE card.
Related Procedures for 40-WSS-C and 40-WSS-CECards

The following section lists procedures and tasks related to the configuration of the 40-WSS-C or 40-WSS-
CE card:
and 40-DMX-CE Cards
40-WXC-C Card
The double-slot 40-channel wavelength cross-connect C-band (40-WXC-C) card selectively sends any
wavelength combination coming from nine input ports to a common output port. The device can manage up
to 41 channels spaced at 100GHz on each port according to the channel grid in Table 48: Channel
Allocation Plan, on page 82. Each channel can be selected from any input. The card is optically passive and
provides bidirectional capability. It can be installed in Slots 1 to 6 and 12 to 17.
.The 40-WXC-C card provides the following features:
Demultiplexing, selection, and multiplexing of DWDM aggregate signal from input ports to common
output port.
Aggregate DWDM signal monitoring and control through a VOA.
VOAs are deployed in every channel path in order to regulate the channel’s optical power. In the case
of an electrical power failure, VOAs are set to their maximum attenuation value, or to a fixed and
configurable one. The VOA can also be set manually.
Per-channel optical power monitoring using photodiodes.
The 40-WXC-C card acts as a selector element with the following characteristics:
91
40-WXC-C Card
It is able to select a wavelength from one input port and pass the wavelength through to the common out port.
Simultaneously, the card can block the same wavelength coming from the other eight input ports.
It is able to stop wavelengths from all nine inputs.
It is able to monitor optical power and control path attenuation using per channel VOA independently
of the wavelength input-to-out port connection.
The 40-WXC-C card has six types of ports:

COM TX: The COM TX port sends an aggregate optical signal to a booster amplifier card (for example,
the OPT-BST card) for transmission outside of the NE.
EXP TX: The EXP TX port sends an optical signal to the other 40-WXC-C card within the NE.
MON TX: The optical service channel (OSC) monitor.
ADD/DROP RX: The 40-WXC-C card provides 40 input optical channels. For the wavelength range,
see Table 48: Channel Allocation Plan, on page 82.
ADD/DROP TX: The DROP TX port sends the split off optical signal that contains drop channels to the
40-WXC-C card, where the channels are further processed and dropped.
The following figure shows the 40-WXC-C optical module functional block diagram.
Figure 6: 40-WXC-C Optical Module Functional Block Diagram
92
40-WXC-C Power Monitoring
For more information about the 40-WXC-C card, see


The 40-WXC-C has 83 physical diodes (P1 through P40) that monitor power at the outputs of the card.
The following table describes the physical diodes.
Table 53: 40-WXC-C Physical Photodiode Port Calibration
P1 DROP DROP TX
P2 EXP EXP RX
PDi3 5 RX Add i RX ports (that is, channel
input Add i RX power), up to 40
ports and therefore 40 PDs
1
PDi4 TX COM TX port (that is, per channel
output COM TX power) up to 40
channels and therefore 40 PDs
PD5 COM COM TX port (that is, total

output COM TX power)
i indicates any channel from 01 through 40.
Additionally, the 40-WXC-C has two virtual diodes. Virtual diodes are monitor points for each physical
photodiode; they are identified with a physical diode relative to the way that the physical diode is
identified with one of the two interlink (ILK) ports. The following table lists the virtual diodes.
Table 54: 40-WXC-C Virtual Photodiode Port Calibration
VPD1 COM COM RX port (total input COM

RX power)
VPD2 EXP EXP TX port (total output EXP TX

power)
The usage of WXC and mesh PP power readings to troubleshoot a LOS-P in WXC COM TX port in Side
A is described in the following example. The example is explained assuming a single wavelength 1558.17
in the setup that comes from Side H to Side A. If there is more than one wavelength, then there is a risk of
dropping traffic when pulling common fibers. The example is explained below:
When the wavelength from side H is 1558.17, you can check the power reading at WXC EXP TX port of the
WXC card and verify the consistency with side H pre output power and WXC COMRX-EXPTX port loss. You
can also check with a power meter connected to the 8th fiber (since it is from side H) of an MPO-FC (or
93
40-WXC-C Channel Plan
LC) cable connected to the TAP-TX port of the MESH-PP. This value should be consistent with the
previous reading, less than the insertion loss of the installed PP-MESH. If it is consistent, the issue is with
the MPO between side A WXC and PP-MESH. If it is not consistent, the issue is with the PP-MESH or the
LC-LC from side H. With only the PP-MESH already tested during installation, the only issue can be with
the patch cord b.
You can check if the 1558.17 wavelength from side H is unequalized (that is, if the channel is not aligned
with the linear fit of the power values of the other channels) by keeping the DMX COM-RX port of side H
in maintenance, and checking both the signal and ASE levels of CHAN-TX ports of the DMX card. If the
channel is equalized (that is, if the channel is aligned with the linear fit of the power values of the other
channels), then the issue is in the WXC side A that cannot properly regulate the VOA for such channel. If
the channel is unequalized, then the issue is on a remote node.
Note With an OSA or a spare 40 DMX, you can see the light coming from all the sides from TAP-TX of
the PP-MESH.

channels (wavelengths) that are cross connected by the 40-WXC-C card.
Related Procedures for 40-WXC-C Card

The following section lists procedures and tasks related to the configuration of the 40-WXC-C card:
NTP-G185 Installing Fiber-Optic Cables between Mesh Nodes
and 40-DMX-CE Cards
NTP-G174 Modifying Line Settings and PM Thresholds for 40-WXC-C, 80-WXC-C, or 16-WXC-FS
Cards
80-WXC-C Card
(Cisco ONS 15454, ONS 15454 M6, NCS 2015 only)
The double-slot 80-channel Wavelength Cross-Connect C-band (80-WXC-C) card manages up to 80 ITU-T 50
GHz-spaced channels identified in the channel plan and sends them to dedicated output ports. Each channel
94
80-WXC-C Card
can be selected from any input port to any output port. The card is optically passive, and provides
bidirectional capability. It can be installed in Slots 1 to 5 and 12 to 16 the ONS 15454 chassis. It can be
installed in Slots 2 to 6 in the Cisco ONS 15454 M6 and Slots 2 to 17 in the NCS 2015 chassis.
The 80-WXC-C card provides the following functionalities:
When used in the multiplexer or bidirectional mode, the 80-WXC-C card allows selection of a single
wavelength or any combination of wavelengths from any of the nine input ports to the common
output port.
When used in the bidirectional mode, the output wavelength from the COM-RX port is split to manage
the express and drop wavelengths.
When used in the demultiplexer mode, the 80-WXC-C card, allows selection of a single wavelength or
a combination of wavelengths from the common input port to any of the nine output ports.
Automatic VOA shutdown (AVS) blocking state on each wavelength and port.
Per-channel (closed loop) power regulation on the output port based on OCM block feedback.
Per-channel (open loop) attenuation regulation on the output port which is not based on the OCM feedback.
The OCM unit provides per-channel optical power monitoring on the following ports:
COM port in output direction
COM port in input direction
DROP-TX port in output direction
Eight Express/Add/Drop (EAD) ports and one Add/Drop (AD) port in both input and output directions
The 80-WXC-C card has 14 types of ports:

MON: The MON port monitors power on the COM T/R port.
DROP TX: In the bidirectional mode, the DROP TX port sends the optical signal to the demultiplexer.
EXP TX: The EXP TX port sends the split off optical signal that contains pass-through channels to the
other side of the NE.
COM T/R: The COM port is bidirectional. It functions as a COM TX port in the multiplexer mode and
as a COM RX port in the demultiplexer mode.
AD T/R: The AD port functions as ADD RX port in bidirectional and multiplexer modes and as a
DROP port in the demultiplexer mode.
EAD T/R i (where i = 1 to 8): The EAD ports function as EXP ports in the bidirectional mode, as ADD
ports in the multiplexer mode, and as DROP ports in the demultiplexer mode.
The different units of the 80-WXC-C card are:

40/60 splitter with VOA on drop path—The preamplifier output signal from the preamplifier is split in a
40%-to-60% ratio; 40% is sent on the drop path (DROP-TX port) and 60% is sent on the pass-through path
(EXP-TX port). The VOA equipped on the drop path is used to match the power range of the receiver
photodiode without the need for bulk attenuation. If a channel is expected to be dropped in the 80-WXC-C
95
card, the pass-through channel is stopped after the EXP-TX port either by a 40-WSS-C or a 40-WXC-
C card.
50 Ghz 10 port WXC—The WXC block is optically passive and has bidirectional capability. The WXC
block can selectively send any wavelength combination coming from the eight input EAD ports and
one AD port to a common (COM) output port, when used as a multiplexer, whereas it can selectively
send any wavelength combination coming from its common (COM) input port to any of the eight
output EAD ports and one AD port, when used as a demultiplexer. The WXC block can manage (on
each port) up to 80 channels according to the channel grid reported in Table 57: 80-WXC-C Channel
Plan, on page 97. Each channel can be selected from any input and routed to any output.
50 Ghz Optical Channel Monitor (OCM)—The OCM provides per channel power monitoring on the
COM T/R, DROP-TX, AD, and EADi (i=1 to 8) ports. The power value for each wavelength is
refreshed after a variable timer depending on the port and card activity.
For instructions on proper handling of the 80-WXC-C card, see 80-WXC-C Card Handling.
For more information about the 80-WXC-C card, see
http://www.cisco.com/en/US/prod/collateral/optical/ps5724/ps2006/datasheet_c78-598521.html.

The 80-WXC-C has two physical photodiodes and an OCM unit that monitors power at the different ports
of the card. The following table describes the physical photodiodes.
Table 55: 80-WXC-C Port Calibration
PD1 COM Total Power COM
PD2 EXP-TX Total Power EXP-TX
OCM1 EAD 1 Per-Channel and Total EAD-1

Power

Power

Power

Power

Power

Power

Power
96

Power
OCM9 AD Per-Channel and Total Power AD
OCM10 Output Per-Channel and Total COM

Power
OCM11 Input Per-Channel and Total Power COM
OCM12 Drop Per-Channel and Total Power DROP-TX
Port Numbers and TL1 Aids” section in the Cisco ONS SONET TL1 Command Guide.
Additionally, the 80-WXC-C has two virtual photodiodes. The following table lists the virtual photodiodes.
Table 56: 80-WXC-C Virtual Photodiode Port Calibration
VPD3 DROP-TX Total Power DROP-TX
VPD4 COM-RX Total Power COM-RX

The following table shows the 80 ITU-T 50-GHz-spaced, C-band channels (wavelengths) that are
cross connected by the 80-WXC-C card.
Table 57: 80-WXC-C Channel Plan

6
Ch. 0 - 196 1529.55
97
30.3 30.3 195.9 1530.33
30.7 195.85 1530.72
31.1 195.8 1531.12
31.5 195.75 1531.51
31.9 195.7 1531.90
32.3 195.65 1532.29
32.7 195.6 1532.68
33.1 195.55 1533.07
33.5 195.5 1533.47
33.9 195.45 1533.86
34.3 34.3 195.4 1534.25
34.6 195.35 1534.64
35.0 195.3 1535.04
35.4 195.25 1535.43
35.8 195.2 1535.82
36.2 195.15 1536.22
36.6 195.1 1536.61
37.0 195.05 1537
37.4 195 1537.40
37.8 194.95 1537.79
98
38.2 38.2 194.9 1538.19
38.6 194.85 1538.58
39.0 194.8 1538.98
39.4 194.75 1539.37
39.8 194.7 1539.77
40.2 194.65 1540.16
40.6 194.6 1540.56
41.0 194.55 1540.95
41.3 194.5 1541.35
41.7 194.45 1541.75
42.1 42.1 194.4 1542.14
42.5 194.35 1542.94
42.9 194.3 1542.94
43.3 194.25 1543.33
43.7 194.2 1543.73
44.1 194.15 1544.13
44.5 194.1 1544.53
44.9 194.05 1544.92
45.3 194 1545.32
45.7 193.95 1545.72
99
46.1 46.1 193.9 1546.12
46.5 193.85 1546.52
46.9 193.8 1546.92
47.3 193.75 1547.32
47.7 193.7 1547.72
48.1 193.65 1548.11
48.5 193.6 1548.51
48.9 193.55 1548.91
49.3 193.5 1549.32
49.7 193.45 1549.72
50.1 50.1 193.4 1550.12
50.5 193.35 1550.52
50.9 193.3 1550.92
51.3 193.25 1551.32
51.7 193.2 1551.72
52.1 193.15 1552.12
52.5 193.1 1552.52
52.9 193.05 1552.93
53.3 193 1553.33
53.7 192.95 1553.73
100
54.1 54.1 192.9 1554.13
54.5 192.85 1554.54
54.9 192.8 1554.94
55.3 192.75 1555.34
55.7 192.7 1555.75
56.2 192.65 1556.15
56.6 192.6 1556.55
57.0 192.55 1556.96
57.4 192.5 1557.36
57.8 192.45 1557.77
58.2 58.2 192.4 1558.17
58.6 192.35 1558.58
59.0 192.3 1558.98
59.4 192.25 1559.39
59.8 192.2 1559.79
60.2 192.15 1560.20
60.6 192.1 1560.61
61.0 192.05 1561.01
61.4 192 1561.42
61.8 191.95 1561.83

This channel is unused by the 80-WXC-C

The following section lists procedures and tasks related to the configuration of the 80-WXC-C card:
101
16-WXC-FS Card

and 40-DMX-CE Cards
Cards
16-WXC-FS Card
The 16-WXC-FS card is a double-slot cross connect card, tunable over 96 channels in the C-band, at 50-
GHz spacing on the ITU-T grid. The card provides the flex spectrum capability, which allows the user the
flexibility to allocate the channel bandwidth, to increase the network scalability. The channel bandwidth is
not fixed, but can be defined arbitrarily, with a given granularity and within a given range. Attenuation and
power values are defined for each sub-range. The central frequency ranges from 191'350 Ghz (1566 .72
nm) to 196'100 Ghz (1528 .77 nm).
The 16-WXC-FS card can be used in point-to-point, ring, multi-ring, or mesh topologies. The 16-WXC-FS
card supports up to 16 directions for each ROADM node. The card is optically passive and provides
bidirectional capability. It can be installed in slots 2, 4, or 6 in the Cisco ONS 15454 M6 chassis. It is
recommended that you use the 16-WXC-FS card in slot 4 when used with EDRA amplifiers to comply with
optical safety. It is recommended that you use the 16-WXC-FS card and the EDRA-2-xx card in slots 2 and
4, 5 and 7, 8 and 10, 11 and 13 of the Cisco ONS 15454 M15 chassis.
Important In the Cisco ONS 15454 M6 chassis, the 16-WXC-FS card front panel has two compression latch devices.
These latches enforce the position of the unit in the chassis. To insert or remove a card from the Cisco ONS
15454 M6 chassis, rotate the compression latches fully in the anti-clockwise direction. After the card is
inserted or removed, close the unit and rotate the compression latches fully in the clockwise direction.
For more information about the 16-WXC-FS card, see

http://www.cisco.com/en/US/solutions/collateral/ns340/ ns394/ns398/ns406/data_sheet_c78-729313.html
Limitations
The 16-WXC-FS card is not compatible with 15454 -M6-FTA fan tray assembly; the card is compatible
with 15454 -M6-FTA2 fan tray assembly or a subsequent fan tray assembly release.
16-WXC-FS Ports
The 16-WXC-FS card has these ports:
EXP-TXi (where i = 1 to 16)—The EXP TX port sends the split-off optical signal that contains pass-
through channels to the other side of the NE. For example, in four degrees setup, the EXP ports can be
used as drop Tx ports, EXP-Tx(1 to 4) are used as express channel from one side to other side. The 5th
to 16th EXP-Tx ports are used to transmit the power to passive units.
EXP-RXi (where i = 1 to 16)—The EXP RX port receives the optical signal from the pass-through channels.
For example, in four degrees setup, the EXP ports can be used as drop Rx ports, EXP-Rx(1 to
102
Key Features
4) are used to receive power from the express channel from one side to other. The 5th to 16th EXP-
Rx ports are used to receive the power from the passive units.
COM-TX—The COM TX port transmits the combined power from all directions or add drop ports
towards the amplifier card.
COM-RX—The COM RX port receives the optical signal from a preamplifier card and sends it to the
optical cross connect.
UPG-TX—The UPG TX port can be used to drop channels and transmits power to the preamplifier card. This
port can also be used to increase the number of ports by connecting to another 16-WXC-FS card.
UPG-RX-The UPG RX port can be used to add channels and receives power from the preamamplifer
card. This port can also be used to increase the number of ports by connecting to another 16-WXC-
FS card.
Two LC-duplex adapters are required to connect COM and UPG ports, and four MPO connectors to
connect add/drop ports of the 16-WXC card. All the 16 I/O ports of the 16-WXC-FS card can be used
either for node interconnection or for add/drop.
Key Features
The 16-WXC-FS card provides these features when used in multiplexer mode:
The card allows you to select a single 50-GHz spaced channel or any combination of the aggregated 96
channels grid on the COM-TX port.
The combination of input signals from the 16 EXP-RX ports and the UPG-RX port into COM-TX port.
The selection of an arbitrary wavelength range or different wavelength ranges, with a common insertion
loss value on the COM-TX port.
Automatic VOA shutdown (AVS) blocking state on each wavelength on the COM-TX port.
Per-channel (closed loop) power regulation on the COM-TX output port based on OCM block feedback.
Per-channel (open loop) attenuation regulation on the EXP-TX output port, which is not based on the
OCM feedback.
The 16-WXC-FS card provides these features when used in de-multiplexer mode:
The card allows you to select a single 50-GHz spaced channel or any combination of the aggregated 96
channels grid on any of the 16 EXP-TX port.
Splitting of the input signal from COM-RX port into a total of 16 EXP-TX ports and 1 UPG-TX port.
AVS blocking state on each wavelength on any of the 16 EXP-TX ports.
Per-channel (closed loop) power regulation on the EXP-TX output port based on OCM block feedback.
Per-channel (open loop) attenuation regulation on the EXP-TX output port which is not based on the
OCM feedback.
Selection of an arbitrary wavelength range or of different wavelength ranges, with a common insertion
loss value on any of the 16 EXP-TX ports.
103
16-WXC-FS Power Monitoring
DWDM Optical amplifier(s) partially compensates the loss of couplers or splitters and wavelength
blockers.
16-WXC-FS Power Monitoring

The 16-WXC-FS card has two physical photodiodes and an OCM unit that monitors power at the
different ports of the card.
Table 58: 16-WXC-FS Port Calibration
PD1 COM-RX Total Input Power COM-RX
PD2 COM-TX Total Output Power COM-TX
OCM1 COM-RX Per-Channel and Input COM-RX

Power
OCM2 COM-TX Per-Channel and Output COM-TX

Power
OCM3 to OCM18 De-MUX Output Ports EXP-TX
OCM19 to OCM34 MUX Input Ports EXP-RX
OCM35 De-MUX Output Ports UPG-TX
OCM36 MUX Input Ports UPG-RX
For information on associated TL1 AIDs for the optical power monitoring points, see the “CTC Port
Numbers and TL1 Aids” section in the Cisco ONS SONET TL1 Command Guide.
The OCM unit provides per-channel optical power monitoring on these ports:
COM-TX and COM-RX ports
UPG-TX and UPG-RX ports
EXP-TXi (where i = 1 to 16) ports in output direction
EXP-RXi (where i = 1 to 16) ports in input direction
104
Task Flow Diagram of 16-WXC-FS Card
Task Flow Diagram of 16-WXC-FS Card

Figure 7: Task Flow Diagram of 16-WXC-FS Card
Related Procedures for 16-WXC-FS Card (Procedimientos

relacionados para la tarjeta de 16-WXC-FS)
The following section lists procedures and tasks related to the configuration of the 16-WXC-FS card:
and 40-DMX-CE Cards
105
Single Module ROADM (SMR-C) Cards
Cards
Single Module ROADM (SMR-C) Cards (Módulo

ROADM (SMR-C) tarjetas)
Note Para información de la etiqueta de seguridad 40-SMR1-C y 40-SMR2-C, consulte las etiquetas de
seguridad.
Las tarjetas de ranura única 40 canales módulo ROADM (SMR-C) integran los siguientes bloques
funcionales en la tarjeta de una sola línea:
Optical preamplifier
Optical booster amplifier
Optical service channel (OSC) filter
2x1 wavelength cross-connect (WXC) or a 4x1 WXC
Optical channel monitor (OCM)
The SMR-C cards are available in two versions:

40-SMR1-C Card
40-SMR2-C Card
Las tarjetas de SMR-C pueden administrar hasta 40 canales espaciados a 100GHz en cada
puerto según la plantilla de canal en la tabla 10-10. Pueden instalar las tarjetas en las ranuras 1
a 6 y 12 a 17. Para obtener más información acerca de la tarjeta 40-SMR1-C o 40-SMR2-C, ver
http://www.cisco.com/en/US/prod/collateral/optical/ps5724/ps2006/data_sheet_c78-578552.html.
SMR-C Card Key Features (Características principales tarjeta C

SMR)
Las unidades de amplificador óptico en las tarjetas de SMR-C proporcionan las siguientes características:
Filtro de aplanamiento incorporado ganancia
Etapa media acceso para unidad de compensación de dispersión (sólo aplica para el amplificador de
fibra dopada de erbio preamplificador [EDFA])
Modo de potencia de salida fija
Fixed gain mode
Función de transferencia de baja frecuencia nondistorting
Compensación de emisión espontánea amplificada (ASE) de ganancia fija y modo de potencia de salida
fija rápida supresión transitoria
Tilt programable (sólo aplicable para preamplificador EDFA)
106
40-SMR1-C Card
Monitoreo completo y capacidad de manejo de la alarma

Seguridad óptica ayuda a través de la detección de pérdida de señal y alarma en cualquier puerto de
entrada, control, la alimentación rápida y reduce la potencia de salida máxima en modo seguro
Sección EDFA calcula la potencia de la señal, teniendo en cuenta la contribución que se espera de
energía ASE a la potencia de salida total. Potencia de salida de la señal o la ganancia de la señal se
puede utilizar como señales de retroalimentación para el bucle de control de potencia de bomba EDFA
La unidad WXC de 1 x 2 (40-SMR1-C tarjeta) proporciona las siguientes características:

Selección de cada longitud de onda de la señal de 100 gigahertz agregados del EXP-RX o puertos
ADD-RX
Apagado automático de VOA (AVS) bloqueo de estado en cada longitud de onda y puerto por canal
regulación de potencia basado en la unidad externa de la OCM
Lazo abierto control de atenuación de trayectoria para cada longitud de onda y puerto de
La unidad WXC de 1 x 4 (40-SMR2-C tarjeta) proporciona las siguientes características:

Selección de longitud de onda individual de lo agregado 100GHz de señal desde la EXPi-RX (donde i =
1, 2, 3) o puertos de ADD-RX
Apagado automático de VOA (AVS) estado en cada longitud de onda y puerto de bloqueo Regulación
de potencia por canal basado en la unidad externa de la OCM
Lazo abierto control de atenuación de trayectoria para cada longitud de onda y puerto de La unidad
OCM ofrece por canal potencia óptica supervisión en EXP-RX, ADD-RX, TX DROP y línea-TX
puertos.
40-SMR1-C Card
The 40-SMR1-C tarjeta incluye una unidad WXC de 100Ghz 1 x 2 con unidad de preamplificador
integrado (solo EDFA).
The 40-SMR1-C tarjeta tiene los siguientes tipos de puertos:
MON RX: El puerto de MON RX supervisa energía en el puerto de salida de TX EXP.
MON TX: El puerto TX MON monitores de energía en el puerto de salida de línea-TX.
DC RX: El puerto RX DC recibe la señal óptica de la dispersión compensación unidad (DCU) y envía al
segundo preamplificador etapa de entrada.
DC TX: El puerto DC TX envía la señal óptica de la primera salida de preamplificador de etapa a la
DCU.
OSC RX: El puerto de OSC RX es el OSC añadir puerto de entrada.
OSC TX: El puerto de TX de la OSC es el puerto de salida de la DROP OSC.
ADD/DROP RX: The ADD RX puerto recibe la señal óptica de la sección de multiplexor de la NE y lo
envía a la unidad WXC de 1 x 2.
ADD/DROP TX: El puerto DROP TX envía la división de señal óptica a la sección de demultiplexor
de la NE
107
40-SMR1-C Card
LINE RX: El puerto de la línea RX es el puerto de señal de entrada.

LINE TX: El puerto de la línea TX es el puerto de salida de señal.
EXP RX: El puerto EXP RX recibe la señal desde el otro lado de la NE y lo envía a la unidad WXC de
1 x 2.
EXP TX: El puerto de TX EXP envía la división de la señal óptica que contiene canales de paso al otro
lado de la NE
La siguiente figura muestra un diagrama de bloques de la tarjeta 40-SMR1-C.

Figure 8: 40-SMR1-C Block Diagram
Las diferentes unidades de la tarjeta 40-SMR1-C son:

Filtro OSC-OSC el filtro permite agregar un canal OSC para la banda C en la ruta de transmisión y a un
canal OSC en el camino de recepción. La tarjeta OSCM conectado a los puertos de OSC-TX y RX
OSC genera el canal OSC.
Preamplificador EDFA con ganancia variable de doble etapa, el preamplificador doble etapa permite la
inserción de un DCU entre DC-TX y RX DC puertos compensar la dispersión cromática. También está
equipado con atenuador óptico variable incorporado (VOA) y aumento de aplanar el filtro (GFF) que provee
compensación de inclinación y permite el uso de este dispositivo sobre una amplia gama de pérdidas span (5
dB a 35 dB).
El divisor y VOA 70/30: la señal de salida del preamplificador se divide en una proporción de 70% - a -
30%, 70% es enviado a la ruta de paso a través (puerto de EXP-TX) y 30% se envía a la trayectoria de
la caída (puerto de DROP-TX). La VOA en la trayectoria de la caída se utiliza para que coincida con
el rango de potencia del diodo de la foto de receptor sin necesidad de atenuación a granel. Si un canal
se espera que se cayó en la tarjeta 40-SMR1-C, el canal de paso se detiene después de que el EXP-TX
Puerto ya sea por una tarjeta de 40-WSS-C, 40-SMR1-C o 40-SMR2-C.
108
40-SMR1-C Power Monitoring
1x2 WXC—1 x 2 WXC agregados en su puerto de salida de un canal óptico 100-GHz-espacio recibido
de puerto su ADD-RX o RX de EXP. Además de la función de conmutación, la WXC de 1 x 2 permite
establecer una diferente por potencia para cada una de las longitudes de onda administradas y también
monitorear la potencia óptica.
OCM— La OCM ofrece por canales potencia de control en el RX de DROP, EXP-RX, ADD-RX y TX
línea puertos. El valor de la potencia para cada longitud de onda se actualiza después de un tiempo
variable dependiendo de la actividad portuaria y tarjeta.
You can install the 40-SMR1-C card in the following slots.


The 40-SMR1-C card has seven physical diodes (PD1 through PD6 and PD8) and an OCM unit that
monitors power at the input and output ports of the card (see the following table).
Table 59: 40-SMR1-C Port Calibration
PD1 LINE LINE-RX
PD2 LINE LINE-RX
PD3 DC DC-TX
PD4 DC DC-RX
PD5 EXP EXP-TX
PD6 OSC OSC-RX
PD8 LINE LINE-TX
OCM1 LINE OCH DROP-TX
OCM2 DROP OCH EXP-RX
OCM3 ADD OCH ADD-RX
OCM4 EXP OCH LINE-TX
40-SMR1-C Channel Plan

channels (wavelengths) supported by the 40-SMR1-C card.
109
40-SMR2-C Card
40-SMR2-C Card (Tarjeta 40-SMR2-C)

La tarjeta 40-SMR2-C incluye booster amplificador unidades (EDFA doble) y una unidad WXC de
100Ghz 1 x 4 con preamplificador integrado.
La tarjeta 40-SMR2-C tiene los siguientes tipos de puertos:
MON RX: El puerto de MON RX supervisa energía en el puerto de salida de TX EXP.
MON TX: El puerto TX MON monitorea la energía en el puerto de salida de línea-TX.
DC RX: El puerto RX DC recibe la señal óptica de la unidad dispersión cromaticas (DCU) y envía al
segundo preamplificador etapa de entrada.
DC TX: El puerto DC TX envía la señal óptica de la primera salida de preamplificador de etapa a la
DCU.
OSC RX: El puerto de OSC RX es el OSC añadir puerto de entrada.
OSC TX: El puerto de TX de la OSC es el puerto de salida de la gota OSC.
ADD/DROP RX: el puerto ADD RX recibe la señal óptica de la sección de multiplexor de la NE y lo
ADD/DROP TX: el puerto DROP TX envía la división de señal óptica a la sección de demultiplexor
de la NE
LINE RX: El puerto de la línea RX es el puerto de señal de entrada.
LINE TX: El puerto de la línea TX es el puerto de salida de señal.
EXP TX: El puerto de TX EXP envía la división de la señal óptica que contiene canales de paso al otro
lado de la NE
EXPi-RX (where i = 1, 2, 3): El puerto de EXPi-RX recibe la señal desde el otro lado de la NE y lo
La siguiente figura muestra un diagrama de bloques de la tarjeta 40-SMR2-C.
110
40-SMR2-C Card
Figure 9: 40-SMR2-C Block Diagram
Las diferentes unidades de la tarjeta 40-SMR2-C son:

OSC filter— El filtro OSC permite agregar un canal OSC para la banda C en la ruta de transmisión y a
un canal OSC en el camino de recepción. La tarjeta OSCM conectado a los puertos de OSC-TX y RX
OSC genera el canal OSC.
Preamplificador EDFA con ganancia variable de doble etapa —El preamplificador doble etapa permite la
inserción de un DCU entre los puertos DC-RX y TX de DC para compensar la dispersión cromática.
También está equipado con atenuador óptico variable incorporado (VOA) y aumento de aplanar el filtro
(GFF) que provee compensación de inclinación y permite el uso de este dispositivo sobre una amplia gama
de pérdidas span (5 dB a 35 dB).
70/30 splitter and VOA—La señal de salida del preamplificador se divide en una proporción de 70% - a
- 30%, 70% es enviado a la ruta de paso a través (puerto de EXP-TX) y 30% se envía a la trayectoria
de la caída (puerto de DROP-TX). La VOA en la trayectoria de la caída se utiliza para que coincida
con el rango de potencia del diodo de la foto de receptor sin necesidad de atenuación a granel. Si un
canal se espera que se cayó en la tarjeta 40-SMR2-C, el canal de paso se detiene después del puerto de
EXP-TX por una tarjeta de 40-SMR1-C, o 40-SMR2-C 40-WSS-C.
1x4 WXC—1 x 4 WXC agregados en su puerto de salida de un canal óptico 100-GHz-espacio recibido
de su ADD-RX o RX EXPi (donde i = 1, 2, 3) Puerto. Además de la función de conmutación, la WXC
de 1 x 4 permite un diferente por potencia para cada una de las longitudes de onda administradas y
también monitorear la potencia óptica.
111
Una etapa fija ganancia amplificador de booster EDFA — Amplificador booster amplifica la señal de
salida de la unidad de 1 x 4 WXC antes de transmitir en la fibra. Puesto que es un amplificador de
ganancia fija (17 dB), no permite aumento de control de inclinación.
OCM— La OCM ofrece por canales de energía seguimiento en DROP-RX, EXPi-RX (donde i = 1, 2,
3), ADD-RX y TX línea puertos. El valor de la potencia para cada longitud de onda se actualiza
después de un tiempo variable dependiendo de la actividad portuaria y tarjeta.
Puede instalar la tarjeta 40-SMR2-C en las siguientes ranuras.

40-SMR2-C Power Monitoring (Control de potencia 40-SMR2-C)

La tarjeta 40-SMR2-C tiene ocho diodos físicos (PD1 por PD8) y un módulo OCM que potencia en los
puertos de entrada y salidos de la tarjeta (consulte la tabla siguiente).
Table 60: 40-SMR2-C Port Calibration
PD1 LINE LINE-RX
PD2 LINE LINE-RX
PD3 DC DC-TX
PD4 DC DC-RX
PD5 EXP EXP-TX
PD6 OSC OSC-RX
PD7 Not reported on CTC Internal port
PD8 LINE LINE-TX
OCM1 LINE OCH LINE-TX
OCM2 DROP OCH DROP-TX
OCM3 ADD OCH ADD-RX
OCM4 EXP-1 OCH EXP1-RX
112

channels (wavelengths) supported by the 40-SMR2-C card.
Related Procedures for 40-SMR1-C and 40-SMR2-C Card

The following section lists procedures and tasks related to the configuration of the 40-SMR-1C and 40-
SMR-2C cards:
NTP-G243 Performing the Two-Degree ROADM Node with 40-SMR-1-C and OPT-AMP-17-C Cards
Acceptance Test
NTP-G244 Performing the Four Degree ROADM Node with 40-SMR-2-C Cards Acceptance Test
and 40-DMX-CE Cards
NTP-G241 Modifying the Line Settings and PM Thresholds for 40-SMR1-C and 40-SMR2-C Cards
17 SMR9 FS, 24 SMR9 FS, 34 SMR9 FS, and SMR20 FS/SMR20 FS CV Cards
The 17 SMR9 FS, 24 SMR9 FS, 34 SMR9 FS, and SMR20 FS/SMR20 FS CV cards are tunable over 96
channels in the C-band, at 50-GHz spacing on the ITU-T grid. The cards provide the flex spectrum
capability, which give the flexibility to allocate channel bandwidth, to increase the network scalability. The
channel bandwidth is not fixed, but can be defined arbitrarily, with a specified granularity and within a
given range. For each sub-range, attenuation and power values are defined. The central frequency ranges
from 191350 Ghz (1566 .72 nm) to 196100 Ghz (1528 .77 nm).
The 17 SMR9 FS, 24 SMR9 FS, 34 SMR9 FS, and SMR20 FS/SMR20 FS CV cards are single-slot cards that
integrate two cross-connect blocks (multiplexer and demultiplexer), a variable gain EDFA pre-amplifier, and a
variable gain EDFA booster amplifier. In addition, the SMR20 FS CV card has a dedicated laser source at the
demultiplexer section, and a photodiode at the multiplexer section; these support the connection verification
capability. The 17 SMR9 FS, 24 SMR9 FS, and 34 SMR9 FS cards support up to 9 directions for each ROADM
node. The SMR20 FS/SMR20 FS CV card support up to 20 directions for each ROADM node. The cards can be
installed in any service slot in the Cisco ONS 15454 M2, ONS 15454 M6, and the NCS 2015 chassis. The cards
can be used in point-to-point, ring, multi-ring, or mesh topologies.
The SMR20 FS CV cards provide the connection verification capability using a connectivity check
signal. The correctness and the quality of the interconnections (determined by measuring the insertion
loss of the external passive path) can be validated with the connection verification feature in the cards .
For more information about the connection verification, see Connection Verification section.
113
SMR9 FS Ports
The EDFA pre-amplifier in SMR20 FS/SMR20 FS CV cards have switchable gain ranges. The
following table describes the gain ranges and extended gain ranges of a EDFA pre-amplifier in the 17
SMR9 FS, 24 SMR9 FS, 34 SMR9 FS, and SMR20 FS/SMR20 FS CV cards.
Table 61: Gain Ranges and Extended Gain Ranges of EDFA Pre-Amplifier
Card Gain Range Extended Gain Range
17 SMR9 FS 0 - 17 dB with controlled tilt 20 dB with uncontrolled tilt
SMR20 FS/SMR20 FS CV Gain Range 1: 0 - 17 dB with 20 dB with uncontrolled tilt

controlled tilt
Gain Range 2: 12 - 24 dB with 35 dB with uncontrolled tilt

controlled tilt
For more information, such as the block diagrams and the card specifications of the 17 SMR9 FS, 24
SMR9 FS, 34 SMR9 FS, and SMR20 FS/SMR20 FS CV cards, see the data sheet.
SMR9 FS Ports
The SMR9 FS card has these ports:
through channels to the other side of the NE. For example, in four degrees setup, the EXP ports can be
used as drop Tx ports, EXP-Tx(1 to 4) are used as express channels from one side to other side. The
5th to 9th EXP-Tx ports are used to transmit power to passive units.
EXP-RXi (where i = 1 to 9)—The EXP RX port receives the optical signal from the pass-through
channels. For example, in the four degrees setup, the EXP ports can be used as drop Rx ports, EXP-
Rx(1 to 4) are used to receive power from the express channel, from one side to other. The 5th to 9th
EXP-Rx ports are used to receive power from passive units.
OSC-TX— The OSC-TX port transmits the Service Channel signal received from the LINE-RX port
signal, separating it from the C-Band signals.
OSC-RX— The OSC-RX port receives signal from the Service Channel module and transmits it to the
LINE-TX port.
COM-TX—The COM TX port transmits the combined power from all the directions or add drop ports
towards the amplifier.
COM-RX— The COM RX port receives the optical signal from the pre-amplifier and sends it to the
Note The COM-TX and COM-RX ports are not physical ports on the faceplate.
These ports are represented in CTC.
114
SMR20 FS and SMR20 FS CV Ports
LINE-TX— The booster amplifier amplifies the composite signal coming from WXC-MUX towards
the LINE-TX port.
LINE-RX— The pre amplifier amplifies the composite signal coming from the LINE-RX port towards
the WXC-DMX input.
SMR20 FS and SMR20 FS CV Ports

The SMR20 FS and SMR20 FS CV cards have these ports:
through channels to the other side of the NE. For example, in the four degrees setup, the EXP ports
can be used as drop Tx ports; EXP-Tx(1 to 4) are used as express channel from one side to other side.
The 5th to 20th EXP-Tx ports are used to transmit power to passive units.
EXP-RXi (where i = 1 to 20)—The EXP RX port receives the optical signal from the pass-through
channels. For example, in the four degrees setup, the EXP ports can be used as add Rx ports, EXP-
Rx(1 to 4) are used to receive power from the express channels from one side to other. The 5th to 20th
EXP-Rx ports are used to receive power from passive units.
OSC-TX— The OSC-TX port transmits the Service Channel signal received from the LINE-RX port
signal, separating it from the C-Band signals.
OSC-RX— The OSC-RX port receives signal from the Service Channel module and transmits it to the
LINE-TX port.
COM-TX—The COM TX port transmits the combined power from all the directions or add drop ports
towards the booster amplifier.
COM-RX— The COM RX port receives the optical signal from the pre-amplifier and sends it to the
Note The COM-TX and COM-RX ports are not physical ports on the faceplate.
These ports are represented in CTC.
LINE-TX— The booster amplifier amplifies the composite signal coming from WXC-MUX towards
the LINE-TX port.
LINE-RX— The pre amplifier amplifies the composite signal coming from the LINE-RX port towards
the WXC-DMX input.
Key Features
The multiplexer section of the 17 SMR9 FS, 24 SMR9 FS, 34 SMR9 FS, and SMR20 FS/SMR20 FS
CV cards provide the following features:
Selection of any arbitrary wavelength range from any EXP-RXi ports and routing to MUX output port.
Automatic VOA shutdown (AVS) blocking state on each wavelength on the MUX output port.
Per-channel (closed loop) power regulation on the MUX output port based on OCM block feedback.
115
Connection Verification
Per-channel (open loop) attenuation regulation on the MUX output port, which is not based on the OCM
feedback.
Amplification of the aggregated C-Band signal towards the LINE-TX port by the variable gain booster
EDFA amplifier.
Combination of C-Band signals with 1510 nm by OSC MUX filter.
Detection of the connectivity check signal, of wavelength 97 nm, by an embedded photodiode.
The demultiplexer section of the 17 SMR9 FS, 24 SMR9 FS, 34 SMR9 FS, and SMR20 FS/SMR20 FS
CV cards provide the following features:
Selection of any arbitrary wavelength range and routing to any EXP-TXi port.
AVS blocking state on each wavelength, on any of the EXP-TXi ports.
Per-channel (closed loop) power regulation on the EXP-TXi output port based on OCM block feedback.
Per-channel (open loop) attenuation regulation on the EXP-TXi output port, which is not based on the
OCM feedback.
Amplification of the C-Band signals entering the LINE-RX port by the pre-amplifier.
Separation of C-Band signals from 1510 nm by OSC De-MUX filter.
Generation and transmission of the connectivity check signal into the DE-MUX input port.
The 17 SMR9 FS, 24 SMR9 FS, 34 SMR9 FS, and SMR20 FS cards also support count-based licensing.
For more information on licensing, see the Cisco ONS 15454 DWDM Licensing Configuration Guide.
Connection Verification
The SMR20 FS CV cards provide the connection verification feature. This feature measures power levels
and verifies the optical cables and patchcords in a node for:
Connectivity: Checks whether the cable is connected.
Insertion Loss: Checks whether the cable loss is within expected value.
A 1567 nm connectivity check signal is generated and transmitted into the DE-MUX input port by a
dedicated laser source. This signal, in turn, is detected by an embedded photo diode to complete the
verification. The highlights of this feature are:
It validates the SMR20 FS CV card connection with other nodes or local Add/Drop elements.
It detects any incorrect cabling of the ROADM network element.
It collects insertion losses of every possible optical path inside the network element, in order to predict
any possible failure.
It verifies the connection every six hours, by default. Refer to http://www.cisco.com/c/en/us/td/docs/
optical/15000r10_0/ncs/network_config/guide/b_ncs_network_configuration/b_ncs_network_
configuration_chapter_010000.html#task_8B1E0075021B4A7EBCAC85FD09C02AC8 for manual
validation of the SMR20 FS CV interconnections.
116
Connection Verification Prerequisites
Note In releases earlier to Release 10.8, the Connection Verification (CV) procedure aborts when the CV and circuit
creation procedures that use the same wavelength, run concurrently on CV enabled cards. The wavelength that
was used for CV is then auto-provisioned due to which the circuit creation uses a different wavelength.
Connection Verification Prerequisites

The connection verification works only if the following conditions are fulfilled:
Flex nodes must be present for the connection verification to work.
Loopback caps must be installed on all the unused ports of the passive modules.
At least one SMR20 FS CV card must be present in the node.
All sides of the node must have a SMR20 FS CV card to test all cables and patchcords.
All passive modules must be connected with an USB cable and associated, so that power readings can
be calculated.
Supported Cards
The cards that supports connection verification are as follow:
16-AD-FS
SMR20 FS CV
MF-DEG-5 and MF-DEG-5-CV
MF-MPO-16LC and MF-MPO-16LC-CV
MF-PPMESH8-5AD
MF-UPG-4 and MF-UPG-4-CV
100GC-CK-LC and 200G-CK-LC
Note • Other MXP and TXP cards support CV partially; these cards support the
CV for the patch cords belonging to paths going from TXP card trunk port
to SMR20-FS-CV EXP-RX ports and not for the patch cords belonging to
path in the opposite direction.
MF-DEG-5, MF-DEG-5-CV, MF-MPO-16LC, MF-MPO-16LC-CV,
MF-PPMESH8-5AD, MF-UPG-4, and MF-UPG-4-CV cards require
loopback caps on unused ports. The (-CV) version is shipped with
the loopback pre-installed.
Running the Connection Verification

The connection verification runs:
117
PIDs of 17 SMR9 FS, 24 SMR9 FS, 34 SMR9 FS, and SMR20 FS/SMR20 FS CV Cards
Automatically at these time intervals and events:

020 minutes after first shelf controller boot or reboot
1One minute after enabling the connection verification
2Ten minutes after new patch-cord creation or deletion (*)
3Ten minutes after new circuit creation or deletion (*)
4Every six hours
For manual execution of connection verification, refer to http://www.cisco.com/c/en/us/td/docs/optical/

15000r10_0/ncs/network_config/guide/b_ncs_network_configuration/b_ncs_network_configuration_
chapter_010000.html#task_8B1E0075021B4A7EBCAC85FD09C02AC8.
indicates that this condition occurs only after an automatic run is interrupted by the creation or deletion of
a circuit or a patch cord.
PIDs of 17 SMR9 FS, 24 SMR9 FS, 34 SMR9 FS, and SMR20 FS/SMR20 FS CV Cards
The following table lists the PIDs and descriptions of the 17 SMR9 FS, 24 SMR9 FS, 34 SMR9 FS,
and SMR20 FS/SMR20 FS CV cards.
PID Description
NCS2K-9-SMR17FS= 9 port Single Module ROADM - 0-17 dB Gain - Flex Spectrum
NCS2K-20-SMRFS= 20 port Single Module ROADM - Switchable Gain - Flex

Spectrum
NCS2K-20-SMRFS-CV= 20 port Single Module ROADM - Switchable Gain Flex

Spectrum with Connection Verification
NCS2K-9-SMR17FS-L= 9 port Single Module ROADM - 0-17 dB Gain - Licensed
NCS2K-20-SMRFS-L= 20 port Single Module ROADM - Switchable Gain - Flex

Spectrum - Licensed
L-NCS2K-SMR-FS= License PID to enable Flex Spectrum capability for the 17 SMR9
FS, 24 SMR9 FS, 34 SMR9 FS, and SMR20 FS cards. NCS
Flex package is required to use this license.
L-NCS2K-SMR-2P= License PID to enable two EXP-TX/EXP-RX ports on the 17

SMR9 FS, 24 SMR9 FS, or 34 SMR9 FS cards.
L-NCS2K-SMR-4P= License PID to enable four EXP-TX/EXP-RX ports on the

SMR20 FS card.
118
Related Procedures for 17 SMR9 FS, 24 SMR9 FS, 34 SMR9 FS, and SMR20 FS/SMR20 FS CV Cards
Related Procedures for 17 SMR9 FS, 24 SMR9 FS, 34 SMR9 FS, and SMR20 FS/SMR20 FS CV Cards
The following section lists procedures and tasks related to the configuration of the 17 SMR9 FS, 24
SMR9 FS, 34 SMR9 FS, and SMR20 FS/SMR20 FS CV cards:
DLP-G325 Changing Optical Amplifier Line Settings
DLP-G326 Changing Optical Amplifier Threshold Settings
DLP-G406 Changing Card Optical Channel Parameters for 40-WXC-C, 80-WXC-C, 16-WXC-FS, 17
SMR9 FS, 24 SMR9 FS, 34 SMR9 FS, SMR20 FS, or SMR20 FS CV Cards
DLP-G407 Changing the Optical Channel Thresholds for 40-WXC-C, 80-WXC-C, 16-WXC-FS, 17
SMR9 FS, 24 SMR9 FS, 34 SMR9 FS, SMR20 FS, or SMR20 FS CV Cards
DLP-G408 Changing Optical Line Parameters for 40-WXC-C, 80-WXC-C, 16-WXC-FS, 17 SMR9 FS,
24 SMR9 FS, 34 SMR9 FS, SMR20 FS, or SMR20 FS CV Cards
DLP-G409 Changing the Optical Line Thresholds for 40-WXC-C, 80-WXC-C, 16-WXC-FS, 17 SMR9
FS, 24 SMR9 FS, 34 SMR9 FS, SMR20 FS, or SMR20 FS CV Cards
DLP-G772 Viewing Wavelength Power for 16-WXC-FS, 17 SMR9 FS, 24 SMR9 FS, 34 SMR9 FS,
SMR20 FS, or SMR20 FS CV Card
DLP-G773 Creating a Flex Spectrum or ITU Circuit for 16-WXC-FS, 17 SMR9 FS, 24 SMR9 FS, 34
SMR9 FS, SMR20 FS, or SMR20 FS CV Card
DLP-G140 View Power Statistics for Optical Amplifier, 40-SMR1-C, 40-SMR2-C, 17 SMR9 FS, 24
SMR9 FS, 34 SMR9 FS, SMR20 FS, and SMR20 FS CV Cards
DLP-G141 View Optical Power Statistics for 32MUX-O, 32WSS, 32WSS-L, 32DMX-O,32DMX,
32DMX-L, 40-WSS-C, 40-WSS-CE, 40-WXC-C, 80-WXC-C, 16-WXC-FS, 17 SMR9 FS, 24 SMR9
FS, 34 SMR9 FS, SMR20 FS, SMR20 FS CV, 40-MUX-C, 40-DMX-C, and 40-DMX-CE Cards
MMU Card
The single-slot Mesh Multi-Ring Upgrade Module (MMU) card supports multiring and mesh upgrades for
ROADM nodes in both the C-band and the L-band. Mesh/multiring upgrade is the capability to optically
bypass a given wavelength from one section of the network or ring to another one without requiring 3R
regeneration. In each node, you need to install one east MMU and one west MMU. The card can be
installed in Slots 1 through 6 and 12 through 17.
The MMU has six types of ports:
EXP RX port: The EXP RX port receives the optical signal from the ROADM section available on the
NE.
EXP TX port: The EXP TX port sends the optical signal to the ROADM section available on the NE.
EXP-A RX port: The EXP-A RX port receives the optical signal from the ROADM section available on
other NEs or rings.
EXP-A TX port: The EXP-A TX port sends the optical signal to the ROADM section available on other
NEs or rings.
119
MMU Power Monitoring
COM TX port: The COM TX port sends the optical signal to the fiber stage section.
COM RX port: The COM RX port receives the optical signal from the fiber stage section.
For more information about the MMU card, see

http://www.cisco.com/en/US/prod/collateral/optical/ps5724/ps2006/ps5320/product_data_sheet0900aecd803fc502.html.
MMU Power Monitoring

Physical photodiodes P1 through P3 monitor the power for the MMU card. The returned power level values
are calibrated to the ports as shown in the following table. VP1 to VP3 are virtual photodiodes that have
been created by adding (by software computation) the relevant path insertion losses of the optical splitters
(stored in the module) to the real photodiode (P1 to P3) measurement.
Table 62: MMU Port Calibration
P1 1 (EXP-RX) EXP RX
P2 5 (EXP A-RX) EXP A RX
P3 6 (EXP A-TX) EXP A TX
VP1 2 (EXP-TX) EXP TX
VP2 4 (COM-TX) COM TX
VP3 3 (COM-RX) COM RX
Related Procedures for MMU Card

The following section lists procedures and tasks related to the configuration of the MMU card:
NTP-G149 Modifying the MMU Line Settings and PM Thresholds
120
CHAPTER 8
Provisioning Transponder and Muxponder Cards
This chapter describes transponder (TXP), muxponder (MXP), GE_XP, 10GE_XP, GE_XPE, 10GE_XPE,
ADM-10G, OTU2_XP, 100G-LC-C, 10x10G-LC, CFP-LC, 100G-CK-C, 100G-ME-C,100ME-CKC,
100GS-CK-LC, 400G-XP-LC, WSE, AR_MXP, AR_XP, and AR_XPE cards, as well as their associated
plug-in modules (Small Form-factor Pluggables [SFP, SFP+, XFP, CXP, or CFP module]). For card safety
and compliance information, see the Regulatory Compliance and Safety Information for Cisco ONS
Products document.
Note The cards and procedures described in this chapter are supported on the Cisco ONS 15454, Cisco ONS
15454 M6, Cisco ONS 15454 M2 platforms, unless noted otherwise.
Note In this chapter, “100G-LC-C card” refers to the 15454-M-100G-LC-C card. “10x10G-LC” refers to
the 15454-M-10x10G-LC card. “CFP-LC” refers to the 15454-M-CFP-LC card.
Note Cisco ONS 15454 DWDM supports IBM's 5G DDR (Double Data Rate) InfiniBand interfaces.
5G DDR InfiniBand is referred to as IB_5G.
Card Overview, on page 123

Interface Classes, on page 129
TXP_MR_10G Card, on page 140
TXP_MR_10E Card, on page 141
TXP_MR_2.5G and TXPP_MR_2.5G Cards, on page 145
40E-TXP-C and 40ME-TXP-C Cards, on page 148
MXP_2.5G_10G Card, on page 148
MXP_2.5G_10E Card, on page 150
121
MXP_2.5G_10E_C and MXP_2.5G_10E_L Cards, on page 153

MXP_MR_2.5G and MXPP_MR_2.5G Cards, on page 158
MXP_MR_10DME_C and MXP_MR_10DME_L Cards, on page 163
40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards, on page 170
GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards, on page 175
ADM-10G Card, on page 198
OTU2_XP Card, on page 215
TXP_MR_10EX_C Card, on page 223
MXP_2.5G_10EX_C card, on page 224
MXP_MR_10DMEX_C Card, on page 229
AR_MXP, AR_XP, and AR_XPE Cards, on page 236
100G-LC-C, 100G-ME-C, 100G-CK-C, 100GS-CK-LC, 100ME-CKC, and 200G-CK-LC Cards, on
page 257
10x10G-LC Card, on page 262
CFP-LC Card, on page 265
MR-MXP Card, on page 267
Key Features of 100G-LC-C, 100G-ME-C, 100G-CK-C, 100ME-CKC, 10x10G-LC, 100GS-CK-LC,
200G-CK-LC, CFP-LC, and MR-MXP Cards, on page 271
Functions and Features, on page 281
Related Procedures for 100G-LC-C, 100G-ME-C, 100G-CK-C, 100ME-CKC, 10x10G-LC, CFP-LC,
100GS-CK-LC, 200G-CK-LC, and MR-MXP Cards, on page 282
400G-XP-LC Card, on page 282
Supported MSM Configurations, on page 302
WSE Card, on page 303
MLSE UT, on page 309
SFP, SFP+, QSFP+, XFP, CXP, CFP, CFP2 and CPAK Modules, on page 310
NTP-G128 Managing Pluggable Port Modules, on page 310
Transponder and Muxponder Protection Topologies, on page 328
Path Diversion Support for Client Protection, on page 339
NTP-G33 Creating a Y-Cable Protection Group, on page 339
NTP-G199 Creating a Splitter Protection Group, on page 345
NTP-G198 Creating 1+1 Protection for Cards, on page 347
Thresholds, on page 349
Parameters, and Thresholds, on page 416
NTP-G333 Adding an ADM-10G Card to an Existing Topology, on page 445
NTP-G97 Modifying the 4x2.5G Muxponder Card Line Settings and PM Parameter Thresholds, on page
446
NTP-G99 Modifying the 2.5G Data Muxponder Card Line Settings and PM Parameter Thresholds, on
page 472
NTP-G148 Modifying the 10G Data Muxponder Card Line Settings and PM Parameter Thresholds, on
page 497
122
Card Overview
NTP-G293 Modifying the 40G Muxponder Card Line Settings and PM Parameter Thresholds, on page
508
NTP-G281 Managing the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Channel Group Settings,
on page 541
NTP-G283 Managing the Card CFM Settings, on page 553
NTP-G285 Managing the Card EFM Settings, on page 565
NTP-G287 Managing the Card REP Settings, on page 571
NTP-G165 Modifying the Ethernet, Line and PM Thresholds, on page 577
NTP-G237 Retrieving and Clearing MAC Addresses on SVLANs, on page 606
NTP-G311 Provisioning the Storm Control Settings, on page 608
NTP-G205 Enabling Link Integrity on a Card, on page 609
DLP-G289 Provisioning CVLAN Rate Limiting on a Card, on page 611
NTP-G208 Provisioning SVLAN Rate Limiting on a Card, on page 611
NTP-G204 Enabling IGMP Snooping on a Card, on page 614
NTP-G206 Enabling MVR on a Card, on page 616
NTP-G314 Adding a Card on FAPS Ring, on page 629
NTP-G197 Provisioning the OTU2_XP Card Line Settings, PM Parameters, and Thresholds, on page
632
NTP-G162 Changing the ALS Maintenance Settings, on page 662
NTP-G302 Configuring Loopback on a Card, on page 664
NTP-G299 Configuring Backplane Loopback on a Card, on page 666
NTP-G192 Forcing FPGA Update, on page 668
NTP-G196 Forcing FPGA Update on a Card in Protection Group, on page 669
NTP-G232 Enabling Error Decorrelator, on page 670
NTP-G315 Enabling the Wavelength Drifted Channel Automatic Shutdown Feature, on page 671
NTP-G316 Enabling REP and FAPS on the Same Port, on page 671
NTP-G321 Provisioning Multiple Operating Modes, on page 672
NTP-G322 Modifying the Card Line Settings and PM Parameter Thresholds, on page 673
NTP-G235 Provisioning an Operating Mode, on page 708
NTP-G361 Provisioning an Operating Mode on the 400G-XP-LC Card, on page 709
NTP-G362 Manual FPGA Upgrade on the 400G-XP-LC Card, on page 711
NTP-G366 Viewing the ODU Utilization for ODU Circuits, on page 712
NTP-G367 Provisioning Encryption on 400G-XP-LC Card, on page 713
NTP-G236 Modifying the 100G-LC-C, 100G-CK-C, 100G-ME-C, 100ME-CKC, 10x10G-LC, 100GS-
CK-LC, , 200G-CK-LC, CFP-LC, WSE, MR-MXP, or 400G-XP-LC Card Line Settings and PM
Parameter Thresholds, on page 718
NTP-G351 Retrieving MAC Addresses on MR-MXP Cards, on page 766
NTP-G338 Provisioning an Operating Mode on the WSE Card, on page 767
NTP-G339 Modifying the WSE Card Line Settings and PM Parameter Thresholds, on page 768
NTP-G340 Provisioning Encryption on the WSE and MR-MXP Cards, on page 784
NTP-G342 Provisioning FIPS and CC Mode, on page 793
NTP-G363 Provisioning LSE on Cards, on page 796
Card Overview
The card overview section lists the cards described in this chapter and provides compatibility information.
123
Card Compatibility
The purpose of a TXP, MXP, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, ADM-10G, OTU2_XP,
AR_MXP, AR_XP, or AR_XPE card is to convert the “gray” optical client interface signals into trunk
signals that operate in the “colored” dense wavelength division multiplexing (DWDM) wavelength range.
Client-facing gray optical signals generally operate at shorter wavelengths, whereas DWDM colored
optical signals are in the longer wavelength range (for example, 1490 nm = violet; 1510 nm = blue; 1530
nm = green; 1550 nm = yellow; 1570 nm = orange; 1590 nm = red; 1610 nm = brown). Some of the newer
client-facing PPMs, however, operate in the colored region. Transponding or muxponding is the process of
converting the signals between the client and trunk wavelengths.
An MXP generally handles several client signals. It aggregates, or multiplexes, lower rate client signals
together and sends them out over a higher rate trunk port. Likewise, it demultiplexes optical signals coming
in on a trunk and sends them out to individual client ports. A TXP converts a single client signal to a single
trunk signal and converts a single incoming trunk signal to a single client signal. GE_XP, 10GE_XP,
GE_XPE, and 10GE_XPE cards can be provisioned as TXPs, as MXPs, or as Layer 2 switches.
All of the TXP and MXP cards perform optical to electrical to optical (OEO) conversion. As a result,
they are not optically transparent cards. The reason for this is that the cards must operate on the signals
passing through them, so it is necessary to do an OEO conversion.
On the other hand, the termination mode for all of the TXPs and MXPs, which is done at the electrical
level, can be configured to be transparent. In this case, neither the Line nor the Section overhead is
terminated. The cards can also be configured so that either Line or Section overhead can be terminated, or
both can be terminated.
Note The MXP_2.5G_10G card, by design, when configured in the transparent termination mode, actually
does terminate some of the bytes. See "Termination Modes" section for details.
Card Compatibility
Table 63: Platform and Software Release Compatibility for Transponder and Muxponder Cards
Card Name R4.5 - R4.6 R4.7 - R6.0 R7.0 R7.2 R8.0 - R8.5 R9.0 R9.
TXP_MR_10G 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWDM 154
TXP_MR_10E No 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWDM 154
TXP_MR_10E_C No No 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWDM 154
TXP_MR_10E_L No No 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWDM 154

TXP_MR_2.5G and 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWDM 154
TXPP_MR_2.5G
MXP_2.5G_10G 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWDM 154
MXP_2.5G_10E No 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWDM 154
MXP_2.5G_10E_C No No 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWDM 154
MXP_2.5G_10E_L No No 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWDM 154
124
Card Compatibility
Card Name R4.5 - R4.6 R4.7 - R6.0 R7.0 R7.2 R8.0 - R8.5 R9.0
MXP_MR_2.5G and No 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWDM

MXPP_MR_2.5G
MXP_MR_10DME_C No No 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWDM
MXP_MR_10DME_L No No 15454-DWDM 15454-DWDM 15454-DWDM 15454-DWDM
GE_XP and 10GE_XP No No No No 15454-DWDM 15454-DWDM
GE_XPE and No No No No No 15454-DWDM

10GE_XPE
ADM-10G No No No No 15454-DWDM 15454-DWDM
OTU2_XP No No No No No 15454-DWDM
TXP_MR_10EX_C, No No No No No No
MXP_2.5G_10EX_C,
and
MXP_MR_10DMEX_C
40E-TXP-C, No No No No No No
40ME-TXP-C,
40E-MXP-C, and
40ME-MXP-C
40E-MXP-C No No No No No No
40G-MXP-C No No No No No No
AR_XP No No No No No No
AR_MXP and No No No No No No
AR_XPE
100G-LC-C, No No No No No No
100G-ME-C,
10x10G-LC, and
100GS-CK-LC
CFP-LC No No No No No No
WSE No No No No No No
100G-CK-LC, No No No No No No
100ME-CK-LC, and
400G-XP-LC
125
Card Compatibility
Table 64: Platform and Software Release Compatibility for Transponder and Muxponder Cards
R9.2 R9.2.1 R9.3 R9.4 R9.6.x R9.8 R10.3 R10.5 R10.5.2 R10.6.1/10.6.2 R10.7
Card R10.0 R10.1
Name /10.8/10.9
TXP_MR_10G DW154-DM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM
TXP_MR_10E DW154-DM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM, 15454D-WDM, 15454D-WDM,
NCS NCS NCS
2015 2015 2015
TXPMR10EC 15454M-2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2,
15454M-6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6,
DW154-DM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM
TXP_MR_10E_L DW154-DM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM
TXP_MR_25G. 15454M-2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2,
and 15454M-6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6,
TXPP_MR_25G. DW154-DM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM
MXP_25G._10G DW154-DM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM
MXP_25G._10E DW154-DM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM
MXP_2.5G_10E_C 15454M-2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2,
15454M-6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6,
MXP_25G._10E_L DW154-DM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM
MXP_MR_25G. 15454M-2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2,
MXPMR5G2. DW154-DM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM
MXPMR10DMEC 15454M-2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2,
15454M-6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6,
(From
R10.8)
NCS
2015
MXPMR10DMEL DW154-DM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM
GE_XP 15454M-2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2,
10GE_XP DW154-DM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM
(From
R10.8)
NCS
2015
126
Card Compatibility
Card R9.2 R9.2.1 R9.3 R9.4 R9.6.x R9.8 R10.0 R10.1 R10.3 R10.5 R10.5.2 R10.6.1/10.6.2 R10.7
Name /10.8/10.9
GE_XPE 15454M-2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2,
10GE_XPE DW154-DM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM
(From
R10.8)
NCS
2015
ADM-10G 15454M-2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2,
15454M-6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6,
OTU2_XP 15454M-2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454D-WDM, 15454D-WDM, 15454D-WDM,
15454M-6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M2, 15454-M2, 15454-M2,
DW154-DM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454-M6, 15454-M6, 15454-M6,
NCS NCS NCS
2015 2015 2015
TXPMR10EXC, 15454M-2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2,
MXP5G2.10EXC, 15454M-6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6,
and DW154-DM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM
MXPMR10DMEXC
40E-TXP-C, No 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2,
40ME-TXP-C, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6,
40E-MXP-C, 154D-WDM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454D-WDM
and
40ME-MXP-C
40E-MXP-C No 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454D-WDM, 15454D-WDM, 15454D-WDM,
15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M2, 15454-M2, 15454-M2,
154D-WDM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 154D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454-M6, 15454-M6, 15454-M6,
NCS NCS NCS
2015 2015 2015
40G-MXP-C 15454M-2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2,
15454M-6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6,
AR_XP No No No 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454D-WDM, 15454D-WDM, 15454D-WDM,
15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M2, 15454-M2, 15454-M2,
154D-WDM 154D-WDM 154D-WDM 154D-WDM 15454D-WDM 15454D-WDM 15454D-WDM 15454-M6, 15454-M6, 15454-M6,
NCS NCS NCS
2015 2015 2015
127
Card Compatibility
Card R9.2 R9.2.1 R9.3 R9.4 R9.6.x R9.8 R10.0 R10.1 R10.3 R10.5 R10.5.2 R10.6.1/10.6.2 R10.7
Name /10.8/10.9
AR_MXP No No No No 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2,
and 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6, 15454-M6,
AR_XPE 154D-WDM 154D-WDM 154D-WDM 15454D-WDM 15454D-WDM 15454D-WDM, 15454D-WDM, 15454D-WDM, 15454D-WDM,
NCS NCS NCS NCS
2015 2015 2015 2015
100G-LC-C, No No No No 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2,
100G-ME-C, 15454-M6 15454-M6 15454-M6 15454-M6 15454-M6 15454-M6, 15454-M6, 15454-M6, 15454-M6,
and NCS NCS NCS NCS
10x10G-LC 2015 2015 2015 2015
CFP-LC No No No No 15454-M6 15454-M6 15454-M6 15454-M6 15454-M6 15454-M6 15454-M6, 15454-M6, 15454-M6,
NCS NCS NCS
2015 2015 2015
WSE No No No No No 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2,

15454-M6 15454-M6 15454-M6 15454-M6 15454-M6, 15454-M6, 15454-M6, 15454-M6,
NCS NCS NCS NCS
2015 2015 2015 2015
100GS-CK-LC No No No No No No No 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2,

15454-M6 15454-M6 15454-M6, 15454-M6, 15454-M6, 15454-M6,
NCS NCS NCS NCS
2015 2015 2015 2015
200G-CK-LC No No No No No No No No 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2,

15454-M6 15454-M6, 15454-M6, 15454-M6, 15454-M6,
NCS NCS NCS NCS
2015 2015 2015 2015
MR-MXP No No No No No No No No 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2,

15454-M6 15454-M6, 15454-M6, 15454-M6, 15454-M6,
NCS NCS NCS NCS
2015 2015 2015 2015
100ME-CKC No No No No No No 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2,

15454-M6 15454-M6 15454-M6 15454-M6, 15454-M6, 15454-M6, 15454-M6,
NCS NCS NCS NCS
2015 2015 2015 2015
100G-CK-C No No No No No No 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2, 15454-M2,

15454-M6 15454-M6 15454-M6 15454-M6, 15454-M6, 15454-M6, 15454-M6,
NCS NCS NCS NCS
2015 2015 2015 2015
400G-XP-LC No No No No No No No No No No No 15454-M6 15454-M2,

and 15454-M6
NCS and
2015 NCS
2015
128
Safety Labels
Version Number Compatibility for Transponder and Muxponder Cards

Older versions of the TXP_MR_10E_C, TXP_MR_2.5G, TXPP_MR_2.5G, and MXP_2.5G_10E_C cards
cannot be installed in the Cisco ONS 15454 M2 and Cisco ONS 15454 M6 shelves because of an
incompatible backplane connector.
The following table describes the version numbers of the cards that are compatible with the Cisco ONS
15454 M2 and Cisco ONS 15454 M6 shelves. The version numbers can be viewed from the HW Rev field
in the Inventory tab.
Table 65: Version Number Compatibility
Card Version Number

TXP_MR_2.5G Version 06 or later of the different unit part number
TXPP_MR_2.5G Version 06 or later of the different unit part number

MXP_2.5G_10E_C Version 04 or later of the 800-26774 part number
TXP_MR_10E_C Version 04 or later of the 800-26772 part number
Safety Labels
For information about safety labels, see the "Safety Labels" section.
Interface Classes
The input interface cards have been grouped in classes listed in the following table. The subsequent
tables list the optical performance and output power of each interface class.
Table 66: Card Interfaces Assigned to Input Power Classes
Input Power Class Card
A 10-Gbps multirate transponder cards (TXP_MR_10G,

TXP_MR_10E, TXP_MR_10E_C, and
TXP_MR_10E_L) with forward error correction
(FEC) enabled, 10-Gbps muxponder cards
(MXP_2.5G_10G, MXP_2.5G_10E,
MXP_MR_10DME_C, MXP_MR_10DME_L,
MXP_2.5G_10E_C, and MXP_2.5G_10E_L) with
FEC enabled, 40-Gbps transponder cards
(40E-TXP-C, and 40ME-TXP-C), and 40-Gbps
muxponder cards (40G-MXP-C, 40E-MXP-C, and
40ME-MXP-C)
129
Interface Classes
B 10-Gbps multirate transponder card (TXP_MR_10G)

without FEC and the 10-Gbps muxponder card
(MXP_2.5G_10G, MXP_MR_10DME_C,
MXP_MR_10DME_L), 40-Gbps transponder cards
(40E-TXP-C, and 40ME-TXP-C), and 40-Gbps
muxponder cards (40G-MXP-C, 40E-MXP-C, and
40ME-MXP-C), and ADM-10G cards with FEC
disabled
C OC-192 LR ITU cards without FEC, 10-Gbps

multirate transponder (TXP_MR_10E,
TXP_MR_10E_C, and TXP_MR_10E_L) and
muxponder (MXP_2.5G_10E, MXP_2.5G_10E_L,
and MXP_MR_10DME_L) cards with FEC disabled
D 2.5-Gbps multirate transponder card

(TXP_MR_2.5G), both protected and unprotected,
with FEC enabled
E OC-48 100-GHz dense wavelength division

multiplexing (DWDM) muxponder card
(MXP_MR_2.5G) and 2.5-Gbps multirate transponder
card (TXP_MR_2.5G), protected or unprotected; FEC
disabled; and retime, reshape, and regenerate (3R)
mode enabled
F 2.5-Gbps multirate transponder card

(TXP_MR_2.5G), protected or unprotected, in
regenerate and reshape (2R) mode
G OC-48 ELR 100 GHz card
H 2/4 port GbE transponder (GBIC WDM 100GHz)
I 10-Gbps multirate transponder cards (TXP_MR_10E,

TXP_MR_10E_C, and TXP_MR_10E_L) and
10-Gbps muxponder cards (MXP_2.5G_10E,
MXP_2.5G_10E_L, and MXP_MR_10DME_L) with
enhanced FEC (E-FEC) enabled, 40-Gbps transponder
cards (40E-TXP-C, and 40ME-TXP-C), and 40-Gbps
muxponder cards (40G-MXP-C, 40G-MXP-C,
40E-MXP-C, and 40ME-MXP-C) with E-FEC enabled
K OC-192/STM-64 LR ITU cards without FEC, 100GHz

10Gbps Ethernet Xponder (GE_XP, GE_XPE,
10GE_XP, 10GE_XPE), Sonet/SDH add/drop
(ADM_10G), OTU2 Xponder (OTU2_XP), with FEC
disabled
L 40Gbps Duobinary CRS-1 DWDM ITU-T line card
130
Interface Classes
M 2.5 Gbps DWDM ITU-T SPF
N 10Gbps enhanced full tunable transponder

(TXP_MR_10E_C) and muxponder
(MXP_2.5G_10E_C, MXP_MR_10DME_C) with
E-FEC enabled
O 10Gbps Ethernet Xponder (GE_XP, GE_XPE,

10GE_XP, 10GE_XPE), 10Gbps Sonet/SDH add/drop
enabled
P 10Gbps Ethernet Xponder (GE_XP, GE_XPE,

10GE_XP, 10GE_XPE), 10Gbps Sonet/SDH add/drop
(ADM_10G), OTU2 Xponder (OTU2_XP), with
E-FEC enabled
T 40Gbps DPSK CRS-1 DWDM ITU-T line card
V OC-192/STM-64 LR ITU cards without FEC, full

tunable 10Gbps Ethernet Xponder (GE_XP, GE_XPE,
disabled, full tunable
W 10Gbps Ethernet Xponder (GE_XP, GE_XPE,

enabled, full tunable
X 10Gbps Ethernet Xponder (GE_XP, GE_XPE,

(ADM_10G), OTU2 Xponder (OTU2_XP), with
E-FEC enabled, full tunable
Y 10Gbps enhanced full tunable transponder

(TXP_MR_10EX_C) and muxponder
(MXP_2.5G_10EX_C, MXP_MR_10DMEX_C),
with FEC enabled and maximum likelihood sequence
estimator (MLSE) correction
Z 10Gbps enhanced full tunable transponder

(TXP_MR_10EX_C) and muxponder
(MXP_2.5G_10EX_C, MXP_MR_10DMEX_C),
with E-FEC enabled and MLSE correction
131
Interface Classes
Table 67: 40-Gbps Interface Optical Performance
Limited (if appl.) Limited (if appl.) Limited (if appl.)
OSNR =
optical
signal-to-noise
ratio
Maximum bit 40 Gbps 40 Gbps 40 Gbps

rate
FEC Yes No Yes (E-FEC)
Threshold Optimum Average Optimum
Maximum 10–15 10–12 10–15

BER
BER = bit
error rate
sensitivity
OSNR =
optical
signal-to-noise
ratio
sensitivity
overload
Transmitted Power Range—These values, decreased by patchcord and connector losses, are also the
input power values for the OADM cards.
40-Gbps +2.5 to 3.5 dBm +2.5 to 3.5 dBm —

multirate
transponder/40-Gbps
FEC
transponder
(40E-TXP-C,
and
40ME-TXP-C)
OC-192 LR — — —
ITU
132
Interface Classes
Limited (if appl.) Limited (if appl.) Limited (if appl.)
OSNR =
optical
signal-to-noise
ratio
Dispersion +/–800 ps/nm +/–1,000 ps/nm +/–800 ps/nm

compensation
tolerance
Table 68: 10-Gbps Interface Optical Performance (Class A, B, C, I, and K)
Parameter Class A Class B Class C Class I Class K
Type Power OSNR Power OSNR Power OSNR Power OSNR Power OSNR
Maximum 10 Gbps 10 Gbps 10 Gbps 10 Gbps 10 Gbps

bit rate
Regeneration 3R 3R 3R 3R 3R
FEC Yes No No Yes (E-FEC) No
Threshold Optimum Average Average Optimum Average
Maximum 10–15 10–12 10–12 10–15 10–12

BER
133
Interface Classes
OSNR 23 dB 8.5 dB 23 dB 19 dB 19 dB 19 dB 20 dB 23 dB 16 dB3

sensitivity 6 dB This
value is
for Xen
Pak
XFP
used
with
Catalyst
card.
23 dB 17 dB4
This
value is
for XFP
used
with
Catalyst,
Xponder,
and
ADM-10G
cards.
23 dB 17 dB5
This
value is
for X2
XFP
used
with
Catalyst
card.
Power –24 –18 –21 –20 –22 –22 –26 –18 –24 –17
sensitivity dBm dBm dBm dBm dBm dBm dBm dBm dBm3 dBm3
–23 –18
dBm4 dBm4
–23 –17
dBm5 dBm5
Power –8 dBm –8 dBm –9 dBm –8 dBm –7 dBm
overload
134
Interface Classes
input power values for the optical add drop multiplexer (OADM) cards.
10-Gbps +2.5 to 3.5 dBm +2.5 to 3.5 dBm +3.0 to 6.0 dBm +3.0 to 6.0 dBm —
multirate (for
transponder TXP_MR_10G)
/10-Gbps +3.0 to 6.0 dBm
FEC
(for
transponder TXP_MR_10E)
OC-192 — — +3.0 to 6.0 dBm — –1.0 to +3.0 dBm

LR ITU
10-Gbps — — — — –1.0 to +3.0 dBm

Ethernet
Xponder,
Sonet/SDH
Add/Drop,
OTU2
Xponder
Dispersion +/–800 ps/nm +/–1,000 ps/nm +/–1,000 ps/nm +/–800 ps/nm –400 to +800
compensation ps/nm
tolerance
Table 69: 10-Gbps Interface Optical Performance (Class N, O, P, and V)
Parameter Class N Class O Class P Class V
Type Power OSNR Power OSNR Power OSNR Power OSNR

Limited Limited Limited Limited Limited Limited Limited Limited

bit rate
FEC Yes (E-FEC) Yes Yes (E-FEC) No
Threshold Optimum Optimum Optimum Average
Maximum 10–15 10–15 10–15 10–12

BER
OSNR 19 dB 5 dB 11 dB 11 dB 23 dB 8 dB 23 dB 16 dB
sensitivity
135
Interface Classes
Parameter Class N Class O Class P Class V

Power –27 dBm –20 dBm –18 dBm –18 dBm –27 dBm –18 dBm –24 dBm –18 dBm
sensitivity
overload
10-Gbps +3.0 to 6.0 dBm — — —

multirate
transponder/10-Gbps
FEC
transponder
OC-192 — — — 0 to +3.0 dBm

LR ITU
10-Gbps — –1.0 to +3.0 dBm –1.0 to +3.0 dBm 0 to +3.0 dBm

Ethernet
Xponder,
Sonet/SDH
Add/Drop,
OTU2
Xponder
Dispersion +/–800 ps/nm –500 to +1100 ps/nm –500 to +1100 ps/nm –500 to +1600 ps/nm
compensation
tolerance
Table 70: 10-Gbps Interface Optical Performance (Class W, X, Y, and Z)
Parameter Class W Class X Class Y Class Z


bit rate
FEC Yes Yes (E-FEC) Yes Yes (E-FEC)
Threshold Optimum Optimum Optimum Optimum
Maximum 10–15 10–15 10–15 10–15

BER
136
Interface Classes
Parameter Class W Class X Class Y Class Z

OSNR 8.5 dB 8.5 dB 19 dB 5 dB 23 dB 8 dB 19 dB 5.5 dB

sensitivity
Power –18 dBm –18 dBm –27 dBm –20 dBm –24 dBm –20 dBm –27 dBm –20 dBm
sensitivity
overload
10-Gbps — — +3.0 to 6.0 dBm +3.0 to 6.0 dBm

multirate
transponder/10-Gbps
FEC
transponder
OC-192 — — — —
LR ITU
10-Gbps 0 to +3.0 dBm 0 to +3.0 dBm — —

Ethernet
Xponder,
Sonet/SDH
Add/Drop,
OTU2
Xponder
Dispersion –500 to +1100 ps/nm –500 to +1300 ps/nm –800 to +1600 ps/nm –2200 to +3700 ps/nm
compensation
tolerance
Table 71: 2.5-Gbps Interface Optical Performance (Class D, E, and F)
Parameter Class D Class E Class F
Maximum bit 2.5 Gbps 2.5 Gbps 2.5 Gbps

rate
FEC Yes No No
Threshold Average Average Average
137
Interface Classes
Parameter Class D Class E Class F
Maximum 10–15 10–12 10–12

BER
sensitivity
sensitivity
overload
TXP_MR_2.5G –1.0 to 1.0 dBm –1.0 to 1.0 dBm –1.0 to 1.0 dBm
and
TXPP_MR_2.5G
MXP_MR_2.5G — +2.0 to +4.0 dBm —

and
MXPP_MR_2.5G
OC-48 ELR — — —
100 GHz
2/4 port GbE — — —

Transponder
(GBIC WDM
100GHz)
2.5 Gbps — — —
DWDM
ITU-T SPF
Dispersion –1200 to +5400 ps/nm –1200 to +5400 ps/nm –1200 to +3300 ps/nm
compensation
tolerance
Table 72: 2.5-Gbps Interface Optical Performance (Class G, H, and M)
Parameter Class G Class H Class M
Maximum bit 2.5 Gbps 1.25 Gbps 2.5 Gbps

rate
138
Interface Classes
Parameter Class G Class H Class M
FEC No No No
Threshold Average Average Average
Maximum 10–12 10–12 10–12

BER
sensitivity
sensitivity
overload
Transmitted Power Range—These values, decreased by patchcord and
connector losses, are also the input power values for the optical add drop
multiplexer (OADM) cards.
TXP_MR_2.5G — — —
TXPP_MR_2.5G —
MXP_MR_2.5G –2.0 to 0 dBm
MXPP_MR_2.5G —
OC-48 ELR — — —
100 GHz
2/4 port GbE –1200 to +3300 ps/nm 0 to +3 dBm —

Transponder
(GBIC WDM
100GHz)
2.5 Gbps — 0 to +4 dBm

DWDM
ITU-T SPF
Dispersion –1000 to +3600 ps/nm –800 to +2400 ps/nm

compensation
tolerance
139
TXP_MR_10G Card
TXP_MR_10G Card
The TXP_MR_10G card has reached end of support.
The TXP_MR_10G processes one 10-Gbps signal (client side) into one 10-Gbps, 100-GHz DWDM signal
(trunk side). It provides one 10-Gbps port per card that can be provisioned for an STM-64/OC-192 short
reach (1310-nm) signal, compliant with ITU-T G.707, ITU-T G.709, ITU-T G.691, and Telcordia GR-253-
CORE, or a 10GBASE-LR signal compliant with IEEE 802.3.
The TXP_MR_10G card is tunable over two neighboring wavelengths in the 1550-nm, ITU 100-GHz
range. It is available in 16 different versions, each of which covers two wavelengths, for a total coverage of
32 different wavelengths in the 1550-nm range.
Note ITU-T G.709 specifies a form of forward error correction (FEC) that uses a “wrapper” approach. The
digital wrapper lets you transparently take in a signal on the client side, wrap a frame around it and restore
it to its original form. FEC enables longer fiber links because errors caused by the optical signal degrading
with distance are corrected.
The trunk port operates at 9.95328 Gbps (or 10.70923 Gbps with ITU-T G.709 Digital Wrapper/FEC) and
at 10.3125 Gbps (or 11.095 Gbps with ITU-T G.709 Digital Wrapper/FEC) over unamplified distances up
to 80 km (50 miles) with different types of fiber such as C-SMF or dispersion compensated fiber limited by
loss and/or dispersion.
Caution Because the transponder has no capability to look into the payload and detect circuits, a TXP_MR_10G
card does not display circuits under card view.
Caution You must use a 15-dB fiber attenuator (10 to 20 dB) when working with the TXP_MR_10G card in a
loopback on the trunk port. Do not use direct fiber loopbacks with the TXP_MR_10G card. Using direct
fiber loopbacks causes irreparable damage to the TXP_MR_10G card.
You can install TXP_MR_10G cards in Slots 1 to 6 and 12 to 17 and provision this card in a linear configuration.
TXP_MR_10G cards cannot be provisioned as a bidirectional line switched ring (BLSR)/Multiplex Section
Shared Protection Ring (MS-SPRing), a path protection/subnetwork connection protection (SNCP), or a
regenerator. They can only be used in the middle of BLSR/MS-SPRing and 1+1 spans when the card is
configured for transparent termination mode.
The TXP_MR_10G port features a 1550-nm laser for the trunk port and a 1310-nm laser for the for the
client port and contains two transmit and receive connector pairs (labeled) on the card faceplate.
The MTU setting is used to display the OverSizePkts counters on the receiving trunk and client port
interfaces. Traffic of frame sizes up to 65535 bytes pass without any packet drops, from the client port to
the trunk port and vice versa irrespective of the MTU setting.
The TXP_MR_10G card has the following available wavelengths and versions:
• ITU grid blue band:
140
Related Procedures for TXP_MR_10G Card
1538.19 to 1538.98 nm, 10T-L1-38.1

1539.77 to 1540.56 nm, 10T-L1-39.7
1530.33 to 1531.12 nm, 10T-L1-30.3
1531.90 to 1532.68 nm, 10T-L1-31.9
1534.25 to 1535.04 nm, 10T-L1-34.2
1535.82 to 1536.61 nm, 10T-L1-35.8
1542.14 to 1542.94 nm, 10T-L1-42.1
1543.73 to 1544.53 nm, 10T-L1-43.73
ITU grid red band:

1554.13 to 1554.94 nm, 10T-L1-54.1
1555.75 to 1556.55 nm, 10T-L1-55.7
1546.12 to 1546.92 nm, 10T-L1-46.1
1547.72 to 1548.51 nm, 10T-L1-47.7
1550.12 to 1550.92 nm, 10T-L1-50.1
1551.72 to 1552.52 nm, 10T-L1-51.7
1558.17 to 1558.98 nm, 10T-L1-58.1
1559.79 to 1560.61 nm, 10T-L1-59.7
For more information about the TXP_MR_10G card, see
http://www.cisco.com/en/US/prod/collateral/optical/ps5724/ps2006/ps5320/product_data_sheet0900aecd80121bf7_ps13234_Products_Data_Sheet.html.
Related Procedures for TXP_MR_10G Card

The following is the list of procedures and tasks related to the configuration of the TXP_MR_10G card:
NTP-G75 Monitor Transponder and Muxponder Performance
TXP_MR_10E Card
The card is fully backward compatible with the TXP_MR_10G card. It processes one 10-Gbps signal (client
side) into one 10-Gbps, 100-GHz DWDM signal (trunk side) that is tunable over four wavelength channels
(spaced at 100 GHz on the ITU grid) in the C band and tunable over eight wavelength channels (spaced at 50
GHz on the ITU grid) in the L band. There are eight versions of the C-band card, with each version covering
141
TXP_MR_10E Functions
four wavelengths, for a total coverage of 32 wavelengths. There are five versions of the L-band card,
with each version covering eight wavelengths, for a total coverage of 40 wavelengths.
You can install TXP_MR_10E cards in Slots 1 to 6 and 12 to 17 in ONS 15454 DWDM chassis, Slots 2
and 3 in ONS 15454 M2 chassis, Slots 2 to 7 in ONS 15454 M6, Slots 2 to 16 in Cisco NCS 2015 chassis
and provision the cards in a linear configuration, BLSR/MS-SPRing, path protection/SNCP, or a
regenerator. The card can be used in the middle of BLSR/MS-SPRing or 1+1 spans when the card is
The TXP_MR_10E card features a 1550-nm tunable laser (C band) or a 1580-nm tunable laser (L band) for
the trunk port and ONS-XC-10G-S1 1310-nm or ONS-XC-10G-L2 1550-nm laser XFP module for the
client port that can be ordered separately.
Note When the ONS-XC-10G-L2 XFP is installed, the TXP_MR_10E card must be installed in Slots 6, 7, 12, or
13 in the ONS 15454 chassis.
On its faceplate, the TXP_MR_10E card contains two transmit and receive connector pairs, one for the
trunk port and one for the client port. Each connector pair is labeled.
Key Features
The key features of the TXP_MR_10E card are:
A tri-rate client interface (available through the ONS-XC-10G-S1 XFP, ordered separately)
OC-192 (SR1)
10GE (10GBASE-LR)
10G-FC (1200-SM-LL-L)
IB_5G
OC-192 to ITU-T G.709 OTU2 provisionable synchronous and asynchronous mapping

interfaces. Traffic of frame sizes up to 65535 bytes pass without any packet drops, from the client
port to the trunk port and vice versa irrespective of the MTU setting.
TXP_MR_10E Functions
The following functions of the TXP_MR_10E card are explained in "Card Features" chapter:
Client Interface
DWDM Trunk Interface
FEC
Client-to-Trunk Mapping
For more information about the TXP_MR_10E card, see
http://www.cisco.com/en/US/prod/collateral/optical/ps5724/ps2006/ps5320/product_data_sheet0900aecd803fc3e8_ps13234_Products_Data_Sheet.html.
142
Related Procedures for TXP_MR_10E Card
Related Procedures for TXP_MR_10E Card

The following is the list of procedures and tasks related to the configuration of the TXP_MR_10E card:
TXP_MR_10E_C and TXP_MR_10E_L Cards

The TXP_MR_10E_C and TXP_MR_10E_L cards are fully backward compatible with the TXP_MR_10G
and TXP_MR_10E cards. They processes one 10-Gbps signal (client side) into one 10-Gbps, 100-GHz
DWDM signal (trunk side). The TXP_MR_10E_C is tunable over the entire set of C-band wavelength
channels (82 channels spaced at 50 GHz on the ITU grid). The TXP_MR_10E_L is tunable over the entire
set of L-band wavelength channels (80 channels spaced at 50 GHz on the ITU grid) and is particularly well
suited for use in networks that employ DS fiber or SMF-28 single-mode fiber.
The advantage of these cards over previous versions (TXP_MR_10G and TXP_MR_10E) is that there is
only one version of each card (one C-band version and one L-band version) instead of several versions
needed to cover each band.
You can install TXP_MR_10E_C and TXP_MR_10E_L cards in Slots 1 to 6 and 12 to 17 in ONS 15454
DWDM chassis, Slot 2 in ONS 15454 M2 chassis, Slots 2 to 6 in ONS 15454 M6 and provision the cards
in a linear configuration, BLSR/MS-SPRing, path protection/SNCP, or a regenerator. The cards can be
used in the middle of BLSR/MS-SPRing or 1+1 spans when the cards are configured for transparent
termination mode.
The TXP_MR_10E_C and TXP_MR_10E_L cards feature a universal transponder 2 (UT2) 1550-nm
tunable laser (C band) or a UT2 1580-nm tunable laser (L band) for the trunk port and a separately
orderable ONS-XC-10G-S1 1310-nm or ONS-XC-10G-L2 1550-nm laser XFP module for the client port.
Note When the ONS-XC-10G-L2 XFP is installed, the TXP_MR_10E_C or TXP_MR_10E-L card is required to
be installed in a high-speed slot (slot 6, 7, 12, or 13).
On its faceplate, the TXP_MR_10E_C and TXP_MR_10E_L cards contain two transmit and receive
connector pairs, one for the trunk port and one for the client port. Each connector pair is labeled.
Key Features
The key features of the TXP_MR_10E_C and TXP_MR_10E_L cards are:
A tri-rate client interface (available through the ONS-XC-10G-S1 XFP, ordered separately):
OC-192 (SR1)
10GE (10GBASE-LR)
10G-FC (1200-SM-LL-L)
143
Faceplates and Block Diagram
A UT2 module tunable through the entire C band (TXP_MR_10E_C card) or L band (TXP_MR_10E_L
card). The channels are spaced at 50 GHz on the ITU grid.
OC-192 to ITU-T G.709 OTU2 provisionable synchronous and asynchronous mapping.
For a detailed list of the supported pluggables, see,

http://www.cisco.com/c/en/us/td/docs/optical/spares/gbic/ guides/b_ons_pluggables.html

Figure 10: TXP_MR_10E_C and TXP_MR_10E_L Faceplates and Block Diagram
For information about safety labels for the cards, see the "Class 1M Laser Product Cards” section.
Caution You must use a 15-dB fiber attenuator (10 to 20 dB) when working with the TXP_MR_10E_C or
TXP_MR_10E_L card in a loopback on the trunk port. Do not use direct fiber loopbacks with the cards. Using
direct fiber loopbacks causes irreparable damage to the cards.
TXP_MR_10E_C and TXP_MR_10E_L Functions

The following functions of the TXP_MR_10E_C and TXP_MR_10E_L cards are explained in "Card Features"
chapter:
Automatic Laser Shutdown
Card level indicators
Port level indicators
Client Interface
144
Related Procedures for TXP_MR_10E_C and TXP_MR_10E_L Cards

FEC
Related Procedures for TXP_MR_10E_C and TXP_MR_10E_L Cards

The following is the list of procedures and tasks related to the configuration for both TXP_MR_10E_C and
TXP_MR_10E_L:
DLP-G358 Provisioning TXP_MR_10E_L and TXP_MR_10E_C Cards for Acceptance Testing
TXP_MR_2.5G and TXPP_MR_2.5G Cards

The TXP_MR_2.5G card processes one 8-Mbps to 2.488-Gbps signal (client side) into one 8-Mbps to 2.5-
Gbps, 100-GHz DWDM signal (trunk side). It provides one long-reach STM-16/OC-48 port per card,
compliant with ITU-T G.707, ITU-T G.709, ITU-T G.957, and Telcordia GR-253-CORE.
The TXPP_MR_2.5G card processes one 8-Mbps to 2.488-Gbps signal (client side) into two 8-Mbps to
2.5-Gbps, 100-GHz DWDM signals (trunk side). It provides two long-reach STM-16/OC-48 ports per card,
compliant with ITU-T G.707, ITU-T G.957, and Telcordia GR-253-CORE.
The TXP_MR_2.5G and TXPP_MR_2.5G cards are tunable over four wavelengths in the 1550-nm,
ITU 100-GHz range. They are available in eight versions, each of which covers four wavelengths, for a
total coverage of 32 different wavelengths in the 1550-nm range.
Note ITU-T G.709 specifies a form of FEC that uses a “wrapper” approach. The digital wrapper lets you transparently
take in a signal on the client side, wrap a frame around it, and restore it to its original form. FEC enables longer
fiber links because errors caused by the optical signal degrading with distance are corrected.
The trunk/line port operates at up to 2.488 Gbps (or up to 2.66 Gbps with ITU-T G.709 Digital
Wrapper/FEC) over unamplified distances up to 360 km (223.7 miles) with different types of fiber such as
C-SMF or higher if dispersion compensation is used.
Caution Because the transponder has no capability to look into the payload and detect circuits, a TXP_MR_2.5G or
TXPP_MR_2.5G card does not display circuits under card view.
The TXP_MR_2.5G and TXPP_MR_2.5G cards support 2R (retime, regenerate) and 3R (retime, reshape, and
regenerate) modes of operation where the client signal is mapped into a ITU-T G.709 frame. The mapping
145
TXP_MR_2.5G and TXPP_MR_2.5G Cards
function is simply done by placing a digital wrapper around the client signal. Only OC-48/STM-16 client
signals are fully ITU-T G.709 compliant, and the output bit rate depends on the input client signal. The
following table shows the possible combinations of client interfaces, input bit rates, 2R and 3R modes,
and ITU-T G.709 monitoring.
Table 73: 2R and 3R Mode and ITU-T G.709 Compliance by Client Interface
Client Interface Input Bit Rate 3R vs. 2R ITU-T G.709
OC-48/STM-16 2.488 Gbps 3R On or Off
DV-6000 2.38 Gbps 2R —
2 Gigabit Fibre Channel 2.125 Gbps 3R On or Off

(2G-FC)/fiber
No monitoring
connectivity (FICON)
High-Definition 1.48 Gbps 2R —

Television (HDTV)
Gigabit Ethernet (GE) 1.25 Gbps 3R On or Off

(1G-FC)/FICON
OC-12/STM-4 622 Mbps 3R On or Off
Enterprise System 200 Mbps 2R —

Connection (ESCON)
SDI/D1/DVB-ASI video 270 Mbps 2R —
ISC-1 Compat 1.06 Gbps 2R Off
ISC-3 1.06 or 2.125 Gbps 2R —
ETR_CLO 16 Mbps 2R —
Note ITU-T G.709 and FEC support is disabled for all the 2R payload types in the TXP_MR_2.5G and
TXPP_MR_2.5G cards.
The output bit rate is calculated for the trunk bit rate by using the 255/238 ratio as specified in ITU-T
G.709 for OTU1. The following table lists the calculated trunk bit rates for the client interfaces with ITU-T
G.709 enabled.
Table 74: Trunk Bit Rates With ITU-T G.709 Enabled
Client Interface ITU-T G.709 Disabled ITU-T G.709 Enabled
OC-48/STM-16 2.488 Gbps 2.66 Gbps
146
Related Procedures for TXP_MR_2.5G and TXPP_MR_2.5G Cards
Client Interface ITU-T G.709 Disabled ITU-T G.709 Enabled
2G-FC 2.125 Gbps 2.27 Gbps
GE 1.25 Gbps 1.34 Gbps
1G-FC 1.06 Gbps 1.14 Gbps
OC-12/STM-3 622 Mbps 666.43 Mbps
OC-3/STM-1 155 Mbps 166.07 Mbps
For 2R operation mode, the TXP_MR_2.5G and TXPP_MR_2.5G cards have the ability to pass data
through transparently from client side interfaces to a trunk side interface, which resides on an ITU grid. The
data might vary at any bit rate from 200-Mbps up to 2.38-Gbps, including ESCON, DVB-ASI, ISC-1, and
video signals. In this pass-through mode, no performance monitoring (PM) or digital wrapping of the
incoming signal is provided, except for the usual PM outputs from the SFPs. Similarly, this card has the
ability to pass data through transparently from the trunk side interfaces to the client side interfaces with bit
rates varying from 200-Mbps up to 2.38-Gbps. Again, no PM or digital wrapping of received signals is
available in this pass-through mode.
For 3R operation mode, the TXP_MR_2.5G and TXPP_MR_2.5G cards apply a digital wrapper to the
incoming client interface signals (OC-N/STM-N, 1G-FC, 2G-FC, GE). PM is available on all of these
signals except for 2G-FC, and varies depending upon the type of signal. For client inputs other than OC-
48/STM-16, a digital wrapper might be applied but the resulting signal is not ITU-T G.709 compliant. The
card applies a digital wrapper that is scaled to the frequency of the input signal.
The TXP_MR_2.5G and TXPP_MR_2.5G cards have the ability to take digitally wrapped signals in from
the trunk interface, remove the digital wrapper, and send the unwrapped data through to the client
interface. PM of the ITU-T G.709 OH and SONET/SDH OH is implemented.
You can install TXP_MR_2.5G and TXPP_MR_2.5G cards in Slots 1 to 6 and 12 to 17 in ONS 15454 DWDM
chassis, Slots 2 and 3 in ONS 15454 M2 chassis, Slots 2 to 7 in ONS 15454 M6. You can provision this card in a
linear configuration. TXP_MR_10G and TXPP_MR_2.5G cards cannot be provisioned as a BLSR/MS-SPRing,
a path protection/SNCP, or a regenerator. They can be used in the middle of BLSR/MS-SPRing or 1+1 spans
only when the card is configured for transparent termination mode.
The TXP_MR_2.5G card features a 1550-nm laser for the trunk/line port and a 1310-nm laser for the client
port. It contains two transmit and receive connector pairs (labeled) on the card faceplate. The card uses
dual LC connectors for optical cable termination.
The TXPP_MR_2.5G card features a 1550-nm laser for the trunk/line port and a 1310-nm or 850-nm laser
(depending on the SFP) for the client port and contains three transmit and receive connector pairs
(labeled) on the card faceplate. The card uses dual LC connectors for optical cable termination.
Related Procedures for TXP_MR_2.5G and TXPP_MR_2.5G Cards

The following is the list of procedures and tasks related to the configuration for both TXP_MR_2.5G and
TXPP_MR_2.5G:
147
40E-TXP-C and 40ME-TXP-C Cards
40E-TXP-C and 40ME-TXP-C Cards

The 40E-TXP-C and 40ME-TXP-C cards process a single 40-Gbps signal (client side) into a single 40-
Gbps, 50-GHz DWDM signal (trunk side). It provides one 40-Gbps port per card that can be provisioned
for an OC-768/STM-256 very short reach (1550-nm) signal compliant with ITU-T G.707, ITU-T G.691,
and Telcordia GR-253-CORE, 40G Ethernet LAN signal compliant with IEEE 802.3ba, or OTU3 signal
compliant with ITU-T G.709.
You can install and provision the 40E-TXP-C and 40ME-TXP-C cards in a linear configuration in:
Slots 1 to 5 and 12 to 16 in ONS 15454 DWDM chassis
Slot 2 in ONS 15454 M2 chassis
Slots 2 to 6 in ONS 15454 M6 chassis
When a protection switch occurs on the 40E-TXP-C, and 40ME-TXP-C cards, the recovery
from PSM protection switch takes about 3 to 4 minutes.
For more information about the 40E-TXP-C and 40ME-TXP-C cards, see
Related Procedures for 40E-TXP-C and 40ME-TXP-C Cards

The following is the list of procedures and tasks related to the configuration of 40E-TXP-C and 40ME-TXP-C:
MXP_2.5G_10G Card
The MXP_2.5G_10G card has reached end of support.
The MXP_2.5G_10G card multiplexes/demultiplexes four 2.5-Gbps signals (client side) into one 10-Gbps,
100-GHz DWDM signal (trunk side). It provides one extended long-range STM-64/OC-192 port per card
on the trunk side (compliant with ITU-T G.707, ITU-T G.709, ITU-T G.957, and Telcordia GR-253-
CORE) and four intermediate- or short-range OC-48/STM-16 ports per card on the client side. The port
operates at 9.95328 Gbps over unamplified distances up to 80 km (50 miles) with different types of fiber
such as C-SMF or dispersion compensated fiber limited by loss and/or dispersion.
Client ports on the MXP_2.5G_10G card are also interoperable with SONET OC48.
The MXP_2.5G_10G card is tunable over two neighboring wavelengths in the 1550-nm, ITU 100-GHz
range. It is available in 16 different versions, each of which covers two wavelengths, for a total coverage of
32 different wavelengths in the 1550-nm range.
148
Related Procedures for MXP_2.5G_10G Card

Note ITU-T G.709 specifies a form of FEC that uses a “wrapper” approach. The digital wrapper lets you transparently
take in a signal on the client side, wrap a frame around it and restore it to its original form. FEC enables longer
fiber links because errors caused by the optical signal degrading with distance are corrected.
The port can also operate at 10.70923 Gbps in ITU-T G.709 Digital Wrapper/FEC mode.
Caution Because the transponder has no capability to look into the payload and detect circuits, an
MXP_2.5G_10G card does not display circuits under card view.
Caution You must use a 20-dB fiber attenuator (15 to 25 dB) when working with the MXP_2.5G_10G card in a
loopback on the trunk port. Do not use direct fiber loopbacks with the MXP_2.5G_10G card. Using
direct fiber loopbacks causes irreparable damage to the MXP_2.5G_10G card.
You can install MXP_2.5G_10G cards in Slots 1 to 6 and 12 to 17 in ONS 15454 DWDM chassis, Slots
2 and 3 in ONS 15454 M2 chassis, Slots 2 to 7 in ONS 15454 M6.
Caution Do not install an MXP_2.5G_10G card in Slot 3 if you have installed a DS3/EC1-48 card in Slots 1or 2.
Likewise, do not install an MXP_2.5G_10G card in Slot 17 if you have installed a DS3/EC1-48 card in
Slots 15 or 16. If you do, the cards will interact and cause DS-3 bit errors.
You can provision this card in a linear configuration. MXP_2.5G_10G cards cannot be provisioned as
a BLSR/MS-SPRing, a path protection/SNCP, or a regenerator. They can be used in the middle of
BLSR/MS-SPRing or 1+1 spans only when the card is configured for transparent termination mode.
The MXP_2.5G_10G port features a 1550-nm laser on the trunk port and four 1310-nm lasers on the client
ports and contains five transmit and receive connector pairs (labeled) on the card faceplate. The card uses
a dual LC connector on the trunk side and SFP connectors on the client side for optical cable termination.
Note When you create a 4xOC-48 OCHCC circuit, you need to select the G.709 and Synchronous options. A
4xOC-48 OCHCC circuit is supported by G.709 and synchronous mode. This is necessary to provision
a 4xOC-48 OCHCC circuit.
For more information about the MXP_2.5G_10G card, see
http://www.cisco.com/en/US/prod/collateral/optical/ps5724/ps2006/ps5320/product_data_sheet0900aecd80121bee_ps13234_Products_Data_Sheet.html.
Related Procedures for MXP_2.5G_10G Card

The following is the list of procedures and tasks related to the configuration of MXP_2.5G_10G:
149
MXP_2.5G_10E Card
446
MXP_2.5G_10E Card
The MXP_2.5G_10E card has reached end of support.
The faceplate designation of the card is “4x2.5G 10E MXP.” The MXP_2.5G_10E card is a DWDM
muxponder that supports full transparent termination the client side. The card multiplexes four 2.5 Gbps
client signals (4 x OC48/STM-16 SFP) into a single 10-Gbps DWDM optical signal on the trunk side. The
MXP_2.5G_10E provides wavelength transmission service for the four incoming 2.5 Gbps client
interfaces. The MXP_2.5G_10E muxponder passes all SONET/SDH overhead bytes transparently.
The MXP_2.5G_10E card is not compatible with the MXP_2.5G_10G card, which does not support full
transparent termination. You can install MXP_2.5G_10E cards in Slots 1 to 6 and 12 to 17 in ONS 15454
DWDM chassis, Slots 2 and 3 in ONS 15454 M2 chassis, Slots 2 to 7 in ONS 15454 M6. You can
provision this card in a linear configuration, as a BLSR/MS-SPRing, a path protection/SNCP, or a
regenerator. The card can be used in the middle of BLSR/MS-SPRing or 1+1 spans when the card is
The MXP_2.5G_10E features a 1550-nm laser on the trunk port and four 1310-nm lasers on the client ports and
contains five transmit and receive connector pairs (labeled) on the card faceplate. The card uses a dual LC
connector on the trunk side and uses SFP modules on the client side for optical cable termination. The SFP
pluggable modules are short reach (SR) or intermediate reach (IR) and support an LC fiber connector.
Key Features
The MXP_2.5G_10E card has the following high level features:
Four 2.5 Gbps client interfaces (OC-48/STM-16) and one 10 Gbps trunk. The four OC-48 signals are
mapped into a ITU-T G.709 OTU2 signal using standard ITU-T G.709 multiplexing.
Onboard E-FEC processor: The processor supports both standard Reed-Solomon (RS, specified in ITU-
T G.709) and E-FEC, which allows an improved gain on trunk interfaces with a resultant extension of
the transmission range on these interfaces. The E-FEC functionality increases the correction capability
of the transponder to improve performance, allowing operation at a lower OSNR compared to the
standard RS (255,239) correction algorithm. A new block code (BCH) algorithm implemented in E-
FEC allows recovery of an input BER up to 1E-3.
Pluggable client interface optic modules: The MXP_2.5G_10E card has modular interfaces. Two types of
optics modules can be plugged into the card. These include an OC-48/STM 16 SR-1 interface with a 7-km
(4.3-mile) nominal range (for short range and intra-office applications) and an IR-1 interface with
150
MXP_2.5G_10E Functions
a range up to 40 km (24.9 miles). SR-1 is defined in Telcordia GR-253-CORE and in I-16 (ITU-T G.957).
IR-1 is defined in Telcordia GR-253-CORE and in S-16-1 (ITU-T G.957).
High level provisioning support: The MXP_2.5G_10E card is initially provisioned using CiscoTransport
Planner software. Subsequently, the card can be monitored and provisioned using CTC software.
Link monitoring and management: The MXP_2.5G_10E card uses standard OC-48 OH (overhead)
bytes to monitor and manage incoming interfaces. The card passes the incoming SDH/SONET data
stream and its overhead bytes transparently.
Control of layered SONET/SDH transport overhead: The card is provisionable to terminate regenerator
section overhead. This is used to eliminate forwarding of unneeded layer overhead. It can help reduce
the number of alarms and help isolate faults in the network.
Automatic timing source synchronization: The MXP_2.5G_10E normally synchronizes from the control
card. If for some reason, such as maintenance or upgrade activity, the control card is not available, the
MXP_2.5G_10E automatically synchronizes to one of the input client interface clocks.
Configurable squelching policy: The card can be configured to squelch the client interface output if
there is LOS at the DWDM receiver or if there is a remote fault. In the event of a remote fault, the
card manages multiplex section alarm indication signal (MS-AIS) insertion.

MXP_2.5G_10E Functions
The following functions of the MXP_2.5G_10E card are explained in "Card Features" chapter:
Client Interface
DWDM Interface
Multiplexing Function
Timing Synchronization
FEC
SONET/SDH Overhead Byte Processing
Card-Level Indicators
Client Interface Monitoring
Jitter
Lamp Test
Onboard Traffic Generation
Wavelength Identification
The card uses trunk lasers that are wave-locked, which allows the trunk transmitter to operate on the ITU grid
effectively. The laser is tunable over eight wavelengths at 50-GHz spacing or four at 100-GHz spacing.
151
Related Procedures for MXP_2.5G_10E Card
Table 75: MXP_2.5G_10E Trunk Wavelengths
Band Wavelength (nm) Band Wavelength (nm)
30.3 1530.33 46.1 1546.12
30.3 1531.12 46.1 1546.92
30.3 1531.90 46.1 1547.72
30.3 1532.68 46.1 1548.51
34.2 1534.25 50.1 1550.12
34.2 1535.04 50.1 1550.92
34.2 1535.82 50.1 1551.72
34.2 1536.61 50.1 1552.52
38.1 1538.19 54.1 1554.13
38.1 1538.98 54.1 1554.94
38.1 1539.77 54.1 1555.75
38.1 1540.56 54.1 1556.55
42.1 1542.14 58.1 1558.17
42.1 1542.94 58.1 1558.98
42.1 1543.73 58.1 1559.79
42.1 1544.53 58.1 1560.61
For more information about the MXP_2.5G_10E card, see

http://www.cisco.com/en/US/prod/collateral/optical/ps5724/ps2006/ps5320/product_data_sheet0900aecd801018ac.html.
Related Procedures for MXP_2.5G_10E Card

The following is the list of procedures and tasks related to the configuration of MXP_2.5G_10E Card:
446
152
MXP_2.5G_10E_C and MXP_2.5G_10E_L Cards
MXP_2.5G_10E_C and MXP_2.5G_10E_L Cards

The MXP_2.5G_10E_C and MXP_2.5G_10E_L cards are DWDM muxponders that support transparent
termination mode on the client side. The faceplate designation of the cards is “4x2.5G 10E MXP C” for the
MXP_2.5G_10E_C card and “4x2.5G 10E MXP L” for the MXP_2.5G_10E_L card. The cards multiplex
four 2.5-Gbps client signals (4 x OC48/STM-16 SFP) into a single 10-Gbps DWDM optical signal on the
trunk side. The MXP_2.5G_10E_C and MXP_2.5G_10E_L cards provide wavelength transmission service
for the four incoming 2.5 Gbps client interfaces. The MXP_2.5G_10E_C and MXP_2.5G_10E_L
muxponders pass all SONET/SDH overhead bytes transparently.
The digital wrapper function (ITU-T G.709 compliant) formats the DWDM wavelength so that it can be
used to set up GCCs for data communications, enable FEC, or facilitate PM.
The MXP_2.5G_10E_C and MXP_2.5G_10E_L cards work with OTN devices defined in ITU-T G.709.
The cards support ODU1 to OTU2 multiplexing, an industry standard method for asynchronously mapping
a SONET/SDH payload into a digitally wrapped envelope. See the "Multiplexing Function” section.
The MXP_2.5G_10E_C and MXP_2.5G_10E_L cards are not compatible with the MXP_2.5G_10G
card, which does not support transparent termination mode.
You can install MXP_2.5G_10E_C and MXP_2.5G_10E_L cards in Slots 1 to 6 and 12 to 17 in ONS
15454 DWDM chassis, Slots 2 and 3 in ONS 15454 M2 chassis, Slots 2 to 7 in ONS 15454 M6. You can
provision a card in a linear configuration, as a BLSR/MS-SPRing, a path protection/SNCP, or a
regenerator. The cards can be used in the middle of BLSR/MS-SPRing or 1+1 spans when the cards are
The MXP_2.5G_10E_C card features a tunable 1550-nm C-band laser on the trunk port. The laser is
tunable across 82 wavelengths on the ITU grid with 50-GHz spacing between wavelengths. The
MXP_2.5G_10E_L features a tunable 1580-nm L-band laser on the trunk port. The laser is tunable across
80 wavelengths on the ITU grid, also with 50-GHz spacing. Each card features four 1310-nm lasers on the
client ports and contains five transmit and receive connector pairs (labeled) on the card faceplate. The cards
uses dual LC connectors on the trunk side and use SFP modules on the client side for optical cable
termination. The SFP pluggable modules are SR or IR and support an LC fiber connector.
Key Features
The MXP_2.5G_10E_C and MXP_2.5G_10E_L cards have the following high level features:
Four 2.5 Gbps client interfaces (OC-48/STM-16) and one 10 Gbps trunk. The four OC-48 signals are
mapped into a ITU-T G.709 OTU2 signal using standard ITU-T G.709 multiplexing.
Onboard E-FEC processor: The processor supports both standard RS (specified in ITU-T G.709) and E-FEC,
which allows an improved gain on trunk interfaces with a resultant extension of the transmission range on
these interfaces. The E-FEC functionality increases the correction capability of the transponder to improve
performance, allowing operation at a lower OSNR compared to the standard RS (255,239)
153
MXP_2.5G_10E_C and MXP_2.5G_10E_L Functions
correction algorithm. A new BCH algorithm implemented in E-FEC allows recovery of an input BER
up to 1E-3.
Pluggable client interface optic modules: The MXP_2.5G_10E_C and MXP_2.5G_10E_L cards have
modular interfaces. Two types of optics modules can be plugged into the card. These include an OC-
48/STM 16 SR-1 interface with a 7-km (4.3-mile) nominal range (for short range and intra-office
applications) and an IR-1 interface with a range up to 40 km (24.9 miles). SR-1 is defined in
Telcordia GR-253-CORE and in I-16 (ITU-T G.957). IR-1 is defined in Telcordia GR-253-CORE and
in S-16-1 (ITU-T G.957).
High level provisioning support: The cards are initially provisioned using Cisco TransportPlanner
software. Subsequently, the card can be monitored and provisioned using CTC software.
Link monitoring and management: The cards use standard OC-48 OH (overhead) bytes to monitor and
manage incoming interfaces. The cards pass the incoming SDH/SONET data stream and its overhead
bytes transparently.
Control of layered SONET/SDH transport overhead: The cards are provisionable to terminate
regenerator section overhead. This is used to eliminate forwarding of unneeded layer overhead. It can
help reduce the number of alarms and help isolate faults in the network.
Automatic timing source synchronization: The MXP_2.5G_10E_C and MXP_2.5G_10E_L cards
normally synchronize from the control card. If for some reason, such as maintenance or upgrade
activity, the control card is not available, the cards automatically synchronize to one of the input client
interface clocks.
Configurable squelching policy: The cards can be configured to squelch the client interface output if
card manages MS-AIS insertion.
The cards are tunable across the full C band (MXP_2.5G_10E_C) or full L band (MXP_2.5G_10E_L),
thus eliminating the need to use different versions of each card to provide tunability across specific
wavelengths in a band.
For information about safety labels for the cards, see the "Class 1 Laser Product Cards” section.
MXP_2.5G_10E_C and MXP_2.5G_10E_L Functions

The following functions of the MXP_2.5G_10E_C and MXP_2.5G_10E_L cards are explained in the"Card
Features" chapter:
Client Interface
DWDM Interface
FEC
154

Jitter
Lamp Test
The card uses trunk lasers that are wavelocked, which allows the trunk transmitter to operate on the ITU
grid effectively. Both the MXP_2.5G_10E_C and MXP_2.5G_10E_L cards implement the UT2 module.
The MXP_2.5G_10E_C card uses a C-band version of the UT2 and the MXP_2.5G_10E_L card uses an L-
band version. For MXP_2.5G_10E_C card, the laser is tunable over 82 wavelengths in the C band at 50-
GHz spacing on the ITU grid.
Table 76: MXP_2.5G_10E_C Trunk Wavelengths
1 196.00 1529.55 42 193.95 1545.72
2 195.95 1529.94 43 193.90 1546.119
3 195.90 1530.334 44 193.85 1546.518
4 195.85 1530.725 45 193.80 1546.917
5 195.80 1531.116 46 193.75 1547.316
6 195.75 1531.507 47 193.70 1547.715
7 195.70 1531.898 48 193.65 1548.115
8 195.65 1532.290 49 193.60 1548.515
9 195.60 1532.681 50 193.55 1548.915
10 195.55 1533.073 51 193.50 1549.32
11 195.50 1533.47 52 193.45 1549.71
12 195.45 1533.86 53 193.40 1550.116
13 195.40 1534.250 54 193.35 1550.517
14 195.35 1534.643 55 193.30 1550.918
15 195.30 1535.036 56 193.25 1551.319
16 195.25 1535.429 57 193.20 1551.721
17 195.20 1535.822 58 193.15 1552.122
155
18 195.15 1536.216 59 193.10 1552.524
19 195.10 1536.609 60 193.05 1552.926
20 195.05 1537.003 61 193.00 1553.33
21 195.00 1537.40 62 192.95 1553.73
22 194.95 1537.79 63 192.90 1554.134
23 194.90 1538.186 64 192.85 1554.537
24 194.85 1538.581 65 192.80 1554.940
25 194.80 1538.976 66 192.75 1555.343
26 194.75 1539.371 67 192.70 1555.747
27 194.70 1539.766 68 192.65 1556.151
28 194.65 1540.162 69 192.60 1556.555
29 194.60 1540.557 70 192.55 1556.959
30 194.55 1540.953 71 192.50 1557.36
31 194.50 1541.35 72 192.45 1557.77
32 194.45 1541.75 73 192.40 1558.173
33 194.40 1542.142 74 192.35 1558.578
34 194.35 1542.539 75 192.30 1558.983
35 194.30 1542.936 76 192.25 1559.389
36 194.25 1543.333 77 192.20 1559.794
37 194.20 1543.730 78 192.15 1560.200
38 194.15 1544.128 79 192.10 1560.606
39 194.10 1544.526 80 192.05 1561.013
40 194.05 1544.924 81 192.00 1561.42
41 194.00 1545.32 82 191.95 1561.83
For MXP_2.5G_10E_L card, the laser is fully tunable over 80 wavelengths in the L band at 50-GHz
spacing on the ITU grid.
156
Table 77: MXP_2.5G_10E_L Trunk Wavelengths
1 190.85 1570.83 41 188.85 1587.46
2 190.8 1571.24 42 188.8 1587.88
3 190.75 1571.65 43 188.75 1588.30
4 190.7 1572.06 44 188.7 1588.73
5 190.65 1572.48 45 188.65 1589.15
6 190.6 1572.89 46 188.6 1589.57
7 190.55 1573.30 47 188.55 1589.99
8 190.5 1573.71 48 188.5 1590.41
9 190.45 1574.13 49 188.45 1590.83
10 190.4 1574.54 50 188.4 1591.26
11 190.35 1574.95 51 188.35 1591.68
12 190.3 1575.37 52 188.3 1592.10
13 190.25 1575.78 53 188.25 1592.52
14 190.2 1576.20 54 188.2 1592.95
15 190.15 1576.61 55 188.15 1593.37
16 190.1 1577.03 56 188.1 1593.79
17 190.05 1577.44 57 188.05 1594.22
18 190 1577.86 58 188 1594.64
19 189.95 1578.27 59 187.95 1595.06
20 189.9 1578.69 60 187.9 1595.49
21 189.85 1579.10 61 187.85 1595.91
22 189.8 1579.52 62 187.8 1596.34
23 189.75 1579.93 63 187.75 1596.76
24 189.7 1580.35 64 187.7 1597.19
25 189.65 1580.77 65 187.65 1597.62
26 189.6 1581.18 66 187.6 1598.04
27 189.55 1581.60 67 187.55 1598.47
157
Related Procedures for MXP_2.5G_10E_C and MXP_2.5G_10E_L Cards
28 189.5 1582.02 68 187.5 1598.89
29 189.45 1582.44 69 187.45 1599.32
30 189.4 1582.85 70 187.4 1599.75
31 189.35 1583.27 71 187.35 1600.17
32 189.3 1583.69 72 187.3 1600.60
33 189.25 1584.11 73 187.25 1601.03
34 189.2 1584.53 74 187.2 1601.46
35 189.15 1584.95 75 187.15 1601.88
36 189.1 1585.36 76 187.1 1602.31
37 189.05 1585.78 77 187.05 1602.74
38 189 1586.20 78 187 1603.17
39 188.95 1586.62 79 186.95 1603.60
40 188.9 1587.04 80 186.9 1604.03
Related Procedures for MXP_2.5G_10E_C and MXP_2.5G_10E_L Cards

The following is the list of procedures and tasks related to the configuration of MXP_2.5G_10E_C and
MXP_2.5G_10E_L cards:
NTP-G97 Modifying the 4x2.5G Muxponder Card Line Settings and PM Parameter Thresholds
MXP_MR_2.5G and MXPP_MR_2.5G Cards

The MXP_MR_2.5G card aggregates a mix and match of client Storage Area Network (SAN) service
client inputs (GE, FICON, Fibre Channel, and ESCON) into one 2.5 Gbps STM-16/OC-48 DWDM signal
on the trunk side. It provides one long-reach STM-16/OC-48 port per card and is compliant with Telcordia
GR-253-CORE.
Note In Software Release 7.0 and later, two additional operating modes have been made available to the user:
pure ESCON (all 8 ports running ESCON), and mixed mode (Port 1 running FC/GE/FICON, and Ports 5
through 8 running ESCON). When the card is part of a system running Software Release 6.0 or below, only
one operating mode, (FC/GE) is available for use.
158
The 2.5-Gbps Multirate Muxponder–Protected–100 GHz–Tunable 15xx.xx-15yy.yy (MXPP_MR_2.5G) card

aggregates various client SAN service client inputs (GE, FICON, Fibre Channel, and ESCON) into one
2.5 Gbps STM-16/OC-48 DWDM signal on the trunk side. It provides two long-reach STM-16/OC-48
ports per card and is compliant with ITU-T G.957 and Telcordia GR-253-CORE.
Because the cards are tunable to one of four adjacent grid channels on a 100-GHz spacing, each card is
available in eight versions, with 15xx.xx representing the first wavelength and 15yy.yy representing the last
wavelength of the four available on the card. In total, 32 DWDM wavelengths are covered in accordance
with the ITU-T 100-GHz grid standard, G.692, and Telcordia GR-2918-CORE, Issue 2.
Table 78: Card Versions
Card Version Frequency Channels at 100 GHz (0.8 nm) Spacing
1530.33–1532.68 1530.33 nm 1531.12 nm 1531.90 nm 1532.68 nm
1534.25–1536.61 1534.25 nm 1535.04 nm 1535.82 nm 1536.61 nm
1538.19–1540.56 1538.19 nm 1538.98 nm 1539.77 nm 1540.56 nm
1542.14–1544.53 1542.14 nm 1542.94 nm 1543.73 nm 1544.53 nm
1546.12–1548.51 1546.12 nm 1546.92 nm 1547.72 nm 1548.51 nm
1550.12–1552.52 1550.12 nm 1550.92 nm 1551.72 nm 1552.52 nm
1554.13–1556.55 1554.13 nm 1554.94 nm 1555.75 nm 1556.55 nm
1558.17–1560.61 1558.17 nm 1558.98 nm 1559.79 nm 1560.61 nm
The muxponders are intended to be used in applications with long DWDM metro or regional unregenerated
spans. Long transmission distances are achieved through the use of flat gain optical amplifiers.
The client interface supports the following payload types:
2G FC
1G FC
2G FICON
1G FICON
GE
ESCON
Note Because the client payload cannot oversubscribe the trunk, a mix of client
signals can be accepted, up to a maximum limit of 2.5 Gbps.
The current version of the ITU-T Transparent Generic Framing Procedure (GFP-T) G.7041 supports transparent
mapping of 8B/10B block-coded protocols, including Gigabit Ethernet, Fibre Channel, and FICON.
159
In addition to the GFP mapping, 1-Gbps traffic on Port 1 or 2 of the high-speed serializer/deserializer
(SERDES) is mapped to an STS-24c channel. If two 1-Gbps client signals are present at Port 1 and Port 2
of the SERDES, the Port 1 signal is mapped into the first STS-24c channel and the Port 2 signal into the
second STS-24c channel. The two channels are then mapped into an OC-48 trunk channel.
Table 79: MXP_MR_2.5G and MXPP_MR_2.5G Client Interface Data Rates and Encapsulation
Client Interface Input Data Rate ITU-T GFP-T G.7041 Encapsulation
2G FC 2.125 Gbps Yes
1G FC 1.06 Gbps Yes
2G FICON 2.125 Gbps Yes
1G FICON 1.06 Gbps Yes
GE 1.25 Gbps Yes
ESCON 0.2 Gbps Yes
Table 80: Client Data Rates and Ports
Mode Port(s) Aggregate Data Rate
2G FC 1 2.125 Gbps
1G FC 1, 2 2.125 Gbps
2G FICON 1 2.125 Gbps
1G FICON 1, 2 2.125 Gbps
GE 1, 2 2.5 Gbps
1G FC -ESCON (mixed mode) 1 ,5, 6, 7, 8 1.06 Gbps 0.8 Gbps

1.86 Gbps total
1G FICON -ESCON (mixed mode) 1 ,5, 6, 7, 8 1.06 Gbps 0.8 Gbps

1.86 Gbps total
GE -ESCON (mixed mode) 1 ,5, 6, 7, 8 1.25 Gbps 0.8 Gbps

Total 2.05 Gbps
ESCON 1, 2, 3, 4, 5, 6, 7, 8 1.6 Gbps
160

Figure 11: MXP_MR_2.5G and MXPP_MR_2.5G Faceplates
For information about safety labels for the cards, see the "Class 1M Laser Product Cards” section.
The card has eight SFP client interfaces. Ports 1 and 2 can be used for GE, FC, FICON, or ESCON. Ports 3
through 8 are used for ESCON client interfaces. There are two SERDES blocks dedicated to the high-speed
interfaces (GE, FC, FICON, and ESCON) and two SERDES blocks for the ESCON interfaces. A FPGA is
provided to support different configurations for different modes of operation. This FPGA has a Universal Test
and Operations Physical Interface for ATM (UTOPIA) interface. A transceiver add/drop multiplexer (TADM)
chip supports framing. Finally, the output signal is serialized and connected to the trunk front end
161
MXP_MR_2.5G and MXPP_MR_2.5G Functions
with a direct modulation laser. The trunk receive signal is converted into an electrical signal with an
avalanche photodiode (APD), is deserialized, and is then sent to the TADM framer and FPGA.
The MXPP_MR_2.5G is the same, except a 50/50 splitter divides the power at the trunk interface. In the
receive direction, there are two APDs, two SERDES blocks, and two TADM framers. This is necessary
to monitor both the working and protect paths. A switch selects one of the two paths to connect to the
client interface.
Figure 12: MXP_MR_2.5G and MXPP_MR_2.5G Block Diagram
Caution You must use a 20-dB fiber attenuator (15 to 25 dB) when working with the MXP_MR_2.5G and
MXPP_MR_2.5G cards in a loopback configuration on the trunk port. Do not use direct fiber loopbacks with
the MXP_MR_2.5G and MXPP_MR_2.5G cards. Using direct fiber loopbacks causes irreparable damage to
the MXP_MR_2.5G and MXPP_MR_2.5G cards.
MXP_MR_2.5G and MXPP_MR_2.5G Functions

The following functions of the MXP_MR_2.5G and MXPP_MR_2.5G cards are explained in the "Card
Features" chapter:
Performance Monitoring
Distance Extension
Slot Compatibility
Interoperability with Cisco MDS Switches
Client and Trunk Ports
162
Related Procedures for MXP_MR_2.5G and MXPP_MR_2.5G Cards

Port level indicator
Related Procedures for MXP_MR_2.5G and MXPP_MR_2.5G Cards

The following is the list of procedures and tasks related to the configuration of MXP_MR_2.5G and
MXPP_MR_2.5G cards:
NTP-G99 Modifying the 2.5G Data Muxponder Card Line Settings and PM Parameter Thresholds, on
page 472
MXP_MR_10DME_C and MXP_MR_10DME_L Cards

The MXP_MR_10DME_C and MXP_MR_10DME_L cards aggregate a mix of client SAN service client
inputs (GE, FICON, and Fibre Channel) into one 10.0 Gbps STM-64/OC-192 DWDM signal on the trunk
side. It provides one long-reach STM-64/OC-192 port per card and is compliant with Telcordia GR-253-
CORE and ITU-T G.957.
The cards support aggregation of the following signal types:
1-Gigabit Fibre Channel
1-Gigabit Ethernet
1-Gigabit ISC-Compatible (ISC-1)
2-Gigabit ISC-Peer (ISC-3)
Note On the card faceplates, the MXP_MR_10DME_C and MXP_MR_10DME_L

cards are displayed as 10DME_C and 10DME_L, respectively.
Caution The card can be damaged by dropping it. Handle it safely.
Note Because the client payload cannot oversubscribe the trunk, a mix of client
signals can be accepted, up to a maximum limit of 10 Gbps.
163
MXP_MR_10DME_C and MXP_MR_10DME_L Cards
The MXP_MR_10DME_C card can be installed in Slots 2 to 7 in Cisco NCS 2015 chassis. This card
upgrades to a new bootcode automatically when it is installed between slots 2 and 7. After the
bootcode upgrade, the card can be installed in Slots 2 to 16 of the Cisco NCS 2015 chassis.
Note The MXP_MR_10DME_C and MXP_MR_10DME_L cards are not compatible

with the MXP_2.5G_10G card, which does not support transparent termination
mode.
The MXP_MR_10DME_C card features a tunable 1550-nm C-band laser on the trunk port. The laser is tunable
across 82 wavelengths on the ITU grid with 50-GHz spacing between wavelengths. The MXP_MR_10DME_L
features a tunable 1580-nm L-band laser on the trunk port. The laser is tunable across 80 wavelengths on the ITU
grid, also with 50-GHz spacing. Each card supports eight SFP based client ports and one trunk port. The cards
uses dual LC connectors on the trunk side and use SFP modules on the client side for optical cable termination.
The SFP pluggable modules are SR or IR and support an LC fiber connector.
The current version of the GFP-T G.7041 supports transparent mapping of 8B/10B block-coded
protocols, including Gigabit Ethernet, Fibre Channel, ISC, and FICON.
Table 81: MXP_MR_10DME_C and MXP_MR_10DME_L Client Interface Data Rates and Encapsulation
Client Interface Input Data Rate GFP-T G.7041 Encapsulation
1G FC 1.06 Gbps Yes
2G FICON/2G ISC-Compatible 2.125 Gbps Yes

(ISC-1)/ 2G ISC-Peer (ISC-3)

Gigabit Ethernet 1.25 Gbps Yes
There are two FPGAs on each MXP_MR_10DME_C and MXP_MR_10DME_L, and a group of four ports is
mapped to each FPGA. Group 1 consists of Ports 1 through 4, and Group 2 consists of Ports 5 through 8. The
following table shows some of the mix and match possibilities on the various client data rates for Ports 1
through 4, and Ports 5 through 8. An X indicates that the data rate is supported in that port.
Table 82: Supported Client Data Rates for Ports 1 through 4 and Ports 5 through 8
Port (Group 1) Port (Group 2) Gigabit Ethernet 1G FC 2G FC 4G FC
1 5 X X X X
2 6 X X — —
3 7 X X X —
4 8 X X — —
164
Key Features
GFP-T PM is available through RMON and trunk PM is managed according to Telcordia GR-253-CORE
and ITU G.783/826. Client PM is achieved through RMON for FC and GE.
A buffer-to-buffer credit management scheme provides FC flow control. With this feature enabled, a port
indicates the number of frames that can be sent to it (its buffer credit), before the sender is required to stop
transmitting and wait for the receipt of a “ready” indication The MXP_MR_10DME_C and
MXP_MR_10DME_L cards support FC credit-based flow control with a buffer-to-buffer credit extension of
up to 1600 km (994.1 miles) for 1G FC, up to 800 km (497.1 miles) for 2G FC, or up to 400 km (248.5 miles)
for 4G FC. The feature can be enabled or disabled.
The MXP_MR_10DME_C and MXP_MR_10DME_L cards feature a 1550-nm laser for the trunk/line port
and a 1310-nm or 850-nm laser (depending on the SFP) for the client ports. The cards contains eight 12.5
degree downward tilt SFP modules for the client interfaces. For optical termination, each SFP uses two LC
connectors, which are labeled TX and RX on the faceplate. The trunk port is a dual-LC connector with a
45 degree downward angle.
The throughput of the MXP_MR_10DME_C and MXP_MR_10DME_L cards is affected by the
following parameters:
Distance extension—If distance extension is enabled on the card, it provides more throughput but more
latency. If distance extension is disabled on the card, the buffer to buffer credits on the storage switch
affects the throughput; higher the buffer to buffer credits higher is the throughput.
Note For each link to operate at the maximum throughput, it requires a minimum
number of buffer credits to be available on the devices which the link connects
to. The number of buffer credits required is a function of the distance between
the storage switch extension ports and the link bandwidth, that is, 1G, 2G, or
4G. These buffer credits are provided by either the storage switch (if distance
extension is disabled) or by both the storage switch and the card (if distance
extension is enabled).
Forward Error Correction (FEC)—If Enhanced FEC (E-FEC) is enabled on the trunk port of the card, the
throughout is significantly reduced in comparison to standard FEC being set on the trunk port.
Note If distance extension is enabled on the card, the FEC status does not usually
affect the throughput of the card.
Payload size—The throughput of the card decreases with decrease in payload size. The
resultant throughput of the card is usually the combined effect of the above parameters.
Key Features
The MXP_MR_10DME_C and MXP_MR_10DME_L cards have the following high-level features:
Onboard E-FEC processor: The processor supports both standard RS (specified in ITU-T G.709) and E-FEC,
which allows an improved gain on trunk interfaces with a resultant extension of the transmission range on
these interfaces. The E-FEC functionality increases the correction capability of the transponder to improve
performance, allowing operation at a lower OSNR compared to the standard RS (255,239)
165
Key Features
correction algorithm. A new BCH algorithm implemented in E-FEC allows recovery of an input BER
up to 1E-3.
Pluggable client interface optic modules: The MXP_MR_10DME_C and MXP_MR_10DME_L cards
have modular interfaces. Two types of optics modules can be plugged into the card. These include an
OC-48/STM 16 SR-1 interface with a 7-km (4.3-mile) nominal range (for short range and intra-office
applications) and an IR-1 interface with a range up to 40 km (24.9 miles). SR-1 is defined in
Telcordia GR-253-CORE and in I-16 (ITU-T G.957). IR-1 is defined in Telcordia GR-253-CORE and
in S-16-1 (ITU-T G.957).
Y-cable protection: Supports Y-cable protection between the same card type only, on ports with the
same port number and signal rate. See the "Y-Cable Protection Availability on TXP, MXP, and
Xponder Cards” section for more detailed information.
High level provisioning support: The cards are initially provisioned using Cisco TransportPlanner
ALS: A safety mechanism used in the event of a fiber cut. For details regarding ALS provisioning for
the MXP_MR_10DME_C and MXP_MR_10DME_L cards, see the NTP-G162 Changing the ALS
Maintenance Settings section.
Link monitoring and management: The cards use standard OC-48 OH bytes to monitor and manage incoming
interfaces. The cards pass the incoming SDH/SONET data stream and its OH bytes transparently.
Control of layered SONET/SDH transport overhead: The cards are provisionable to terminate
Automatic timing source synchronization: The MXP_MR_10DME_C and MXP_MR_10DME_L cards
normally synchronize from the control card. If for some reason, such as maintenance or upgrade
activity, the control card is not available, the cards automatically synchronize to one of the input client
interface clocks.
Note MXP_MR_10DME_C and MXP_MR_10DME_L cards cannot be used for line

timing.
Configurable squelching policy: The cards can be configured to squelch the client interface output if
card manages MS-AIS insertion.
The cards are tunable across the full C band (MXP_MR_10DME_C) or full L band
(MXP_MR_10DME_L), thus eliminating the need to use different versions of each card to provide
tunability across specific wavelengths in a band.
You can provision a string (port name) for each fiber channel/FICON interface on the
MXP_MR_10DME_C and MXP_MR_10DME_L cards, which allows the MDS Fabric Manager
to create a link association between that SAN port and a SAN port on a Cisco MDS 9000 switch.
From Software Release 9.0, the fast switch feature of MXP_MR_10DME_C and MXP_MR_10DME_L
cards along with the buffer-to-buffer credit recovery feature of MDS switches, prevents reinitialization
of ISL links during Y-cable switchovers.
166
MXP_MR_10DME_C and MXP_MR_10DME_L Functions


The following functions of the MXP_MR_10DME_C and MXP_MR_10DME_L cards are explained in
the "Card Features" chapter:
grid effectively. Both the MXP_MR_10DME_C and MXP_MR_10DME_L cards implement the UT2
module. The MXP_MR_10DME_C card uses a C-band version of the UT2 and the MXP_MR_10DME_L
card uses an L-band version.
The MXP_MR_10DME_C card is tunable over 82 wavelengths in the C band at 50-GHz spacing on the
ITU grid.
Table 83: MXP_MR_10DME_C Trunk Wavelengths
1 196.00 1529.55 42 193.95 1545.72
2 195.95 1529.94 43 193.90 1546.119
3 195.90 1530.334 44 193.85 1546.518
4 195.85 1530.725 45 193.80 1546.917
5 195.80 1531.116 46 193.75 1547.316
6 195.75 1531.507 47 193.70 1547.715
7 195.70 1531.898 48 193.65 1548.115
8 195.65 1532.290 49 193.60 1548.515
9 195.60 1532.681 50 193.55 1548.915
10 195.55 1533.073 51 193.50 1549.32
11 195.50 1533.47 52 193.45 1549.71
12 195.45 1533.86 53 193.40 1550.116
13 195.40 1534.250 54 193.35 1550.517
14 195.35 1534.643 55 193.30 1550.918
15 195.30 1535.036 56 193.25 1551.319
167
16 195.25 1535.429 57 193.20 1551.721
17 195.20 1535.822 58 193.15 1552.122
18 195.15 1536.216 59 193.10 1552.524
19 195.10 1536.609 60 193.05 1552.926
20 195.05 1537.003 61 193.00 1553.33
21 195.00 1537.40 62 192.95 1553.73
22 194.95 1537.79 63 192.90 1554.134
23 194.90 1538.186 64 192.85 1554.537
24 194.85 1538.581 65 192.80 1554.940
25 194.80 1538.976 66 192.75 1555.343
26 194.75 1539.371 67 192.70 1555.747
27 194.70 1539.766 68 192.65 1556.151
28 194.65 1540.162 69 192.60 1556.555
29 194.60 1540.557 70 192.55 1556.959
30 194.55 1540.953 71 192.50 1557.36
31 194.50 1541.35 72 192.45 1557.77
32 194.45 1541.75 73 192.40 1558.173
33 194.40 1542.142 74 192.35 1558.578
34 194.35 1542.539 75 192.30 1558.983
35 194.30 1542.936 76 192.25 1559.389
36 194.25 1543.333 77 192.20 1559.794
37 194.20 1543.730 78 192.15 1560.200
38 194.15 1544.128 79 192.10 1560.606
39 194.10 1544.526 80 192.05 1561.013
40 194.05 1544.924 81 192.00 1561.42
41 194.00 1545.32 82 191.95 1561.83
The MXP_MR_10DME_L card is fully tunable over 80 wavelengths in the L band at 50-GHz spacing on
the ITU grid.
168
Table 84: MXP_MR_10DME_L Trunk Wavelengths
1 190.85 1570.83 41 188.85 1587.46
2 190.8 1571.24 42 188.8 1587.88
3 190.75 1571.65 43 188.75 1588.30
4 190.7 1572.06 44 188.7 1588.73
5 190.65 1572.48 45 188.65 1589.15
6 190.6 1572.89 46 188.6 1589.57
7 190.55 1573.30 47 188.55 1589.99
8 190.5 1573.71 48 188.5 1590.41
9 190.45 1574.13 49 188.45 1590.83
10 190.4 1574.54 50 188.4 1591.26
11 190.35 1574.95 51 188.35 1591.68
12 190.3 1575.37 52 188.3 1592.10
13 190.25 1575.78 53 188.25 1592.52
14 190.2 1576.20 54 188.2 1592.95
15 190.15 1576.61 55 188.15 1593.37
16 190.1 1577.03 56 188.1 1593.79
17 190.05 1577.44 57 188.05 1594.22
18 190 1577.86 58 188 1594.64
19 189.95 1578.27 59 187.95 1595.06
20 189.9 1578.69 60 187.9 1595.49
21 189.85 1579.10 61 187.85 1595.91
22 189.8 1579.52 62 187.8 1596.34
23 189.75 1579.93 63 187.75 1596.76
24 189.7 1580.35 64 187.7 1597.19
25 189.65 1580.77 65 187.65 1597.62
26 189.6 1581.18 66 187.6 1598.04
27 189.55 1581.60 67 187.55 1598.47
169
Related Procedures for MXP_MR_10DME_C and MXP_MR_10DME_L Cards
28 189.5 1582.02 68 187.5 1598.89
29 189.45 1582.44 69 187.45 1599.32
30 189.4 1582.85 70 187.4 1599.75
31 189.35 1583.27 71 187.35 1600.17
32 189.3 1583.69 72 187.3 1600.60
33 189.25 1584.11 73 187.25 1601.03
34 189.2 1584.53 74 187.2 1601.46
35 189.15 1584.95 75 187.15 1601.88
36 189.1 1585.36 76 187.1 1602.31
37 189.05 1585.78 77 187.05 1602.74
38 189 1586.20 78 187 1603.17
39 188.95 1586.62 79 186.95 1603.60
40 188.9 1587.04 80 186.9 1604.03
For more information about the MXP_MR_10DME_C and MXP_MR_10DME_L cards, see
http://www.cisco.com/en/US/prod/collateral/optical/ps5724/ps2006/ps5320/product_data_sheet0900aecd803fc51a.html.
Related Procedures for MXP_MR_10DME_C and MXP_MR_10DME_L Cards

The following is the list of procedures and tasks related to the configuration of MXP_MR_10DME_C and
MXP_MR_10DME_L cards:
page 497
40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards

The 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards aggregate a variety of client service inputs
(Gigabit Ethernet, Fibre Channel, OTU2, OTU2e, and OC-192) into a single 40-Gbps OTU3/OTU3e signal
on the trunk side.
Note In CTC, the 40E-MXP-C and 40ME-MXP-C card is displayed with the same card name, 40E-MXP-C.
170
40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards
The 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards support aggregation of the following signals:
With overclock enabled on the trunk port:
OC-192/STM-64 (only on 40E-MXP-C and 40ME-MXP-C cards)
10 Gigabit Fibre Channel
OTU2e
10 Gigabit Ethernet LAN-Phy (CBR mapping) (only on 40E-MXP-C and 40ME-MXP-C cards)
With overclock disabled on the trunk port:

8 Gigabit Fibre Channel
10 GigabitEthernet LAN-Phy (GFP framing)
10 GigabitEthernet LAN-Phy (WIS framing)
OC-192/STM-64
OTU2
Caution Handle the card with care. Dropping or misuse of the card could result in
permanent damage.
You can install and provision the 40G-MXP-C, cards in a linear configuration in:
Slots 2 to 15 in Cisco NCS 2015 chassis (for 40E-MXP-C card)
The client ports of the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards interoperates with all the
existing TXP/MXP (OTU2 trunk) cards.
The auto negotiation is not supported on the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards in 8G
FC client mode. Hence, during interoperation, the auto negotiation of the 8G-FC client port of the other
device connected to 8G-FC client port on 40G-MXP-C, 40E-MXP-C, or 40ME-MXP-C card must be set to
Fixed/Disabled.
The client port of 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards do not interoperate with
OTU2_XP card when the signal rate is OTU1e (11.049 Gbps) and the “No Fixed Stuff” option is enabled
on the trunk port of OTU2_XP card.
For OTU2 and OTU2e client protocols, Enhanced FEC (EFEC) is not supported on Port 1 of the 40G-
MXP-C, 40E-MXP-C, and 40ME-MXP-C cards.
Table 85: Client Interface Data Rates for 40G-MXP-C, 40E-MXP-C and 40ME-MXP-C Cards
40G-MXP-C, 40E-MXP-C and 40ME-MXP-C Client Port FEC Configuration Supported on OTU2/OTU2e Client
Protocol
Port 1 Only Standard FEC
171
Key Features
40G-MXP-C, 40E-MXP-C and 40ME-MXP-C Client Port FEC Configuration Supported on

OTU2/OTU2e Client Protocol
Port 2 Standard and Enhanced FEC
When setting up the card for the first time, or when the card comes up after clearing the LOS-P condition
due to fiber cut, the trunk port of the 40G-MXP-C card takes about 6 minutes to lock a signal. The trunk
port of the 40G-MXP-C card raises an OTUK-LOF alarm when the card is comes up. The alarm clears
when the trunk port locks the signal.
When a protection switch occurs on the 40E-MXP-C and 40ME-MXP-C cards, the recovery
from PSM protection switch takes about 3 to 4 minutes.
Key Features
The 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards provides the following key features:
The 40G-MXP-C card uses the RZ-DQPSK 40G modulation format.
The 40E-MXP-C and 40ME-MXP-C cards uses the CP-DQPSK modulation format.
Onboard E-FEC processor—The E-FEC functionality improves the correction capability of the transponder to
improve performance, allowing operation at a lower OSNR compared to the standard RS (239,255)
correction algorithm. A new BCH algorithm implemented (according to G.975.1 I.7) in E-FEC allows
recovery of an input BER up to 1E-3. The 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards support
both the standard RS (specified in ITU-T G.709) and E-FEC standard, which allows an improved gain on
trunk interfaces with a resultant extension of the transmission range on these interfaces.
Y-cable protection—Supports Y-cable protection only between the same card type on ports with the
same port number and signal rate. For more information on Y-cable protection, see the "Y-Cable
Protection Availability on TXP, MXP, and Xponder Cards" section.
Note Y-cable cannot be created on a 10 GE port when WIS framing is enabled on the
40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards.
Unidirectional regeneration—The 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards supports

unidirectional regeneration configuration. Each 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C card
in the configuration regenerates the signal received from another 40G-MXP-C, 40E-MXP-C, and
40ME-MXP-C card in one direction.
Note When you configure the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards
in the Unidirectional Regen mode, ensure that the payload is not configured on
the pluggable port modules of the 40G-MXP-C, 40E-MXP-C, and 40ME-
MXP-C card.
172
Figure 13: 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards in Unidirectional Regeneration Configuration
High level provisioning support—The cards are initially provisioned using Cisco Transport Planner
Automatic Laser Shutdown (ALS)—A safety mechanism, Automatic Laser Shutdown (ALS), is used in
the event of a fiber cut. The Auto Restart ALS option is supported only for OC-192/STM-64 and
OTU2 payloads. The Manual Restart ALS option is supported for all payloads. For more information
on provisioning ALS for the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards, see the NTP-G162
Changing the ALS Maintenance Settings section.
Control of layered SONET/SDH transport overhead—The cards are provisionable to terminate
Automatic timing source synchronization—The 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards
synchronize to the card cards. Because of a maintenance or upgrade activity, if the control cards are
not available, the cards automatically synchronize to one of the input client interface clocks.
Squelching policy—The cards are set to squelch the client interface output if there is LOS at the DWDM
receiver, or if there is a remote fault. In the event of a remote fault, the card manages MS-AIS insertion.
The 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards are tunable across the full C-band wavelength.

The 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards use trunk lasers that are wavelocked, which
allows the trunk transmitter to operate on the ITU grid effectively. These cards implement the UT2 module;
they use a C-band version of the UT2. The laser is tunable over 82 wavelengths in the C-band at 50-GHz
spacing on the ITU grid.
Table 86: 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Trunk Wavelengths
1 196.00 1529.55 42 193.95 1545.72
2 195.95 1529.94 43 193.90 1546.119
3 195.90 1530.334 44 193.85 1546.518
4 195.85 1530.725 45 193.80 1546.917
5 195.80 1531.116 46 193.75 1547.316
173
6 195.75 1531.507 47 193.70 1547.715
7 195.70 1531.898 48 193.65 1548.115
8 195.65 1532.290 49 193.60 1548.515
9 195.60 1532.681 50 193.55 1548.915
10 195.55 1533.073 51 193.50 1549.32
11 195.50 1533.47 52 193.45 1549.71
12 195.45 1533.86 53 193.40 1550.116
13 195.40 1534.250 54 193.35 1550.517
14 195.35 1534.643 55 193.30 1550.918
15 195.30 1535.036 56 193.25 1551.319
16 195.25 1535.429 57 193.20 1551.721
17 195.20 1535.822 58 193.15 1552.122
18 195.15 1536.216 59 193.10 1552.524
19 195.10 1536.609 60 193.05 1552.926
20 195.05 1537.003 61 193.00 1553.33
21 195.00 1537.40 62 192.95 1553.73
22 194.95 1537.79 63 192.90 1554.134
23 194.90 1538.186 64 192.85 1554.537
24 194.85 1538.581 65 192.80 1554.940
25 194.80 1538.976 66 192.75 1555.343
26 194.75 1539.371 67 192.70 1555.747
27 194.70 1539.766 68 192.65 1556.151
28 194.65 1540.162 69 192.60 1556.555
29 194.60 1540.557 70 192.55 1556.959
30 194.55 1540.953 71 192.50 1557.36
31 194.50 1541.35 72 192.45 1557.77
32 194.45 1541.75 73 192.40 1558.173
33 194.40 1542.142 74 192.35 1558.578
174
Related Procedures for 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards
34 194.35 1542.539 75 192.30 1558.983
35 194.30 1542.936 76 192.25 1559.389
36 194.25 1543.333 77 192.20 1559.794
37 194.20 1543.730 78 192.15 1560.200
38 194.15 1544.128 79 192.10 1560.606
39 194.10 1544.526 80 192.05 1561.013
40 194.05 1544.924 81 192.00 1561.42
41 194.00 1545.32 82 191.95 1561.83
For more information on 40G-MXP-C card, see

http://www.cisco.com/en/US/prod/collateral/optical/ps5724/ps2006/datasheet_c78-598898.html.
For more information on 40E-MXP-C and 40ME-MXP-C cards, see
Related Procedures for 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards

The following is the list of procedures and tasks related to the configuration of 40G-MXP-C, 40E-MXP-
C, and 40ME-MXP-C cards:
NTP-G293 Modifying the 40G Muxponder Card Line Settings and PM Parameter Thresholds, on page
508
GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards
Note GE_XPE card is the enhanced version of the GE_XP card and 10GE_XPE card is the enhanced version of
the 10GE_XP card.
The cards aggregate Ethernet packets received on the client ports for transport on C-band trunk ports that
operate on a 100-GHz grid. The trunk ports operate with ITU-T G.709 framing and either FEC or E-FEC.
The GE_XP and 10GE_XP cards are designed for bulk point-to-point transport over 10GE LAN PHY
wavelengths for Video-on-Demand (VOD), or broadcast video across protected 10GE LAN PHY
wavelengths. The GE_XPE and 10GE_XPE cards are designed for bulk GE_XPE or 10GE_XPE point-to-
point, point-to-multipoint, multipoint-to-multipoint transport over 10GE LAN PHY wavelengths for Video-
on-Demand (VOD), or broadcast video across protected 10GE LAN PHY wavelengths.
175
GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards
Note When all the cards in the chassis are simultaneously reset by the user, the GE_XP and 10GE_XP cards
undergo a hard reset instead of a soft reset. This causes traffic loss for traffic going through these cards.
You can install and provision the GE_XP, and GE_XPE cards in a linear configuration in:
Slots 2 to 7 in Cisco NCS 2015 chassis. These cards upgrade to a new bootcode automatically when
they are installed between slots 2 and 7.
After the bootcode upgrade, the cards can be installed in Slots from 2 to 16 in Cisco NCS 2015 chassis.
The 10GE_XP and 10GE_XPE cards can be installed in Slots 1 through 6 or 12 through 17. The GE_XP
and GE_XPE are double-slot cards with twenty Gigabit Ethernet client ports and two 10 Gigabit Ethernet
trunk ports. The 10GE_XP and 10GE_XPE are single-slot cards with two 10 Gigabit Ethernet client ports
and two 10 Gigabit Ethernet trunk ports. The client ports support SX, LX, and ZX SFPs and SR and
10GBASE-LR XFPs. (LR2 XFPs are not supported.) The trunk ports support a DWDM XFP.
The RAD pluggables (ONS-SC-E3-T3-PW= and ONS-SC-E1-T1-PW=) do not support:
No loopbacks (Terminal or Facility)
RAI (Remote Alarm Indication) alarm
AIS and LOS alarm
Caution A fan-tray assembly (15454E-CC-FTA for the ETSI shelf, or 15454-CC-

FTA for the ANSI shelf) must be installed in a shelf where a GE_XP,
10GE_XP, GE_XPE, or 10GE_XPE card is installed.
GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards can be provisioned to perform different Gigabit Ethernet
transport roles. All the cards can work as Layer 2 switches. However, the 10GE_XP and 10GE_XPE cards can
also perform as a 10 Gigabit Ethernet transponders (10GE TXP mode), and the GE_XP and GE_XPE can
perform as a 10 Gigabit Ethernet or 20 Gigabit Ethernet muxponders (10GE MXP or 20GE MXP mode).
Note Changing the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card mode requires the ports to be in a OOS-
DSBL (ANSI) or Locked, disabled (ETSI) service state. In addition, no circuits can be provisioned on the
cards when the mode is being changed.
176
Key Features
Table 87: GE_XP, 10GE_XP, GE_XPE, and 10GE_XPECard Modes
Card Mode Cards Description

Layer 2 Ethernet switch GE_XP Provides capability to switch
between any two ports irrespective
10GE_XP
of client or trunk port. Supported
GE_XPE Ethernet protocols and services
include 1+1 protection, QoS
10GE_XPE
(Quality of Service), CoS (Class of
Service), QinQ, MAC learning,
MAC address retrieval, service
provider VLANs (SVLANs), IGMP
snooping and Multicast VLAN
Registration (MVR), link integrity,
and other Ethernet switch services.
10GE TXP 10GE_XP Provides a point-to-point

application in which each 10
10GE_XPE Gigabit Ethernet client port is
mapped to a 10 Gigabit Ethernet
trunk port.
10GE MXP GE_XP Provides the ability to multiplex the

twenty Gigabit Ethernet client ports
20GE MXP GE_XPE on the card to one or both of its 10
Gigabit Ethernet trunk ports. The
card can be provisioned as a single
MXP with twenty Gigabit Ethernet
client ports mapped to one trunk
port (Port 21) or as two MXPs with
ten Gigabit Ethernet client ports
mapped to a trunk port (Ports 1 to
10 mapped to Port 21, and Ports
11-20 mapped to Port 22).
Key Features
The GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards have the following high-level features:
Link Aggregation Control Protocol (LACP) that allows you to bundle several physical ports together to
form a single logical channel.
Ethernet Connectivity Fault Management (CFM) protocol that facilitates proactive connectivity
monitoring, fault verification, and fault isolation.
Ethernet Operations, Administration, and Maintenance (OAM) protocol that facilitates link monitoring,
remote failure indication, and remote loopback.
Resilient Ethernet Protocol (REP) that controls network loops, handles link failures, and improves
convergence time.
Configurable service VLANs (SVLANs) and customer VLANs (CVLANs).
177
Key Features
Ingress rate limiting that can be applied on both SVLANs and CVLANs. You can create SVLAN and
CVLAN profiles and can associate a SVLAN profile to both UNI and NNI ports; however, you can
associate a CVLAN profile only to UNI ports.
CVLAN rate limiting that is supported for QinQ service in selective add mode.
Differentiated Services Code Point (DSCP) to class of service (CoS) mapping that you can configure for
each port. You can configure the CoS of the outer VLAN based on the incoming DSCP bits. This
feature is supported only on GE_XPE and 10GE_XPE cards.
Ports, in Layer 2 switch mode, can be provisioned as network-to-network interfaces (NNIs) or user-
network interfaces (UNIs) to facilitate service provider to customer traffic management.
Broadcast drop-and-continue capability for VOD and broadcast video applications.
Gigabit Ethernet MXP, TXP, and Layer 2 switch capability.
Far-End Laser Control (FELC) that is supported on copper SFPs from Release 8.52 and later releases.
For more information on FELC, see the "Far-End Laser Control” section.
Layer 2 switch mode that provides VLAN translation, QinQ, ingress CoS, egress QoS, Fast Ethernet
protection switching, and other Layer 2 Ethernet services.
Interoperable with TXP_MR_10E and TXP_MR_10E_C cards. Also interoperable with Cisco Catalyst
6500 and Cisco 7600 series Gigabit Ethernet, 10 GE interfaces and CRS-1 10GE interfaces.
The GE_XP and GE_XPE cards have twenty Gigabit Ethernet client ports and two 10 Gigabit Ethernet
trunk ports. The 10GE_XP and 10GE_XPE cards have two 10 Gigabit Ethernet client ports and two 10
Gigabit Ethernet trunk ports. The client Gigabit Ethernet signals are mapped into an ITU-T G.709
OTU2 signal using standard ITU-T G.709 multiplexing when configured in one of the MXP modes
(10GE MXP or 20GE MXP).
ITU-T G.709 framing with standard Reed-SoloMon (RS) (255,239) FEC. Performance monitoring and
ITU-T G.709 Optical Data Unit (ODU) synchronous and asynchronous mapping. E-FEC with ITU-T
G.709 ODU and 2.7 Gbps with greater than 8 dB coding gain.
IEEE 802.3 frame format that is supported for 10 Gigabit Ethernet interfaces. The minimum frame size
is 64 bytes. The maximum frame size is user-provisionable.
MAC learning capability in Layer 2 switch mode.
MAC address retrieval in cards provisioned in the L2-over-DWDM mode.
When a port is in UNI mode, tagging can be configured as transparent or selective. In transparent mode,
only SVLANs in the VLAN database of the node can be configured. In selective mode, a CVLAN-to-
SVLAN relationship can be defined.
Layer 2 VLAN port mapping that allows the cards to be configured as multiple Gigabit Ethernet TXPs
and MXPs.
Y-cable protection is configurable in TXP and MXP modes.
Two protection schemes are available in Layer 2 mode. They are:
1+1 protection—Protection scheme to address card, port, or shelf failures for client ports.
Fast Automatic Protection—Protection scheme to address card, port, or shelf failures for trunk ports.
178
Protocol Compatibility list
End-to-end Ethernet link integrity.

Pluggable client interface optic modules (SFPs and XFPs)—Client ports support tri-rate SX, LX, and
ZX SFPs, and 10-Gbps SR1 XFPs.
Pluggable trunk interface optic modules; trunk ports support the DWDM XFP.
Internet Group Management Protocol (IGMP) snooping that restricts the flooding of multicast traffic by
forwarding multicast traffic to those interfaces where a multicast device is present.
Multicast VLAN Registration (MVR) for applications using wide-scale deployment of multicast traffic
across an Ethernet ring-based service provider network.
Ingress CoS that assigns a CoS value to the port from 0 (highest) to 7 (lowest) and accepts CoS of
incoming frames.
Egress QoS that defines the QoS capabilities for the egress port.
MAC address learning that facilitates switch processing.
Storm Control that limits the number of packets passing through a port. You can define the maximum
number of packets allowed per second for the following types of traffic: Broadcast, Multicast, and
Unicast. The threshold for each type of traffic is independent and the maximum number of packets
allowed per second for each type of traffic is 16777215.

Protocol Compatibility list

Table 88: Protocol Compatibility List for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards
Protocol LI 1+1 FAPS IGMP REP LACP CFM EFM

LI No Yes Yes No No Yes No
1+1 No Yes Yes No No Yes No
FAPS Yes Yes Yes No No Yes No
IGMP Yes Yes Yes Yes No Yes No
REP No No No Yes No Yes No
LACP No No No No No No No
CFM Yes Yes Yes Yes Yes No No
EFM No No No No No No No
Trunk 1 and Trunk 2 on the faceplate

3-1 and 4-1 on CTC
3 (Trunk) and 4 (Trunk) on the Optics Thresholds table
179
Client Interface
Client Interface
The client interface is implemented with separately orderable SFP or XFP modules. The client
interfaces support the following tri-rate SFPs and XFPs using dual LC connectors and multimode fiber:
SFP - GE/1G-FC/2G-FC - 850 nm - MM - LC (PID ONS-SE-G2F-SX)
SFP - GE/1G-FC/2G-FC 1300 nm - SM - LC (PID ONS-SE-G2F-LX)
SFP - GE/1G-FC/2G-FC 1300 nm - SM - LC (PID ONS-SE-G2F-ZX)
SFP - 10/100/1000Base-T - Copper (PID ONS-SE-ZE-EL) Intra office up to 100; Cable: RJ45 STP
CAT5, CAT5E, and CAT6
SFP - 1000Base BX D/Gigabit Ethernet 1550 nm - SM - LC (PID ONS-SE-GE-BXD)
SFP - 1000Base BX U/Gigabit Ethernet 1550 nm - SM - LC (PID ONS-SE-GE-BXU)
SFP - Fast Ethernet 1310 nm - SM - LC (PID ONS-SI-100-LX10)
SFP - Fast Ethernet 1310 nm - MM - LC (PID ONS-SI-100-FX)
SFP - Fast Ethernet over DS1/E1 - SM - LC (PID ONS-SC-EOP1)
SFP - Fast Ethernet over DS3/E3 - SM - LC (PID ONS-SC-EOP3)
SFP - E1/DS1 over Fast Ethernet - SM - LC (PID ONS-SC-E1-T1-PW)
SFP - E3/DS3 PDH over Fast Ethernet - SM - LC (PID ONS-SC-E3-T3-PW)
Figure 14: Recommended Topology for Using ONS-SC-E1-T1-PW and ONS -SC-E3-T3-PW SFPs
The client interfaces support the following dual-rate XFP using dual LC connectors and single-mode fiber:
XFP - OC-192/STM-64/10GE/10-FC/OTU2 - 1310 SR - SM LC (PID: ONS-XC-10G-S1)
XFP - 10GE - 1550 nm - SM - LC (PID ONS-XC-10G-L2)
XFP - 10GE - 1550 nm - SM - LC (PID ONS-XC-10G-C)
Note If ONS-XC-10G-C XFP is used on GE_XP, 10GE_XP, GE_XPE, and

10GE_XPE cards on client port 1, the maximum temperature at which the
system qualifies is +45 degree Celsius.
180
The client interfaces support the following multimode XFP using dual LC connectors and multi-mode fiber:
• XFP - OC-192/10GFC/10GE - 850 nm MM LC (PID ONS-XC-10G-SR-MM)

The GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards have two 10 Gigabit Ethernet trunk ports operating at
10 Gigabit Ethernet (10.3125 Gbps) or 10 Gigabit Ethernet into OTU2 (nonstandard 11.0957 Gbps). The ports
are compliant with ITU-T G.707, ITU-T G.709, and Telcordia GR-253-CORE standards. The ports are capable
of carrying C-band and L-band wavelengths through insertion of DWDM XFPs. Forty channels are available in
the 1550-nm C band 100-GHz ITU grid, and forty channels are available in the L band.
The maximum system reach in filterless applications without the use of optical amplification or
regenerators is nominally rated at 23 dB over C-SMF and NZ-DS SMF fibers. This rating is not a product
specification, but is given for informational purposes. It is subject to change.
Configuration Management
The GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards support the following configuration
management parameters:
Port name—User-assigned text string.
Admin State/Service State—Administrative and service states to manage and view port status.
MTU—Provisionable maximum transfer unit (MTU) to set the maximum number of bytes per frames
accepted on the port.
Mode—Provisional port mode, either Autonegotiation or the port speed.
Flow Control—Flow control according to IEEE 802.1x pause frame specification can be enabled or
disabled for TX and RX ports.
Bandwidth—Provisionable maximum bandwidth allowed for the port.
Ingress CoS—Assigns a CoS value to the port from 0 (highest) to 7 (lowest) and accepts CoS of
incoming frames.
Egress QoS—Defines the QoS capabilities at the egress port.
NIM—Defines the port network interface management type based on Metro Ethernet Forum
specifications. Ports can be defined as UNI or NNI.
MAC Learning—MAC address learning to facilitate switch processing.
VLAN tagging provided according to the IEEE 802.1Q standard.
Note When the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards are provisioned
in a MXP or TXP mode, only the following parameters are available: Port
Name, State, MTU, Mode, Flow control, and Bandwidth.
181
Security
Security
GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE card ports can be provisioned to block traffic from a user-
defined set of MAC addresses. The remaining traffic is normally switched. You can manually specify the
set of blocked MAC addresses for each port. Each port of the card can receive traffic from a limited
predefined set of MAC addresses. The remaining traffic will be dropped. This capability is a subset of the
Cisco IOS “Port Security” feature.
Card Protection
The following card protection schemes are available for the GE_XP, 10GE_XP, GE_XPE, and
10GE_XPE cards.
Y-Cable protection
1+1 protection
L2 over DWDM protection- Fast Automatic Protection Switch (FAPS)
Related Procedures for Card Protection

The following are the related procedures for creating card protection on GE_XP, 10GE_XP, GE_XPE,
and 10GE_XPE cards:
NTP-G198 Creating 1+1 Protection for Cards, on page 347
DLP-G381 Provisioning Layer 2 Protection Settings, on page 595
IGMP Snooping
As networks increase in size, multicast routing becomes critically important as a means to determine which
segments require multicast traffic and which do not. IP multicasting allows IP traffic to be propagated from
one source to a number of destinations, or from many sources to many destinations. Rather than sending
one packet to each destination, one packet is sent to the multicast group identified by a single IP destination
group address. GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards can learn up to a maximum of 1024
multicast groups. This includes groups on all the VLANs.
Internet Group Management Protocol (IGMP) snooping restricts the flooding of multicast traffic by
forwarding multicast traffic to those interfaces where a multicast device is present.
When the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card receives an IGMP leave group message from
a host, it removes the host port from the multicast forwarding table after generating group specific queries
to ensure that no other hosts interested in traffic for the particular group are present on that port. Even in the
absence of any “leave” message, the cards have a timeout mechanism to update the group table with the
latest information. After a card relays IGMP queries from the multicast router, it deletes entries periodically
if it does not receive any IGMP membership reports from the multicast clients.
In a multicast router, general queries are sent on a VLAN when Protocol Independent Multicast (PIM) is enabled
on the VLAN. The GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card forwards queries to all ports belonging to
the VLAN. All hosts interested in this multicast traffic send Join requests and are added to the forwarding table
entry. The Join requests are forwarded only to router ports. By default, these router ports are
182
IGMP Snooping Guidelines and Restrictions
learned dynamically. However, they can also be statically configured at the port level in which case the
static configuration overrides dynamic learning.
For information about interaction of IGMP with other protocols, see the Protocol Compatibility list.
IGMP Snooping Guidelines and Restrictions

The following guidelines and restrictions apply to IGMP snooping on GE_XP, 10GE_XP, GE_XPE,
and 10GE_XPE cards:
IGMP snooping V2 is supported as specified in RFC 4541.
IGMP snooping V3 is not supported and the packets are flooded in the SVLAN.
Layer 2 multicast groups learned through IGMP snooping are dynamic.
GE_XP and 10GE_XP cards support IGMP snooping on 128 stacked VLANs and GE_XPE and
10GE_XPE cards support up to 256 stacked VLANs that are enabled.
IGMP snooping can be configured per SVLAN or CVLAN. By default, IGMP snooping is disabled on
all SVLANs and CVLANs.
IGMP snooping on CVLAN is enabled only when:
MVR is enabled.
UNI ports are in selective add and selective translate modes. For each UNI port, a CVLAN must
be specified for which IGMP snooping is to be enabled.
IGMP snooping can be enabled only on one CVLAN per port. If you enable IGMP snooping on
CVLAN, you cannot enable IGMP snooping on the associated SVLAN and vice versa. The number of
VLANs that can be enabled for IGMP snooping cannot exceed 128.
When IGMP snooping is enabled on double-tagged packets, CVLAN has to be the same on all ports
attached to the same SVLAN.
When IGMP snooping is working with the Fast Automatic Protection Switch (FAPS) in a ring-based
setup, it is advisable to configure all NNI ports as static router ports. This minimizes the multicast
traffic hit when a FAPS switchover occurs.
The following conditions are raised from IGMP snooping at the card:
MCAST-MAC-TABLE-FULL—This condition is raised when the multicast table is full and a new join
request is received. This table is cleared when at least one entry gets cleared from the multicast table
after the alarm is raised.
MCAST-MAC-ALIASING—This condition is raised when there are multiple L3 addresses that map to
the same L2 address in a VLAN. This is a transient condition.
For more information on severity level of these conditions and procedure to clear these alarms, refer to
the Cisco ONS 15454 DWDM Troubleshooting Guide.
183
Fast-Leave Processing
Fast-Leave Processing
Note Fast-Leave processing is also known as Immediate-Leave.
IGMP snooping Fast-Leave processing allows the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE to remove
an interface that sends a leave message from the forwarding table without first sending group specific
queries to the interface. When you enable IGMP Fast-Leave processing, the card immediately removes a
port from the IP multicast group when it detects an IGMP, version 2 (IGMPv2) leave message on that port.
Static Router Port Configuration

Multicast-capable ports are added to the forwarding table for every IP multicast entry. The card learns of
such ports through the PIM method.
Report Suppression
Report suppression is used to avoid a storm of responses to an IGMP query. When this feature is enabled, a
single IGMP report is sent to each multicast group in response to a single query. Whenever an IGMP
snooping report is received, report suppression happens if the report suppression timer is running. The
Report suppression timer is started when the first report is received for a general query. Then this time is
set to the response time specified in general query.
IGMP Statistics and Counters

An entry in a counter contains multicasting statistical information for the IGMP snooping capable GE_XP,
10GE_XP, GE_XPE, or 10GE_XPE card. It provides statistical information about IGMP messages that
have been transmitted and received. IGMP statistics and counters can be viewed via CTC from the
Performance > Ether Ports > Statistics tab.
This information can be stored in the following counters:
cisTxGeneralQueries—Number of general queries transmitted through an interface.
cisTxGroupSpecificQueries—Total group specific queries transmitted through an interface.
cisTxReports—Total membership reports transmitted through an interface.
cisTxLeaves—Total Leave messages transmitted through an interface.
cisRxGeneralQueries—Total general queries received at an interface.
cisRxGroupSpecificQueries—Total Group Specific Queries received at an interface.
cisRxReports—Total Membership Reports received at an interface.
cisRxLeaves—Total Leave messages received at an interface.
cisRxValidPackets—Total valid IGMP packets received at an interface.
cisRxInvalidPackets—Total number of packets that are not valid IGMP messages received at an interface.
184
Related Procedure for Enabling IGMP Snooping
Related Procedure for Enabling IGMP Snooping

To enable IGMP snooping on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards, see the NTP-
G204 Enabling IGMP Snooping on a Card, on page 614.
Multicast VLAN Registration

Multicast VLAN Registration (MVR) is designed for applications using wide-scale deployment of
multicast traffic across an Ethernet-ring-based service provider network (for example, the broadcast of
multiple television channels over a service-provider network). MVR allows a subscriber on a port to
subscribe and unsubscribe to a multicast stream on the network-wide multicast VLAN. It allows the single
multicast VLAN to be shared in the network while subscribers remain in separate VLANs. MVR provides
the ability to continuously send multicast streams in the multicast VLAN, but to isolate the streams from
the subscriber VLANs for bandwidth and security reasons.
MVR assumes that subscriber ports subscribe and unsubscribe (“Join” and “Leave”) these multicast
streams by sending out IGMP Join and Leave messages. These messages can originate from an IGMP
version-2-compatible host with an Ethernet connection. MVR operates on the underlying mechanism of
IGMP snooping. MVR works only when IGMP snooping is enabled.
The card identifies the MVR IP multicast streams and their associated MAC addresses in the card
forwarding table, intercepts the IGMP messages, and modifies the forwarding table to include or remove
the subscriber as a receiver of the multicast stream, even though the receivers is in a different VLAN than
the source. This forwarding behavior selectively allows traffic to cross between different VLANs.
Note When MVR is configured, the port facing the router must be configured as NNI in order to allow the router
to generate or send multicast stream to the host with the SVLAN. If router port is configured as UNI, the
MVR will not work properly.
Related Procedure for Enabling MVR

To enable MVR on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards, see the NTP-G206
Enabling MVR on a Card, on page 616.
MAC Address Learning

The GE_XPE and 10 GE_XPE cards support 32K MAC addresses. MAC address learning can be enabled or
disabled per SVLAN on GE_XPE and 10 GE_XPE cards. The cards learn the MAC address of packets they
receive on each port and add the MAC address and its associated port number to the MAC address learning table.
As stations are added or removed from the network, the GE_XPE and 10 GE_XPE cards update the MAC
address learning table, adding new dynamic addresses and aging out those that are currently not in use.
MAC address learning can be enabled or disabled per SVLAN. When the configuration is changed
from enable to disable, all the related MAC addresses are cleared. The following conditions apply:
If MAC address learning is enabled on per port basis, the MAC address learning is not enabled on all
VLANs, but only on VLANs that have MAC address learning enabled.
If per port MAC address learning is disabled then the MAC address learning is disabled on all VLANs,
even if it is enabled on some of the VLAN supported by the port.
185
Related Procedure for MAC Address Learning
If the per port MAC address learning is configured on GE-XP and 10 GE-XP cards, before upgrading
to GE-XPE or 10 GE-XPE cards, enable MAC address learning per SVLAN. Failing to do so
disables MAC address learning.
Related Procedure for MAC Address Learning

To enable MAC address learning on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards, see
the DLP-G221 Enabling MAC Address Learning on SVLANs, on page 603.
MAC Address Retrieval

MAC addresses learned can be retrieved or cleared on GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards
provisioned in L2-over-DWDM mode. The MAC addresses can be retrieved using the CTC or TL1 interface.
GE_XPE and 10GE_XPE cards support 32K MAC addresses and GE_XP and 10GE_XP cards support
16K MAC addresses. To avoid delay in processing requests, the learned MAC addresses are retrieved using
an SVLAN range. The valid SVLAN range is from 1 to 4093.
The MAC addresses of the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards can also be retrieved. The
card MAC addresses are static and are used for troubleshooting activities. One MAC address is assigned to
each client, trunk, and CPU ports of the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card. These internal
MAC addresses can be used to determine if the packets received on the far-end node are generated by
GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards.
For MAC address retrieval, the following conditions apply:
The cards must be provisioned in L2-over-DWDM mode.
MAC address learning must be enabled per SVLAN on GE_XPE or 10 GE_XPE cards.
MAC address learning must be enabled per port on GE_XP or 10 GE_XP cards.
Related Procedure for MAC Address Retrieving

To retrieve and clear MAC addresses on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards, see
the NTP-G237 Retrieving and Clearing MAC Addresses on SVLANs, on page 606.
Link Integrity
The GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE card support end-to-end Ethernet link integrity. This
capability is integral to providing an Ethernet private line service and correct operation of Layer 2 and
Layer 3 protocols on the attached Ethernet devices.
The link integrity feature propagates a trunk fault on all the affected SVLAN circuits in order to squelch the
far end client interface. Ethernet-Advanced IP Services (E-AIS) packets are generated on a per-
port/SVLAN basis. An E-AIS format is compliant with ITU Y.1731.
Note E-AIS packets are marked with a CoS value of 7 (also called .1p bits). Ensure that the network is not
overloaded and there is sufficient bandwidth for this queue in order to avoid packet drops.
186
Related Procedure for Enabling Link Integrity
When link integrity is enabled on a per-port SVLAN basis, E-AIS packets are generated when the
following alarms are raised;
LOS-P
OTUKLOF/LOM
SIGLOSS
SYNCHLOSS
OOS
PPM not present
When link integrity is enabled, GE_XP and 10 GE_XP card supports up to128 SVLANs and GE_XPE,
10 GE_XPE can support up to 256 SVLANs.
Related Procedure for Enabling Link Integrity

To enable link integrity on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards, see the NTP-
G205 Enabling Link Integrity on a Card, on page 609.
Ingress CoS
Ingress CoS functionality enables differentiated services across the GE_XPE and 10GE_XPE cards. A
wide range of networking requirements can be provisioned by specifying the class of service applicable to
each transmitted traffic.
When a CVLAN is configured as ingress CoS, the per-port settings are not considered. A maximum of
128 CVLAN and CoS relationships can be configured.
Related Procedure for Enabling Ingress CoS

To enable Ingress CoS on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards, see the:
DLP-G380 Provisioning Ethernet Settings, on page 579
DLP-G612 Modifying the Parameters of the Channel Group Using CTC, on page 544
CVLAN Rate Limiting

CVLAN rate limiting is supported on GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards. CVLAN rate
limiting is supported for QinQ service in selective add mode. The following limitations and restrictions
apply to CVLAN rate limiting:
CVLAN rate limiting is not supported for the following service types:
Selective translate mode
Transparent mode
Selective double add mode
Selective translate add mode
187
Related Procedure for Provisioning CVLAN Rate
Untagged packets
CVLAN range
Services associated with the channel group
CVLAN rate limiting and SVLAN rate limiting cannot be applied to the same service instance.
Pseudo-IOS command line interface (PCLI) is not supported for CVLAN rate limiting.
A VLAN profile with Link Integrity option enabled cannot be used to perform CVLAN rate limiting.
On GE_XP and 10 GE_XP cards, CVLAN rate limiting can be applied to up to 128 services. However,
the number of provisionable CVLAN rate limiting service instances is equal to 192 minus the number
of SVLAN rate limiting service instances present on the card (subject to a minimum of 64 CVLAN
rate limiting service instances).
On GE_XPE and 10 GE_XPE cards, CVLAN rate limiting can be applied to up to 256 services.
However, the number of provisionable CVLAN rate limiting service instances is equal to 384 minus
the number of SVLAN rate limiting service instances present on the card (subject to a minimum of 128
CVLAN rate limiting service instances).
Related Procedure for Provisioning CVLAN Rate

To provision CVLAN rate on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards, see the DLP-
G289 Provisioning CVLAN Rate Limiting on a Card, on page 611.
DSCP to CoS Mapping

DSCP to CoS mapping can be configured for each port. You can configure the CoS of the outer VLAN
based on the incoming DSCP bits. This feature is supported only on GE_XPE and 10GE_XPE cards. PCLI
is not supported for DSCP to CoS mapping.
DSCP to CoS mapping is supported for the following service types:
Selective add mode
Selective translate mode
Transparent mode
Selective double add mode
Selective translate add mode
Untagged packets
CVLAN range
Services associated with the channel group
Related Procedure for Provisioning CoS Based on DSCP

To provision CoS based on DSCP on the GE_XPE and 10GE_XPE cards, see the DLP-G384
Provisioning the QinQ Settings, on page 601.
188
Link Aggregation Control Protocol
Link Aggregation Control Protocol

Link Aggregation Control Protocol (LACP) is part of the IEEE802.3ad standard that allows you to
bundle several physical ports together to form a single logical channel. LACP allows a network device
such as a switch to negotiate an automatic bundling of links by sending LACP packets to the peer device.
LACP allows you to form a single Layer 2 link automatically from two or more Ethernet links. This protocol
ensures that both ends of the Ethernet link are functional and agree to be members of the aggregation group
before the link is added to the group. LACP must be enabled at both ends of the link to be operational.
For more information on LACP, refer to the IEEE802.3ad standard. For information about interaction
of LACP with other protocols, see the Protocol Compatibility list.
Advantages of LACP
LACP provides the following advantages:
High-speed network that transfers more data than any single port or device.
High reliability and redundancy. If a port fails, traffic continues on the remaining ports.
Hashing algorithm that allows to apply load balancing policies on the bundled ports.
Functions of LACP
LACP performs the following functions in the system:
Maintains configuration information to control aggregation.
Exchanges configuration information with other peer devices.
Attaches or detaches ports from the link aggregation group based on the exchanged configuration
information.
Enables data flow when both sides of the aggregation group are synchronized.
Modes of LACP
LACP can be configured in the following modes:
On — Default. In this mode, the ports do not exchange LACP packets with the partner ports.
Active — In this mode, the ports send LACP packets at regular intervals to the partner ports.
Passive — In this mode, the ports do not send LACP packets until the partner sends LACP packets.
After receiving the LACP packets from the partner ports, the ports send LACP packets.
Parameters of LACP
LACP uses the following parameters to control aggregation:
System Identifier—A unique identification assigned to each system. It is the concatenation of the
system priority and a globally administered individual MAC address.
Port Identification—A unique identifier for each physical port in the system. It is the concatenation of
the port priority and the port number.
189
Unicast Hashing Schemes
Port Capability Identification—An integer, called a key, that identifies the capability of one port to
aggregate with another port. There are two types of keys:
Administrative key—The network administrator configures this key.
Operational key—The LACP assigns this key to a port, based on its aggregation capability.
Aggregation Identifier—A unique integer that is assigned to each aggregator and is used for
identification within the system.
Unicast Hashing Schemes

LACP supports the following unicast hashing schemes:
Ucast SA VLAN Incoming Port
Ucast DA VLAN Incoming Port
Ucast SA DA VLAN Incoming port
Ucast Src IP TCP UDP
Ucast Dst IP TCP UDP
Ucast Src Dst IP TCP UDP
Note Unicast hashing schemes apply to unicast traffic streams only when the
destination MAC address is already learned by the card. Hence, MAC learning
must be enabled to support load balancing as per the configured hashing
scheme. If the destination MAC address is not learned, the hashing scheme is
Ucast Src Dst IP TCP UDP.
LACP Limitations and Restrictions

The LACP on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards has the following limitations
and restrictions:
Hot standby link state is not supported on the channel group.
Marker protocol generator is not supported.
ALS cannot be configured on the channel group.
Loopback configuration cannot be applied on the channel group.
Related Procedure for LACP

To provision Channel Group using LACP, see the NTP-G281 Managing the GE_XP, 10GE_XP,
GE_XPE, and 10GE_XPE Card Channel Group Settings, on page 541.
190
Ethernet Connectivity Fault Management
Ethernet Connectivity Fault Management

Ethernet Connectivity Fault Management (CFM) is part of the IEEE 802.1ag standard. The Ethernet CFM is an
end-to-end per service instance that supports the Ethernet layer Operations, Administration, and Management
(OAM) protocol. It includes proactive connectivity monitoring, link trace on a per service basis, fault
verification, and fault isolation for large Ethernet metropolitan-area networks (MANs) and WANs.
CFM is disabled on the card by default. CFM is enabled on all the ports by default.
For more information on CFM, refer to the IEEE 802.1ag standard. For information about interaction of
CFM with other protocols, see the Protocol Compatibility list. The following sections contain conceptual
information about Ethernet CFM.
Maintenance Domain
A maintenance domain is an administrative domain that manages and administers a network. You can
assign a unique maintenance level (from 0 to 7) to define the hierarchical relationship between domains.
The larger the domain, the higher the maintenance level for that domain. For example, a service provider
domain would be larger than an operator domain and might have a maintenance level of 6, while the
operator domain maintenance level would be 3 or 4.
Maintenance domains cannot intersect or overlap because that would require more than one entity to
manage it, which is not allowed. Domains can touch or nest if the outer domain has a higher maintenance
level than the nested domain. Maintenance levels of nesting domains must be communicated among the
administrating organizations. For example, one approach would be to have the service provider assign
maintenance levels to operators.
The CFM protocol supports up to eight maintenance domains on GE_XP, 10GE_XP, GE_XPE, and
10GE_XPE cards.
Maintenance Association
A maintenance association identifies a service within the maintenance domain. You can have any number
of maintenance associations within each maintenance domain. The CFM protocol supports up to 1500
maintenance associations on GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards.
Note Each maintenance association is mapped to a maintenance domain. This mapping is done to configure a
Maintenance End Point (MEP). The CFM protocol supports up to 1000 mappings on GE_XP,
10GE_XP, GE_XPE, and 10GE_XPE cards.
Maintenance End Points

Maintenance End Points (MEPs) reside at the edge of the maintenance domain and are active elements of
the Ethernet CFM. MEPs transmit Continuity Check messages at periodic intervals and receive similar
messages from other MEPs within a domain. MEPs also transmit Loopback and Traceroute messages at the
request of the administrator. MEPs confine CFM messages within the boundary of a maintenance domain
through the maintenance level. There are two types of MEPs:
Up (Inwards, towards the bridge)
Down (Outwards, towards the wire).
191
Maintenance Intermediate Points
You can create up to 255 MEPs and MIPs together on GE_XP and 10GE_XP cards. You can create up to
500 MEPs and MIPs together on GE_XPE and 10GE_XPE cards.
The MEP continuity check database (CCDB) stores information that is received from other MEPs in
the maintenance domain. The card can store up to 4000 MEP CCDB entries.
Maintenance Intermediate Points

Maintenance Intermediate Points (MIPs) are internal to the maintenance domain and are passive elements
of the Ethernet CFM. They store information received from MEPs and respond to Linktrace and Loopback
CFM messages. MIPs forward CFM frames received from MEPs and other MIPs, drop all CFM frames at a
lower level, and forward all CFM frames at a higher level.
You can create up to 255 MEPs and MIPs together on GE_XP and 10GE_XP cards. You can create up to
500 MEPs and MIPs together on GE_XPE and 10GE_XPE cards.
The MIP CCDB maintains the information received for all MEPs in the maintenance domain. The card
can store up to 4000 MIP CCDB entries.
CFM Messages
The Ethernet CFM on GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards supports the following messages:
Continuity Check—These messages are exchanged periodically among MEPs. They allow MEPs to
discover other MEPs within a domain and allow MIPs to discover MEPs. These messages are
confined to a domain.
Loopback—These messages are unicast messages that a MEP transmits, at the request of an
administrator, to verify connectivity to a specific maintenance point. A reply to a loopback message
indicates whether a destination is reachable.
Traceroute—These messages are multicast messages that a MEP transmits, at the request of an
administrator, to track the path to a destination MEP.
CFM Limitations and Restrictions

The CFM on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards has the following limitations
and restrictions:
CFM is not supported on channel groups.
CFM is not enabled on protected ports running REP, FAPS, and 1+1.
Y.1731 enhancements including AIS, LCK, and performance monitoring messages along with CFM are
not supported.
IEEE CFM MIB is not supported.
L1 and CFM are mutually exclusive on a SVLAN because LI and CFM use the same MAC address.
MAC security and CFM are mutually exclusive on the card due to hardware resource constraints.
Related Procedure for Ethernet CFM

For information about the supported Ethernet CFM features on the GE_XP, 10GE_XP, GE_XPE,
and 10GE_XPE cards, see the NTP-G283 Managing the Card CFM Settings, on page 553.
192
Ethernet OAM
Ethernet OAM
The Ethernet OAM protocol is part of the IEEE 802.3ah standard and is used for installing, monitoring, and
troubleshooting Ethernet MANs and Ethernet WANs. This protocol relies on an optional sublayer in the
data link layer of the OSI model. The Ethernet OAM protocol was developed for Ethernet in the First Mile
(EFM) applications. The terms Ethernet OAM and EFM are interchangeably used and both mean the same.
Normal link operation does not require Ethernet OAM. You can implement Ethernet OAM on any full-
duplex point-to-point or emulated point-to-point Ethernet link for a network or part of a network (specified
interfaces). OAM frames, called OAM Protocol Data Units (OAM PDUs), use the slow protocol
destination MAC address 0180.c200.0002. OAM PDUs are intercepted by the MAC sublayer and cannot
propagate beyond a single hop within an Ethernet network.
Ethernet OAM is disabled on all interfaces by default. When Ethernet OAM is enabled on an interface,
link monitoring is automatically turned on.
For more information on Ethernet OAM protocol, refer to IEEE 802.3ah standard. For information
about interaction of Ethernet OAM with other protocols, see the Protocol Compatibility list.
Components of the Ethernet OAM

Ethernet OAM consists of two major components, the OAM Client and the OAM Sublayer.
OAM Client
The OAM client establishes and manages the Ethernet OAM on a link. The OAM client also enables and
configures the OAM sublayer. During the OAM discovery phase, the OAM client monitors the OAM
PDUs received from the remote peer and enables OAM functionality. After the discovery phase, the OAM
client manages the rules of response to OAM PDUs and the OAM remote loopback mode.
OAM Sublayer
The OAM sublayer presents two standard IEEE 802.3 MAC service interfaces:
One interface facing toward the superior sub-layers, which include the MAC client (or link aggregation).
Other interface facing toward the subordinate MAC control sublayer.
The OAM sublayer provides a dedicated interface for passing OAM control information and OAM PDUs
to and from the client.
Benefits of the Ethernet OAM

Ethernet OAM provides the following benefits:
Competitive advantage for service providers
Standardized mechanism to monitor the health of a link and perform diagnostics
Features of the Ethernet OAM

The Ethernet OAM protocol has the following OAM features:
Discovery—Identifies devices in the network and their OAM capabilities. The Discovery feature uses
periodic OAM PDUs to advertise the OAM mode, configuration, and capabilities. An optional phase
allows the local station to accept or reject the configuration of the peer OAM entity.
193
Ethernet OAM Limitations and Restrictions
Link Monitoring—Detects and indicates link faults under a variety of conditions. It uses the event
notification OAM PDU to notify the remote OAM device when it detects problems on the link.
Remote Failure Indication—Allows an OAM entity to convey the failure conditions to its peer through
specific flags in the OAM PDU.
Remote Loopback—Ensures link quality with a remote peer during installation or troubleshooting.
Ethernet OAM Limitations and Restrictions

The Ethernet OAM on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards has the following
limitations and restrictions:
CFM, REP, link integrity, LACP, FAPS, IGMP on SVLAN and L2 1+1 protection are not supported
with EFM.
IEEE EFM MIB is not supported.
EFM cannot be enabled or disabled at the card level.
Unidirectional functionality is not supported.
Errored Symbol Period, Rx CRC errors, Tx CRC errors are not supported.
OAM PDUs are limited to 1 frame per second.
Dying Gasp and critical events are not supported.
Note Dying Gasp RFI is not generated on GE_XP, 10GE_XP, GE_XPE, and
10GE_XPE cards. However, if the peer device sends a dying gasp RFI, the card
detects it and raises an alarm.
Related Procedure for Ethernet OAM

For information about the supported Ethernet OAM features on the GE_XP, 10GE_XP, GE_XPE,
and 10GE_XPE cards, see the NTP-G285 Managing the Card EFM Settings, on page 565.
Resilient Ethernet Protocol

The Resilient Ethernet Protocol (REP) is a protocol used to control network loops, handle link failures,
and improve convergence time.
REP performs the following tasks:
Controls a group of ports connected in a segment.
Ensures that the segment does not create any bridging loops.
Responds to link failures within the segment.
Supports VLAN load balancing.
For information about interaction of REP with other protocols, see the Protocol Compatibility list.
194
REP Segments
REP Segments
A REP segment is a chain of ports connected to each other and configured with a segment ID. Each
segment consists of regular segment ports and two edge ports. A GE_XP, 10GE_XP, GE_XPE, or
10GE_XPE card can have up to 2 ports that belong to the same segment, and each segment port can have
only one external neighbor port.
A segment protects only against a single link failure. Any more failures within the segment result in loss
of connectivity.
Characteristics of REP Segments

REP segments have the following characteristics:
If all the ports in the segment are operational, one port blocks traffic for each VLAN. If VLAN load
balancing is configured, two ports in the segment control the blocked state of VLANs.
If any port in the segment is not operational, all the other operational ports forward traffic on all VLANs
to ensure connectivity.
In case of a link failure, the alternate ports are immediately unblocked. When the failed link comes up,
a logically blocked port per VLAN is selected with minimal disruption to the network.
REP Port States

Ports in REP segments take one of three roles or states: Failed, Open, or Alternate.
A port configured as a regular segment port starts as a failed port.
When the neighbor adjacencies are determined, the port transitions to the alternate port state, blocking
all the VLANs on the interface. Blocked port negotiations occur and when the segment settles, one
blocked port remains in the alternate role and all the other ports become open ports.
When a failure occurs in a link, all the ports move to the failed state. When the alternate port receives
the failure notification, it changes to the open state, forwarding all VLANs.
Link Adjacency
Each segment port creates an adjacency with its immediate neighbor. Link failures are detected and acted
upon locally. If a port detects a problem with its neighbor, the port declares itself non-operational and
REP converges to a new topology.
REP Link Status Layer (LSL) detects its neighbor port and establishes connectivity within the segment. All
VLANs are blocked on an interface until the neighbor port is identified. After the neighbor port is identified,
REP determines the neighbor port that must be the alternate port and the ports that must forward traffic.
Each port in a segment has a unique port ID. When a segment port starts, the LSL layer sends packets
that include the segment ID and the port ID.
A segment port does not become operational if the following conditions are satisfied:
No neighbor port has the same segment ID or more than one neighbor port has the same segment ID.
The neighbor port does not acknowledge the local port as a peer.
195
Fast Reconvergence
Fast Reconvergence
REP runs on a physical link and not on per VLAN. Only one hello message is required for all VLANs
that reduces the load on the protocol.
REP Hardware Flood Layer (HFL) is a transmission mechanism that floods packets in hardware on an
admin VLAN. HFL avoids the delay that is caused by relaying messages in software. HFL is used for fast
reconvergence in the order of 50 to 200 milliseconds.
VLAN Load Balancing

You must configure two edge ports in the segment for VLAN load balancing. One edge port in the REP
segment acts as the primary edge port; the other edge port as the secondary edge port. The primary edge
port always participates in VLAN load balancing in the segment. VLAN load balancing is achieved by
blocking certain VLANs at a configured alternate port and all the other VLANs at the primary edge port.
REP Configuration Sequence

You must perform the following tasks in sequence to configure REP:
Configure the REP administrative VLAN or use the default VLAN 1. The range of REP admin VLAN
is 1 to 4093. VLAN 4094 is not allowed.
Add ports to the segment in interface configuration mode.
Enable REP on ports and assign a segment ID to it. REP is disabled on all ports by default. The range
of segment ID is 1 to 1024.
Configure two edge ports in the segment; one port as the primary edge port and the other as the
secondary edge port.
If you configure two ports in a segment as the primary edge port, for example, ports on different
switches, REP selects one of the ports to serve as the primary edge port based on port priority. The
Primary option is enabled only on edge ports.
Configure the primary edge port to send segment topology change notifications (STCNs) and VLAN
load balancing to another port or to other segments. STCNs and VLAN load balancing configurations
are enabled only for edge ports.
Note A port can belong to only one segment. Only two ports can belong to the same
segment. Both the ports must be either regular ports or edge ports. However, if
the No-neighbor port is configured, one port can be an edge port and another
port can be a regular port.
REP Supported Interfaces

REP supports the following interfaces:
REP is supported on client (UNI) and trunk (NNI) ports.
Enabling REP on client ports allows protection at the access or aggregation layer when the cards are
connected to the L2 network.
196
REP Limitations and Restrictions
• Enabling REP on trunk ports allows protection at the edge layer when the cards are connected in a ring.
REP Limitations and Restrictions

The REP on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards has the following limitations
and restrictions:
Fast re-convergence and VLAN load balancing are not supported on UNI ports in transparent mode.
Native VLAN is not supported.
CFM, EFM, link integrity, LACP, FAPS, and L2 1+1 protection are not supported on ports that are
configured as part of REP segment and vice versa.
When a node installed with GE_XP, GE_XPE, 10GE_XP, or 10GE_XPE cards configured with REP or
LACP is upgraded, traffic loss may occur. This traffic loss is due to reconvergence when the cards soft
reset during the upgrade process.
NNI ports cannot be configured as the primary edge port or blocking port at the access or aggregation
layer.
Only three REP segments can be configured on GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards.
Consider the following configuration:
More than one REP closed segment is configured on the GE_XP, 10GE_XP, GE_XPE, and
10GE_XPE cards and the same HFL admin VLAN is enabled on the switches.
If two different segments are configured on more than one common switch, the following
consequences happen.
Layer 1 loop
Flooding of HFL packets across segments if one REP segment fails
Segment goes down due to LSL time out even if the segment does not have faults
Hence, it is recommended not to configure two different segments on more than one common switch.
Consider the following configuration:

VLAN Load Balancing is configured on GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards by
specifying the VLB preempt delay.
Primary and secondary edge ports are configured on the same switch.
HFL or LSL is activated.
This configuration leads to high convergence time during manual premption, VLB activation,
and deactivation (400 to 700 milliseconds).
Related Procedure for Managing the REP Settings

To manage the REP settings on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards, see the NTP-
G287 Managing the Card REP Settings, on page 571.
For more information about the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards, see:
197
Related Procedures for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards
http://www.cisco.com/en/US/prod/collateral/optical/ps5724/ps2006/product_data_sheet0900aecd805ebef7.html
http://www.cisco.com/en/US/prod/collateral/optical/ps5724/ps2006/product_data_sheet0900aecd805ec093.html
Related Procedures for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards

The following is the list of procedures and tasks related to the configuration of the GE_XP,
10GE_XP, GE_XPE, and 10GE_XPE cards:
NTP-G165 Modifying the Ethernet, Line and PM Thresholds, on page 577
NTP-G311 Provisioning the Storm Control Settings, on page 608
NTP-G208 Provisioning SVLAN Rate Limiting on a Card, on page 611
NTP-G314 Adding a Card on FAPS Ring, on page 629
ADM-10G Card
The ADM-10G card operates on ONS 15454 SONET, ONS 15454 SDH, ONS 15454 M2, ONS 15454 M6,
and DWDM networks to carry optical signals and Gigabit Ethernet signals over DWDM wavelengths for
transport. The card aggregates lower bit-rate client SONET or SDH signals (OC-3/STM-1, OC-12/STM-4,
OC-48/STM-16, or Gigabit Ethernet) onto a C-band tunable DWDM trunk operating at a higher OC-
192/STM-64 rate. In a DWDM network, the ADM-10G card transports traffic over DWDM by mapping
Gigabit Ethernet and SONET or SDH circuits onto the same wavelength with multiple protection options.
You can install and provision the ADM-10G card in a linear configuration in:
Slots 1 to 5 and 12 to 16 in standard and high-density ONS 15454 ANSI shelves (15454-SA-ANSI or
15454-SA-HD), the ETSI ONS 15454 standard shelf assembly, or the ONS 15454 ETSI high-density
shelf assembly
Caution Fan-tray assembly 15454E-CC-FTA (ETSI shelf)/15454-CC-FTA (ANSI shelf)

must be installed in a shelf where the ADM-10G card is installed.
The card is compliant with ITU-T G.825 and ITU-T G.783 for SDH signals. It supports concatenated and
non-concatenated AU-4 mapped STM-1, STM-4, and STM-16 signals as specified in ITU-T G.707. The
card also complies with Section 5.6 of Telcordia GR-253-CORE and supports synchronous transport signal
(STS) mapped OC-3, OC-12, and OC-48 signals as specified in the standard.
The client SFP and trunk XFP are compliant with interface requirements in Telcordia GR-253-
CORE, ITU-T G.957 and/or ITU-T G.959.1, and IEEE 802.3.
198
Key Features
Key Features
The ADM-10G card has the following high-level features:
Operates with the control card.
Interoperable with TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10EX_C, and OTU2_XP cards.
Has built-in OC-192/STM-64 add/drop multiplexing function including client, trunk, and STS
cross-connect.
Supports both single-card and double-card (ADM-10G peer group) configuration.
Supports path protection/SNCP on client and trunk ports for both single-card and double-card
configuration. The card does not support path protection/SNCP between a client port and a trunk
port. Path protection/SNCP is supported only between two client ports or two trunk ports.
Supports 1+1 protection on client ports for double-card configuration only.
Supports SONET, SDH, and Gigabit Ethernet protocols on client SFPs.
Supports XFP DWDM trunk interface single wavelengths.
Returns zero bit errors when a control card switches from active to standby or when manual or forced
protection switches occur.
Has 16 SFP-based client interfaces (gray, colored, coarse wavelength division multiplexing (CWDM),
and DWDM optics available).
Supports STM1, STM4, STM16, and Gigabit Ethernet client signals (8 Gigabit Ethernet maximum).
Has one XFP-based trunk interface supporting E-FEC/FEC and ITU-T G.709 for double-card
configuration.
Has two XFP-based trunk interface supporting E-FEC/FEC and ITU-T G.709 for single-card configuration.
Has two SR XFP interlink interfaces supporting redundancy connection with protection board and
pass-through traffic for double-card configuration.
Supports frame-mapped generic framing procedure (GFP-F) and LEX mapping for Ethernet over
SONET or SDH.
Can be installed or pulled from operation, in any slot, without impacting other service cards in the shelf.
Supports client to client hairpinning, that is, creation of circuits between two client ports for both single-card
and double-card configuration. See the Circuit Provisioning for more detailed information.

ADM-10G POS Encapsulation, Framing, and CRC

The ADM-10G card supports Cisco EoS LEX (LEX) and generic framing procedure framing (GFP-
F) encapsulation on 8 POS ports corresponding to 8 GigE ports (Port 1 to Port 8) in both single-card
and double-card (ADM-10G peer group) configuration.
You can provision framing on the ADM-10G card as either the default GFP-F or LEX framing. With GFP-
F framing, you can configure a 32-bit cyclic redundancy check (CRC) or none (no CRC) (the default). LEX
199
POS Overview
framing supports 16-bit or 32-bit CRC configuration. The framing type cannot be changed when there is
a circuit on the port.
On the CTC, navigate to card view and click the Provisioning > Line> Ethernet Tab. To see the various
parameters that can be configured on the ethernet ports, see the “CTC Display of ethernet Port Provisioning
Status” section in the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and
Configuration Guide. Parameters such as, admin state, service state, framing type, CRC, MTU and soak
time for a port can be configured.
It is possible to create an end-to-end circuit between equipment supporting different kinds of encapsulation
(for example, LEX on one side and GFP-F on other side). But, under such circumstances, traffic does not
pass through, and an alarm is raised if there is a mismatch.
POS Overview
Ethernet data packets need to be framed and encapsulated into a SONET/SDH frame for transport across the
SONET/SDH network. This framing and encapsulation process is known as packet over SONET/SDH (POS).
The Ethernet frame comes into the ADM-10G card on a standard Gigabit Ethernet port and is processed
through the card’s framing mechanism and encapsulated into a POS frame. When the POS frame exits, the
ADM-10G card is in a POS circuit, and this circuit is treated as any other SONET circuit (STS) or SDH
circuit (VC) in the node. It is cross-connected and rides the SONET/SDH signal out the port of an optical
card and across the SONET/SDH network.
The destination of the POS circuit is a card or a device that supports the POS interface. Data packets in
the destination card frames are removed and processed into ethernet frames. The Ethernet frames are then
sent to a standard Ethernet port of the card and transmitted onto an Ethernet network.
POS Framing Modes

A POS framing mode is the type of framing mechanism employed by the ADM-10G card to frame and
encapsulate data packets into a POS signal. These data packets were originally encapsulated in Ethernet
frames that entered the standard Gigabit Ethernet interface of the ADM-10G card.
GFP-F Framing
The GFP-F framing represent standard mapped Ethernet over GFP-F according to ITU-T G.7041. GFP-F
defines a standard-based mapping of different types of services onto SONET/SDH. GFP-F maps one
variable length data packet onto one GFP packet. GFP-F comprises of common functions and payload
specific functions. Common functions are those shared by all payloads. Payload-specific functions are
different depending on the payload type. GFP-F is detailed in the ITU recommendation G.7041.
LEX Framing
LEX encapsulation is a HDLC frame based Cisco Proprietary protocol, where the field is set to values
specified in Internet Engineering Task Force (IETF) RFC 1841. HDLC is one of the most popular Layer 2
protocols. The HDLC frame uses the zero insertion/deletion process (commonly known as bit stuffing) to
ensure that the bit pattern of the delimiter flag does not occur in the fields between flags. The HDLC frame
is synchronous and therefore relies on the physical layer to provide a method of clocking and synchronizing
the transmission and reception of frames. The HDLC framing mechanism is detailed in the IETF’s RFC
1662, “PPP in HDLC-like Framing.”
200
GFP Interoperability
GFP Interoperability
The ADM-10G card defaults to GFP-F encapsulation that is compliant with ITU-T G.7041. This mode allows the
card to operate with ONS 15310-CL, ONS 15310-MA, ONS 15310-MA SDH, or ONS 15454 data cards (for
example, ONS 15454 CE100T-8 or ML1000-2 cards). GFP encapsulation also allows the ADM-10G card to
interoperate with other vendors Gigabit Ethernet interfaces that adhere to the ITU-T G.7041 standard.
LEX Interoperability
The LEX encapsulation is compliant with RFC 1841. This mode allows the card to operate with ONS
15310-CL, ONS 15310-MA, ONS 15310-MA SDH, or ONS 15454 data cards (for example, G1000-
4/G1K-4 cards, CE-1000-4, ONS 15454 CE100T-8 or ML1000-2 cards).
201
Faceplate and Block Diagram

Figure 15: ADM-10G Card Faceplate and Block Diagram
202
Port Configuration Rules
Port Configuration Rules

Figure 16: ADM-10G Card Port Capacities
Port 17 acts as trunk2 or ILK1 interface based on single-card or double-card configuration.
Client Interfaces
The ADM-10G card uses LC optical port connectors supports up to 16 SFPs that can be utilized for OC-
N/STM-N traffic. Eight of the SFPs can be used for Gigabit Ethernet. The interfaces can support any mix
of OC-3/STM-1, OC-12/STM-4, OC-48/STM-16, or Gigabit Ethernet of any reach, such as SX, LX, ZX,
SR, IR, or LR. The interfaces support a capacity of:
4 x OC-48/STM-16
16 x OC-12/STM-4
16 x OC-3/STM-1
8 x GE
The supported client SFPs and XFPs are:

Gray SFPs
1000Base-SX SFP 850 nm (ONS-SE-G2F-SX=)
1000Base-LX SFP 1310 nm (ONS-SE-G2F-LX=)
OC48/STM16 IR1, OC12/STM4 SR1, OC3/STM1 SR1, GE-LX multirate SFP 1310 nm
(ONS-SE-Z1=)
OC3/STM1 IR1, OC12/STM4 IR1 multirate SFP 1310 nm (ONS-SI-622-I1=)
OC48/STM16 SR1 SFP 1310 nm (ONS-SI-2G-S1=)
OC48/STM16 IR1 SFP 1310 nm (ONS-SI-2G-I1=)
OC48/STM16, 1550 LR2, SM LC (ONS-SE-2G-L2=)
Colored DWDM SFPs

1000Base-ZX SFP 1550 nm (ONS-SI-GE-ZX=)
OC3/STM1 LR2 SFP 1550 nm (ONS-SI-155-L2=)
203
Interlink Interfaces
OC48/STM16 LR2 SFP 1550 nm (ONS-SI-2G-L2=)

OC48/STM16 SFP (ONS-SC-2G-xx.x)
Note xx.x = 28.7 to 60.6. ONS-SC-2G-28.7, ONS-SC-2G-33.4, ONS-SC-2G-41.3,

ONS-SC-2G-49.3, and ONS-SC-2G-57.3 are supported from Release 8.5 and
later.
CWDM SFPs
OC48/STM16/GE CWDM SFP (ONS-SC-Z3-xxxx)
XFPs
OC-192/STM-64/10GE XFP 1550 nm (ONS-XC-10G-I2)
Interlink Interfaces
Two 2R interlink interfaces, called ILK1 (Port 17) and ILK2 (Port 18), are provided for creation of ADM-10G
peer groups in double-card configurations. In a single-card configuration, Port 17 (OC-192/STM-64) and Port 18
(OC-192/STM-64 or OTU2 payload) must be configured as trunk interfaces. In a double-card configuration
(ADM-10G peer group), Ports 17 and 18 must be configured as ILK1 and ILK2 interfaces, respectively.
Physically cabling these ports between two ADM-10G cards, located on the same shelf, allows you to
configure them as an ADM-10G peer group.The ILK ports carry 10 Gb of traffic each.
The interlink interfaces support STM64 SR1 (ONS-XC-10G-S1=) XFP and 10GE BASE
SR (ONS-XC-10G-SR-MM=) XFPs.

The ADM-10G card supports OC-192/STM-64 signal transport and ITU-T G.709 digital wrapping
according to the ITU-T G.709 standard.The ADM-10G card supports three trunk XFPs:
Two DWDM trunks, and one trunk interface in a single-card configuration.
One DWDM trunk XFP in a double-card configuration.
The supported DWDM trunk XFPs are:

10G DWDM (ONS-XC-10G-xx.x=) (colored XFP)
STM64 SR1 (ONS-XC-10G-S1=) (gray XFP)
When using OC-48/STM-16 traffic, some contiguous port configurations are unavailable due to
hardware limitations. This limitation does not impact the Gigabit Ethernet payload.
204
Note The ADM-10G card cannot be used in the same shelf with SONET or SDH cross-connect cards.
Table 89: OC-48/STM-16 Configuration Limitations
OC-48/STM-16 Port Number Ports Restricted from Optical Traffic

OC-48/STM-16 on Port 13 No OC-N/STM-N on Port 1 through Port 3
Note The total traffic rate for each trunk cannot exceed OC-192/STM-64 on each ADM-10G card, or for each
ADM-10G peer group.
Note Gigabit Ethernet is supported on Ports 1 through 8. Ports 9 through Port 12 support only OC-3/STM-1 or
OC-12/STM-4.
Additionally, the following guidelines apply to the ADM-10G card:

Trunk Port 17 supports OC-192/STM-64.
Trunk Ports 18 and 19 support OC-192/STM-64 and OTU2.
The interlink port supports OC-192/STM-64.
Up to six ADM-10G cards can be installed in one shelf.
Up to 24 ADM-10G cards can be installed per network element (NE) regardless of whether the card is
installed in one shelf or in multiple shelves.
The card can be used in all 15454-SA-ANSI and 15454-SA-HD shelves as well as ETSI ONS 15454
standard and high-density shelves.
A lamp test function can be activated from CTC to ensure that all LEDs are functional.
The card can operate as a working protected or working non-protected card.
In a redundant configuration, an active card hardware or software failure triggers a switch to the standby
card. This switch is detected within 10 ms and is completed within 50 ms.
ADM-10G cards support jumbo frames with MTU sizes of 64 to 9,216 bytes; the maximum is 9,216.
After receiving a link or path failure, the ADM-10G card can shut down only the downstream Gigabit
Ethernet port.
205
Security
Note In ADM-10G cards, the Gigabit Ethernet port does not support flow control.
Security
The ADM-10G card that an SFP or XFP is plugged into implements the Cisco Standard Security Code
Check Algorithm that keys on the vendor ID and serial number.
If a pluggable port module (PPM) is plugged into a port on the card but fails the security code check
because it is not a Cisco PPM, a minor NON-CISCO-PPM alarm is raised.
If a PPM with an unqualified product ID is plugged into a port on this card—that is, the PPM passes
the security code as a Cisco PPM but it has not been qualified for use on the ADM-10G card— a minor
UNQUAL-PPM alarm is raised.
Protection
The ADM-10G card supports 1+1 and SONET path protection and SDH SNCP protection architectures in
compliance with Telcordia GR-253-CORE, Telcordia GR-1400-CORE, and ITU-T G.841 specifications.
Circuit Protection Schemes

The ADM-10G card supports path protection/SNCP circuits at the STS/VC4 (high order) level and can be
configured to switch based on signal degrade calculations. The card supports path protection/SNCP on
client and trunk ports for both single-card and double-card configuration.
Note The ADM-10G card supports path protection/SNCP between client ports and trunk port 17. The card does
not support path protection/SNCP between client ports and trunk ports 18 or 19. The card does not
support path protection/SNCP between port 17 and trunk ports 18 and 19.
The card allows open-ended path protection/SNCP configurations incorporating other vendor equipment.
In an open-ended path protection/SNCP, you can specify one source point and two possible endpoints (or
two possible source points and one endpoint) and the legs can include other vendor equipment. The source
and endpoints are part of the network discovered by CTC.
Port Protection Schemes

The ADM-10G card supports unidirectional and bidirectional 1+1 APS protection schemes on client ports
for double-card configuration (ADM-10G peer group) only. 1+1 APS protection scheme is not supported in
single-card configuration. For 1+1 optical client port protection, you can configure the system to use any
pair of like facility interfaces that are on different cards of the ADM-10G peer group.
Circuit Provisioning
The ADM-10G card supports STS circuit provisioning both in single-card and double-card (ADM-10G
peer group) configuration. The card allows you to create STS circuits between:
206
Circuit Provisioning
Client and trunk ports

Two trunk ports
Two client ports (client-to-client hairpinning)
Note Circuits between two trunk ports are called pass-through circuits.
For an ADM-10G card in single-card configuration, if you are creating STS circuits between two client
ports, the following limitation must be considered:
• Gigabit Ethernet to Gigabit Ethernet connections are not supported.
For an ADM-10G card that is part of an ADM-10G peer group, if you are creating STS circuits between
two client ports or between client and trunk ports, the following limitations must be considered:
Gigabit Ethernet to Gigabit Ethernet connections are not supported.
Optical channel (OC) to OC, OC to Gigabit Ethernet, and Gigabit Ethernet to OC connections between
two peer group cards are supported. Peer group connections use interlink port bandwidth, hence,
depending on the availability/fragmentation of the interlink port bandwidth, it may not be possible to
create an STS circuit from the Gigabit Ethernet/OC client port to the peer card trunk port. This is
because, contiguous STSs (that is, STS-3c, STS-12c, STS-24c, and so on) must be available on the
interlink port for circuit creation.
An alarm is raised on the port having the STS circuit created on the port of the ADM-10G card.
Right click the alarm and choose Select Affected Circuits to view the circuits affected by this alarm.
CTC informs that no STS circuits are affected by the alarm instead of highlighting the circuit passing
over that port in Circuits pane.
Note There are no limitations to create an STS circuit between two trunk ports.
The two ADM-10G cards used in a paired mode use interlink ports ILK1 (Port 17) and ILK2 (Port 18). A
CCAT or VCAT circuit created between the peer ADM-10G cards uses the ILK1 port if the source or
destination is Port 19. The circuits created with a single ADM-10G card uses the ILK2 port.
If the circuit is of type STS-nc (where n is an integer and can take values 3,6,9,12,18,24,36,48,96) and uses
the ILK2 port, then the starting timeslot needs to use specific timeslots for traffic to flow. The timeslots can
be 12m+1 for STS-12c circuits and 48m+1 (where m is an integer and can take values 0,1,2,3...) for STS-
48c circuits. The timeslots can be 3m+1 for the other STS-nc circuits.
The following example illustrates how to use the correct timeslot for an ILK2 port:
If there is no circuit on the ILK2 port and a STS-3c circuit is created, the circuit uses timeslots 1 to 3. An STS-
12c circuit must be created on the ILK2 port later. The STS-12c circuit must have used timeslots 4 to
However, the STS-12c circuit uses timeslots starting from 12m+1 (1, 13, 25, and so on) as defined in the
above rule. Therefore, before creating the STS-12c circuit, dummy circuits must be created in CTC that
consumes STS-9 bandwidth.
207
ADM-10G CCAT and VCAT Characteristics
ADM-10G CCAT and VCAT Characteristics

The ADM-10G card supports high-order (HO) contiguous concatenation (CCAT) and HO virtual
concatenation (VCAT) circuits on 8 GigE ports (Port 1 to Port 8) in both single-card and double-card
(ADM-10G peer group) configuration.
To enable end-to-end connectivity in a VCAT circuit that traverses through a third-party network, you
can use Open-Ended VCAT circuit creation.
The ADM-10G card supports flexible non-LCAS VCAT groups (VCGs). With flexible VCGs, the ADM-
10G can perform the following operations:
Add or remove members from groups
Put members into or out of service, which also adds/removes them from the group
Add or remove cross-connect circuits from VCGs
Any operation on the VCG member is service effecting (for instance, adding or removing members from
the VCG). Adding or removing cross-connect circuits is not service-affecting, if the associated members
are not in the group
The ADM-10G card allows independent routing and protection preferences for each member of a VCAT
circuit. You can also control the amount of VCAT circuit capacity that is fully protected, unprotected, or
uses Protection Channel Access (PCA) (when PCA is available). Alarms are supported on a per-member as
well as per virtual concatenation group (VCG) basis.
The ADM-10G card supports both automatic and manual routing for VCAT circuit, that is, all members are
manually or automatically routed. Bidirectional VCAT circuits are symmetric, which means that the same
number of members travel in each direction. With automatic routing, you can specify the constraints for
individual members; with manual routing, you can select different spans for different members. Two types of
automatic and manual routing are available for VCAT members: common fiber routing and split routing.
The ADM-10G card supports VCAT common fiber routing and VCAT split fiber (diverse) routing. With VCAT
split fiber routing, each member can be routed independently through the SONET or SDH or DWDM network
instead of having to follow the same path as required by CCAT and VCAT common fiber routing. This allows a
more efficient use of network bandwidth, but the different path lengths and different delays encountered may
cause slightly different arrival times for the individual members of the VCG. The VCAT differential delay is this
relative arrival time measurement between members of a VCG. The maximum tolerable VCAT split fiber routing
differential delay for the ADM-10G card is approximately 55 milliseconds. A loss of alignment alarm is
generated if the maximum differential delay supported is exceeded.
The differential delay compensation function is automatically enabled when you choose split fiber routing
during the CTC circuit configuration process. CCAT and VCAT common fiber routing do not enable or
need differential delay support.
Caution Protection switches with switching time of less than 60 milliseconds are not guaranteed with the differential
delay compensation function enabled. The compensation time is added to the switching time.
Note For TL1, EXPBUFFERS parameter must be set to ON in the ENT-VCG command to enable support for
split fiber routing.
208
Available Circuit Sizes
Available Circuit Sizes

Table 90: Supported SONET Circuit Sizes of ADM-10G card
CCAT VCAT High Order
STS-1 STS-1-1nV (n= 1 to 21)
STS-3c STS-3c-mv (m= 1 to 7)
STS-6c
STS-9c
STS-12c
STS-24c
Table 91: Supported SDH Circuit Sizes of ADM-10G card
CCAT VCAT High Order
VC-4 VC-4-mv (m= 1 to 7)
VC-4-2c
VC-4-3c
VC-4-4c
VC-4-8c
Note In ADM-10G cards, the Gigabit Ethernet port does not support flow control. When less than seven VC-4s
are configured for the port, with the client traffic expected to be below the line rate, a burst in traffic
beyond the supposed bandwidth leads to packet loss. It is, therefore, recommended to use an external flow
control mechanism with less than seven VC-4s configured. Connecting a GE-XP or GE-XPE card between
the client traffic and the ADM-10G Gigabit Ethernet interface enables such flow control.
Related Procedure for VCAT Circuit

The following is the list of procedures related to creating VCAT circuits:
NTP-G245 Creating an Automatically Routed VCAT Circuit
NTP-G246 Creating a Manually Routed VCAT Circuit
209
Intermediate Path Performance Monitoring
Intermediate Path Performance Monitoring

Intermediate path performance monitoring (IPPM) allows a node to monitor the constituent channel of
an incoming transmission signal. You can enable IPPM for STS/VC-4s payload on OCn and Trunk ports
of ADM-10G card. The IPPM is complaint with GR253/G.826.
Software Release 9.2 and higher enables the ADM-10G card to monitor the near-end and far-end PM data
on individual STS/VC-4 payloads by enabling IPPM. After provisioning IPPM on the card, service
providers can monitor large amounts of STS/VC-4 traffic through intermediate nodes, thus making
troubleshooting and maintenance activities more efficient. IPPM occurs only on STS/VC-4 paths that have
IPPM enabled, and TCAs are raised only for PM parameters on the selected IPPM paths.
For a CCAT circuit, you can enable IPPM only on the first STS/VC-4 of the concatenation group. For a
VCAT circuit, you can enable IPPM independently on each member STS/VC-4 of the concatenation group.
Related Procedure for IPPM

To enable IPPM on the ADM-10G card, see:
NTP-G247 Enabling or Disabling Path Performance Monitoring on Intermediate Nodes
Pointer Justification Count Performance Monitoring

Pointers are used to compensate for frequency and phase variations. Pointer justification counts indicate
timing errors on SONET networks. When a network is out of synchronization, jitter and wander occur on
the transported signal. Excessive wander can cause terminating equipment to slip.
Slips cause different effects in service. Voice service has intermittent audible clicks. Compressed voice
technology has short transmission errors or dropped calls. Fax machines lose scanned lines or experience
dropped calls. Digital video transmission has distorted pictures or frozen frames. Encryption service loses
the encryption key, causing data to be transmitted again.
Pointers provide a way to align the phase variations in STS and VC4 payloads. The STS payload pointer is
located in the H1 and H2 bytes of the line overhead. Clocking differences are measured by the offset in
bytes from the pointer to the first byte of the STS synchronous payload envelope (SPE) called the J1 byte.
Clocking differences that exceed the normal range of 0 to 782 can cause data loss.
There are positive (PPJC) and negative (NPJC) pointer justification count parameters. PPJC is a count of path-
detected (PPJC-PDET-P) or path-generated (PPJC-PGEN-P) positive pointer justifications. NPJC is a count of
path-detected (NPJC-PDET-P) or path-generated (NPJC-PGEN-P) negative pointer justifications depending on
the specific PM name. PJCDIFF is the absolute value of the difference between the total number of detected
pointer justification counts and the total number of generated pointer justification counts. PJCS-PDET-P is a
count of the one-second intervals containing one or more PPJC-PDET or NPJC-PDET. PJCS-PGEN-P is a count
of the one-second intervals containing one or more PPJC-PGEN or NPJC-PGEN.
A consistent pointer justification count indicates clock synchronization problems between nodes. A
difference between the counts means that the node transmitting the original pointer justification has timing
variations with the node detecting and transmitting this count. Positive pointer adjustments occur when the
frame rate of the SPE is too slow in relation to the rate of the STS-1.
You must enable PPJC and NPJC performance monitoring parameters for ADM-10Gcard. In CTC, the
count fields for PPJC and NPJC PMs appear white and blank unless they are enabled on the card view
Provisioning tab.
210
Performance Monitoring Parameter Definitions

This section describes the STS and VC-4 path performance monitoring parameters that ADM-10G
card support.
Table 92: STS Near-end Path Performance Monitoring Parameters
Parameter Definition
CV-P Near-End STS Path Coding Violations (CV-P) is a

count of BIP errors detected at the STS path layer
(that is, using the B3 byte). Up to eight BIP errors can
be detected per frame; each error increments the
current CV-P second register.
ES-P Near-End STS Path Errored Seconds (ES-P) is a count

of the seconds when at least one STS path BIP error
was detected. An AIS Path (AIS-P) defect (or a
lower-layer, traffic-related, near-end defect) or a Loss
of Pointer Path (LOP-P) defect can also cause an
ES-P.
SES-P Near-End STS Path Severely Errored Seconds (SES-P)

is a count of the seconds when K (2400) or more STS
path BIP errors were detected. An AIS-P defect (or a
lower-layer, traffic-related, near-end defect) or an
LOP-P defect can also cause an SES-P.
UAS-P Near-End STS Path Unavailable Seconds (UAS-P) is

a count of the seconds when the STS path was
unavailable. An STS path becomes unavailable when
ten consecutive seconds occur that qualify as SES-Ps,
and continues to be unavailable until ten consecutive
seconds occur that do not qualify as SES-Ps.
FC-P Near-End STS Path Failure Counts (FC-P) is a count

of the number of near-end STS path failure events. A
failure event begins when an AIS-P failure, an LOP-P
failure, a UNEQ-P failure, or a Section Trace
Identifier Mismatch Path (TIM-P) failure is declared.
A failure event also begins if the STS PTE that is
monitoring the path supports Three-Bit (Enhanced)
Remote Failure Indication Path Connectivity
(ERFI-P-CONN) for that path. The failure event ends
when these failures are cleared.
PPJC-PDET-P Positive Pointer Justification Count, STS Path

Detected (PPJC-PDET-P) is a count of the positive
pointer justifications detected on a particular path in
an incoming SONET signal.
211
PPJC-PGEN-P Positive Pointer Justification Count, STS Path
Generated (PPJC-PGEN-P) is a count of the
positive pointer justifications generated for a
particular path to reconcile the frequency of the SPE
with the local clock.
NPJC-PDET-P Negative Pointer Justification Count, STS Path
Detected (NPJC-PDET-P) is a count of the
negative pointer justifications detected on a
particular path in an incoming SONET signal.
NPJC-PGEN-P Negative Pointer Justification Count, STS Path
Generated (NPJC-PGEN-P) is a count of the
negative pointer justifications generated for a
particular path to reconcile the frequency of the SPE
with the local clock.
PJCDIFF-P Pointer Justification Count Difference, STS Path

(PJCDIFF-P) is the absolute value of the difference
between the total number of detected pointer
justification counts and the total number of
generated pointer justification counts. That is,
PJCDiff-P is equal to (PPJC-PGEN-P - NPJC-
PGEN-P) - (PPJC-PDET-P - NPJC-PDET-P).
PJCS-PDET-P Pointer Justification Count Seconds, STS Path

Detect (NPJCS-PDET-P) is a count of the one-
second intervals containing one or more PPJC-
PDET or NPJC-PDET.
PJCS-PGEN-P Pointer Justification Count Seconds, STS Path

Generate (PJCS-PGEN-P) is a count of the one-
second intervals containing one or more PPJC-
PGEN or NPJC-PGEN.
Table 93: VC-4 Near-end Path Performance Monitoring Parameters
HP-EB High-Order Path Errored Block (HP-EB) indicates

that one or more bits are in error within a block.
HP-BBE High-Order Path Background Block Error (HP-BBE)

is an errored block not occurring as part of an SES.
HP-ES High-Order Path Errored Second (HP-ES) is a

one-second period with one or more errored blocks
or at least one defect.
212
HP-SES High-Order Path Severely Errored Seconds (HP-SES)

is a one-second period containing 30 percent or more
errored blocks or at least one defect. SES is a subset
of ES.
HP-UAS High-Order Path Unavailable Seconds (HP-UAS) is

a count of the seconds when the VC path was
unavailable. A high-order path becomes unavailable
when ten consecutive seconds occur that qualify as
HP-SESs, and it continues to be unavailable until ten
consecutive seconds occur that do not qualify as
HP-SESs.
HP-BBER High-Order Path Background Block Error Ratio

(HP-BBER) is the ratio of BBE to total blocks in
available time during a fixed measurement interval.
The count of total blocks excludes all blocks during
SESs.
HP-ESR High-Order Path Errored Second Ratio (HP-ESR) is

the ratio of errored seconds to total seconds in
HP-SESR High-Order Path Severely Errored Second Ratio

(HP-SESR) is the ratio of SES to total seconds in
HP-PPJC-PDET High-Order, Positive Pointer Justification Count, Path

Detected (HP-PPJC-Pdet) is a count of the positive
pointer justifications detected on a particular path on
an incoming SDH signal.
HP-NPJC-PDET High-Order, Negative Pointer Justification Count,

Path Detected (HP-NPJC-Pdet) is a count of the
negative pointer justifications detected on a particular
path on an incoming SDH signal.
HP-PPJC-PGEN High-Order, Positive Pointer Justification Count, Path

Generated (HP-PPJC-Pgen) is a count of the positive
pointer justifications generated for a particular path.
HP-NPJC-PGEN High-Order, Negative Pointer Justification Count,

Path Generated (HP-NPJC-Pgen) is a count of the
negative pointer justifications generated for a
particular path.
213
ADM-10G Functions
HP-PJCDIFF High-Order Path Pointer Justification Count

Difference (HP-PJCDiff) is the absolute value of the
difference between the total number of detected
pointer justification counts and the total number of
generated pointer justification counts. That is,
HP-PJCDiff is equal to (HP-PPJC-PGen -
HP-NPJC-PGen) - (HP-PPJC-PDet - HP-NPJC-PDet).
HP-PJCS-PDET High-Order Path Pointer Justification Count Seconds

(HP-PJCS-PDet) is a count of the one-second intervals
containing one or more HP-PPJC-PDet or
HP-NPJC-PDet.
HP-PJCS-PGEN High-Order Path Pointer Justification Count Seconds

(HP-PJCS-PGen) is a count of the one-second
intervals containing one or more HP-PPJC-PGen or
HP-NPJC-PGen.
ADM-10G Functions
The following functions of the ADM-10G card are explained in the "Card Features" chapter:
Related Procedures for ADM-10G Card

The following is the list of procedures and tasks related to the configuration of the ADM-10G card:
Parameters, and Thresholds, on page 416
NTP-G200 Creating, Deleting, and Managing STS or VC Circuits for the ADM-10G Card
NTP-G333 Adding an ADM-10G Card to an Existing Topology, on page 445
DLP-G775 Displaying the Bandwidth Usage of the STS Timeslots

Purpose This task displays the bandwidth usage of the STS
timeslots on the interlink interfaces, ILK1 (Port 17)
and ILK2 (Port 18), in ADM-10G double-card
configuration.
Tools/Equipment None
214
OTU2_XP Card
Prerequisite Procedures • DLP-G46 Log into CTC

• DLP-G403 Creating the ADM-10G Peer Group,
on page 417
Required/As Needed As needed
Onsite/Remote Onsite or remote
Security Level Provisioning or higher
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the ADM-10G card where
you want to display the bandwidth usage of the STS timeslots on the interlink interfaces.
Step 2 Click the Maintenance > ILK Utilization tabs.
Step 3 In the Interlink Ports drop-down list, choose the interlink port for which you want to display the bandwidth
usage and click Refresh.
The bandwidth usage of STS 1 to 192 timeslots are displayed in the Free/Occupied column. The
bandwidth usage values are updated only after clicking the Refresh button.
Step 4 Return to your originating procedure (NTP).
OTU2_XP Card
The OTU2_XP card is a single-slot card with four ports with XFP-based multirate (OC-192/STM-64,
10GE, 10G FC, IB_5G) Xponder. The OTU2_XP card supports multiple configurations.
Table 94: OTU2_XP Card Configurations and Ports
Configuration Port 1 Port 2 Port 3 Port 4
2 x 10G transponder Client port 1 Client port 2 Trunk port 1 Trunk port 2
2 x 10G standard Trunk port 1 Trunk port 2 Trunk port 1 Trunk port 2
regenerator (with
enhanced FEC
(E-FEC) only on one
port)
10 GE LAN Phy to Client port Client port in Trunk port Trunk port in
WAN Phy transponder or trunk transponder or
port in regenerator regenerator
configuration configuration
215
Key Features
Configuration Port 1 Port 2 Port 3 Port 4
1 x 10G E-FEC Not used Not used Trunk port Trunk port
regenerator (with
E-FEC on two ports)
1 x 10G splitter Client port Not used Trunk port Trunk port (protect)
protected (working)
transponder
All the four ports are ITU-T G.709 compliant and support 40 channels (wavelengths) at 100-GHz
channel spacing in the C-band (that is, the 1530.33 nm to 1561.42 nm wavelength range).
The OTU2_XP card can be installed in Slots 1 to 6 and 12 to 17 in ONS 15454 DWDM chassis, Slots 2 and
3 in ONS 15454 M2, Slots 2 to 7 in ONS 15454 M6, Slots 2 to 16 in Cisco NCS 2015 chassis. The
OTU2_XP card supports SONET SR1, IR2, and LR2 XFPs, 10GE BASE SR, SW, LR, LW, ER, EW, and
ZR XFPs, and 10G FC MX-SN-I and SM-LL-L XFPs.
Caution Fan-tray assembly 15454E-CC-FTA (ETSI shelf)/15454-CC-FTA (ANSI shelf) must be installed in a
shelf where the OTU2_XP card is installed.
Key Features
The OTU2_XP card has the following high-level features:
10G transponder, regenerator, and splitter protection capability.
Compatible with the ONS 15454 ANSI high-density shelf assembly, the ETSI ONS 15454 shelf
assembly, and the ETSI ONS 15454 high-density shelf assembly. Compatible with TCC2/TCC2P/
TCC3/TNC/TNCE/TSC/TSCE cards.
Note Due to memory limitations, TCC2/TCC2P cards are not supported from
Release 10.5.2 onwards. As a result, in a multishelf configuration, the
TCC2/TCC2P card cannot be a node controller or a shelf controller. Upgrade
the TCC2/TCC2P card to a TCC3 card
Interoperable with TXP_MR_10E and TXP_MR_10E_C cards.

Four port, multirate (OC-192/STM-64, 10G Ethernet WAN Phy, 10G Ethernet LAN Phy, 10G Fibre
Channel, IB_5G) client interface. The client signals are mapped into an ITU-T G.709 OTU2 signal
using standard ITU-T G.709 multiplexing.
ITU-T G.709 framing with standard Reed-SoloMon (RS) (255,239) FEC. Performance monitoring and
ITU-T G.709 Optical Data Unit (ODU) synchronous mapping. Enhanced FEC (E-FEC) with ITU-T
G.709 ODU with greater than 8 dB coding gain.
The trunk rate remains the same irrespective of the FEC configuration. The error coding performance
can be provisioned as follows:
FEC—Standard ITU-T G.709.
216
Key Features
E-FEC—Standard ITU-T G.975.1 (subclause I.7)
IEEE 802.3 frame format supported for 10 Gigabit Ethernet interfaces. The minimum frame size is 64
bytes. The maximum frame size is user-provisionable.
Supports fixed/no fixed stuff mapping (insertion of stuffing bytes) for 10G Ethernet LAN Phy signals
(only in transponder configuration).
Supports 10G Ethernet LAN Phy to 10G Ethernet WAN Phy conversion on Ports 1 (client port) and 3
(trunk port).
Supports 10G Ethernet LAN Phy to WAN Phy conversion using CTC and TL1. When enabled on the
OTU2_XP card, the first Channel (Ports 1 and 3) supports LAN to WAN conversion. The second
channel carries normal 10GE, 10G FC, and OC192/STM64 traffic.
The LAN Phy to WAN Phy conversion functions in accordance to WAN Interface Sublayer (WIS)
mechanism as defined by IEEE802.3ae (IEEE Std 802.3ae-2002, Amendment to CSMA/CD).
Default configuration is transponder, with trunk ports configured as ITU-T G.709 standard FEC.
In transponder or regenerator configuration, if one of the ports is configured the corresponding port is
automatically created.
In regenerator configuration, only Ports 3 and 4 can be configured as E-FEC. Ports 1 and 2 can be
configured only with standard FEC.
When port pair 1-3 or 2-4 is configured as regenerator (that is, card mode is standard regenerator), the
default configuration on Ports 3 and 4 is automatically set to standard FEC.
When Ports 3 and 4 are configured as regenerator (that is, card mode is E-FEC regenerator), the default
configuration on both these ports is automatically set to E-FEC.
In a splitter-protected transponder configuration, the trunk ports (Port 3 and Port 4) are configured as
ITU-T G.709 standard FEC or E-FEC. OCHCC circuits with different trunk wavelengths can be
configured for the working and protect paths. The process of setting the trunk wavelengths is similar
to the “DLP-G367 Change the 2.5G Multirate Transponder Trunk Wavelength Settings” task on page
11-175. OCHCC circuits having different trunk wavelengths on the working and protect paths can be
upgraded to GMPLS circuits.
Supports protection through Y-cable protection scheme.
Note When enabled, the 10G Ethernet LAN Phy to WAN Phy conversion feature does
not support Y-cable protection on the LAN to WAN interface (ports 1 and 3).
Client ports support SONET SR1, IR2, and LR2 XFPs, 10GE BASE SR, SW, LR, LW, ER, EW, and
ZR XFPs, and 10G FC MX-SN-I and SM-LL-L XFPs.
Following are the OTU2 link rates that are supported on the OTU2_XP trunk port:
Standard G.709 (10.70923 Gbps) when the client is provisioned as “SONET” (including 10G
Ethernet WAN PHY) (9.95328 Gbps).
G.709 overclocked to transport 10GE as defined by ITU-T G. Sup43 Clause 7.2 (11.0491 Gbps)
when the client is provisioned as “10G Ethernet LAN Phy” (10.3125 Gbps) with “No Fixed
Stuff” enabled.
217
OTU2_XP Card Interface
G.709 overclocked to transport 10GE as defined by ITU-T G. Sup43 Clause 7.1 (11.0957 Gbps)
when the client is provisioned as “10G Ethernet LAN Phy” (10.3125 Gbps) with “No Fixed
Stuff” disabled.
G.709 proprietary overclocking mode to transport 10G FC (11.3168 Gbps) when the client is
provisioned as “10G Fiber Channel” (10.518 Gbps).
Proprietary rate at the trunk when the client is provisioned as IB_5G.
The MTU setting is used to display the ifInerrors and OverSizePkts counters on the receiving trunk and
client port interfaces. Traffic of frame sizes up to 65535 bytes pass without any packet drops, from the
client port to the trunk port and vice versa irrespective of the MTU setting.
The OTU2_XP card configured in the Transponder or Mixed mode does not support egress Ethernet
variables such as ifOutOctets, ifOutDiscards, ifOutMulticastPkts, and ifOutBroadcastPkts.

OTU2_XP Card Interface

The OTU2_XP card is a multi-functional card that operates in different configurations, such as
transponder, standard regenerator, E-FEC regenerator, and 10G Ethernet LAN Phy to WAN Phy
conversion mode. The OTU2_XP card acts as a protected transponder, when the 10G Ethernet LAN Phy to
WAN Phy is in splitter protected transponder configuration mode.
Depending on the configuration of the OTU2_XP card, the ports act as client or trunk ports (see Table 94:
OTU2_XP Card Configurations and Ports). The following section describes the client and trunk rates
supported on the OTU2_XP card for different card configurations:
Client Interface
In transponder and 10G Ethernet LAN Phy to WAN Phy card configurations, Ports 1 and 2 act as client
ports and in splitter protected transponder configuration, Port 1 acts as a client port. For these card
configurations, the client rates supported are:
OC-192/STM-64
10G Ethernet WAN Phy
10G Ethernet LAN Phy
10G Fibre Channel
IB_5G
Trunk Interface
In transponder, 10G Ethernet LAN Phy to WAN Phy, and splitter protected transponder card configurations,
Ports 3 and 4 act as trunk ports. For these card configurations, the trunk rates supported are:
OC-192/STM-64
10G Ethernet WAN Phy
218

10G Fibre Channel
OTU2 with ITU-T G.709 for OC-192 client interface
OTU2e with ITU-T G.709 for 10G Ethernet LAN Phy client interface
Proprietary rate at the trunk when the client is provisioned as IB_5G
In standard regenerator card configuration, all four ports act as trunk ports and in E-FEC regenerator
configuration, Ports 3 and 4 act as the trunk ports. For these card configurations, the trunk rate supported
is OTU2 G.709
Note The above mentioned OTU2 signal must be an OC-192/STM-64, 10G Ethernet WAN Phy, 10G Ethernet
LAN Phy, or 10G Fibre Channel signal packaged into an OTU2 G.709 frame. Additionally, the standard
regenerator and E-FEC regenerator configuration supports an OTU2 signal that is OTU2 has been
generated by multiplexing four ODU1 signals.
The OTU2_XP card supports the following configuration management parameters:
Card Configuration—Provisionable card configuration: Transponder, Standard Regen, Enhanced FEC,
or Mixed, or 10G Ethernet LAN Phy to WAN Phy.
Port Mode—Provisionable port mode when the card configuration is set as Mixed. The port mode can
be chosen as either Transponder or Standard Regen for each port pair (1-3 and 2-4). For card
configurations other than Mixed, CTC automatically sets the port mode depending on the selected card
configuration. For 10G Ethernet LAN Phy to WAN Phy mode, CTC automatically selects the port pair
(1-3) as 10G Ethernet LAN Phy to WAN Phy. Port pair (2-4) in 10G Ethernet LAN Phy to WAN Phy
mode is selected as Transponder or Standard Regen.
Termination Mode—Provisionable termination mode when the card configuration is set as either
Transponder or Mixed. The termination mode can be chosen as Transparent, Section, or Line. For
Standard Regen and Enhanced FEC card configurations, CTC automatically sets the termination mode
as Transparent. For 10G Ethernet LAN Phy to WAN Phy mode, CTC automatically selects the
Termination Mode of port pair (1-3) as Line. You cannot provision the Termination Mode parameter.
Fault Signalling—Provisionable Fault Signaling mode configuration when the card configuration is set
as either Transponder, Mixed, or Standard Regen. The Fault Signaling mode configuration can be
chosen as AIS/Send Local Fault or Squelch/Laser-Off. For Enhanced FEC card configuration, CTC
automatically sets the AIS/Send Local Fault or Squelch/Laser-Off mode configuration as AIS/Send
Local Fault. For 10G Ethernet LAN Phy to WAN Phy mode, the CTC automatically selects the
AIS/Send Local Fault or Squelch/Laser-Off of port pair (1-3) as Squelch/Laser-Off. You cannot
provision the AIS/Send Local Fault or Squelch/Laser-Off parameter.
Note When Fault Signaling is enabled in Standard Regen configuration with port
pairs (1-3) and (2-4), Squelch/Laser-Off is supported on ports 1 and 2 and
AIS/Send Local Fault on ports 3 and 4.
219
OTU2_XP Card Configuration Rules
Note When you choose the 10G Ethernet LAN Phy to WAN Phy conversion, the
Termination mode is automatically set to LINE. The AIS/Squelch is set to
Squelch/Laser-Off and ODU Transparency is set to Cisco Extended Use for
Ports 1 and 3.
Regen Line Name—User-assigned text string for regeneration line name.

ODU Transparency—Provisionable ODU overhead byte configuration, either Transparent Standard Use
or Cisco Extended Use. See the ODU Transparency for more detailed information. For 10G Ethernet
LAN Phy to WAN Phy mode, CTC automatically selects the ODU Transparency as Cisco Extended
Use. You cannot provision the ODU Transparency parameter.
Port name—User-assigned text string.
Admin State/Service State—Administrative and service states to manage and view port status.
ALS Mode—Provisionable ALS function.
Reach—Provisionable optical reach distance of the port.
Wavelength—Provisionable wavelength of the port.
AINS Soak—Provisionable automatic in-service soak period.

The following rules apply to OTU2_XP card configurations:
When you preprovision the card, port pairs 1-3 and 2-4 come up in the default Transponder configuration.
The port pairs 1-3 and 2-4 can be configured in different modes only when the card configuration is
Mixed. If the card configuration is Mixed, you must choose different modes on port pairs 1-3 and 2-4
(that is, one port pair in Transponder mode and the other port pair in Standard Regen mode).
If the card is in Transponder configuration, you can change the configuration to Standard Regen or
Enhanced FEC.
If the card is in Standard Regen configuration and you have configured only one port pair, then
configuring payload rates for the other port pair automatically changes the card configuration to
Mixed, with the new port pair in Transponder mode.
If the card is in Standard Regen configuration, you cannot directly change the configuration to Enhanced
FEC. You have to change to Transponder configuration and then configure the card as Enhanced FEC.
If the card is in Enhanced FEC configuration, Ports 1 and 2 are disabled. Hence, you cannot directly
change the configuration to Standard Regen or Mixed. You must remove the Enhanced FEC group
by moving the card to Transponder configuration, provision PPM on Ports 1 and 2, and then change
the card configuration to Standard Regen or Mixed.
If the card is in Standard Regen or Enhanced FEC configuration, you cannot change the payload rate of
the port pairs. You have to change the configuration to Transponder, change the payload rate, and then
move the card configuration back to Standard Regen or Enhanced FEC.
220
If any of the affected ports are in IS (ANSI) or Unlocked-enabled (ETSI) state, you cannot change the
card configuration.
If IB_5G payload has to be provisioned, the NE Default should match the values. For more information on
editing the NE Default values, see the "NTP-G135 Edit Network Element Defaults” task.
Table 95: OTU2_XP Card Configuration for IB_5G Payload Provisioning
Parameter NE Default Name Value
FEC OTU2-XP.otn.otnLines.FEC Standard
ITU-T G.709 OTN OTU2-XP.otn.otnLines.G709OTN Enable
Termination Mode OTU2-XP.config.port.TerminationMode Transparent
ODU Transparency OTU2-XP.config.port.OduTransparency Cisco Extended Use
AIS/Squelch OTU2-XP.config.port.AisSquelchMode Squelch
If the card is changed to 10G Ethernet LAN Phy to WAN Phy, the first PPM port is deleted and
replaced by a 10G Ethernet port; the third PPM port is deleted and automatically replaced with
OC192/STM64 (SONET/SDH) port. The third PPM port is automatically deleted and the third PPM
port is replaced with OC192/STM64 (SONET/SDH).
Table 96: Card Configuration Transition Summary
Card Transition To
Configuration
Transponder Standard Regen Enhanced FEC Mixed 10G Ethernet
LAN Phy to WAN
Phy
Transponder — Yes Yes Yes Yes
Standard Regen Yes — No Yes Yes
Enhanced FEC Yes No — No No
Mixed Yes Yes No — Yes
221
Security
Card Transition To
Configuration
Transponder Standard Regen Enhanced FEC Mixed 10G Ethernet
LAN Phy to WAN
Phy
10G Ethernet Yes Yes No The 10G —

LAN Phy to Ethernet LAN
WAN Phy Phy to WAN
Phy to Mixed is
supported if the
Port pair 1-3 is
chosen as
Transponder.
The 10G
Ethernet LAN
Phy to WAN
Phy to Mixed is
not supported if
the Port pair 1-3
is chosen as
Standard Regen.
Security
The OTU2_XP card, when an XFP is plugged into it, implements the Cisco Standard Security Code
Check Algorithm that keys on vendor ID and serial number.
If a PPM is plugged into a port on the card but fails the security code check because it is not a Cisco PPM,
a NON-CISCO-PPM Not Reported (NR) condition occurs.
If a PPM with a non-qualified product ID is plugged into a port on this card, that is, the PPM passes the
security code as a Cisco PPM but it has not been qualified for use on the OTU2_XP card, a UNQUAL-
PPM NR condition occurs.
ODU Transparency
A key feature of the OTU2_XP card is the ability to configure the ODU overhead bytes (EXP bytes and RES
bytes 1 and 2) using the ODU Transparency parameter. The two options available for this parameter are:
Transparent Standard Use—ODU overhead bytes are transparently passed through the card. This option
allows the OTU2_XP card to act transparently between two trunk ports (when the card is configured in
Standard Regen or Enhanced FEC).
Cisco Extended Use—ODU overhead bytes are terminated and regenerated on both ports of the
regenerator group.
The ODU Transparency parameter is configurable only for Standard Regen and Enhanced FEC card
configuration. For Transponder card configuration, this parameter defaults to Cisco Extended Use and
cannot be changed.
222
Related Procedures for OTU2_XP Card
Note The Forward Error Correction (FEC) Mismatch (FEC-MISM) alarm will not be raised on OTU2_XP card
when you choose Transparent Standard Use.
For more information about the OTU2_XPcard, see

Related Procedures for OTU2_XP Card

The following is the list of procedures and tasks related to the configuration of the OTU2_XP card:
NTP-G199 Creating a Splitter Protection Group, on page 345
TXP_MR_10EX_C Card
The TXP_MR_10EX_C card is a multirate transponder card. The card is fully backward compatible with
TXP_MR_10E_C cards (only when the error decorrelator is disabled in the CTC on the
TXP_MR_10EX_C card). It processes one 10-Gbps signal (client side) into one 10-Gbps, 100-GHz
DWDM signal (trunk side). The TXP_MR_10EX_C card is tunable over the 82 channels of C-band (82
channels spaced at 50 GHz on the ITU grid).
You can install TXP_MR_10EX_C card in Slots 1 to 6 and 12 to 17 in ONS 15454 DWDM chassis, Slots 2
and 3 in ONS 15454 M2 chassis, Slots 2 to 7 in ONS 15454 M6. The card can be provisioned in linear,
BLSR/MS-SPRing, path protection/SNCP configurations or as a regenerator. The card can be used in the
middle of BLSR/MS-SPRing or 1+1 spans when the card is configured for transparent termination mode.
The TXP_MR_10EX_C card features an MLSE-based Universal Transponder 1550-nm tunable laser and a
separately orderable ONS-XC-10G-S1 1310-nm or ONS-XC-10G-L2 1550-nm laser XFP module for the
client port.
Note The PRE FEC BER performance of the TXP_MR_10EX_C card may be significantly low when compared
to the TXP_MR_10E card. However, this does not affect the Post FEC BER performance, but could
possibly affect any specific monitoring application that relies on the PRE FEC BER value (for example,
protection switching). In this case, the replacement of TXP_MR_10E card with the TXP_MR_10EX_C
may not work properly.
Note When the ONS-XC-10G-L2 XFP is installed, the TXP_MR_10EX_C card must be installed in a high-speed
slot (slot 6, 7, 12, or 13)
223
Key Features
Key Features
The key features of the TXP_MR_10EX_C card are:
A multi-rate client interface (available through the ONS-XC-10G-S1 XFP, ordered separately):
OC-192 (SR1)
10GE (10GBASE-LR)
10G-FC (1200-SM-LL-L)
(ONS-XC-10G-S1 version 3 only) IB_5G
An MLSE-based UT module tunable through 82 channels of C-band. The channels are spaced at 50
GHz on the ITU grid.
OC-192 to ITU-T G.709 OTU2 provisionable synchronous and asynchronous mapping.
Proprietary rate at the trunk when the client is provisioned as IB_5G.
For information about safety labels for the card, see the "Class 1M Laser Product Cards” section.
Caution You must use a 15-dB fiber attenuator (10 to 20 dB) when working with the TXP_MR_10EX_C card in a
loopback on the trunk port. Do not use direct fiber loopbacks with this card, because they can cause
irreparable damage to the card.
For more information about the TXP_MR_10EX_C card, see

Related Procedures for TXP_MR_10EX_C Card

The following is the list of procedures and tasks related to the configuration of the TXP_MR_10EX_C card:
MXP_2.5G_10EX_C card
The MXP_2.5G_10EX_C card is a DWDM muxponder supports transparent termination mode on the client side.
The faceplate designation of the card is “4x2.5G 10EX MXP.” The card multiplexes four 2.5-Gbps client signals
(4xOC48/STM-16 SFP) into a single 10-Gbps DWDM optical signal on the trunk side. The card
224
Key Features
provides wavelength transmission service for the four incoming 2.5-Gbps client interfaces.
The MXP_2.5G_10EX_C muxponder passes all SONET/SDH overhead bytes transparently.
The digital wrapper function (ITU-T G.709 compliant) formats the DWDM wavelength so that it can be
used to set up GCCs for data communications, enable FEC, or facilitate PM.
The MXP_2.5G_10EX_C card works with OTN devices defined in ITU-T G.709. The card supports
ODU1 to OTU2 multiplexing, an industry standard method for asynchronously mapping a SONET/SDH
payload into a digitally wrapped envelope. See the "Multiplexing Function” section.
The MXP_2.5G_10EX_C card is not compatible with the MXP_2.5G_10G card, which does not
support transparent termination mode.
You can install the MXP_2.5G_10EX_C card in Slots 1 to 6 and 12 to 17 in ONS 15454 DWDM chassis, Slots 2
and 3 in ONS 15454 M2 chassis, Slots 2 to 7 in ONS 15454 M6. You can provision a card in a linear
configuration, a BLSR/MS-SPRing, a path protection/SNCP, or a regenerator. The card can be used in the
middle of BLSR/MS-SPRing or 1+1 spans when the card is configured for transparent termination mode.
The MXP_2.5G_10EX_C card features a tunable 1550-nm C-band laser on the trunk port. The laser is tunable
across 82 wavelengths on the ITU grid with 50-GHz spacing between wavelengths. The card features four 1310-
nm lasers on the client ports and contains five transmit and receive connector pairs (labeled) on the card
faceplate. The card uses dual LC connectors on the trunk side and SFP modules on the client side for optical
cable termination. The SFP pluggable modules are SR or IR and support an LC fiber connector.
4xOC-48 OCHCC circuit is supported by G.709 and synchronous mode, which are necessary to provision
the 4xOC-48 OCHCC circuit.
Key Features
The MXP_2.5G_10EX_C card has the following high-level features:
Four 2.5-Gbps client interfaces (OC-48/STM-16) and one 10-Gbps trunk. The four OC-48 signals are
mapped into an ITU-T G.709 OTU2 signal using standard ITU-T G.709 multiplexing.
Onboard E-FEC processor: The processor supports both standard RS (specified in ITU-T G.709) and E-
FEC, which allows an improved gain on trunk interfaces with a resultant extension of the transmission
range on these interfaces. The E-FEC functionality increases the correction capability of the
transponder to improve performance, allowing operation at a lower OSNR compared to the standard
RS (255,239) correction algorithm.
Pluggable client-interface optic modules: The MXP_2.5G_10EX_C card has modular interfaces. Two
types of optic modules can be plugged into the card. These modules include an OC-48/STM-16 SR-1
interface with a 7-km (4.3-mile) nominal range (for short range and intra-office applications) and an
IR-1 interface with a range of up to 40 km (24.9 miles). SR-1 is defined in Telcordia GR-253-CORE
and in I-16 (ITU-T G.957). IR-1 is defined in Telcordia GR-253-CORE and in S-16-1 (ITU-T G.957).
High-level provisioning support: The card is initially provisioned using Cisco TransportPlanner
Link monitoring and management: The card uses standard OC-48 OH (overhead) bytes to monitor and
manage incoming interfaces. The card passes the incoming SDH/SONET data stream and its overhead
bytes transparently.
225
section overhead, which eliminates forwarding of unneeded layer overhead. It can help reduce the
number of alarms and help isolate faults in the network.
Automatic timing source synchronization: The MXP_2.5G_10EX_C card normally synchronizes from
the control card. If for some reason, such as maintenance or upgrade activity, the control card is not
available, the card automatically synchronize to one of the input client-interface clocks.
Configurable squelching policy: The card can be configured to squelch the client interface output if
LOS occurs at the DWDM receiver or if a remote fault occurs. In the event of a remote fault, the card
manages MS-AIS insertion.
The card is tunable across the full C-band, thus eliminating the need to use different versions of each
card to provide tunability across specific wavelengths in a band.


Figure 17: MXP_2.5G_10EX_C Faceplate and Block Diagram
226
MXP_2.5G_10EX_C Functions
For information about safety labels for the card, see the "Class 1 Laser Product Cards” section.
MXP_2.5G_10EX_C Functions
The following functions of the MXP_2.5G_10EX_C card are explained in the "Card Features" chapter:
Client Interface
DWDM Interface
FEC
Jitter
Lamp Test
grid effectively. The MXP_2.5G_10EX_C card implements the MLSE-based UT module. The
MXP_2.5G_10EX_C card uses a C-band version of the UT2.
The MXP_2.5G_10EX_C card is tunable over 82 wavelengths in the C-band at 50-GHz spacing on the
ITU grid.
Table 97: MXP_2.5G_10EX_C Trunk Wavelengths
1 196.00 1529.55 42 193.95 1545.72
2 195.95 1529.94 43 193.90 1546.119
3 195.90 1530.334 44 193.85 1546.518
4 195.85 1530.725 45 193.80 1546.917
5 195.80 1531.116 46 193.75 1547.316
6 195.75 1531.507 47 193.70 1547.715
7 195.70 1531.898 48 193.65 1548.115
227
8 195.65 1532.290 49 193.60 1548.515
9 195.60 1532.681 50 193.55 1548.915
10 195.55 1533.073 51 193.50 1549.32
11 195.50 1533.47 52 193.45 1549.71
12 195.45 1533.86 53 193.40 1550.116
13 195.40 1534.250 54 193.35 1550.517
14 195.35 1534.643 55 193.30 1550.918
15 195.30 1535.036 56 193.25 1551.319
16 195.25 1535.429 57 193.20 1551.721
17 195.20 1535.822 58 193.15 1552.122
18 195.15 1536.216 59 193.10 1552.524
19 195.10 1536.609 60 193.05 1552.926
20 195.05 1537.003 61 193.00 1553.33
21 195.00 1537.40 62 192.95 1553.73
22 194.95 1537.79 63 192.90 1554.134
23 194.90 1538.186 64 192.85 1554.537
24 194.85 1538.581 65 192.80 1554.940
25 194.80 1538.976 66 192.75 1555.343
26 194.75 1539.371 67 192.70 1555.747
27 194.70 1539.766 68 192.65 1556.151
28 194.65 1540.162 69 192.60 1556.555
29 194.60 1540.557 70 192.55 1556.959
30 194.55 1540.953 71 192.50 1557.36
31 194.50 1541.35 72 192.45 1557.77
32 194.45 1541.75 73 192.40 1558.173
33 194.40 1542.142 74 192.35 1558.578
34 194.35 1542.539 75 192.30 1558.983
35 194.30 1542.936 76 192.25 1559.389
228
Related Procedures for MXP_2.5G_10EX_C Card
36 194.25 1543.333 77 192.20 1559.794
37 194.20 1543.730 78 192.15 1560.200
38 194.15 1544.128 79 192.10 1560.606
39 194.10 1544.526 80 192.05 1561.013
40 194.05 1544.924 81 192.00 1561.42
41 194.00 1545.32 82 191.95 1561.83
Related Procedures for MXP_2.5G_10EX_C Card

The following is the list of procedures and tasks related to the configuration of the MXP_2.5G_10EX_C card:
NTP-G97 Modifying the 4x2.5G Muxponder Card Line Settings and PM Parameter Thresholds, on
page 446
MXP_MR_10DMEX_C Card
The MXP_MR_10DMEX_C card aggregates a mix of client SAN service-client inputs (GE, FICON, and
Fibre Channel) into one 10-Gbps STM-64/OC-192 DWDM signal on the trunk side. It provides one long-
reach STM-64/OC-192 port per card and is compliant with Telcordia GR-253-CORE and ITU-T G.957.
The card supports aggregation of the following signal types:
1-Gigabit Ethernet
1-Gigabit ISC-Compatible (ISC-1)
2-Gigabit ISC-Peer (ISC-3)
Caution The card can be damaged by dropping it. Handle it carefully.
The MXP_MR_10DMEX_C muxponder passes all SONET/SDH overhead bytes transparently.

The digital wrapper function (ITU-T G.709 compliant) formats the DWDM wavelength so that it can be used to
set up GCCs for data communications, enable FEC, or facilitate PM. The MXP_MR_10DMEX_C card works
with the OTN devices defined in ITU-T G.709. The card supports ODU1 to OTU2 multiplexing, an
229
MXP_MR_10DMEX_C Card
industry standard method for asynchronously mapping a SONET/SDH payload into a digitally
wrapped envelope. See the "Multiplexing Function” section.
Note You cannot disable ITU-T G.709 on the trunk side. If ITU-T G.709 is enabled, then FEC cannot be disabled.
Note Because the client payload cannot oversubscribe the trunk, a mix of client signals can be accepted, up to a
maximum limit of 10 Gbps.
You can install the MXP_MR_10DMEX_C card in Slots 1 to 6 and 12 to 17 in ONS 15454 DWDM
chassis, Slots 2 and 3 in ONS 15454 M2 chassis, Slots 2 to 7 in ONS 15454 M6.
Note The MXP_MR_10DMEX_C card is not compatible with the MXP_2.5G_10G card, which does not support
transparent termination mode.
The MXP_MR_10DMEX_C card features a tunable 1550-nm C-band laser on the trunk port. The laser is tunable
across 82 wavelengths on the ITU grid with 50-GHz spacing between wavelengths. Each card features four
1310-nm lasers on the client ports and contains five transmit and receive connector pairs (labeled) on the card
faceplate. The card uses dual LC connectors on the trunk side and SFP modules on the client side for optical
cable termination. The SFP pluggable modules are SR or IR and support an LC fiber connector.
The current version of the GFP-T G.7041 supports transparent mapping of 8B/10B block-coded
protocols, including Gigabit Ethernet, Fibre Channel, ISC, and FICON.
In addition to the GFP mapping, 1-Gbps traffic on Port 1 or 2 of the high-speed SERDES is mapped to an
STS-24c channel. If two 1-Gbps client signals are present at Port 1 and Port 2 of the high-speed
SERDES, the Port 1 signal is mapped into the first STS-24c channel and the Port 2 signal into the second
STS-24c channel. The two channels are then mapped into an OC-48 trunk channel.
Table 98: MXP_MR_10DMEX_C Client Interface Data Rates and Encapsulation
Client Interface Input Data Rate GFP-T G.7041 Encapsulation
1G FC 1.06 Gbps Yes


Gigabit Ethernet 1.25 Gbps Yes
The MXP_MR_10DMEX_C card includes two FPGAs, and a group of four ports is mapped to each FPGA.
Group 1 consists of Ports 1 through 4, and Group 2 consists of Ports 5 through 8. The following table shows
230
Key Features
some of the mix and match possibilities on the various client data rates for Ports 1 through 4, and Ports
5 through 8. An X indicates that the data rate is supported in that port.
Table 99: Supported Client Data Rates for Ports 1 through 4 and Ports 5 through 8
Port (Group 1) Port (Group 2) Gigabit Ethernet 1G FC 2G FC 4G FC
1 5 X X X X
2 6 X X — —
3 7 X X X —
4 8 X X — —
GFP-T PM is available through RMON and trunk PM is managed according to Telcordia GR-253-CORE
and ITU G.783/826. Client PM is achieved through RMON for FC and GE.
A buffer-to-buffer credit management scheme provides FC flow control. With this feature enabled, a port
indicates the number of frames that can be sent to it (its buffer credit), before the sender is required to stop
transmitting and wait for the receipt of a “ready” indication. The MXP_MR_10DMEX_C card supports FC
credit-based flow control with a buffer-to-buffer credit extension of up to 1600 km (994.1 miles) for 1G
FC, up to 800 km (497.1 miles) for 2G FC, or up to 400 km (248.5 miles) for 4G FC. The feature can be
enabled or disabled.
The MXP_MR_10DMEX_C card features a 1550-nm laser for the trunk/line port and a 1310-nm or 850-nm laser
(depending on the SFP) for the client ports. The card contains eight 12.5-degree downward-tilt SFP modules for
the client interfaces. For optical termination, each SFP uses two LC connectors, which are labeled TX and RX on
the faceplate. The trunk port is a dual-LC connector with a 45-degree downward angle.
Key Features
The MXP_MR_10DMEX_C card has the following high-level features:
Onboard E-FEC processor: The processor supports both standard RS (specified in ITU-T G.709) and E-
FEC, which allows an improved gain on trunk interfaces with a resultant extension of the transmission
range on these interfaces. The E-FEC functionality increases the correction capability of the
transponder to improve performance, allowing operation at a lower OSNR compared to the standard
RS (255,239) correction algorithm.
Pluggable client-interface optic modules: The MXP_MR_10DMEX_C card has modular interfaces. Two
types of optics modules can be plugged into the card. These modules include an OC-48/STM-16 SR-1
interface with a 7-km (4.3-mile) nominal range (for short range and intra-office applications) and an IR-1
interface with a range of up to 40 km (24.9 miles). SR-1 is defined in Telcordia GR-253-CORE and in I-16
(ITU-T G.957). IR-1 is defined in Telcordia GR-253-CORE and in S-16-1 (ITU-T G.957).
Y-cable protection: The card supports Y-cable protection between the same card type only, on ports
with the same port number and signal rate. See the "Y-Cable Protection Availability on TXP, MXP,
and Xponder Cards" section for more detailed information.
High-level provisioning support: The card is initially provisioned using Cisco TransportPlanner
ALS: This safety mechanism is used in the event of a fiber cut. For details regarding ALS provisioning for
the MXP_MR_10DMEX_C card, see the NTP-G162 Changing the ALS Maintenance Settings section.
231
Key Features
Link monitoring and management: The card uses standard OC-48 OH (overhead) bytes to monitor and
manage incoming interfaces. The card passes the incoming SDH/SONET data stream and its OH
(overhead) bytes transparently.
section overhead, which eliminates forwarding of unneeded layer overhead. It can help reduce the
number of alarms and help isolate faults in the network.
Automatic timing source synchronization: The MXP_MR_10DMEX_C card normally synchronizes
from the control card. If for some reason, such as maintenance or upgrade activity, the control card
is not available, the card automatically synchronizes to one of the input client-interface clocks.
Note MXP_MR_10DMEX_C card cannot be used for line timing.
Configurable squelching policy: The card can be configured to squelch the client-interface output if
LOS occurs at the DWDM receiver or if a remote fault occurs. In the event of a remote fault, the card
manages MS-AIS insertion.
The card is tunable across the full C-band, thus eliminating the need to use different versions of each
card to provide tunability across specific wavelengths in a band.
You can provision a string (port name) for each fiber channel/FICON interface on the
MXP_MR_10DMEX_C card, which allows the MDS Fabric Manager to create a link association
between that SAN port and a SAN port on a Cisco MDS 9000 switch.

232

Figure 18: MXP_MR_10DMEX_C Faceplate and Block Diagram
For information about safety labels for the card, see the "Class 1M Laser Product Cards” section.
Caution You must use a 20-dB fiber attenuator (15 to 25 dB) when working with the card in a loopback on the
trunk port. Do not use direct fiber loopbacks with the card, because they can cause irreparable damage to
the MXP_MR_10DMEX_C card.
MXP_MR_10DMEX_C Functions
The following functions of the MXP_MR_10DMEX_C card are explained in the "Card Features" chapter:
• Card level indicators
233
• Port level indicators
grid effectively. The MXP_MR_10DMEX_C card uses a C-band version of the MLSE-based UT module.
The MXP_MR_10DMEX_C card is tunable over 82 wavelengths in the C-band at 50-GHz spacing on
the ITU grid.
Table 100: MXP_MR_10DMEX_C Trunk Wavelengths
1 196.00 1529.55 42 193.95 1545.72
2 195.95 1529.94 43 193.90 1546.119
3 195.90 1530.334 44 193.85 1546.518
4 195.85 1530.725 45 193.80 1546.917
5 195.80 1531.116 46 193.75 1547.316
6 195.75 1531.507 47 193.70 1547.715
7 195.70 1531.898 48 193.65 1548.115
8 195.65 1532.290 49 193.60 1548.515
9 195.60 1532.681 50 193.55 1548.915
10 195.55 1533.073 51 193.50 1549.32
11 195.50 1533.47 52 193.45 1549.71
12 195.45 1533.86 53 193.40 1550.116
13 195.40 1534.250 54 193.35 1550.517
14 195.35 1534.643 55 193.30 1550.918
15 195.30 1535.036 56 193.25 1551.319
16 195.25 1535.429 57 193.20 1551.721
17 195.20 1535.822 58 193.15 1552.122
18 195.15 1536.216 59 193.10 1552.524
19 195.10 1536.609 60 193.05 1552.926
20 195.05 1537.003 61 193.00 1553.33
21 195.00 1537.40 62 192.95 1553.73
234
Related Procedures for MXP_MR_10DMEX_C Card
22 194.95 1537.79 63 192.90 1554.134
23 194.90 1538.186 64 192.85 1554.537
24 194.85 1538.581 65 192.80 1554.940
25 194.80 1538.976 66 192.75 1555.343
26 194.75 1539.371 67 192.70 1555.747
27 194.70 1539.766 68 192.65 1556.151
28 194.65 1540.162 69 192.60 1556.555
29 194.60 1540.557 70 192.55 1556.959
30 194.55 1540.953 71 192.50 1557.36
31 194.50 1541.35 72 192.45 1557.77
32 194.45 1541.75 73 192.40 1558.173
33 194.40 1542.142 74 192.35 1558.578
34 194.35 1542.539 75 192.30 1558.983
35 194.30 1542.936 76 192.25 1559.389
36 194.25 1543.333 77 192.20 1559.794
37 194.20 1543.730 78 192.15 1560.200
38 194.15 1544.128 79 192.10 1560.606
39 194.10 1544.526 80 192.05 1561.013
40 194.05 1544.924 81 192.00 1561.42
41 194.00 1545.32 82 191.95 1561.83
Related Procedures for MXP_MR_10DMEX_C Card

The following is the list of procedures and tasks related to the configuration of the
MXP_MR_10DMEX_C card:
page 497
235
AR_MXP, AR_XP, and AR_XPE Cards
AR_MXP, AR_XP, and AR_XPE Cards

The AR_MXP (Any-Rate Muxponder), AR_XP (Any-Rate Xponder), and AR_XPE (Any-Rate Enhanced
Xponder) cards are supported on ONS 15454 DWDM platform. The AR_MXP card supports a trunk
bandwidth of up to 10 Gbps. The AR_XP and AR_XPE cards support a trunk bandwidth of up to 20 Gbps.
The AR_MXP, AR_XP, and AR_XPE cards aggregate a mix of client SAN services (FC or FICON
1G/2G/4G/8G, ESCON and ISC3-STP 1G/2G), Ethernet (FE, GE, 10GE LAN), OCn (OC3/STM-1,
OC12/STM-4, and OC48/STM-16), OTU (OTU1, OTU2e/1e), and Video (SD-SDI, HD-SDI, and 3G-SDI)
into one 10 Gbps signal on the trunk side.
Note When all the cards in the chassis are simultaneously reset by the user, the AR_XP card undergoes a hard
reset instead of a soft reset. This causes traffic loss for traffic going through these cards.
Table 101: AR_MXP, AR_XP, and AR_XPE Client Interface Data Rates and Encapsulation
Client Interface Input Data Rate GFP Encapsulation
OC3/ STM1 155.52 Mbps —
OC12/STM4 622.08 Mbps —
OC48/STM16 2.488 Gbps —
FE 100 Mbps GFP-F
GE 1.125 Gbps GFP-F GFP-T (as per G.709

mentioned in 17.7.1.1
1000BASE-X transcoding) for
AR_XPE card
10GE LAN 10.31 Gbps —
1GFC 1.06 Gbps GFP-T
8GFC 8.5 Gbps GFP-T for AR_MXP and AR_XP

cards GMP for AR_XPE card
OTU1 2.66 Gbps —
OTU2 10.7 Gbps —
ESCON 200 Mbps GFP-T
1G ISC3-STP 1.06 Gbps GFP-T
2G ISC3-STP 2.125 Gbps GFP-T
236
Key Features
Client Interface Input Data Rate GFP Encapsulation
HD-SDI 1.485 Gbps GFP-F
SD-SDI 270 Mbps GFP-F
3G-SDI 2.970 Gbps GFP-F
Key Features
The AR_MXP, AR_XP, and AR_XPE cards support the following key features:
Multiple Operating Modes—The AR_MXP, AR_XP, or AR_XPE card can be configured into multiple
operating modes. The cards are equipped with pluggables for client and trunk options, and offer a
large variety of configurations. For more information about multiple operating modes, see 11.0.3
Multiple Operating Modes, page 11-105.
Operating Mode to Client Payload Mapping—Each operating mode supports a specific set of client
payloads.
Table 102: AR_MXP, AR_XP, and AR_XPE Card Supported Client-Payload Mapping—SONET/SDH, Ethernet, OTU1, and FC
Card Rate SONET/SDH Ethernet OTU FC

Mode
OC3S/TM1 OC12S/TM4 OC48S/TM16 FE GE 10 GE OTU1 OTU2e FCION1GFC/1G FCION2GFC/2G FCION4GFC/4G FCION8GFC/8G ESCON
TXP_MR LOW Yes Yes Yes Yes Yes N/A No No Yes Yes Yes No Yes
HIGH No No No No No Yes No Yes No No No Yes No
TXP_MR LOW Yes Yes Yes Yes Yes N/A No No Yes Yes Yes No Yes
HIGH N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A
MXPDME HIGH No No No No Yes N/A No No Yes Yes Yes No No
MXPDME HIGH No No No No Yes N/A No No Yes Yes Yes No No
MXPMR LOW Yes Yes No Yes Yes N/A No No Yes No No No Yes
HIGH Yes Yes Yes Yes Yes N/A Yes No Yes Yes Yes No Yes
MXPMR LOW Yes Yes No Yes Yes N/A No No Yes No No No Yes
HIGH Yes Yes Yes Yes Yes N/A Yes No Yes Yes Yes No Yes
MXP4x2-510G-. HIGH No No Yes No No N/A Yes No No No No No No
MXP4x2-510G-. HIGH No No Yes No No N/A Yes No No No No No No
MXPV-D10G- HIGH No No No No No N/A No No No No No No No
237
Key Features
Card Rate SONET/SDH Ethernet OTU FC

Mode
OC3S/TM1 OC12S/TM4 OC48S/TM16 FE GE 10 GE OTU1 OTU2e FCION1GFC/1G FCION2GFC/2G FCION4GFC/4G FCION8GFC/8G ESCON
RGN HIGH No No No No No N/A No Yes No No No No No
LOW No No No No No N/A Yes No No No No No No
Table 103: AR_MXP, AR_XP, and AR_XPE Card Supported Client-Payload Mapping—ISC and Video
ISC Video
Card Mode Rate ISC-1 ISC3_STP_1G ISC3_STP_2G SD-SDI HD-SDI 3G-SDI
TXP_MR LOW No Yes Yes No No No
HIGH No No No No No No
TXPP_MR LOW No No N/A No No No
HIGH N/A N/A N/A N/A N/A N/A
MXP_DME HIGH No No No No No No
MXPP_DME HIGH No No No No No No
MXP_MR LOW No No No No No No
HIGH No No No Yes Yes No
MXPP_MR LOW No No No No No No
HIGH No No No Yes Yes No
MXP-4x2.5-10G HIGH No No No No No No
MXPP-4x2.5-10G HIGH No No No No No No
MXP-VD-10G HIGH No No No No No Yes
RGN HIGH No No No No No No
LOW No No No No No No
Auto Sensing—The AR_MXP, AR_XP, and AR_XPE cards support auto sensing of client payloads.
The line card analyzes the received client signal and configures the payload on the client port
automatically without user intervention.
Auto sensing feature is supported on the Gigabit Ethernet, OC-3/STM-1, OC-12/STM-4, and
OC-48/STM-16 payloads. Following operating card modes support the autosensing feature:
TXP (low rate)
TXPP (low rate)
MXP_MR (low and high Rate)
238
Key Features
MXPP_MR (low and high rate)

CTC supports the configuration of all the provisioning parameters supported by the
autosensed payload. However, creation and deletion of the
circuits are the only configurations supported on the “AUTO” payload.
Video Multiplexing—The AR_XP and AR_XPE cards support the capability to multiplex SD-SDI,
HD-SDI, and 3G-SDI signals over the OTU2 trunk interface allowing to maximize the wavelength
bandwidth, maintain full transparency for uncompressed signals, and reduce latency. The video
multiplexing of 3G-SDI signal is not supported on the AR_MXP card.
Regenerator Mode—This mode regenerates the OTU2e or OTU1 signals with ODU transparent or
CISCO Extended Use options. For OTU2e, FEC can be Disabled, Standard G.975, EFEC I.4 or
EFEC I.7, and for OTU1, FEC can be Standard G.975 or Disabled.
High Speed GCCs—The AR_MXP, AR_XP, and AR_XPE cards support the provisioning of GCC
channel on OTN (OTU1/OTU2) enabled client and trunk ports. A maximum of five GCC channels on
the Cisco ONS 15454 shelften GCC channels on Cisco ONS 15454 M2 or Cisco ONS 15454 M6 shelf
can be created. The high speed GCC enables you to create the GCC when both the NE and FE line
cards are in Cisco ONS 15454 M2 or Cisco ONS 15454 M6 shelf. The legacy GCC on Cisco ONS
15454 shelf can be selected on one side and the Cisco ONS 15454, Cisco ONS 15454 M2 or Cisco
ONS 15454 M6 shelf on the other side.
Y-cable protection—Y-cable protection between the same card type is supported only on ports with the
same port number and signal rate. Switching time is high between two AR_XPE cards when auto
negotiation is enabled. Hence, if Y-cable protection is configured on AR_XPE cards, auto-negotiation
must be disabled on the client ports so that the switching time is less than 50 ms. For more detailed
information, see "Y-Cable Protection Availability on TXP, MXP, and Xponder Cards" section.
Splitter protection—For splitter protection, OCHCC circuits with different trunk wavelengths for the
working and protect paths can be configured. The process of setting the trunk wavelengths is similar to
the “DLP-G367 Change the 2.5G Multirate Transponder Trunk Wavelength Settings” task on page 11-
175. OCHCC circuits having different trunk wavelengths on the working and protect paths can be
upgraded to GMPLS circuits.
SyncE Support—Customers using a packet network find it difficult to provide timing to multiple remote
network elements (NEs) through an external time division multiplexed (TDM) circuit. The SyncE
feature helps to overcome this problem by providing effective timing to the remote NEs through a
packet network. SyncE leverages the physical layer of the Ethernet to transmit frequency to the remote
sites. SyncE's functionality and accuracy resemble the SONET/SDH network because of its physical
layer characteristic. The SyncE feature provides the required synchronization at the physical level.
Operation messages maintain SyncE links and ensure that a node always derives timing from the most
reliable source. SyncE uses the Ethernet Synchronization Message Channel (ESMC) to enable
traceability of the best clock source to correctly define the timing source and prevent a timing loop.
SyncE is not supported on the AR_XPE card.
Licensing—The AR_MXP and AR_XP cards offer you an unprecedented flexibility. The cards support
a wide range of different applications and configurations. To help you take advantage of such
flexibility to lower capital expenditures (CapEx) on your network, Cisco provides a licensing model
for AR_MXP and AR_XP cards. Licensing is not supported on the AR_XPE card. For more
information on licensing, see the Licensing Configuration Guide.
GFP-T Mapping— The GFP-T framing mode can be provisioned on the AR_XP and AR_MXP cards in the
CTC card view > Provisioning > Line tab. The AR_XP and AR_MXP cards must be configured
239
Key Features
in the high-rate MXP_DME mode. When GFP-T framing mode is provisioned, autonegotiation is
enabled but does not impact traffic.
When the software version of the node is changed from Release 10.6.2 to releases prior to 10.6.1, the AR_XP
card undergoes a hard reset. This is applicable for the ONS 15454, 15454 M2 and 15454 M6 chassis.
The AR_MXP, AR_XP, and AR_XPE cards can be installed in any service slots in the chassis. The
AR_MXP, AR_XP, and AR_XPE cards do not interoperate with all the existing TXP or MXP cards. The
AR_MXP card allows you to configure only one high rate XFP port. This can be a muxponder mode where
N [N= 1 to 8] client ports goes out via 1 trunk XFP port or in a transponder mode where client and trunk
are XFP ports. There is no limitation in the AR_XP and AR_XPE cards, where you can use both high rate
trunk ports simultaneously.
The AR_XPE card does not interoperate with AR_MXP and AR_XP cards.
The GE client interfaces on the AR-XPE card interoperate with NCS 4000 platform, when ODU2 is
multiplexed on a 100G trunk interface, with both 100GS-CK-LC and 200G-CK-LC cards, in MXP-
10X10G operating mode. The GE client mapping on AR-XPE cards must be performed directly on ODU0,
and then on ODU2 not passing through the ODU1 container.
Multiple Operating Modes
A single AR_MXP, AR_XP, or AR_XPE card can be configured into multiple operating modes. Criteria for
selecting a particular operational mode are defined by the network level design. CTP helps you to choose the
appropriate operational mode. Each operating mode is divided into two categories based on the trunk rate:
Low rate (trunk rate < 5G)
High rate (trunk rate > 5G)
The AR_XP or AR_XPE card allows you to configure two high rate operational modes, where as you
can configure only one high rate operational mode on the AR_MXP card.
When you configure the AR_MXP, AR_XP, or AR_XPE card in to multiple operational modes, make
sure that the following tasks are completed:
In order to make the ports operational and to correctly report alarms, OCHCC circuit must be created
for the following operating modes::
Low-rate MXP_MR
High-rate MXP_MR
Low-rate MXPP_MR
High-rate MXPP_MR
Same operational mode is configured at both ends and ensure the port numbers are same on both ends.
The OCHCC circuit should be created between the same client port numbers at the near and far end.
Ensure ODU1 and timeslots are matching at both ends.
For AR_XPE card that is configured with 1GE or 1GFC payload, ensure that ODU0 and ODU1 are
matching at both ends.
For auto sensing payloads created on auto ports, you should check the Auto Sensing checkbox in the
provisioning pane.
240
Key Features
GMPLS circuits can be created on AR_MXP, AR_XP, and AR_XPE cards.

PPMs must be provisioned on all ports before configuring the operational mode.
The following conditions determine the maximum bandwidth at the client side when a 4GFC payload is
configured in the TXP_MR or TXPP_MR mode:
The maximum client bandwidth should not exceed 28G when TXP_MR or TXPP_MR operating mode
is configured on the AR_MXP, AR_XP, or AR_XPE card and other operating modes, like low-rate or
high-rate TXP_MR,TXPP_MR, MXP_DME, MXPP_DME, MXP_MR, MXPP_MR, MXP-4X2.5G-
10G, MXPP-4X2.5G-10G, and MXP-VDC-10G, are configured on the same card.
The maximum client bandwidth should not exceed 20G when a TXP_MR or TXPP_MR operating
mode is configured on the AR_MXP, AR_XP, or AR_XPE card and if more than two or more
combinations of Low-rate or high-rate TXP_MR,TXPP_MR, MXP_DME, MXPP_DME,
MXP_MR, MXPP_MR, MXP-4X2.5G-10G, MXPP-4X2.5G-10G, and MXP-VDC-10G,
operating modes are configured on the same card.
The utilized client bandwidth is 8G when the TXP_MR operating mode is configured with a 4GFC
as payload.
The utilized client bandwidth is 12G when the TXPP_MR operating mode is configured with a
4GFC as payload.
There is no restriction on the bandwidth if only TXP_MR or TXPP_MR operating mode with
4GFC payload is configured on the card. For example, four instances of TXP_MR mode with
4GFC payload on one AR_MPX, AR_XP, or AR_XPE card.
The low-rate or high-rate RGN operating mode does not add to the client side bandwidth. For
example, four instances of TXP_MR mode with 4GFC and one instance of high-rate RGN
mode on same card.
For all the other payloads and operating modes, the client bandwidth utilized is the client
payload data rate.
If you revert to a release earlier than Release 9.80, ensure that you delete the following card modes:
Low-rate TXPP_MR if the client payload is 4GFC.
High-rate TXP_MR if the client payload is 10 GE.
The AR_MXP, AR_XP, and AR_XPE cards support the following operating modes:
TXP_MR (Unprotected Transponder)
TXPP_MR (Protected Transponder)
MXP_DME (Unprotected Data Muxponder)
MXPP_DME (Protected Data Muxponder)
MXP_MR (Unprotected Multirate Muxponder)
MXPP_MR (Protected Multirate Muxponder)
MXP-4x2.5-10G (OC48/OTU1 Unprotected Muxponder)
MXPP-4x2.5-10G (OC48/OTU1 Protected Muxponder)
241
RGN (OTU1/OTU2 Regenerator)

MXP-VD-10G (Video Muxponder)

The AR_MXP, AR_XP, or AR_XPE card can be configured as a low-rate or a high-rate TXP_MR card mode.
Note OTN cannot be enabled for 4GFC trunk ports.
Low Rate—A maximum of four TXP_MR configurations can be provisioned on a single AR_MXP,
AR_XP, or AR_XPE card. The AR_MXP, AR_XP, or AR_XPE card can be configured as a low-
rate TXP_MR card by adhering to the following provisioning rules:
Two SFP ports must be grouped. The allowed port pairs are 1-2, 3-4, 5-6, 7-8, 1-5, 2-6, 3-7, and/or 4-
8.
Ports 2, 4, 5, 6, 7, or 8 can be configured as trunk ports.
Ports 1, 2, 3, 4, 5 or 7 can be configured as client ports.
Note The trunk port is not created when the low-rate TXP_MR card operating mode
is configured. It is created after the client payload is created.
Figure 19: Low-Rate TXP_MR Card Operating Mode Configuration
High Rate—Only one TXP_MR configuration can be provisioned on a single AR_MXP, AR_XP, or
AR_XPE card. The AR_MXP, AR_XP, or AR_XPE card can be configured as a high-rate
TXP_MR card by adhering to the following provisioning rules:
242
XFP ports 9 and 10 must be grouped.

Port 10 must be configured as a trunk port.
Port 9 must be configured as a client port.
Figure 20: High-Rate TXP_MR Card Operating Mode Configuration

The AR_MXP, AR_XP, or AR_XPE card can be configured as a low-rate TXPP_MR card mode. A
maximum of two TXPP_MR configurations can be provisioned on a single AR_MXP, AR_XP, or
AR_XPE card. The AR_MXP, AR_XP, or AR_XPE card can be configured as a low-rate TXPP_MR card
by adhering to the following provisioning rules:
Three SFP ports must be grouped. The allowed port pairs are 1-5-6 or 2-7-8, or both.
Ports 5 and 6, and 7 and 8 must be configured as trunk ports, where 6 and 8 are the protect trunk ports for 5
and 6 respectively.
Ports 1 and 2 must be configured as client ports.
Splitter protection is automatically created between ports 5-6 and 7-8.
243
Figure 21: Low-Rate TXPP_MR Card Operating Mode Configuration

The AR_XP or AR_XPE card can be configured as a high-rate 4:1 or 8:1 MXP_DME card mode. The
AR_MXP card can be configured as a high rate 8:1 MXP_DME card mode.
4:1 MXP_DME mode—A maximum of two MXP_DME configurations can be provisioned on a single
AR_XP or AR_XPE card. The AR_XP or AR_XPE card can be configured as a high-rate 4:1
MXP_DME card by adhering to the following provisioning rules:
Four SFP ports and one XFP port must be grouped. The allowed port pairs are 1-2-3-4-9 or 5-6-7-8-
10, or both.
Port 9 or 10 must be configured as a trunk port.
Ports 1, 2, 3, and 4, or 5, 6, 7, and 8 must be configured as client ports.
8:1 MXP_DME mode—Only one MXP_DME configuration can be provisioned on a single AR_MXP,
AR_XP, or AR_XPE card. The AR_MXP, AR_XP, AR_XPE card can be configured as a high-rate
8:1 MXP_DME card by adhering to the following provisioning rules:
Eight SFP ports and one XFP port must be grouped. The allowed port pairs are 1-2-3-4-5-6-7-8-9.
Port 9 must be configured as a trunk port.
Ports 1 to 8 must be configured as client ports.
244
Figure 22: High-Rate MXP_DME Card Operating Mode Configuration

The AR_XP or AR_XPE card can be configured as a high-rate 4:2 or 8:2 MXPP_DME card mode.
4:2 MXP_DME mode—Only one MXPP_DME configuration can be provisioned on a single AR_XP or
AR_XPE card. The AR_XP or AR_XPE card can be configured as a high-rate 4:2 MXPP_DME card
by adhering to the following provisioning rules:
Four SFP ports and two XFP ports must be grouped. The allowed port pairs are 1-2-3-4-9-10 or 5-
6-7-8-9-10.
Ports 9 and 10 must be configured as trunk ports.
Ports 1, 2, 3, and 4, or 5, 6, 7, and 8 must be configured as client ports.
Splitter protection is automatically created between ports 9 and 10. Port 10 will be the protected trunk port
for port 9.
8:2 MXPP_DME mode—Only one MXPP_DME configuration can be provisioned on a single AR_XP
or AR_XPE card. The AR_XP or AR_XPE card can be configured as a high-rate 8:2 MXPP_DME
card by adhering to the following provisioning rules:
Eight SFP ports and two XFP ports must be grouped. The allowed port pairs are 1-2-3-4-5-6-7-8-9-10.
Ports 9 and 10 must be configured as trunk ports.

Ports 1 to 8 must be configured as client ports.
for port 9.
245
Figure 23: High-Rate MXPP_DME Card Operating Mode Configuration

The AR_MXP, AR_XP, or AR_XPE card can be configured as a low-rate or a high-rate MXP_MR card mode.
Low Rate—A maximum of two MXP_MR configurations can be provisioned depending on the
availability of client ports. The AR_MXP, AR_XP, or AR_XPE card can be configured as a low-rate
MXP_MR card by adhering to the following provisioning rules:
N:1 muxponder must be created, where N varies from client ports 2 to 7.
Only ports 5, 6, 7, or 8 can be configured as trunk ports.
Ports 1 to 8 can be configured as client ports, if they are not configured as trunk ports.
Any client port can be added or deleted, if the trunk bandwidth supports the new payload without impacting the
traffic on the existing services. Minimum of two client ports should be part of the operational mode group.
On the AR_XPE card, 1GE or 1G FC payload cannot be configured with other payloads. When a 1GE or
1GFC payload is configured on a port of MXP_MR (low rate) mode, then only 1GE or 1GFC payload
can be configured on the other ports.
246
Figure 24: Low-Rate MXP_MR Card Operating Mode Configuration
High Rate—A maximum of two MXP_MR configurations can be provisioned on a AR_XP or AR_XPE
card and only one such configuration can be provisioned on an AR_MXP card. The AR_MXP,
AR_XP, or AR_XPE card can be configured as a high-rate MXP_MR card by adhering to the
following provisioning rules:
Only ports 9 and 10 can be configured as trunk ports.
Ports 1 to 8 can be configured as client ports.
Any client payload can be added or deleted, if the trunk bandwidth supports the new payload without
impacting the traffic on the existing services.
On the AR_XPE card, when you create a OCHCC circuit using 1GE or 1GFC payload, only ODU0
mapping is supported and timeslot mapping is not supported. When a OCHCC circuit is created on a
particular ODU1 timeslot with payloads using timeslot mapping, OCHCC circuits cannot be created on
payloads using ODU0 mapping, but can be created on the other ODU1 timeslot. In MXP_MR (high-rate)
mode, while creating a OCHCC circuits on the GE or 1GFC client payload, you can select the ODU1 and
ODU0 timeslots instead of ODU1 and timeslot selection.
247
Figure 25: High-Rate MXP_MR Card Operating Mode Configuration

The AR_MXP, AR_XP, or AR_XPE card can be configured as a low-rate or a high-rate MXPP_MR
card mode.
Low Rate—A maximum of two MXPP_MR configurations can be provisioned depending on the
availability of client ports. Any client payload can be added or deleted, if the trunk bandwidth supports
the new payload without impacting the traffic on the existing services.
The AR_MXP, AR_XP, or AR_XPE card can be configured as a low-rate MXPP_MR card by adhering
to the following provisioning rules:
Only ports 5 and 6 or 7 and 8, or both can be configured as trunk port.
Ports 1 to 8 can be configured as client ports, if ports are not configured as a trunk ports and are not part of
another muxponder.
Splitter protection is automatically created between ports 5 and 6 or 7 and 8.

On the AR_XPE card, 1GE or 1G FC payload cannot be configured with other payloads. When a 1GE or
1GFC payload is configured on a port of MXPP_MR (low rate) mode, then only 1GE or 1GFC payload
can be configured on the other ports.
248
Figure 26: Low-Rate MXPP_MR Card Operating Mode Configuration
High Rate—A maximum of one MXPP_MR configuration can be provisioned on a AR_XP or AR_XPE
card. Any client payload can be added or deleted, if the trunk bandwidth supports the new payload
without impacting the traffic on the existing services.
The AR_XP or AR_XPE card can be configured as a high-rate MXPP_MR card by adhering to the
Ports 1 to 8 can be configured as client ports.
for port 9.
On the AR_XPE card, when you create a OCHCC circuit using 1GE or 1GFC payload, only ODU0
mapping is supported and timeslot mapping is not supported. When a OCHCC circuit is created on a
particular ODU1 timeslot with payloads using timeslot mapping, OCHCC circuits cannot be created on
payloads using ODU0 mapping, but can be created on the other ODU1 timeslot.
When you create a OCHCC circuit between two nodes, with a Provisional Patch Cord (PPC) between the
trunks in splitter protection mode, then, while editing the OCHCC circuit, check the far-end and near-end
details. The near-end and far-end should either be the client and the trunk port respectively or vice-versa.
The client port cannot exist with the trunk port . In some cases, the client and the trunk ports are displayed
together, which is incorrect.
249
Figure 27: High-Rate MXPP_MR Card Operating Mode Configuration

The AR_MXP, AR_XP, or AR_XPE card can be configured as a high-rate MXP-4x2.5-10G card mode.
Only one MXP-4x2.5-10G configuration can be provisioned on an AR_MXP card and a maximum of two
on a AR_XP or AR_XPE card.
The AR_MXP, AR_XP, or AR_XPE card can be provisioned as MXP-4x2.5-10G card by adhering to
the following provisioning rules:
The allowed port pairs are 1-2-3-4-9 or 5-6-7-8-10, or both.
Ports 9 and 10 can be configured as trunk ports.
Ports 1-2-3-4 or 5-6-7-8 can be configured as client ports.
Figure 28: High-Rate MXP-4x2.5-10G Card Operating Mode Configuration
250

The AR_XP or AR_XPE card can be configured as a high-rate MXPP-4x2.5-10G card mode. Only
one MXPP-4x2.5-10G configuration can be provisioned on a AR_XP or AR_XPE card.
The AR_XP or AR_XPE card can be configured as MXPP-4x2.5-10G card by adhering to the
Four SFP ports and two XFP ports must be configured. The allowed port pair is 1-2-3-4-9-10 or 5-
6-7-8-9-10, or both.
Ports 1-2-3-4 or 5-6-7-8 can be configured as client ports.
for port 9.
Figure 29: High-Rate MXPP-4x2.5-10G Card Operating Mode Configuration
MXP_MR_S (Unprotected Multirate Muxponder-Static) and MXPP_MR_S

(Protected Multirate Muxponder-Static)
The MXP_MR_S and MXPP_MR_S operating modes are similar to the existing MXP_MR and
MXPP_MR operating modes except for static timeslot and ODU allocation. A specific set of client
payloads or a mix of client playloads can be used only if the trunk bandwidth and timeslot are available as
per the static allocation mapping.
For example, the MXP_MR_S and MXPP_MR_S modes can be used to provision a dual 4xOC-48 or a
mix of 2-OC-48 + 2-GE or 1-OC-48 + 6-GE into one OTU2 muxponder.
This works similar to traditional transponders/muxponders where operators can choose to use OCH-CC
or just provision OCH-Trail/OCH-NC for creating the circuits.

The AR_MXP, AR_XP, or AR_XPE card can be configured as a low-rate or high-rate RGN card mode.
251
Low Rate—A maximum of four RGN configurations can be provisioned on a single AR_MXP,
AR_XP, or AR_XPE card. The AR_MXP, AR_XP, or AR_XPE card can be configured as a low-rate
RGN card by adhering to the following provisioning rules:
The allowed port pairs are 1-2, 3-4, 5-6, 7-8 or 1-5, 2-6, 3-7, 4-8.
Figure 30: Low-Rate RGN Card Operating Mode Configuration
High Rate—Only one RGN configuration can be provisioned on a AR_MXP, AR_XP, or AR_XPE
card. The AR_MXP, AR_XP, or AR_XPE card can be configured as a high rate RGN card by
adhering to the following provisioning rules:
The allowed port pairs are 9-10.
Figure 31: High-Rate RGN Card Operating Mode Configuration
The 10 GE over OTU2e/OTU1e signal with disabled FEC, standard FEC, I.4 or I.7 EFEC mode can be
regenerated. The ODU transparency can either be Transparent Standard Use or Cisco Extended Use.
252
Note Payload PMs are not supported in this operating mode.

The AR_XP or AR_XPE card can be configured as a high-rate MXP-VD-10G card mode. A maximum
of two MXP-VD-10G configurations can be provisioned on a AR_XP or AR_XPE card.
The AR_XP or AR_XPE card can be configured as MXP-VD-10G card by adhering to the
The allowed port pairs are 1-2-3-9 or 5-6-7-10.
Ports 1-2-3 and 5-6-7 can be configured as client ports.
Figure 32: High-Rate MXP-VD-10G Card Operating Mode Configuration
Scenarios of Different Operational mode Configurations on a AR_XP, or AR_XPE Card

The following section provides a few sample scenarios of different operational modes that can be
configured on an AR_XP or AR_XPE card:
Scenario 1
In this example, the following three operational modes are configured on the AR_XP or AR_XPE card:
Low-rate TXP_MR (Cl=1;Tr=5)
Low-rate MXP_MR (Cl=3,4;Tr=7)
High-rate 3:1 MXP_MR (Cl=2,6,8;Tr=9)
253
Scenario 2
Figure 33: Scenario 1
Scenario 2
In this example, the following four operational modes are configured on the AR_XP or AR_XPE card:
Low-rate TXP_MR (Cl=1;Tr=2)
8G FC TXP (Cl=9;Tr=10)
Low-rate MR_MXP (Cl=4;TR=7,8)
Low-rate MR_MXP (Cl=3,6;TR=5)
254
Scenario 3
Scenario 3
In this example, the following two operational modes are configured on the AR_XP card:
High-rate MXP-4x2.5-10G (Cl=1,2,3,4;Tr=9)
High-rate 4:1 MXP_DME (Cl=5,6,7,8;Tr=10)
Scenario 4
In this example, the following three operational modes are configured on the AR_XP or AR_XPE card:
Low-rate MXP_MR (Cl=1,2,3;Tr=5)
Low-rate MXP_MR (Cl=4,6,8; Tr=7)
RGN(Cl=9;Tr=10)
255
Scenario 5
Scenario 5
In this example, the following two operational modes are configured on the AR_XP or AR_XPE card:
Low-rate MXPP_MR (Cl=1,3,4;Tr=5,6)
High-rate MXPP_MR (Cl=2,7,8;Tr=9,10)
256
AR_MXP, AR_XP, and AR_XPE Functions and Features
AR_MXP, AR_XP, and AR_XPE Functions and Features

The AR_MXP, AR_XP, and AR_XPE cards have the following functions and features are explained in
the "Card Features" chapter:
Client Interface
DWDM Interfac
Enhanced FEC (E-FEC) Feature
Y-Cable Protection
Jitter Consideration
For more information about the AR_MXP and AR_XPE cards, see
For more information about the AR_XPE card, see
http://www.cisco.com/en/US/prod/collateral/optical/ps5724/ps2006/datasheet_c78-726878.html
Related Procedures for AR_MXP, AR_XP, and AR_XPE Cards

The following is the list of procedures and tasks related to the configuration of the AR_MXP, AR_XP, and
AR_XPE cards:
NTP-G321 Provisioning Multiple Operating Modes, on page 672
NTP-G322 Modifying the Card Line Settings and PM Parameter Thresholds, on page 673
100G-LC-C, 100G-ME-C, 100G-CK-C, 100GS-CK-LC,

100ME-CKC, and 200G-CK-LC Cards
The 100G-LC-C, 100G-ME-C, 100G-CK-C, and 100ME-CKC cards are tunable DWDM trunk cards,
which simplifies the integration and transport of 100 Gigabit Ethernet interfaces and services into
enterprises or service provider optical networks. The 100GS-CK-LC and 200G-CK-LC cards simplify the
integration and transport of 100 and 200 Gigabit Ethernet interfaces and services into enterprises or service
provider optical networks. These cards are supported on Cisco ONS 15454 M2, Cisco ONS 15454 M6, and
Cisco NCS 2015 platforms.
The cards interoperate with 10x10G-LC and CFP-LC cards through a chassis backplane.
Note The 100GS-CK-LC and 200G-CK-LC cards do not operate with the CFP-LC card.
The cards provide the following benefits:
257
100G-LC-C, 100G-ME-C, 100G-CK-C, 100GS-CK-LC, 100ME-CKC, and 200G-CK-LC Cards
Provides 100 Gbps wavelengths transport over fully uncompensated networks, with more than 2,500 km
of unregenerated optical links.
Enables 100-Gbps transport over very high Polarization Mode Dispersion (PMD).
Improves overall system density of up to 100 Gbps per slot, which is five times greater than what can
be achieved with 40 Gbps units.
Up to six cards can be installed per ONS 15454 M6 shelf, supporting up to 42 100-Gbps interfaces per 42-
rack units (RU) bay frame. It is possible to place up to two 100G TXPs, one 100 G Regen, or one 100 G
MXP in an ONS 15454 M6 shelf.
Note The fan-tray assembly 15454-M6-FTA2 (for the M6 chassis), 15454-M2-FTA2 (for the M2 chassis) must be
installed in the shelf where the cards are installed. When an ONS-SC+-10G-C pluggable is used along with the
10x10G-LC card, the maximum operating temperature of the shelf must not exceed 50 degrees Celsius.
100G-LC-C, 100G-CK-C, 100ME-CKC, and 100G-ME-C Cards

The 100G-CK-C card works similar to the 100G-LC-C card. The 100G-CK-C card has the new CPAK client
interface replacing the CXP client interface of the 100G-LC-C card. The CPAK client interface enables different
payload combinations such that this card can be used instead of the 100G-LC-C and CFP-LC cards.
The 100G-ME-C and 100ME-CKC cards are metro edge versions of 100G-LC-C and 100G-CK-C respectively.
The metro edge cards have chromatic dispersion of +/-5000 ps/nm and does not support 20% FEC.
The 100G-CK-C and 100ME-CKC cards support the following pluggables:
CPAK-100G-SR10 pluggable with 100GE/OTU4 and 40GE payloads
CPAK-100G-LR4 pluggable with 100GE/OTU4 payloads
CPAK-100G-SR4 pluggable with 100GE payloads
The 100G-LC-C and 100G-ME-C cards support these client signal types:
100GE/OTU4
OTU4 from BP OTL4.10 (interconnect with CFP client)
100GE from BP CAUI (interconnect with CFP client)
3 x OTU3e(255/227) from BP OTL3.4 (interconnect with 10 x10G client)
2 x OTU3 from BP OTL3.4 (interconnect with CFP client)
2 x 40 GE from BP XLAUI (interconnect with CFP client)
In addition to the above, the 100G-CK-C and 100ME-CKC cards support these client signal types:
100GE/OTU4 for the CPAK-100G-SR10/CPAK-100G-LR4 client interface
40GE for the CPAK-100G-SR10 client interface
The 100G-LC-C card and 100G-CK-C cards provide a 100 G DWDM trunk interface that supports up
to 70000 ps/nm of CD robustness.
258
Key Features
The 100G-LC-C card and 100G-CK-C cards enables configuration of the CD dispersion tolerance to
50000 ps/nm and 30000 ps/nm to reduce power consumption.
100GS-CK-LC and 200G-CK-LC Cards

The 100GS-CK-LC and 200G-CK-LC cards are tunable DWDM trunk cards, which simplify the
integration and transport of 100 and 200 Gigabit Ethernet interfaces and services into enterprises or service
provider optical networks. The 200G-CK-LC card is an enhancement of the 100GS-CK-LC card.
The 100GS-CK-LC and 200G-CK-LC cards provide the following benefits:
Allow choosing 16 QAM and QPSK as the modulation formats at the line side.
Provide Standard G-FEC (Reed-Solomon), Soft Decision FEC (SD-FEC) encoding with 20% overhead,
and Hard Decision FEC (HD-FEC) encoding with 7% overhead.
Provide Nyquist filtering for best performance and optimal band usage.
Support gridless tunability.
Allow client access either through the local 100G CPAK interface or through backplane lines.
In MXP-10X10G operating mode, allow 10GE and OC-192 clients (multiplexed on 100G trunk) to
interoperate with NCS 4000 platform. The NCS 2000 line cards must fill the PT and MSI bytes to
interoperate with the supported NCS 4000 10G client. The interoperability applies for Hard
Decision FEC (HD-FEC) encoding with 7% overhead and GFEC trunk modes.
The 200G-CK-LC card also supports feature-based licensing. The 200G-CK-LIC is the licensed card
version of the 200G-CK-LC card. The licensed card version has only some basic functionality enabled
while other features can be enabled separately with specific licenses.
Key Features
The card key features are listed in the Key Features of 100G-LC-C, 100G-ME-C, 100G-CK-C, 100ME-
CKC, 10x10G-LC, 100GS-CK-LC, 200G-CK-LC, CFP-LC, and MR-MXP Cards.
The cards are single-slot cards and can be installed in Slot 2 to Slot 7 in the Cisco ONS 15454 M6 chassis,Slot 2
and Slot 3 in the Cisco ONS 15454 M2 chassis. The 100G-LC-C and 100G-ME-C cards have one DWDM port
and one CXP port. The 100G-CK-C and 100ME-CK-C cards have one DWDM port and one CPAK port.
Operating Modes for 100G-LC-C, 100G-ME-C, 100G-CK-C,

100GS-CK-LC, 200G-CK-LC, and 100ME-CKC Cards
Each operating mode can be configured using the specific set of cards and client payloads. Key Features of
100G-LC-C, 100G-ME-C, 100G-CK-C, 100ME-CKC, 10x10G-LC, 100GS-CK-LC, 200G-CK-LC, CFP-
LC, and MR-MXP Cards, on page 271 describes how each mode can be configured, the supported
payloads, and the valid port pair for a specific operating mode.
100G Operating Modes

The 100G-LC-C, 100G-ME-C, 100G-CK-C, 100GS-CK-LC, 100ME-CKC, and 200G-CK-LC cards
support the following 100G operating modes. The operating mode configuration for the 100G operating
modes is performed on the client card.
259
Operating Modes for 100G-LC-C, 100G-ME-C, 100G-CK-C, 100GS-CK-LC, 200G-CK-LC, and 100ME-CKC Cards
TXP-100G (Standalone 100GE Transponder)

RGN-100G (100G Regenerator)
TXP-100G (Standalone 100GE Transponder)

The cards can be configured as a standalone 100 Gigabit Ethernet transponder. The 100 Gigabit Ethernet traffic
is supported on the CXP/CPAK and coherent optical trunk. The 100 Gigabit Ethernet or OTU4 payload traffic is
routed from the CXP/CPAK to the optical trunk, passing through the T100 framer and vice versa. The supported
client signals in this mode are 100 Gigabit Ethernet LAN-PHY or OTU4 data rates.
RGN-100G (100G Regenerator)
The cards can be configured as a regenerator. Two cards can be connected to work in a back-to-back
mode connecting through the chassis backplane in the same shelf. The allowed slot pairs are 2-3, 4-5, 6-7,
8-9, 10-11, 12-13, or 14-15.
The client signals supported are 100 Gigabit Ethernet or OTU4. Regeneration is performed leveraging on
the OTU4 backplane interconnection. OTU4 overhead is terminated, allowing ODU4 to transparently pass
through. GCC0 is terminated, while GCC1 and GCC2 are allowed to pass through.
The CXP client is not required because communication between the two cards acting as a regeneration
group is supported through the chassis backplane.
MXP-2x40G
The 100G-CK-C and 100ME-CKC cards support the MXP-2x40G operating mode. The 100G-CK-C and
100ME-CKC cards can be configured as a 2-port 40 GE muxponder. Two 40 GE flows through the CPAK
client interface and are multiplexed in the 100G trunk interface. The traffic on the second client interface
can be configured only after the traffic is provisioned on the first client interface. This operating mode is
not supported on the 100GS-CK-LC card.
Note The synchronization for the 100G-CK-LC card is derived only from port 1. Hence, the traffic on port 2
must originate from the same synchronization source as port 1. The two ports must carry traffic from the
same synchronization source.
If ONS 15454 with the MXP-2x40G operating mode is connected to a NCS 6000 router, ensure that both
the 40G ports are connected to the same group of six ports on the NCS 6000 router. The 40G ports 1 and 2
need to connect to 1-6, 7-12, 13-18 ports on the NCS 6000 router.
200G Operating Modes

The 100GS-CK-LC and 200G-CK-LC cards also support the 200G operating modes. The operating
mode configuration for these modes is performed on the trunk card.
MXP_200G
MXP_10x10G_100G
MXP_CK_100G
MXP_200G
Three cards, trunk card, peer card, and skip card are required to configure this operating mode. The skip
card is adjacent to the peer card.
260
Operating Modes for 100G-LC-C, 100G-ME-C, 100G-CK-C, 100GS-CK-LC, 200G-CK-LC, and 100ME-CKC Cards
The trunk card is 100GS-CK-LC or 200G-CK-LC card; the peer card and skip cards are MR-MXP. The
first 10x10G is taken from the two SFP and two QFSP+ ports of the peer MR-MXP card and the second
10x10G is taken from the two SFP and two QFSP+ ports of the skip MR-MXP card.
200G-CK-LC card supports another configuration in the MXP_200G operating mode. In this
configuration, 2x40GE clients on QSFP+ ports and 2x10GE clients on SFP+ ports of both the peer MR-
MXP and skip MR-MXP cards are multiplexed into 200G traffic on the trunk 200G-CK-LC card.
The operating mode can be provisioned on the following slots:
ONS 15454 M6: 100GS-CK-LC or 200G-CK-LC card in slots 2 or 7, peer and skip MR-MXP cards in
adjacent slots 3, 4 or 5, 6
NCS 2015: 100GS-CK-LC or 200G-CK-LC card in slots 2, 7, 8, 13, or 14, peer and skip MR-MXP
cards in adjacent slots.
MXP_10x10G_100G
Three cards, trunk card, peer card, and skip card are required to configure this operating mode.
The trunk card is 100GS-CK-LC or 200G-CK-LC card; the peer card is 10x10G-LC and the skip card is
MR-MXP . The first 10x10G is taken from the ten SFP ports of the peer 10x10G-LC card and the
second 10x10G is taken from the two SFP and two QFSP+ ports of the skip MR-MXP card.
ONS 15454 M6: 100GS-CK-LC or 200G-CK-LC card in slots 2 or 7, peer and skip MR-MXP cards in
adjacent slots 3, 4 or 5, 6
NCS 2015: 100GS-CK-LC or 200G-CK-LC card in slots 2, 7, 8, 13, or 14, peer and skip MR-MXP
cards in adjacent slots.
MXP_CK_100G
Two cards, trunk and peer cards are required to configure this operating mode. The trunk card is 100GS-
CK-LC or 200G-CK-LC; the peer card is MR-MXP . The first 100G is taken from the CPAK client port of
the trunk 100GS-CK-LC or 200G-CK-LC card and the second 100G is taken from the CPAK client port of
the MR-MXP card.
200G-CK-LC card supports another configuration in the MXP_CK_100G operating mode. In this configuration,
10x10GE clients on QSFP+ or SFP+ ports of the peer MR-MXP card and 100GE client on the CPAK port of the
200G-CK-LC card are multiplexed into a 200G configuration on the trunk 200G-CK-LC card.
ONS 15454 M6: 100GS-CK-LC or 200G-CK-LC card and the peer MR-MXP card need to be in
adjacent slots 2-3, 4-5, 6-7
NCS 2015: 100GS-CK-LC or 200G-CK-LC card and the peer MR-MXP card need to be in adjacent
slots 2-3, 4-5, 6-7, 8-9, 10-11, 12-13, 14-15
References
For more information about the cards, see:
http://www.cisco.com/en/US/solutions/collateral/ns340/ns394/ns398/ns406/data_sheet_c78-729401.html
261
10x10G-LC Card
http://www.cisco.com/c/en/us/products/collateral/optical-networking/
network-convergence-system-2000-series/datasheet-c78-733529.html
http://www.cisco.com/c/en/us/products/collateral/optical-networking/
network-convergence-system-2000-series/datasheet-c78-733699.html
10x10G-LC Card
The 10x10G-LC card is a DWDM client card, which simplifies the integration and transport of 10 Gigabit
Ethernet interfaces and services into enterprises or service provider optical networks. The 10x10G-LC
card is supported on ONS 15454 M2 and ONS 15454 M6 platforms.
The 10x10G-LC card is a single-slot card and can be installed in any service slots of the chassis. The
10x10G-LC card consists of a 10-port SFP+ based (gray, colored, coarse wavelength division
multiplexing ([CWDM], and DWDM optics available) and one 100 G CXP-based port.
The 10x10G-LC card interoperates with 100G-LC -C cards through a chassis backplane.
Note The fan-tray assembly 15454-M6-FTA2 (for the Cisco ONS 15454 M6 chassis) or 15454-M2-FTA2 (for
the Cisco ONS 15454 M2Cisco NCS 2002 chassis) must be installed in the shelf where a 10x10G-LC card
is installed. When an ONS-SC+-10G-C pluggable is used along with the 10x10G-LC card, the maximum
operating temperature of the shelf must not exceed 50 degrees Celsius.
The 10x10G-LC card supports the following signal types:

OC-192/STM-64 (9.95328 Gbps)
10 Gigabit Ethernet LAN PHY (10.3125 Gbps)
10 G FC (10.518 Gbps)
8 G FC
OTU-2
G.709 overclocked to transport 10 Gigabit Ethernet as defined by ITU-T G. Sup43 Clause 7.1 (11.0957
Gbps)
IB_5G (supported only in TXP-10G operating mode)
The key features of 10x10G-LC card are listed in Key Features of 100G-LC-C, 100G-ME-C, 100G-CK-
C, 100ME-CKC, 10x10G-LC, 100GS-CK-LC, 200G-CK-LC, CFP-LC, and MR-MXP Cards.
Operating Modes for 10x10G-LC Card

The 10x10G-LC card supports the following operating modes:
MXP-10x10G (10x10G Muxponder)
RGN-10G (5x10G Regenerator)/TXP-10G (5x10G Transponder)
Low Latency
262
Fanout-10X10G
TXPP-10G
MXP-10x10G (10x10G Muxponder)
The 10x10G-LC card can be configured as a 10x10G muxponder. It can be connected with a 100G-LC-C,
100G-ME-C, 100G-CK-C, 100GS-CK-LCor 100ME-CKC card to support 10-port 10 G muxponder
capabilities. The 100G-LC-C, 100G-ME-C, 100G-CK-C, 100GS-CK-LC, 200G-CK-LC, or 100ME-CKC
card can be connected through the chassis backplane (no client CXP/CPAK required) with the 10x10G-LC
card to provide OTN multiplexing of the 10 G data streams into a single 100 G DWDM OTU4 wavelength.
When 10x10G-LC card is configured with 100GS-CK-LC card, OC-192/STM-64) and 10 Gigabit Ethernet
LAN PHY payloads are supported. The allowed slot pairs are 2-3, 4-5, 6-7, 8-9, 10-11, 12-13, or 14-15.
The 10x10G muxponder mode supports client signals that are a mix and combination of any
10 Gigabit Ethernet LAN-PHY, OC-192, STM-64, 10 G FC/FICON, 8 G FC/FICON, or OTU2 data rates.
RGN-10G (5x10G Regenerator)/TXP-10G (5x10G Transponder)
The 10x10G-LC card works as a standalone supporting the multitransponder functionality. The 10 Gbps SFP+
ports should be paired to provide the 10 G transponder functionality for each of the couple of ports. By using the
grey optics SFP+ to provide the client equipment connectivity and DWDM SFP+ on the WDM side, up to five
10 G transponders are supported by a single 10x10G-LC card. Up to 6 10x10G-LC cards are supported on the
Cisco ONS 15454 M6 chassis allowing for 30 10 Gbps transponders in a single shelf.
All the ports can be equipped with or without the G.709 Digital Wrapper function providing wide
flexibility in terms of the supported services.
As the client and trunk ports are completely independent, it is also possible to equip both the SFP+ of the
same pair of ports with the DWDM SFP+ thereby allowing them to function as a WDM regenerator. The
CXP pluggable is unused in this configuration.
Each of the SFP+ ports can be provisioned as a client or trunk. When one port is selected as a trunk, the
other port of the pair is automatically selected as the client port. The allowed port pairs are 1-2, 3-4, 5-6, 7-
8, or 9-10.
For RGN-10G mode, both the ports are trunk ports.
It is not a constraint to provision 5 couple of TXP-10G mode or 5 couple of RGN-10G mode. A mix of
TXP-10G and RGN-10G modes can be configured. For example, couple 1-2 and 5-6 can be configured as
a TXP-10G mode and the remaining as the RGN-10G mode.
Table 104: Supported Payload Mapping Between Two SFP+ Ports
SFP+ Payload (Peer-1) SFP+ Payload (Peer -2)
10GE-LAN (CBR Mapped) OTU2e or 10GE-LAN (CBR Mapped)
OTU2 OC192 or OTU2
Low Latency
263
The 10x10G-LC card can be configured in the low latency mode. This configuration minimizes the time
spent by the signal to cross the card during the regeneration process. Adjacent SFP ports must be selected
while provisioning this mode although each SFP port functions as a unidirectional regenerator. Both ports
are trunk ports. The allowed ports are 1-2, 3-4, 5-6, 7-8, or 9-10. A mix of TXP-10G, RGN-10G, and low
latency modes can be configured.
The low latency mode supports 10GE and 10G FC data rates. The same payload must be provisioned on
both the SFP ports involved in this operating mode. GCC cannot be provisioned on the ports used in the
low latency mode. The low latency mode does not support terminal and facility loopback.
Fanout-10X10G
The 10x10G-LC card can be configured in the fanout-10x10G mode. The fanout configuration configures
the CXP side as the client and SFP side as the trunk. This configuration functions as ten independent
transponders. The CXP lanes are managed independently and the payload for each CXP-lane-SPF+ pair is
independent from the other pairs.
The fanout configuration provides the following mapping for the port pairs:
CXP lane 2-SFP1
CXP lane 3-SFP2
CXP lane 4-SFP3
CXP lane 5-SFP4
CXP lane 6-SFP5
CXP lane 7-SFP6
CXP lane 8-SFP7
CXP lane 9-SFP8
CXP lane 10-SFP9
CXP lane 11-SFP10
Note CXP lane 1 and CXP lane 12 are not supported in this configuration.
The fanout configuration supports the following payload types and mapping modes:
10GE (CXP line), transparent (no mapping), 10GE (SFP)
10GE (CXP line), GFP mapping, OTU2 (SFP)
10GE (CXP line), CBR mapping, OTU2e (SFP)
TXPP-10G
Splitter protection can be implemented on the 10x10G-LC card in the TXPP-10G mode. The 10x10G-LC
card supports up to two splitter protection groups with one client and two trunk ports. The client and
trunk ports on the two groups are:
• Port 3 (client), port 4, and port 6 (trunks) on the first protection group
264
CFP-LC Card
• Port 7 (client), port 8, and port 10 (trunks) on the second protection group
Port 1 and port 2 are available for unprotected transponders and can be configured in the standard TXP-
10G mode, with the first port selected as the trunk and the other port selected as the client. Two ports, port
5 and port 9 are left unused. A Y-Cable protection group cannot be defined on the same 10x10G-LC card
when it is provisioned in the TXPP-10G mode. The splitter protection is supported only for 10GE traffic,
with trunk ports set to disabled FEC, standard FEC, or enhanced FEC (E-FEC) mode.
The following figure shows the 10x10G-LC card configured for splitter protection.
Figure 38: Splitter Protection on the 10x10G-LC card
Note If the card is configured only once in the TXPP-10G mode, with port 3 or port 7 as the client port, the rest
of the ports are available for configuration in the standard TXP-10G mode (except port 5 and port 9, which
are left unused). The TXPP-10G mode configuration is successful only when three licenses for the three
ports (one client and two trunk ports) involved in splitter protection are available for the card. No new
licensing is required for the splitter protection operating mode.
For more information about the 10x10G-LC card, see

CFP-LC Card
The CFP-LC card is a client card, which simplifies the integration and transport of 40 GE and 100 GE
interfaces and services into enterprises or service provider optical networks. The CFP-LC card is supported
on the Cisco ONS 15454 M6 and NCS 2015 platform. The CFP-LC card provides 100 Gbps services to
support 100 G DWDM wavelengths generated by the 100G-LC-C card. The traffic coming from CFP
interfaces is switched to the trunk port through a cross-switch.
265
Key Features
The CFP-LC card supports the following signal types:

100 Gigabit Ethernet
40 Gigabit Ethernet
OTU-3
OTU-4
Client ports can be equipped with a large variety of CFP pluggables.
Key Features
The key features of CFP-LC card are listed in Key Features of 100G-LC-C, 100G-ME-C, 100G-CK-
C, 100ME-CKC, 10x10G-LC, 100GS-CK-LC, 200G-CK-LC, CFP-LC, and MR-MXP Cards.
The CFP-LC card is a double-slot card and can be installed in Slot 3 or Slot 5 in the Cisco ONS 15454 M6
chassis, and the 100G-LC-C peers cards must be placed in the adjacent slots (2 and 5 or 4 and 7). If the
card is plugged in one of the unsupported slots or in a Cisco ONS 15454 M2 chassis, the system raises an
EQPT::MEA (Mismatch of Equipment Alarm) notification. Up to two CFP-LC cards can be installed per
Cisco ONS 15454 M6 shelf assembly, supporting up to 28x 40-Gbps or 14x 100 Gbps interfaces per 42-
rack units (RU) bay frame.
The CFP-LC card is equipped with two 100 G CFP pluggable modules and a cross-bar embedded switch
module. The CFP-LC card provides two backplane interfaces (working both at 100 Gb or 40 Gb) that are
suitable for the cross-switch application on the incoming CFP signals. The CFP-LC card can be
configured to send all the client CFP services towards the backplane to be connected with up to two 100G-
LC-C cards placed in the two adjacent slots (upper and lower) of the Cisco ONS 15454 M6 chassis in
order to provide two 100 G transponders configurations.
Note The fan-tray assembly 15454-M6-FTA2 (for the M6 chassis) must be installed in the shelf where a CFP-
LC card is installed.
Operating Modes for CFP-LC Card

The CFP-LC card supports the following operating modes:
2x40G Muxponder
CFP-TXP (100G Transponder)
2x40G Muxponder
The CFP-LC card can be configured as a 2-port 40 G muxponder. It can be connected with the 100G-LC-
C, 100G-ME-C, 100G-CK-C, or 100ME-CKC card to support 2-port 40 G muxponder capabilities. The
100G-LC-C, 100G-ME-C, 100G-CK-C, 100ME-CKC card can be connected through the
266
MR-MXP Card
Cisco ONS 15454 M6backplane (no client CXP/CPAK required) with the CFP-LC card to provide OTN
multiplexing of the 40 G data streams into a single 100 G WDM OTU4 wavelength. The 2x40G
muxponder mode supports client signals that are a mix and combination of any 40 Gigabit Ethernet LAN-
PHY or OTU3 data rates.
CFP-TXP (100G Transponder)
The CFP-LC card can be configured as a 100G transponder. It can be connected with the 100G-LC-C,
100G-ME-C, 100G-CK-C, or 100ME-CKC card to support the client interface for the 100-Gbps
transponder capabilities. The 100G CXP pluggable available on the 100G-LC or 100G-ME-C card supports
only 100GE-BASE-SR10 client interface, while the 100GE-BASE-LR4 is supported using a CFP form
factor only. The 100G CPAK pluggable available on the 100G-CK-C or 100ME-CKC card supports the
CPAK-100G-SR10 and CPAK-100G-LR4 client interfaces.
The CFP-LC card can be connected through the Cisco ONS 15454 M6backplane with up to two 100G-LC
cards placed in the upper or in the lower slot of the same shelf to provide the equivalent functionalities of
two 100 G LR4 transponders, leveraging on CFP pluggables as client interface.
For more information about the CFP-LC card, see
MR-MXP Card
The MR-MXP card is a mixed rate 10G and 40G client muxponder that is supported on Cisco ONS 15454
M2 and Cisco ONS 15454 M6 platforms. The card is equipped with one CPAK port, two SFP ports, and
two QSFP+ ports. The card can interoperate with 100GS-CK-LC, 200G-CK-LC, and 10x10G-LC cards
through a chassis backplane.
Note The FPGA and firmware upgrade (via CTC) for MR-MXP cards should be done one by one. Wait till the
card completely comes up, to active or standby (based on configuration) before upgrading the next card in
the chassis. If this is not followed, the load on the TNC card increases causing longer booting time for the
line cards in the chassis and in a few cases, the line cards might not boot up.
When the node is upgraded to R10.5.2.4 or R10.6.x from a previous release, traffic loss on the MR-MXP card
might occur for few seconds. When the node is reverted from R10.6.x to R10.5.x, cold reboot is required.
The TRAF-AFFECT-RESET-REQUIRED (Traffic Affecting Reset Required) alarm is raised on the MR-MXP
card in CTC after the node is upgraded to R10.5.2.4 or R10.6. Hence, it is recommended to reboot the card.
In the Card view, go to Provisioning > Card.
Click FPGA/FIRMWARE Upgrade/Traffic Affecting Reset to reboot the card.
When the node is upgraded to R10.8 followed by reset of the active control card, FPGA upgrade of
the MR-MXP card fails.
Perform the following steps to upgrade FPGA successfully.
Soft reset the MR-MXP card.
Click FPGA/FIRMWARE Upgrade/Traffic Affecting Reset to upgrade FPGA.
267
Key Features
Encryption as an Appliance
The MR-MXP-K9 and MR-MXP-K9= PIDs of MR-MXP card are referred as Encryption as an appliance
PIDs. The card authentication and payload encryption are enabled by default and cannot be disabled for
these PIDs.
The MR-MXP-K9 and MR-MXP-K9= PIDs of MR-MXP card do not interoperate with other PIDs of
the MR-MXP card. In MXP-200G operating mode, the two MR-MXP cards must have the same PIDs.
Key Features
The card key features are listed in the Key Features of 100G-LC-C, 100G-ME-C, 100G-CK-C, 100ME-
CKC, 10x10G-LC, 100GS-CK-LC, 200G-CK-LC, CFP-LC, and MR-MXP Cards.
The MR-MXP card provides the following features:
Termination point for a 100G client payload on the CPAK port. The aggregated payloads are forwarded
to a 200G companion trunk card.
Provides encryption capability on the virtual port or OTU4 backplane port. This card provides
confidentiality of the data, which is sent over a fiber optic communication channel, using Next
Generation Cryptography. The encryption works only after provisioning the high speed or low speed
encryption license. To provision encryption on the MR-MXP card, see NTP-G340 Provisioning
Encryption on the WSE and MR-MXP Cards, on page 784.
Supports feature-based licensing. The base functionality is enabled in the licensed card version.
Additional features such as encryption are provided through specific feature licenses. The MR-MXP-
LIC is the licensed card version of the MR-MXP card. For more information on licensing, see the
Licensing Configuration Guide.
Third Party Certificates-From Release 10.7, the MR-MXP card supports the generation of a Certificate
Signing Request (CSR) and the installation of Locally Significant Certificates (LSCs) that can be used
to authenticate the peer card connection. Third party certificates also referred to as Locally Significant
Certificates (LSCs) are certificates that are signed by a Certification Authority (CA) other than Cisco
Certificate Authority. LSCs allow customers to have their own Public Key Infrastructure (PKI) to
provide better security, to have control of their own CA, and to define policies, restrictions, and usages
on the generated certificates.
A public-private key is generated inside the target system and then the generated public key along with
other product or customer specific information (collectively called as a Certificate Signing Request) is
then sent to be signed by a CA (customer owned or a third party) after which, the signed certificates
are imported or installed via a trusted and secure channel or method into the target system. After the
signed certificates are installed, it can be used in conjunction with the private key to authenticate any
remote connection before exchanging sensitive information with the same.

Operating Modes for MR-MXP Card

The MR-MXP card supports the following 200G operating modes:
MXP-200G
MXP-10x10G-100G
268
• MXP-CK-100G
Each operating mode can be configured using the specific set of cards and client payloads. The operating
mode is configured on the companion trunk card (100GS-CK-LC or 200G-CK-LC). For more information
about these operating modes, see Operating Modes for 100G-LC-C, 100G-ME-C, 100G-CK-C, 100GS-
CK-LC, 200G-CK-LC, and 100ME-CKC Cards, on page 259.
The MR-MXP card supports the following 100G operating modes:
MXP-100G
TXP-100G
100G-B2B
Note All the 100G and 200G operating modes support the encryption feature except MXP-CK-100G.
MXP-100G
MXP-100G operating mode is provisioned with MR-MXP card on the client side and the adjacent 200G-CK-LC
card or 100GS-CK-LC card on the trunk side. The operating mode can be provisioned only from the client side
but can be deleted from both client and trunk sides. This mode supports 10GE as the payload. This mode uses the
SFP+ and QSFP+ ports on MR-MXP client card and the DWDM port on the 200G-CK-LC card or 100GS-CK-
LC card. The aggregate signal from client is sent to trunk through the backplane.
MXP-100G operating mode is also provisioned with MR-MXP card on the client side and the adjacent
200G-CK-LC card on the trunk side. The operating mode can be provisioned only from the client side but
can be deleted from both client and trunk sides. This mode supports 2X10GE+2X40GE as the payload.
This mode uses the SFP+ and QSFP+ ports on MR-MXP client card and the DWDM port on the 200G-CK-
LC card. The aggregate signal from client is sent to trunk through the backplane.
ONS 15454 M2: Slots 2 and 3
ONS 15454 M6: Slots 2 and 3, 4 and 5, 6 and 7
NCS 2015: Slots 2 and 3, 4 and 5, 6 and 7, 8 and 9, 10 and 11, 12 and 13, 14 and 15
TXP-100G
TXP-100G operating mode is provisioned with MR-MXP card on the client side and the adjacent 200G-
CK-LC card or 100GS-CK-LC card on the trunk side. The operating mode can be provisioned only from
the client side but can be deleted from both client and trunk sides. This mode supports 100GE as the
payload. This mode uses the CPAK port on MR-MXP client card and the DWDM port on the 200G-CK-
LC card or 100GS-CK-LC card. The aggregate signal from client is sent to trunk through the backplane.
100G-B2B
269
The 100G-B2B operating mode can be provisioned with MR-MXP card on the client side and the adjacent
MR-MXP card card on the trunk side. The operating mode performs encryption of an 100GE client signal
taken from the CPAK interface or 10x10GE client signal taken from the two QSFP and SFP interfaces of
the client MR-MXP card and maps it to an OTU4 signal with encryption. The OTU4 signal is passed to the
trunk MR-MXP card in the peer slot through the back plane. The trunk MR-MXP card converts the OTU4
signal to grey wavelength with either an SR-10 or an LR-4 through the CPAK interface of the trunk card.
The 100GE client payload can be divided into either four or 10 sub-lanes.
The CPAK port or two QSFP and 2 SFP+ ports can be selected on the client card during the provisioning.
The operating mode can be provisioned from any MR-MXP card in the peer slot pair. When the operating
mode is created, the card that the user selects to create operating mode acts as the client card and the peer
card for that card acts as the trunk card. When payloads are created on both the client and trunk cards, CTC
provides the option to select the number of lanes as required for LR4/SR10 based payload.
The provisioning operations like payload/operating mode creation and FEC settings in 100G-B2B
operating mode of MR-MXP card takes longer when compared to other operating modes.
Sub Operating Modes

The sub OpMode in MR-MXP cards determines the operating mode on the card client ports. For
example, the QSFP+ port can be provisioned either as a 40GE port or can be divided into four 10G ports.
This provisioning is controlled by the sub OpMode. The sub OpMode is created by default when the
operating mode is configured on the card.
OPM_10x10G—This is the default sub OpMode for the MXP-100G, MXP-200G, and MXP-10x10G-100G
operating modes. In this sub OpMode, the SFP and QSFP+ ports are divided in such a way that 10 10GE
payloads can be provisioned. When a PPM is provisioned on a QSFP+ port, four internal ports are created.
A 10 GE payload can be provisioned on each of these ports. The OPM-10x10G operating mode is
provisioned with MR-MXP card on the client side and the adjacent MR-MXP card on the trunk side. The
operating mode can be provisioned only from the client side but can be deleted from both client and trunk
sides. The aggregate signal from client is sent to trunk through the backplane.
OPM_100G—This is the default sub OpMode for the MXP-CK-100G operating mode where the CPAK
port can be provisioned with a 100GE or OTU4 payload. The 100GE payload can be divided into
either four or 10 sub-lanes. For 100GE payload, the OPM-100G operating mode is provisioned with
MR-MXP card on the client side and the adjacent MR-MXP card on the trunk side. For OTU4
payload, the OPM-100G operating mode is provisioned with MR-MXP card on the client side and the
adjacent 200G-CK-LC card on the trunk side.The operating mode can be provisioned only from the
client side but can be deleted from both client and trunk sides. The aggregate signal from client is sent
to trunk through the backplane.
OPM_2x40G_2x10G—This sub OpMode is provisioned for the MXP-100G operating mode to support
the 2X10GE+2X40GE payload. This operating mode is provisioned with MR-MXP card on the client
side and the adjacent 200G-CK-LC card on the trunk side. The operating mode can be provisioned
only from the client side but can be deleted from both client and trunk sides. The aggregate signal from
client is sent to trunk through the backplane.
270
Limitations of Payloads on MR-MXP Card
This sub OpMode is also provisioned for the MXP-200G operating mode to support the following
sub OpMode combinations on both peer and skip MR-MXP cards.
OPM_10x10G and OPM_10x10G
OPM_2x40G_2x10G and OPM_2x40G_2x10G
OPM_2x40G_2x10G and OPM_10x10G
OPM_10x10G and OPM_2x40G_2x10G
Limitations of Payloads on MR-MXP Card

Line timing is not supported.
DCC communication channel is not supported for OC192/STM64.
GCC0 communication channel is not supported.
Trace is not supported for OC192/STM64.
Overclocking of OTU2 payload is not supported.
Y cable protection is not supported.
Only G-FEC is supported on OTN payloads.
The lanes in a QSFP+ port support only homogeneous payloads.
Key Features of 100G-LC-C, 100G-ME-C, 100G-CK-C,

100ME-CKC, 10x10G-LC, 100GS-CK-LC, 200G-CK-
LC, CFP-LC, and MR-MXP Cards
The 100G-LC-C, 100G-ME-C, 100G-CK-C, 100ME-CKC, 10x10G-LC, 100GS-CK-LC, 200G-CK-LC,
CFP-LC, and MR-MXP cards support the following key features:
Operating Modes—The cards can be configured into multiple operating modes. The cards can be equipped
with pluggables for client and trunk options, and offer a large variety of configurations. When you
configure the card into multiple operational modes, make sure that the following tasks are completed:
The card must be preprovisioned and the modes must be configured. None of the modes are
provisioned on the card by default. All operating modes are created on the card level. These
are card-specific provisioning, which decides the behavior of a particular card.
Depending on the card mode selected, the supported payload for that particular card mode must be
provisioned on the PPMs.
The payloads can be provisioned after configuring the operational mode on the card.

271
Key Features of 100G-LC-C, 100G-ME-C, 100G-CK-C, 100ME-CKC, 10x10G-LC, 100GS-CK-LC, 200G-CK-LC, CFP-LC, and MR-MXP Cards
Each operating mode can be configured using the specific set of cards and client payloads.
Table 105: Operating Modes and Supported Payloads for 100G-LC-C, 100G-ME-C, 100G-CK-C, 100ME-CKC,
10x10G-LC, 100GS-CK-LC, 200G-CK-LC, CFP-LC, and MR-MXP Cards
Card (provisioning Operational Mode Peer Card (connected Supported Client

executed on this card) through backplane) Payloads
100G-LC-C, 100G-ME-C, TXP-100G (Standalone — 100GE, OTU4

100G-CK-C, 100G Transponder)
100ME-CKC
RGN-100G (100G 100G-LC-C, 100G-ME-C, — Regeneration of any
Regenerator) 100G-CK-C, 100 G configuration
100ME-CKC
MXP-2x40G (for — 40GE

100G-CK-C,
100ME-CKC)
272

100GS-CK-LC and TXP-100G (Standalone — 100GE and OTU4

200G-CK-LC 100G Transponder) OTU4 is supported only
for the 200G-CK-LC card.
RGN-100G (100G 100GS-CK-LC or Regeneration of any

Regenerator) 200G-CK-LC 100 G configuration
MXP-200G MR-MXP 10GE, OC192/STM64,

and OTU2
Skip card is MR-MXP
OC192/SMT64, and OC192/STM64, and
OTU2 payloads are
OTU2 payloads are
supported only when the
supported in MLR QSFP+
sub OpMode in MR-
MXP is OPM_10x10G.
MXP-10x10G-100G 10x10G-LC 10GE, OC192/STM64,

and OTU2
Skip card is MR-MXP
OC192/STM64, and
OTU2 payloads are
sub OpMode in MR-MXP
is OPM_10x10G.
MXP-CK-100G MR-MXP
273

10GE, 100GE,
OC192/STM64, and
OTU2
10GE, OC192/STM64,
and OTU2 payloads are
is OPM_10x10G.
OTU4 (only with
200G-CK-LC card)
When 200G-CK-LC and
MR-MXP cards are
provisioned in
MXP-CK-100G operating
mode with OTU4
payload, the FEC
parameter on the
200G-CK-LC client can
be set only to Standard
and cannot be changed to
Disable or Enhanced.
100GE and OTU4
payloads are supported
only when the sub
OpMode in MR-MXP is
OPM_100G.
274

10x10G-LC MXP-10x10G (10x10G 100G-LC-C, 100G-ME-C, OC192/STM-64, 10GE-

Muxponder) 100G-CK-C, LAN Phy, 10GE-WAN
100ME-CKC, , Phy (using OC192),
100GS-CK-LC OTU2, OTU2e, 8G FC,
200G-CK-LC 10G FC, FICON
Only OC192/STM64 and
10GE are supported
when the 10x10G-LC
card is connected with
the 100GS-CK-LC card.
Only OC192/STM64,
10GE, and OTU2 are
supported when the
10x10G-LC card is
connected with the
200G-CK-LC card.
RGN-10G (5x10G — 10GE-LAN Phy, OTU2

Regenerator)
TXP-10G (5x10G — 10GE-LAN Phy, OTU2e,

Transponder) OTU2, OC192/STM-64,
8G FC, 10G FC, IB_5G
Low Latency — 10GE, 10G FC
Fanout-10X10G — 10GE
TXPP-10G — 10GE
CFP-LC 2x40G Muxponder 100G-LC-C or OTU3/40GE-LAN Phy

100G-CK-C card
CFP-TXP (100G 100G-LC-C or OTU4, 100GE

Transponder)—One port 100G-CK-C card
CFP-TXP (100G Two 100G-LC-C or OTU4, 100GE
Transponder)—Two ports 100G-CK-C cards
275

MR-MXP MXP-100G 200G-CK-LC card or 10GE, OC192/STM64,

100GS-CK-LC card and OTU2
OC192/STM64, and
OTU2 payloads are
is OPM_10x10G.
MXP-100G 200G-CK-LC card 2X10GE+2X40GE

This payload is supported
only when the sub
OpMode in MR-MXP is
OPM_2x40G_2x10G.
TXP-100G 200G-CK-LC card or 100GE

100GS-CK-LC card
100G-B2B MR-MXP 100GE, 10x10GE
MXP-200G 200G-CK-LC card or 10GE, OC192/STM64,

100GS-CK-LC card 40G, and OTU2
Skip card is MR-MXP
MXP-CK-100G 200G-CK-LC card or 100GE,10GE,OC192/STM64,

MXP-CK-100G 200G-CK-LC OTU4

This payload is supported
only when the sub
OpMode in MR-MXP is
OPM_100G.
MXP-10X10G-100G 200G-CK-LC card or 10GE,OC192/STM64,

For operating modes of the respective cards, see the Operating Modes for 100G-LC-C, 100G-ME-C, 100G-
CK-C, 100GS-CK-LC, 200G-CK-LC, and 100ME-CKC Cards, Operating Modes for 10x10G-LC Card,
Operating Modes for CFP-LC Card, and Operating Modes for MR-MXP Card, on page 268.
Protocol Transparency—The 100G-LC-C, 100G-ME-C, 100G-CK-C, 100ME-CKC, 100GS-CK-LC,
and 200G-CK-LC cards deliver any 100 Gbps services for cost-effective, point-to-point networking.
The 10x10G-LC card delivers any 10 Gbps services for cost-effective, point-to-point networking. In
case of 100 G muxponder clients that are mapped into OTU4 DWDM wavelength.
276
Table 106: Transponder Client Configurations and Mapping for 100G-LC-C and 100G-CK-C Cards
Client Trunk
Format Rate (Gbps) Mapping Format Rate with 7% GFEC,

20% GFEC, or EFEC
OH (Gbps)
100GE LAN-PHY 101.125 Bit transparent OTU4 111.809
through standard
G.709v3 mapping
OTU4 111.809 Transparent G.709

standard
Table 107: Transponder Client Configurations and Mapping for 10x10G-LC Card
Client Mapping
Format Rate (Gbps)
10GE LAN-PHY (MXP-10x10G 10.3125 CBR-BMP clause 17.2.4 (ex G

mode) sup43 7.1) + GMP ODU2e to
OPU3e4
10GE LAN-PHY (MXP-10x10G 10.3125 GFP-F clause 17.4.1 (ex G sup43

mode) 7.3) + GMP ODU2 to OPU3e4
10GE LAN-PHY (TXP-10G mode) 10.3125 CBR-BMP clause 17.2.4 (ex G

sup43 7.1)
10GE LAN-PHY (TXP-10G mode) 10.3125 GFP-F clause 17.4.1 (ex G sup43
7.3)
OC-192/STM-64 9.953 CBR-BMP clause 17.2.2 (Sync) +

GMP ODU2 to OPU3e4
10G FC 10.518 513b Transc + AMP GFP-F clause

17.8.2 + GMP ODU2e to OPU3e4
8G FC 8.500 CBR-BMP clause 17.9 (OduFlex)

+ GMP ODU2 to OPU3e4 (8
timeslot mapping)
8G FC 8.500 GMP ODU2 to OPU3e4
OTU2 10.709 ODU transparent + GMP ODU2 to

OPU3e4
OTU2e 11.095 ODU transparent + GMP ODU2e

to OPU3e4
IB-5G 5.0000 GMP ODU2e to OPU3e4
277
Table 108: Client Configurations and Mapping for CFP-LC Card
Client Trunk
Format Rate (Gbps) Mapping Format Rate with 7% GFEC

or EFEC OH (Gbps)
100GE LAN-PHY 101.125 Bit transparent OTU4 111.809
through standard
G.709v3 mapping

standard
40GE LAN-PHY 41.250 1024b/1027b transc

OPU4 GMP G709
Appendix VIII

standard
Flow-Through Timing—The cards allow the timing to flow through from client to line optical interface.
The received timing from client interface is used to time the line transmitter interface. This flow-
through timing allows multiple cards to be placed in the same shelf but be fully independently timed,
independent of the NE timing.
Far-End Laser Control (FELC)—FELC is supported on the cards. For more information on FELC, see
"Far-End Laser Control" section.
Performance Monitoring—The 100-Gbps DWDM trunk provides support for both transparent and non-
transparent signal transport performance monitoring. The Digital Wrapper channel is monitored according
to G.709 (OTN) and G.8021 standards. Performance Monitoring of optical parameters on the client and
DWDM line interface include Loss Of Signal (LOS), Laser Bias Current, Transmit Optical Power, and
Receive Optical Power. Calculation and accumulation of the performance monitoring data are supported in
15-minute and 24-hour intervals as per G.7710. Physical system parameter measured at the wavelength
level like Mean PMD, accumulated Chromatic Dispersion, or Received OSNR are also included in the set of
performance monitoring parameters. These can greatly simplify troubleshooting operations and enhance the
set of data which can be collected directly from the equipment. The performance monitoring for the CFP-
LC card takes into account that the two CFP-LC cards are an host board supporting CFP client equipment,
while the digital monitoring if the incoming client is implemented on the 100G cards. There is a virtual port
connection that displays the Digital Wrapper monitoring according to G.709 (OTN) as well as the RMON
for Ethernet signals, while the optical performance monitoring is directly available on the two CFP-LC
cards. Calculation and accumulation of the performance monitoring data are supported in 15-minute and 24-
hour intervals as per G.7710.
Loopback—The terminal, facility, or backplane loopback can be provisioned on all the ports of the 100G-LC-
C, 100G-CK-C, 100G-ME-C, 100ME-CKC, 10x10G-LC, 100GS-CK-LC, and 200G-CK-LC cards
configured in any operating mode except for the low latency mode. The backplane facility loopback cannot
be configured on the 10x10G -LC card configured in the MXP-10x10G mode. The loopback can be
provisioned only when the port is in OOS-MT state. A new port cannot be provisioned when the backplane
loopback is configured on the 10x10G-LC card. For the CFP-LC card configured in the CFP-TXP or CFP-
MXP mode, the facility or terminal loopback can be configured on the backplane of the peer 100G-LC-C,
100G-CK-C, 100G-ME-C, 100ME-CKC, 100GS-CK-LC, and 200G-CK-LC cards. Terminal and facility
loopback can be provisioned on MR-MXP cards configured in any operating mode.
278
In Release 10.0.2, the facility loopback and drop feature can be provisioned on the client, trunk, and
backplane interfaces of the 100G-LC-C, 10x10G-LC, CFP-LC, and 100G-CK-C cards as follows:
Trunk facility loopback (drop) and client facility loopback (drop) is supported on:
100G-LC-C cards configured in the TXP mode (with CXP client pluggable) for OTU4 and
100G-CK-LC configured in the TXP mode (with CPAK client pluggable) for OTU4 and
When facility loopback (drop) is provisioned on the trunk interface, the trunk RX signal is sent
back to the trunk TX port and an ODUk-AIS (for OTU4 payloads) or an LF (for 100GE
payloads) signal is fowarded to the client port in the downstream direction for any of the squelch
settings. When facility loopback (drop) is provisioned on the client interface, the client RX signal
is sent back to the client TX port and an ODUk-AIS signal is forwarded to the trunk port in the
downstream direction for any of the squelch settings.
Backplane facility loopback (drop) is supported on:
100G-LC-C and CFP-LC configured in the TXP mode (with CFP client pluggable) for OTU4
and 100GE client payloads.
100G-CK-C and CFP-LC configured in the TXP mode (with CFP client pluggable) for OTU4
and 100GE client payloads.
When facility loopback (drop) is provisioned on the backplane interface, the client RX signal is
sent back to the client TX port and an ODUk-AIS signal is forwarded to the trunk port in the
downstream direction for any of the squelch settings.
Fault propagation on 10GE, 40GE, and 100GE clients— In R 10.3, a new squelch option named LF is
supported for GigE payloads. A local fault (LF) indication is fowarded to the client port in the
downstream direction when a failure on the trunk port occurs. The LF option is supported for :
10GE payloads on 10x10G-LC cards configured in the:
0 RGN-10G or TXP-10G mode
1 MXP-10x10G mode (paired with 100G-LC-C, 100G-CK-C, or 100GS-CK-LC card)
2 MXP-10x10G-100G mode ( paired with a 100GS-CK-LC or 200G-CK-LC card)
100GE payloads on:

0 100G-LC-C, 100G-CK-LC, 100GS-CK-LC, or 200G-CK-LC cards configured in the TXP-
100G mode
1 CFP-LC cards configured in the CFP-TXP mode (paired with 100G-LC-C or 100G-CK-
C card)
40GE payloads on:

0 CFP-LC card configured in the 2x40G Muxponder mode (paired with a 100G-LC-C
or 100G-CK-C card)
1 100G-CK-C card configured in the MXP-2x40G mode
279
Trail Trace Identifier—In R 10.3, the Trail Trace Identifier (TTI) in the path monitoring overhead is
supported in OTU, and ODU OTN frames. It is possible to to individually manage the Source Access
Point Identifer (SAPI), Destination Access Point Identifer (DAPI), and User Operator Data fields on
VTXP. This feature is also supported on these cards.
10x10G-LC— OTU4 and ODU4 payloads
CFP-LC— OTU4, ODU4, OTU3, and ODU3 payloads
100G-LC-C, 100G-CK-LC, 100GS-CK-LC, 200G-CK-LC— OTU4 and ODU4 payloads
The Trail Trace Identifier Mismatch (TTIM) alarm is raised after comparing only the SAPI bytes.
TTI monitoring is not supported between two nodes (node 1, node 2) in the following conditions:
Node 1 and node 2 are installed with a release earlier to R10.3. Node 2 is upgraded to R 10.3. New
TTI strings provisioned at either node1 or node 2 raises the TTIM alarm.
Node 1 is installed with the R 10.3 software. Node 2 is installed with a release earlier to R10.3.
New TTI strings provisioned at either node1 or node 2 raises the TTIM alarm.
Node 1 is installed with R 10.3 software and TTI settings are configured. Node 2 is installed with
the R10.3 software but the database is loaded from a release earlier to R10.3.
Generalized Multiprotocol Label Switching — The Generalized Multiprotocol Label Switching

(GMPLS) circuit can be created on the 100G-LC-C, 100G-CK-C, 10 x10G-LC, 100GS-CK-LC, and
200G-CK-LC cards. However, this circuit cannot be created when the card is in 100G regenerator
mode. When the card is configured in MXP-10 x10G card mode, only GMPLS Optical Channel
Network Connections (OCHNCs) can be created.
Automatic Laser Shutdown (ALS) can be configured on all the ports. ALS is supported only on the
ports that are configured with OC192/STM64, OTU2, and OTU4 payloads.
GCC channels—can be provisioned on the OTU2 client and trunk ports of the 10 x10G-LC card, OTU3
port (virtual port on the peer 100G-LC-C or 100G-CK-C card) of the CFP-LC card, and the OTU4
client and trunk ports of the 100G-LC-C or 100G-CK-C card.
50 ms switching with PSM—A protection switch time of less than 50 ms can be achieved with two
CFP-LC cards on their 100GE client ports using a PSM card that is configured in the standalone mode.
The client ports of the CFP-LC cards are connected to the working and protect ports of the PSM card.
An OCHCC circuit must be created between the two client ports. PSM is also supported on 100GS-
CK-LC or 200G-CK-LC cards on their trunk ports where the protection switch time of 50 ms is
achieved in the TXP-100G configuration with 20%SD FEC.
The optical TX power can be set to a value from -10.0 to +0.25 dBm on the trunk port of the 100G-LC-
C, 100G-CK-C card, or 200G-CK-LC card -10.0 to -0.5 dBm for 100GS-CK-LC card; to enable it to
interoperate with ASR 9000 series routers and Cisco CRS-3 routers. The TX shutdown feature allows
you to turn off the TX power on the 100G-LC-C, 100G-CK-C, or 200G-CK-LC cards when the trunk
port in out of service or in maintenance. The 100G-LC-C, 100G-CK-C, and 200G-CK-LC cards have
the ability to receive optical signals even when the TX power is turned off.
Pseudo Random Binary Sequence (PRBS)—For 100G-CK-C and 100G-LC-C cards, the trunk ports can
generate PRBS_31 pattern and detect PRBS_11, PRBS_23, and PRBS_31 patterns. Only PRBS_31 is
supported on the 100GS-CK-LC card. The detection is always on and does not need to be enabled. The
generation can be enabled that prompts the card to fulfill the OPU with PRBS_31 pattern.
280
Functions and Features
Licensing—The 100G-LC-C card adds the capability to cost-effectively transport the 10G service
offering as a Pay-As-You-Grow licensing model for the 10 x 10G muxponder. A licensed card works
in conjunction with a licensed 10 x10G line card. The two cards that can only work in this
configuration and in combination of the other licensed pair card offers a price-sensitive solution with
the ability to equip one 10G service.
The 200G-CK-LC card also supports licensing. The 200G-CK-LIC is the licensed card version of
the 200G-CK-LC card. The licensed card version has only some basic functionality enabled while
other features can be enabled separately with specific licenses. For more information on licensing,
see the Licensing Configuration Guide.
Note Licensing is not supported on the CFP-LC, 100G-CK-C and 100GS-CK-LC cards.
Multivendor Interoperability - From Release 10.6.2, the 200G-CK linecard can be configured to inter-
operate with other vendor interfaces. A new option called, Interop Mode is available to disable/enable
interoperability. This option is available, when, the:
Modulation format is 100G-QPSK
FEC is set to 7% High Gain FEC
Admin state of the trunk port is set to OOS-DSBLD (Out of service and disabled).
License L-NCS2K-DQPSK-LH= is active.
The Interop Mode is available on the full PID (NCS2K-200G-CK) and on the licensed PID
version, 200G-CK-LIC, when license L-NCS2K-DQPSK-LH= is active.
The behavior and performance of the card configured with HG-FEC Multivendor FEC, is the same
as the old HG-FEC mode (no optical performance variation). The only difference is that the DGD
data retrieved form the CTC PM tab has a reduced accuracy.
200G-CK-LC and 10x10G-LC cards—Supports protection through Y-cable protection scheme.
Y-cable protection is supported when the 200G-CK-LC card is configured in TXP-100G operating
mode and the 100G client CPAK ports are provisioned with 100GE payload. This configuration uses
the CPAK-100G-LR4 pluggable.
Y-cable protection is supported when the 10x10G-LC card is configured in MXP-10x10G operating
mode with 200G-CK-LC card and the 10x10G-LC card is provisioned with 10GE, OC-192/STM-
64 payloads. This configuration uses the ONS-SC+-10G-LR and ONS-SC+-10G-SR pluggables.

The cards have the following functions and features, explained in the Card Features, on page 805 chapter:
Jitter Considerations
281
Related Procedures for 100G-LC-C, 100G-ME-C, 100G-CK-C, 100ME-CKC, 10x10G-LC, CFP-LC, 100GS-CK-LC, 200G-CK-LC, and MR-MXP Cards
• Port level indicators
Related Procedures for 100G-LC-C, 100G-ME-C,

100G-CK-C, 100ME-CKC, 10x10G-LC, CFP-LC,
100GS-CK-LC, 200G-CK-LC, and MR-MXP Cards
NTP-G235 Provisioning an Operating Mode, on page 708
400G-XP-LC Card
The 400G-XP-LC card is a tunable DWDM trunk card that simplifies the integration and transport of 10 Gigabit
and 100 Gigabit Ethernet interfaces and services into enterprises and service provider optical networks. The card
is a double- slot unit that provides 400 Gbps of client and 400 Gbps of trunk capacity. The card supports six
QSFP+ based client ports that can be equipped with 4x 10 Gbps optics and four QSFP28 or QSFP+ based client
ports that can be equipped with 100 Gbps QSFP28 and 4x 10 Gbps QSFP+ optics. The card is capable of
aggregating client traffic to either of the two 200 Gbps coherent CFP2 trunk ports.
The 400G-XP-LC card supports the following client signals:
10 GE: The payload can be provisioned for the OPM_10x10G slice mode for any trunk configuration.
The cross-connect circuit bandwidth is ODU2e.
100 GE: The payload can be provisioned for the OPM_100G slice mode for any trunk configuration.
The cross-connect circuit bandwidth is ODU4.
OTU2: This payload is supported only on the QSFP-4X10G-MLR pluggable. The payload can be
provisioned for the OPM_10x10G slice mode for any trunk configuration. The cross-connect
circuit bandwidth is ODU2.
OTU2e: This payload is supported only on the QSFP-4X10G-MLR pluggable. The payload can be
provisioned for the OPM_10x10G slice mode for any trunk configuration. The cross-connect
circuit bandwidth is ODU2e.
OC192/STM64: This payload is supported only on the QSFP-4X10G-MLR pluggable. The payload can
be provisioned for the OPM_10x10G slice mode for any trunk configuration. The cross-connect circuit
bandwidth is ODU2.
OTU4: This payload is supported only on the ONS-QSFP28-LR4 pluggable. The payload can be
provisioned for the OPM_100G slice mode for any trunk configuration. The cross-connect
circuit bandwidth is ODU4.
282
Key Features
16G FC: This payload is supported only on the ONS-QC+-4X16FC-MM pluggable. A new operating mode,
OPM_6x16G_FC is introduced to support this payload on ports 1, 2, 3, 4, 5, and 6. This operating mode can
be provisioned on any slice, with trunk configuration set to M_100G and M_200G.
Note For any card mode except REGEN with slide mode as OPM-10x10G, you can configure a mix of 10G
payloads (OC192/STM64, OTU2, 10GE) on the same slice or client port with the exception of CDR ports
(7,8,9, and 10). On CDR ports, the first configured 10G lane would determine the configurable payloads for
the other three port lanes.
Note If a slice is configured using the OPM_10x10G slice mode, it can be used only for 10G circuit creation whereas
if a slice is configured using the OPM_100G slice mode, it can be used only for 100G circuit creation.
The 400G-XP-LC card is supported on Cisco ONS 15454 M2, Cisco ONS 15454 M6, and Cisco NCS 2015
platforms.
One 400G-XP-LC card can be installed in the Cisco ONS 15454 M2 DC chassis that is powered by 15454-
M2-DC or 15454-M2-DC–E. Three 400G-XP-LC cards can be installed in the Cisco ONS 15454 M6
chassis that is powered by 15454-M6-DC, 15454-M6-DC40, or 15454-M6-AC2 (180V AC to 264V AC).
Seven 400G-XP-LC cards can be installed in the Cisco NCS 2015 chassis that is powered by DC 2 + 2, DC
3 + 1, or AC 2 + 2 PSU.
The 400G-XP LC supports PSM. The switch time for all 10G payloads is less than 50 ms. The switch time
for 100G trunk rate is higher than the 200G.
Limitations
To achieve a switch time of less than 50 ms, the squelch mode should either be LF or AIS.
Switch time of less than 50 ms is not supported on client ports 7,8,9,10.
PSM in standalone mode is supported.
Note The maximum short term operating temperature of the Cisco ONS 15454 M2 shelf must not exceed 50
degrees when the 400G-XP-LC card is installed.
Note It is recommended to wait for two seconds after performing every TL1 operation.
For information on safety labels for the cards see the "Class 1M Laser Product Cards” section. For
more information about the 400G-XP-LC card, see http://www.cisco.com/c/en/us/products/collateral/
optical-networking/network-convergence-system-2000-series/datasheet-c78-736916.html.
Key Features
The 400G-XP-LC card supports the following key features:
283
Key Features
Operating Modes—The card can be configured in the MXP, OTNXC, and REGEN operating modes. The
cards can be equipped with pluggables for client and trunk ports, and offer a large variety of
configurations. When you configure the card, make sure that the following tasks are completed:
The trunk port PPMs must be preprovisioned before configuring the card operating mode.
The client payloads can be provisioned after configuring the operational mode on the card.
The table below details the configurations supported on the 400G-XP-LC card for the supported
card modes.
Table 109: Configuration Options for the 400G-XP-LC Card Modes
Configuration Options
Card configuration MXP OTNXC REGEN
Trunk None None None

configuration ( per
trunk) M_100G M_100G M_100G
M_200G M_200G M_200G
Slice configuration None None Slice configuration is not
supported
OPM_100G -
OPM_10x10G OPM_10x10G
OPM_6x16G_FC -
For more information about the trunk and slice configuration, see Slice Definition and Line Card
Configuration for 400G-XP-LC Card, on page 291.
Each trunk port functions as a muxponder instance has the following features:
The trunk port supports Analog Coherent Optical (ACO) CFP2 coherent pluggable.
Note Before removing the CFP2 pluggable from any of two trunk ports, ensure that
the relevant trunk port is set to the OOS (Out-of-service) state. Wait until the
trunk port LED turns off. Wait for a further 120 seconds before extracting the
CFP2 pluggable.
Configurable trunk capacity:

100 Gbps coherent DWDM transmission with quadrature phase shift keying (QPSK )modulation.
200 Gbps coherent DWDM transmission with 16-state quadrature amplitude modulation
(16-QAM) modulation.
Configurable trunk FEC: SD-FEC with 15% or 25% overhead.

Configurable differential/non-differential line encoding.
284
Key Features
Nyquist shaping if channels at trunk TX.

Flex spectrum tunability over the full extended C-Band.
100 Gbps through 100 Gbps QSFP28 client ports.
10 Gbps through 4x 10 Gbps QSFP+ client ports.
16 Gbps through 4 x 16 Gbps QSFP+ client ports.
The supported CD ranges are detailed in the table below:
Table 110: CD Range for 400G-XP-LC Card
200G 16-QAM 100G QPSK
Low High Low High
Default Working -10000 50000 -20000 90000

CD Range
Default CD -9000 45000 -18000 72000

Thresholds
Allowed CD Range -60000 60000 -280000 280000

Working and
Thresholds)
Loopback—The following loopback types are supported:

0 Client ports - Terminal (Inward), Facility (Line)
1 Trunk ports - Terminal (Inward)
2 Iports - Facility (Line), Terminal loopback (Drop)
Note Before you provision loopback on the iports, place the relevant trunk ports in the
OOS-MT state. This causes the iports to move to the OOS-MT state.
Automatic Laser Shutdown (ALS) can be configured on all the ports.

Provides encryption capability on the OTU4 (IPort) ports. This card provides confidentiality of the data,
which is sent over a fiber optic communication channel, using Next Generation Cryptography. To
provision encryption on the 400G-XP-LC card, see "NTP-G367 Provisioning Encryption on 400G-
XP-LC Card". The MXP operating mode supports the encryption feature. The 400G-XP-LC card does
not support Encryption as an Appliance.
100GE ethernet client ports can be provisioned with or without IEEE 802.3 bj FEC. The options are
Auto, Force-Fec-On, Force-Fec-Off.
Trail Trace Identifier (TTI)—TTI in the section monitoring overhead is supported . Source AccessPoint
Identifer (SAPI), Destination Access Point Identifer (DAPI), and User Operator Data fields are
supported in Release 10.6.2 and later releases.
285
Key Features
Trunk Port Interworking—The two CFP2 trunk ports can interoperate with each other when the source
and destination 400G-XP-LC cards have the same trunk mode and slice mode configuration. For more
information, see Trunk Port Interworking in 400G-XP-LC Cards, on page 295.
PRBS Support—The ODU4 internal ports can support configuration of PRBS with all operating modes
when the source and destination 400G-XP-LC cards have the same trunk mode. For more information,
see PRBS Support on the 400G-XP-LC Card, on page 299.
GCC0 Support—The 400G-XP-LC card supports provision of GCC0 channel on the trunk port. For
more information, see GCC0 Support on the 400G-XP-LC Card, on page 300.
OTN cross-connection support—For more information, see OTN Cross-connect Capability on
400G-XP-LC Cards, on page 287.
Interoperability—The 400G-XP-LC card is interoperable with the NC55-6X200-DWDM-S card
supported on NCS 5500 and the NCS4K-4H-OPW-QC2 Card supported on NCS 4000.
The following table describes the configurations, payload types and pluggables supported for
interoperability between the 400G-XP-LC card and the NCS4K-4H-OPW-QC2 card.
Table 111: 400G-XP-LC Interoperability with the NCS4K-4H-OPW-QC2 card.
Payload type Trunk Pluggables for Pluggables for Pluggables for Pluggables for
configuration trunk ports on client ports on trunk ports on client ports on
400G-XP-LC 400G-XP-LC 4H-OPW-QC2 4H-OPW-QC2
100GE OTU4 CFP2 QSFP-100G-SR4-S CFP2 QSFP-100G-SR4-S
100GE OTU4C2 CFP2 QSFP-100G-SR4-S CFP2 QSFP-100G-SR4-S
OTU2 OTU4 CFP2 ONS-QSFP-4X10 CFP2 ONS-QSFP28-LR4

MLR
OTU2 OTU4C2 CFP2 ONS-QSFP-4X10 CFP2 ONS-QSFP28-LR4

MLR
10GE OTU4 CFP2 ONS-QSFP-4X10 CFP2 ONS-QSFP-4X10

MLR MLR
10GE OTU4C2 CFP2 ONS-QSFP-4X10 CFP2 ONS-QSFP-4X10

MLR MLR
The following table describes the configurations, payload types and pluggables supported for
interoperability between the 400G-XP-LC card and the NC55-6X200-DWDM-S card.
Table 112: 400G-XP-LC Interoperability with the NC55-6X200-DWDM-S card.
Payload type Trunk Pluggables for Pluggables for Pluggables for Pluggables for
configuration trunk ports on client ports on trunk ports on client ports on
400G-XP-LC 400G-XP-LC 6X200-DWDM-S 6X200-DWDM-S
100GE OTU4 CFP2 QSFP-100G-SR4-S CFP2 QSFP-100G-SR4-S
100GE OTU4C2 CFP2 QSFP-100G-SR4-S CFP2 QSFP-100G-SR4-S
286
OTN Cross-connect Capability on 400G-XP-LC Cards

OTN Cross-connect Capability on 400G-XP-LC Cards

The 400G-XP-LC card supports a new OTN cross-connect (OTNXC) operating mode. You cannot edit the
trunk and slice mode after the 400G-XP-LC card is configured in OTNXC mode. This mode allows
ODU2e switching between client to trunk ports or trunk to trunk ports within a single 400G-XP-LC card
for 100G and 200G trunk rates. Both trunk ports are configured with the same rate (100G or 200G). Only
the 10GE client payloads are supported. Each 10GE is mapped to an ODU2e channel. Each 10G client port
of the 400G-XP-LC card consists of only one ODU2e and each OTU4C2 ( 200G) trunk port of the 400G-
XP-LC card consists of 20 ODU2es.
You can create 20xODU2e trunk-to-trunk cross-connections or up to 40x10GE client-to-trunk cross-
connections. Client-to-trunk cross-connections can be protected or unprotected. The card supports up to
20x10GE circuits with SNC-N 1+1 bidirectional protection.
The OTNXC card mode requires a new trunk FPGA image. The 400G-XP LC card should be running on
firmware (SCP) version 5.24 or above. A Condition message warns the user about availability of a new image.
To upgrade the FPGA image, see NTP-G362 Manual FPGA Upgrade on the 400G-XP-LC Card, on page 711.
You can create single card cross-connects or end-to-end cross-connects in an OTN ring. Before you
create an end-to-end ODU circuit, WSON OCH trails or SSON trails must be configured between the
nodes that help discover the topology.
OTNXC Constraints
The following constaints apply to ODU circuit creation between 400G-XP-LC cards configured in the
OTNXC mode.
Both trunk ports of the 400G-XP-LC card are configured with the same rate (100G or 200G)
Only 10GE payloads are supported on the client ports.
An ODU circuit cannot be created between two client ports of the 400G-XP-LC card.
Each client port belongs to one of the four card slices. Slice 1 and Slice 2 are linked to the first trunk
port and Slice 3 and Slice 4 are linked to the second trunk port. Cross-connecting between slices of the
same trunk is not allowed. The possible cross-connections that can be created are within the same
client slice or between the client slice and any of the other trunk slices.
There is a bandwidth limitation between the two internal ASICs of the 400G-XP-LC card due to which
a maximum of 20x10G interlink connections can be defined. These resources are consumed by either
trunk-to-trunk cross-connects or client-to-trunk cross-connects when the client does not belong to the
trunk slice.
Protected cross-connects are restricted to client ports 1,2,3,7, and 8 belonging to slices 1and 2.
Do not provision more than one path for non-protected circuits.
287
ODU Utilization Panes
ODU Utilization Panes

There are three utilization panes that display the ODU utilization for the 400G-XP-LC card at the card
level, network level, and cross-connect level. To view the ODU utilization, see NTP-G366 Viewing the
ODU Utilization for ODU Circuits, on page 712.
OTNXC Exceptions
The following exceptions apply to ODU circuits between 400G-XP-LC cards configured in the
OTNXC mode:
WSON OCH trail creation is allowed between the trunks ports of 400G-XP-LC cards configured in
different operating modes (MXP and OTNXC)
Downgrading WSON OCH trails to non-WSON OCH trails is allowed even though OTN circuits exist.
OCH trail deletion is allowed if though the trunk port has an ODU cross-connect passing through it.
Restoration and revert operations are allowed on an OCH trail when the 400G-XP-LC card is
configured in OTNXC mode.
If the circuit protection type is SNC-N, the circuit service state is OOS-PARTIAL (Locked-partial) if
the source or destination nodes have a fault on both the trunk ports causing the port service state to
change to OOS-AU,FLT (ANSI) or Unlocked-disabled,failed (ETSI)) or if three or more intermediate
nodes have the service state as FLT.
If the circuit protection type is None, the circuit service state is OOS-PARTIAL (Locked-partial) if
the source or intermediate nodes have the service state as FLT.
When the traffic is manually switched to the protect path in a protected revertive ODU circuit, the
WKSWPR alarm is raised on the node. The alarm may not persist after a control card reset.
Performing a database restore operation, may not clear the WKSWPR alarm.
Single card cross-connects may persist in CTC for some time even after the node is disconnected.
Interoperability
The 400G-XP-LC card has two trunk ports, each supporting up to 20 ODU2es. These ODU2es are
numbered from 1 through 20. ODU2es from 1 through 10 belong to the first ODU4 slice and ODU2es from
11 through 20 belong to the second ODU4 slice. Each ODU number has a pre-defined group of timeslots as
seen in the following table.
Trunk Port ODU4 Slice ODU Trunk ODU Trunk FAC Tributary Port Timeslots
Number Number
Trunk 1 Slice 1 1 96 1 1 11 21 31 41 51
61 71
(FAC 10)
2 97 2 2 12 22 32 42 52
62 72
288
Interoperability
Number Number
3 98 3 3 13 23 33 43 53
63 73
4 99 4 4 14 24 34 44 54
64 74
5 100 5 5 15 25 35 45 55
65 75
6 101 6 6 16 26 36 46 56
66 76
7 102 7 7 17 27 37 47 57
67 77
8 103 8 8 18 28 38 48 58
68 78
9 104 9 9 19 29 39 49 59
69 79
10 105 10 10 20 30 40 50
60 70 80
Slice 2 11 106 1 1 11 21 31 41 51
61 71
12 107 2 2 12 22 32 42 52
62 72
13 108 3 3 13 23 33 43 53
63 73
14 109 4 4 14 24 34 44 54
64 74
15 110 5 5 15 25 35 45 55
65 75
16 111 6 6 16 26 36 46 56
66 76
17 112 7 7 17 27 37 47 57
67 77
18 113 8 8 18 28 38 48 58
68 78
19 114 9 9 19 29 39 49 59
69 79
289
Interoperability
Number Number
20 115 10 10 20 30 40 50
60 70 80
Trunk 2 Slice 1 1 116 1 1 11 21 31 41 51

61 71
(FAC 11)
2 117 2 2 12 22 32 42 52
62 72
3 118 3 3 13 23 33 43 53
63 73
4 119 4 4 14 24 34 44 54
64 74
5 120 5 5 15 25 35 45 55
65 75
6 121 6 6 16 26 36 46 56
66 76
7 122 7 7 17 27 37 47 57
67 77
8 123 8 8 18 28 38 48 58
68 78
9 124 9 9 19 29 39 49 59
69 79
10 125 10 10 20 30 40 50
60 70 80
Slice 2 11 126 1 1 11 21 31 41 51
61 71
12 127 2 2 12 22 32 42 52
62 72
13 128 3 3 13 23 33 43 53
63 73
14 129 4 4 14 24 34 44 54
64 74
15 130 5 5 15 25 35 45 55
65 75
16 131 6 6 16 26 36 46 56
66 76
290
Regeneration Mode for 400G-XP LC
Number Number
17 132 7 7 17 27 37 47 57
67 77
18 133 8 8 18 28 38 48 58
68 78
19 134 9 9 19 29 39 49 59
69 79
20 135 10 10 20 30 40 50
60 70 80
When the 400G-XP-LC card interoperates with NCS4K-4H-OPW-QC2 card, the first ODU4 slice of the
400G-XP-LC trunk is connected to the second ODU4 slice of the same NCS4K-4H-OPW-QC2 trunk.
Regeneration Mode for 400G-XP LC

From Release 10.8.0, the 400G-XP LC can be configured as a regenerator. The regeneration functionality is
available only on the trunk ports. A new card operating mode, REGEN, is available. No client ports are
involved. The two trunk ports must have the same rate to achieve regeneration (wavelengths and FEC of
the trunks can vary).
Note For traffic to flow in the REGEN mode, it is mandatory that the 400G-XP LC should be running on
firmware (SCP) version 5.24 or above.
It is recommended to use the REGEN mode only with the MXP operating mode (the output from the
MXP trunk of a 400G-XP LC can be connected to trunk ports in REGEN mode).
Slice Definition and Line Card Configuration for 400G-XP-LC Card

The image below displays the client and trunk ports of the 400G-XP-LC card.
291
Figure 39: 400G-XP-LC Card
The client to trunk port mapping is fixed in the 400G-XP-LC card as detailed in the table below.
Table 113: Trunk -Client Port Mapping on the 400G-XP-LC Card
Trunk Client Port Pluggable Type
Trunk 1 (CFP2-11)- Slice 1 and Ports 1, 2, 3 QSFP+

Slice 2 7
Ports 7, 8 QSFP+ or QSFP28
Trunk 2 (CFP2-12) - Slice 3 and Ports 4, 5, 6 QSFP+

Slice 4
Ports 9, 10 QSFP+ or QSFP28
QSFP+ and QSFP28 share the same form factor.
The trunk ports can be configured with either 100G or 200G rate. The client ports are grouped into four slices.
The slice mode defines the aggregation capacity and can be configured independently.
The configuration of each of the two trunk ports is independent and is done using either one of the two
trunk operating modes.
Trunk Operating Modes (trunk capacity)
M-100G: 100G QPSK . One slice is enabled on the trunk. Slice 2 is enabled for Trunk 1 and Slice 4 is
enabled on Trunk 2.
292
• M-200G: 200G 16 QAM. Two slices are enabled on the trunk.
From Release 10.6.2, the NCS2K-400G-XP linecard supports the 16G fiber channel payload. This new
payload is supported only on the ONS-QC-16GFC-SW= pluggable. The supported payload mapping is
CBR, with encoding 64b or 66b.
Note The maximum transmit launch power (per lane) of the ONS-QC-16GFC-SW= pluggable is +1dBm (the
lowest transmit launch power is -7.6dBm).
To support the 16G FC payload, a new operating mode, OPM_6x16G_FC is introduced. This operating
mode can be provisioned on any MXP card configuration slice, with M_100G and M_200G trunk ports.
The OPM_6x16G_FC can also be provisioned with any other another slice opmode in the card.
The OPM_6X16G_FC shall enable 16G-FC clients on ports 1, 2, 3, 4, 5 and 6. The client ports 2 and 5 (shared
between 2 slices) cannot support different payload bit-rates. This means that in case of contextual provisioning of
OPM_6x16G_FC and OPM_10x10G on slices 1 and 2 or slices 3 and 4 , the available options are:
provision a ONS-QC-16GFC-SW= pluggable on the shared ports and have 6x 16G-FC payloads and 8x
10G payloads (10GE or OTU2)
provision a QSFP-4X10G-MLR (or ONS-QSFP-4X10G-LR-S) pluggable on the shared ports and have
4x 16G-FC + 10x 10G payloads (10GE and/or OTU2)
Slice Mode:
OPM-100G: Enables 100G client on the QSFP 28 port.
OPM-10x10G: Enables 10G client over a set of QSFP+ ports.
OPM-6x16G_FC: Enables 16G client over a set of QSFP+ ports.
Traffic from the client ports are aggregated on the 100G or 200G trunk at the intermediate ports. There
are four intermediate ports (iports) , two per trunk. The iports are automatically configured when the
slices are configured.
The relation between the two trunk ports ( Ports 11 and 12) , client ports (Ports 1 through 10) and the
four slices are represented in the tables below.
Table 114: Trunk, Slice, and Port Configuration for Trunk 1 of the 400G-XP-LC Card
Trunk 1 Client Ports
Trunk Slice Operation Mode 1 28 3 7 8

Mode
Slice 1 Slice 2 Port Lanes
293
9
M-200GOPM-100G OPM-100G - - - 4x 4x
OPM-100G OPM-10x10G - 3,4 1 to 4 4x 1 to 4
OPM-10x10G OPM-100G 1 to 4 1, 2 - 1 to 4 4x
OPM-10x10G OPM-10x10G 1 to 4 1 to 4 1 to 4 1 to 4 1 to 4
OPM-6x16G_FC OPM-100G 1 to 4 1,2 4x

10
OPM-6x16G_FC OPM-10x10G 1 to 4 1,2 or 3,4 1 to 4 1 to 4
OPM-100G OPM-6x16G_FC - 3,4 1 to 4 4x

11
OPM-10x10G OPM-6x16G 1 to 4 1,2 or 3,4 1 to 4 1 to 4
OPM-6x16G OPM-6x16G_FC 1 to 4 1,2 and 3,4 1 to 4
M-100GNA OPM-100G - - 4x
OPM-10x10G 3,4 1 to 4 1 to 4
OPM-6x16G_FC 3,4 1 to 4
Port 2 is shared between Slice 1 and Slice 2
4x refers to all four lanes of the QSFP28 pluggable
Depending on the PPM provisioned, ports 1,2 can be 16G FC or ports 3,4 can be 10GE/OTU2.
Table 115: Trunk, Slice, and Port Configuration for Trunk 2 of the 400G-XP-LC Card
Trunk 2 Client Ports
Trunk Slice Operation Mode 4 5 6 9 10

Mode 12
Slice 3 Slice 4 Port Lanes
M-200G OPM-100G OPM-100G - - - 4x 4x
OPM-100G OPM-10x10G - 3,4 1 to 4 4x 1 to 4
OPM-10x10G OPM-100G 1 to 4 1, 2 - 1 to 4 4x
OPM-10x10G OPM-10x10G 1 to 4 1 to 4 1 to 4 1 to 4 1 to 4
OPM-6x16G_FC OPM-100G 1 to 4 1,2 - - 4x

13
OPM-6x16G_FC OPM-10x10G 1 to 4 1,2 or 3,4 1 to 4 - 1 to 4
OPM-100G OPM-6x16G_FC - 3,4 1 to 4 4x -

14
OPM-10x10G OPM-6x16G_FC 1 to 4 1,2 or 3,4 1 to 4 1 to 4 -
OPM-6x16G_FC OPM-6x16G_FC 1 to 4 1,2 and 3,4 1 to 4 1 to 4 -
294
Trunk Port Interworking in 400G-XP-LC Cards
M-100GNA OPM-100G - - - - 1 to 4
OPM-10x10G 3,4 1 to 4 1 to 4
3,4 1 to 4
Port 5 is shared between Slice 3 and Slice 4

To provide greater flexibility on the network design and deployment, the two CFP2 trunk ports of the
400G-XP-LC card can interoperate with each other when the same trunk operating mode and slice
configurations exist on both source and destination cards.
OCHCC circuits can be created between compatible client ports as detailed in the tables below.
Table 116: Compatible Client Ports for M-100G Trunk Port Configuration
Trunk 1 - CFP2 Port 11 Source/Destination Source/Destination Trunk 2 - CFP2 Port 12

Client Ports Client Ports
Slice Slice 2: 8 10 Slice 4: Slice

configuration 1 OPM_100G OPM_100G configuration 1
Slice Slice 2: 2-3 5-3 Slice 4: Slice

configuration 2 OPM_10x10G OPM_10x10G configuration 2
2-4 5-4
3-1 6-1
3-2 6-2
3-3 6-3
3-4 6-4
8-1 10-1
8-2 10-2
8-3 10-3
8-4 10-4
295


configuration 2 OPM_6x16G_FC OPM_6x16G_FC configuration 2
2-4 5-4
3-1 6-1
3-2 6-2
3-3 6-3
3-4 6-4
Table 117: Compatible Client Ports for M-200G Trunk Port Configuration

Slice Slice1: 7 9 Slice 3: Slice

configuration 1 OPM_100G OPM_100G configuration 1
Slice 2: 8 10 Slice 4:
OPM_100G OPM_100G
OPM_100G OPM_100G
2-4 5-4
3-1 6-1
3-2 6-2
3-3 6-3
3-4 6-4
8-1 10-1
8-2 10-2
8-3 10-3
8-4 10-4
296


1-2 4-2
1-3 4-3
1-4 4-4
2-1 5-1
2-2 5-2
7-1 9-1
7-2 9-2
7-3 9-3
7-4 9-4
OPM_100G OPM_100G
297


1-2 4-2
1-3 4-3
1-4 4-4
2-1 5-1
2-2 5-2
7-1 9-1
7-2 9-2
7-3 9-3
7-4 9-4
Slice 2: 2-3 5-3 Slice 4:
OPM_10x10G OPM_10x10G
2-4 5-4
3-1 6-1
3-2 6-2
3-3 6-3
3-4 6-4
8-1 10-1
8-2 10-2
8-3 10-3
8-4 10-4
Slice Slice 1-1 4-1 Slice 3: Slice
configuration 1 1:OPM_6x16G_FC OPM_6x16G_FC configuration 3
1-2 4-2
1-3 4-3
1-4 4-4
2-1 5-1
2-2 5-2
298
PRBS Support on the 400G-XP-LC Card


configuration 2 OPM_6x16G_FC OPM_6x16G_FC configuration 4
2-4 5-4
3-1 6-1
3-2 6-2
3-3 6-3
3-4 6-4
PRBS Support on the 400G-XP-LC Card

The ODU4 internal ports on the 400G-XP-LC card support configuration of PRBS with all operating modes.
Before you begin

Pseudo Random Binary Sequence (PRBS) feature allows users to perform data integrity checks on their
encapsulated packet data payloads using a pseudo-random bit stream pattern. PRBS generates a bit
pattern and sends it to the peer router that uses this feature to detect if the sent bit pattern is intact or not.
Procedure
Step 1 In the node view, double-click the card where you want to provision PRBS. The card view appears.
Step 2 Set the admin state to OOS, MT for the source and destination trunk ports. Which in turn puts
corresponding IPorts in OOS, MT state.
Note The PRBS configuration supports the 400G-XP-LC card only when the port is in Maintenance
State. In case the port is in In-Service or Out-of-Service, PRBS is disabled.
Step 3 Click the Maintenance > PRBS Configuration tabs.

Step 4 From the Pattern drop-down list, choose a pattern.The supported patterns are None, PRBS_11, and PRBS_31.
Note Same pattern should be applied in both source and destination trunk ports. Same pattern should be
applied in both source and destination IPorts.
Step 5 Click Apply.

The 400G-XP-LC card provides a PRBS sync status with the following values:
PATTERN_OK: When the Internal Port is receiving one of the recognized patterns.
PATTERN_ERROR: When the Internal Port is receiving a recognized pattern but the pattern contains
errors. This also occurs when there is a pattern mismatch.
PATTERN_NONE: When the Internal Port is not receiving a recognized PRBS pattern.
299
Limitations of PRBS Support on 400G-XP-LC card
Note Click Refresh in the PRBS window under Maintenance to check the pattern sync status on the
internal ports.
In case of pattern errors, the card provides a PRBS error counter. The counter zeroes itself when the
PRBS is disabled.
Limitations of PRBS Support on 400G-XP-LC card

PRBS cannot be enabled on Internal Ports (IPorts) if corresponding client payloads are not provisioned.
Client payloads cannot be provisioned if PRBS is enabled on the corresponding Internal Ports(IPorts).
CPRBS pattern shows OK even with mismatch configuration if no cross connections or clients are
created.
GCC0 Support on the 400G-XP-LC Card

The 400G-XP-LC card supports provision of one GCC0 channel for each of the trunk ports on the
operating modes-OTNXC, MXP, and MXP-2x150G(8QAM).
In case of OTU4C3 (8QAM) payload, only one GCC0 channel is configurable on the first trunk port
(Port-11). The configuration on the second trunk port (Port-12) is automatically blocked.
In case of MXP-2x150G(8QAM) payload, the GCC0 channel is configurable only on the second trunk
port (Port-12), no GCC0 channel configuration is supported on the first trunk port (Port-11).
The OTU4 and OTU2 client ports do not support GCC0 channels on the card.
The 400G-XP-LC card supports a maximum of two GCC0 channels on each trunk port.
The OTU4C2 trunk port supports the Low Speed GCC 196K and High Speed GCC 1200K. The 400G-
XP card supports only High Speed GCC rate, 1200K. So, GCC0 channels provisioning on 400G-XP
cards which are part of 15454-M12 as Node Controller (NC) configurations is not supported.
The OTNXC or OCHTRAIL circuits are not supported over the direct GCC0 link on the 400G-XP-LC
card.
The GCC0 channel provisioning is not supported on REGEN card mode on the 400G-XP-LC card.
However, GCC0 tunneling is enabled.
The Field-Programmable Gate Array (FPGA) should be upgraded to the latest version before creating a
GCC0 circuit on the 400G-XP-LC card trunk ports. The CTC throws an error message during the
circuit creation if FPGA version is outdated.
GCC0 channels provisioning is supported with hardware FPGA image version > 0.28. GCC
provisioning will fail with a deny error message if FPGA version is = < 0.28.
Hardware FPGA image version information is available under CTC > Card View > Maintenance >
Info Tab > FPGA_HW_VERSION.
Hardware FPGA image version information will be available under CTC > Card view > Maintenance
> Info tab > PGA_HW_VERSION.
FPGA image upgrade is traffic impacting and, should be done in a maintenance window.
300
2x150G Support on the 400G-XP-LC Card
To Upgrade FPGA Image, go to CTC > Card View > Provisioning > Card tab and, click on the
FPGA or FIRMWARE UPGRADE button and follow the auto generated instruction.
2x150G Support on the 400G-XP-LC Card

From Release 10.9, the 400G-XP-LC card supports the configuration of 2x150G mode in 8QAM modulation
format. It is configurable on the trunk ports of the card by selecting M_150G as the Trunk Operating mode.
The M_150G mode does not support muxponder, cross connection, and regeneration configurations.
The M_150G trunk mode configuration supports client slices 1, 3 and 4. The available ports 1[1:4], 2[1:2],
4[1:4], 5[1:4], 6[1:4], 7[1:4], 9[1:4], 10[1:4]. When the M_150G trunk mode in configured, the slices 1, 3
and 4 are independently configurable as OPM_100G, OPM_10x10G or OPM_6x16G-FC. It is possible to
change a slice mode without it being traffic affecting on the other provisioned slices. The admin state of
both the trunk ports are aligned.
On a M_150G configured trunk mode, all client payloads or options are the same as the standard
M_200G MXP mode.
The M_150G trunk mode is applicable to both trunk ports. This is required since this mode splits the
ODU4line frames into two interleaved 150G signals transported separately by the two trunk ports.
The trunk ports configured as M_150G support the same optical and FEC alarms/Monitors provided by the
M_200G mode. An LOS-P or LOF alarm on any of the two trunk ports of M_150G correlates all the
OTU4C3 container OTN alarms.
The Line OTN Alarms and Performance Monitors of the 2x150G mode container frame (OTU4C3) is
evaluated as the summarization of the Alarms or PMs related to the 3 embedded ODU4 internal ports 1, 3
& 4. The resulting values are available at the OTN layer of Trunk12.
Limitations of 2x150G Support on the 400G-XP-LC Card

The trunk ports are put in Out-of-Service state before unplugging any CFP2 trunk. Extracting an In-
Service CFP2 trunk results in shutting down of the other trunk.
The loopback setting of both the M_150G trunks are aligned. However, the internal loopback ports are
configurable independently with the same limitations as that of M_100G and the M_200G modes.
The TTI-SM of the OTU4C3 container is configurable and is monitored only on Trunk 12.
The GCC0 provisioning is supported only for Trunk-12.
The FEC setting of both the M_150G trunks are aligned.
Related Procedures for 400G-XP-LC Cards

NTP-G361 Provisioning an Operating Mode on the 400G-XP-LC Card, on page 709
NTP-G362 Manual FPGA Upgrade on the 400G-XP-LC Card, on page 711
301
Supported MSM Configurations
PRBS Support on the 400G-XP-LC Card, on page 299
Supported MSM Configurations

The following configurations are supported :
Configuration Card Configuration Payload Total Client Interfaces
1 40 400G-XP-LC cards 10 GE 1600
2 20 400G-XP-LC cards 10 GE 1520

36 200G-CK-LC cards
72 MR-MXP cards
3 70 400G-XP-LC cards 100 GE 280
4 20 400G-XP-LC cards 100 GE 800
36 200G-CK-LC cards 10 GE
72 MR-MXP cards
Recommendations
Ensure you follow the recommendations stated below for optimum system performance.
Five CTC sessions can run concurrently.
Only one TL1 session can run at a time when TL1 scripts are run continuously for monitoring on a node.
Only one OTDR scan can be run at a time.

Only one EPNM session can run at a time.
Two SNMP traps can be configured.
Performing software downloads, database backup, and database restore operations must not be
performed when the system is synchronizing with EPNM or when TL1 sessions are running.
Software upgrade must not be run with the recommended environment (five CTC sessions, one OTDR
scan, one TL1 session, one EPNM session, and two SNMP traps) enabled as it impacts the upgrade
operation.
The following operations may cause degradation of system performance:
Retrieving performance monitoring values using HTTP in a browser.
Performing a full SNMP walk.
Running parallel sessions of EPNM and TL1.
302
WSE Card
WSE Card
The Wire Speed Encryption (WSE) card is an optical line card that provides encryption capability, at the OTN
layer, to the Cisco ONS 15454 M2 and Cisco ONS 15454 M6 platforms. This card provides confidentiality of the
data, which is sent over a fiber optic communication channel, using Next Generation Cryptography. In addition
to providing encryption, this card also provides integrated transponder functionality.
The WSE card supports these client signals:
10GE LAN PHY mapped to OTU2e
OTU2
OTU2e
OTU1e
OC-192/STM-64
10GE WAN
10GE LAN mapped to OTU2
8G FC/10G FC
The WSE card does not support auto negotiation for SAN protocols (10GFC/8GFC). The WSE card
supports only speed lock for SAN protocols.
The WSE card is tunable on 96 wavelength channels, spaced at 50-GHz over the entire C-band. The digital
wrapper function (ITU-T G.709 compliant) formats the DWDM wavelength so that it can be used to set up
GCCs for data communications, enable FEC, or facilitate PM. The WSE card works with the OTN devices
defined in ITU-T G.709. The OTN client can be FEC, standard G.975 FEC, or disabled FEC.
For information on safety labels for the cards, see the "Class 1M Laser Product Cards” section.
Caution A 15 to 20 dB fiber attenuator must be used when working with the cards in a loopback on the trunk port.
Do not use direct fiber loopbacks with the cards. Using direct fiber loopbacks causes irreparable damage to
the DWDM/CWDM XFP/SFPs plugged in WSE card.
The WSE card is a single-slot card and can be installed in any service slots in the chassis. The card has 10
SFP+ ports. The trunk and client ports are fixed. The trunk ports are 2, 4, 6, 8, and 10; the client ports are
1, 3, 5, 7, and 9. The trunk SFP+ can be grey or DWDM. The trunks include FEC and EFEC for longer
reach. Depending on the traffic pattern, the WSE card provides per port flexibility.
Up to six WSE cards can be installed per Cisco ONS 15454 M6 shelf assembly, supporting up to 30
encrypted streams in a 2-rack unit (RU) bay frame. Up to two WSE cards can be installed per Cisco ONS
15454 M2 shelf assembly, supporting up to 10 encrypted streams in a 6-rack unit (RU) bay frame. It is
possible to aggregate the wavelength required with 40G and 100G cards in the same chassis. Up to 15 WSE
cards can be installed per Cisco NCS 2015 shelf assembly.
When the software version of the node is changed from Release 10.6.2 to releases prior to 10.6.1, the WSE
card undergoes a hard reset. This is applicable for the ONS 15454, 15454 M2, 15454 M6 chassis.
When the node is upgraded followed by reset of the active control card, FPGA upgrade of the WSE card fails.
303
Key Features
Perform the following steps to upgrade FPGA successfully.

Soft reset the WSE card.
Click FPGA/FIRMWARE Upgrade/Traffic Affecting Reset to upgrade FPGA.
Key Features
The WSE card supports these key features:
Operating Modes—The WSE card can be configured into multiple operating modes. The card can be
equipped with pluggables for client and trunk options, and offers a large variety of configurations.
For more information about multiple operating modes, see Multiple Operating Modes.
Security Features
Secure Boot—This feature does a boot verification in hardware. It ensures that only authentic
Cisco software boots up on the Cisco platform, and provides tamper and cloning resistance.
Digital Image Signing—After the secure boot, the Digital Image Signing ensures that the software
that runs on Cisco devices is authentic. This maintains the integrity of the image that is loaded on
the WSE card.
Key Exchange—Key exchange between authenticated peer cards happens over the GCC2 channel
that is secured using Transport Layer Security (TLS). The Elliptic Curve Diffie Hellman
Ephemeral (ECDHE) algorithm is used for key exchange.
Confidentiality of Data—The WSE card protects against ciphertext manipulation and cut-and-paste
attempts. AES algorithm in XTS mode of operation.
Role Based Access Control—Access control is enforced to ensure that there is complete separation
in managing the transport (provisioning) and the security functionalities. As a result, depending
on the role assigned to a user, only certain operations can be performed by that user.
Card Authentication—The Secure Unique Device Identification (SUDI) certificate that is formatted as
an X.509 certificate and conforms to the IEEE 802.1 AR standard. It is signed using Cisco's Root
Certificate Authority. This certificate carries a unique identifier used to authenticate the peer card as
being a WSE card before the data is exchanged. Information cannot be exchanged with a card that is
not authenticated.
High Speed GCCs—The WSE card supports the provisioning of GCC channel on OTN (OTU2/OTU2e)
enabled client and trunk ports. A maximum of ten GCC0 channels can be created per WSE card, on
Cisco ONS 15454 M2 or Cisco ONS 15454 M6, or Cisco NCS 2015 shelf, and a maximum of five
GCC2 channels can be created per WSE card, on Cisco ONS 15454 M2 or Cisco ONS 15454 M6, or
Cisco NCS 2015 shelf.
OCH-trail Protection—Provides protection for the DWDM signals through external optical switch units
(Protection Switch Module [PSM]).
Licensing—A licensed version of the card provides a cost-effective solution for customers who do not need
to encrypt data on all five streams from day one itself. The licensed WSE card provides single stream
encryption as a base functionality. When an additional encrypted stream is required, you need to purchase a
software ugrade license. Licensing is required for only security features. A WSE card without
304
WSE Workflow Diagram
a license acts as for transponder. For more information on licensing, see the Licensing
Configuration Guide.
Third Party Certificates—The WSE card supports the generation of a Certificate Signing Request (CSR)
and installation of Locally Significant Certificates (LSCs) that can be used to authenticate the peer
card connection.
For information on safety labels for the cards, see the "Class 1M Laser Product Cards” section.
WSE Workflow Diagram

The following figure shows the workflow diagram of the WSE card. The diagram provides information
on the tasks required to configure the WSE card.
305

A single WSE card can be configured into multiple operating modes. The criteria for selecting a particular
operating mode are defined by the network level design. CTP helps you to choose the appropriate
operating mode. When you configure the WSE card into multiple operating modes, make sure that these
tasks are completed:
The PPMs must be configured on the card, and then the operating modes. None of the modes are
provisioned on the card by default. All operating modes are created on a per port basis. This is card-
specific provisioning, which decides the behavior of a particular card.
Depending on the card mode selected, the supported payload for that particular card mode must be
provisioned on the PPMs.
The WSE card supports these operating modes:

TXP-10G
RGN-10G
A mix of TXP-10G and RGN-10G modes can be configured on the WSE card.
TXP-10G
A maximum of five TXP-10G configurations can be provisioned on a single WSE card. When the card
is configured in this mode, these features are supported:
Enable or disable card authentication
Enable or disable payload encryption
OTN cannot be disabled on the trunk port.
Table 118: Supported Payload Mapping in TXP-10G Mode
Client Payload Trunk Mapping
10GE LAN PHY-CBR OTU2e
OTU2 OTU2
OTU2e OTU2e
8G FC OTU2
10G FC OTU2
10GE LAN PHY-GFP OTU2
OTU1e OTU1e
306
RGN-10G
RGN-10G
In the RGN-10G mode, the card behaves as a standard regenerator with DWDM SFP+ on both the client and
trunk ports. The card supports OTU1e, OTU2, and OTU2e regeneration on all the client and trunk pairs. When
the WSE card is configured in this mode, card authentication and payload encryption features are not supported.
The OTN cannot be disabled when the card is configured in RGN-10G mode.
Card Authentication
The WSE cards provide TLS 1.2 based card-to-card authentication per port. An authentication failure on
one trunk port does not affect the traffic on any other trunk port. The card authentication must be enabled to
configure encryption on the card.
Cisco Signed certificates are installed on the WSE card by default. These certificates are exchanged
between the cards during card authentication.
All ports are re-authenticated upon a soft-reset of the card.
In case of TLS or SSL authentication failure, the KEY_EX_FAIL alarm is raised on the particular trunk port.
Key Management
A single key, called a master key, is exchanged for each TLS session. It is exchanged using an asymmetric
key algorithm (Elliptic Curve Diffie Hellman). The master key is used to derive a set of symmetric keys
for payload encryption.
The user can change the master key at anytime from CTC, which initiates another DH exchange between
the sender and the receiver. The user can also specify the time when the master key is periodically reset.
The keys used for encryption of data are never stored in plaintext on the card. All keys are deleted when
the card reboots or is removed from the chassis. The key changes do not affect the traffic.
Important Notes on KEY-EX-FAIL Alarm

After an upgrade of a software version, KEY-EX-FAIL alarm may be raised due to soft reset of the
card. However, the traffic is not impacted, and the alarm will be cleared in the next exchange interval
of the master key
When the MANRESET alarm (Manual System Reset alarm) is cleared on a client WSE card, the KEY-
EX-FAIL alarm might be raised due to soft reset of the card. The alarm is raised when the server exits
the existing connection and establishes a new connection during this period. However, the traffic is
not impacted.
Payload Encryption
The payload on each port can be encrypted independent of the other streams. NIST approved Advanced
Encryption Standard (AES) AES-256, a symmetric key cryptographic algorithm in XTS mode of operation,
is used to encrypt the OTN payload. The payload encryption needs to be enabled at both source and
destination trunk ports; otheriwse, it is traffic affecting.
307
AES Secure Packet
AES Secure Packet

The concept of a packet does not exist within OTN; however, packet-based traffic is necessary for
encryption using XTS-AES algorithm. A single OTN frame cannot be tagged with the necessary
Encapsulating Security Payload (ESP) header, which carry the information necessary for encryption and
decryption of payloads. The ESP header and trailer require a total of 32 bytes within the OTN overhead.
The AES secure packet for each port can be made up of four or eight OTN frames. In CTC, the user
can choose from these two options for transporting the ESP header and trailer:
Four OTN frame based AES secure packet—The four OTN frame-based AES secure packet transports
four ESP header and four ESP trailer bytes within each OTN frame. In the four OTN frame-based AES
secure packet, eight overhead bytes are utilized in each OTN frame in order to transport all 32 bytes of
ESP header and trailer within a single AES secure packet. Each location is four bytes wide, therefore
two locations from each OTN frame are utilized, one for the ESP header and one for the ESP trailer.
Eight OTN frame based AES secure packet— The eight OTN frame-based AES secure packet
transports two ESP header and two ESP trailer bytes within each OTN frame. In the eight OTN frame-
based AES secure packet, four overhead bytes are utilized in each OTN frame in order to transport all
32 bytes of ESP header and trailer within a single AES secure packet. Each location is four bytes wide;
therefore, only one location from each OTN is utilized. Within the selected location, two bytes are
used for the ESP header, and two bytes for the ESP trailer.
Pseudo Random Binary Sequence (PRBS) testing is used to ensure that the selected overhead bytes can
be used to transport the ESP header and trailer safely. Both the transmitting node and receiving node must
be aware that PRBS testing is taking place. Each node must also know which bytes are to be tested.

The cards have the following functions and features, explained in the "Card Features" chapter:
Scenarios that Affect Traffic

Scenario 1: Traffic in a Stacked Topology
Consider an example where the WSE cards are connected in a stacked topology:
Client:WSE1:Trunk===Trunk:WSE2:Client===Client:WSE3:Trunk===Trunk:WSE4:Client
where WSE:Trunk represents OTU2e payload and WSE:Client represents 10GE signal.
In this scenario, card-to-card authentication and payload encryption are enabled on all the trunk ports, and
loopback is not configured. In this stacked topology, the WSE2 and WSE3 client will report a
synchronization loss since the keys are different, and an ODUk-AIS is raised on the trunk ports. The key is
not exchanged between WSE1 and WSE2 cards, and WSE 3 and WSE4 cards. This creates a deadlock and
the traffic does not recover.
308
Related Procedures for WSE Card
Scenario 2: Traffic in a Far-end and Near-end Client Loopback

Consider an example where loopback is configured on the WSE cards:
TS(10GE): near-end WSE1(client):(trunk)=== far-end WSE2(trunk):(client loopback)
where the trunk represents OTU2e payload and client represents 10GE signal.
In WSE card, do not enable encryption with far-end or near-end client loopback as this results in
synchronization loss at the client, and an ODUk-AIS is raised on the trunk port. The key is exchanged only
after the ODUk-AIS on the trunk is cleared. This forms a deadlock and the traffic does not recover.
Scenario 3: Traffic After Enabling PRBS Ingress and Egress

In a scenario when WSE cards are connected in a point-to-point setup:
10GE(client)===OTU2e(trunk)----OTU2e(trunk)===10GE(client-loopback)
When PRBS Ingress and Egress are enabled at both ends of the setup, the traffic will go down. When
PRBS Ingress and Egress are enabled at both ends of the setup, the traffic will go down.
Note When software version is downgraded to a previous version, the traffic may be affected with frame loss and
BIP errors.
Related Procedures for WSE Card

NTP-G338 Provisioning an Operating Mode on the WSE Card, on page 767
NTP-G339 Modifying the WSE Card Line Settings and PM Parameter Thresholds, on page 768
NTP-G340 Provisioning Encryption on the WSE and MR-MXP Cards, on page 784
NTP-G342 Provisioning FIPS and CC Mode, on page 793
DLP-G803 Installing Locally Significant Certificates on Cards, on page 797
MLSE UT
The maximum likelihood sequence estimation (MLSE) based universal transponder (UT) modules are
added to the TXP_MR_10EX_C, MXP_2.5G_10EX_C, and MXP_MR_10DMEX_C cards to support the
error decorrelator functionality to enhance system performance.
Error Decorrelator
The MLSE feature uses the error decorrelator functionality to reduce the chromatic dispersion (CD) and
polarization mode dispersion (PMD), thereby extending the transmission range on the trunk interface. You
can enable or disable the error decorrelator functionality using CTC or TL1. The dispersion compensation
unit (DCU) is also used to reduce CD and PMD. The MLSE-based UT module helps to reduce CD and
PMD without the use of a DCU.
309
SFP, SFP+, QSFP+, XFP, CXP, CFP, CFP2 and CPAK Modules
SFP, SFP+, QSFP+, XFP, CXP, CFP, CFP2 and CPAK Modules
Small Form-factor Pluggable (SFP), Enhanced Small-Form-factor Pluggable (SFP+), Quad Small-Form-factor
Pluggable Plus (QSFP+), 10-Gbps SFP (XFP), CXP, and C Form-factor pluggable (CFP and CPAK) modules are
integrated fiber optic transceivers that provide high-speed serial links from a port or slot to the network. For more
information on SFP, SFP+, QSFP+, XFP, CXP, CFP, CFP2 and CPAK modules and for a list of SFP, SFP+,
XFP, CXP, CFP, CFP2 and CPAK modules supported by the transponder and muxponder cards, see the
Installing the GBIC, SFP, SFP+, XFP, CXP, CFP, and CFP2 Optical Modules in Cisco ONS Platforms.
In CTC, SFP, SFP+, QSFP+, XFP, CXP, CFP, CFP2 and CPAK modules are called pluggable port
modules (PPMs). To provision SFP, SFP+, QSFP+, XFP, CXP, CFP, CFP2 or CPAK module and change
the line rate for multirate PPMs, see the DLP-G726 Preprovisioning a Multirate PPM task.
NTP-G128 Managing Pluggable Port Modules

Purpose Complete this procedure to provision a multirate PPM,
provision the optical line rate of a multirate PPM, or
delete a single-rate or multirate PPM.
Prerequisite Procedures • DLP-G723 Install PPM on a Line Card

• DLP-G46 Log into CTC
Note If a single-rate PPM is installed, the PPM screen will autoprovision and no further steps are necessary.
Note When you autoprovision a PPM, initial alarm and TCA defaults are supplied by Cisco Transport Controller
(CTC) depending on your port and rate selections and the type of PPM. These default values can be
changed after you install the PPM.
310
NTP-G128 Managing Pluggable Port Modules
Note The hardware device that plugs into a TXP, MXP, AR_MXP, AR_XP, AR_XPE, 100G-LC-C, 10x10G-LC,
CFP-LC, 100G-CK-C, 100G-ME-C, 100GS-CK-LC, 200G-CK-LC, 400G-XP-LC, 100ME-CKC, WSE,
GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, ADM-10G, or OTU2_XP card faceplate to provide a fiber
interface to the card is called a Small Form-factor Pluggable (SFP, SFP+, XFP, or CXP) or C Form-factor
pluggable (CFP, CFP2). In CTC, SFPs, XFPs, CXPs, and CFPs are called pluggable port modules (PPMs).
SFPs/XFPs/CXPs/CFPs/CFP2s are hot-swappable I/O devices that plug into a port to link the port with the
fiber-optic network. Multirate PPMs have provisionable port rates and payloads. For more information
about SFP, SFP+, QSFP+, XFP, CXP, CFP, CFP2 and CPAK Modules, on page 310.
Procedure
Step 1 Click the Alarms tab:

Verify that the alarm filter is not turned on. See the "DLP-G128 Disable Alarm Filtering" as necessary.
Verify that no unexplained conditions appear. If unexplained conditions appear, resolve them before
continuing. Refer to the Troubleshooting Guide.
Step 2 If you are provisioning a MXP_MR_2.5G or MXPP_MR_2.5G card, complete the DLP-G235 Changing
the 2.5G Data Muxponder Card Mode. If not, continue with Step 3
Step 3 If you are provisioning a MXP_MR_10DME_C, MXP_MR_10DME_L, or MXP_MR_10DMEX_C card,
complete the DLP-G332 Changing the 10G Data Muxponder Port Mode. If not, continue with Step 4.
Step 4 If you are provisioning a GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE card, complete the DLP-G379
Changing the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode. If not, continue with Step 5.
Step 5 If you are provisioning a OTU2_XP card, complete the DLP-G452 Changing the OTU2_XP Card Mode. If
not, continue with Step 6.
Step 6 If you are provisioning a PPM on an ADM-10G card, complete the DLP-G411 Provisioning an ADM-10G
PPM and Port. If not, continue with Step 10.
Step 7 If you are provisioning a PPM on an AR_MXP, AR_XP, or AR_XPE card, complete the NTP-
G321 Provisioning Multiple Operating Modes, on page 672. If not, continue with Step 10.
Step 8 If you are provisioning a PPM on an 100G-LC-C, 10x10G-LC, CFP-LC, 100G-CK-C, 100G-ME-C, or
100ME-CKC card, complete the NTP-G235 Provisioning an Operating Mode, on page 708. If not,
continue with Step 10.
Step 9 If you are provisioning a PPM on an 400G-XP-LC card, complete the NTP-G361 Provisioning an
Operating Mode on the 400G-XP-LC Card, on page 709. If not, continued with Step 10.
Step 10 If you are provisioning a PPM on a WSE card, complete the NTP-G338 Provisioning an Operating Mode
on the WSE Card, on page 767. If not, continue with Step 10.
Step 11 Complete the DLP-G726 Preprovisioning a Multirate PPM task for TXP, MXP, AR_MXP, AR_XP, AR_XPE,
100G-LC-C, 10x10G-LC, CFP-LC, 100G-CK-C, 100G-ME-C, 100GS-CK-LC, , 200G-CK-LC, 100ME-CKC,
400G-XP-LC, WSE, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, or OTU2_XP ports with multirate PPMs.
If you already preprovisioned the multirate PPM, skip this step and continue with Step 11.
Step 12 If you are provisioning an IBM ETR_CLO (External Time Reference – Control Link Oscillator) or
InterSystem Coupling Link (ISC) service on the PPM, complete DLP-G274 Verifying Topologies for
ETR_CLO and ISC Services. Otherwise, continue with Step 12.
Step 13 Complete the DLP-G278 Provisioning the Optical Line Rate to assign a line rate to a TXP, MXP, AR_MXP,
AR_XP, AR_XPE, WSE, 100G-LC-C, 10x10G-LC, CFP-LC, 100G-CK-C, 100G-ME-C, 100GS-CK-LC,
311
DLP-G235 Changing the 2.5G Data Muxponder Card Mode
200G-CK-LC, 100ME-CKC, 400G-XP-LC, or OTU2_XP port after the PPM is provisioned. (This task is
not performed for GE_XP, 10GE_XP, GE_XPE, and 10GE _XPE cards.)
Step 14 If you need to delete a PPM at any point in this procedure, complete the DLP-G727 Delete PPM
Provisioning task.
Stop. You have completed this procedure.
DLP-G235 Changing the 2.5G Data Muxponder Card Mode

Purpose This task changes the card mode for MXP_MR_2.5G
and MXPP_MR_2.5G muxponder cards. The card
mode determines which PPMs can be provisioned for
the card.
Prerequisite Procedures DLP-G46 Log into CTC
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_MR_2.5G
or MXPP_MR_2.5G card where you want to change the card settings.
Step 2 Click the Provisioning > Line > SONET (ANSI) or SDH (ETSI) tabs.
Step 3 Locate the Trunk port table row and verify that the Service State column value is OOS-MA,DSBLD
(ANSI) or Locked-enabled,disabled (ETSI). If the service state is correct, continue with Step 6. If not,
complete the following steps:
Click the Admin State table cell and choose OOS,DSBLD (ANSI) or Locked,Maintenance (ETSI).
Click Apply, then Yes.
Step 4 Click the Provisioning > Line > Client tabs.
Step 5 Locate the Trunk port table row and verify that the Service State column value is OOS-MA,DSBLD
(ANSI) or Locked-enabled,disabled (ETSI). If the service state is correct, continue with Step 6. If not,
complete the following steps:
Step 6 Click the Provisioning > Card tabs.
Step 7 Change the Card Mode as needed:
FC-GE—Choose this option if you will provision any of the following PPM port rates: FC1G (Ports 1-1
and 2-1 only), FC2G (Port 1-1 only), FICON1G (Ports 1-1 and 2-1 only), FICON2G (Port 1-1 only),
and ONE_GE (Ports 1-1 through 8-1).
312
DLP-G332 Changing the 10G Data Muxponder Port Mode
Mixed—Choose this option if you will provision any of the following PPM port rates: FC1G and
ONE_GE (Port 1–1 only), ESCON (Ports 5–1 through 8-1 only)
ESCON—Choose this option if you will provision the ESCON PPM on Ports 1-1 through 8-1.
NoteThe Provisioning > Card tab also has the display-only Tunable Wavelengths field. This field
shows the supported wavelengths of the trunk port after the card is installed in the format:
first wavelength-last wavelength-frequency spacing-number of supported wavelengths. For
example, 1529.55nm-1561.83nm-50gHz-82.
Step 8 Click Apply.


Purpose This task changes the port mode for the
MXP_MR_10DME_C, MXP_MR_10DME_L, and
MXP_MR_10DMEX_C muxponder cards. The port
mode determines which PPMs can be provisioned on
the ports.
Note The MXP_MR_10DME_C, MXP_MR_10DME_L, and MXP_MR_10DMEX_C cards have two port mode
groups, one for Ports 1 through 4, and the second for Ports 5 through 8. To change the port mode, all ports
within the selected port group must be in OOS (out-of-service) service state. Ports in the second port group
do not need to be in OOS service state if you are not changing the port mode for the second port group.
Before you change the port mode, you must also ensure that any PPM port rate provisioned for the selected
port group is deleted (see the DLP-G727 Delete PPM Provisioning).
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_MR_10DME_C,
MXP_MR_10DME_L, or MXP_MR_10DMEX_C card where you want to change the port mode.
Step 3 Change the port mode as described in Table 119: 10G Data Muxponder Card Port Modes.
Note The PPM port rates are provisioned in the DLP-G726 Preprovisioning a Multirate PPM task.
313
Table 119: 10G Data Muxponder Card Port Modes
Parameter Description Options
Port 1-4 Mode Sets the mode of operation for Ports Chose one of the following:
1-1 through 4-1. • FC-GE_ISC—Choose this
option if you will provision
any of the following PPM port
rates: FC1G (Ports 1-1
through 4-1), FC2G (Ports 1-1
and 3-1 only), FICON1G
(Ports 1-1 through 4-1),
FICON2G (Ports 1-1 and 3-1
only), ONE_GE (Ports 1-1
through 4-1), ISC3 COMPAT
(Ports 1-1 through 4-1), ISC3
PEER 1G (Ports 1-1 through
4-1), and ISC3 PEER 2G
(Ports 1-1 and 3-1 only).
• FC4G—Choose this option if
you will provision an FC4G
or FICON4G PPM (Port 1-1
only).
Port 5-8 Mode Sets the mode of operation for Chose one of the following:
Ports 5-1 through 8-1.
• FC-GE_ISC—choose this
option if you will provision
any of the following PPM port
rates: FC1G (Ports 5-1
through 8-1), FC2G (Ports 5-1
and 7-1 only), FICON1G
(Ports 5-1 through 8-1),
FICON2G (Ports 5-1 and 7-1
only), ONE_GE (Ports 5-1
through 8-1), ISC3 COMPAT
(Ports 5-1 through 8-1), ISC3
PEER 1G (Ports 5-1 through
8-1), and ISC3 PEER 2G
(Ports 5-1 and 7-1 only).
• FC4G—choose this option if
you will provision an FC4G
or FICON4G PPM port rate
(Port 5-1 only).
Note The Provisioning > Cards tab also has a display-only Tunable Wavelengths field which shows the
wavelengths supported by the card. If a MXP_MR_10DME_C card is installed, the 32 C-band
wavelengths appear. If the MXP_MR_10DME_L card is installed, the 32 L-band wavelengths appear.
If the MXP_MR_10DMEX_C card is installed, the 82 C-band wavelengths appear.
314
DLP-G379 Changing the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode
Step 4 Click Apply.

Note Loopbacks on MXP-MR-10DME are not applicable when Fiber Channel switches are present.
Note If the Fiber Channel switch version is not present then the Distance Extension settings are not
supported.
Purpose This task changes the GE_XP, 10GE_XP, GE_XPE,

and 10GE_XPE card mode. 10GE_XP and
10GE_XPE cards can be provisioned as a Layer 2
Ethernet switch or a 10G Ethernet TXP. GE_XP and
GE_XPE cards can be provisioned as a Layer 2
Ethernet switch, 10G Ethernet MXP, or 20G Ethernet
MXP.
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the GE_XP,
10GE_XP, GE_XPE, or 10GE_XPE card where you want to change the card mode.
Step 2 In card view, click Provisioning > Ether Ports > Ports.
Step 3 Verify that any provisioned client or trunk ports have an OOS-MA,DSBLD (ANSI) or Locked-
enabled,disabled(ETSI) service state in the Service State column. If so, continue with Step 4. If not,
complete the following substeps.
For the first port that is not out of service, in the Admin State column, choose OOS-MA,DSBLD (ANSI)
or Locked-enabled,disabled (ETSI).
Repeat Step a for each port that is not out of service.
Click Apply.
Step 5 Choose one of the following card modes:
315
Table 120: GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Modes
Mode Cards Description
L2 over DWDM GE_XP Provisions the GE_XP, 10GE_XP,

GE_XPE, or 10GE_XPE as a
10GE_XP
Layer 2 switch.
GE_XPE
10GE_XPE
10GE TXP 10GE_XP Provisions the 10GE_XP or

10GE_XPE as a 10 Gigabit
10GE_XPE Ethernet transponder. Traffic
received on the 10GE client Port
1-1 is sent to 10 Gigabit Ethernet
trunk Port 3-1, and traffic received
on 10 Gigabit Ethernet client Port
2-1 is sent to 10 Gigabit Ethernet
trunk Port 4-1.
10GE MXP GE_XP Provisions the GE_XP or GE_XPE

as a 10 Gigabit Ethernet
GE_XPE muxponder. Traffic received on
Gigabit Ethernet client Ports 1-1
through 10-1 is multiplexed and
sent to 10 Gigabit Ethernet trunk
Port 21-1, and traffic received on
Port 22-1.
20GE MXP GE_XP Provisions the GE_XP or GE_XPE

as a 20 Gigabit Ethernet
GE_XPE
muxponder. Traffic received on
Port 21-1. Trunk port 22-1 is not
used.
The GE-XP and GE-XPE cards operating in 10GE MXP mode and configured for 100% traffic flow, do not drop
frames when up to nine ports are in use. However, when all the ten ports are in use, some frames are dropped.
When the tenth port is to be used, configure the Committed Info Rate (CIR) at 55% on any one of the ports. For
more information about configuring the CIR, see DLP-G380 Provisioning Ethernet Settings.
Step 6 Click Apply, then click Yes in the confirmation dialog box.
316
DLP-G411 Provisioning an ADM-10G PPM and Port
DLP-G411 Provisioning an ADM-10G PPM and Port

Purpose This task provisions a fixed-rate PPM and port on an
ADM-10G PPM card.
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the ADM-10G card where you
want to provision PPM settings.
Step 2 Click the Provisioning > Pluggable Port Modules tabs.
Step 3 In the Pluggable Port Modules area, click Create. The Create PPM dialog box appears.
Step 4 In the Create PPM dialog box, complete the following:
PPM—Choose the SFP you want to install from the drop-down list.
PPM Type—Choose the number of ports supported by your SFP from the drop-down list. If only one
port is supported,PPM (1 port) is the only option.
Step 5 Click OK. The newly created PPM appears in the Pluggable Port Modules area. The row in the
Pluggable Port Modules area turns white and the Actual Equipment Type column lists the equipment
Step 6 name. In the Pluggable Ports area, click Create. The Create Ports dialog box appears. In the Create Ports
Step 7 dialog box, complete the following:
Port—Choose the port you want to configure from the drop-down list.
Port Type—Choose the port type, such as OC-3, OC-12, OC-48, or ONE-GE from the drop-down list.
Ports 1 - 8 can only be OC-3, OC-12, or ONE_GE
Ports 9 - 12 can on be OC-3 or OC-12
Ports 13 - 16 can only be OC-3, OC-12, or OC-48
Step 8 Click OK. The newly created port appears in the Pluggable Ports area. The port type you provisioned is listed
in the Rate column.
Step 9 If you want to provision a PPM or another port, repeat Steps 4 through 8.
317
DLP-G452 Changing the OTU2_XP Card Mode
DLP-G452 Changing the OTU2_XP Card Mode

Purpose This task changes the OTU2_XP card mode. The card
mode determines which PPMs can be provisioned for
the card.
Caution Changing the card configuration to 10G Ethernet LAN Phy to WAN Phy automatically replaces the current port
configurations (Ports 1 and 3) to 10G Ethernet and OC192. This resets and reboots the OTU2_XP card.
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the OTU2_XP card where
you want to change the card mode.
Step 2 In card view, click the Provisioning > Line > Ports tabs.
Step 3 Verify that all provisioned client or trunk ports have an OOS-MA, DSBLD (ANSI) or Locked-enabled,
disabled (ETSI) service state in the Service State column. If so, continue with Step 4. If not, complete
the following substeps.
For the first port that is not out of service, in the Admin State column, choose OOS, DSBLD > Locked,
disabled (ANSI) or (ETSI).
Repeat Step a for each port that is not out of service.
Click Apply.
Step 5 Change the Card Configuration as needed:
Transponder—Choose this option to provision the OTU2_XP card as a transponder. Port pairs 1-3 and
2-4 are both configured as transponders. This is the default card configuration.
Standard Regen—Choose this option to provision the OTU2_XP card as a standard regenerator (with
E-FEC only on one port). Port pairs 1-3 and 2-4 are both configured as regenerators.
Enhanced FEC—Choose this option to provision the OTU2_XP card as an E-FEC regenerator (with
E-FEC on two ports). Port pair 3-4 is configured as enhanced regenerator. Ports 1 and 2 are not used.
Mixed—Choose this option to provision the OTU2_XP card as a transponder and a standard regenerator
(mixed configuration). One of the port pair (1-3 or 2-4) is configured as a transponder and the other
port pair as a standard regenerator.
318
DLP-G274 Verifying Topologies for ETR_CLO and ISC Services
10G Ethernet LAN Phy to WAN Phy—Choose this option to provision the OTU2_XP card to enable
the 10G Ethernet LAN Phy to WAN Phy conversion. Port pair 1-3 supports LAN Phy to WAN Phy
conversion. Port pair 2-4 can be configured either as a transponder or a standard regenerator.
NoteIf you revert to the previous release (release earlier than 9.10), be sure to disable the 10G Ethernet
LAN Phy to WAN Phy conversion feature. If you do not disable the 10G Ethernet LAN Phy to
WAN Phy feature, an error message stating that the user needs to disable 10G Ethernet LAN Phy
to WAN Phy feature before reverting to the previous release is displayed.
Note Table 11-188 on page 11-439 lists the Ethernet variables supported on Ports 1 and 3 of the
OTU2_XP card that has the 10G Ethernet LAN Phy to WAN Phy enabled. When the card is
in the 10G Ethernet LAN Phy to WAN Phy mode, no 10G FC RMONS are supported on
Ports 2 and 4.
For more information on OTU2_XP card configuration rules, see the OTU2_XP Card
Configuration Rules section.
Step 6 Click Apply. Then click Yes in the confirmation dialog box.

Purpose This task verifies that the DWDM network topology
can support the IBM ETR_CLO and ISC services.
Tools/Equipment Cisco TransportPlanner site plan
Procedure
Step 1 Display your site plan in Cisco TransportPlanner.

Step 2 Verify that the topology where you plan to run the ETR_CLO or ISC service can support the service.
The following topologies support ETR_CLO or ISC:
Single span—Two terminal sites with no intermediate sites in between and one of the following sets of
cards installed:
32MUX-O and 32DMX-O cards
32WSS and 32DMX cards
32WSS and 32-DMX-O cards
319
40-MUX-C and 40-DMX-C/40-DMX-CE cards

40-WSS-C/40-WSS-CE and 40-DMX-C/40-DMX-CE cards
Figure 40: Single-Span Topology
Point-to-Point—Two terminal sites with one of the following sets of cards installed:
Line amplifiers can be installed between the terminal sites, but intermediate (traffic terminating)
sites cannot be installed.
Figure 41: Point-to-Point Topology
Two hubs—Two hub nodes in a ring with one of the following sets of cards installed:
Line amplifiers can be installed between the hubs.
320
DLP-G278 Provisioning the Optical Line Rate
Figure 42: Hubs with No Line Amplifiers
Figure 43: Hubs with Line Amplifiers

Purpose This task provisions the line rate for TXP, MXP,
AR_MXP, AR_XP, AR_XPE, 100G-LC-C,
10x10G-LC, CFP-LC, 100G-CK-C, 100G-ME-C,
100ME-CKC, 100GS-CK-LC, 200G-CK-LC, WSE,
400G-XP-LC, GE_XP, 10GE_XP, GE_XPE,
10GE_XPE, ADM-10G, and OTU2_XP cards.

• DLP-G726 Preprovisioning a Multirate PPM
• DLP-G274 Verifying Topologies for ETR_CLO
and ISC Services, on page 319
321
Note The optical line rate for cards with single-rate PPMs is provisioned automatically when you complete the
"DLP-G726 Preprovisioning a Multirate PPM" task if the trunk port is out of service. If the optical line rate
was provisioned automatically, you do not need to complete this task for the MXP_2.5G_10G,
MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, MXP_2.5G_10EX_C, GE_XP, 10GE_XP,
GE_XPE, 10GE_XPE, or OTU2_XP card. If the trunk port was in-service when you provisioned the PPM,
complete this task to provision the optical line rate manually for those cards.
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the card where you want to
provision PPM ports. If the data rate that you are provisioning is DV-6000, HDTV, ESCON, SDI/D1
Video, ISC1, ISC3 (for TXP_MR_2.5G and TXPP_MR_2.5G cards), or ETR_CLO, complete the
following steps. Otherwise, continue with Step 4.
Click the Provisioning > OTN > OTN Lines tabs.
In the ITU-T G.709 OTN field for the respective PPM, choose Disable.
In the FEC field for the respective PPM, choose Disable.
Click Apply.
Step 2 For the TXP_MR-10G card, click the Provisioning > Data Rate Selection tabs. For all other cards, go to
Step 4.
Step 3 In the Data Rate Selection area, click Create and choose the type of port from the drop-down list. The
supported port types are SONET (including 10G Ethernet WAN Phy) and 10G Ethernet LAN Phy.
Step 5 In the Pluggable Ports area, click Create. The Create Port dialog box appears.
Step 6 In the Create Port dialog box, complete the following:
Port—Choose the port and port number from the drop-down list. The first number indicates the PPM in
the Pluggable Port Modules area, and the second number indicates the port number on the PPM. For
example, the first PPM with one port appears as 1-1 and the second PPM with one port appears as 2-1.
The PPM number can be 1 to 4, but the port number is always 1.
Port Type—Choose the type of port from the drop-down list. The port type list displays the supported
port rates on your PPM. See table "PPM Port Types" for definitions of the supported rates.
Step 7 Click OK. The row in the Pluggable Ports area turns white if the physical SFP is installed and light blue if the
SFP is not installed. If the optical parameter values differ from the NE Default settings, change the port state to
In-Service (for ANSI) or Unlocked (for ETSI) to synchronize the values with the NE Default settings.
Step 8 Repeat Step 5 through Step 7 to configure the rest of the port rates as needed.
322
Table 121: PPM Port Types
Card Port Type
TXP_MR_2.5G • OC-3/STM1—155 Mbps

TXPP_MR_2.5G • OC-12/STM4—622 Mbps
• OC-48/STM16—2.48 Gbps
• ONE_GE—One Gigabit Ethernet 1.125 Gbps
• ESCON—Enterprise System Connection 200
Mbps (IBM signal)
• DV6000—Proprietary signal from video vendor
• SDI_D1_VIDEO—Serial Digital Interface and
Digital Video signal type 1
• HDTV—High Definition Television
• PASS-THRU—Not specified
• FC1G—Fibre Channel 1.06 Gbps
• FC2G—Fibre Channel 2.125 Gbps
• FICON1G—Fiber connectivity1.06 Gbps (IBM
signal)
• FICON2G—Fiber connectivity 2.125 Gbps (IBM
signal)
• ETR_CLO—External Time Reference–Control
Link Oscillator
• ISC compat—InterSystem Coupling Link 1
(ISC1)
• ISC peer—InterSystem Coupling Link 3 (ISC3)
• DVB-ASI — Proprietary signal from video
vendor. Digital Video Broadcast - Asynchronous
Serial Interface
• ISC1— InterSystem Channel 1 Gbps (IBM
signal)
MXP_2.5G_10G • OC-48/STM16—2.48 Gbps

MXP_2.5G_10E Automatically provisioned when the PPM is
created if the trunk port is out of service.
MXP_2.5G_10E_C
MXP_2.5G_10E_L
MXP_2.5G_10EX_C
323
Card Port Type

TXP_MR_10G SONET (OC-192)/SDH (STM-64) including
Provisioned on the Data Rate Selection tab. 10G Ethernet WAN Phy
TXP_MR_10E SONET (OC-192)/SDH (STM-64) including

TXP_MR_10E_C 10G Ethernet WAN Phy—10 Gbps
TXP_MR_10E_L 10G Ethernet LAN Phy—10 Gbps Ethernet
TXP_MR_10EX_C 10G Fibre Channel—10 Gbps Fibre Channel

(TXP_MR_10EX_C only) IB_5G
40E-TXP-C 40ME-TXP-C SONET (OC-768)/SDH (STM-256)

OTU3
MXP_MR_2.5G If the card mode is FC_GE:

MXPP_MR_2.5G • FC1G ISL—Fibre Channel 1.06 Gbps (Ports 1-1
and 2-1)
• FC2G ISL—Fibre Channel 2.125 Gbps (Port 1-1
only)
• FICON1G ISL—Fiber connectivity 1.06 Gbps
(IBM signal) (Ports 1-1 and 2-1)
(IBM signal) (Port 1-1 only)
(Ports 1-1 and 2-1 only)
If the card mode is Mixed:

• FC1G ISL—Fibre Channel 1.06 Gbps (Port 1-1
only)
(IBM signal) (Port1-1 only)
(Port 1-1 only)
Mbps (IBM signal) (Ports 5-1 through 8-1)
If the card mode is ESCON:

Mbps (IBM signal) (Ports 1-1 through 8-1)
324
Card Port Type

MXP_MR_10DME_C If the port mode is FC_GE_ISC:
MXP_MR_10DME_L FC1G—Fibre Channel 1.06 Gbps (Ports 1-1
MXP_MR_10DMEX_C through 8-1)
FC2G—Fibre Channel 2.125 Gbps (Ports 1-1,
3-1, 5-1, and 7-1 only; ports are not available if
the port that follows—2-1, 4-1, 6-1, or 8-1—
has a PPM provisioned.)
FICON1G—Fiber connectivity 1.06 Gbps (IBM
signal) FICON2G—Fiber connectivity 2.125
Gbps (IBM signal) (Ports 1-1, 3-1, 5-1, and 7-1
only; ports are not available if the port that
follows—2-1, 4-1, 6-1, or 8-1—has a PPM
provisioned.)
ONE_GE—One Gigabit Ethernet 1.125 Gbps
(Ports 1-1 through 8-1)
ISC COMPAT (Ports 1-1 through 8-1)
ISC3 PEER 1G (Ports 1-1 through 8-1)
ISC3 PEER 2G (Ports 1-1, 3-1, 5-1, and 7-1
only; ports are not available if the port that
follows—2-1, 4-1, 6-1, or 8-1—has a PPM
provisioned.)
If the port mode is FC4G:

FC4G—Fibre Channel 4.25 Gbps (Ports 1-1 or 5-1
only; ports are not available if any of the three
ports that follow has a PPM provisioned.)
signal) (Ports 1-1 or 5-1 only; ports are not
available if any of the three ports that follow
has a PPM provisioned.)
40G-MXP-C 40E-MXP-C 40ME-MXP-C SONET (OC-192)/SDH (STM-64)

FC8G
FC10G
TEN_GE
OTU2
325
Card Port Type

GE_XP GE_XP and GE_XPE client ports1
10GE_XP 10GE_XP and 10GE_XPE client and trunk
GE_XPE ports; GE_XP and GE_XPE trunk ports1
10GE_XPE
OTU2_XP SONET (including 10G Ethernet WAN Phy)—

10 Gbps
10G Ethernet LAN Phy—10 Gbps Ethernet
10G Fiber Channel—10 Gbps Fibre Channel
IB_5G—InfiniBand 5 Gbps
NoteIf you have an OTU2 signal in which the
OPU2 has been generated by
multiplexing four ODU1 signals,
choose SONET as the port rate. This
allows the OTU2 signal to be
transported transparently in standard
or E-FEC regenerator configuration.
326
Card Port Type

AR_MXP OC-3/STM1—155 Mbps
AR_XP OC-12/STM4—622 Mbps
AR_XPE OC-48/STM16—2.48 Gbps
Gigabit Ethernet—1.125 Gbps
Fast Ethernet—100 Mbps
ESCON-Enterprise System Connection 200
Mbps (IBM signal)
FC1G—Fibre Channel 1.06 Gbps
FICON1G—Fiber connectivity1.06 Gbps (IBM
signal)
FICON2G—Fiber connectivity 2.125 Gbps
(IBM signal)
FICON4G—Fiber connectivity 4.25 (IBM signal)

signal)
SD-SDI—270 Mbps
HD-SDI—1.485 Gbps
Third-generation SDI (3G-SDI)—2.970 Gbps
OTU2E —11.09 Gbps
OTU1—2.66 Gbps
327
Transponder and Muxponder Protection Topologies
Card Port Type

100G-LC-C SONET (OC-192)/SDH (STM-64)
10x10G-LC 10G Ethernet LAN Phy
CFP-LC 40G Ethernet LAN Phy
100G-CK-C 100 GE
100G-ME-C
FC 8G
100ME-CKC
FC 10G
400G-XP-LC
OTU2
OTU3
OTU4
IB_5G
WSE 10GE LAN PHY

8G FC
10G FC
SONET (OC-192)/SDH (STM-64)
OTU2
OTU2e
Transponder and Muxponder Protection Topologies

The ONS 15454 supports Y-cable and splitter protection for transponder (TXP) and muxponder (MXP) cards.
The following figure shows Y-cable and splitter protection.
328
Y-Cable Protection
Figure 44: Y-Cable and Splitter Protection
Y-Cable Protection
The Y-cable protection scheme employs two Y cables, which are hardware combiner/splitters. A signal
injected into the stem of the Y is duplicated into both arms of the Y with 50 percent attenuation in each
arm. Signals injected into the arms of the Y are summed into the stem of the Y.
A Y-cable protection group requires two DWDM cards with the arms of the Y-cables connected to the
client ports on the DWDM cards, and the stems of the Y-cables connected to the client source, such as an
OC-N card. When a TXP Y-cable protection group is required, the two TXP cards must be installed in the
same shelf assembly in adjacent slots.
The following figure shows a functional block diagram of Y-cable protection.
329
Y-Cable Protection
Figure 45: Y-Cable Protection
A Y-cable protection group has two paths:

Transmit (TX) path, defined as the client RX and the trunk TX
Receive (RX) path, defined as the trunk RX and the client TX
The basic behavior of the Y-cable group is that an incoming client signal is bridged to the two TX paths, and one
RX path is selected for the outgoing client signal. Thus, a Y-cable protection group only protects against defects
in the RX path. The following figure shows the RX path for the near-end Y-cable protection group.
Figure 46: Rx Path for Near-End Y-Cable Protection
To protect against all defects, a pair of Y-cable protection groups is required. Each protects against
defects in its own RX path. The following figure shows how the near-end and the far-end jointly protect
against defects.
330
Y-Cable Protection
Figure 47: Near-End and Far-End Y-Cable Protection
A Y-cable protection group is defined by two client ports on two different cards. One client port is designated as
working and the other is designated as protect. Some of the rules in a Y-cable protection are as follows:
The cards must have the same equipment type.
The cards must have the same payload data type.
The cards must have the same termination mode.
The client ports must have the same payload type.
The client ports must have the same facility number.
The cards must have the same operating mode.
For example, a Y-cable protection group can include MXP Client 2 on the working and protect cards, but
cannot include Client 2 on the working card if Client 3 is on the protect card. TXP cards have a single
client (facility 1), so this requirement is satisfied by default.
Zero, one, two, or all of the client ports on an MXP card can be in Y-cable protection groups. Some
clients can be in a protection group while others are unprotected.
The client ports on a card that are in Y-cable protection groups are either all working or all protect. You
cannot mix working and protect client ports on the same card. For convenience, the trunk ports adopt the
designation (working or protect) of the client ports.
The Y-cable protection groups on an MXP card switch independently. A Y-cable protection group performs
protection switching by disabling the transmitter on the standby client port and enabling the active client port.
The protection group does not enable the active transmitter, because the active transmitter may have been
disabled for other reasons. The port is disabled if it has an OOS-DBLD service state, is squelched, or is
shutdown by automatic laser shutdown (ALS). The protection group releases a signal that the active
transmitter is disabled. This activity changes the RX path but not the TX path. A Y-cable protection group
can only protect its RX path.
A Y-cable protection group enables its client receivers unless the client facilities have an OOS-DSBLD
service state. This means that client receivers (and trunk transmitters) are operational regardless of the
active/standby status of the card. Traffic might not be lost if both client lasers in a Y-cable protection group
are enabled. If the output powers of the two lasers are not identical, then the receiver at the stem of the Y-
cable can opt for the stronger client laser and ignore the weaker signal.
331
Splitter Protection
Splitter Protection
The protection group is defined by the two trunk ports on the splitter card. One trunk port is designated
working and the other is designated as protect. A splitter card has a single trunk laser and a hardware
splitter that duplicates the trunk signal out of the card’s two trunk ports. The switch in the card receives one
of the two trunk input signals and the received signal is connected to the client ports.
A splitter protection group has two TX paths and two RX paths on the same card; the paths share client
ports. The TX path is defined as the client RX and the trunk TX, and the RX path is defined as the trunk
RX and the client TX. In a splitter group, an incoming client signal is bridged to the TX paths, and one RX
path is selected for the outgoing client signal.
A splitter protection group performs switching by enabling the receiver of the active trunk port and then
routing the active trunk traffic to the client ports. The protection group does not disable the transmitter on
the standby trunk port.
Splitter protection is supported in AR_MXP, AR_XP, AR_XPE, and 10x10G-LC cards by configuring
the operating mode.
When any client port of the 10x10G-LC card is involved in Y-cable protection group, then splitter
protection must not be allowed in that card.
Switch Criteria
Cisco Transport Controller (CTC), the ONS 15454 software interface, performs protection switches based
on priority, trunk and client line conditions, switch commands, unidirectional/bidirectional switching, and
other criteria.
Switch Priority
Switch priorities are defined in the following table.
Table 122: Switch Priorities
Request/State Abbreviation Priority
Lockout of Protection LO 8
(highest)
Forced Switch FS 7
Signal Fail SF 6
Signal Degrade SD 5
Manual Switch MS 4
Wait to Restore WTR 3
Do Not Revert DNR 2
No Request NR 1 (lowest)
All switch criteria are assigned a numerical priority, which is reversed from ITU-T G.873.1 to avoid confusion
when comparing priorities. In this document, a higher priority is numerically greater than a lower priority.
332
Line Conditions on the Trunk
If the protection channel and the working channel have conditions with the same priority, and the priority
is greater than Do Not Revert (DNR), then the condition on the protection channel takes precedence.
In practice, only two priorities can exist independently and simultaneously on the working and protection
channels: signal fail (SF) and signal degrade (SD). This requirement means that if both channels have, for
example, an SF condition without any higher conditions present, then the protection group chooses the
working channel. Traffic switches away from the highest-priority condition.
Line Conditions on the Trunk

The following line conditions on the trunk generate the priorities given:
OTUn-LOS on a trunk, if ITU-T G.709 is enabled, has an SF priority.
OTUn-LOF on a trunk, if ITU-T G.709 is enabled, has an SF priority.
OTUn-LOM on a trunk, if ITU-T G.709 is enabled, has an SF priority.
OTUn-AIS on a trunk, if ITU-T G.709 is enabled, has an SF priority.
ODUn-AIS on a trunk, if ITU-T G.709 is enabled, has an SF priority.
OTU BER SF on a trunk, if ITU-T G.709 is enabled, has an SF priority.
OTU BER SD on a trunk, if ITU-T G.709 is enabled, has an SD priority.
TIM on OTU SM TTI on a trunk, if ITU-T G.709 is enabled, has an SF priority.
TIM on ODU PM TTI on a trunk, if ITU-T G.709 is enabled, has an SF priority.
S-LOF on a trunk, if ITU-T G.709 is disabled and the trunk is OCn, has an SF priority.
S-LOS on a trunk, if ITU-T G.709 is disabled and the trunk is OCn, has an SF priority.
SF on a trunk, if ITU-T G.709 is disabled and the trunk is OCn, has an SF priority.
SD on a trunk, if ITU-T G.709 is disabled and the trunk is OCn, has an SD priority.
AIS-L on a trunk, if ITU-T G.709 is disabled and the trunk is OCn, has an SF priority.
RS-LOF on a trunk, if ITU-T G.709 is disabled and the trunk is STMn, has an SF priority.
RS-LOS on a trunk, if ITU-T G.709 is disabled and the trunk is STMn, has an SF priority.
SF on a trunk, if ITU-T G.709 is disabled and the trunk is STMn, has an SF priority.
SD on a trunk, if ITU-T G.709 is disabled and the trunk is STMn, has an SD priority
MS-AIS on a trunk, if ITU-T G.709 is disabled and the trunk is STMn, has an SF priority.
TIMS-S on J0 on a trunk, if ITU-T G.709 is disabled and TIM is enabled, has an SF priority.
RS-TIM-S on J0 on a trunk, if ITU-T G.709 is disabled and TIM is enabled, has an SF priority.
CARLOSS on a trunk, if ITU-T G.709 is disabled and the payload is GigE, has an SF priority.
SIGLOSS on a trunk, if ITU-T G.709 is disabled and the payload is Fibre Channel (any speed), has an
SF priority.
GE-OOSYNC on a trunk, if ITU-T G.709 is disabled and the payload is 10GigE, has an SF priority.
OOS on a trunk, if ITU-T G.709 is disabled and the payload is GigE, has an SF priority.
OOS on a trunk, if ITU-T G.709 is disabled and the payload is Fibre Channel, has an SF priority.
SYNCLOS on a trunk, if ITU-T G.709 is disabled and the payload is Fibre Channel, has an SF priority.
Line Conditions on the Client

Most of the defects on client ports are corrected by switching at the far-end protection group.
In a Y-cable protection group, a line alarm indication signal (AIS-L) on the client signal has an SF priority
if generic framing procedure (GFP) is not used and the client framing is SONET.
333
Switch Commands
Switch Commands
Switch commands have the following priorities:
A Lockout of Protect (Lockon Working) switch command has an LO priority on the protect port.
A Force From Working (Force to Protect) switch command has an FS priority on the working port.
A Force From Protect (Force To Working) switch command has an FS priority on the protect port.
A Manual From Working (Manual To Protect) switch command has an MS priority on the working port.
A Manual From Protect (Manual To Working) switch command has an MS priority on the protect port.
A Clear command cancels (unlocks) any switch command.
Unidirectional and Bidirectional Switching

Y-cable and splitter protection support unidirectional switching. In unidirectional switching, the near-
end protection group switches without regard for the status of the far-end protection group.
Therefore, the near-end working facilities can be active at the same time the far-end protection facilities are
in standby. This does not mean that a defect at the far end will not cause a near-end switch. A defect at the
far end might result in a condition at the near end, which then causes a switch, but the switch is caused by
the near-end condition.
Bidirectional protection cannot be provisioned unless the near end and far end have the same hardware
and data modes and the trunks are connected as working-to-working and protect-to-protect.
Any other configuration results in an undefined behavior. Y-cable and splitter protection groups are
not required to detect misconfigured bidirectional protection.
A Y-cable or splitter protection group switches unidirectionally unless at least one trunk signal is intact
and there is an operational card terminating the trunk signal at the far end.
Other Switch Criteria

This section details switch criteria other than line conditions. A card is said to become operational after it
has received and processed the first provisioning message after a warm or cold boot. A card ceases to be
operational when it is reset, either with a soft reset request or a hardware reset.
A soft reset of a card does not cause a protection switch or a traffic disruption greater than the disruption induced
by the soft reset of an unprotected card. If one or both cards are not operational, then any disruption of traffic on
the active card will cause traffic loss until both cards have become operational again.
Switch conditions with a priority lower than FS are ignored by a Y-cable protection group unless both cards
are operational. Switch conditions cannot be used to restore traffic while one member of the protection
group is reset. For instance, if the working/active card is soft reset and a Forced Switch to the protect card
is issued, the protect client laser will turn on but the working client laser will not turn off. Traffic will be
lost until the working card becomes operational and can process the Forced Switch request.
The LO and FS switch conditions are accepted by the shelf regardless of the operational status of the cards
in a Y-cable protection group or a splitter protection group. A nonoperational card cannot process the
switch condition; the provisioning has been accepted by the shelf controller and will be issued to the cards
when it becomes operational.
The LO and FS switch conditions are implemented immediately by the operational cards in a Y-cable
protection group even if one card is nonoperational. This might cause traffic loss.
Y-cable protection switching is inhibited during a shelf controller reset. Protection switching does not
resume until the cards receive their first provisioning message from the active shelf controller.
334
Switch Stability
Each card in a Y-cable protection group begins its provisioning hold-off timer after processing the first
provisioning message. For proper behavior, both cards should be provisioned within the provisioning hold-
off timer interval. A card missing condition has an SF+ priority. This gives the card missing condition a
higher priority than any span alarm.
A card MEA condition has an SF priority.
An SFP failure condition has an SF priority.
An SFP mismatch (failure to support the data rate or mode) condition has an SF priority.
An SFP missing condition has an SF priority.
A wavelength mismatch condition has an SF priority.
A port that is OOS-DSBLD has an SF+ priority.
The OOS-DSBLD condition has a higher priority than any span alarm.
A port that is shutdown by ALS has an SF priority.
The hold-off timer interval is not applicable for WSE, 10x10G-LC, 100G-LC-C, 100G-CK-C, 100GS-CK-
LC, and 200G-CK-LC cards.
Switch Stability
Y-cable and splitter protection groups use a variety of timers to prevent oscillation, as detailed in the
following requirements. No timer is provisionable.
The protection groups implement soak-to-clear timers. A soak-to-clear timer starts when a switch condition
clears. While the timer is running, the protection group behaves as though the switch condition is still
present. If the switch condition recurs before the timer has expired, the timer is canceled. When the switch
condition clears, the timer is restarted.
The durations of soak-to-clear timers are not user-provisionable and are unrelated to the soak times for
alarms and conditions. A soak-to-clear timer is not started when a switch condition clears if the switch
condition has a lower priority than the currently active switch condition For example, an SD BER soak-to-
clear timer will not start if SD BER clears while AIS is present, since AIS has a higher priority than SD
BER. All line defects with an SF priority, except for SF BER, share a single one-second soak-to-clear
timer. SF BER and SD BER line conditions have a 10-second soak-to-clear timer.
The protection group does not switch sooner than 1.5 seconds after the last switch (the switch hold-off timer).
This timer prevents rapid oscillation of the protection group.
A Y-cable protection group does not switch for the first 5 seconds after it is created unless both cards in the
protection group become active before 5 seconds elapses.This delay allows both cards in the protection
group to be provisioned before any switching decisions are made.
A Y-cable protection group does not switch sooner than 0.5 seconds after a client or trunk facility moves
from the OOS-SDBLD state. This hold-off timer allows the cards to ignore transients caused by a port
going in-service. The ALS condition has a 3 second soak-to-clear timer.
Revertive and Nonrevertive Attributes

Both revertive and nonrevertive switching is supported; the default switch mode is nonrevertive.
Network element (NE) defaults contain a revertive attribute for Y-cable and splitter protection. When
applicable in revertive mode, the revert delay timer, also called the Wait-To-Restore (WTR) timer, is
software provisionable for Y-cable and splitter protection. The WTR timer is provisionable between 0.5
and 12 minutes, in 0.5 minute increments, and it has a default value of 5 minutes.
335
Communications Channels
When applicable, the NE defaults contain a WTR attribute for Y-cable and splitter protection. When a Y-
cable protection group is deleted, a dialog box will appear warning of possible traffic loss.
Communications Channels
In a Y-cable protection group, only the working client cam be provisioned with a section data communications
channel (SDCC) or line data communications channel (LDCC), and only the working client port can be
provisioned as a timing reference (as permitted by payload). The working and protect trunks can be provisioned
separately with communication channels (SDCC, LDCC, or generic communications channel [GCC], as
permitted by payload type). The communication channels are not protected.
Inherited Port Properties

Selected port properties of the protection port are inherited from the working port. In this section, the
word port refers to a Y-cable client port or a splitter trunk port:
The maximum Ethernet Frame Size of the protect port is inherited from the working port.
The Port Type (SONET or SDH) of the protect port is inherited from the working port.
The Termination Mode of the protect port is inherited from the working port.
The SF BER threshold of the protect port is inherited from the working port.
The SD BER threshold of the protect port is inherited from the working port.
The SyncMsgIn and SendDoNotUse attributes of the protect port are inherited from the working port.
Section trace provisioning of the protect port is inherited from the working port.
The line thresholds of the protect port are inherited from the working port.
The SDCC/LDCC/GCC provisioning of the protect port is inherited from the working port.
The ALS provisioning of the protect port is inherited from the working port.
ALS is not permitted on the client ports of Y-cable protection groups. This requirement applies only to
splitter protection groups.
Switch Status Reporting

Y-cable and splitter protection groups indicate to management software the active/standby status of
facilities and cards involved in the protection group. A facility has an active/standby status within the
protection group and it has a status that is reported to the management software. These two do not always
coincide. Internally, the protection group always has one active facility and one standby facility. In some
circumstances, the protection group reports both facilities as standby.
The reported status of any port on a nonoperational card is undefined. While a card is reset, its status
might or might not be reported properly. Because the card does not report any status, the report to the user
is a function of the management software, not the protection group.
A Y-cable protection group reports a separate status for the TX path and the RX path, for every facility.
The active/standby status of the protection group is reported as the status of the RX path. If the status of the
far-end protection group is known, then the status of the far-end protection group is reported as the status of
the near-end TX path.
The ability of a protection group to know the status of the far-end protection group is a function of the
equipment type and the trunk type. If the status of the far-end protection group is not known, the status of
the near-end protection group shall be reported as the status of the TX path.
A Y-cable protection group has at most one active client port. A port in a Y-cable or splitter protection group is
reported as standby if it has an OOS-DSBLD service state, regardless of its status within the protection group. A
port in a Y-cable or splitter protection group is reported as active if it does not have an OOS-DSBLD
336
Switch Conditions
state and if it carries overhead traffic (GCC, SDCC, LDCC, or E1 bytes), regardless of its status within
the protection group.
A client port in a Y-cable protection group is reported as active if it does not have an OOS-DSBLD service
state and if it is active within the protection group. A trunk port in a Y-cable protection group is reported
as active if it does not have an OOS-DSBLD service state and if any client port on the same card is active.
Transponders have exactly one client port, and the relationship of client to trunk is clear. Muxponder
cards have multiple client ports, which means that multiple protection groups are present. If any client
port on a muxponder is active, and if the trunk is in-service, the trunk is also reported as active.
Client ports and trunk ports on unprotected cards (cards not part of any protection group) are reported as
active if they do not have an OOS-DSBLD service state.
Switch Conditions
Protection groups generate conditions and transient conditions to provide a status to the node
management software. Common conditions include:
The protection group raises a MAN-REQ condition against the working facility while a Manual Switch
to Protection switch command is in effect.
The protection group raises a MAN-REQ condition against the protection facility while a Manual
Switch to Working switch command is in effect.
The protection group raises a FORCED-REQ condition against the working facility while a Forced
Switch to Protection switch command is in effect.
The protection group raises a FORCED-REQ condition against the protection facility while a Forced
Switch to Working switch command is in effect.
The protection group raises a LOCKOUT-REQ condition against the protection facility while a Lockout
of Protection switch command is in effect.
The protection group signals an APS-CLEAR condition when a switch command is preempted by a
higher-priority switch condition.
The protection group signals a FAILTOSW condition while a switch command is inhibiting a protection
switch due to a lower-priority line condition.
The protection group raises a WTR condition against the working facility while the Wait To Restore
timer is running.
The protection group, if it is in revertive mode, raises a WKSWPR condition against the working
facility while the protection facility is active.
The protection group, if it is in nonrevertive mode, signals a WKSWPR condition against the working
facility when the protection facility becomes active.
The protection group, if it is nonrevertive, signals a WKSWBK condition against the working facility
when the working facility becomes active.
Protection Switching Performance Requirements

Protection switching is executed within 50 ms of a defect appearing at the near end. Loss of light on the
client outputs of a Y-cable protection group does not exceed 20 ms during a switch.
During a protection switch, the standby client transmitter turns off, and the active client transmitter turns
on. If the standby transmitter turns off before the active transmitter is fully on, a loss of light occurs at the
stem of the Y-cable. This loss of light does not last longer than 20 ms. If a payload cannot tolerate a loss of
light less than 20 ms, then that payload cannot be used with Y-cable protection.
337
Usability Requirements
Usability Requirements
The following section discusses regeneration groups, automatic laser shutdown, and client signal failures.
Regeneration Groups
A regeneration group boosts the power and improves the signal-to-noise (S/N) ratio in a DWDM signal.
The purpose is to extend the reach of a DWDM signal between two termination points. In an ideal
condition, regeneration is totally transparent to the endpoints. However, some regeneration techniques fall
short of this ideal condition and might modify, delay, or even drop overhead signals (ITU-T G.709, GFP, or
other section-level signaling protocols).
The behavior of Y-cable and splitter protection groups is unchanged by the presence of a single peer-to-
peer regeneration group in one or both of the DWDM spans. This requirement cannot be met if the
regeneration corrupts the overhead bytes that are necessary for protection switching.

ALS disables the transmitter of a facility if the receiver of the same facility detects a loss of light. ALS
exists as a human-safety standard. After ALS shuts down the transmitter, it is not restarted until the loss of
light condition clears. To facilitate restarting lasers when both ends of a span are shut down by ALS, the
facility can be provisioned to send short test pulses of light. ALS is not permitted on the client ports of a Y-
cable protection group.
Client Signal Failures

Y-cable protection groups can protect against failures of the client RX signal at the end. The far-end client
RX failure can be in the fiber (in an “arm” of the Y), in the equipment (for example, the SFP), or in the
provisioning (client OOS-DSBLD). These failure types require special handling because they are out-of-
band with respect to the normal client payload. The term used for these failures is client signal fail (CSF).
This has the same meaning as GFP-CSF, but does not imply that GFP-CSF is used for the signaling. Client
signal failures include:
An S-LOF on a client port, if the client is OC-N, is signaled to the downstream client port as a CSF.
An S-LOS on a client port, if the client is OC-N, is signaled to the downstream client port as a CSF.
An RS-LOF on a client port, if the client is STM-N, is signaled to the downstream client port as a CSF.
An RS-LOS on a client port, if the client is STM-N, is signaled to the downstream client port as a CSF.
A GE-OOSYNC on a client port, if the client is GigE or 10GigE, is signaled to the downstream client
port as a CSF.
An SFP missing condition on a client port is signaled to the downstream silent port as a CSF.
An SFP mismatch (failure to support client data rate) condition on a client port is signaled to the
downstream client port as a CSF.
An SFP failure condition on a client port is signaled to the downstream client port as a CSF.
An OOS-DSBLD condition on a client port is signaled to the downstream client port as a CSF.
In-service Upgrade
A Y-cable group switches normally during a software activation or software revert if both cards in the Y-
cable group are running the same software release.
This behavior is different from that of OC-N 1+1 protection groups, which will not switch until the software
activation is complete. The Y-cable group is able to switch before either card has booted to the new release
338
Path Diversion Support for Client Protection
and after both cards have booted to the new release. This requirement does not preempt the other
requirements that both cards be operational and that an active TCC2/TCC2P be installed.
Path Diversion Support for Client Protection

The ONS 15454 DWDM system provides the capability to provision unprotected wavelengths on a
per-wavelength basis and supports the reuse of unprotected wavelengths on adjacent spans.
The following figure provides examples of unprotected wavelengths.
Figure 48: Example of Unprotected Wavelengths
NTP-G33 Creating a Y-Cable Protection Group

Purpose This procedure creates a Y-cable protection group
between the client ports of two TXP, MXP, AR_XP,
AR_MXP, AR_XPE, 10x10G-LC, CFP-LC,
100G-CK-C, 100GS-CK-LC, 200G-CK-LC, GE_XP,
10GE_XP, GE_XPE, 10GE_XPE, or OTU2_XP cards
when the cards are provisioned in the TXP or MXP
mode.
339
Tools/Equipment • Installed TXP, MXP, AR_MXP, AR_XP,

AR_XPE, 10x10G-LC, CFP-LC, 100G-CK-C,
100GS-CK-LC, 200G-CK-LC, GE_XP,
10GE_XP, GE_XPE, 10GE_XPE, or OTU2_XP
card.
• Cisco TransportPlanner Traffic Matrix
Prerequisite Procedures • NTP-G15 Installing the Common Control Cards

on ONS 15454 Shelf
• NTP-G14 Install DWDM Equipment
• NTP-G139 Verifying Cisco Transport Planner
Reports and Files
Note Y-cable protection is available for the 100GS-CK-LC and 200G-CK-LC cards only in the MXP-10x10G
operating modes
Note In the MXP-10x10G opmode, for the 200G-CK-LC and 10x10G-LC cards, Y-cable creation for OTU2
client payload of 10x10G-LC is not supported in R10.70.
Note In the MXP-10x10G-100G opmode, Y-cable creation for client ports of 10x10G-LC, for the combination
of 200G-CK-LC and 100GS-CK-LC trunk cards is not supported in R10.70.
Note Y-cable protection is available for the 10x10G-LC card when it is provisioned in one of the following modes:
TXP-10G mode—The client ports are provisioned with 10G Ethernet LAN Phy, 8G FC, 10G FC,
OTU2, and OC192/STM-64 payloads.
MXP-10G mode—The client ports are provisioned with 10GE, 8G FC, 10G FC, OTU2, and
OC192/STM-64 payloads.
340
Note Y-cable protection is available for the 100G-CK-C card for the CPAK-100G-LR4 pluggable with
100GE/OTU4 payloads.
Note Y-cable protection is available for the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards when they are
provisioned in the 10GE MXP, 20GE MXP, or 10GE TXP mode. If you are provisioning Y-cable
protection for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards, the Ethernet mode must be set to 1000
and 10000 Mbps respectively. To provision the Ethernet mode, see the DLP-G380 Provisioning Ethernet
Settings, on page 579. Y-cable protection cannot be provisioned for the GE_XP, 10GE_XP, GE_XPE, and
10GE_XPE cards when they are provisioned in L2-over-DWDM mode.
Note Y-cable protection is available for the OTU2_XP card when it is provisioned in the TXP card mode. The
OTU2-XP and 40E-MXP-C card cannot implement Y-cable protection for the client ports in 10 GE LAN
PHY mode. Hence, a pair of OTU2_XP cards is used at each end in pass-through mode (Transponder mode
with G.709 disabled) to implement Y-cable protection. The 40E-MXP-CE card can implement Y-cable
protection without the OTU2-XP card for the client ports in LAN PHY GFP mode. However, the 40E-
MXP-CE card cannot implement Y-cable protection without the OTU2-XP card for the client ports in LAN
PHY WIS mode.
Note For SONET or SDH payloads, Loss of Pointer Path (LOP-P) alarms can occur on a split signal if the ports
are not in a Y-cable protection group.
Procedure
Step 1 View the Cisco Transport Planner Traffic Matrix (see the Cisco Transport Planner Node Setup Information
and Files table) for your site. Verify the cards that need Y-cable protection groups. (Cards requiring Y-cable
protection are indicated with “Y-Cable” in the Traffic Matrix table Protection Type column.) For more
information, see the Cisco Transport Planner DWDM Operations Guide.
Step 2 Verify that the cards are installed according to the requirements specified in Cable Connections for Y-Cable
Protection of One Client Signal. Protection Types, on page 343 lists the protection types available for DWDM
client cards.
Step 3 Verify that pluggable ports are provisioned for the same payload and payload rate on the cards where you
want to create the Y-cable protection group:
a) Display the card in card view.
b) Click the Provisioning > Pluggable Port Module tab.
c) Verify that a pluggable port is provisioned in the Pluggable Port Module area, and the payload type and
rate is provisioned for it in the Pluggable Ports area. If they are not the same, for example, if the pluggable
port and rate are not the same, you must either delete the provisioned rate and create a new rate to match
using the DLP-G725 Preprovisioning PPM Slot task or replace the pluggable port (SFP or XFP) using
the DLP-G728 Remove PPM from the Line Card task.
341
Step 4 In node view (single-shelf mode) or shelf view (multishelf mode), click the Provisioning > Protection tabs.
Step 5 In the Protection Groups area, click Create.
Step 6 In the Create Protection Group dialog box, enter the following:
Name—Type a name for the protection group. The name can have up to 32 alphanumeric (a-z, A-Z, 0-
9) characters. Special characters are permitted. For TL1 compatibility, do not use question mark (?),
backslash (\), or double quote (“) characters.
Type—Choose Y Cable from the drop-down list.
Protect Port—From the drop-down list, choose the port that will be the standby or protection port to the
active port. The list displays the available transponder or muxponder ports. If transponder or
muxponder cards are not installed, no ports appear in the drop-down list.
After you choose the protect port, a list of available working ports appear in the Available Ports list. If no
cards are available, no ports appear. If this occurs, you can not complete this task until you install the
physical cards or preprovision the slots.
Step 7 From the Available Ports list, select the port that will be protected by the port you selected in Protect Ports.
Click the top arrow button to move the port to the Working Ports list.
Step 8 Complete the remaining fields:
Revertive—Check this check box if you want traffic to revert to the working port after failure conditions
remain corrected for the amount of time entered in the Reversion Time field.
Reversion time—If Revertive is checked, select a reversion time from the drop-down list. The range is
0.5 to 12.0 minutes. The default is 5.0 minutes. Reversion time is the amount of time that will elapse
before the traffic reverts to the working card. The reversion timer starts after conditions causing the
switch are cleared.
Note The bidirectional switching option is available for Y-cable protection groups only in the
following cases:
• On the MXP_MR_10DME card when ISC3_PEER_1G/ISC3_PEER_2G is the client payload.
• On the MXP_MR_10DME and MXP_MR_2.5G cards when Fibre Channel is the client payload.
In this case bidirectional switching is:
• Automatically enabled when Distance Extension is enabled.
• Automatically disabled when Distance Extension is disabled.
The bidirectional switching option is available for all SONET and SDH 1+1 protection groups.
Step 9 Click OK.

Step 10 Repeat this procedure for every Y-cable protection group indicated in the Cisco TransportPlanner
Traffic Matrix.
342
Protection Types
Protection Types
Table 123: Protection Types
Protection Type Cards Description and Installation

Requirements
Y-cable Pairs a working transponder or

muxponder card or port with a
protect transponder or muxponder
card or port. The protect port must
be on a different card than the
working port and it must be the
same card type as the working port.
The working and protect port
numbers must be the same, that is,
Port 1 can only protect Port 1, Port
2 can only protect Port 2, and so
on.
Note The working and protect
card must be in the same
shelf for a multishelf
node.
343
Protection Types
Protection Type Cards Description and Installation

Requirements
MXP_2.5_10G
MXP_2.5_10E
MXP_2.5_10E_C
MXP_2.5_10E_L
TXP_MR_10EX_C
TXP_MR_10G
TXP_MR_10E
TXP_MR_10E_C
TXP_MR_10E_L
TXP_MR_2.5G
40E-TXP-C
40ME-TXP-C
MXP_MR_2.5G
MXP_MR_10DME_C
MXP_MR_10DME_L
MXP_MR_10DMEX_C
40G-MXP-C
40E-MXP-C
40ME-MXP-C
GE_XP (when provisioned in 10GE
MXP or 20GE MXP card mode)
10GE_XP (when provisioned in
10GE TXP card mode)
GE_XPE
10GE_XPE
OTU2_XP
AR_MXP
AR_XP
AR_XPE
10x10G-LC
CFP-LC
100G-CK-C
344
NTP-G199 Creating a Splitter Protection Group
Protection Type Cards Description and

Installation Requirements
Splitter TXPP_MR_2.5G A splitter protection group is

MXPP_MR_2.5G automatically created when a
TXPP_MR_2.5G,
AR_MXP MXPP_MR_2.5G, AR_MXP,
AR_XP, AR_XPE, or 10x10G-LC
AR_XP
card is installed. You can edit the
AR_XPE splitter protection group name.
10x10G-LC
OTU2_XP A splitter protection group is

configurable for the OTU2_XP
card. You can create a splitter
protection group on ports 3 and 4
of the OTU2_XP card using the
NTP-G199 Creating a Splitter
Protection Group, on page 345.
1+1 GE_XP In the Layer 2 (L2) card mode

1+1 protection is provided to
10GE_XP protect the card against client port
GE_XPE and card failure.
10GE_XPE

Purpose This procedure creates a splitter protection group
between the trunk ports of an OTU2_XP card. For
additional information about splitter protection, see
the "Splitter Protection" section.
Tools/Equipment Installed OTU2_XP card

Cisco TransportPlanner Traffic Matrix
Prerequisite Procedures In the Hardware Installation Guide:

• NTP-G15 Install the Common Control Cards
• NTP-G14 Install DWDM Equipment
Reports and Files
345
Note A splitter protection group is automatically created when a TXPP_MR_2.5G, MXPP_MR_2.5G, or PSM
card is installed. You can edit the splitter protection group name for these cards. The splitter protection
group is deleted when you delete the TXPP_MR_2.5G, MXPP_MR_2.5G, or PSM card.
Note Splitter protection is available for the OTU2_XP card when it is provisioned in Transponder configuration
only. In a splitter-protected Transponder configuration, Port 1 is the client port, Port 3 is the working
trunk port, and Port 4 is the standby trunk port.
Note For SONET or SDH payloads, Loss of Pointer Path (LOP-P) alarms can occur on a split signal if the ports
are not in a splitter protection group.
Procedure
Step 1 View the Cisco TransportPlanner Traffic Matrix (see the Cisco Transport Planner Node Setup Information
and Files table) for your site. Verify which OTU2_XP card needs a splitter protection group. (Cards requiring
splitter protection are indicated with “Splitter” in the Traffic Matrix table Protection Type column. Refer to
the Cisco Transport Planner DWDM Operations Guide for more information.)
Step 2 Verify that the OTU2_XP card is installed according to the requirements specified in Cable Connections for
Y-Cable Protection of One Client Signal
Step 3 Verify that the pluggable port (SFP or XFP) slot is provisioned for the same payload rate as the pluggable
port on the OTU2_XP card where you will create the splitter protection group:
a) Display the OTU2_XP card in card view.
b) Click the Provisioning > Pluggable Port Module tabs.
c) Verify that a pluggable port (SFP or XFP) slot is provisioned in the Pluggable Port Module area, and that
the payload rate of the pluggable port (SFP or XFP) slot is same as the payload rate of the pluggable port
on the OTU2_XP card provisioned in the Pluggable Ports area. If they are not the same, you must either
delete the provisioned rate and create a new rate to match using the DLP-G725 Preprovisioning PPM Slot
task or replace the pluggable port (SFP or XFP) using the DLP-G728 Remove PPM from the Line Card
task.
Step 4 In node view (single-shelf mode) or shelf view (multishelf view), click the Provisioning > Protection tabs.
Type—Choose Splitter from the drop-down list.
346
NTP-G198 Creating 1+1 Protection for Cards
Protect Card—From the drop-down list, choose the port that will be the standby or protection port to the
active port. The list displays the available OTU2_XP ports. If transponder or muxponder cards are not
installed or if the trunk ports of the card are part of a regenerator group, no ports appear in the drop-
down list.
After you choose the protect port, a list of available working ports appear in the Available Cards list.
If no cards are available, no ports appear. If this occurs, you cannot complete this task until you install
the physical cards or preprovision the slots using the DLP-G353 Preprovisioning a Slot.
Step 7 From the Available Cards list, select the port that will be protected by the port you selected in Protect Cards.
Click the top arrow button to move the port to the Working Cards list.
Revertive—Check this check box if you want traffic to revert to the working port after failure
conditions remain corrected for the amount of time entered in the Reversion Time field.
switch are cleared.
NoteThe Bidirectional Switching option is not applicable for splitter protection groups.
Step 9 Click OK.

Step 10 Repeat this procedure for every splitter protection group indicated in the Cisco TransportPlanner Traffic
Matrix.
NTP-G198 Creating 1+1 Protection for Cards

Purpose This procedure creates a 1+1 protection group to
protect against client port and card failure of GE_XP,
10GE_XP, GE_XPE, 10GE_XPE cards.
Prerequisite Procedures In the Hardware Installation Guide:

Reports and Files
347
DLP-G461 Creating a 1+1 Protection Group for Cards
Procedure
Step 1 Verify that the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card is installed according to the
requirements specified in Cable Connections for Y-Cable Protection of One Client Signal
Step 2 Complete the NTP-G242 Creating an Internal Patchcord Manually by selecting the Trunk to Trunk
(L2) option, at the trunk port where you want to create 1+1 protection.
Step 3 Complete the DLP-G461 Creating a 1+1 Protection Group for Cards, on page 348 to create a protection group.
Step 4 Configure the standby port behavior, by setting the Protection Action to None or Squelch. For detailed
information on how to configure the standby port behavior, see the DLP-G380 Provisioning Ethernet
Settings, on page 579 task.
Note Do not enable squelch in a 1 + 1 protection group, if the 100FX, 100LX SFP, and ONS-SE-ZE-EL
SFP is used in the protection group and is connected to the peer via the parallel cable (not Y-cable)
Note When you configure L2 1 + 1 protection on 10GE_XP and 10GE_XPE cards, set the Protection
Action to None on the client ports. Setting the Protection Action as Squelch results in
unexpected switching behavior.
Step 5 Configure the standby and active port speed, by setting the mode parameter to Auto or 1000 or any other
values. For detailed information on how to configure the standby port behavior, see the DLP-G380
Provisioning Ethernet Settings, on page 579 task.
DLP-G461 Creating a 1+1 Protection Group for Cards

Purpose This procedure creates a 1+1 protection group for
GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE slots
where internal patchcords were created.
Prerequisite Procedures DLP-G344 Verifying Provisionable and Internal

Patchcords
Procedure
Step 1 In node view (single-shelf mode) or multishelf view (multishelf mode), click the Provisioning >
Protection tabs.
348
NTP-G98 Provisioning the 2.5G Multirate Transponder Card Line Settings and PM Parameter Thresholds
Type—Choose L2 1+1 (port) from the drop-down list.
Protect Port—From the drop-down list, choose the port that will be the standby or protection port for the
active port. The list displays the available transponder or muxponder ports. If transponder or
muxponder cards are not installed, no ports appear in the drop-down list.
After you choose the protect port, a list of available working ports appear in the Available Ports list. If no
cards are available, no ports appear. If this occurs, you cannot complete this task until you install the
physical cards or preprovision the slots using the DLP-G353 Preprovisioning a Slot task.
Step 4 From the Available Ports list, select the port that will be protected by the port you selected in the
Protected Port drop-down list. Click the top arrow button to move the port to the Working Ports list.
Revertive—Check this check box if you want traffic to revert to the working port after failure
conditions remain corrected for the amount of time entered in the Reversion Time field.
switch are cleared.
The bidirectional switching option is available for SONET and SDH 1+1 protection groups.
Step 6 Click OK.
Step 7 Repeat this procedure for every 1+1 protection group indicated in the Cisco TransportPlanner Traffic Matrix.
NTP-G98 Provisioning the 2.5G Multirate Transponder

Card Line Settings and PM Parameter Thresholds
Purpose This procedure changes the line and threshold settings
for TXP_MR_2.5G and TXPP_MR_2.5G transponder
cards.
Prerequisite Procedures DLP-G723 Install PPM on a Line Card

DLP-G726 Preprovisioning a Multirate PPM (if
necessary)
DLP-G278 Provisioning the Optical Line Rate, on
page 321
349
DLP-G229 Changing the 2.5G or 10G Transponder Card Settings
Procedure
Step 1 As needed, complete the NTP-G103 Backing Up the Database task to preserve the existing transmission
settings.
Step 2 Perform any of the following tasks as needed:
DLP-G229 Changing the 2.5G or 10G Transponder Card Settings, on page 350
DLP-G230 Changing the 2.5G Multirate Transponder Line Settings, on page 353
DLP-G231 Changing the 2.5G Multirate Transponder Line Section Trace Settings, on page 356
DLP-G232 Changing the Multirate Transponder SONET or SDH Line Threshold Settings, on page 359
DLP-G320 Changing the 2.5G Multirate Transponder Line RMON Thresholds, on page 364
DLP-G305 Provisioning the 2.5G Multirate Transponder Trunk Port Alarm and TCA Thresholds, on
page 366
DLP-G306 Provisioning the 2.5G Multirate Transponder Client Port Alarm and TCA Thresholds, on
page 368
DLP-G234 Changing the Multirate Transponder OTN Settings, on page 372
DLP-G367 Changing the Multirate Transponder Trunk Wavelength Settings, on page 357

Purpose This task changes the card settings for TXP_MR_2.5G
and TXPP_MR_2.5G, TXP_MR_10G,
TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L,
and TXP_MR_10EX_C transponder cards.
350
Procedure
change the card settings.
Step 3 Modify any of the settings described in the following table.
Note The Card subtab Framing Type and Tunable Wavelengths fields are display-only. Framing Type
shows the card framing type, either SONET or SDH, depending on whether the card is installed
in an ANSI or ETSI chassis. The Tunable Wavelengths field shows the tunable wavelengths for
the physical TXP_MR_2.5G or TXPP_MR_2.5G that is installed.
Table 124: 2.5G or 10G Transponder Card Settings

Termination Mode Sets the mode of operation (option Transparent
only supported for SONET/SDH
Section (ANSI) or
payloads).
Regeneration Section (ETSI) -
Only for TXP_MR_2.5G,
TXPP_MR_2.5G, and
TXP_MR_10E.
Line (ANSI) or Multiplex
Section (ETSI)
AIS/Squelch Configuration (TXP_MR_10E, TXP_MR_10E_C, Squelch

TXP_MR_10E_L, or
AIS
TXP_MR_10EX_C only) Sets the
transparent termination mode
configuration.
351

Regeneration Peer Slot Sets the slot containing another None
multirate card to create a
1
regeneration peer group. A
regeneration peer group facilitates 2
the management of two multirate
cards that are needed to perform a 3
complete signal regeneration. 4
The regeneration peer group
5
synchronizes provisioning of the
two cards. Payload type and ITU-T 6
G.709 optical transport network
(OTN) changes made on one 12
multirate card are reflected on the 13
peer multirate card.
Note Y-cable protection 14
groups cannot be 15
created on TXP cards
that are in a regeneration 16
peer group. 17
Regeneration Group Name Sets the regeneration peer group User defined
name.
Tunable Wavelengths (Only for 10G multirate —

transponder cards) Shows the
supported wavelengths of the trunk
port after the card is installed. For
the TXP_MR_10E_C, or
TXP_MR_10E_L cards, the first
and last supported wavelength,
frequency spacing, and number of
supported wavelengths are shown
in the format: first wavelength-last
wavelength-frequency
spacing-number of supported
wavelengths. For example, the
TXP_MR_10E_C card would
show:
1529.55nm-1561.83nm-50gHz-82.
The TXP_MR_10E show the four
wavelengths supported by the card
that is installed. The
TXP_MR_10G show the two
that is installed.
Step 4 Click Apply.
352
DLP-G230 Changing the 2.5G Multirate Transponder Line Settings

Purpose This task changes the line settings for the client port
of the TXP_MR_2.5G and TXPP_MR_2.5G
transponder cards.
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the TXP_MR_2.5G or
TXPP_MR_2.5G card where you want to change the line settings.
Step 2 Click the Provisioning > Line > SONET tabs.
Note The 2.5G multirate transponder trunk settings are provisioned in the DLP-G305 Provisioning the
2.5G Multirate Transponder Trunk Port Alarm and TCA Thresholds, on page 366.
Table 125: TXP_MR_2.5G and TXPP_MR_2.5G Transponder Card Line Settings

Port (Display only) Displays the port 1
number.
2 (Trunk)
3 (Trunk) (TXPP_MR_2.5G
card only)
Port Name The user can assign a logical name User-defined. Name can be up
for each of the ports shown by to 80 alphanumeric/ special
filling in this field. characters. Blank by default.
353

Admin State Sets the port service state unless IS (ANSI) or Unlocked (ETSI)
network conditions prevent the
IS,AINS (ANSI) or
change. For more information about
Unlocked,automaticInService
administrative states, see the
Administrative and Service States (ETSI)
document. OOS,DSBLD (ANSI) or
Locked,disabled (ETSI)
OOS,MT (ANSI) or
Locked,maintenance (ETSI)
Service State (Display only) Identifies the IS-NR (ANSI) or

autonomously generated state that Unlocked-enabled (ETSI)
gives the overall condition of the
OOS-AU,AINS (ANSI) or
port. Service states appear in the
Unlocked-disabled,
format: Primary State-Primary State
Qualifier, Secondary State. For automaticInService (ETSI)
more information about service OOS-MA,DSBLD (ANSI) or
states, see the Administrative and Locked-enabled,disabled
Service States document. (ETSI)
OOS-MA,MT (ANSI) or
Locked-enabled,maintenance
(ETSI)
SF BER (OC-N and STM-N payloads only) 1E-3

Sets the signal fail bit error rate.
1E-4
1E-5
SD BER (OC-N and STM-N payloads only) 1E-5

Sets the signal degrade bit error
1E-6
rate.
1E-7
1E-8
1E-9
ALS Mode Sets the automatic laser shutdown • Disabled (default)

(ALS) function.
• Auto Restart
• Manual Restart
• Manual Restart for Test
354
Reach Displays the optical reach distance Options: ANSI/ETSI

of the client port. • Autoprovision/Autoprovision
(default)
• SR
• SR 1/I-1—Short reach up to
2-km distance
• IR 1/S1—Intermediate reach,
up to 15-km distance
• IR 2/S2—Intermediate reach
• LR 1/L1—long reach, up to
40-km distance
80-km distance
80-km distance
Wavelength Displays the wavelength of the • First Tunable Wavelength

client port.
• Further wavelengths: 1310 nm
through 1560.61 nm, 100-GHz
ITU spacing; coarse
wavelength division
multiplexing (CWDM)
spacing
Note: supported wavelengths are

marked by asterisks (**)
AINS Soak (OC-N and STM-N payloads only) • Duration of valid input signal,
Sets the automatic in-service soak in hh.mm format, after which
period. the card becomes in service
(IS) automatically
• 0 to 48 hours, 15-minute
increments
Type (OC-N and STM-N payloads only) • SONET

The optical transport type.
• SDH
Step 4 Click Apply.

355
DLP-G231 Changing the 2.5G Multirate Transponder Line Section Trace Settings
DLP-G231Changingthe2.5GMultirateTransponderLineSectionTraceSettings
Purpose This task changes the section trace settings for
TXP_MR_2.5G and TXPP_MR_2.5G transponder
cards.
Note This task only applies to SONET services.
Procedure
TXPP_MR_2.5G card where you want to change the section trace settings.
Step 2 Click the Provisioning > Line > Section Trace tabs.
Table 126: TXP_MR_2.5G and TXPP_MR_2.5G Transponder Card Section Trace Settings

Port (Display only) Port number. 1
2 (Trunk)
3 (Trunk) (TXPP_MR_2.5G
only)
Received Trace Mode Sets the trace mode. Off/None

Manual
Disable AIS/RDI on TIM-S If an TIM on Section overhead Checked (AIS/RDI on TIM-S

alarm arises because of a J0 is disabled)
overhead string mismatch, no alarm
indication signal is sent to Unchecked (AIS/RDI on
downstream nodes if this box is TIM-S is not disabled)
checked.
356
DLP-G367 Changing the Multirate Transponder Trunk Wavelength Settings
Transmit Section Trace String Size Sets the trace string size. • 1 byte
• 16 byte
Transmit Displays the current transmit string; String of trace string size
sets a new transmit string. You can
click the button on the right to
change the display. Its title changes,
based on the current display mode.
Click Hex to change the display to
hexadecimal (button changes to
ASCII); click ASCII to change the
display to ASCII (button changes
to Hex).
Expected Displays the current expected String of trace string size

string; sets a new expected string.
You can click the button on the
right to change the display. Its title
changes, based on the current
display mode. Click Hex to change
the display to hexadecimal (button
changes to ASCII); click ASCII to
change the display to ASCII (button
changes to Hex).
Received (Display only) Displays the current String of trace string size
received string. You can click
Refresh to manually refresh this
display, or check the Auto-refresh
every 5 sec check box to keep this
display updated automatically.
Auto-refresh If checked, automatically refreshes Checked/unchecked (default)

the display every 5 seconds.
Step 4 Click Apply.


Purpose This task changes the trunk wavelength settings for
the TXP_MR_2.5G and TXPP_MR_2.5G,
TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C,
TXP_MR_10E_L, and TXP_MR_10EX_C cards.
357
Note Before modifying the wavelength settings, change the port state to OOS,DSBLD (for ANSI) or
Locked,disabled (for ETSI) and delete the circuit and patchcord provisioning present on the port. Payload
or communication channel provisioning can be retained.
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the multirate card where you
want to change the trunk wavelength settings.
Step 2 Click the Provisioning > Line > Wavelength Trunk Settings tabs.
Step 3 Modify any of the settings as described in the following table.
Table 127: Multirate Transponder Card Wavelength Trunk Settings

Port (Display only) Displays the port • 2 (Trunk)
number.
• 3 (Trunk) (TXPP_MR_2.5G
only)
Band Indicates the wavelength band that C—The C-band wavelengths

can be provisioned. If the physical are available in the
TXP_MR_10G, TXP_MR_10E, Wavelength field.
TXP_MR_10E_C,
TXP_MR_10E_L, and L—The L-band wavelengths
TXP_MR_10EX_C is installed, this are available in the
field is display-only. Wavelength field.
Even/Odd Sets the wavelengths available for Even—Displays even C-band

provisioning for TXP_MR_10E_C, or L-band wavelengths in the
and TXP_MR_10E_L cards. Wavelength field.
Odd—Displays odd C-band or
L-band wavelengths in the
Wavelength field.
358
DLP-G232 Changing the Multirate Transponder SONET or SDH Line Threshold Settings

Wavelength The wavelength provisioned for First Tunable Wavelength
the
Further wavelengths in
trunk.
100-GHz ITU-T C-band or
L-band spacing, depending
on the card that is installed.
For TXP_MR_10G and
TXP_MR_10E cards, the
wavelengths carried by the
card are identified with two
asterisks. The wavelengths
supported by the SFPs/XFPs
plugged to the card are
identified with two asterisks.
Other wavelengths have a
dark grey background. If the
card is not installed, all
wavelengths appear with a
dark grey background.
Step 4 Click Apply.

DLP-G232 Changing the Multirate Transponder SONET or SDH

Line Threshold Settings
Purpose This task changes the line threshold settings for
TXP_MR_2.5G and TXPP_MR_2.5G transponder
cards carrying OC-3/STM-1, OC-12/STM-4, and
OC-48/STM-16 payloads. You can also use this task
to change the line threshold settings for
TXP_MR_10E_L, and TXP_MR_10EX_C
transponder cards carrying SONET or SDH payloads,
including the physical 10G Ethernet WAN Phy
payload.
359
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the multirate transponder
card where you want to change the line threshold settings.
Step 2 Click the Provisioning > Line Thresholds tabs.
Note You must modify Near End and Far End independently; 15 Min and 1 Day independently; and
Line and Section independently. To do so, choose the appropriate radio button and click Refresh.
Step 3 Modify any of the settings in the following table.

Note Some parameters and options in the following table do not apply to all the
multirate cards. If a parameter or option does not apply, that parameter or option
does not appear in CTC.
Table 128: Multirate Transponder Card Line Thresholds Settings
Parameter Description Options - ANSI Options - ETSI

Port (Display only) Port 1 1
number
2 (Trunk) 2 (Trunk)
3 (Trunk) 3 (Trunk)
(TXPP_MR_2.5G (TXPP_MR_2.5G
only) only)
EB Path Errored Block Numeric. Threshold Numeric. Threshold

indicates that one or more display options include: display options include:
bits are in error within a Direction—Near End Direction—Near End
block
or Far End or Far End
Interval—15 Min Interval—15 Min
(minutes) or 1 day (minutes) or 1 day
Types—Line or Types—Multiplex
Section (near end Section or
only) Regeneration Section
(near end only)
Choose an option in
each category and click Choose an option in
Refresh. each category and click
Refresh.
360

CV Coding violations Numeric. Threshold —
display options include:
• Direction—Near End
or Far End
• Interval—15 Min
(minutes) or 1 day
• Types—Line or
Section (near end
only)
Choose an option in each

category and click
Refresh.
ES Errored seconds Numeric. Threshold Numeric. Threshold

display options include: display options include:
• Direction—Near End Direction—Near End
• Interval—15 Min Interval—15 Min
• Types—Line or Types—Multiplex
(near end only)
category and click Choose an option in
Refresh.
SES Severely errored seconds Numeric. Threshold Numeric. Threshold
(near end only)
Refresh.
361
FC (Line or Multiplex Section Numeric. Threshold —

only) Failure count display options include:
or Far End
(minutes) or 1 day
• Types—Line or
Section (near end
only)

category and click
Refresh.
SEFS (Near End Section or Numeric. Threshold —

Regeneration Section display options include:
only) Severely errored
framing seconds
or Far End
(minutes) or 1 day
• Types—Line or
Section (near end
only)

category and click
Refresh.
362

UAS Unavailable seconds Numeric. Threshold Numeric. Threshold
• Types—SM (OTUk) Types—SM (OTUk)
or PM (ODUk) for or PM (ODUk) for
2.5G cards and Line 2.5G cards and
or Section (near end Multiplex Section or
only) for 10G cards. Regeneration Section
(near end only) for
Choose an option in each 10G cards.
category and click
Refresh. Choose an option in
each category and click
Refresh.
BBE Background block errors — Numeric. Threshold
or Far End
(minutes) or 1 day
• Types—SM (OTUk)
or PM (ODUk) for
2.5G cards and
Multiplex Section or
Regeneration Section
(near end only) for
10G cards

category and click
Refresh.
363
DLP-G320 Changing the 2.5G Multirate Transponder Line RMON Thresholds
OFS (Near End Section or — Numeric. Threshold

only) Out of frame
seconds
or Far End
(minutes) or 1 day
• Types—Line or
Section (near end
only)

category and click
Refresh.
Step 4 Click Apply.


Purpose This task changes the line remote monitoring (RMON)
threshold settings for TXP_MR_2.5G and
TXPP_MR_2.5G transponder cards carrying the 1G
Ethernet or 1G FC/FICON payloads.
Procedure
Step 1 In card view, display the TXP_MR_2.5G or TXPP_MR_2.5G card where you want to change the line threshold
settings.
Step 2 Click the Provisioning > Line Thresholds > RMON Thresholds tabs.
Step 3 Click Create. The Create Threshold dialog box appears.
Step 4 From the Port drop-down list, choose the applicable port.
Step 5 From the Variable drop-down list, choose an Ethernet variable. See the following table for a list of available
Ethernet variables.
364
Table 129: TXP_MR_2.5G and TXPP_MR_2.5G Card 1G Ethernet and 1G FC/FICONThresholds
Variable Description
ifInErrors Number of inbound packets that contained errors

preventing them from being delivered to a higher-layer
protocol.
rxTotalPkts Total number of received packets.
8b10bStatsEncodingDispErrors Number of IETF 8b10b disparity violations on the

Fibre Channel line side.
8b10bIdleOrderedSets Number of received packets containing idle ordered

sets.
8b10bNonIdleOrderedSets Number of received packets containing non-idle

ordered sets.
8b10bDataOrderedSets Number of received packets containing data ordered

sets.
Step 6 From the Alarm Type drop-down list, indicate whether the event will be triggered by the rising threshold, the
falling threshold, or both the rising and falling thresholds.
Step 7 From the Sample Type drop-down list, choose either Relative or Absolute. Relative restricts the threshold
to use the number of occurrences in the user-set sample period. Absolute sets the threshold to use the total
number of occurrences, regardless of time period.
Step 8 Enter the appropriate number of seconds for the Sample Period.
Step 9 Enter the appropriate number of occurrences for the Rising Threshold.
For a rising type of alarm, the measured value must move from below the falling threshold to above the rising
threshold. For example, if a network is running below a rising threshold of 1000 collisions every 15 seconds
and a problem causes 1001 collisions in 15 seconds, the excess occurrences trigger an alarm.
Step 10 Enter the appropriate number of occurrences in the Falling Threshold field. In most cases a falling threshold
is set lower than the rising threshold.
A falling threshold is the counterpart to a rising threshold. When the number of occurrences is above the rising
threshold and then drops below a falling threshold, it resets the rising threshold. For example, when the network
problem that caused 1001 collisions in 15 seconds subsides and creates only 799 collisions in 15 seconds,
occurrences fall below a falling threshold of 800 collisions. This resets the rising threshold so that if network
collisions again spike over a 1000 per 15-second period, an event again triggers when the rising threshold is
crossed. An event is triggered only the first time a rising threshold is exceeded (otherwise, a single network
problem might cause a rising threshold to be exceeded multiple times and cause a flood of events).
Step 11 Click OK.
365
DLP-G305 Provisioning the 2.5G Multirate Transponder Trunk Port Alarm and TCA Thresholds
DLP-G305 Provisioning the 2.5G Multirate Transponder Trunk

Port Alarm and TCA Thresholds
Purpose This task changes the TXP_MR_2.5G and
TXPP_MR_2.5G trunk port alarm and threshold
crossing alert (TCA) thresholds.
Note In this task, trunk port refers to Port 2 for TXP_MR_2.5G cards, and to Ports 2 and 3 for TXPP_MR_2.5G
cards.
Procedure
TXPP_MR_2.5G card where you want to change the trunk port alarm and TCA settings.
Step 2 Click the Provisioning > Pluggable Port Modules tab. Under Pluggable Ports, record the Rate that is
provisioned.
Step 3 Look up the rate in the following table and note whether it is 2R or 3R.
Table 130: 2R and 3R Mode and ITU-T G.709 Compliance by Client Interface
OC-48/STM-16 2.488 Gbps 3R On or Off
DV-6000 2.38 Gbps 2R —
2 Gigabit Fibre Channel 2.125 Gbps 3R (no monitoring) On or Off

(2G-FC)/fiber
connectivity (FICON)
High-Definition 1.48 Gbps 2R —

Television (HDTV)
Gigabit Ethernet (GE) 1.25 Gbps 3R On or Off

(1G-FC)/FICON
366
DLP-G305 Provisioning the 2.5G Multirate Transponder Trunk Port Alarm and TCA Thresholds
Enterprise System 200 Mbps 2R —

Connection (ESCON)
SDI/D1 video 270 Mbps 2R —
ISC-1 Compact 1.06 Gbps 3R Off
ISC-3 1.06 or 2.125 Gbps 2R —
ETR_CLO 16 Mbps 2R —
Step 4 Click the Provisioning > Optics Thresholds tabs.

Step 5 Under Types, verify that the TCA radio button is checked. If not, check it and click Refresh.
Step 6 Referring to the following table, verify the trunk port TCA thresholds for RX Power High and RX Power
Low depending on whether the rate is 2R or 3R. Provision new thresholds as needed by double-clicking
the threshold value you want to change, deleting it, entering a new value, and hitting Enter.
Note Do not modify the Laser Bias parameters.
Note You must modify 15 Min and 1 Day independently. To do so, choose the appropriate radio
button and click Refresh.
Table 131: TXP_MR_2.5G and TXPP_MR_2.5G Trunk Port TCA Thresholds
Signal TCA RX Power Low TCA RX Power High
3R –23 dBm –9 dBm
2R –24 dBm –9 dBm
Step 7 Click Apply.

Step 8 Under Types, click the Alarm radio button and click Refresh.
Step 9 Verify the trunk port Alarm thresholds for RX Power High is –7 dBm, and for RX Power Low is –26 dBm.
Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it,
entering a new value, and hitting Enter.
Step 10 Click Apply.
367
DLP-G306 Provisioning the 2.5G Multirate Transponder Client

Purpose This task provisions the client port alarm and TCA
thresholds for the TXP_MR_2.5G and
TXPP_MR_2.5G cards.
Prerequisite Procedures DLP-G278 Provisioning the Optical Line Rate, on

page 321
DLP-G46 Log into CTC
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the TXP_MR_2.5G
or TXPP_MR_2.5G card where you want to change the client port alarm and TCA settings.
Step 2 Click the Provisioning > Optics Thresholds tabs. The TCA thresholds are shown by default.
Step 3 Referring to the following table, verify the Port 1 (client) TCA thresholds for RX Power High, RX Power
Low, TX Power High, and TX Power Low based on the client interface at the other end. Provision new
thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a
new value, and hitting Enter.
Note The hardware device that plugs into a TXP, MXP, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, or
ADM-10G card faceplate to provide a fiber interface to the card is called a Small Form-factor
Pluggable (SFP or XFP). In CTC, SFPs and XFPs are called pluggable port modules (PPMs).
SFPs/XFPs are hot-swappable input/output devices that plug into a port to link the port with the
fiber-optic network. Multirate PPMs have provisionable port rates and payloads. For more
information about SFPs and XFPs, see the SFP, SFP+, QSFP+, XFP, CXP, CFP, CFP2 and
CPAK Modules, on page 310.
Table 132: TXP_MR_2.5G and TXPP_MR_2.5G Card Client Interface TCA Thresholds
Port Type (by Pluggable Port TCA RX Power TCA RX Power TCA TX Power TCA TX Power
CTC) Module (SFP) Low High Low High
OC-3 15454-SFP3-1-IR –23 –8 –21 –2
368
STM-1 15454E-SFP-L.1.1 –24 –10 –21 –2
OC-12 15454-SFP12-4-IR –28 –7 –21 –2
STM-4 15454E-SFP-L.4.1 –28 –8 –21 –2
OC-48 ONS-SE-2G-S1 –18 –3 –16 3
15454-SFP-OC48-IR –18 0 –11 6
STM-16 ONS-SE-2G-S1 –18 –3 –16 3

15454E-SFP-L.16.1
ONE_GE 15454-SFP-GEFC-SX –17 0 –16 3

15454E-SFP-GEFC-S
ONS-SE-G2F-SX
15454-SFP-GE+-LX –20 –3 –16 3

15454E-SFP-GE+-LX
ONS-SE-G2F-LX
ESCON 15454-SFP-200 –21 –14 –35 –8

15454E-SFP-200
ONS-SE-200-MM
DV6000 15454-SFP-OC48-IR –18 0 –11 6
15454E-SFP-L.16.1 –18 –3 –16 3
SDI_D1_ 15454-SFP12-4-IR –28 –7 –21 –2

VIDEO
15454E-SFP-L.4.1 –28 –8 –21 –2
HDTV 15454-SFP-GE+-LX –20 –3 –16 3

15454E-SFP-GE+-LX
ONS-SE-G2F-LX
PASS-THRU 2R MODE (not — — — —

specified)
FC1G 15454-SFP-GEFC-SX –17 0 –16 3

15454E-SFP-GEFC-S
ONS-SE-G2F-SX
15454-SFP-GE+-LX –20 –3 –16 3

15454E-SFP-GE+-LX
ONS-SE-G2F-LX
369
FC2G 15454-SFP-GEFC-SX –15 0 –16 3

15454E-SFP-GEFC-S
ONS-SE-G2F-SX
15454-SFP-GE+-LX –20 –3 –16 3

15454E-SFP-GE+-LX
ONS-SE-G2F-LX
FICON1G 15454-SFP-GEFC-SX –17 0 –16 3

15454E-SFP-GEFC-S
ONS-SE-G2F-SX
15454-SFP-GE+-LX –20 –3 –16 3

15454E-SFP-GE+-LX
ONS-SE-G2F-LX

15454E-SFP-GEFC-S
ONS-SE-G2F-SX
15454-SFP-GE+-LX –20 –3 –16 3

15454E-SFP-GE+-LX
ONS-SE-G2F-LX
ETR_CLO 15454-SFP-200 –17 0 –16 3

15454E-SFP-200
ONS-SE-200-MM
ISC compat 15454-SFP-GE+-LX –20 –3 –16 3

15454E-SFP-GE+-LX
ONS-SE-G2F-LX
ISC peer 15454-SFP-GE+-LX –20 –3 –16 3

15454E-SFP-GE+-LX
ONS-SE-G2F-LX
Step 4 Click Apply.

Step 6 Referring to the following table, verify the Alarm thresholds for RX Power High, RX Power Low, TX Power
High, and TX Power Low based on the client interface that is provisioned. Provision new thresholds as needed
by double-clicking the threshold value you want to change, deleting it, entering a new value, and hitting Enter.
Table 133: TXP_MR_2.5G and TXPP_MR_2.5G Card Client Interface Alarm Thresholds
Port Type (by Pluggable Port Alarm RX Power Alarm RX Power Alarm TX Power Alarm TX Power
OC-3 15454-SFP3-1-IR –26 –5 –17 –6
STM-1 15454E-SFP-L.1.1 –27 –7 –17 –6
370
OC-12 15454-SFP12-4-IR –31 –4 –17 –6
STM-4 15454E-SFP-L.4.1 –31 –5 –17 –6
OC-48 ONS-SE-2G-S1 –21 0 –12 –1
15454-SFP-OC48-IR –21 3 –7 2
STM-16 ONS-SE-2G-S1 –21 0 –12 –1

15454E-SFP-L.16.1
ONE_GE 15454-SFP-GEFC-SX –20 3 –12 –2

15454E-SFP-GEFC-S
ONS-SE-G2F-SX
15454-SFP-GE+-LX –23 0 –12 –1

15454E-SFP-GE+-LX
ONS-SE-G2F-LX
ESCON 15454-SFP-200 –24 –11 –31 –12

15454E-SFP-200
ONS-SE-200-MM
DV6000 15454-SFP-OC48-IR –21 3 –7 2
15454E-SFP-L.16.1 –21 0 –12 –5
SDI_D1_ 15454-SFP12-4-IR –31 –4 –17 –6

VIDEO
15454E-SFP-L.4.1 –31 –5 –17 –6
HDTV 15454-SFP-GE+-LX –23 0 –12 –1

15454E-SFP-GE+-LX
ONS-SE-G2F-LX
PASS-THRU 2R MODE (not — — — —

specified)
FC1G 15454-SFP-GEFC-SX –20 3 –12 –2

15454E-SFP-GEFC-S
ONS-SE-G2F-SX
15454-SFP-GE+-LX –23 0 –12 –1

15454E-SFP-GE+-LX
ONS-SE-G2F-LX
371
DLP-G234 Changing the Multirate Transponder OTN Settings
FC2G 15454-SFP-GEFC-SX –18 3 –12 –2

15454E-SFP-GEFC-S
ONS-SE-G2F-SX
15454-SFP-GE+-LX –23 0 –12 –1

15454E-SFP-GE+-LX
ONS-SE-G2F-LX
FICON1G 15454-SFP-GEFC-SX –20 3 –12 –2

15454E-SFP-GEFC-S
ONS-SE-G2F-SX
15454-SFP-GE+-LX –23 0 –12 –1

15454E-SFP-GE+-LX
ONS-SE-G2F-LX

15454E-SFP-GEFC-S
ONS-SE-G2F-SX
15454-SFP-GE+-LX –23 0 –12 –1

15454E-SFP-GE+-LX
ONS-SE-G2F-LX
ETR_CLO 15454-SFP-200 –20 3 –12 –2

15454E-SFP-200
ONS-SE-200-MM
ISC compat 15454-SFP-GE+-LX –23 0 –12 –1

15454E-SFP-GE+-LX
ONS-SE-G2F-LX
ISC peer 15454-SFP-GE+-LX –23 0 –12 –1

15454E-SFP-GE+-LX
ONS-SE-G2F-LX
Step 7 Click Apply.


Purpose This task changes the OTN settings for the
TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10G,
TXP_MR_10EX_C, 40E-TXP-C, and 40ME-TXP-C
transponder cards.
372
Procedure
change the OTN settings.
Step 2 Click the Provisioning > OTN tabs, then choose one of the following subtabs: OTN Lines, G.709
Thresholds, FEC Thresholds, or Trail Trace Identifier.
Step 3 Modify any of the settings described in the following tables.
Note You must modify Near End and Far End; 15 Min and 1 Day; and SM and PM settings independently.
To do so, choose the appropriate radio button and click Refresh.
Table 134: Multirate Transponder Card OTN Line Settings

Port (Display only) Displays the port • 1 (only when data rate is set
number. to OTU3)
• 2 (Trunk)
• 3 (Trunk) (TXPP_MR_2.5G)
G.709 OTN Sets the OTN lines according to Enable

ITU-T G.709. For
TXP-MR-10EX_C cards, the G.709 Disable
OTN should be enabled.
FEC Sets the OTN lines to forward error Enable—FEC is on.

correction (FEC). FEC mode can
be Disabled, Enabled, or, Enhanced Disable—FEC is off.
FEC mode can be enabled to Standard—(TXP_MR_10E,
provide greater range and lower bit 40E-TXP-C, and 40ME-
error rate. For TXP_MR_10E, TXP-C only) Standard FEC
40E-TXP-C, and 40ME-TXP-C is on.
cards, Standard is the same as
enabling FEC. For Enhanced—(TXP_MR_10E,
TXP-MR-10EX_C cards, the FEC 40E-TXP-C, and 40ME-
should be enabled. TXP-C only) Enhanced FEC
is on.
373
SF BER (Display only) The signal fail bit • 1E-5

error rate.
SD BER Sets the signal degrade bit error • 1E-5

rate.
• 1E-6
• 1E-7
• 1E-8
• 1E-9
Asynch/Synch Mapping (TXP_MR_10E only) Sets how the • Asynch mapping

ODUk (client payload) is mapped
to the optical channel (OTUk). • Synch mapping
Table 135: Multirate Transponder Card ITU-T G.709 Threshold Settings
Port (Display only) Port number. • 2 (Trunk)

ES Errored seconds Numeric. Can be set for Near End

or Far End, for 15-minute or
one-day intervals, or for SM
(OTUk) or PM (ODUk). Select a
bullet and click Refresh.
Note SM (OTUk) is the
ITU-T G.709 optical
channel transport unit
order of k overhead
frame used for
management and
performance
monitoring. PM (ODUk)
is the ITU-T G.709
optical channel data unit
order of k overhead
frame unit used for path
performance
monitoring.
SES Severely errored seconds Numeric. Can be set for Near End
374
UAS Unavailable seconds Numeric. Can be set for Near End

BBE Background block errors Numeric. Can be set for Near End
FC Failure counter Numeric. Can be set for Near End

Note Latency for a 1G-FC payload without ITU-T G.709 is 4 microseconds, and with ITU-T G.709 is
40 microseconds. Latency for a 2G-FC payload without ITU-T G.709 is 2 microseconds, and
with ITU-T G.709 is 20 microseconds. Consider these values when planning a FC network that is
sensitive to latency.
Table 136: Multirate Transponder Card FEC Threshold Settings
Port (Display only) Port number. • 2 (Trunk)

Bit Errors Corrected Sets the value for bit errors Numeric. Can be set for 15-minute
corrected during the selected time or one-day intervals.
period.
Uncorrectable Words Sets the value for uncorrectable Numeric. Can be set for 15-
words during the selected time minute or one-day intervals.
period.
Table 137: MultirateTransponder Card Trail Trace Identifier Settings
Port (Display only) Port number. • 1 (OTU3) for 40E-TXP-C and

40ME-TXP-C cards
• 2 (Trunk)
375

Level Sets the level. Section
Path

Manual
Disable AIS/RDI on TIM-S If a TIM on Section overhead alarm Checked (AIS/RDI on TIM-S
is raised because of a J0 overhead is disabled)
string mismatch, no alarm
Unchecked (AIS/RDI on
indication signal is sent to
downstream nodes if this box is TIM-S is enabled)
checked.
Transmit Displays the current transmit string; String of trace string size; trail trace
sets a new transmit string. You can identifier is 64 bytes in length.
to Hex Mode).

changes to Hex Mode).
panel updated.

the display every 5 minutes.
Step 4 Click Apply.
376
NTP-G96 Provisioning the 10G Multirate Transponder Card Line Settings, PM Parameters, and Thresholds
NTP-G96 Provisioning the 10G Multirate Transponder

Card Line Settings, PM Parameters, and Thresholds
for 10G multirate transponder cards including the
TXP_MR_10E_L, and TXP_MR_10EX_C cards.
Prerequisite Procedures • NTP-G179 Installing the Transponder and
Muxponder Cards
• DLP-G723 Install PPM on a Line Card
• DLP-G726 Preprovisioning a Multirate PPM (if
necessary)
• DLP-G278 Provisioning the Optical Line Rate,
on page 321
Note The TXP_MR_10G card does not support PPMs.
Procedure
Step 1 As needed, complete the NTP-G103 Backing Up the Database to preserve the existing transmission settings.
Step 2 If you are provisioning a TXP_MR_10G card, complete the DLP-G365 Provisioning the TXP_MR_10G
Data Rate, on page 378, and if you are provisioning a TXP_MR_10E or TXP_MR_10EX_C card, complete
the DLP-G712 Provisioning the TXP_MR_10E or TXP_MR_10EX_C Data Rate, on page 379. If not,
continue with the next step.
DLP-G229 Changing the 2.5G or 10G Transponder Card Settings, on page 350
DLP-G217 Changing the 10G Multirate Transponder Line Settings, on page 380
377
DLP-G365 Provisioning the TXP_MR_10G Data Rate
DLP-G218 Changing the 10G or 40G Multirate Transponder Line Section Trace Settings, on page 385
DLP-G232 Changing the Multirate Transponder SONET or SDH Line Threshold Settings, on page 359
DLP-G319 Changing the 10G Multirate Transponder Line RMON Thresholds for 10G Ethernet LAN
Phy Payloads, on page 388
DLP-G301 Provisioning the 10G Multirate Transponder Trunk Port Alarm and TCA Thresholds, on
page 392
DLP-G302 Provisioning the 10G Multirate Transponder Client Port Alarm and TCA Thresholds, on
page 393
DLP-G367 Changing the Multirate Transponder Trunk Wavelength Settings, on page 357
DLP-G365 Provisioning the TXP_MR_10G Data Rate

Purpose This task changes the TXP_MR_10G card data rate.
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the TXP_MR_10G card where
you want to change the card data rate settings.
Step 2 Click the Provisioning > Data Rate Selection tabs.
Step 3 Click Create.
Step 4 In the Create Port dialog box, choose one of the following data rates:
• SONET (ANSI) or SDH (ETSI) (including 10G Ethernet WAN Phy)
• 10G Ethernet LAN Phy
Step 5 Click Ok.

378
DLP-G712 Provisioning the TXP_MR_10E or TXP_MR_10EX_C Data Rate
DLP-G712 Provisioning the TXP_MR_10E or TXP_MR_10EX_C Data Rate

Purpose This task changes the TXP_MR_10E or
TXP_MR_10EX_C card data rate.
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the TXP_MR_10E or
TXP_MR_10EX_C card where you want to change the card data rate settings.
Step 3 In the Pluggable Port Modules area, click Create. The Create PPM dialog box appears.
Step 4 In the Create PPM dialog box, complete the following:
PPM—Choose the SFP you want to install from the drop-down list.
PPM Type—Choose the number of ports supported by your SFP from the drop-down list. If only one
port is supported, PPM (1 port) is the only option.
Step 5 Click OK. The newly created PPM appears in the Pluggable Port Modules area. The row in the Pluggable
Port Modules area turns white and the Actual Equipment Type column lists the equipment name.
Step 6 In the Pluggable Ports area, click Create. The Create Ports dialog box appears.
• SONET (ANSI) or SDH (ETSI) (including 10G Ethernet WAN Phy)
• 10G Ethernet LAN Phy
• 10G FIBER Channel
• (TXP-MR-10EX_C card only) IB_5G
Step 8 Click OK.

379
DLP-G217 Changing the 10G Multirate Transponder Line Settings

Purpose This task changes the line settings for TXP_MR_10G,
and TXP_MR_10EX_C cards.
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the TXP_MR_10G,
TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, or TXP_MR_10EX_C card where you want to change
the line settings.
Step 2 Click the Provisioning > Line > SONET/SDH/Ethernet tabs. SONET is the option for ANSI shelves
when 10G Ethernet WAN phy is the Pluggable Port Rate, SDH is the option for ETSI shelves when 10G
Ethernet WAN phy is the Pluggable Port Rate, and Ethernet is the option for ANSI or ETSI shelves when
10GE LAN Phy is the Pluggable Port Rate.
Note In the following table, some parameter tabs do not always apply to all 10G multirate
transponder cards. If a tab does not apply, it will not appear in CTC.
380
Table 138: TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, or TXP_MR_10EX_C Line Settings
Parameter Description ONS 15454 (ANSI) Options ONS 15454 SDH (ETSI)
Options
Port (Display only) Displays 1 (OC192) (10G 1 (STM-64) (10G

the port number. Ethernet WAN Phy) Ethernet WAN Phy)
(if TXP_MR_10G) (if TXP_MR_10G)
1 (TEN_GE) (if 1 (TEN_GE) (if
Ethernet LAN is Ethernet LAN is
provisioned on the provisioned on the
TXP_MR_10G card) TXP_MR_10G card)
1-1 (OC192) (10G 1-1 (STM-64) (10G
Ethernet WAN Phy Ethernet WAN Phy
on the on the
TXP_MR_10E card) TXP_MR_10E card)
1-1 (TEN_GE) (if 1-1 (TEN_GE) (if
Ethernet LAN is Ethernet LAN is
1-1 (FC10G) (if 10G 1-1 (FC10G) (if 10G
fiber channel is fiber channel is
2 (Trunk) 2 (Trunk)
(TXP_MR_10EX_C (TXP_MR_10EX_C
only) IB_5G only) IB_5G
Port Name Provides the ability to User-defined. Name User-defined. Name

assign the specified port a can be up to can be up to
name. alphanumeric/special alphanumeric/special
characters. Blank by characters. Blank by
default. default.
Admin State Sets the port service state. IS Unlocked

For more information Unlocked,automaticInService
IS,AINS
about administrative
states, see the OOS,DSBLD Locked,disabled
Administrative and
Service States document. OOS,MT Locked,maintenance
381
Options
Service State (Display only) Identifies • IS-NR • Unlocked-enabled

the autonomously
• OOS-AU,AINS • Unlocked-disabled,
generated state that gives
the overall condition of automaticInService
• OOS-MA,DSBLD
the port. Service states • Locked-enabled,disabled
appear in the format: • OOS-MA,MT
Primary State-Primary • Locked-enabled,maintenance
State Qualifier, Secondary
State. For more
information about service
states, see the
Administrative and
Service States document.
SF BER (SONET [ANSI] or SDH • 1E-3 • 1E-3

[ETSI] including 10G
Ethernet WAN Phy only) • 1E-4 • 1E-4
Sets the signal fail bit • 1E-5 • 1E-5
error rate.
SD BER (SONET [ANSI] or SDH • 1E-5 • 1E-5

Ethernet WAN Phy only) • 1E-6 • 1E-6
Sets the signal degrade bit • 1E-7 • 1E-7
error rate.
• 1E-8 • 1E-8
• 1E-9 • 1E-9
Type (SONET [ANSI] or SDH • SONET • SONET

Ethernet WAN Phy only) • SDH • SDH
The optical transport type.
382
Options
ALS Mode Sets the ALS function • Disabled (default): • Disabled (default):
mode. The DWDM ALS is off; the laser ALS is off; the laser
transmitter supports ALS is not automatically is not automatically
according to ITU-T G.644 shut down when shut down when
(06/99). ALS can be traffic outages (LOS) traffic outages (LOS)
disabled, or it can be set occur. occur.
for one of three mode
options. • Auto Restart: ALS is • Auto Restart: ALS is
on; the laser on; the laser
automatically shuts automatically shuts
down when traffic down when traffic
outages (LOS) occur. outages (LOS) occur.
It automatically It automatically
restarts when the restarts when the
conditions that conditions that
caused the outage are caused the outage are
resolved. resolved.
• Manual Restart: ALS • Manual Restart: ALS
is on; the laser is on; the laser
However, the laser However, the laser
must be manually must be manually
restarted when restarted when
resolved. resolved.
• Manual Restart for • Manual Restart for
Test: Manually Test: Manually
restarts the laser for restarts the laser for
testing. testing.
AINS Soak (SONET [ANSI] or SDH • Duration of valid • Duration of valid

[ETSI] including 10G input signal, in input signal, in
Ethernet WAN Phy only) hh.mm format, after hh.mm format, after
Sets the automatic which the card which the card
in-service soak period. becomes in service becomes in service
Double-click the time and (IS) automatically (IS) automatically
use the up and down
arrows to change settings. • 0 to 48 hours, • 0 to 48 hours,
15-minute 15-minute
increments increments
383
Options
ProvidesSync (TXP_MR_10E, OC192 Checked or unchecked Checked or unchecked

only) Sets the
ProvidesSync card
parameter. If checked, the
card is provisioned as a
network element (NE)
timing reference.
SyncMsgIn (TXP_MR_10E, OC192 Checked or unchecked Checked or unchecked

only) Sets the EnableSync
card parameter. Enables
synchronization status
messages (S1 byte), which
allow the node to choose
the best timing source.
Max Size (TXP_MR_10E, • 1548 bytes • 1548 bytes
TXP_MR_10G LAN Phy
• Jumbo (1518 to 9216 • Jumbo (1518 to 9216
only) Sets the maximum
Ethernet packet size. bytes) bytes)
Incoming MAC Address (TXP_MR_10E, Value of MAC address. Value of MAC address.
TXP_MR_10G LAN Phy Six bytes in Six bytes in
only) Sets the incoming hexadecimal format. hexadecimal format.
MAC address.
Wavelength Displays the wavelength • First Tunable First Tunable

of the client port. Wavelength Wavelength
• Further wavelengths: Further wavelengths:
1310 nm through 1310 nm through
1560.61 nm, 1560.61 nm,
100-GHz ITU 100-GHz ITU
spacing; coarse spacing; coarse
wavelength division wavelength division
multiplexing multiplexing
(CWDM) spacing (CWDM) spacing
Note: supported Note: supported

wavelengths are marked wavelengths are marked
by asterisks (**) by asterisks (**)
Reach Displays the optical reach The Reach options depend The Reach options depend
distance of the client port. on the traffic type that has on the traffic type that has
been selected. been selected.
384
DLP-G218 Changing the 10G or 40G Multirate Transponder Line Section Trace Settings
Options
Squelch Hold Off Timer (Only for TXP_MR_10E • Disable (0 ms) - • Disable (0 ms) -
card) Sets the period in Default value Default value
milliseconds that the
client interface waits for • 50 ms • 50 ms
resolution of issues on the • 100 ms • 100 ms
trunk side. The client
squelching starts after this • 250 ms • 250 ms
period.
• 500 ms • 500 ms
The user can configure the
squelch hold off timer in
CTC only under the
following conditions:
• The card must be
configured in TXP or
MXP operating
modes.
• The client payload
must be 10GE or
100GE.
• The Squelch
drop-down in CTC
must be set to
Squelch.
Step 4 Click Apply.

DLP-G218 Changing the 10G or 40G Multirate Transponder Line

Section Trace Settings
Purpose This task changes the line section trace settings for
the TXP_MR_10G, TXP_MR_10E,
TXP_MR_10E_C, TXP_MR_10E_L,
TXP_MR_10EX_C, 40E-TXP-C, and 40ME-TXP-C
transponder cards.
385
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the card where you want
to change the section trace settings.
Note The Section Trace tab is available for the 10G Multirate Transponder cards only if no PPMs are
provisioned, or the OC192 PPM is provisioned. The tab is not available if a 10G Ethernet LAN
Phy or 10G Fibre Channel PPM is provisioned.
Table 139: 10G or 40G Card Section Trace Settings
Parameter Description SONET Options

SDH Options
Port Sets the port number. • 1-1 (OC192) and 1-1 (STM64) and 2
2—Trunk for 10G —Trunk for 10G
cards cards
• 1 (OC-768) and 2 1 (STM-256) and 2
(OC-768) for 40G (STM-256) for 40G
cards cards
Received Trace Mode Sets the trace mode. • Off/None Off/None
• Manual Manual
Transmit Section Trace Sets the trace string size. • 1 byte 1 byte
String Size
• 16 byte 16 byte
386
Parameter Description SONET Options SDH Options

Transmit Displays the current String of trace string size String of trace string size
transmit string; sets a new
transmit string. You can
click the button on the
right to change the
display. Its title changes,
based on the current
display mode. In Transmit
String Type, click Hex
Mode to change the
display to hexadecimal
(button changes to
ASCII); click ASCII to
change the display to
ASCII (button changes to
Hex Mode).The supported
range for 1 bit Hex TX
trace is 20 to 7E. If TX
trace is provisioned
outside this range, client
transmits 00.
Disable AIS/RDI on If an TIM on Section Checked (AIS/RDI Checked (AIS/RDI

TIM-S overhead alarm arises on TIM-S is on TIM-S is
because of a J0 overhead disabled) disabled)
Unchecked (AIS/RDI Unchecked (AIS/RDI
on TIM-S is not on TIM-S is not
downstream nodes if this
box is checked. disabled) disabled)
Expected Displays the current String of trace string size String of trace string size
expected string; sets a
new expected string. You
can click thebutton on the
right to change the
display mode. In Expected
String Type, click Hex
Mode to change the
(button changes to
Hex Mode).
387
DLP-G319 Changing the 10G Multirate Transponder Line RMON Thresholds for 10G Ethernet LAN Phy Payloads
Received (Display only) Displays String of trace string size String of trace string size
the current received
string. You can click
Refresh to manually
refresh this display, or
check the Auto-refresh
every 5 sec check box to
keep this panel updated.
Auto-refresh If checked, automatically Checked/unchecked Checked/unchecked

refreshes the display every (default) (default)
5 seconds.
Step 4 Click Apply.

Step 5 Click Default to restore default values.
DLP-G319 Changing the 10G Multirate Transponder Line RMON

Thresholds for 10G Ethernet LAN Phy Payloads
TXP_MR_10E_L, and TXP_MR_10EX_C
transponder cards carrying the physical 10G Ethernet
LAN payload.
Procedure
Step 1 Display the TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, or TXP_MR_10EX_C

card where you want to change the line threshold settings in card view.
388
Step 5 From the Variable drop-down list, choose an Ethernet variable. See the following table for a list of
available Ethernet variables.
Table 140: TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, or TXP_MR_10EX_C Card GE LAN Phy Variables
ifInOctets Total number of octets received on the

interface, including framing characters.
ifInMulticastPkts Number of multicast frames received error free.
ifInBroadcastPkts Number of packets, delivered by a sublayer to an

higher sublayer, that were addressed to a
broadcast address at this sublayer.
preventing them from being delivered to a higher-
layer protocol.
ifInErrorBytePkts (TXP_MR_10G only) Number of receive error bytes.
ifInFramingErrorPkts (TXP_MR_10G only) Number of receive framing error counters.
ifInJunkInterPkts (TXP_MR_10G only) Number of receive interpacket junk counters.
ifOutOctets (TXP_MR_10G only) Total number of octets transmitted out of the

txTotalPkts (TXP_MR_10G only) Total number of transmit packets.
ifOutMulticastPkts (TXP_MR_10G only) Number of multicast frames transmitted error free.
ifOutBroadcastPkts (TXP_MR_10G only) Total number of packets that higher-level protocols

requested be transmitted, and that were addressed to
a broadcast address at this sublayer, including those
that were discarded or not sent.
dot3StatsFCSErrors Number of frames with frame check errors, that is,
there is an integral number of octets, but an
incorrect Frame Check Sequence (FCS).
dot3StatsFrameTooLong (TXP_MR_10G only) Number of received frames that were larger than
the maximum size permitted.
etherStatsUndersizePkts Total number of packets received that were less than
64 octets long (excluding framing bits, but including
FCS octets) and were otherwise well formed.
389
etherStatsFragments Total number of packets received that were less than

64 octets in length (excluding framing bits but
including FCS octets) and had either a bad FCS with
an integral number of octets (FCS Error) or a bad FCS
with a non-integral number of octets (Alignment
Error). Note that it is entirely normal for
etherStatsFragments to increment. This is because it
counts both runts (which are normal occurrences due
to collisions) and noise hits.
etherStatsPkts64Octets Total number of packets (including bad packets)

received that were 64 octets in length (excluding
framing bits but including FCS octets).
etherStatsPkts65to127Octets Total number of packets (including bad packets)

received that were between 65 and 127 octets in length
inclusive (excluding framing bits but including FCS
octets).
etherStatsPkts128to255Octets The total number of packets (including bad packets)

received that were between 128 and 255 octets in
length inclusive (excluding framing bits but including
FCS octets).

FCS octets).

FCS octets).

FCS octets).
etherStatsBroadcastPkts Total number of good packets received that were

directed to the broadcast address. Note that this does
not include multicast packets.
etherStatsMulticastPkts Total number of good packets received that were

directed to a multicast address. Note that this number
does not include packets directed to the broadcast
address.
etherStatsOversizePkts The total number of packets received that were longer

than 1518 octets (excluding framing bits, but including
390
etherStatsJabbers Total number of packets received that were longer than

1518 octets (excluding framing bits, but including FCS
octets), and had either a bad FCS with an integral
number of octets (FCS Error) or a bad FCS with a
nonintegral number of octets (Alignment Error).
etherStatsOctets Total number of octets of data (including those in

bad packets) received on the network (excluding
etherStatsCRCAlignErrors (TXP_MR_10G only) Total number of packets received that had a length
(excluding framing bits, but including FCS octets)
of between 64 and 1518 octets, inclusive, but had
either a bad FCS with an integral number of octets
(FCS Error) or a bad FCS with a non-integral
number of octets (Alignment Error).
rxPauseFrames (TXP_MR_10G only) Number of received IETF 802.x pause frames.
rxControlFrames Number of MAC control frames passed by the

MAC sublayer to the MAC control sublayer.
rxUnknownOpcodeFrames (TXP_MR_10G only) Number of MAC control frames received that contain
an opcode that is not supported by the device.
Step 8 Type in an appropriate number of seconds for the Sample Period.
Step 9 Type in the appropriate number of occurrences for the Rising Threshold.
Step 11 Click OK.

Note To view all RMON thresholds, click Show All RMON thresholds.
391
DLP-G301 Provisioning the 10G Multirate Transponder Trunk

Purpose This task provisions the TXP_MR_10G,
or TXP_MR_10EX_C trunk port alarm and threshold
cross alert (TCA) thresholds.
Procedure
the trunk port alarm and TCA settings.
Step 3 Under Types, verify that the TCA radio button is checked. If not, check it, then click Refresh.
Step 4 Referring to the following table, verify the trunk port (Port 2) TCA thresholds for RX Power High, RX
Power Low, TX Power High, and TX Power Low. Provision new thresholds as needed by double-clicking
the threshold value you want to change, deleting the existing value, and entering the new value. Hit Enter,
then click Apply.
Table 141: 10G Multirate Transponder Trunk Port TCA Thresholds
Card TCA RX TCA RX TCA TX TCA TX

Power High Power Low Power High Power Low
TXP_MR_10G –8 dBm –18 dBm 7 dBm –1 dBm
392

TXP_MR_10E –9 dBm –18 dBm 9 dBm 0 dBm

TXP_MR_10E_C
TXP_MR_10E_L
TXP_MR_10EX_C
Step 5 Click Apply.

Step 7 Referring to the following table, verify the trunk port (Port 2) Alarm thresholds for RX Power High, RX
the threshold value you want to change, deleting the existing value, and entering the new value. Hit Enter,
then click Apply.
Table 142: 10G Multirate Transponder Trunk Port Alarm Thresholds
Card Alarm RX Alarm RX Alarm TX Alarm TX

TXP_MR_10G –8 dBm –20 dBm 4 dBm 2 dBm
TXP_MR_10E –8 dBm –20 dBm 7 dBm 3 dBm

TXP_MR_10E_C
TXP_MR_10E_L
TXP_MR_10EX_C
Step 8 Click Apply.

DLP-G302 Provisioning the 10G Multirate Transponder Client

thresholds for the TXP_MR_10G, TXP_MR_10E,
TXP_MR_10E_C, TXP_MR_10E_L, and
TXP_MR_10EX_C cards.
393

page 321
Required/As Needed Required
Procedure
the client port alarm and TCA settings.
Step 4 Referring to the following table, verify the Port 1 (Client) TCA thresholds for RX Power High, RX Power
thresholds as needed by double-clicking the threshold value you want to change, deleting the existing
value, and entering the new value. Hit Enter, then click Apply.
Table 143: TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, or TXP_MR_10EX_C Card Client Interface TCA Thresholds
Pluggable Port Pluggable Port TCA RX Power TCA RX Power TCA TX Power TCA TX Power
Rate Module (XFP) High Low High Low
SONET (or TXP_MR_10E –1 –11 –1 –6
SDH) uses
ONS-XC-10G-S1
TXP_MR_10G
(XFP not
present)
394
Pluggable Port Pluggable Port TCA RX Power TCA RX Power TCA TX Power TCA TX Power
10G Ethernet TXP_MR_10E 0.5 –14.4 –1 –6

LAN Phy uses
ONS-XC-10G-S1
TXP_MR_10G
(XFP not
present)
10G Fibre TXP_MR_10E 0.5 –14.4 –1 –6

Channel uses
ONS-XC-10G-S1
IB_5G (Only the TXP_MR_10EX_C 1.0 –14.0 5.0 12.0

TXP_MR_10EX_C uses
card supports ONS-XC-10G-S1
IB_5G) Version 3
Step 5 Click Apply.

Step 7 Referring to the following table, provision the Port 1 (Client) Alarm thresholds for RX Power High, RX
Power Low, TX Power High, and TX Power Low based on the client interface that is provisioned.
Table 144: TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, or TXP_MR_10EX_C Card Client Interface Alarm Thresholds
Pluggable Port Pluggable Port Alarm RX Power Alarm RX Power Alarm TX Power Alarm TX Power
SONET (or TXP_MR_10E 3 –16 1 –8
SDH) uses
ONS-XC-10G-S1
TXP_MR_10G
(XFP not
present)
10G Ethernet TXP_MR_10E 3 –16 1 –8

LAN Phy uses
ONS-XC-10G-S1
TXP_MR_10G
(XFP not
present)
10G Fibre TXP_MR_10E 3 –16 1 –8

Channel uses
ONS-XC-10G-S1
395
NTP-G292 Provisioning the 40G Multirate Transponder Card Line Settings, PM Parameters, and Thresholds
Pluggable Port Pluggable Port Alarm RX Power Alarm RX Power Alarm TX Power Alarm TX Power
IB_5G (Only the TXP_MR_10EX_C 3.0 –16 1.0 –8

TXP_MR_10EX_C uses
card supports ONS-XC-10G-S1
IB_5G) Version 3
Step 8 Click Apply.

NTP-G292 Provisioning the 40G Multirate Transponder

Card Line Settings, PM Parameters, and Thresholds
Purpose This procedure changes the line settings, PM
parameters, and threshold settings for 40G multirate
transponder cards (40E-TXP-C, 40ME-TXP-C).

Muxponder Cards
necessary)
on page 321
Note The 40E-TXP-C and 40ME-TXP-C cards do not support PPMs.
396
DLP-G656 Provisioning the 40E-TXP-C and 40ME-TXP-C Data Rate
Procedure
settings.
Step 2 If you are provisioning a 40E-TXP-C or 40ME-TXP-C card, complete the DLP-G656 Provisioning the
40E-TXP-C and 40ME-TXP-C Data Rate, on page 397 task. If not, continue with the next step.
DLP-G657 Changing the 40G Multirate Transponder Card Settings, on page 398
DLP-G658 Changing the 40G Multirate Transponder Line Settings, on page 400
DLP-G659 Changing the 40G Multirate Transponder SONET, SDH, or Ethernet Line Settings, on page
403
DLP-G218 Changing the 10G or 40G Multirate Transponder Line Section Trace Settings, on page 385
DLP-G661 Changing the 40G Multirate Transponder Line Thresholds for SONET or SDH Payloads, on
page 410
DLP-G663 Provisioning the 40G Multirate Transponder Trunk Port Alarm and TCA Thresholds, on
page 413
DLP-G664 Provisioning the 40G Multirate Transponder Client Port Alarm and TCA Thresholds, on
page 414
DLP-G656 Provisioning the 40E-TXP-C and 40ME-TXP-C Data Rate

Purpose This task changes the 40E-TXP-C and 40ME-TXP-C
card data rate.
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 40E-TXP-C card where
you want to change the card data rate settings.
397
DLP-G657 Changing the 40G Multirate Transponder Card Settings
Step 2 Click the Provisioning > Data Rate Selection tabs.

• SONET (ANSI) OC-768 or SDH (ETSI) STM-256
• 40G Ethernet LAN Phy (only when overclock mode is ON)
• OTU3
Step 5 Click OK.


Purpose This task changes the card settings of the 40E-TXP-C
and 40ME-TXP-C cards.
Procedure
you want to change the card settings.
398
Table 145: 40E-TXP-C and 40ME-TXP-C Card Settings
Parameter Description ANSI Options

ETSI Options
Regeneration Peer Slot Sets the slot containing • None None
another 40E-TXP-C or
40ME-TXP-C card to •1 1
create a regeneration peer •2 2
group. A regeneration
peer group facilitates the •3 3
management of two
•4 4
40E-TXP-C or
40ME-TXP-C cards that •5 5
are needed to perform a
complete signal • 12 12
regeneration. • 13 13
The regeneration peer
• 14 14
group synchronizes
provisioning of the two • 15 15
cards. Payload type and
ITU-T G.709 optical • 16 16
transport network (OTN)
changes made on one
40E-TXP-C or
40ME-TXP-C card is
reflected on the peer
40E-TXP-C or
40ME-TXP-C card.
Note Y-cable
protection
groups cannot
be created on
TXP cards that
are in a
regeneration
peer group.
Regeneration Group (Display only) The — —

Name regeneration peer group
name.
Trunk Wavelengths (Display only) Shows the — —

supported wavelengths of
the trunk port after the
card is installed. The
40E-TXP-C, or
40ME-TXP-C that is
installed shows the
C-band wavelengths that
it supports.
399
Step 4 Click Apply.


Purpose This task changes the line settings of the 40E-TXP-C
and 40ME-TXP-C cards.
Procedure
you want to change the line settings.
Step 2 Click the Provisioning > Line > Ports tabs.
Step 3 Modify any of the settings for the Client tab as described in the following table.
Table 146: Line Settings of the 40E-TXP-C, and 40ME-TXP-C Cards

Port (Display only) Displays the port 1 and 2
number.
Port Name Assigns a logical name for each of User-defined. The port name can
the ports shown by filling in this be up to 80 alphanumeric or
field. special characters, or both. The
port name is blank by default.
OOS,DSBLD (ANSI) or
service states, see the Locked,disabled (ETSI)
Administrative and Service States OOS,MT (ANSI) or
document. Locked,maintenance (ETSI)
IS,AINS (ANSI) or
(ETSI)
400

Service State (Display only) Identifies the IS-NR (ANSI) or Unlocked-
autonomously generated state that enabled (ETSI)
Unlocked-disabled,
OOS-MA,MT (ANSI) or
Locked-
enabled,maintenance (ETSI)
ALS Mode (Client port only) Sets the ALS Disabled (default)—ALS is
function mode. off; the laser is not
automatically shut down
when traffic outage or loss of
signal (LOS) occurs.
Auto Restart: (OC-768/STM-
256/OTU-3 only) ALS is on;
the laser automatically shuts
down when traffic outages
(LOS) occur. It
automatically restarts when
the conditions that caused
the outage are resolved.
Manual Restart—ALS is on;
down when traffic outage or
LOS occurs. However, the
laser must be manually
restarted when conditions
that caused the outage are
resolved.
Manual Restart for Test—
Manually restarts the laser
for testing.
401

Reach (Display only) Displays the optical • Autoprovision—(trunk port
reach distance of the port. only) The system
automatically provisions the
reach.
• VSR—(client port only) The
system provisions very short
reach (VSR) for the port.
Wavelength Provisions the wavelength for the • First Tunable Wavelength

port.
• Further wavelengths: Further
wavelengths in 100-GHz
ITU-T C-band spacing. The
asterisks. If the card is not
installed, all wavelengths
appear with a dark grey
background.
Fault Signalling (Display only) Applicable only to Squelch/Laser-Off

client port 1. When the termination
AIS/Send Local Fault
mode is set to transparent,
Squelch/Laser-Off is enabled. For Disable/Transparent
section/line termination mode,
NoteBoth Squelch/Laser-Off
AIS/Send Local Fault is enabled.
and AIS/Send
For trunk port, Squelch/Laser-Off
Local Fault options
is disabled.
are supported when
the selected
Termination Mode
is Transparent. If
the Termination
Mode selected is
Section or Line,
then only AIS/Send
Local Fault is
supported. This is
applicable for OC-
192/STM-64 and
OC-768/STM-256.
For OTN payloads,
both
Squelch/Laser-Off
and AIS/Send
Local Fault options
are supported.
402
DLP-G659 Changing the 40G Multirate Transponder SONET, SDH, or Ethernet Line Settings

Overclock Enables or disables overclock OFF (default)
mode
ON
on trunk port.
First Tunable Wavelength

Rx Wavelength Provisions the wavelength of the
Further wavelengths: Further
trunk port.
wavelengths in 100-GHz
background.
Step 4 Click Apply.

DLP-G659 Changing the 40G Multirate Transponder SONET,

SDH, or Ethernet Line Settings
Purpose This task changes the SONET, SDH, or Ethernet line
settings for 40E-TXP-C and 40ME-TXP-C cards.
Procedure
you want to change the SONET, SDH, or Ethernet line settings.
Step 2 Click the Provisioning > Line > SONET/SDH/Ethernet tabs.
Note In the following table, some parameter tabs do not always apply to all 40G multirate transponder
cards. If a tab does not apply, it will not appear in CTC.
403
Table 147: SONET, SDH Line Settings of the 40E-TXP-C and 40ME-TXP-C Cards
Parameter Description ANSI Options ETSI Options

Port (Display only) Displays • 1 (OC-768) • 1 (STM-256)
the port number.
• 1 (40G Ethernet • 1 (40G Ethernet
LAN Phy) LAN Phy)
• 1 (OTU3) • 1 (OTU3)

[ETSI] only) Sets the
signal fail bit error rate. • 1E-4 • 1E-4
• 1E-5 • 1E-5

signal degrade bit error • 1E-6 • 1E-6
rate. • 1E-7 • 1E-7
• 1E-8 • 1E-8
• 1E-9 • 1E-9
ProvidesSync (OC-768/STM-256 only) Checked or unchecked Checked or unchecked

Sets the ProvidesSync
card parameter. If
checked, the card is
provisioned as a network
element (NE) timing
reference.
SyncMsgIn (OC-768/STM-256 only) Checked or unchecked Checked or unchecked

Sets the EnableSync card
parameter. Enables
404
Admin SSM In Overrides the • PRS—Primary • G811—Primary

synchronization status Reference Source reference clock
message (SSM) and the (Stratum 1)
• STU—Sync traceability
synchronization
• STU—Sync traceability unknown
traceability unknown
(STU) value. If the node unknown • G812T—Transit node
does not receive an SSM • ST2—Stratum 2 clock traceable
signal, it defaults to STU. • ST3—Stratum 3 • G812L—Local node
• SMC—SONET clock traceable
minimum clock • SETS—Synchronous
equipment
• ST4—Stratum 4
• DUS—Do not use for
timing synchronization
• RES—Reserved; quality
level set by user
Send DoNotUse (OC-768/STM-256 only) Checked or unchecked Checked or unchecked

Sets the Send DoNotUse
card state. When checked,
sends a do not use (DUS)
message on the S1 byte.
[ETSI] only) Indicates the
optical transport type. • SDH • SDH
Termination Mode (OC-768/STM-256 only) • Transparent • Transparent

Sets the mode of
• Section • Regeneration Section
operation.
(RS)
Note This option is • Line
only available • Multiplex Section
for (MS)
SONET/SDH
payloads.
405
Table 148: Ethernet Line Settings of the 40E-TXP-C and 40ME-TXP-C Cards
Port (Display only) Displays • 1-1 to 1-16 • 1-1 to 1-16

the port number. (OC3/OC12/OC48/GE) (STM1/STM4/STM16/GE)
• 17-1 • 17-1
(Trunk/Interlink) (Trunk/Interlink)
• 18-1 • 18-1
• 19-1 (Trunk) • 19-1 (Trunk)
Note Port 17 and Note Port 17 and
Port 18 are Port 18 are
trunk ports trunk ports
that support that support
OC192 STM64
payload in a payload in a
single-card single-card
configuration. configuration.
These ports These ports
are interlink are interlink
ports in a ports in a
double-card double-card
(ADM-10G (ADM-10G
peer group). peer group).
Port Name Provides the ability to User-defined. Name can User-defined. Name can
assign the specified port a be up to be up to
name. 80 alphanumeric/special 80 alphanumeric/special
default. default.
Admin State Sets the port service state. • IS • Unlocked

For more information
• IS,AINS • Unlocked,automaticInService
states, see the • OOS,DSBLD • Locked,disabled
Administrative and
Service States document. • OOS,MT • Locked,maintenance
406

Service State (Display only) Identifies IS-NR Unlocked-enabled
the autonomously
OOS-AU,AINS Unlocked-disabled,
OOS-MA,DSBLD
the port. Service states Locked-enabled,disabled
appear in the format: OOS-MA,MT
Primary State-Primary
State. For more
states, see the
Administrative and
options. • Manual Restart: ALS • Manual Restart: ALS
resolved. resolved.
testing. testing.
407
DLP-G692 Changing the 40G Multirate Transponder OTU Settings

ETSI Options
AINS Soak Sets the automatic • Duration of valid Duration of valid
in-service soak period. input signal, in input signal, in
Double-click the time and hh.mm format, after hh.mm format, after
use the up and down which the card which the card
arrows to change settings. becomes in service becomes in service
(IS) automatically (IS) automatically
• 0 to 48 hours, 0 to 48 hours,
15-minute 15-minute
Note The Note The
AINS AINS
service service
state is state is
not not
supported supported
on on
interlink interlink
ports. ports.
Step 4 Click Apply.


Purpose This task changes the OTU settings of the
40E-TXP-C, and 40ME-TXP-C transponder cards.
408
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 40E-TXP-C or 40ME-
TXP-C card where you want to change the OTU settings.
Step 2 Click the Provisioning > Line > OTU tabs.
Table 149: OTU Settings of the 40E-TXP-C, and 40ME-TXP-C Cards

ETSI Options
Port (Display only) Displays • 1-1 1-1
the port number that is
applicable only for • 2-1 2-1
OC-192/STM-64 • 3-1 3-1
payloads.
• 4-1 • 4-1
SyncMsgIn (Display only) Checked or unchecked Checked or unchecked

(OC-768/STM-256 only)
parameter. Enables
Admin SSM Overrides the • PRS—Primary • G811—Primary

synchronization
equipment
• ST4—Stratum 4
level set by user
409
ProvidesSync (Display only) Checked or unchecked Checked or unchecked

card parameter. If
element (NE) timing
reference.
Step 4 Click Apply.

DLP-G661 Changing the 40G Multirate Transponder Line

Thresholds for SONET or SDH Payloads
Purpose This task changes the line threshold settings of
40E-TXP-C and 40ME-TXP-C transponder cards
carrying SONET or SDH payloads, including the
physical 40G Ethernet WAN Phy payload.
Procedure
you want to change the line threshold settings.
Step 2 Click the Provisioning > Line Thresholds > SONET Thresholds (ANSI) or SDH Thresholds (ETSI) tabs.
Table 150: Line Threshold Settings for the 40E-TXP-C, and 40ME-TXP-C Cards

Port (Display only) Port • 1 (OC-768) • 1 (STM-256)
number
• 2 (OC-768) • 2 (STM-256)
410

or Far End
(minutes) or 1 day
• Types—Line or
Section (near end
only)

category and click
Refresh.

(near end only)
Refresh.
411

(near end only)
Click Reset to Default to Refresh.
restore default values. Click Reset to Default
to restore default values.

or Far End
(minutes) or 1 day
• Types—Line or
Section (near end
only)

category and click
Refresh.
Click Reset to Default to
restore default values.
412

UAS (Line or Multiplex Section Numeric. Threshold Numeric. Threshold
only) Unavailable seconds display options include: display options include:
(near end only)
restore default values. Click Reset to Default
to restore default values.
Step 4 Click Apply.

DLP-G663 Provisioning the 40G Multirate Transponder Trunk

Purpose This task provisions the 40E-TXP-C, and
40ME-TXP-C trunk port alarm and threshold cross
alert (TCA) thresholds.
Procedure
you want to change the trunk port alarm and TCA settings.
413
Step 3 Under Types area, verify that the TCA radio button is selected. If not, click it, then click Refresh.
Step 4 Referring to the following table, verify the trunk port (Port 2) TCA thresholds for RX Power High, RX Power
Low, TX Power High, and TX Power Low. Provision new thresholds as needed by double-clicking the
threshold value you want to change, deleting the existing value, and entering the new value. Press Enter, then
click Apply.
Step 5 Under Intervals area, select 15 Min or 1 Day, then click Refresh.
Table 151: Trunk Port TCA Thresholds of the 40E-TXP-C, and 40ME-TXP-C Cards
Card TCA RX Power High TCA RX Power Low TCA TX Power High TCA TX Power Low
(dbm) (dbm) (dbm) (dbm)
40E-TXP-C –9.0 –22.0 9.0 0.0

40ME-TXP-C
Step 6 Click Apply.

Step 7 Under Types area, click the Alarm radio button and click Refresh.
Step 8 Referring to the following table, verify the trunk port (Port 2) alarm thresholds for RX Power High, RX Power
Low, TX Power High, and TX Power Low. Provision new thresholds as needed by double-clicking the
threshold value you want to change, deleting the existing value, and entering the new value. Press Enter, then
click Apply.
Table 152: Trunk Port Alarm Thresholds of the 40E-TXP-C, and 40ME-TXP-C Cards

40E-TXP-C –9.0 –22.0 9.0 0.0

40ME-TXP-C

Step 11 Click Default to restore default values.
DLP-G664 Provisioning the 40G Multirate Transponder Client

thresholds for the 40E-TXP-C, and 40ME-TXP-C
cards.
414

page 321
Procedure
you want to change the client port alarm and TCA settings.
Step 3 Under Types area, verify that the TCA radio button is selected. If not, click it, then click Refresh.
Step 4 Referring to the following table, verify the client port (Port 1) TCA thresholds for RX Power High, RX Power
thresholds as needed by double-clicking the threshold value you want to change, deleting the existing value,
and entering the new value. Press Enter, then click Apply.
Table 153: Client Interface TCA Thresholds of the 40E-TXP-C, and 40ME-TXP-C Cards
Pluggable Port Rate TCA RX Power High TCA RX Power Low TCA TX Power High TCA TX Power Low
40G Ethernet LAN 3.0 –6.0 6.0 –3.0

Phy
OC-768/STM-256 3.0 –6.0 6.0 –3.0
OTU3 3.0 –6.0 6.0 –3.0
Step 6 Click Apply.

Step 8 Referring to the following table, provision the client port (Port 1) alarm thresholds for RX Power High, RX
Power Low, TX Power High, and TX Power Low based on the client interface that is provisioned.
Table 154: Card Client Interface Alarm Thresholds of the 40E-TXP-C, and 40ME-TXP-C Cards
Pluggable Port Rate Alarm RX Power Alarm RX Power Alarm TX Power Alarm TX Power
High Low High Low
40G Ethernet LAN 5.0 –8.0 4.0 –1.0

Phy
415
NTP-G170 Provisioning the ADM-10G Card Peer Group, Ethernet Settings, Line Settings, PM Parameters, and Thresholds
Pluggable Port Rate Alarm RX Power Alarm RX Power Alarm TX Power Alarm TX Power
High Low High Low
OC-768/STM-256 5.0 –8.0 4.0 –1.0
OTU3 5.0 –8.0 4.0 –1.0

NTP-G170 Provisioning the ADM-10G Card Peer Group, Ethernet

Settings, Line Settings, PM Parameters, and Thresholds
Purpose This procedure creates an ADM-10G peer group and
changes line settings, PM parameters, and threshold
settings for ADM-10G cards.

DLP-G723 Install PPM on a Line Card
DLP-G411 Provisioning an ADM-10G PPM and Port,
on page 317
page 321
Procedure
settings.
Step 2 To provision a peer group, complete the DLP-G403 Creating the ADM-10G Peer Group, on page 417.
Step 3 To display the bandwidth usage of the STS timeslots, complete the DLP-G775 Displaying the
Bandwidth Usage of the STS Timeslots, on page 214.
Step 4 To provision Ethernet settings, complete the DLP-G469 Provisioning the ADM-10G Card Ethernet
Settings, on page 418.
Step 5 To change line settings, complete the following tasks as needed:
DLP-G397 Changing the ADM-10G Line Settings, on page 419
416
DLP-G403 Creating the ADM-10G Peer Group
DLP-G398 Changing the ADM-10G Line Section Trace Settings, on page 425
DLP-G399 Changing the ADM-10G Line Thresholds for SONET and SDH Payloads, on page 427
DLP-G412 Changing the ADM-10G Line RMON Thresholds for the 1G Ethernet Payload, on page 432
Step 6 To change thresholds, complete the following tasks as needed:

DLP-G400 Provisioning the ADM-10G Interlink or Trunk Port Alarm and TCA Thresholds, on page
435
DLP-G401 Provisioning the ADM-10G Client Port Alarm and TCA Thresholds, on page 437
DLP-G402 Changing the ADM-10G OTN Settings, on page 438
DLP-G403 Creating the ADM-10G Peer Group

Purpose This task creates peer group protection for two
ADM-10G cards within the same node, located on
the same shelf. Perform this task on only one of the
two peer cards.

Muxponder Cards
Note You cannot perform this task on a single ADM-10G card; it is only available if a second ADM-10G card
can be accessed through the interlink ports (Port 17 and Port 18).
Note Due to a hardware limitation, you cannot provision the SDCC/LDCC on Port 17.
417
DLP-G469 Provisioning the ADM-10G Card Ethernet Settings
Procedure
Step 3 In the ADM Group Peer drop-down list, choose the slot number where the companion ADM-10G card is
located.
Step 4 In the ADM Peer Group field, enter a group name.
Step 5 Click Apply.
Note The Card Parameters Tunable Wavelengths area is read-only and does not contain any
wavelengths until circuits are separately provisioned for the card.
DLP-G469 Provisioning the ADM-10G Card Ethernet Settings

Purpose This task changes the Ethernet settings for the
ADM-10G card.
Procedure
you want to change the Ethernet settings. The card view appears.
Step 2 Click the Provisioning > Line > Ethernet tabs.
Step 3 Modify any of the settings for the Ethernet tab as described in the following table. The parameters that
appear depend on the card mode.
Table 155: ADM-10G Card Ethernet Settings

Port (Display only) The Port number —
(n-n) and rate.
418
• HDLC
CRC encap value for HDLC:
DLP-G397 Changing the ADM-10G Line Settings
MTU The maximum size of the Ethernet Jumbo. Default: 64 to 9216

frames accepted by the port.
Numeric: 1548
Mode Sets the Ethernet mode. • 1000 Mbps
Framing Sets the framing type. • GFP-F
CRC Encap Sets the CRC encap values for the CRC encap value for GFP-F:
framing type.
• None (default)
• 32-Bit
• 16-Bit
• 32-Bit (default)
AINS Soak Automatic in-service soak time. • Duration of valid input signal,
The duration of time that must pass in hh.mm format, after which
with an uninterrupted signal before the card becomes in service
the traffic/termination transitions (IS) automatically
to the IS-NR (ANSI) or
unlocked-enabled (ETSI) service • 0 to 48 hours, 15-minute
state. increments
Step 4 Click Apply.

Purpose This task changes the line settings for the ADM-10G
card.
419
Procedure
Step 3 Modify any of the settings described in the following table as needed.
Note In the following table, some parameter tabs do not always apply to all ADM-10G cards. If a tab
does not apply, it will not appear in CTC.
Table 156: ADM-10G Line Port Tab Settings

the port number. (OC3/OC12/OC48/GE) (STM1/STM4/STM16/GE)
• 17-1 • 17-1
• 18-1 • 18-1
• 19-1 (Trunk) • 19-1 (Trunk)
OC192 STM64
(ADM-10G (ADM-10G
default. default.
420

Admin State Sets the port service state.
• IS • Unlocked
about administrative • IS,AINS • Unlocked,automaticInService
Administrative and

the autonomously
• OOS-MA,DSBLD
State. For more
states, see the
Administrative and
421
options. • Auto Restart: (Not • Auto Restart: (Not
applicable for applicable for
Gigabit Ethernet Gigabit Ethernet
client interfaces) client interfaces)
ALS is on; the laser ALS is on; the laser
resolved. resolved.
resolved. resolved.
testing. testing.
422

ETSI Options
AINS Soak Sets the automatic • Duration of valid Duration of valid
Double-click the time and hh.mm format, after hh.mm format,
use the up and down which the card after which the card
arrows to change settings. becomes in service becomes in service
(IS) automatically (IS) automatically
• 0 to 48 hours, 0 to 48 hours,
15-minute 15-minute
Note The Note The
AINS AINS
service service
state is state is
not not
supported supported
on on
interlink interlink
ports. ports.
Wavelength Tunable wavelength. Shows the supported Shows the supported

wavelengths of the trunk wavelengths of the trunk
port after the card is port after the card is
installed in the format: installed in the format:
first wavelength-last first wavelength-last
wavelength-frequency wavelength-frequency
spacing-number of spacing-number of
supported wavelengths. supported wavelengths.
For example, For example,
1529.55nm-1561.83nm-50gHz-8 1529.55nm-1561.83nm-
are supported 50gHz-8 are supported
wavelengths. You can wavelengths. You can
also view the bandwidth also view the bandwidth
of the wavelength of the wavelength
information in THz. information in THz.
Step 4 Click Apply.

Step 5 Click the Provisioning > Line >SONET or SDH tabs.
Step 6 Modify any of the settings described in the following table as needed.
423
Table 157: ADM-10G Line SONET or SDH Tab Settings

the client and trunk port (OC3/OC12/OC48/GE) (STM1/STM4/STM16/GE)
number.
• 17-1 (OC192) • 17-1(STM64)
• 18-1 • 18-1
(OC192/Interlink) (STM64/Interlink)
• 19-1 (OC192) • 19-1 (STM64)
OC192 STM64
(ADM-10G (ADM-10G
ProvidesSync When checked, the card Checked or unchecked Checked or unchecked

is provisioned as an NE
timing reference.
SyncMsgIn Enables synchronization Checked or unchecked Checked or unchecked

status messages (S1 byte),
which allow the node to
choose the best timing
source.
SF BER Sets the signal fail bit • 1E-3 • 1E-3

error rate.
• 1E-4 • 1E-4
• 1E-5 • 1E-5
Send DoNotUse When checked, sends a Checked or unchecked Checked or unchecked

DUS message on the S1
byte.
424
DLP-G398 Changing the ADM-10G Line Section Trace Settings
SD BER Sets the signal degrade bit • 1E-5 • 1E-5

error rate.
• 1E-6 • 1E-6
• 1E-7 • 1E-7
• 1E-8 • 1E-8
• 1E-9 • 1E-9
Type (Display only) Type of • SONET • SDH

node.
• SDH

message (SSM) (Stratum 1)
synchronization
traceability unknown • ST2—Stratum 2 unknown
(STU) value. If the node • TNC—Transit node • G812T—Transit node
does not receive an SSM clock clock traceable
signal, it defaults to STU. • ST3E—Stratum 3E • G812L—Local node
clock traceable
• ST3—Stratum 3
• SETS—Synchronous
• SMC—SONET
equipment
minimum clock
• ST4—Stratum 4
level set by user

the ADM-10G cards.
425
Note The Section Trace tab is available for ports configured as OC-N (Ports 1 through 16, Ports 17 and 18
[only in a single-card configuration] and Port 19). Section trace is not available on interlink ports.
Procedure
you want to change the section trace settings. The card view appears.
Table 158: ADM-10G Section Trace Settings

Port Sets the port number. • 1-1 to 1-16 • 1-1 to 1-16
(OC3/OC12/OC48/GE) (STM1/STM4/STM16/GE)
• 17-1 (OC 192) • 17-1 (STM64)
• 18-1 (OC192) • 18-1 (STM64)
• 19-1 (OC192) • 19-1 (STM64)
OC192 STM64
(ADM-10G (ADM-10G
Received Trace Mode Sets the trace mode. • Off/None • Off/None

• Manual • Manual
426
DLP-G399 Changing the ADM-10G Line Thresholds for SONET and SDH Payloads
Transmit Section Trace Sets the trace string size. • 1 byte • 1 byte
String Size
• 16 byte • 16 byte
• 64 byte • 64 byte
Current Current Transmit String String of trace string size String of trace string size
displays the current
transmit string; New
Transmit String sets a new
transmit string. Current
String Type allows you to
choose between ASCII or
Hexadecimal format.
Click Hex to change the
(button changes to
Hex).
Received (Display only) Current String of trace string size String of trace string size
Received String displays
Refresh to manually
every 5 sec check box to
keep this panel updated.

5 seconds.
Step 4 Click Apply.

DLP-G399ChangingtheADM-10GLineThresholdsforSONETandSDHPayloads
ADM-10G cards carrying SONET payloads.
427
Procedure
you want to change the line threshold settings. The card view appears.
Step 2 Click the Provisioning > Line Thresholds > SONET Thresholds or SDH Thresholds tabs.
Table 159: ADM-10G Card Line Threshold Settings

Port (Display only) Port • 1-1 to 1-16 • 1-1 to 1-16
number (OC3/OC12/OC48/GE) (STM1/STM4/STM16/GE)
• 17-1 (OC 192) • 17-1 (STM 64)
• 18-1 (OC192) • 18-1 (STM64)
• 19-1 (OC192) • 19-1 (STM64)
OC192 STM64
(ADM-10G (ADM-10G
428
EB Path Errored Block — Numeric. Threshold

indicates that one or more display options include:
bits are in error within a
block
or Far End
(minutes) or 1 day
• Types—Multiplex
Section or
(near end only)

category and click
Refresh.

or Far End
(minutes) or 1 day
• Types—Line or
Section (near end
only)

category and click
Refresh.

• Direction—Near End • Direction—Near End
• Interval—15 Min • Interval—15 Min
• Types—Line or • Types—Line or
Section (near end Section (near end
only) only)
Choose an option in each Choose an option in

category and click each category and click
Refresh. Refresh.
429

only) only)

Refresh. Refresh.
or Far End
(minutes) or 1 day
Section or
(near end only)

category and click
Refresh.
FC (Line Section only) Numeric. Threshold —

Failure count display options include:
or Far End
(minutes) or 1 day
• Types—Line or
Section (near end
only)

category and click
Refresh.
430

PSC Protection Switching Numeric. Threshold —
Count display options include:
or Far End
(minutes) or 1 day

category and click
Refresh.
PSD Protection Switching Numeric. Threshold —

Duration display options include:
or Far End
(minutes) or 1 day

category and click
Refresh.
UAS (Line Section only) Numeric. Threshold Numeric. Threshold

Unavailable seconds display options include: display options include:
only) only)

Refresh. Refresh.
Step 4 Click Apply.

431
DLP-G412 Changing the ADM-10G Line RMON Thresholds for

the 1G Ethernet Payload
Purpose This task changes the line RMON threshold settings
for an ADM-10G card carrying the 1G Ethernet
payload.

DLP-G411 Provisioning an ADM-10G PPM and Port,
on page 317
Note This task can only be performed if the ADM-10G card has at least one PPM port provisioned for Gigabit
Ethernet.
Procedure
want to change the line RMON thresholds. The card view appears.
Step 5 From the Variable drop-down list, choose the applicable Ethernet variable. See the following table for a list
of available Ethernet variables.
Table 160: ADM-10G Gigabit Ethernet Thresholds
ifInOctets Total number of octets received on the interface,

including framing characters.

preventing them from being deliverable to a
higher-layer protocol.
ifOutOctets Total number of octets transmitted out of the interface,

432
ifInMulticastPkts Number of multicast frames received error-free.
ifInBroadcastPkts Number of packets, delivered by a sublayer to a higher

layer or sublayer, that were addressed to a broadcast
address at this sublayer.
ifInErrorBytePkts Number of receive error bytes.
dot3StatsFCSErrors Number of frames with frame check errors; that is,

there is an integral number of octets, but there is also
an incorrect frame check sequence (FCS).
dot3StatsFrameTooLong Number of received frames that were larger than the

permitted maximum size.
dot3ControlInUnknownOpcodes A count of MAC control frames received on this

interface that contain an opcode not supported by this
device.
dot3InPauseFrames A count of MAC control frames received on this

interface with an opcode indicating the PAUSE
operation.
dot3OutPauseFrames A count of MAC control frames transmitted on this

operation.
etherStatsUndersizePkts Total number of packets received that were

well-formed and less than 64 octets long (excluding
framing bits and including FCS octets).

an integral number of octets (FCS error) or a bad FCS
with a non-integral number of octets (alignment error).
Note It is normal for etherStatsFragments to
increment. This is because it counts both
runts (which are normal occurrences due

transmitted and received by the interface that were 64
octets in length (excluding framing bits and including
FCS octets).

transmitted and received by the interface that were
between 65 and 127 octets in length, inclusive.
433

between 128 and 255 octets in length, inclusive,
excluding framing bits and including FCS octets.

between 256 and 511 octets in length, inclusive.


etherStatsBroadcastPkts Total number of good packets transmitted and

received by the interface that were directed to the
broadcast address.
Note Multicast packets are not included.
etherStatsMulticastPkts Total number of good packets transmitted and

received by the interface that were directed to a
multicast address.
Note This number does not include packets
directed to the broadcast address.
etherStatsOversizePkts Total number of packets transmitted and received by

the interface that were well-formed and longer than
1518 octets, excluding framing bits and including FCS
octets.
etherStatsJabbers Total number of packets received that were longer

than 1518 octets (excluding framing bits and including
FCS octets), and had a bad FCS with an integral
number of octets (FCS error) or a bad FCS with a
non-integral number of octets (alignment error).
txTotalPkts Total number of transmit packets.
Step 6 From the Alarm Type drop-down list, indicate whether the event will be triggered by the rising threshold,
the falling threshold, or both the rising and falling thresholds.
Step 7 From the Sample Type drop-down list, choose either Relative or Absolute.
Relative restricts the threshold to use the number of occurrences in the user-set sample period. Absolute
sets the threshold to use the total number of occurrences, regardless of time period.
434
DLP-G400 Provisioning the ADM-10G Interlink or Trunk Port Alarm and TCA Thresholds
Step 8 Type an appropriate number of seconds for the Sample Period.

Step 9 Type the appropriate number of occurrences for the Rising Threshold.
Step 11 Click OK.

DLP-G400 Provisioning the ADM-10G Interlink or Trunk Port

Alarm and TCA Thresholds
Purpose This task provisions the ADM-10G interlink or trunk
port alarm and threshold crossing alert (TCA)
thresholds.
Procedure
want to change the interlink or trunk port alarm and TCA settings.
Step 4 Referring to the following table, verify the interlink or trunk port TCA thresholds for RX Power High, RX
the threshold value you want to change, deleting it, entering a new value, and pressing Enter.
435
DLP-G400 Provisioning the ADM-10G Interlink or Trunk Port Alarm and TCA Thresholds
Table 161: ADM-10G Interlink and Trunk Port TCA Thresholds
Port TCA RX TCA RX TCA TX TCA TX

17-1 and 18-1 –7.0 dBm –27.0 dBm 6.0 dBm –4.0 dBm
(Trunk/Interlink)
Note Port 17 and
Port 18 are
trunk ports
in
single-card
configuration
and an
interlink port
in
double-card
configuration
(ADM-10G
peer group).
19-1 (Trunk) –7.0 dBm –27.0 dBm 6.0 dBm –4.0 dBm
Step 5 Click Apply.

Step 7 Referring to the following table, verify the interlink or trunk port alarm thresholds for RX Power High,
RX Power Low, TX Power High, and TX Power Low.
Step 8 Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it,
entering a new value, and pressing Enter.
436
DLP-G401 Provisioning the ADM-10G Client Port Alarm and TCA Thresholds
Table 162: ADM-10G Interlink and Trunk Port Alarm Thresholds
Port Alarm RX Alarm RX Alarm TX Alarm TX

17-1 1.0 dBm –13.0 dBm 1.0 dBm –8.0 dBm

(Trunk/Interlink)
Note Port 17 is a
trunk port in
single-card
configuration
and an
interlink port
in
double-card
configuration
(ADM-10G
peer group).
18-1 –5.0 dBm –30.0 dBm 5.0 dBm –3.0 dBm

(Trunk/Interlink)
Note Port 18 is a
trunk port in
single-card
configuration
and an
interlink port
in
double-card
configuration
(ADM-10G
peer group).
19-1 (Trunk) –5.0 dBm –30.0 dBm 5.0 dBm –3.0 dBm
Step 9 Click Apply.

DLP-G401 Provisioning the ADM-10G Client Port Alarm and TCA Thresholds
thresholds for the ADM-10G card.
437
DLP-G402 Changing the ADM-10G OTN Settings

page 321
Procedure
want to change the client port alarm and TCA settings.
Step 4 Referring to Table 132: TXP_MR_2.5G and TXPP_MR_2.5G Card Client Interface TCA Thresholds, on
page 368 and Table 133: TXP_MR_2.5G and TXPP_MR_2.5G Card Client Interface Alarm Thresholds, on
page 370, verify the Port 1 to 16 (Client) Alarm thresholds for RX Power High, RX Power Low, TX Power
High, and TX Power Low based on the client interface that is provisioned.
Note You must modify 15 Min and 1 Day independently. To do so, choose the appropriate radio button
and click Refresh.
Step 6 Click Apply.

Step 8 Referring to Table 132: TXP_MR_2.5G and TXPP_MR_2.5G Card Client Interface TCA Thresholds, on
page 368 and Table 133: TXP_MR_2.5G and TXPP_MR_2.5G Card Client Interface Alarm Thresholds, on
page 370, verify the interlink ports 17-1 and 18-1 for RX Power High, RX Power Low, TX Power High, and
TX Power Low settings.

Purpose This task changes the line OTN settings for the
ADM-10G card.
438
Procedure
you want to change the OTN settings.
Step 2 Click the Provisioning > OTN tabs, then click one of the following subtabs: OTN Lines,
ITU-T G.709 Thresholds, FEC Thresholds, or Trail Trace Identifier.
SM and PM independently. To do so, choose the appropriate radio buttons and click Refresh.
Table 163: ADM-10G Card OTN Lines Settings

Port (Display only) Displays the port • 18-1 (Trunk/Interlink)
number and optional name.
• 19-1 (Trunk)
Note Port 18 is a trunk
port in single-card
configuration and
an interlink port in
double-card
configuration
(ADM-10G peer
group).
ITU-TG.709 OTN Sets the OTN lines according to Enable

ITU-T G.709.
Disable
FEC Sets the OTN lines FEC mode. FEC Disable—FEC is off.
mode can be Disabled, Enabled, or,
for the TXP_MR_10E, Enhanced Standard—Standard FEC is
FEC mode can be enabled to on.
provide greater range and lower bit Enhanced—Enhanced FEC is
error rate. For TXP_MR_10E on.
cards, Standard is the same as
enabling FEC.
439

rate.
• 1E-6
• 1E-7
• 1E-8
• 1E-9
SF BER (Display only) Indicates the signal • 1E-5

fail bit error rate.
Synch Mapping Sets how the ODUk (client Synch mapping

payload) is mapped to the optical
channel (OTUk).
Table 164: ADM-10G Card ITU-T G.709 Threshold Settings

• 19-1 (Trunk)
port in single-card
configuration and
double-card
configuration
(ADM-10G peer
group).
440

ES Errored seconds. Selecting the SM Numeric. Threshold display
(OTUk) radio button selects FEC, options include:
overhead management, and PM Direction—Near End or Far
using OTUk. Selecting the PM
End
radio button selects path PM using
ODUk. Interval—15 Min (minutes) or
1 day
Types—SM (OTUk) or PM
(ODUk)

category and click Refresh.
ITU-T G.709 optical
order of k overhead
frame used for
management and
performance
is the ITU-T G.709
order of k overhead
performance
monitoring.
SES Severely errored seconds Numeric. Threshold display options

include:
• Direction—Near End or Far
End
• Interval—15 Min (minutes) or
1 day
• Types—SM (OTUk) or PM
(ODUk)
Choose an option in each category

and click Refresh.
441
UAS Unavailable seconds Numeric. Threshold display options

include:
End
1 day
(ODUk)

and click Refresh.
BBE Background block errors Numeric. Threshold display options

include:
End
1 day
(ODUk)

and click Refresh.
FC Failure counter Numeric. Threshold display options

include:
End
1 day
(ODUk)

and click Refresh.
442
Table 165: ADM-10G Card FEC Threshold Settings

• 19-1 (Trunk)
port in single-card
configuration and
double-card
configuration
(ADM-10G peer
group).
Bit Errors Corrected Displays the number of bit errors Numeric display. Can be set for
corrected during the selected time 15-minute or 1 day intervals.
period.
Uncorrectable Words Displays the number of Numeric display. Can be set for
uncorrectable words in the selected 15-minute or 1 day intervals.
time period.
Table 166: ADM-10GTrail Trace Identifier Settings
Port Sets the port number. • 18-1 (Trunk/Interlink)

• 19-1 (Trunk)
port in single-card
configuration and
double-card
configuration
(ADM-10G peer
group).
Level Sets the level. • Section

• Path
Received Trace Mode Sets the trace mode. • Off/None

• Manual
443

Disable FDI on TTIM If a Trace Identifier Mismatch on Checked (FDI on TTIM is
Section/Path overhead alarm arises disabled)
because of a J0/J1 overhead string
Unchecked (FDI on TTIM is
mismatch, no Forward Defect
Indication (FDI) signal is sent to not disabled)
the downstream nodes if this box
is checked.
Transmit Current Transmit String displays String of trace string size; trail trace
the current transmit string; New identifier is 64 bytes in length.
In Transmit String Type, click Hex
to change the display to
to Hex).
Expected Current Expected String displays String of trace string size

the current expected string; New
sets a new expected string. You can
In Expected String Type, click Hex
to Hex).
Received (Display only) Current Received String of trace string size

String displays the current received
string. You can click Refresh to
manually refresh this display, or
check the Auto-refresh every 5 sec
check box to keep this panel
updated.
Auto-refresh (every 5 sec) If checked, automatically refreshes Checked/unchecked (default)

Step 4 Click Apply.

444
NTP-G333 Adding an ADM-10G Card to an Existing Topology
NTP-G333 Adding an ADM-10G Card to an Existing Topology

Purpose This procedure adds an ADM-10G card to an existing
topology. Perform the steps in this procedure when
OCHNC and DCC are present in the network. In case
of OCH trails, delete all the circuits in Step 3 that
traverses the port before deleting the OCH-trail.
Prerequisite Procedures • DLP-G46 Log into CTC.

• Complete the turn up procedures in the "Turning
Up a Node" chapter for the node to be added.
• An updated Cisco Transport Planner network
plan recalculated with the new node.
Procedure
Step 1 If path protected circuits exist between Node A and Node B, complete the DLP-A197 Initiate a Path
Protection Force Switch task. This task applies a force switch on the path between Node A and Node B.
Step 2 Complete the NTP-G129 Add a DWDM Node task to add Node C.
Step 3 Complete the DLP-G106 Deleting Optical Channel Network Connections task to delete OCHNC circuit
between Node A and Node B.
Step 4 Complete the NTP-G59 Creating, Deleting, and Managing Optical Channel Network Connections task to
create OCHNC circuit between Node A-->Node C and Node C-->Node B for wavelength connectivity.
Note The ports on the card in Node C must be tuned to the same wavelength as Node A and Node B.
Step 5 Create DCC terminations on Node C. See the DLP-A377 Provision Section DCC Terminations task.
Alternatively, if additional bandwidth is needed for CTC management, complete the DLP-A378
Provision Line DCC Terminations task.
TNC reloads when SDCC and LDCC co-exist on the same card. This behavior is observed in the following
cards:
TXP-MR-10G
TXP-MR-2.5G
TXPP-MR-2.5G
TXP-MR-10E
445
NTP-G97 Modifying the 4x2.5G Muxponder Card Line Settings and PM Parameter Thresholds
MXP-MR-2.5G
MXPP-MR-2.5G
MXP-MR-10DME
MXP-MR-10DMEX
ADM-10G
TXP-MR-10EX
TXPP-MR-10EX
OTU2-XP
Step 6 Ensure that the DCCs are functional between Node A-->Node C and Node C-->Node B. See the "DLP-
G76 Provision DCC/GCC Terminations" task.
Step 7 Complete the following task to create pass-through STS or VC circuits in Node C.
NTP-G200 Creating, Deleting, and Managing STS or VC Circuits for the ADM-10G Card
Step 8 Complete the NTP-A301 Merge Circuits task for each circuit created.
Step 9 If path protected circuits exist between Node A and Node B, complete the DLP-A198 Clear a Path
Protection Force Switch task. This task clears a force switch on the path between Node A and Node B.
NTP-G97 Modifying the 4x2.5G Muxponder Card

Line Settings and PM Parameter Thresholds
for the MXP_2.5G_10G, MXP_2.5G_10E,
MXP_2.5G_10E_C, MXP_2.5G_10E_L, and
MXP_2.5G_10EX_C muxponder cards.

Muxponder Cards
necessary)
on page 321
446
DLP-G222 Changing the 4x2.5G Muxponder Card Settings
Procedure
settings.
DLP-G222 Changing the 4x2.5G Muxponder Card Settings, on page 447
DLP-G223 Changing the 4x2.5G Muxponder Line Settings, on page 449
DLP-G224 Changing the 4x2.5G Muxponder Section Trace Settings, on page 454
DLP-G225 Changing the 4x2.5G Muxponder Trunk Settings, on page 456
DLP-G226 Changing the 4x2.5G Muxponder SONET/SDH Line Thresholds Settings, on page 459
DLP-G303 Provisioning the 4x2.5G Muxponder Trunk Port Alarm and TCA Thresholds, on page 463
DLP-G304 Provisioning the 4x2.5G Muxponder Client Port Alarm and TCA Thresholds, on page 465
DLP-G228 Changing the 4x2.5G Muxponder Line OTN Settings, on page 466
DLP-G369 Changing the 4x2.5G Muxponder Trunk Wavelength Settings, on page 458
Step 3 As needed, complete the NTP-G103 Backing Up the Database task.


Purpose This task changes the card settings for the
MXP_2.5G_10G, MXP_2.5G_10E,
MXP_2.5G_10EX_C muxponder cards, including
payload type, termination mode, and wavelength.
447
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_2.5G_10G,
MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, or MXP_2.5G_10EX_C card where you want to
change the card settings.
Step 3 Modify any of the settings described in the following table. The Parameters shown in the following table do
not apply to all 4x2.5G muxponder cards. If the parameter or option does not apply, it is not shown in CTC.
Table 167: MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, or MXP_2.5G_10EX_C Card Settings

Termination Mode Sets the mode of operation. Options For ANSI platforms:
that do not apply to a card do not
• Transparent
display.
The MXP_2.5G_10G card is based • Section (MXP_2.5G_10E,
on SONET/SDH multiplexing. The MXP_2.5G_10E_C,
transparent mode terminates and MXP_2.5G_10E_L, and
rebuilds the B1 byte (as well as MXP_2.5G_10EX_C only)
other bytes) of the incoming • Line (MXP_2.5G_10G only)
OC-48/STM-16 signal. The B2 byte
is not touched. For ETSI platforms:
The MXP_2.5G_10E, • Transparent
MXP_2.5G_10E_C,
MXP_2.5G_10E_L, and • Multiplex Section
MXP_2.5G_10EX_C cards are (MXP_2.5G_10G, only)
fully transparent in transparent
• Regeneration Section
mode based on the
(MXP_2.5G_10E,
OTN/ITU-T G.709 multiplexing
MXP_2.5G_10E_C,
scheme. It does not terminate the
MXP_2.5G_10E_L, and
B1 byte or other bytes.
MXP_2.5G_10EX_C only)
It encapsulates OC-48/STM-16
bytes into ODU1 first, then
multiplexes them into an OTU2.
AIS/Squelch (MXP_2.5G_10E, Ais
MXP_2.5G_10E_C,
Squelch
MXP_2.5G_10E_L, and
MXP_2.5G_10EX_C only) Sets the
transparent termination mode
configuration.
448
DLP-G223 Changing the 4x2.5G Muxponder Line Settings
Tunable Wavelengths (Display only) Shows the supported —

wavelengths of the trunk port after
the card is installed. For the
MXP_2.5G_10E_C, or
MXP_2.5G_10E_L cards, the first
and last supported wavelength,
frequency spacing, and number of
supported wavelengths are shown
in the format: first wavelength-last
wavelength-frequency
spacing-number of supported
wavelengths. For example, the
MXP_2.5G_10E_C card would
show:
1529.55nm-1561.83nm-50gHz-82.
The MXP_2.5G_10G and
MXP_2.5G_10E show the four
that is installed. You can also view
the bandwidth of the wavelength
information in THz.
Step 4 Click Apply.


Purpose This task changes the line settings for the
MXP_2.5G_10G, MXP_2.5G_10E,
449
Procedure
change the line settings.
Step 2 Click the Provisioning > Line > SONET (ANSI) or SDH (ETSI) tabs.
Note The SONET tab appears only if you have created a PPM for a given port.

Table 168: MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, or MXP_2.5G_10EX_C Card Line Settings

Port (Display only) Port number. Ports 1
1 to 4 are client ports
2
(OC-48/STM-16). Port 5 is the
DWDM trunk (OC-192/STM-64) 3
that provides wavelength services.
Client ports will not appear of the 4
pluggable port module is not 5 (Trunk) (MXP_2.5G_10G
provisioned for it.
only)
Port Name Provides the ability to assign the User-defined. Name can be up
specified port a logical name. to 80 alphanumeric/ special
characters. Blank by default.
IS,AINS (ANSI) or
administrative states, see the Unlocked,automaticInService
OOS,MT (ANSI) or
450

Unlocked-disabled,
OOS-MA,MT (ANSI) or
Locked-
SF BER Sets the signal fail bit error rate. 1E-3

1E-4
1E-5
SD BER Sets the signal degrade bit error 1E-5

rate. 1E-6
1E-7
1E-8
1E-9
451

ALS Mode Sets the ALS function mode. The Disable (default): ALS is off;
DWDM transmitter supports ALS the laser is not automatically
according to ITU-T G.644 (06/99). shut down when traffic
ALS can be disabled or can be set outages (LOS) occur.
for one of three mode options.
Auto Restart: ALS is on; the
laser automatically shuts
(LOS) occur. It automatically
restarts when the conditions
resolved.
Manual Restart: ALS is on; the
(LOS) occur. However, the
resolved.
Manual Restart for Test:
for testing.
AINS Soak Sets the automatic in-service soak Duration of valid input signal,
period. Double-click the time and in hh.mm format, after which
use the up and down arrows to the card becomes in service
change settings. (IS) automatically
0 to 48 hours, 15-minute
increments
Type Sets the optical transport type. SONET

SDH
SyncMsgIn Enables synchronization status Checked or unchecked

messages (S1 byte), which allow
the node to choose the best timing
source. (This parameter does not
appear for the MXP_2.5G_10E
trunk port.)
452
Displays the optical reach distance Options: ANSI/ETSI

of the client port.
• Autoprovision/Autoprovision
(default)

ProvidesSync Sets the ProvidesSync card Checked or unchecked
parameter. If checked, the card is
provisioned as an NE timing
reference. (This parameter does not
appear for the MXP_2.5G_10E
trunk port.)
Reach
• SR
• SR 1/I-1—Short reach up to
2-km distance
• IR 1/S1—Intermediate reach,
• IR 2/S2—Intermediate reach
40-km distance
80-km distance
80-km distance

client port.
• Further wavelengths: 850 nm
through 1560.61 nm 100-GHz
ITU spacing CWDM spacing
. You can also view the
bandwidth of the wavelength
information in THz.
Step 4 Click Apply.

453
DLP-G224 Changing the 4x2.5G Muxponder Section Trace Settings

Purpose This task changes the section trace settings for the
MXP_2.5G_10G, MXP_2.5G_10E,
Note The Section Trace tab appears only if you have created a PPM for the card.
Procedure
change the section trace settings.
Table 169: MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, or MXP_2.5G_10EX_C Card Section Trace Settings
Port Sets the port number. •1

•2
•3
•4
• 5 (Trunk; MXP_2.5G_10G
only)

• Manual
454

checked.
Transmit Section Trace String Size Sets the trace string size. Select • 1 byte
either radio button.
• 16 byte
to Hex).

changes to Hex).
panel updated.

Step 4 Click Apply.

455
DLP-G225 Changing the 4x2.5G Muxponder Trunk Settings

Purpose This task provisions the trunk settings for the
MXP_2.5G_10E, MXP_2.5G_10E_C,
MXP_2.5G_10E_L, and MXP_2.5G_10EX_C
muxponder cards.
Note This task does not apply to the MXP_2.5G_10G card.
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_2.5G_10E,
MXP_2.5G_10E_C, MXP_2.5G_10E_L, or MXP_2.5G_10EX_C card where you want to change the trunk
settings.
Step 2 Click the Provisioning > Line > Trunk tabs.
Table 170: MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, or MXP_2.5G_10EX_C Card Trunk Settings

Port (Display only) Displays the port 5 (Trunk)
number. Port 5 is the DWDM trunk
(OC-192/STM-64) that provides
wavelength services.
specified port a logical name. to 80 alphanumeric/ special
456

IS,AINS (ANSI) or
OOS,MT (ANSI) or

gives the overall condition of the OOS-AU,AINS (ANSI) or
Unlocked-disabled,
automaticInService (ETSI)
Qualifier, Secondary State. For
OOS-MA,MT (ANSI) or
Locked-
ALS Mode Sets the ALS function mode. The Disabled (default): ALS is off;
for one of three mode options. Auto Restart: ALS is on; the
(LOS) occur. It
Manual Restart: ALS is on;
resolved.
for testing.
457
DLP-G369 Changing the 4x2.5G Muxponder Trunk Wavelength Settings

AINS Soak (OC-N and STM-N payloads only) Duration of valid input signal,
Sets the automatic in-service soak in hh.mm format, after which
period. the card becomes in service
(IS) automatically
increments
Step 4 Click Apply.

DLP-G369 Changing the 4x2.5G Muxponder Trunk Wavelength Settings

the MXP_2.5G_10G, MXP_2.5G_10E,
MXP_2.5G_10EX_C cards.
Procedure
MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, and MXP_2.5G_10EX_C card where you want
to change the trunk wavelength settings.
Table 171: MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, and MXP_2.5G_10EX_C Card Wavelength Trunk Settings

number.
458
DLP-G226 Changing the 4x2.5G Muxponder SONET/SDH Line Thresholds Settings

Band (Display only) Indicates the C—The C-band wavelengths
wavelength band available from the are available in the
card that is installed. If the card is Wavelength field.
preprovisioned, the field can be
L—The L-band wavelengths
provisioned to the band of the card
are available in the
that will be installed.
Wavelength field.

provisioning for or L-band wavelengths in the
MXP_2.5G_10E_C and Wavelength field.
MXP_2.5G_10E_L cards. (This
field does not apply to
MXP_2.5G_10G or
MXP_2.5G_10E cards.) Wavelength field.

the
trunk.
100-GHz ITU-T C-band or
L-band spacing, depending
on the card that is installed.
For MXP_2.5G_10G and
MXP_2.5G_10E cards, the
background.You can view
the bandwidth of wavelength
information in THz.
Step 4 Click Apply.

DLP-G226 Changing the 4x2.5G Muxponder SONET/SDH

Line Thresholds Settings
Purpose This task changes the SONET (ANSI) or SDH (ETSI)
line threshold settings for the MXP_2.5G_10G,
MXP_2.5G_10E, MXP_2.5G_10E_C,
MXP_2.5G_10E_L, and MXP_2.5G_10EX_C
muxponder cards.
459
Procedure
change the line threshold settings.
Step 2 Click the Provisioning > Line Thresholds tabs.
Step 3 Modify any of the settings described in the following table. Some parameter tabs or selections do not always
apply to all 4x2.5G muxponder cards. If the tabs or selections do not apply, they do not appear in CTC.
Table 172: MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, or MXP_2.5G_10EX_C Card Line Threshold Settings

Port (Display only) Port •1 •1
number
•2 •2
•3 •3
•4 •4
• 5 (MXP_2.5G_10G • 5 (MXP_2.5G_10G
only) only)

block
or Far End
(minutes) or 1 day
Section or
(near end only)

category and click
Refresh.
460

or Far End
(minutes) or 1 day
• Types—Line or
Section (near end
only)

category and click
Refresh.

(near end only)
Refresh.
(near end only)
Refresh.
461
SEFS (Near End Section or Numeric. Threshold —

framing seconds
or Far End
(minutes) or 1 day
• Types—Line or
Section (near end
only)

category and click
Refresh.
or Far End
(minutes) or 1 day
Section or
(near end only)

category and click
Refresh.
or Far End
(minutes) or 1 day
• Types—Line or
Section (near end
only)

category and click
Refresh.
462
DLP-G303 Provisioning the 4x2.5G Muxponder Trunk Port Alarm and TCA Thresholds

• Types—Line or • Types—Multiplex
(near end only)
Refresh.
Step 4 Click Apply.

DLP-G303 Provisioning the 4x2.5G Muxponder Trunk Port

Purpose This task changes the MXP_2.5G_10G,
MXP_2.5G_10E, MXP_2.5G_10E_C,
MXP_2.5G_10E_L, and MXP_2.5G_10EX_C trunk
port alarm and TCA thresholds.
Procedure
change the trunk port alarm and TCA settings.
Step 3 Select TCA (if not already selected), a 15 Min or 1 Day PM interval radio button and then click Refresh.
463
DLP-G303 Provisioning the 4x2.5G Muxponder Trunk Port Alarm and TCA Thresholds
Step 4 Referring to the following table, verify the trunk port (Port 5) TCA thresholds for RX Power High, RX
Power Low, TX Power High, and TX Power Low.
Step 5 Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting
it, entering a new value, and pressing Enter.
Table 173: MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, or MXP_2.5G_10EX_C Trunk Port TCA Thresholds

MXP_2.5G_10G –8 dBm –18 dBm 7 dBm –1 dBm
MXP_2.5G_10E –9 dBm –18 dBm 9 dBm 0 dBm
MXP_2.5G_10E_C –9 dBm –18 dBm 9 dBm 0 dBm
MXP_2.5G_10E_L –9 dBm –18 dBm 9 dBm 0 dBm
MXP_2.5G_10EX_C –9 dBm –18 dBm 9 dBm 0 dBm
Step 6 Click Apply.

Step 8 Referring to the following table, verify the trunk port (Port 5) Alarm thresholds for RX Power High, RX Power
Low, TX Power High, and TX Power Low.
Table 174: MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, or MXP_2.5G_10EX_C Trunk Port Alarm Thresholds

MXP_2.5G_10G –8 dBm –20 dBm 4 dBm 2 dBm
MXP_2.5G_10E –8 dBm –20 dBm 7 dBm 3 dBm
MXP_2.5G_10E_C –8 dBm –20 dBm 7 dBm 3 dBm
MXP_2.5G_10E_L –8 dBm –20 dBm 7 dBm 3 dBm
MXP_2.5G_10EX_C –8 dBm –20 dBm 7 dBm 3 dBm
464
DLP-G304 Provisioning the 4x2.5G Muxponder Client Port Alarm and TCA Thresholds
DLP-G304 Provisioning the 4x2.5G Muxponder Client Port

thresholds for the MXP_2.5G_10G, MXP_2.5G_10E,
MXP_2.5G_10EX_C cards.

page 321
Procedure
change the client port alarm and TCA settings.
Step 3 Referring to the following table, verify the client Port N (where N = 1 through 4) TCA thresholds for RX
Power High, RX Power Low, TX Power High, and TX Power Low based on the client interface at the other
end.
and click Refresh.
CPAK Modules, on page 310
465
DLP-G228 Changing the 4x2.5G Muxponder Line OTN Settings
Table 175: MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, or MXP_2.5G_10EX_C

Card Client Interfaces TCA Thresholds
CTC) Module (SFP) High Low High Low
OC-48 ONS-SE-2G-S1 –3 –18 3 –16
15454-SFP-OC48-IR 0 –18 6 –11
STM-16 ONS-SE-2G-S1 –3 –18 3 –16
15454E-SFP-L.16.1 0 –18 6 –11
Step 5 Provision each additional client port.

Step 7 Referring to the following table, verify the client Port N (where N = 1 through 4) Alarm thresholds for RX
Power High, RX Power Low, TX Power High, and TX Power Low based on the client interface that is
provisioned.
Table 176: MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, or MXP_2.5G_10E_L Card Client Interfaces Alarm Thresholds
CTC) Module (SFP) High Low High Low
OC-48 ONS-SE-2G-S1 0 –21 0 –13
15454-SFP-OC48-IR 3 –21 3 –8
STM-16 ONS-SE-2G-S1 0 –21 0 –13
15454E-SFP-L.16.1 3 –21 3 –8
Step 9 Click Apply.


Purpose This task changes the line OTN settings for
MXP_2.5G_10G, MXP_2.5G_10E,
466
Procedure
change the line OTN settings.
Step 2 Click the Provisioning > OTN tabs, then choose one of the following subtabs: OTN Lines,
OTN G.709 Thresholds, FEC Thresholds, or Trail Trace Identifier.
Step 3 Modify any of the settings as described in the following tables.
Note You must modify Near End and Far End independently, 15 Min and 1 Day independently, and SM
and PM independently. To do so, choose the appropriate radio button and click Refresh.
Note In the following table, some parameter tabs or values do not always apply to all MXP_2.5G_10G,
MXP_2.5G_10E, MXP_2.5G_10E_C, or MXP_2.5G_10E_L cards. If the tabs or values do not
apply, they do not appear in CTC.
Table 177: MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, or MXP_2.5G_10EX_C Card Line OTN Settings

Port (Display only) Displays the port (Trunk)
number.
G.709 OTN Sets the OTN lines according to Enable

ITU-T G.709.
Disable
FEC Sets the OTN line FEC mode. FEC Enable—(MXP_2.5G_10G

mode can be Disabled or Enabled. only) FEC is on.
With the MXP_2.5G_10E card,
Enhanced FEC (E-FEC) mode can Disable—FEC is off.
be enabled to provide greater range Standard—(MXP_2.5G_10E
and lower bit error rate. E-FEC only) FEC is on.
applies only to the MXP_2.5G_10E
card. Enhanced—(MXP_2.5G_10E
only) Enhanced FEC is on.
467

rate.
• 1E-6
• 1E-7
• 1E-8
• 1E-9
SF BER (Display only) Sets the signal fail • 1E-5

bit error rate.
Asynch/Synch Mapping (MXP_2.5G_10E only) The • ODU Multiplex

MXP_2.5G_10E can perform
standard ODU multiplexing
according to ITU-T G.709. The
card uses this to aggregate the four
OC-48 client signals.
Table 178: MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, or MXP_2.5G_10EX_C ITU-T G.709 Threshold Settings
Port (Display only) Port number 5 (Trunk)
468

ES Errored seconds Numeric. Threshold display options
include:
End
1 day
(ODUk)

and click Refresh.
ITU-T G.709 optical
order of k overhead
frame used for
management and
performance
is the ITU-T G.709
order of k overhead
performance
monitoring.
SES Severely errored seconds. Two Numeric. Threshold display

types of thresholds can be asserted. options include:
Selecting the SM (OTUk) radio
Direction—Near End or Far
button selects FEC, overhead
management, and PM using OTUk. End
Selecting the PM radio button Interval—15 Min (minutes) or
selects path PM using ODUk. 1 day
(ODUk)

469
UAS Unavailable seconds Numeric. Threshold display options

include:
End
1 day
(ODUk)

and click Refresh.
BBE Background block errors Numeric. Threshold display options

include:
End
1 day
(ODUk)

and click Refresh.
FC Failure counter Numeric. Threshold display options

include:
End
1 day
(ODUk)

and click Refresh.
Table 179: MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, or MXP_2.5G_10EX_C FEC Threshold Settings

number.
470
Bit Errors Corrected Displays the number of bit errors Numeric

corrected during the interval
selected. The interval can be set for
15 minutes or one day.
Uncorrectable Words Displays the number of Numeric

uncorrectable words during the
interval selected. The interval can
be set for 15 minutes or one day.
Table 180: MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, or MXP_2.5G_10EX_C Trail Trace Identifier Settings
Port Sets the port number. The trail trace 5 (Trunk)

identifier is applicable only to the
trunk interface, which handles
ITU-T G.709 frames.

• Path

• Manual
Disable FDI on TTIM If a Trace Identifier Mismatch on • Checked (FDI on TTIM is

Section overhead alarm arises disabled)
because of a J0 overhead string
mismatch, no Forward Defect • Unchecked (FDI on TTIM is
is checked.
to Hex).
471
NTP-G99 Modifying the 2.5G Data Muxponder Card Line Settings and PM Parameter Thresholds

changes to Hex).
every 5 sec box to keep this panel
updated.

Step 4 Click Apply.

NTP-G99Modifyingthe2.5GDataMuxponderCardLineSettings
and PM Parameter Thresholds
for the MXP_MR_2.5G and MXPP_MR_2.5G
muxponder cards.

Muxponder Cards
necessary)
on page 321
472
DLP-G236 Changing the 2.5G or 10G Data Muxponder Client Line Settings
Procedure
settings.
DLP-G237 Changing the 2.5G Data Muxponder Distance Extension Settings
DLP-G238 Changing the 2.5G or 10G Data Muxponder SONET/SDH Settings
DLP-G239 Changing the 2.5G or 10G Data Muxponder Section Trace Settings
DLP-G240 Changing the 2.5G or 10G Data Muxponder SONET or SDH Line Thresholds
DLP-G321 Changing the 2.5G or 10G Data Muxponder Line RMON Thresholds
DLP-G307 Provisioning the 2.5G Data Muxponder Trunk Port Alarm and TCA Thresholds
DLP-G308 Provisioning the 2.5G Data Muxponder Client Port Alarm and TCA Thresholds
DLP-G370 Changing the 2.5G or 10G Data Muxponder Trunk Wavelength Settings
Note To use the Alarm Profiles tab, including creating alarm profiles and suppressing alarms, see
the Alarm and TCA Monitoring and Management document.
Purpose This task changes the client line settings for
MXP_MR_2.5G, MXPP_MR_2.5G,
MXP_MR_10DME_C, MXP_MR_10DME_L, and
MXP_MR_10DMEX_C muxponder cards.
473
Procedure
to change the line settings.
Step 2 Click the Provisioning > Line > Client tabs. Tabs and parameter selections vary according to
PPM provisioning.
Step 3 Modify any of the settings for the Client tab as described in the following table.
Table 181: 2.5G or 10G Data Muxponder Card Client Settings

Port (Display only) Port number. 1 and 2 for 2.5G data
muxponder cards
1 through 8 for 10G data
muxponder cards
Port Name The user can assign a logical name User-defined. Name can be up to
for each of the ports shown by 80 alphanumeric/special
filling in this field. characters. Blank by default.
Note You can provision a
string (port name) for
each fiber
channel/FICON interface
on the cards, which
allows the MDS Fabric
Manager to create a link
association between that
SAN port and a SAN
port on a
Cisco MDS 9000 switch.
change. For more information about OOS,DSBLD (ANSI) or
administrative states, see the Locked,disabled (ETSI)
474

Service State Identifies the autonomously IS-NR (ANSI) or Unlocked-
generated state that gives the enabled (ETSI)
overall condition of the port.
Service states appear in the format:
Unlocked-disabled,
Primary State-Primary State
OOS-MA,MT (ANSI) or
Locked-
ALS Mode Sets the ALS function mode. Disabled (default): ALS is off;
the laser is not automatically
shut down when traffic
outages (LOS) occur.
Auto Restart:
(MXP_MR_2.5G only) ALS
is on; the laser automatically
shuts down when traffic
outages (LOS) occur. It
resolved.
for testing.
475

Reach Displays the optical reach distance The reach distances that appear
of the client port. in the drop-down list depend on
the card:
Autoprovision—The system to
automatically provision the
reach from the pluggable port
module (PPM) reach value
on the hardware.
SX—Short laser wavelength
on multimode fiber optic
cable for a maximum length
of 550 meters. The operating
wavelength range is 770-860
nm.
LX—Long wavelength for a
long haul fiber optic cable for
a maximum length of 10 km.
The operating wavelength
range is 1270-1355 nm.
CX—Two pairs of 150-ohm
shielded twisted pair cable
for a maximum length of 25
meters.
T—Four pairs of Category 5
Unshielded Twisted Pair
cable for a maximum length
of 100 meters.
DX—Single mode up to 40 km.
HX—Single mode up to 40 km.
ZX—Extended wavelength
single-mode optical fiber for
up to 100 km. The operating
wavelength range is 1500-
1580 nm.
VX—Single mode up to 100
km. The operating wavelength
476

Wavelength Displays the wavelength of the First Tunable Wavelength
client port.
Further wavelengths:850 nm
through 1560.61 nm; 100-GHz
ITU spacing; CWDM spacing
Squelch Shuts down the far-end laser in Squelch

response to certain defects.
(Squelch does not apply to ISC Disable
COMPACT payloads.)
Step 4 Click Apply.


Purpose This task changes the distance extension settings for
MXP_MR_2.5G and MXPP_MR_2.5G muxponder
cards.
Note Distance extension settings can be changed only if the facilities are out of service (OOS,DSBLD).
Note The distance extension parameters only apply to client ports (Ports 1 to 8) and not to the trunk ports (Port 9
for MXP_MR_2.5G card or Ports 9 and 10 for the MXPP_MR_2.5G card).
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_MR_2.5G or
MXPP_MR_2.5G card where you want to change the distance extension settings.
Step 2 Click the Provisioning > Line > Client tabs. A client port must be provisioned for the tab to be present.
477
Step 3 Locate the Client port table row and verify that the Service State column value is OOS-MA,DSBLD (ANSI)
or Locked-enabled,disabled (ETSI). If yes, continue with Step 4. If not, complete the following substeps:
Step 4 Click the Provisioning > Line > Distance Extension tabs. Tabs and parameter selections vary according
to PPM provisioning.
Step 5 Modify any of the settings for the Distance Extension tab as described in the following table.
Table 182: MXP_MR_2.5G or MXPP_MR_2.5G Card Line Distance Extension Settings
Port (Display only) Port number •1

•2
Enable Distance Extension Allows end-to-end distances of up Checked or unchecked

to 1600 km for FC1G and up to 800
km for FC2G. If Distance
Extension is enabled, set the
connected Fibre Channel switches
to Interop or Open Fabric mode,
depending on the Fibre Channel
switch. By default, the
MXP_MR_2.5G and
MXPP_MR_2.5G card will
interoperate with the Cisco
Multilayer Director Switch (MDS)
storage products.
Auto Detect Credits Allows automatic detection of Checked or unchecked

buffer credits for Fibre Channel
flow control.
Credits Available (Display only) Displays the number Numeric (range depends on the
of buffer credits available. client equipment attached to
the card)
Autoadjust GFP Buffer Threshold Allows the threshold of the generic Checked or unchecked
framing procedure (GFP) buffer
between two MXP_MR_2.5G or
two MXPP_MR_2.5G cards to be
automatically adjusted.
478
GFP Buffers Available Displays the number of GFP Numeric

buffers available between two
MXP_MR_2.5G or two
MXPP_MR_2.5G cards.
Step 6 Click Apply.


Purpose This task changes the OC-48 (ANSI) or STM-16
(ETSI) settings for MXP_MR_2.5G and
MXPP_MR_2.5G muxponder cards. This task also
changes the OC-192 (ANSI) or STM-64 (ETSI)
settings for the MXP_MR_10DME_C and
MXP_MR_10DME_L muxponder cards.
Note SONET (OC-48)/SDH (STM-16) settings apply only to the trunk ports (Port 9 for the MXP_MR_2.5G card
and Ports 9 and 10 for the MXPP_MR_2.5G card.)
Procedure
change the OC-48/STM-64 settings.
Step 2 Click the Provisioning > Line > SONET (ANSI) or SDH (ETSI). Tabs and parameter selections vary
according to PPM provisioning.
Step 3 Modify any of the settings for the SONET or SDH tab as described in the following table.
479
Table 183: MXP_MR_2.5G or MXPP_MR_2.5G Card Line SONET or SDH Settings

Port (Display only) Port number. 9 (trunk for MXP_MR_2.5G,
MXP_MR_10DME_C, and
MXP_MR_10DME_L) or 9 and 10
(trunks for MXPP_MR_2.5G)
specified port a name. to 80 alphanumeric/ special
IS,AINS (ANSI) or
OOS,MT (ANSI) or

Unlocked-disabled,
OOS-MA,MT (ANSI) or
(ETSI)

1E-4
1E-5

rate.
• 1E-6
• 1E-7
• 1E-8
• 1E-9
480

ALS Mode Sets the ALS function mode. The Disable (default): ALS is off;
for one of three mode options.
Auto Restart: ALS is on; the
(LOS) occur. It
resolved.
for testing.
use the up and down arrows to the card becomes in service
change settings. (IS) automatically
increments
Type The optical transport type. SONET (ANSI)

SDH (ETSI)
SyncMsgIn Sets the EnableSync card Checked or unchecked

parameter. Enables synchronization
status messages (S1 byte), which
allow the node to choose the best
timing source.
Send DoNotUse Sets the Send DoNotUse card state. Checked or unchecked
When checked, sends a DUS
message on the S1 byte.
481

parameter. If checked, the card
is provisioned as an NE timing
reference.
SF BER and SD BER thresholds apply only to trunk ports (Port 9 for MXP_MR_2.5G and Ports 9 and 10
for MXPP_MR_2.5G).
Step 4 Click Apply.
Purpose This task changes the section trace settings for the
MXP_MR_2.5G, MXPP_MR_2.5G,
MXP_MR_10DME_C and MXP_MR_10DME_L
muxponder cards.
Procedure
Step 2 Click the Provisioning > Line > Section Trace tabs. Tabs and parameter selections vary according to
PPM provisioning.
Step 3 Modify any of the settings in the Section Trace tab as described in the following table.
482
Table 184: 2.5G or 10G Data Muxponder Card Line Section Trace Settings

Port (Display only) Port number. 9 (trunk port for
MXP_MR_2.5G,
MXP_MR_10DME_C, and
MXP_MR_10DME_L)
9 and 10 (trunk ports for
MXPP_MR_2.5G)
Received Trace Mode Sets the received trace mode. Off/None

Manual

checked.
• 16 byte
to Hex).

changes to Hex).
483
panel updated.

Step 4 Click Apply.

DLP-G370Changingthe2.5Gor10GDataMuxponderTrunkWavelengthSettings
the MXP_MR_2.5G, MXPP_MR_2.5G,
MXP_MR_10DME_C, and MXP_MR_10DME_L
cards.
Procedure
to change the trunk wavelength settings.
Table 185: 2.5G or 10G Data Muxponder Card Wavelength Trunk Settings

number.
10 (Trunk) (MXPP_MR_2.5G
only)
484

Band (Display only) Indicates the C—The C band wavelengths
wavelength band that can be are available in the
provisioned. The field is Wavelength field.
display-only when a physical
(MXP_MR_10DME_C, and
MXP_MR_10DME_C or
MXP_MR_10DME_L only)
MXP_MR_10DME_L is installed.
L—The L-band
If the card is provisioned in CTC
only, you can provision the band wavelengths are available in
for the card that will be installed. the Wavelength field.

provisioning. This field does not or L-band wavelengths in the
apply to MXP_MR_2.5G or Wavelength field.
MXPP_MR_2.5G cards
Wavelength field.

the
trunk.
100-GHz ITU-T, C-band
spacing. If the card is
installed, the wavelengths it
carries are identified with two
asterisks. Other wavelengths
have a dark grey background.
If the card is not installed, all
wavelengths appear with a
dark grey background.
Step 4 Click Apply.

DLP-G240 Changing the 2.5G or 10G Data Muxponder SONET

or SDH Line Thresholds
Purpose This task changes the SONET or SDH line threshold
settings for MXP_MR_2.5G, MXPP_MR_2.5G,
MXP_MR_10DME_C, and MXP_MR_10DME_L
muxponder cards.
485
Procedure
to change the line threshold settings.
Step 3 Modify any of the settings as shown in the following table.
Note You must modify Near End and Far End independently, 15 Min and 1 Day independently, and
Note In the following table, some parameters or options do not apply to all the cards. If the parameters
or options do not apply, they do not appear in CTC.
Table 186: 2.5G or10G Data Muxponder Card Line Threshold Settings
Field Description ONS 15454 Options ONS 15454 SDH Options

Port (Display only) Port • 9 (MXP_MR_2.5G) • 9 (MXP_MR_2.5G)
number
• 9 and 10 • 9 and 10
(MXPP_MR_2.5G) (MXPP_MR_2.5G)
• 9 (Trunk) for 9 (Trunk) for
MXP_MR_10DME_C MXP_MR_10DME_C
and and
MXP_MR_10DME_L MXP_MR_10DME_L

bits are in error within a Direction—Near End
block
or Far End
Interval—15 Min
(minutes) or 1 day
Types—Multiplex
Section or
(near end only)
Choose an option in
Refresh.
486

or Far End
(minutes) or 1 day
• Types—Line or
Section (near end
only)

category and click
Refresh.

(near end only)
Refresh.
(near end only)
Refresh.
487

Direction—Near End
or Far End
Interval—15 Min
(minutes) or 1 day
Types—SM (OTUk)
or PM (ODUk)
Choose an option in
Refresh.
SEFS (Section or Regeneration Numeric. Threshold —

Section only) Severely display options include:
errored framing seconds • Direction—Near End
or Far End
(minutes) or 1 day
• Types—Section only

category and click
Refresh.
or Far End
(minutes) or 1 day
• Types—Section only

category and click
Refresh.
488

• Types—Section only • Types—Regeneration
Section (only)
Refresh.
Step 4 Click Apply.

MXP_MR_10G and MXPP_MR_2.5G transponder
cards carrying the 1G Ethernet or 1G FC/FICON
payloads. This task changes the line threshold settings
for MXP_MR_10DME_C and MXP_MR_10DME_L
cards carrying Ethernet, FC/FICON, or ISC/ISC3
payloads.
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), display the card where you want to change
the line RMON threshold settings.
489
Step 4 From the Port drop-down list, choose the applicable port, either the payload port, for example “1-1
(ONE_GE)”, or the equivalent ITU-T G.7041 GFP (Generic Frame Procedure) port.
Step 5 From the Variable drop-down list, choose an Ethernet, FC, FICON, or ISC variable.
Table 187: MXP_MR_2.5G and MXPP_MR 2.5G Card 1G Ethernet or 1G, 2G FC/FICON Variables
ifInOctets Number of bytes received since the last counter reset.
rxTotalPkts Total number of receive packets.
ifInDiscards Number of inbound packets that were chosen to be

discarded even though no errors had been detected to
prevent their being deliverable to a higher-layer
protocol.
ifInErrors Total number of receive errors.
ifOutOctets The total number of octets transmitted out of the

txTotalPkts Total number of transmitted packets.
ifOutDiscards Number of outbound packets that were chosen to be

discarded even though no errors had been detected to
prevent their being transmitted.
mediaIndStatsRxFramesTruncated Total number of frames received that are less than 5

bytes. This value is a part of high-level data link
control (HDLC) and GFP port statistics.
mediaIndStatsRxFramesTooLong Number of received frames that exceed the maximum

transmission unit (MTU). This value is part of HDLC
and GFP port statistics.
mediaIndStatsRxFramesBadCRC Number of receive data frames with payload cyclic

redundancy check (CRC) errors when HDLC framing
is used.
mediaIndStatsTxFramesBadCRC Number of transmitted data frames with payload CRC

errors when HDLC framing is used.
8b10bInvalidOrderedSets Number of 8b10b disparity violations on the Fibre

Channel line side.
8b10bStatsEncodingDispErrors Number of 8b10b disparity violations on the Fibre

Channel line side.
Table 188: MXP_MR_10DME_C or MXP_MR_10DME_L Ethernet Variables
490


bytes. This value is a part of HDLC and GFP port
statistics.
mediaIndStatsRxFramesTooLong Number of received frames that exceed the MTU.

This value is part of HDLC and GFP port statistics.
mediaIndStatsRxFramesBadCRC Number of receive data frames with payload CRC


8b10bInvalidOrderedSetsDispErrorsSum Number of code violations/running disparity errors

in the 8b/10b encoded characters received.
Table 189: MXP_MR_10DME_C or MXP_MR_10DME_L FC/FICON Variables

ifOutOversizePkts Total number of oversized packets output from the

interface.

statistics.


491

fcStatsZeroTxCredits This is a count that increments when the FC/FICON

Tx credits go from a non-zero value to zero.
fcStatsRxRecvrReady Number of received RDY (Receive Ready) order set.
fcStatsTxRecvrReady Number of transmitted RDY (Receive Ready) order

set.
8b10bInvalidOrderedSetsDispErrorsSum Number of Code Violations/Running Disparity errors

Table 190: MXP_MR_10DME_C or MXP_MR_10DME_L ISC and ISC3Variables

8b10bInvalidOrderedSetsDispErrorsSum Number of Code Violations/Running Disparity errors

Table 191: MXP_MR_10DME_C or MXP_MR_10DME_L GFP RMON Variables
gfpStatsRxSBitErrors Received generic framing protocol (GFP) frames with

single bit errors in the core header (these errors are
correctable).
gfpStatsRxTypeInvalid Received GFP frames with invalid type (these are

discarded). For example, receiving GFP frames that
contain Ethernet data when we expect Fibre Channel
data.
gfpStatsRxSblkCRCErrors Total number of superblock CRC errors with the

receive transparent GFP frame. A transparent GFP
frame has multiple superblocks which each contain
Fibre Channel data.
gfpStatsCSFRaised Number of Rx client management frames with Client

Signal Fail indication.
492
DLP-G307 Provisioning the 2.5G Data Muxponder Trunk Port Alarm and TCA Thresholds
gfpStatsLFDRaised The number of Core HEC CRC Multiple Bit Errors.

Note This count is only for cHEC multiple bit
error when in frame. It is a count of when
the state machine goes out of frame.
Step 11 Click OK.

DLP-G307 Provisioning the 2.5G Data Muxponder Trunk Port

Purpose This task changes the MXP_MR_2.5G and
MXPP_MR_2.5G trunk port alarm and TCA
thresholds.
493
Note Throughout this task, trunk port refers to Port 9 (MXP_MR_2.5G and MXPP_MR_2.5G) and Port 10
(MXPP_MR_2.5G only).
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the
MXP_MR_2.5G or MXPP_MR_2.5G card where you want to change the trunk port alarm and TCA settings.
Step 3 Verify the trunk port TCA thresholds for RX Power High is –9 dBm and for RX Power Low is –23 dBm.
Step 6 Verify the trunk port Alarm thresholds for RX Power High is –7 dBm and for RX Power Low is –26 dBm.
Step 8 Click Apply.
DLP-G308 Provisioning the 2.5G Data Muxponder Client Port

thresholds for the MXP_MR_2.5G and
MXPP_MR_2.5G cards.

page 321
494
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_MR_2.5G or
MXPP_MR_2.5G card where you want to change the client port alarm and TCA settings.
Step 3 Referring to the following table, verify the client port (Ports 1 through 8) TCA thresholds for RX Power High,
RX Power Low, TX Power High, and TX Power Low based on the client interface at the other end. Provision
new thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a
new value, and hitting Enter.
and click Refresh.
about SFPs and XFPs, see the SFP, SFP+, QSFP+, XFP, CXP, CFP, CFP2 and CPAK Modules,
on page 310.
Table 192: MXP_MR_2.5G and MXPP_MR_2.5G Card Client Interface TCA Thresholds
CTC) Module (XFP) Low High Low High
FC1G 15454-SFP-GEFC-SX –17 0 –16 3

15454E-SFP-GEFC-S
ONS-SE-G2F-SX
15454-SFP-GE+-LX –20 –3 –16 3

15454E-SFP-GE+-LX
ONS-SE-G2F-LX
FC2G 15454-SFP-GEFC-SX –15 0 –16 3

15454E-SFP-GEFC-S
ONS-SE-G2F-SX
15454-SFP-GE+-LX –20 –3 –16 3

15454E-SFP-GE+-LX
ONS-SE-G2F-LX
495

15454E-SFP-GEFC-S
ONS-SE-G2F-SX
15454-SFP-GE+-LX –20 –3 –16 3

15454E-SFP-GE+-LX
ONS-SE-G2F-LX

15454E-SFP-GEFC-S
ONS-SE-G2F-SX
15454-SFP-GE+-LX –20 –3 –16 3

15454E-SFP-GE+-LX
ONS-SE-G2F-LX
ONE_GE 15454-SFP-GEFC-SX –17 0 –16 3

15454E-SFP-GEFC-S
ONS-SE-G2F-SX
15454-SFP-GE+-LX –20 –3 –16 3

15454E-SFP-GE+-LX
ONS-SE-G2F-LX
ESCON ONS-SE-200-MM –21 –14 –32 –11
Step 4 Click Apply.

Step 5 Repeat Steps 3 and 4 to provision each additional client port.
Step 7 Referring to the following table, verify the client port (Ports 1 through 8) Alarm thresholds for RX Power
High, RX Power Low, TX Power High, and TX Power Low based on the client interface that is provisioned.
Table 193: MXP_MR_2.5G and MXPP_MR_2.5G Card Client Interface Alarm Thresholds
FC1G 15454-SFP-GEFC-SX –20 3 –13 –1

15454E-SFP-GEFC-S
ONS-SE-G2F-SX
15454-SFP-GE+-LX –23 0 –13 0

15454E-SFP-GE+-LX
ONS-SE-G2F-LX
496
FC2G 15454-SFP-GEFC-SX –18 3 –13 –1

15454E-SFP-GEFC-S
ONS-SE-G2F-SX
15454-SFP-GE+-LX –23 0 –13 0

15454E-SFP-GE+-LX
ONS-SE-G2F-LX

15454E-SFP-GEFC-S
ONS-SE-G2F-SX
15454-SFP-GE+-LX –23 0 –13 0

15454E-SFP-GE+-LX
ONS-SE-G2F-LX

15454E-SFP-GEFC-S
ONS-SE-G2F-SX
15454-SFP-GE+-LX –23 0 –13 0

15454E-SFP-GE+-LX
ONS-SE-G2F-LX
ONE_GE 15454-SFP-GEFC-SX –20 3 –13 –1

15454E-SFP-GEFC-S
ONS-SE-G2F-SX
15454-SFP-GE+-LX –23 0 –13 0

15454E-SFP-GE+-LX
ONS-SE-G2F-LX
ESCON ONS-SE-200-MM –24 –11 –35 –8
Step 8 Click Apply.

NTP-G148Modifyingthe10GDataMuxponderCardLineSettings
and PM Parameter Thresholds
for the MXP_MR_10DME_C, MXP_MR_10DME_L,
and MXP_MR_10DMEX_C muxponder cards.
497

Muxponder Cards
necessary)
on page 321
Procedure
settings.
DLP-G334 Changing the 10G Data Muxponder Distance Extension Settings
DLP-G338 Provisioning the 10G Data Muxponder Trunk Port Alarm and TCA Thresholds
DLP-G339 Provisioning the 10G Data Muxponder Client Port Alarm and TCA Thresholds
DLP-G366 Changing the 10G Data Muxponder OTN Settings
498

Purpose This task changes the distance extension settings for
the MXP_MR_10DME_C, MXP_MR_10DME_L,
and MXP_MR_10DMEX_C muxponder card ports
provisioned for Fibre Channel or FICON payloads.
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_MR_10DME_C,
MXP_MR_10DME_L, or MXP_MR_10DMEX_C card where you want to change the distance extension
settings.
Step 2 Click the Provisioning > Line > Distance Extension tabs.
Note The distance extension parameters only apply to client ports (Ports 1 to 8) and not to the trunk
port (Port 9).
Note The client port must be in the OOS,DSBLD (ANSI) or Locked,disabled (ETSI) state in order to
change the distance extension settings. If a Y-cable is provisioned on the client port, both the
working and protect client ports must be in OOS,DSBLD (ANSI) or Locked,disabled (ETSI)
state before you change the distance extension settings.
Table 194: MXP_MR_10DME_C, MXP_MR_10DME_L, or MXP_MR_10DMEX_C Card Line Distance Extension Settings

Port (Display only) Port number. Up to —
eight ports might appear based on
the number of pluggable port
modules that are provisioned.
499
Enable Distance Extension Allows end-to-end distances of up Checked or unchecked

to 1600 km for FC1G and up to 800
km for FC2G. If Distance
Extension is enabled, set the
connected Fibre Channel switches
to Interop or Open Fabric mode,
depending on the Fibre Channel
switch. By default, the
MXP_MR_10DME_C and
MXP_MR_10DME_L card will
interoperate with the Cisco MDS
storage products.
Fast Switch If unchecked, the end-to-end fiber Checked or unchecked (default)

channel link is reinitialized every
time a Y-cable protection switch
occurs. If checked, reinitialization
of the link is avoided when a
Y-cable protection switch occurs,
thus reducing the traffic hit
considerably.
This feature is supported for FC1G,
FC2G, FC4G, FICON1G,
FICON2G, and FICON4G trunk
failures as well as user-initiated
Y-cable protection switch such as,
Manual, Force, or Lockout. It is
recommended that you do not
enable the Fast Switch option as the
link may not come up after a
Y-cable protection switch in certain
cases.
Note This option can be used
only if you have
unchecked Enable
Distance Extension
option.
Step 4 Click Apply.

500
DLP-G338 Provisioning the 10G Data Muxponder Trunk Port Alarm and TCA Thresholds
DLP-G338 Provisioning the 10G Data Muxponder Trunk Port

Purpose This task changes the MXP_MR_10DME_C and
MXP_MR_10DME_L trunk port alarm and TCA
thresholds.
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_MR_10DME_C
or MXP_MR_10DME_L card where you want to change the trunk port alarm and TCA settings.
Step 3 If TCA is not selected, click TCA and then click Refresh.
Step 4 Verify the trunk port (Port 9) TCA thresholds are set at the values shown as follows. Provision new
thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new
value, and press Enter.
RX Power High: –9 dBm
RX Power Low: –18 dBm
TX Power High: 9 dBm
TX Power Low: 0 dBm
Step 6 Verify the trunk port (Port 9) Alarm thresholds are set at the values shown as follows. Provision new
thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new
value, and press Enter.
RX Power High: –8 dBm
RX Power Low: –20 dBm
501
TX Power High: 7 dBm

TX Power Low: 3 dBm
Step 7 Click Apply.

DLP-G339 Provisioning the 10G Data Muxponder Client Port

thresholds for the MXP_MR_10DME_C and
MXP_MR_10DME_L cards.

page 321
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_MR_10DME_C and
MXP_MR_10DME_L card where you want to change the client port alarm and TCA settings.
Step 3 Referring to the following table, verify the client ports (Ports 1 through 8) TCA thresholds for RX Power
High, RX Power Low, TX Power High, and TX Power Low based on the client interface at the other end.
and click Refresh.
about SFPs and XFPs, see the DLP-G278 Provisioning the Optical Line Rate, on page 321.
502
Table 195: MXP_MR_10DME_C and MXP_MR_10DME_L Card Client Interfaces TCA Thresholds
PPM Port Rate Pluggable Port TCA RX Power TCA RX Power TCA TX Power TCA TX Power
Module (XFP) High Low High Low
FC1G 15454-SFP-GEFC-SX 0 –17 3 –16

15454E-SFP-GEFC-S
ONS-SE-G2F-SX
15454-SFP-GE+-LX –3 –20 3 –16

15454E-SFP-GE+-LX
ONS-SE-G2F-LX
FC2G 15454-SFP-GEFC-SX 0 –15 3 –16

15454E-SFP-GEFC-S
ONS-SE-G2F-SX
15454-SFP-GE+-LX –3 –20 3 –16

15454E-SFP-GE+-LX
ONS-SE-G2F-LX
FICON1G 15454-SFP-GEFC-SX 0 –17 3 –16

15454E-SFP-GEFC-S
ONS-SE-G2F-SX
15454-SFP-GE+-LX –3 –20 3 –16

15454E-SFP-GE+-LX
ONS-SE-G2F-LX
FICON2G 15454-SFP-GEFC-SX 0 –17 3 –16

15454E-SFP-GEFC-S
ONS-SE-G2F-SX
15454-SFP-GE+-LX –3 –20 3 –16

15454E-SFP-GE+-LX
ONS-SE-G2F-LX
ISC3 PEER 1G ONS-SE-G2F-SX 0 –17 3 –16
ISC3 PEER 2G ONS-SE-G2F-LX 0 –20 3 –16
FC4G ONS-SE-4G-MM 0 –12 4 –15
ONS-SE-4G-SM –1 –15 4 –15
FICON4G ONS-SE-4G-MM 0 –12 4 –15
ONS-SE-4G-SM –1 –15 4 –15
Step 4 Click Apply.

503
Table 196: MXP_MR_10DME_C and MXP_MR_10DME_L Card Client Interface Alarm Thresholds
PPM Port Rate Pluggable Port Alarm RX Power Alarm RX Power Alarm TX Power Alarm TX Power
Module (XFP) Low High Low High
FC1G 15454-SFP-GEFC-SX –20 3 –13 –1

15454E-SFP-GEFC-S
ONS-SE-G2F-SX
15454-SFP-GE+-LX –23 0 –13 0

15454E-SFP-GE+-LX
ONS-SE-G2F-LX
FC2G 15454-SFP-GEFC-SX –18 3 –13 –1

15454E-SFP-GEFC-S
ONS-SE-G2F-SX
15454-SFP-GE+-LX –23 0 –13 0

15454E-SFP-GE+-LX
ONS-SE-G2F-LX

15454E-SFP-GEFC-S
ONS-SE-G2F-SX
15454-SFP-GE+-LX –23 0 –13 0

15454E-SFP-GE+-LX
ONS-SE-G2F-LX

15454E-SFP-GEFC-S
ONS-SE-G2F-SX
15454-SFP-GE+-LX –23 0 –13 0

15454E-SFP-GE+-LX
ONS-SE-G2F-LX
ISC3 PEER 1G ONS-SE-G2F-SX –20 3 –13 –1
ISC3 PEER 2G ONS-SE-G2F-LX –23 0 –13 0
FC4G ONS-SE-4G-MM –15 3 –11 –1
ONS-SE-4G-SM –18 2 –11 0
FICON4G ONS-SE-4G-MM –15 3 –11 –1
ONS-SE-4G-SM –18 2 –11 0
504
Step 8 Click Apply.


cards.
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_MR_10DME_C
and MXP_MR_10DME_L card where you want to change the OTN settings.
Note You must modify Near End and Far End; 15 Min and 1 Day; and SM and PM independently.
Table 197: MXP_MR_10DME_C and MXP_MR_10DME_L Card OTN Line Settings

number.
G.709 OTN Sets the OTN lines according to • Enable

ITU-T G.709.
• Disable
FEC Sets the OTN lines to forward error • Standard

correction (FEC).
• Enhanced

bit error rate.
505

SD BER Sets the signal degrade bit error 1E-5
rate.
1E-6
1E-7
1E-8
1E-9
Asynch/Synch Mapping Sets how the ODUk (client Asynch mapping

Synch mapping
channel (OTUk).
Table 198: MXP_MR_10DME_C and MXP_MR_10DME_L Card ITU-T G.709 Threshold Settings
Port (Display only) Port number. 9 (Trunk)



506
Latency for a 1G-FC payload without ITU-T G.709 is 4 microseconds, and with ITU-T G.709 is
40 microseconds. Latency for a 2G-FC payload without ITU-T G.709 is 2 microseconds, and with ITU-T
G.709 is 20 microseconds. Consider these values when planning a FC network that is sensitive to latency.
Table 199: MXP_MR_10DME_C and MXP_MR_10DME_L Card FEC Threshold Settings

Bit Errors Corrected Sets the value for bit errors Numeric. Can be set for 15-
corrected. minute or one-day intervals.
words. minute or one-day intervals.
Table 200: MXP_MR_10DME_C and MXP_MR_10DME_L Card Trail Trace Identifier Settings

• Path

• Manual
to Hex).

mismatch, no Forward Defect Unchecked (FDI on TTIM is
is checked.
507
NTP-G293 Modifying the 40G Muxponder Card Line Settings and PM Parameter Thresholds

changes to Hex).
panel updated.
Step 4 Click Apply.

NTP-G293 Modifying the 40G Muxponder Card

Line Settings and PM Parameter Thresholds
Purpose This procedure changes the line and parameter
threshold settings of the 40G-MXP-C, 40E-MXP-C,
and 40ME-MXP-C muxponder cards.

Muxponder Cards
necessary)
on page 321
508
DLP-G662 Changing the 40G Multirate Muxponder Card Settings
Procedure
Step 1 Complete the NTP-G103 Backing Up the Database task to save the existing settings before modifying.
DLP-G666 Changing the 40G Muxponder Line Settings
DLP-G735 Provisioning the 40G Muxponder Ethernet Settings
DLP-G667 Changing the 40G Muxponder SONET (OC-192)/SDH (STM-64) Settings
DLP-G668 Changing the 40G Muxponder Section Trace Settings
DLP-G669 Changing the 40G Muxponder SONET or SDH Line Thresholds
DLP-G670 Changing the 40G Muxponder Line RMON Thresholds for Ethernet, 8G FC, or 10G FC
Payloads
DLP-G671 Provisioning the 40G Muxponder Trunk Port Alarm and TCA Thresholds
DLP-G672 Provisioning the 40G Muxponder Client Port Alarm and TCA Thresholds
DLP-G673 Changing the 40G Muxponder OTN Settings

Purpose This task changes the card settings of the
509
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 40G-MXP-C, or 40E-
MXP-C card where you want to change the card settings.
Step 3 Modify either of the settings described in the following table.
Table 201: 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Card Settings
Card Mode Sets the card mode. • Muxponder • Muxponder

• Unidirectional Regen • Unidirectional Regen
Set the mode to Set the mode to
Unidirectional Regen Unidirectional Regen
under the following under the following
conditions: conditions:
• Trunk port is in • Trunk port is in
OOS,DSBLD locked,disabled
state. state.
• Pluggable port • Pluggable port
modules of the modules of the
card must not card must not
be configured be configured
for payload. for payload.
• Regeneration • Regeneration
peer slot must peer slot must
be set to None. be set to None.
510

Timing Source Sets the clock selection. — —
The line card sets the
clock switch based on the
provisioning of the card.
The clock can be set in
two ways: Internal Clock
and TNC Clock.
Internal Clock: This is
the default value for
normal operations; to
avoid the traffic hits
in case of missing
TNC.
TNC Clock: This is
the default value to
avoid traffic hit
during maintenance
activities like
software download.
After the
maintenance
activity is complete,
the clock must be
set to use the
internal clock.
Note A warning
message is
displayed
when the
provisioning is
set because
this activity
affects traffic.
Trunk Wavelengths (Display only) Shows — —

supported wavelengths of
the trunk port after the
card is installed. The
40G-MXP-C,
40E-MXP-C, and
40ME-MXP-C card that
is installed shows the
C-band wavelengths that
it supports.
Step 4 Click Apply.
511

Purpose This task changes the line settings of the 40G-MXP-C,
40E-MXP-C, and 40ME-MXP-C muxponder cards.
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 40G-MXP-C or 40E-
MXP-C card where you want to change the line settings.
Step 2 Click the Provisioning > Line > Ports tabs. Tabs and parameters vary according to the PPM provisioning.
Table 202: Line Settings of the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards

Port (Display only) Displays the port 1 through 4 (client)
number.
5 (trunk)
Port Name Assigns a logical name for each of User-defined. This can be up to
the port. 80 alphanumeric or special
characters, or both. The port name
is blank by default.
Note You can assign a port
name for each fiber
channel/FICON
interface on the 40G-
MXP-C, 40E-MXP-C,
and 40ME-MXP-C
card, enabling the MDS
Fabric Manager to
associate the SAN port
and a SAN port on the
512

OOS,DSBLD (ANSI) or
change. For more information, see
the Administrative and Service Locked,disabled (ETSI)
States document. OOS,MT (ANSI) or
IS,AINS (ANSI) or
(ETSI)
Service State (Display only) Shows the general IS-NR (ANSI) or Unlocked-
condition of the port. Service states enabled (ETSI)
appear in the format: Primary
State-Primary State Qualifier,
Unlocked-disabled,
Secondary State. For more
information about service states, automaticInService (ETSI)
see the Administrative and Service OOS-MA,DSBLD (ANSI) or
States document. Locked-enabled,disabled
(ETSI)
OOS-MA,MT (ANSI) or
Locked-
513

ALS Mode (Client ports only) Activates the Disabled (default)—ALS is
ALS mode. off; the laser is not
Auto Restart—(OC-
192/STM-64 only) ALS is
on; the laser automatically
shuts down during LOS. It

resolved.
for testing.
AINS Soak Sets the automatic in-service soak Duration of valid input signal, in
period. Double-click the time and hh.mm format, after which the
use the up and down arrows to the card status changes to in
change settings. service (IS) automatically
increments
514
Reach Sets the optical reach distance of • Autoprovision—The system

the client port. automatically provisions the
module (PPM) reach value on
the hardware.
• EW
• LW
• SW
• LRM
• ER
• LR
• SR
• ZR
• IR 2
• LR 2
• DWDM
• CWDM40km
Wavelength Provisions the port wavelength. • First Tunable Wavelength

• Further wavelengths: Further
wavelengths in the 100-GHz
card wavelengths are marked
by asterisks. If the card is not
background.
515
Fault Signalling Shuts down the far-end laser in • Squelch/Laser-Off

Note Squelch does not
apply to ISC
COMPACT
payloads.
• Disable/Transparent
Note Both
Squelch/Laser-Off
and AIS/Send Local
Fault options are
supported when the
selected Termination
Mode is
Disable/Transparent.
If the Termination
Mode selected is
Section or Line, then
only AIS is
supported. This is
applicable for
OC-192/STM-64
and
OC-768/STM-256.
For OTN payloads,
both
Squelch/Laser-Off
and AIS/Send Local
Fault options are
supported.
Overclock (Trunk port only) Enables or OFF (default)

disables overclock mode on the
ON
trunk port.
NoteBefore the overclock is
changed, delete
any existing 10G
Ethernet LAN-Phy
payload that is
present on the
40E-MXP-C
and 40ME-
MXP-C cards.
516

Rx Wavelength (Trunk port only) Provisions the First Tunable Wavelength
trunk port wavelength.
Further wavelengths: Further
wavelengths in the 100-GHz
card wavelengths are marked
by asterisks. If the card is
not installed, all wavelengths
background.
Squelch Hold Off Timer (Only for 40E-MXP-C card) Sets Disable (0 ms) - Default value
the period in milliseconds that the
50 ms
client interface waits for resolution
of issues on the trunk side. The 100 ms
client squelching starts after this
period. 250 ms
The user can configure the squelch 500 ms
hold off timer in CTC only under
the following conditions:
• The card must be configured
in TXP or MXP operating
modes.
• The client payload must be
10GE or 100GE.
• The Squelch drop-down in
CTC must be set to Squelch.
Step 4 Click Apply.


Purpose This task changes the Ethernet settings for the
517
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 40G Muxponder card
(40G-MXP-C, 40E-MXP-C, or 40ME-MXP-C card) where you want to change the Ethernet settings.
The card view appears.
Step 2 Click the Provisioning > Line > Ethernet tabs. The Ethernet tab is available once the 10G Ethernet LAN
Phy payload is selected as the port rate for the pluggable port module.
Step 3 Modify any of the settings for the Ethernet tab as described in the following table.
Table 203: 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Card Ethernet Settings

Port (Display only) The Port number —
(n-n) and rate.
Port Name Allows you to enter a port name. —
MTU (Display only) The maximum size Jumbo: 64 to 9216 bytes (Default)
of the Ethernet frames accepted by
the port.
Mapping Mode Sets the Ethernet mapping mode. • GFP

• WIS
• CBR (only for 40E-MXP-C
and 40ME-MXP-C)
Note CBR is automatically
mapped when a
payload is configured
with overclock on the
trunk port turned ON.
This mapping cannot
be changed.
Enable Flow Control Activates flow control when the —

check box is selected.
Step 4 Click Apply.

518
DLP-G667 Changing the 40G Muxponder SONET (OC-192)/SDH (STM-64) Settings
DLP-G667Changingthe40GMuxponderSONET(OC-192)/SDH(STM-64)Settings
Purpose This task changes the SONET OC-192 or SDH
STM-64 settings for the 40G-MXP-C, 40E-MXP-C,
and 40ME-MXP-C muxponder cards.
Procedure
MXP-C card where you want to change the SONET (OC-192) or SDH (STM-64) settings.
Step 2 Click the Provisioning > Line > SONET (ANSI) or SDH (ETSI). Tabs and parameters vary according
to the PPM provisioning.
Table 204: Line SONET or SDH Settings of the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards

number.
Port Name Assigns a logical name assigned to User-defined. This can be up to

a port. This field is blank by 80 alphanumeric or special
default. characters, or both. The port name
is blank by default.
SF BER Sets the signal fail bit error rate. • 1E-3

• 1E-4
• 1E-5

rate.
• 1E-6
• 1E-7
• 1E-8
• 1E-9
519
ProvidesSync (Display only) Displays the Checked or unchecked

ProvidesSync card parameter state.

timing source.
Send DoNotUse Sets the Send DoNotUse card state. Checked or unchecked
When checked, sends a DUS (do
not use) message on the S1 byte.
Type Indicates the optical transport SONET (ANSI)
type.
SDH (ETSI)
Transparent
Termination Mode (Display-only for Standard
Section (ANSI) or
Regeneration and Enhanced FEC
card configurations) Sets the mode Regeneration Section (RS)
of operation. (ETSI)
Line (ANSI) or Multiplex
Section (MS) (ETSI)
Step 4 Click Apply.


Purpose This task changes the section trace settings of the
40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C
muxponder cards.
520
Procedure
MXP-C card where you want to change the section trace settings.
the PPM provisioning.
Table 205: Line Section Trace Settings of the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards

Port (Display only) Displays the port • 1-1
number that is applicable only for
• 2-1
OC-192/STM-64 payloads.
• 3-1
• 4-1

• Manual
Disable AIS/RDI on TIM-S Disables the alarm indication • Checked (AIS/RDI on TIM-S
signal. is disabled)
• Unchecked (AIS/RDI on
TIM-S is not disabled)
• 16 byte
Transmit Displays and sets the current Transmit string size

transmit string. You can click the
button on the right to change the
display. Its title changes, based on
the current display mode. In
Transmit String Type, click
Hex Mode to change the display to
to Hex Mode). The supported range
for 1 bit Hex TX trace is 20 to 7E.
If TX trace is provisioned outside
this range, client transmits 00.
521
DLP-G691 Changing the 40G Muxponder OTU Settings
Expected Displays and sets the current Expected string size

expected string. You can click the
Expected String Type, click
to Hex Mode). The supported range
for 1 bit Hex TX trace is 20 to 7E.
If TX trace is provisioned outside
this range, client transmits 00.
Received (Display only) Displays the current Received string size

received string. Click Refresh to
updated.
Auto-refresh Automatically refreshes the display • Checked

every 5 seconds.
• Unchecked (default)
Step 4 Click Apply.


Purpose This task changes the OTU settings of the
muxponder cards.
522
Procedure
MXP-C card where you want to change the OTU settings.
Step 2 Click the Provisioning > Line > OTU tabs. Tabs and parameter selections vary according to the
PPM provisioning.
Table 206: OTU Settings of the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards

ETSI Options
Port (Display only) Displays • 1-1 1-1
the port number that is
applicable only for • 2-1 2-1
OC-192/STM-64 • 3-1 3-1
payloads.
• 4-1 • 4-1
SyncMsgIn (Display only) Checked or unchecked Checked or unchecked

parameter. Enables
Admin SSM Overrides the • PRS—Primary • G811—Primary

synchronization
equipment
• ST4—Stratum 4
level set by user
523
ProvidesSync (Display only) Checked or unchecked Checked or unchecked

card parameter. If
element (NE) timing
reference.
Step 4 Click Apply.


Purpose This task changes the SONET or SDH line threshold
settings of the 40G-MXP-C, 40E-MXP-C, and
40ME-MXP-C muxponder cards.
Procedure
MXP-C card where you want to change the line threshold settings.
Step 3 Modify any of the settings shown in the following table. Some parameters and options do not apply to all
40-G-MXP-C cards. If the parameter or options do not apply, they do not appear in CTC.
Table 207: Line Threshold Settings of the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards
Port (Display only) Port • 1-1 • 1-1

number. Applicable for
only OC-192/STM-64 • 2-1 • 2-1
payloads. • 3-1 • 3-1
• 4-1 • 4-1
524

or Far End
(minutes) or 1 day
• Types—Line or
Section (near end
only)
Choose an option
individually in each
category and click
Refresh.

(near end only)
Choose an option
individually in each Choose an option
category and click individually in each
Refresh. category and click
Refresh.
525

(near end only)
Choose an option
restore default values. Click Reset to Default to

or Far End
(minutes) or 1 day
• Types—Line or
Section (near end
only)
Choose an option
individually in each
category and click
Refresh.
Click Reset to Default to
526
DLP-G670 Changing the 40G Muxponder Line RMON Thresholds for Ethernet, 8G FC, or 10G FC Payloads

(near end only)
Choose an option
restore default values. Click Reset to Default to
Step 4 Click Apply.

DLP-G670 Changing the 40G Muxponder Line RMON Thresholds

for Ethernet, 8G FC, or 10G FC Payloads
Purpose This task changes the line threshold settings of
40G-MXP-C, or 40E-MXP-C card carrying Ethernet,
8G FC, or 10G FC payloads.
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), display the 40G-MXP-C, or 40E-MXP-C
card where you want to change the line threshold settings in the card view.
527
Step 4 From the Port drop-down list, choose the payload port— for example “1-1 (TEN_GE)”, or the
equivalent ITU-T G.7041 GFP (Generic Frame Procedure) port.
Step 5 From the Variable drop-down list, choose an Ethernet or FC variable.
Table 208: Ethernet Variables of the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards
ifInUcastPkts Number of packets, delivered by this sub-layer to a

higher sub-layer, which were not addressed to a
multicast or broadcast address at this sub-layer.
inInMulticastPkts Number of packets, delivered by this sub-layer to a

higher sub-layer, which were addressed to a multicast
address at this sub-layer. For a MAC layer protocol,
this includes both Group and Functional addresses.
ifInBroadcastPkts Number of packets, delivered by this sub-layer to a

higher sub-layer, which were addressed to a broadcast
address at this sub-layer.
ifInErrors Total number of received errors.

dot3StatsFCSErrors Count of frames received on a particular interface that

are an integral number of octets in length but do not
pass the Frame Check Sequence (FCS) check.
dot3StatsFrameTooLong Count of frames received on a particular interface that

exceed the maximum permitted frame size.
dot3StatsInPauseFrames Count of frames received on this interface with an

opcode indicating the PAUSE operation.
dot3StatsOutPauseFrames Count of MAC control frames transmitted on this

operation.
etherStatsUndersizePkts Total number of packets transmitted and received by

the interface that were less than 64 octets long
and were otherwise well formed.
528

including FCS octets) and had either a bad Frame
Check Sequence (FCS) with an integral number of
octets (FCS Error) or a bad FCS with a non-integral
number of octets.
etherStatsPkts Total number of packets (including bad packets,

broadcast packets, and multicast packets) transmitted
and received by the interface.

transmitted and received by the interface that were 64
octets in length (excluding framing bits but including
FCS octets).
etherStatsPkts65to127Octets Total number of packets (including error packets)

between 65 and 127 octets in length inclusive
(excluding framing bits but including FCS octets).




etherStatsBroadcastPkts Total number of good packets transmitted and

received by the interface that were directed to the
broadcast address.
etherStatsMulticastPkts Total number of good packets transmitted and

received by the interface that were directed to a
multicast address. Note that this number does not
include packets directed to the broadcast address.
529
etherStatsOversizePkts Total number of packets transmitted and received by

the interface that were longer than 1518 octets
and were otherwise well formed.
etherStatsJabbers Total number of packets transmitted and received by

the interface that were longer than 1518 octets
(excluding framing bits, but including FCS octets),
and were not an integral number of octets in length
or had a bad FCS.
etherStatsOctets Total number of octets of data (including those in bad

packets) transmitted and received by the interface on
the network (excluding framing bits but including
FCS octets).
Table 209: FC Variables of the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards

ifOutErrors Number of outbound packets or transmission units

that could not be transmitted because of errors.

statistics.



mediaIndStatsTxFramesTooLong Total number of transmitted data frames that are less

than 5 bytes. This value is a part of HDLC and GFP
port statistics.
530
mediaIndStatsTxFramesTruncated Number of transmitted data frames that exceed the

MTU. This value is part of HDLC and GFP port
statistics.
Table 210: GFP RMON Variables of the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards
gfpStatsRxFrame Total number of received data frames.
gfpStatsTxFrame Total number of transmitted data frames.

frame has multiple superblocks where each contains
Fibre Channel data.
gfpStatsRxOctets Total number of GFP data octets received.
gfpStatsTxOctets Total number of GFP data octets transmitted.
gfpStatsRxSBitErrors Received GFP frames with single bit errors in the core
header (these errors can be corrected).
gfpStatsRxMBitErrors Received GFP frames with multiple bit errors in the

core header (these errors cannot be corrected).

data.
gfpStatsLFDRaised Count of core HEC CRC multiple bit errors.

Note This count is only of eHec multiple bit
errors when in frame. This can be looked
at as a count of when the state machine
goes out of frame.
gfpRxCmfFrame —
gfpTxCmfFrame —
Step 6 From the Alarm Type drop-down list, choose an alarm type. The alarm type indicates whether or not an event
is triggered by the type of threshold.
Step 8 Enter the number of Sample Period occurrences.
Step 9 Enter the number of Rising Threshold occurrences.
531
DLP-G671 Provisioning the 40G Muxponder Trunk Port Alarm and TCA Thresholds
To trigger the alarm, the measured value of a threshold must always move from below the falling threshold
to above the rising threshold. For example, if a network moves from below a rising threshold of 1000 collisions
every 15 seconds to 1001 collisions.
Step 10 Enter the appropriate number of occurrences for the Falling Threshold field. In most cases a falling threshold
A falling threshold is the exact opposite of a rising threshold. When the number of occurrences is above the
rising threshold and then drops below a falling threshold, it resets the rising threshold. For example, when the
network problem that caused 1001 collisions in 15 seconds subsides and creates only 799 collisions in 15
seconds, occurrences fall below a falling threshold of 800 collisions. This resets the rising threshold so that
if network collisions again spike over a 1000 per 15-second period, an event again triggers when the rising
threshold is crossed. An event is triggered only the first time a rising threshold is exceeded.
Step 11 Click OK.

DLP-G671 Provisioning the 40G Muxponder Trunk Port

Purpose This task changes the trunk port alarm and TCA
thresholds of the 40G-MXP-C, 40E-MXP-C, and
40ME-MXP-C cards.
Procedure
MXP-C card where you want to change the trunk port alarm and TCA settings.
Note You must modify 15 Min and 1 Day independently. To do so, select the appropriate radio
Step 3 If TCA is not selected, click TCA and then click Refresh. If it is selected, continue with Step 4.
Step 4 Verify the trunk port (Port 5) TCA thresholds are set at the values shown as follows:
532
Laser Bias High (%): 95.0

RX Power High (dBm): –9.0
RX Power Low (dBm): –22.0
TX Power High (dBm): 9.0
TX Power Low (dBm): 0.0
Provision new thresholds as needed by replacing the old values with new ones.
Step 6 Verify the trunk port (Port 5) alarm thresholds are set at the values shown as follows:
Laser Bias High (%): 98.0
RX Power High (dBm): –8.0
RX Power Low (dBm): –24.0
TX Power High (dBm): 7.0
TX Power Low (dBm): 3.0
Provision new thresholds as needed replacing the old values with new ones.
Step 7 Click Apply.

DLP-G672 Provisioning the 40G Muxponder Client Port

thresholds of the 40G-MXP-C, 40E-MXP-C, and
40ME-MXP-C cards.

on page 321
533
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 40G-MXP-C, or 40E-MXP-C
card where you want to change the client port alarm and TCA settings.
Step 3 If TCA is not selected, click TCA and then click Refresh. If it is selected, continue with Step 4.
Step 4 Referring to the following table, verify the client ports (Ports 1 through 4) TCA thresholds for RX Power
Provision new thresholds as needed by replacing the old values with new ones.
Note You must modify 15 Min and 1 Day independently. To do so, select the appropriate radio button
and click Refresh.
Table 211: Client Interfaces TCA Thresholds of the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards
FC8G ONS-XC-8G-FC-SM –9 –22 9.0 0.0
FC10G ONS-XC-10G-1470 –9 –22 9.0 0.0

through
ONS-XC-10G-1610
ONS-XC-10G-C
ONS-XC-10G-S1
ONS-XC-10G-I2 2.0 –15.8 8.0 –7.0
ONS-XC-10G-L2 1.0 –14.0 5.0 –12.0
ONS-XC-10G-SR-MM 0.0 0.0 6.0 –6.0
10GE ONS-XC-10G-30.3 –9 –22 9.0 0.0

through
ONS-XC-10G-61.4
ONS-XC-10G-C
ONS-XC-10G-SR-M
ONS-XC-10G-S1
ONS-XC-10G-I2 2.0 –15.8 8.0 –7.0
ONS-XC-10G-L2 –7.0 –24.0 6.5 –2.5
534
OC-192 ONS-XC-10G-30.3 –9 –22 9.0 0.0

through
ONS-XC-10G-61.4
ONS-XC-10G-C
ONS-XC-10G-1470
through
ONS-XC-10G-1610
ONS-XC-10G-I2
ONS-XC-10G-SR-MM
ONS-XC-10G-L2 –9.0 –26.0 8.0 –8.0
ONS-XC-10G-S1 –1.0 –11.0 5.0 –12.0
OTU2 ONS-XC-10G-30.3 –9 –22 9.0 0.0

through
ONS-XC-10G-61.4
ONS-XC-10G-C
ONS-XC-10G-1470
through
ONS-XC-10G-1610
ONS-XC-10G-I2
ONS-XC-10G-L2
ONS-XC-10G-SR-MM
ONS-XC-10G-S1
Step 5 Click Apply.

Step 6 Repeat Steps 3 and 4 to provision the additional client ports.
Provision new thresholds as needed replacing the old values with new ones.
Table 212: Client Interface Alarm Thresholds of the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards
FC8G ONS-XC-8G-FC-SM –9 –22 9.0 0.0

ONS-XC-10G-S1
535
FC10G ONS-XC-10G-30.3 –9 –22 9.0 0.0

through
ONS-XC-10G-61.4
ONS-XC-10G-C
ONS-XC-10G-1470
through
ONS-XC-10G-1610
ONS-XC-10G-S1
ONS-XC-10G-I2 4.5 –18.3 4.5 –3.5
ONS-XC-10G-L2 –4.5 –26.5 6.5 –2.5
ONS-XC-10G-SR-MM 2.0 –2.0 2.0 –2.0
10GE ONS-XC-10G-30.3 –9 –22 9.0 0.0

through
ONS-XC-10G-61.4
ONS-XC-10G-C
ONS-XC-10G-S1
ONS-XC-10G-SR-MM
ONS-XC-10G-I2 4.5 –18.3 4.5 –3.5
ONS-XC-10G-L2 –4.5 –26.5 6.5 –2.5
OC-192 ONS-XC-10G-30.3 –9 –22 9.0 0.0

through
ONS-XC-10G-61.4
ONS-XC-10G-C
ONS-XC-10G-1470
through
ONS-XC-10G-1610
ONS-XC-10G-I2
ONS-XC-8G-FC-SM
ONS-XC-10G-SR-MM
ONS-XC-10G-L2 –7.0 –28.0 4.0 –4.0
ONS-XC-10G-S1 –1.0 –13.0 1.0 –8.0
536
OTU2 ONS-XC-10G-30.3 –9 –22 9.0 0.0

through
ONS-XC-10G-61.4
ONS-XC-10G-C
ONS-XC-10G-1470
through
ONS-XC-10G-1610
ONS-XC-10G-S1
ONS-XC-10G-I2
ONS-XC-10G-L2
ONS-XC-8G-FC-SM
ONS-XC-10G-SR-MM
Step 9 Click Apply.

Step 10 Repeat Steps 7 and 8 to provision additional client ports.

Procedure
MXP-C card where you want to change the OTN settings.
Step 2 Click the Provisioning > OTN tabs, then choose one of the following subtabs: OTN Lines, ITU-T G.709
Note You must modify Near End and Far End, 15 Min and 1 Day, and SM and PM independently.
To do so, select the appropriate radio button and click Refresh.
537
Table 213: OTN Line Settings of the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards

Port (Display only) Displays the port 1-1
number.
2-1
Applicable for trunk ports and ports
with OTU2 payload. 3-1
4-1
5 (Trunk)
ITU-T G.709 Thresholds Sets the OTN lines according to • Enable

ITU-T G.709.
• Disable

correction (FEC).
• Enhanced

bit error rate.

rate.
• 1E-6
• 1E-7
• 1E-8
• 1E-9
Table 214: ITU-T G.709 Threshold Settings of the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards

number.
2-1
4-1
5 (Trunk)
538

(OTUk) or PM (ODUk). Select the
radio button individually and click
Refresh.
Click Reset to Default to restore
default values.
Refresh.

Refresh.
Refresh.

(OTUk) or PM (ODUk). Select
Refresh.
Table 215: FEC Threshold Settings of the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards

number.
2-1
4-1
5 (Trunk)
539

Table 216: Trail Trace Identifier Settings of the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards

number.
2-1
4-1
5 (Trunk)

• Manual
Disable AIS/RDI on TIM-S Disables alarm indication signal. • Checked (AIS/RDI on TIM-S
is disabled)
• Unchecked (AIS/RDI on
TIM-S is not disabled)
• 16 byte
Transmit Displays and sets the current Transmit string size

transmit string. You can click the
Transmit String Type, click
to Hex Mode).
540
NTP-G281 Managing the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Channel Group Settings
Expected Displays and sets the current Expected string size

expected string. You can click the
Expected String Type, click
to Hex Mode).
Received (Display only) Displays the current Received string size

updated.
Auto-refresh Refreshes the display automatically • Checked

every 5 seconds.
Step 4 Click Apply.

NTP-G281 Managing the GE_XP, 10GE_XP, GE_XPE,

and 10GE_XPE Card Channel Group Settings
Purpose This procedure changes the channel group settings
for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE
cards.

Muxponder Cards
• DLP-G379 Changing the GE_XP, 10GE_XP,
GE_XPE, and 10GE_XPE Card Mode, on page
315
necessary)
541
DLP-G611 Creating a Channel Group Using CTC
Procedure
Perform any of the following tasks as needed:

DLP-G612 Modifying the Parameters of the Channel Group Using CTC
DLP-G613 Managing Ports in a Channel Group, on page 548
DLP-G614 Deleting a Channel Group, on page 549
DLP-G615 Retrieving Information on Channel Group, REP, CFM, and EFM, on page 550
DLP-G616 Viewing PM Parameters of a Channel Group, on page 551
DLP-G617 Viewing Utilization PM Parameters of a Channel Group, on page 551
DLP-G618 Viewing History PM Parameters of a Channel Group, on page 552
DLP-G619 Create a Channel Group on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards Using
PCLI
DLP-G620 Add Ports to a Channel Group on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards
Using PCLI

Purpose This task creates a channel group on the GE_XP,
542
Note You can create up to 11 channel groups on the GE_XP and GE_XPE cards and up to 2 channel groups on
the 10GE_XP and 10GE_XPE cards. You can create a channel group with ports only when the ports do not
have
any UNI QinQ settings or NNI SVLAN settings. Otherwise, the channel group will be created with empty
ports.
For information about interaction of LACP with other protocols, see the Protocol Compatibility list, on page
179.
Procedure
Step 1 Verify that the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card is installed according to the requirements
specified in Cable Connections for Y-Cable Protection of One Client Signal table.
Step 2 Verify that the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card is installed in L2-over-DWDM mode. See
the DLP-G379 Changing the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode, on page 315.
Step 3 In card view, click the Provisioning > Channel Groups tabs.
Step 4 Click Create. The Channel Group Creation dialog box appears.
Step 5 Enter the name of the channel group in the Name field.
Step 6 From the Stand Alone list, choose the ports that will belong to this channel group and click the right arrow
button to move the selected ports to the Bundled list.
Step 7 From the LACP Mode drop-down list, choose the LACP mode as needed:
On—Default mode. In this mode, the ports will not exchange LACP packets with the partner ports.
Active—In this mode, the ports will send LACP packets at regular intervals to the partner ports.
Passive—In this mode, the ports will not send LACP packets until the partner ports send LACP packets.
After receiving the LACP packets from the partner ports, the ports will send LACP packets.
Step 8 From the LACP Hashing drop-down list, select the LACP hashing algorithm that the protocol uses to perform
the load balancing task between the bundled ports.
The following hashing algorithms are supported:
• Ucast SA VLAN Incoming Port
• Ucast DA VLAN Incoming Port
• Ucast SA DA VLAN Incoming port
• Ucast Src IP TCP UDP
• Ucast Dst IP TCP UDP
• Ucast Src Dst IP TCP UDP

A new row is added in the LACP table and all the other parameters in the channel group are set to default
values. The default values of these parameters are taken from the first port that is attached to the channel
group.
543

Purpose This task modifies the parameters of the channel
group.
Note Ports cannot be added or removed using this procedure. For adding or removing the ports, see the DLP-
G613 Managing Ports in a Channel Group, on page 548.
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the GE_XP, 10GE_XP,
GE_XPE, or 10GE_XPE card where you want to modify the parameters of the channel group.
Step 3 Choose a channel group from the existing channel groups.
Step 4 Modify the channel group settings as described in the following table.
Table 217: Channel Group Settings

Channel Group (Display only) ID and name of the N.A.
channel group.
Name Sets the name of the channel group. —
Ports (Display only) Port number (n-n) N.A.

and rate (GE or TEN_GE of the
channel group).
LACP Mode Sets the LACP mode. The channel On

group must be in OOS-DSBLD
Active
admin state.
Passive
544
Hashing Sets the LACP hashing algorithm. • Ucast SA VLAN Incoming

The channel group must be in Port
OOS-DSBLD admin state.
• Ucast DA VLAN Incoming
Port
• Ucast SA DA VLAN
Incoming port
• Ucast Src IP TCP UDP
• Ucast Dst IP TCP UDP
• Ucast Src Dst IP TCP UDP
Admin State Sets the administrative state on the IS

channel group.
OOS, DSBLD
Service State (Display only) Sets the service state IS-NR

that indicates the operational state
OOS-MA, DSBLD
of the channel group.
MTU Sets the maximum transfer unit Numeric. Default: 9700

(MTU), which sets the maximum Range: 64 to 9700
number of bytes per frame accepted
on the port. The member ports must
be in OOS-DSBLD admin state.
The default MTU value in the
channel group is taken from the
default settings in the node.
Mode Sets the provisional port mode. If Auto

the port mode is Auto, the Expected
1000 Mbps
Speed field determines which ports
can belong to the bundle. The
member ports must be in
Expected Speed Sets the expected speed of ports of 10 Mbps

the channel group. The channel
group must be in OOS-DSBLD 100 Mbps
admin state. 1000 Mbps
Duplex (Display only) Expected duplex Full

capability of ports of the channel
group.
545

Committed Info Rate Sets the guaranteed information Numeric. Default: 100%
rate based on the service-level Range: 0 to 100%
agreement of the service provider.
The channel group must be in Granularity: 0.1%
Committed Burst Size Sets the maximum number of bits 4k (default)

transferred per second. The channel
8k
group must be in OOS-DSBLD
admin state. 16k
32k
64k
128k
256k
512k
1M
2M
4M
8M
16M
Excess Burst Size Sets the maximum number of bits 4k (default)

credited for later transfer if the
8k
committed burst rate cannot be
transmitted. The channel group 16k
must be in OOS-DSBLD admin
state. 32k
64k
128k
256k
512k
1M
2M
4M
8M
16M
546

NIM Sets the network interface mode UNI Mode
(NIM) for the channel group. The (Default)—provisions the port
member ports must be in as a User-Network Interface
OOS-DSBLD admin state. (UNI). This is the interface
The channel group NIM is set to that faces the subscriber.
UNI or NNI based on the mode of NNI Mode—provisions the port
the first port that is added to the as a Network-to-Network
channel group. Interface (NNI). This is the
interface that faces the service
provider network.
Ingress CoS Provisions the IEEE 802.1p ingress 0

class of service (CoS). Ingress CoS
1
is used to set the priority of the
Ethernet frame in the service 2
provider network. The member
ports must be in OOS-DSBLD 3
admin state. 4
5
6
7
Trust
CVLAN
DSCP
Inner Ethertype (Hex) Defines the inner Ethertype field. Numeric.

The Ethertype field indicates which
Default: 8100 (IEEE Std 802.1Q
protocol is being transported in an
Ethernet frame. The member ports
customer VLAN tag type)
must be in OOS-DSBLD admin Range: 0x600 to 0xffff.
state to modify the Inner Ethertype
value to a non-default value.
Outer Ethertype (Hex) Defines the outer Ethertype field. Numeric.

The Ethertype field identifies which Default: 8100 (IEEE standard
protocol is being transported in an 802.1Q service provider VLAN tag
Ethernet frame. The member ports type)
must be in OOS-DSBLD admin
state. Range: 0x600 to 0xffff
547
DLP-G613 Managing Ports in a Channel Group

MAC Learning Enables or disables MAC learning Checked—MAC learning is
for the port on GE_XP, 10GE_XP, enabled for this port.
GE_XPE, and 10GE_XPE cards.
Unchecked—(Default) MAC
MAC learning is used by Layer 2
learning is disabled for this
switches to learn the MAC
addresses of network nodes so that port.
the Layer 2 switches send traffic to
the right location. In GE_XPE or
10GE_XPE cards, enable MAC
address learning per SVLAN.
Note When you set the Committed Info Rate above 40% on 10GE_XP and 10GE_XPE cards, the
Committed Burst Size and Excess Burst Size must be set to at least 32K. The Committed Burst Size
and Excess Burst Size can be increased based on the packet size and Committed Info Rate value.
Step 5 Click Apply.

DLP-G613 Managing Ports in a Channel Group

Purpose This task adds or removes ports to or from an existing
channel group.
Note • You can assign up to eight ports to a channel group on GE_XP and GE_XPE cards and up to three
ports on the 10GE_XP and 10GE_XPE cards.
You can assign the ports to a channel group only if the ports are in OOS-DSBLD admin state. The ports
must not have any UNI QinQ rule or NNI SVLAN configuration.
If the channel group is configured in UNI mode, only the UNI ports can be added to the channel group. If the
channel group is configured in NNI mode, only the NNI ports can be added to the channel group.
548
DLP-G614 Deleting a Channel Group
Procedure
10GE_XP, GE_XPE, or 10GE_XPE card where you want to add ports to an existing channel group.
Step 3 Choose a channel group from the existing channel groups.
Step 4 Click Add/Remove Ports.
Step 5 To add ports to an existing channel group, from the Stand Alone list, choose the required ports and click the
right arrow button to move the selected ports to the Bundled list.
Step 6 To remove ports from an existing channel group, complete the following: from the Bundled list, choose the
required ports and click the left arrow button to move the selected ports to the Stand Alone list.
Step 7 Click Apply.
DLP-G614 Deleting a Channel Group

Purpose This task deletes a channel group.
Procedure
10GE_XP, GE_XPE, or 10GE_XP card where you want to delete the channel group.
Step 3 Choose a channel group that you want to delete.
Step 4 Click Delete.
549
DLP-G615 Retrieving Information on Channel Group, REP, CFM, and EFM

Purpose This task enables you to view and retrieve information
on the channel group, Resilient Ethernet Protocol
(REP), Connectivity Fault Management (CFM), and
Ethernet in the First Mile (EFM) on the GE_XP,
Security Level Retrieve or higher
Procedure
Step 1 Verify that the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card is installed in L2-over-DWDM mode.
See the DLP-G379 Changing the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode, on page 315
Step 2 In card view, click the Maintenance > Show Commands tabs.
Step 3 From the Command drop-down list, choose a command.
The following commands are supported:
ETH LACP—Displays detailed LACP information from the GE_XP, 10GE_XP, GE_XPE, or
10GE_XPE cards.
REP TOPO—Displays the topology information for a specific REP segment.
REP TOPO ARCHIVE—Displays the previous topology information for a specific REP segment.
REP INTERFACE—Displays information on the REP interface status and configuration. You can
retrieve detailed information for each segment by selecting Detailed from the Level drop-down list and
providing the segment ID.
OAM DISCOVERY—Displays discovery information for all the EFM interfaces or for a specific EFM
interface.
OAM SUMMARY—Displays the active EFM sessions on a device.
OAM STATISTICS—Displays detailed information about the EFM packets.
OAM STATUS—Displays information about the EFM configurations for all the EFM interfaces or for
a specific interface.
For more information, see the Pseudo Command Line Interface Reference document.
Step 4 From the Level drop-down list, choose Normal or Detailed.

Step 5 Click Show. Depending on the command, the appropriate output appears in the text area.
550
DLP-G616 Viewing PM Parameters of a Channel Group
DLP-G616 Viewing PM Parameters of a Channel Group

Purpose This task enables you to view current statistical
performance monitoring (PM) counts on the GE_XP,
10GE_XP, GE_XPE, and 10GE_XPE cards and
channel groups to detect possible performance
problems.
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf mode), double-click the GE_XP, 10GE_XP,
GE_XPE, or 10GE_XPE card where you want to view the channel group statistics. The card view appears.
Step 2 Click the Performance > Channel Groups > Statistics tabs.
Step 3 Click Refresh. Performance monitoring statistics for each channel group on the card appear in the Statistics
tab.
View the PM parameter names in the Param column. The current PM parameter values appear in the Port
# (CHGRP) column. For PM parameter definitions, see the Monitor Performance document.
Note To refresh, reset, or clear PM counts, see the “NTP-G73 Change the PM Display” procedure.
DLP-G617 Viewing Utilization PM Parameters of a Channel Group

Purpose This task enables you to view line utilization PM
counts on the GE_XP, 10GE_XP, GE_XPE, and
10GE_XPE cards and channel groups to detect
possible performance problems.
551
DLP-G618 Viewing History PM Parameters of a Channel Group
Procedure
Step 1 In node view, double-click the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card where you want to
view the channel group utilization. The card view appears.
Step 2 Click the Performance > Channel Groups > Utilization tabs.
Step 3 Click Refresh. The utilization percentages for each channel group on the card appear in the Utilization tab.
View the Port # column to find the channel group you want to monitor.
The transmit (Tx) and receive (Rx) bandwidth utilization values, for the previous time intervals, appear in
the Prev-n columns. For PM parameter definitions, see the Monitor Performance document.
DLP-G618 Viewing History PM Parameters of a Channel Group

Purpose This task enables you to view historical PM counts at
selected time intervals on GE_XP, 10GE_XP,
GE_XPE, and 10GE_XPE cards and channel groups
to detect possible performance problems.
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf mode), double-click the GE_XP, 10GE_XP,
GE_XPE, and 10GE_XPE card where you want to view the channel group history PM data. The card
view appears.
Step 2 Click the Performance > Channel Groups > History tabs.
Step 3 From the Port field, choose a channel group.
Step 4 Click Refresh. Performance monitoring statistics for each channel group on the card appear in the
History tab.
552
NTP-G283 Managing the Card CFM Settings
View the PM parameter names that appear in the Param column. The PM parameter values appear in
the Prev-n columns. For PM parameter definitions, see the Monitor Performance document.
NTP-G283 Managing the Card CFM Settings

Purpose This procedure changes the CFM settings for GE_XP,
Prerequisite Procedures • DLP-G379 Changing the GE_XP, 10GE_XP,

315
necessary)
Procedure

DLP-G621 Enabling CFM on a Card
DLP-G622 Enabling CFM for a Port
DLP-G623 Creating a Maintenance Domain Profile
DLP-G624 Deleting a Maintenance Domain Profile
DLP-G625 Creating a Maintenance Association Profile
DLP-G626 Modifying a Maintenance Association Profile
DLP-G627 Deleting a Maintenance Association Profile
DLP-G628 Mapping Profiles
DLP-G629 Creating a MEP
DLP-G630 Deleting a MEP
DLP-G631 Creating a MIP
553
DLP-G632 Deleting a MIP

DLP-G633 Pinging a MEP
DLP-G634 Displaying Output of a Traceroute MEP
DLP-G635 Enable CFM on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards Using PCLI
DLP-G636 Create a Maintenance Domain on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards
Using PCLI
DLP-G637 Create a Maintenance Intermediate Point on the GE_XP, 10GE_XP, GE_XPE, or
10GE_XPE Cards Using PCLI
DLP-G638 Create a Maintenance End Point on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards
Using PCLI

Purpose This task allows you to enable or disable CFM on
Note CFM is disabled on the card by default. CFM must be enabled at both card and port levels for the CFM
service to work.
For information about interaction of CFM with other protocols, see the “Protocol Compatibility list” section.
Procedure
See the DLP-G379 Changing the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode, on page 315.
Step 2 In card view, click the Provisioning > Security tab.
Step 3 Uncheck the MAC security check box to disable MAC security.
Step 4 In card view, click the Provisioning > CFM > Configuration > Global Settings tabs.
554
Step 5 Check the Enable CFM check box that is present at the bottom of the screen.
Step 6 Choose the value for CC Timer field. The value can be 1 second, 10 seconds, or 1 minute.
Note Continuity Check (CC) messages are periodically exchanged between maintenance end points
(MEPs). The CC Timer field is used to set the time frequency for transmission of CC messages.
Step 7 Click Apply to enable CFM on the card.

Note Uncheck the Enable CFM check box to disable CFM on the card.

Purpose This task allows you to enable or disable CFM for
each port on GE_XP, 10GE_XP, GE_XPE, and
10GE_XPE cards.
Procedure
Note CFM must be enabled at both card and port levels for the CFM service to work. However, CFM
is enabled on all the ports by default.
Step 2 In card view, click the Provisioning > CFM > Configuration > Global Settings tabs.
Step 3 If you want to enable CFM on a specific port, check the Enable CFM check box against that port.
Step 4 Choose the value for CC Timer field. The value can be 1 second, 10 seconds, or 1 minute.
Note Continuity Check (CC) messages are periodically exchanged between MEPs. The CC Timer field
is used to set the time frequency for transmission of CC messages.
Step 5 Click Apply to enable CFM on the port.

Note Uncheck the Enable CFM check box against the port to disable CFM on the port.
555

Purpose This task allows you to create a maintenance
domain profile on the GE_XP, 10GE_XP,
You can create up to eight maintenance domain profiles on the GE_XP, 10GE_XP, GE_XPE, or
10GE_XPE cards. The maximum number of characters for the maintenance domain profile and the
maintenance association profile must not exceed 43 characters.
Procedure
Step 2 In card view, click the Provisioning > CFM > Configuration > Domain Profiles tabs or in
node/network view, click the Provisioning > CFM Profiles > Domain Profiles tabs.
Note Use the network view to store the domain profile on multiple nodes.
Step 3 Click Add row(s).

Step 4 Enter the name of the domain in the Domain Name field.
Step 5 Enter the level of the domain profile in the Level field. The range of the domain profile level is from 0 to 7.
Step 6 Click Store.
Step 7 Choose the card slot where you want to store this domain profile and click OK.
DLP-G624 Deleting a Maintenance Domain Profile

Purpose This task allows you to delete a maintenance domain
profile on the GE_XP, 10GE_XP, GE_XPE, and
10GE_XPE cards.
556
Procedure
Step 2 In card view, click the Provisioning > CFM > Configuration > Domain Profiles tabs or in
node/network view, click the Provisioning > CFM Profiles > Domain Profiles tabs.
Step 3 Select the domain profiles that you want to delete.
Step 4 Check the on Node check box.
Step 5 Click Delete Sel. row(s).
Step 6 Choose the card slot where you want to delete this profile and click OK.
Step 7 In the Deleting Profile dialog box, click Yes.

Purpose This task allows you to create a maintenance
association profile on GE_XP, 10GE_XP, GE_XPE,
and 10GE_XPE cards.
Note You can create up to 1500 maintenance association profiles on GE_XP, 10GE_XP, GE_XPE, or
10GE_XPE cards.
557
Procedure
See theDLP-G379 Changing the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode, on page 315.
Step 2 In card view, click the Provisioning > CFM > Configuration > MA Profiles tabs or in node/network
view, click the Provisioning > CFM Profiles > MA Profiles tabs.
Note Use the network view to store the maintenance association profile on multiple nodes.
Step 3 Click Add row(s).

Step 4 Enter the name of the maintenance association in the Maintenance Profile Name field.
Step 5 Enter the VLAN ID in the VLAN ID field. The range of the VLAN ID is from 1 to 4093.
Step 6 Check the CC Enable check box to receive Continuity Check messages.
Step 7 Click Store.
Step 8 Choose the card slot where you want to store this maintenance association profile and click OK.

Purpose This task allows you to modify a maintenance
and 10GE_XPE cards.
Note Ensure that the maintenance association profile you want to modify is not associated with a maintenance
domain profile.
Procedure
Step 3 Select the maintenance association profiles that you want to modify.
558
Step 4 Click Modify Selected Profile(s).

Step 5 Modify the values as required and click OK.

Purpose This task allows you to delete a maintenance
and 10GE_XPE cards.
Note Ensure that the maintenance association profile you want to delete is not associated with a maintenance
domain profile.
Procedure
Step 3 Select the maintenance association profiles that you want to delete.
Step 4 Check the on Node check box.
Step 5 Click Delete Sel. row(s).
Step 6 Choose the card slot where you want to delete this profile and click OK.
Step 7 In the Deleting Profile dialog box, click Yes.
DLP-G628 Mapping Profiles

Purpose This task allows you to map a maintenance association
profile to a maintenance domain profile on the
559
Note Ensure that you have already created maintenance domain profiles and maintenance association profiles.
Procedure
Step 2 In card view, click the Provisioning > CFM > Configuration > MA-Domain Mapping tabs.
Step 3 From the main drop-down list, choose a maintenance domain profile.
Step 4 Click Link MA Profiles.
Step 5 From the Available Profiles list, choose the required MA profiles and click the right arrow button to
move the MA profiles to the Linked Profiles list and click OK.
Note The maintenance association profiles that are mapped with a specific maintenance domain profile
must have a unique SVLAN ID.

Purpose This task allows you to create a Maintenance End
Point (MEP) for a given VLAN range on a specific
maintenance domain.
560
Note You can create up to 255 MEPs and MIPs on the GE_XP and 10GE_XP cards. You can create up to
500 MEPs and MIPs on the GE_XPE and 10GE_XPE cards.
Procedure
Step 2 In card view, click the Provisioning > CFM > Configuration > MEP tabs.
Step 4 From the Port drop-down list, choose a port where you want to create the MEP.
Note CFM must be enabled on the port to create a MEP. The port must not belong to a channel group.
Step 5 From the Domain drop-down list, choose a maintenance domain.

Step 6 Enter the SVLAN ID in the Vlan Id field.
Note The specified VLAN must be configured on the selected port. The specified VLAN must also
appear in the MA-Domain Mapping table.
Step 7 Enter the MP ID (identifier of the maintenance end point) in the MPID field and click OK. The range of the
MP ID is from 1 to 8191.
The MP ID must not be the same between the maintenance end points.

Purpose This task allows you to delete a MEP on the GE_XP,
561
Procedure
Step 2 In card view, click the Provisioning > CFM > Configuration > MEP tabs.
Step 3 Select the MEPs that you want to delete.

Purpose This task allows you to create a Maintenance
Intermediate Point (MIP) for a given VLAN range
with a specific maintenance level.
Note You can create up to 255 MEPs and MIPs on the GE_XP and 10GE_XP cards. You can create up to
500 MEPs and MIPs on the GE_XPE and 10GE_XPE cards.
Procedure
Step 2 In card view, click the Provisioning > CFM > Configuration > MIP tabs.
Step 4 From the Port drop-down list, choose a port where you want to create the MIP.
Note The port must not belong to a channel group.
Step 5 From the Level drop-down list, choose a maintenance level. The range of the maintenance level is from 0
to 7.
Step 6 Enter the SVLAN range in the Vlan range field. The range of the SVLAN is from 1 to 4093.
Note The specified SVLAN must be configured on the selected port.
562
Step 7 Click OK.


Purpose This task allows you to delete a MIP on the GE_XP,
Procedure
Step 2 In card view, click the Provisioning > CFM > Configuration > MIP tabs.
Step 3 Select the MIPs that you want to delete.
DLP-G633 Pinging a MEP

Purpose This task allows you to display the output of the ping
command on the GE_XP, 10GE_XP, GE_XPE, and
10GE_XPE cards.
563
Procedure
the DLP-G379 Changing the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode, on page 315 task.
Step 2 In card view, click the Provisioning > CFM > Ping tabs.
Step 3 Enter the MP ID value in the MPID field. The range of the MP ID is from 1 to 8191.
Note Remote MP ID user cannot ping local MP ID.
Step 4 (Optional) Enter the MAC address of the remote maintenance point in the Mac Addr field. The format of
MAC address is abcd.abcd.abcd.
Step 5 Enter the SVLAN ID in the VLAN ID field. The range of the SVLAN ID is from 1 to 4093.
Step 6 Enter the domain name in the Domain Name field.
Step 7 Enter the size of the ping packet in the DataGram Size field. The default value is 100.
Step 8 Enter the number of ping packets in the No of Requests field. The default value is 5.
Step 9 Click Ping. The output of the ping command appears in the Ping Response area.

Purpose This task allows you to display the output of the
traceroute command on the GE_XP, 10GE_XP,
Procedure
Step 2 In card view, click the Provisioning > CFM > Traceroute tabs.
Step 3 Enter the remote MP ID value in the MPID field. The range of the MP ID is from 1 to 8191.
Step 4 (Optional) Enter the MAC address of the remote maintenance point in the Mac Addr field. The format of
MAC address is abcd.abcd.abcd.
Step 5 Enter the SVLAN ID in the VLAN ID field. The range of the SVLAN ID is from 1 to 4093.
Step 6 Enter the domain name in the Domain Name field.
564
NTP-G285 Managing the Card EFM Settings
Step 7 Click TraceRoute Response.

The output of the traceroute command appears in the TraceRoute Response area.
Verify the RlyHit message is shown in the traceroute display and LTM reaches a maintenance point
whose MAC address matches the target MAC address.
Verify the RlyFDB message is shown in the traceroute display when the next hop address is found in
the forwarding database.
Verify the RlyMPDB message is shown in the traceroute display when the next hop address is found in
the CCDN.
NTP-G285 Managing the Card EFM Settings

Purpose This procedure changes the EFM settings of the

Muxponder Cards
315
necessary)
Procedure

DLP-G639 Enabling EFM for a Port
DLP-G640 Configuring EFM Parameters
DLP-G641 Configuring EFM Link Monitoring Parameters
DLP-G642 Enabling Remote Loopback for a Port
565
DLP-G643 Enable EFM on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards Using PCLI
DLP-G644 Configure the EFM Mode on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards Using
PCLI

Purpose This task allows you to enable or disable EFM for
each port on the GE_XP, 10GE_XP, GE_XPE, and
10GE_XPE cards.
Note You can enable EFM on both UNI and NNI ports. You cannot enable or disable EFM for ports that belong
to a channel group. For information about interaction of EFM with other protocols, see the “11.14.2
Protocol Compatibility list” section on page 11-62.
Procedure
Step 2 In card view, click the Provisioning > EFM > Configuration tabs. The EFM details appear for each port.
Step 3 From the EFM State drop-down list, choose Enabled.
Step 4 Click Apply to enable EFM for that port.
Note From the EFM State drop-down list, choose Disabled to disable EFM for that port.
566

Purpose This task allows you to configure EFM parameters
on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE
cards.
Procedure
Step 2 In card view, click the Provisioning > EFM > Configuration tabs.
Step 3 Modify the EFM parameter settings as described in the table.
Table 218: EFM Parameter Settings

Port (Display only) Port number (n-n) —
and rate (GE or TEN_GE).
EFM State Sets the state of the EFM protocol Enabled

for each port.
Disabled
Mode Sets the operating mode of the port. Active

If the mode is Active, the port
sends OAM Protocol Data Units Passive
(OAMPDUs) at regular intervals to
the partner ports. If the mode is
Passive, the port will not send
OAMPDUs until the partner ports
send OAMPDUs.
567

Link Fault Sets the Remote Failure Indication Error Block
(RFI) action. If the link is down on
None
a port, the link fault RFI is sent to
the partner port through OAMPDU.
An alarm indicating the remote
failure indication link fault
(RFI-LF) is raised. The alarm is
cleared after you clear the link fault
condition.
You can specify the following
actions for link fault RFI:
• Error Block—The interface is
placed in the error-block state
and the RFI-LF alarm is
raised.
• None—Only the RFI-LF
alarm is raised.
Note Dying Gasp and
critical events are
not supported.
Session Timer Sets the duration up to when the Default: 5 seconds

EFM session is retained with the
Range: 2 to 30 seconds
partner port without receiving
OAMPDUs.
Step 4 Click Apply to save the changes.


Purpose This task allows you to configure EFM link
monitoring parameters for each port on the GE_XP,
568
Procedure
Step 2 In card view, click the Provisioning > EFM > Link Monitoring tabs.
Step 3 Modify the EFM link monitoring parameter settings as described in the table.
Table 219: EFM Link Monitoring Parameter Settings
Port (Display only) Port number (n-n) —

and rate (GE or TEN_GE).
EF Max Sets the threshold value for the Range: 1 to 65535

maximum number of errored
frames to detect during a specific
period.
EF Min Sets the threshold value for the Range: 0 to 65535

minimum number of errored frames
to detect during a specific period.
EF Action Specifies that when the parameter None

value exceeds the maximum
Squelch
threshold value, the applicable
action is None.
When the parameter value falls
below the minimum threshold
value, a threshold crossing alert
(transient condition) is generated.
EF Window Period in which the errored frame Range: 10 to 600

parameters are monitored.
EFP Max Sets the threshold value for the Range: 1 to 65535
frames within the last n frames.
EFP Min Sets the threshold value for the Range: 0 to 65535
minimum number of errored frames
within the last n frames.
EFP Action Specifies that when the parameter None

Squelch
threshold value, the applicable
action is None.
569
EFP Window Period in which the EFP parameters Range: 1 to 65535

are monitored.
EFSS Max Sets the threshold value for the Range: 1 to 900
seconds within the last m seconds.
EFSS Min Sets the threshold value for the Range: 0 to 900
minimum number of errored
seconds within the last m seconds.
EFSS Action Specifies that when the parameter • None

threshold value, the applicable • Squelch
action is None.
EFSS Window Specifies the period when the EFSS Range: 100 to 9000
parameters are monitored.


Purpose This task allows you to enable remote loopback for
each port on the GE_XP, 10GE_XP, GE_XPE, and
10GE_XPE cards.
Procedure
570
NTP-G287 Managing the Card REP Settings
Step 2 In card view, click the Provisioning > EFM > Loopback tabs.
The remote loopback type details appear for each port.
Step 3 From the Remote Loopback Type drop-down list, choose Remote Loopback.
NTP-G287 Managing the Card REP Settings

Purpose This procedure changes the REP settings for the

Muxponder Cards
315
necessary)
Procedure

DLP-G713 Provisioning Administrative VLAN for Ports in a REP Segment
DLP-G645 Creating a Segment
DLP-G646 Editing a Segment
DLP-G647 Activating VLAN Load Balancing
DLP-G648 Deactivating VLAN Load Balancing
DLP-G649 Create a Segment on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards Using PCLI
DLP-G650 Configure STCN on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards Using PCLI
571
DLP-G651 Configure Preemption Delay on the Primary Edge Port Using PCLI
DLP-G652 Configure VLAN Load Balancing on the Primary Edge Port Using PCL

Purpose This task allows you to provision administrative
VLAN for NNI and UNI ports in a REP segment on
the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE
cards.
Note One administrative CVLAN and one administrative SVLAN can be provisioned for each card. The REP
segments using NNI ports send Hardware Flood Layer (HFL) messages using the administrative SVLAN.
The REP segments using UNI ports send HFL messages using the administrative CVLAN. The two
VLANs need not be the same.
Procedure
See DLP-G379 Changing the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode, on page 315.
Step 2 In card view, click the Provisioning > REP > Admin VLAN Configuration tabs.
Step 3 To provision administrative VLAN for NNI ports in a REP segment, perform the following steps:
From the SVLAN drop-down list, choose a SVLAN. The following table describes the REP convergence
time for SVLANs.
Table 220: REP Convergence Time for SVLANs
SVLAN Administrative VLAN REP Convergence Time
0 (default) Not configured 4 to 5 seconds
1 to 4093 Configured Less than 200 milliseconds
572
Click Apply
To associate the chosen SVLAN with the NNI ports, see DLP-G382 Adding SVLANS to NNI Ports.
Step 4 To provision administrative VLAN for UNI ports in a REP segment, perform the following steps:
Enter the CVLAN in the CVLAN field.
Click Apply.
To associate the CVLAN with the UNI ports, see DLP-G384 Provisioning the QinQ Settings.

Purpose This task allows you to create a segment on the
Note • You can create up to three segments on a card. Each segment can have up to two ports on the
same switch.
You must configure the REP administrative VLAN to activate the Hardware Flood Layer (HFL).
Before creating REP segments, you must configure the administrative VLAN or use the default VLAN
1 and add the ports to the segment. Only one SVLAN can be configured per card for all the three
segments. REP uses the administrative VLAN to flood its own control traffic.
The administrative CVLAN is required if a REP port is configured as a UNI port. However, the REP ports
are configured as NNI ports in many configurations, and hence the administrative CVLAN is not required
in these configurations. The option to configure the administrative CVLAN is present in CTC.
You must configure two edge ports in the segment. A segment has only one primary edge port. If you
configure two ports in a segment as the primary edge port, for example, ports on different switches,
REP selects one of the ports to serve as the primary edge port based on port priority.
If REP is enabled on two ports on a switch, both the ports must be either regular ports or edge ports.
However, if the No-neighbor port is configured, one port can be an edge port and another port can be
a regular port.
You can also optionally configure where to send segment topology change notifications (STCNs) and
VLAN load balancing (VLB). STCNs are enabled only for primary edge ports. VLB configurations
are enabled on any edge ports. For information about interaction of REP with other protocols, see the
“11.14.2 Protocol Compatibility list” section on page 11-62
573
Procedure
SeeDLP-G379 Changing the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode, on page 315.
Step 2 In card view, click the Provisioning > REP > Segment tabs.
Step 4 Enter the segment ID in the Segment field. The range of the segment ID is from 1 to 1024.
Step 5 From the Port drop-drown list, choose a REP port that must belong to this segment.
Note A REP port can belong to only one segment.
Step 6 From the Port Role area, choose whether you want to configure the port as an edge port or a regular port. The
options are:
a) Edge—The port is configured as an edge port.
• Check the Primary check box to configure the edge port as a primary edge port. A segment can have
only one primary edge port.
Note If an edge port is configured as primary edge port, the other edge port in the ring
automatically becomes secondary edge port. If neither edge port is configured as primary
edge port, one edge port is automatically selected as primary edge port, and the other edge
port is secondary edge port. Configuring an edge port as a primary edge port is not
mandatory. However, it is recommended since VLAN load balancing must be configured
on the node with the primary edge port.
• Uncheck the Primary check box to configure the edge port as a secondary edge port.
• (Optional) Check the Preferred check box to configure the regular or edge port as a preferred alternate
port (alternate to primary edge port). This port blocks a range of SVLANs for VLAN load balancing.
There is no limit on the number of preferred ports in a REP ring. The preferred port, if configured,
is relevant even without VLAN load balancing, as it takes priority over non-preferred ports for
alternate port election.
Note Configuring a port as preferred does not ensure that it becomes the alternate port; it only
gets preference over the other ports that are not configured as preferred when an alternate
port is elected.
• Check the NoNeighbor check box if the edge port must not have a neighbor port. REP does not
check for neighbor adjacency.
Note When the NoNeighbor check box is checked, ensure that only one segment is created.
b) None—The port is configured as a regular port. If you choose this option, Segment Topology Change
Notifications (STCN) and VLAN Load Balancing (VLB) configurations are disabled.
Check the Preferred check box to configure the regular port as a preferred alternate port.
Step 7 From the STCN area, configure the destination of STCN messages:
Check the Enable check box to enable sending STCN messages.
From the Port drop-down list, choose the STCN port to send STCN messages or enter the segment ID in the
Segment field to send STCN messages. The STCN port and REP port must be unique.
574
Step 8 From the VLAN Load Balancing area, configure VLAN Load Balancing on the primary edge port:
Check the Enable check box to enable VLB.
Enter a single SVLAN or range of SVLANs in the SVLAN field. These SVLANs are blocked at the
alternate ports. The primary edge port blocks the remaining VLANs.
Enter the Rep PortId in the Rep PortId field to identify the VLAN blocking alternate port. This unique
port ID is automatically generated when REP is enabled.
Check the Preferred check box to select the segment port previously identified as the preferred alternate
port for VLAN load balancing.
When you check Preferred under VLAN Load Balancing area, you configure VLAN load balancing
to use one of the previously configured preferred ports (under the Port Role area) to be the load
balancing port. This restricts the load balancing port to be one among the preferred ports, but you
cannot select a specific preferred port.
Step 9 From the VLB Preempt Delay area, enter the trigger delay for automatic VLB activation. The range is 15 to
300 seconds.
Step 10 Click Next.
Step 11 Enter the details of the second port to add it to the segment.
Step 12 Repeat step6 to step 10 when the first port is configured as a regular port and the second port is configured
as a primary edge port. Repeat step 6 to step 7 when the first port is configured as a primary edge port and
the second port is configured as a regular port.
Step 13 Click Finish.

Purpose This task allows you to edit a segment on the GE_XP,
Note You can edit only the STCN and VLB entries for a segment.
575
Procedure
DLP-G379 Changing the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode, on page 315.
Step 2 In card view, click the Provisioning > REP > Segment tabs. The list of segments appear.
Step 3 Choose a segment from the list of segments.
Step 4 Click Edit.
Step 5 Modify the values as required and click Finish.

Purpose This task allows you to activate VLAN load balancing
on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE
cards.
Procedure
Step 4 Click Activate VLB.
Note When VLAN load balancing is activated, the default configuration is manual preemption with
the delay timer disabled.
576
DLP-G648 Deactivating VLAN Load
Balancing
DLP-G648 Deactivating VLAN Load Balancing

Purpose This task allows you to deactivate VLAN load
balancing on the GE_XP, 10GE_XP, GE_XPE, and
10GE_XPE cards.
Procedure
Step 4 Click Deactivate VLB.
NTP-G165 Modifying the Ethernet, Line and PM Thresholds

Purpose This procedure changes Ethernet, line, and PM
threshold settings for the GE_XP, 10GE_XP,

Muxponder Cards
577
NTP-G165 Modifying the Ethernet, Line and PM Thresholds
Procedure
Step 1 As needed, complete the NTP-G103 Backing Up the Database procedure, to preserve the existing
transmission settings.
Step 2 Verify the card mode:
Display the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE card in card view.
Click the Provisioning > Card tabs.
Verify that the card mode is set to the mode designated by your site plan:
L2-over-DWDM (GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE)
10GE TXP (10GE_XP or 10 GE_XPE)
10GE MXP (GE_XP or GE_XPE)
20GE MXP (GE_XP or GE_XPE)
If the card mode is set correctly, continue with step 4. If not, complete the DLP-G379 Changing
the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode, on page 315 task.
Step 3 Complete the DLP-G380 Provisioning Ethernet Settings task.

Step 4 If the ONS-SC-E1-T1-PW or ONS-SC-E3-T3-PW SFP is inserted in the GE_XPE card, complete the
following tasks, as needed.
DLP-G684 Provisioning the PDH Ethernet Settings
DLP-G685 Provisioning the Electrical Lines
Step 5 If the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card mode is L2-over-DWDM, complete the
following tasks, as needed. If the card mode is not L2-over-DWDM, continue with step 7.
DLP-G381 Provisioning Layer 2 Protection Settings
DLP-G382 Adding SVLANS to NNI Ports
DLP-G383 Provisioning the Quality of Service Settings
DLP-G384 Provisioning the QinQ Settings
NTP-G205 Enabling Link Integrity on a Card
DLP-G385 Provisioning the MAC Filter Settings
NTP-G204 Enabling IGMP Snooping on a Card or NTP-G220 Enable IGMP Snooping on GE_XP,
10GE_XP, GE_XPE, or 10GE_XPE Cards Using PCLI.
NTP-G206 Enabling MVR on a Card or NTP-G224 Enable MVR on GE_XP, 10GE_XP, GE_XPE, or
10GE_XPE Cards Using PCLI.
DLP-G460 Enabling MAC Address Learning on SVLANs for GE_XPE or 10GE_XPE Cards or NTP-
G226 Enable MAC Address Learning on SVLANs for GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE
Cards Using PCLI.
Step 6 Complete the following tasks, as needed:
578
DLP-G380 Provisioning Ethernet Settings
DLP-G386 Provisioning the Trunk Port Alarm and TCA Threshold

DLP-G387 Provisioning the Client Port Alarm and TCA Thresholds
DLP-G388 Changing the RMON Threshold
DLP-G389 Changing OTN Settings
NoteTo use the Alarm Profiles tab, including creating alarm profiles and suppressing alarms, see the
Alarm and TCA Monitoring and Management document.

Purpose This task changes the Ethernet settings for the GE_XP,
10GE_XP, GE_XPE, or 10GE_XPE card.
Procedure
GE_XPE, or 10GE_XPE card where you want to change the Ethernet settings. The card view appears.
Step 2 Click the Provisioning > Ether Ports > Ethernet tabs.
Step 3 Modify any of the settings for the Ethernet tab as described in the table. The parameters that appear depend
on the card mode.
Table 221: GE_XP, 10GE_XP, GE_XPE, and 10GE_XPEEthernet Settings
Parameter Description Card Mode Options
Port (Display only) The Port • L2-over-DWDM —

number (n-n) and rate (GE
or TEN_GE). • 10GE TXP
• 10GE MXP
• 20GE MXP
579
Parameter Description Card Mode

Options
MTU The maximum size of the • L2-over-DWDM Numeric. Default: 9700
Ethernet frames accepted
• 10GE TXP Range 64 to 9700 (for
by the port. The port must
R9.1 and later)
be in OOS/locked state. • 10GE MXP (jumbo frame)
• 20GE MXP
Mode Sets the Ethernet mode. L2-over-DWDM Auto (default)

The port must be in
10GE TXP Display Only
OOS/locked state before
setting the card mode. 10GE MXP 1000 Mbps
Note For GE_XP 20GE MXP 10000 Mbps
and GE_XPE
cards that are Auto_Fdx (10Mbps
in Y-cable Full). This option
protection applies to ONS-SE-
groups, Mode ZE-EL copper SFP
must be set to that carries traffic
1000 Mbps for from GE_XP and
those client GE_XPE cards.
ports that are
configured in NoteIf Mode is set to
Y-cable. For Auto on the
10GE_XP and GE_XP or
10GE_XPE GE_XPE port,
cards that are autonegotiation
in Y-cable gets enabled on
protection the peer port.
groups, Mode
must be set to
10000 Mbps. NoteOn GE_XP card,
the copper
Pluggable
Port Module
(PPM)
interface can
auto-negotiate
and carry
traffic even
when the peer
interface
operates at
rates other
than 1000
Mbps.
580

Flow Control Enables/disables flow L2-over-DWDM ON—Flow control is
control messaging with its enabled.
10GE MXP
peer port. When enabled,
OFF (default)—Flow
the port can send and 10GE TXP
receive PAUSE frames control is disabled.
when buffer congestion 20GE MXP Display Only.
occurs. When disabled, no
PAUSE frames are
transmitted and the
PAUSE frames received
are discarded.
Note Flow control
messaging is
symmetric and
not negotiated.
When flow
control is
enabled on one
port, the other
end of the link
(peer port) is
not considered.
That is, even if
flow control is
disabled on the
peer port, the
GE_XP,
10GE_XP,
GE_XPE, or
10GE_XPE
card will send
PAUSE
frames.
581

Media Type Note PROV-MISMATCH• L2-over-DWDM DS1 over Ethernet
alarm is raised if the (ANSI) ONS-SC-
• 10GE MXP
Media Type is not set to E1-T1-PW)
Ethernet Over DS1 • 20GE MXP
DS3 over Ethernet
(ANSI) or Ethernet Over
E1 (ETSI) for (ANSI) ONS-SC-
ONS-SC-EOP1,Ethernet E3-T3-PW)
Over DS3 (ANSI) or E1 Over Ethernet
Ethernet Over E3 (ETSI) (ETSI) ONS-SC-
for ONS-SC-EOP3, or E1-T1-PW)
DS1 Over Ethernet
(ANSI) or E1 Over E3 Over Ethernet
Ethernet (ETSI) for (ETSI) ONS-SC-
ONS-SC-E1-T1-PW or E3-T3-PW)
DS3 Over Ethernet
(ANSI) or E3 Over
Ethernet (ETSI)
ONS-SC-E3-T3-PW. Set
the correct Media Type
to clear the
PROV-MISMATCH
alarm.
Committed Info Rate Sets the guaranteed • L2-over-DWDM Numeric. Default: 100%
information rate based on
the service-level • 10GE MXP Range: 0 to 100%
agreement of the service • 20GE MXP Granularity: 0.1%
provider. The port must
be in OOS/locked state.
Committed Burst Size Sets the maximum • L2-over-DWDM • 4k (default)

number of bits that will be
transferred per second. • 10GE MXP • 8k
The port must be in • 20GE MXP • 16k
OOS/locked state before
the Committed Burst Size • 32k
is provisioned.
• 64k
• 128k
• 256k
• 512k
• 1MB
• 2MB
• 8MB
• 16MB
582

Excess Burst Size The maximum number of L2-over-DWDM • None
bits that are credited for
10GE MXP • 4k (default)
later transfer in the event
the committed burst rate 20GE MXP • 8k
cannot be transmitted. The
port must be in • 16k
OOS/locked state before • 32k
the Excess Burst Size is
provisioned. • 64k
• 128k
• 256k
• 512k
• 1MB
• 2MB
• 8MB
• 16MB
NIM Sets the port network L2-over-DWDM • UNI

interface mode (NIM). Mode—provisions
This parameter classifies the port as a
port types designed for the user-to-network
Metro Ethernet market to interface (UNI). This
simplify deployment, is the interface that
management, and faces the subscriber.
troubleshooting. The port
• NNI
must be in OOS/locked
state before the NIM is Mode—provisions
provisioned. the port as a
network-to-network
interface. This is the
interface that faces
the service provider
network.
Egress QoS Enables Quality of L2-over-DWDM • Checked—QoS is

Service (QoS) on the enabled on the port’s
port’s egress or output egress queues.
queues. The port must be
• Unchecked—
in OOS/locked state
before the Egress QoS is (Default) QoS is
disabled on the
provisioned.
port’s egress queues.
583

MAC Learning Enables or disables MAC L2-over-DWDM Checked—MAC
learning for the port on learning is enabled
GE_XP, 10GE_XP, for this port.
Unchecked—
cards. MAC learning is
(Default) MAC
used by Layer 2 switches
to learn the MAC learning is disabled.
addresses of network
nodes so the Layer 2
switches send traffic to
the right location. Layer 2
switches, including the
GE_XP, 10GE_XP,
cards in L2-over-DWDM
mode with MAC Learning
configured, maintain a
MAC learning table that
associates the MAC
addresses and VLANs
with a given port.
Note MAC
addresses on
SVLANs
attached to the
port must also
be enabled to
provision
MAC address
learning on
GE_XPE and
10GE_XPE
cards.
Note MAC address

table aging is
300 seconds. It
cannot be
changed.
584

Ingress CoS Provisions the IEEE L2-over-DWDM
802.1p ingress Class of
Service (CoS). The CoS
.1p bits set the Ethernet
frame priority. The port
must be in OOS/locked
state before the Ingress
CoS is provisioned.
Ingress CoS is used to set
the priority of the Ethernet
frame in the service
provider network, This
parameter is used to set
the CoS.1p bits in the
SVLAN tag.
Ingress CoS applies only
to ports provisioned as
UNI mode. It does not
apply to ports provisioned
as NNI mode.
585

• 0—(default) All
incoming frames on
the port will have the
CoS.1p bits in the
SVLAN tag set to 0.
• 1—All incoming
frames on the port
will have the CoS.1p
bits in the SVLAN
tag set to 1.
frames on the port
bits in the SVLAN
tag set to 2.
frames on the port
bits in the SVLAN
tag set to 3.
frames on the port
bits in the SVLAN
tag set to 4.
frames on the port
bits in the SVLAN
tag set to 5.
frames on the port
bits in the SVLAN
tag set to 6.
frames on the port
bits in the SVLAN
tag set to 7.
• Trust—Automatically
copies customer
VLAN tag into the
service provider
586

VLAN tag.
CVLAN—CoS can
be provisioned
based on CVLAN.
For information on
how CoS can be
provisioned on the
IEEE 802.1QinQ
CVLAN tags, refer
to the DLP-G384
Provisioning the
QinQ Settings task.
If CVLAN CoS
is configured on a
GE_XP or a
10GE_XP card, a
PROV-MISMATCH
alarm is raised. Until
this alarm is cleared,
provisioning on the
card is not possible.
The CVLAN CoS
configuration takes
effect only after
QinQ is configured.
Inner Ethertype (Hex) Defines the inner L2-over-DWDM Numeric.

Ethertype field. The Default: 8100 (IEEE Std
Ethertype field indicates
802.1Q customer
which protocol is being
VLAN tag type)
transported in an Ethernet
frame. Range: 0x0600 to 0xFFFF
The inner Ethertype

applies to ports
provisioned in UNI mode
only. It does not apply to
ports provisioned as NNI
mode. The ports must be
OOS/locked before the
inner Ethertype is
provisioned.
587

Outer Ethertype (Hex) Defines the outer L2-over-DWDM Numeric.
Ethertype field. The Default: 8100 (IEEE
Ethertype field identifies
802.1Q customer
which protocol is being
VLAN tag type)
transported in an Ethernet
frame. The ports must be Range: 0x0600 to 0xFFFF
OOS/locked before the
Outer Ethertype is
provisioned.
Note The
PROV-MISMATCH
alarm is raised on
GE_XPE and
10GE_XPE cards if
more than four
different Outer
Ethertype options
are configured per
card.
IGMP Static Router Port Adds multicast-capable L2-over-DWDM Checked—IGMP

ports to the forwarding static router port is
table for every IP enabled.
multicast. Unchecked—(Default)
IGMP static router
port is disabled.
AIS Action Defines the AIS action L2-over-DWDM None—No action.

type provisioned on the Squelch—When
port. an AIS packet is
received on a
SVLAN
terminating on
the UNI-port,
the UNI port is
squelched.
588
Protection Action Configures the standby L2-over-DWDM • None—No action.

port behavior. • Squelch—The
Set Protection Action to laser on the
None if Media Type is set standby port in
to Ethernet Over DS1 a 1+1
(ANSI) or Ethernet Over protection
E1 (ETSI) for group is
ONS-SC-EOP1, Ethernet squelched. This
Over DS3 (ANSI) or setting has no
Ethernet Over E3 (ETSI) effect if the port
for ONS-SC-EOP3, or is not part of
DS1 Over Ethernet the 1+1
(ANSI) or E1 Over protection
Ethernet (ETSI) for group.
ONS-SC-E1-T1-PW or
DS3 Over Ethernet
(ANSI) or E3 Over
Ethernet (ETSI) for
ONS-SC-E3-T3-PW.
The table shows the inner and outer Ethertype behavior based on the NIM setting (either NNI mode or UNI
mode). When the NIM is set to UNI, and the QinQ mode is set to Selective, the Ethertype behavior depends
on the SVLAN/CVLAN operation that is provisioned, either Add or Translate. (QinQ parameters are
provisioned in the DLP-G384 Provisioning the QinQ Settings task.)
Note A packet can exit out of any UNI/NNI port if the outermost tag in the packet matches with the SVLAN
provisioned on that port. In other words, in the egress path, the inner tags (even if present) of the
packet are not matched with the inner SVLAN or CVLAN provisioned on the port.
Note The Committed Burst Size and Excess Burst Size must be configured based on the expected
packet size to ensure that no packets are dropped when Flow Control is enabled. For example, if
the CIR is 40% and packet size is 1 KB, the Committed Burst Size and Excess Burst Size should
be set to 1 MB.
Note When you set the Committed Info Rate above 40% on 10GE_XP and 10GE_XPE cards, the
Committed Burst Size and Excess Burst Size must be set to at least 32K. The Committed Burst Size
and Excess Burst Size can be increased based on the packet size and Committed Info Rate value.
Table 222: Ethertype Behavior
Port Type/ Ethertype NNI Mode UNI Mode
Transparent Selective Operation: Selective Operation:

Add Translate
Inner Ethertype Not applicable: the Not applicable: all Working Working
outer Ethertype packets are mapped (card-based) (card-based)
value is used. over the SVLAN.
589
Port Type/ Ethertype NNI Mode UNI Mode

Transparent Selective Operation: Selective Operation:
Add Translate
Outer Ethertype Working (per port) Not applicable: the Not applicable: the This cannot be set
outer Ethertype is outer Ethertype is by port, only by
contained in the the one contained in card. The outer
inner VLAN (same the inner VLAN. Ethertype is
as UNI Selective automatically set to
mode). the inner Ethertype.
Step 4 Click Apply.


Purpose This task changes the PDH Ethernet settings for the
GE_XPE card.

• Set the Media Type as DS1 Over Ethernet in
Provisioning > Ether Ports > Ethernet tab in
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the GE_XPE card where you
want to change the PDH Ethernet settings. The card view appears.
Step 2 Click the Provisioning > Ether Ports > PDH Ethernet Parameters tabs. The PDH Ethernet Parameters
tab appear only when the . The PDH Ethernet Parameters tab is available in GE_XPE card view only,
provided the PPM for GE_XPE port is created in FE mode.
Step 3 Modify any of the settings for the PDH Ethernet Parameters tab as described in table.
590
Table 223: GE_XPE Card PDH Ethernet Settings

number (n-n) and rate.
• 10GE MXP
• 20GE MXP
Port Name (Display only) The port • L2-over-DWDM —

name.
• 10GE MXP
• 20GE MXP
Sets the MPLS Inner • L2-over-DWDM

Label value.
• 10GE MXP
• 20GE MXP
Sets the MPLS Outer • L2-over-DWDM

Label value.
• 10GE MXP
• 20GE MXP
Sets the jitter buffer value. • L2-over-DWDM Table 224: Jitter Buffer
Values for Various
• 10GE MXP Payload Types provides
• 20GE MXP jitter buffer values for
different payloads.
Note The traffic is down if
the jitter buffer is set
to >=192000 when
Media Type is set to
DS1 over Ethernet
(ANSI)
ONS-SC-E1-T1-PW)
and E1 Over Ethernet
(ETSI)
ONS-SC-E1-T1-PW).
(ONS-SC-E1-T1-PW • L2-over-DWDM
only) Sets the RX
sensitivity value. • 10GE MXP
• 20GE MXP
591
Only Unicast IP addresses • L2-over-DWDM —

are accepted.
• 10GE MXP
• 20GE MXP
Only Unicast IP addresses • L2-over-DWDM —

are accepted.
• 10GE MXP
• 20GE MXP
Table 224: Jitter Buffer Values for Various Payload Types
Payload Type Jitter Buffer Value
Lower Limit Upper Limit
T1 (DS1) 1500 20000
T3 (DS3) 400 4500
E1 1500 200000
E3 400 60000
Step 4 Click Apply.


Purpose This task changes the Electrical Lines settings for the
GE_XPE card.

• Set the Media Type as DS1 Over Ethernet in
Provisioning > Ether Ports > Ethernet tab in
592
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the GE_XPE card where you
want to change the Electrical Lines settings. The card view appears.
Step 2 Click the Provisioning > Ether Ports > Electrical Lines tabs. The Electrical Lines tab appear only when
the ONS-SC-E1-T1-PW or ONS-SC-E3-T3-PW SFP is inserted. The Electrical Lines tab is available in
GE_XPE card view only, provided the PPM for GE_XPE port is created in FE mode.
Step 3 Modify any of the settings for the Electrical Lines > DS1 or Electrical Lines > DS3 tab as described in table.
Table 225: GE_XPE Card Electrical Lines Settings

number (n-n
• 10GE MXP
) and rate
• 20GE MXP
Port Name (Display only) The port • L2-over-DWDM —

name.
• 10GE MXP
• 20GE MXP
Clock Source Sets the Clock Source • L2-over-DWDM Default:

• 10GE MXP • Internal (for
ONS-SC-E3-T3-PW)
• 20GE MXP
• Adaptive (for
ONS-SC-E1-T1-PW)
Options:
• Loopback Timing
• Internal
• Adaptive
593

• L2-over-DWDM Default:
• 10GE MXP C-BIT (for ONS-SC-
E3-T3-PW ANSI)
• 20GE MXP
Unframed (for ONS-
SC-E3-T3-PW
ETSI)
ESF (for ONS-SC-
E1-T1-PW ANSI)
Framed (for ONS-

SC-E1-T1-PW
ETSI)
Options:
L2-over-DWDM (for ONS-SC-E3-T3-

PW ANSI)
10GE MXP
20GE MXP HDB3 (for ONS-SC-
E3-T3-PW ETSI)
(for ONS-SC-E1-T1-
PW ANSI)
HDB3 (for ONS-SC-

E1-T1-PW ETSI)
(ETSI)
HDB3 (ETSI)
0-225 ft(for ONS-SC-

E3-T3-PW ANSI)
L2-over-DWDM (for ONS-SC-E1-T1-
10GE MXP PW ANSI)
20GE MXP
0-225 ft
225-450 ft
594
Step 4 Click Apply.


Purpose This task provisions the Layer 2 protection settings
for the GE_XP, 10GE_XP, GE_XPE, and
10GE_XPE cards when the cards are provisioned in
L2-over-DWDM mode.
GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Layer 2 protection settings must be planned for the entire
VLAN ring. One card in the ring is provisioned as the master card and one of its port is set to Blocking.
The master card coordinates the protection switching for the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE
in a VLAN ring.
Up to 1024 SVLANs can be protected. This protection is used in FAPS ring. When a fault occurs on the
working path of FAPs ring, all the SVLANs whose protection is set, are moved to the protection path of
the FAPS ring. All the SVLANs can be protected or a range of SVLANs can be protected.
Note To perform this task, the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card must be in L2-over-DWDM
mode. To change the card mode, complete the DLP-G379 Changing the GE_XP, 10GE_XP, GE_XPE,
and 10GE_XPE Card Mode task.
Note You can choose to enable another card in the ring to be the master card. However, only one card in the ring
can be provisioned as master card. Make sure that the provisioning settings on the card that was previously
configured as the master are disabled as soon as another card is enabled as the master card. To perform this
task complete the DLP-G507 Enabling a Different GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Card as
Master Card task.
Procedure
GE_XPE, or 10GE_XPE card where you want to change the protection settings. The card view appears.
Step 2 Click the Provisioning > Protection tabs.
595
Step 3 In the Status column, modify the port protection status by clicking the appropriate table cell and choosing
one of the following from the drop-down list:
Forwarding—Forwards the Ethernet packets that are received by the port.
Blocking—Blocks the Ethernet packets that are received by the port.
NoteOne port of the master card within a VLAN ring must be set to Blocking. All other ports must be
set to Forwarding.
Step 4 Check the Master check box if you want the card to serve as the protection coordinator for the VLAN ring.
If not, continue with step 5.
Step 5 From the Protection drop-down list, choose one of the following:
Enabled—Enables protection.
Disabled—Disables protection.
Forced—Converts all the SVLANs to protected SVLANs irrespective of the SVLAN protection
configuration in the SVLAN database. This is applicable to a point-to-point linear topology. The
SVLAN protection must be forced to move all SVLANs, including protected and unprotected
SVLANs, to the protect path irrespective of provisioned SVLAN attributes.
Step 6 From the Hold Off Time drop-down list, choose one of the following:
Disabled (default)—A FAPS switchover occurs immediately.
50 msec, 100 msec, 200 msec, 500 msec, 1 sec, 2 sec, or 5 sec—Holds off FAPS protection for the
selected duration.
NoteTo get consistent results ensure Hold Off Time values are the same throughout the ring.
NoteFAPS is an Layer 2 protection enabled on a VLAN. When a fiber fault occurs, Layer 1 protection
is triggered immediately to restore the traffic. Setting the Hold Off Time option prevents
Layer 2 FAPS protection from triggering at the same time as Layer 1 protection thereby
avoiding traffic hits.
Step 7 Click Refresh to refresh the FAPS Layer 2 protection settings.

Step 8 Click Protect SVLAN's to protect the SVLANs.
The Protect All SVLAN's dialog appears.
a) Choose the Select All option to protect all the SVLANs.
b) Choose the Range option to provide the range of SVLANs to protect.
Upto 1024 SVLANs can be protected. SVLANs that are in use are excluded.
c) Click OK.
Step 9 Set the following parameters for FAPS switching with CRC errors:
Switch with CRC Alarm—Check this check box to enable FAPS switching with CRC errors.
CRC Threshold—Threshold for CRC error count. The default CRC threshold value is 10(-e)2. The
available options are 10(-e)2, 10(-e)3, and 10(-e)4.
CRC Soak Count—Number of times the CRC error rate exceeds the CRC threshold value before raising the
DATA-CRC alarm. The default CRC Soak Count is 10. The valid range is from 3 to 10.
596
DLP-G507 Enabling a Different GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Card as Master Card
CRC Poll Interval—Time interval (in seconds) between the successive polls. The default CRC Poll Interval
is 60 seconds.
For example, if the CRC Threshold value = 10(-e)2, CRC Soak Count = 10, and CRC Poll Interval =
60 seconds, then FAPS occurs when the incoming CRC error rate is more than 10(-e)2 continuously
across 10 poll intervals (10*60 = 600 seconds).
Clear/Suppress CRC Alarm—Uncheck the Clear/Suppress CRC Alarm check box for FAPS to occur. If
you check this check box, the DATA-CRC alarm gets cleared and FAPS does not occur.
NoteAs along as the Clear/Suppress CRC Alarm checkbox is checked, the DATA-CRC alarm is not
raised on that port and FAPS does not occur.
NoteFor consistent result, ensure that all the values that are set in Step 7 are same throughout the
ring.

DLP-G507 Enabling a Different GE_XP, 10GE_XP, GE_XPE, or

10GE_XPE Card as Master Card
Purpose This task provisions another GE_XP, 10GE_XP,
GE_XPE, or 10GE_XPE card on a stable VLAN ring,
to be the master card when the cards are provisioned
in L2-over-DWDM mode.
Layer 2 protection must be enabled for the entire
VLAN ring. One card in the ring is provisioned as the
master card and one of its port is set to Blocking. The
master card coordinates the protection switching for
the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE
cards in a VLAN ring.

To perform this task, the card must be in
L2-over-DWDM mode. To change the card mode,
complete the DLP-G379 Changing the GE_XP,
10GE_XP, GE_XPE, and 10GE_XPE Card Mode,
on page 315 .
597
You can choose to enable another card in the ring to be the master card. However, only one card in the
ring can be provisioned as master card. Make sure that the provisioning settings on the card that was
previously configured as the master are disabled as soon as another card is enabled as the master card.
Procedure
GE_XPE, or 10GE_XPE card in a VLAN ring where you want to enable master card provisioning.
Step 2 Perform the following steps:
Click the Provisioning > Protection tabs.
From the Status drop-down list, choose Blocking for a trunk port.
NoteOne port of the master card within a VLAN ring must be set to Blocking. All other ports must be
set to Forwarding.
Check the Master check box for the card that serves as the protection coordinator for the VLAN ring.
From the Protection drop-down list, choose Enabled.
Click Apply.
Step 3 The master card provisioning on the other card must be disabled. Perform the following steps:
Uncheck the Master check box for the card where Master node provisioning must be disabled.
Click Apply.
From the Protection drop-down list, choose Disabled.
Click Apply.
Step 4 The protection on the card that was disabled in step 2 must be enabled again. Perform the following steps:
From the Protection drop-down list, choose Enabled.
Click Apply.
From the Status drop-down list, choose Forwardingon both ports.
Click Apply.

Purpose This task adds or removes service provider VLAN
(SVLAN) provisioning to/from GE_XP, 10GE_XP,
GE_XPE, and 10GE_XPE ports. This task only
applies to GE_XP, 10GE_XP, GE_XPE, and
10GE_XPE cards in L2-over- DWDM mode.
598

• To perform this task, the card must be in
L2-over-DWDM mode. To change the card
mode, complete the DLP-G379 Changing the
GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE
Card Mode, on page 315
• This task can only be performed on ports
provisioned as NNI. See the DLP-G380
Provisioning Ethernet Settings task.
Procedure
GE_XPE, or 10GE_XPE card where you want to change the SVLAN port settings. The card view appears.
Step 2 Click the Provisioning > SVLAN tabs.
Step 3 For each SVLAN shown in the table, click the check box under the Port [port name] table cell to include
the SVLAN in that port. If you do not want the SVLAN included, uncheck the check box.
Note If no SVLANs appear in the SVLAN tab, complete the DLP-G421 Creating and Storing an
SVLAN Database .
Step 4 Click Apply.


Purpose This task provisions the Weighted Round Robin
(WRR) value and bandwidth for QoS Class of Service
(CoS) egress queues on a GE_XP, 10GE_XP,
GE_XPE, and 10GE_XPE card port.
599
DLP-G470 Provisioning the CoS Settings

L2-over-DWDM mode and the port must have
QoS enabled. Refer to the DLP-G379 Changing
the GE_XP, 10GE_XP, GE_XPE, and
10GE_XPE Card Mode, on page 315 and the
DLP-G380 Provisioning Ethernet Settings, if
needed.
Procedure
10GE_XP, GE_XPE, or 10GE_XPE card where you want to change the QoS settings.
Step 2 Click the Provisioning > QoS tabs.
Step 3 In the Port field at the bottom of the window, choose the port where you want to provision the QoS settings.
Step 4 For each CoS egress queue, 0 through 7, define the following:
WRR weight—sets the Weighted Round Robin (WRR) level for the CoS egress queue. The default is 1.
The range is 0 to 15, where 0 is Strict Priority.)
NoteThe GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE define a set of eight queues, one queue for each
CoS. Only one of the queues can be assigned the 0 WRR weight (Strict Priority).
Bandwidth—sets the bandwidth allocated for the CoS egress queue, 100 is the default. This bandwidth
value is the percentage (%) of bandwidth with respect to the SFP, XFP, or port speed (100 Mbps for
FE, 1 Gbps for GE, and 10 Gbps for 10GE) of the interface.
Step 5 Click Apply. Click Yes in the confirmation dialog box.

DLP-G470 Provisioning the CoS Settings

Purpose This task provisions Class of Service (CoS) settings
on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE
card.
600

L2-over-DWDM mode and the port must be in
OOS state.
Procedure
10GE_XP, GE_XPE, or 10GE_XPE card where you want to change the CoS settings.
Step 2 Complete Ingress CoS section in the DLP-G380 Provisioning Ethernet Settings task.

Purpose This task provisions the IEEE 802.1QinQ VLAN tags
on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE
card UNI ports. QinQ tags expand the VLAN
capability by tagging the tagged packets to produce
a “double-tagged” Ethernet frame. For service
providers the expanded VLAN allows specific services
to be provided on specific VLANs for specific
customers, while other types of services can be
provided to other customers on other VLANs.

• DLP-G421 Creating and Storing an SVLAN
Database
• This task can only be performed on the cards
UNI ports. (To provision the port Ethernet
parameters, see the DLP-G380 Provisioning
Ethernet Settings task.)
601
Procedure
GE_XPE, or 10GE_XPE card where you want to change the QinQ settings.
Step 2 Click the Provisioning > QinQ tabs.
Step 3 Click the Port field and choose the port where you want to provision QinQ. Channel groups configured in
UNI mode appear in the Port field along with the physical ports.
Step 4 Click the Mode field and choose one of the following modes from the drop-down list:
Selective—The incoming Ethernet packet is checked against the CVLAN and SVLAN table. If the
CVLAN is not found, the packet is dropped. If you choose Selective, add an entry in the QinQ tab to
map the administrative CVLAN to the SVLAN (if it is not same as the one used for data).
Transparent—All incoming packets are transported with the additional VLAN chosen in the SVLAN
field. If you choose transparent, the traffic on administrative CVLAN will pass through.
Step 5 Click the BPDU field and choose one of the following bridge protocol data unit (BPDU) modes from
the drop-down list:
Drop (default)—If checked, drops incoming packets with any of the following destination MAC
addresses. The BPDU default can be applied for any UNI port.
01-80-c2-00-00-00—IEEE 802.1D
01-80-c2-00-00-02—Link Aggregation Control Protocol (LACP)
01-80-0c-cc-cc-cc—VLAN Spanning Tree Plus (PVST+)
01-00-c-cc-cc-cc—Cisco Discovery Protocol (CDP) type 0x2000, VLAN Trunk Protocol (VTP)
type 0x2003, Port Aggregation Protocol (PAgP), type 0x0104, Uni-Directional Link Detection
(UDLD) type 0x111, Dynamic Trunking Protocol (DTP) type 0x2004
Tunnel—If checked, transparently sends any of the destination MAC addresses listed above.
Step 6 If the Mode was set to Selective, complete the following steps. If not, continue with step 7.
To add a row, click Add.
Click the CVLAN table and type in the CVLAN range. You can enter a single value or a range using “–”
between the two ends of the range.
NoteIf you are using Software Release 8.5 or earlier, it is recommended that you do not specify a
CVLAN range due to certain limitations in the feature.
Click the SVLAN table cell and choose an SVLAN from the drop-down list.
Click the Operation table cell and choose an operation:
Add (default)—Adds the SVLAN on top of the CVLAN. The operation default can be applied for
any UNI port.
Translate—CVLAN is translated with the SVLAN value.
Double Add—(GE_XPE and 10GE_XPE cards only) Adds an inner and an outer SVLAN to double
tagged packets only. CVLAN settings are not required. If this double tagged selective operation is
present on a port, no other selective operation can be present.
602
DLP-G221 Enabling MAC Address Learning on SVLANs
• Translate Add—(GE_XPE and 10GE_XPE cards only) CVLAN gets translated to inner SVLAN
and the SVLAN is added.
Note If Double Add and Translate Add are configured on a GE_XP or a 10GE_XP card, a
PROV-MISMATCH alarm is raised. Until this alarm is cleared, provisioning on the card
is not possible.
Note A CVLAN with a value of 0 means “untagged packet”.
Note Two or more CVLANs cannot be translated over the same SVLAN.
e) (GE_XPE and 10GE_XPE cards only) Click the COS table cell and choose a value from the drop down
list.
f) Click Apply.
g) Continue with step 9.
Step 7 If the Mode was set to Transparent, in the SVLAN field, choose the SVLAN to be added to incoming packets.
Step 8 Click DSCP-Cos mapping Table to provision CoS based on DSCP for each port.
Step 9 For each DSCP, choose a CoS value from 0 to 7 and click OK.
DLP-G221 Enabling MAC Address Learning on SVLANs

Purpose This task enables MAC address learning on SVLANS
for GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE
cards.

VLANs must already be created on the selected card.
Procedure
Step 1 Complete the following tasks, as needed:

DLP-G460 Enabling MAC Address Learning on SVLANs for GE_XPE or 10GE_XPE Cards
NTP-G226 Enable MAC Address Learning on SVLANs for GE_XP, 10GE_XP, GE_XPE, or
10GE_XPE Cards Using PCLI
603
DLP-G460 Enabling MAC Address Learning on SVLANs for GE_XPE or 10GE_XPE Cards
DLP-G460EnablingMACAddressLearningonSVLANsforGE_XPEor10GE_XPE
Cards
Purpose This task enables MAC address learning on SVLANs
attached to the port of a GE_XPE or 10GE_XPE card.

L2-over-DWDM mode. Refer to the DLP-G379
Changing the GE_XP, 10GE_XP, GE_XPE, and
10GE_XPE Card Mode, on page 315.
Note MAC address learning is applicable only for GE_XPE and 10GE_XPE cards. If MAC address learning is
configured on a GE_XP or a 10GE_XP card, a PROV-MISMATCH alarm is raised. Until this alarm is
cleared, provisioning on the card is not possible.
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the GE_XPE or
10GE_XPE card where you want to enable MAC address learning.
Step 2 Enable MAC address learning on the port. Perform the following steps:
Click Provisioning > Ethernet.
Check the MAC Learning check box.
Note If the per port MAC address learning is configured on a GE_XP or 10 GE_XP cards, before
upgrading to a GE_XPE or 10 GE_XPE card, enable MAC address learning per SVLAN. Not
doing so disables MAC address learning.
Step 3 Enable MAC address learning on the SVLAN attached to the port. Perform the following steps:
Click SVLAN > SVLAN DB tabs.
Click Load. This loads an SVLAN database from a network node or local file and replaces any SVLANs
that are in the network view VLAN DB table.
604
Check the MAC Learning check box related to the SVLAN (one or more than one SVLAN) to be
configured with MAC address learning.
Click Store. This records and enables the new configuration.

Purpose This task provisions the MAC address filter for the
GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE cards
when the cards are provisioned in L2-over-DWDM
mode. The MAC address filter is a list of MAC
addresses whose packets should be accepted or
dropped.

GE_XPE, and 10GE_XPE Card Mode
Procedure
GE_XPE, or 10GE_XPE card where you want to change the MAC filter settings.
Step 2 Click the Provisioning > Security > MAC Filter tabs.
Step 3 Click the port for which you want to create a MAC filter.
Step 4 Click Edit.
Step 5 In the Edit MAC Address dialog box, click Add. A new table entry appears with the MAC address
00-00-00-00-00-00.
Step 6 In the MAC Address Port field, type in the MAC address you want to filter over the default 00-00-00-00-00-00
address.
Step 7 If you want to add more MAC addresses, repeat step 5 and step 6. (Up to eight MAC addresses can be added
for each port.) If not, click OK.
Step 8 On the MAC Filter table, provision the Allowed check box:
Checked—All MAC addresses different from the address(es) entered in the table will be dropped.
Unchecked—All MAC addresses matching the address(es) entered in the table will be dropped.
Step 9 Click Apply.
605
NTP-G237 Retrieving and Clearing MAC Addresses on SVLANs
Step 10 Repeat step 3 to step 9 for each port of the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card that you
want to set up.
NTP-G237 Retrieving and Clearing MAC Addresses on SVLANs

Purpose This procedure retrieves and clears MAC addresses
learned on GE_XP, 10GE_XP, GE_XPE, or
10GE_XPE cards.

315
• DLP-G221 Enabling MAC Address Learning on
SVLANs
Caution Retrieving and clearing learned MAC addresses are CPU intensive and traffic affecting. You must clear
the MAC addresses only during a scheduled maintenance window.
Note It is not possible to simultaneously retrieve learned MAC addresses from both CTC and TL1 interfaces.
Procedure
Step 1 In the node view (single-shelf mode) or shelf view (multishelf view), double-click the GE_XP,
10GE_XP, GE_XPE, or 10GE_XPE card where you want to retrieve the MAC addresses.
Step 2 To retrieve the MAC addresses learned, perform the following steps:
Click Maintenance > MAC Addresses > Learned.
In the SVLAN field, type a valid SVLAN range. The SVLAN range is from 1 to 4093.
Click Refresh.
The table displays the following fields:
606
DLP-G546 Viewing MAC Addresses on a Card
MAC Address—Displays the MAC address for the port.

VLAN—Displays the VLAN identifier for the port.
Port—Displays the port number.
Right-click the column heading to display the following options:

Row Count—Displays the number of learned MAC addresses retrieved.
Sort Column—Sorts the table by the column’s values.
Hide Column—Hides the column from view.
Reorder Columns Visibility—Displays all hidden columns.
Step 3 Click Refresh to refresh the list of MAC addresses learned.

Step 4 Click Clear to clear the MAC addresses learned on all the SVLANS of the card.
Note It is not possible to delete the MAC addresses learned on a per SVLAN basis.
Step 5 To view card MAC addresses, complete the DLP-G546 Viewing MAC Addresses on a Card task.
DLP-G546 Viewing MAC Addresses on a Card

Purpose This task allows you to view the MAC addresses for
each client and trunk port and the CPU port of the
card.
Procedure
Step 1 To view the card MAC addresses, click Maintenance > MAC Addresses > Card. The MAC addresses
for each client and trunk port and the CPU port are displayed.
The table displays these fields:
Port—Displays the port number.
MAC Address—Displays the MAC address for the port.
607
NTP-G311 Provisioning the Storm Control Settings
NTP-G311 Provisioning the Storm Control Settings

Purpose This task provisions the storm control settings for the
GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE cards
when the cards are provisioned in L2-over-DWDM
mode.
Prerequisite Procedures To perform this task, the card must be in

L2-over-DWDM mode. To change the card mode,
complete the DLP-G379 Changing the GE_XP,
10GE_XP, GE_XPE, and 10GE_XPE Card Mode,
on page 315 .
Procedure
10GE_XP, GE_XPE, or 10GE_XPE card where you want to change the storm control settings.
Step 2 Click the Provisioning > Security > Storm Control tabs.
Step 3 Modify any of the settings as described in table.
Table 226: Storm Control Settings
Port (Display only) The Port number

(n-n) and rate (GE or TEN_GE).
DLF Storm Control Enables or disables DLF storm • Checked—DLF storm control
control on the card. is enabled.
• Unchecked—DLF storm
control is disabled.
DLF Storm Control Threshold Threshold value to set the number Range: 0 to 16777215 packets per
(pps) of unknown unicast packets per second
second.
608
Mcast Storm Control Enables or disables Multicast storm • Checked—Multicast storm

control on the card. control is enabled.
• Unchecked—Multicast storm
Mcast Storm Control Threshold Threshold value to set the number Range: 0 to 16777215 packets per
(pps) of multicast packets per second. second
Bcast Storm Control Enables or disables Broadcast • Checked—Broadcast storm

storm control on the card. control is enabled.
• Unchecked—Broadcast storm
Bcast Storm Control Threshold Threshold value to set the number Range: 0 to 16777215 packets per
(pps) of broadcast packets per second. second
Step 4 Click Apply.


Purpose This task enables link integrity on GE_XP, 10GE_XP,
GE_XPE, or 10GE_XPE cards.
Prerequisite Procedures None
Procedure
Complete these tasks, as needed:

DLP-G509 Enabling Link Integrity Using CTC
NTP-G216 Enable Link Integrity on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards Using PCLI
609

Purpose This task enables link integrity on GE_XP, 10GE_XP,
GE_XPE, or 10GE_XPE cards.
Procedure
Step 1 From the View menu, choose Go to Network View.

Step 2 Create or load an SVLAN profile. To create a SVLAN profile see the DLP-G471 Creating SVLAN or
CVLAN Profile task.
Note Make sure the Link Integrity check box is selected to enable link integrity for a profile and save
it to the node.
Step 3 Associate the SVLAN profile (with Link Integrity enabled) to a SVLAN on a port. To do this perform
these steps:
In node view (single-shelf mode), or shelf view (multishelf mode), double-click the GE_XP, 10GE_XP,
GE_XPE, or 10GE_XPE card. The card view appears.
Click the Provisioning > Profiles Mapping > SVLAN tabs.
Enter the SVLANs or SVLAN range in the SVLAN to View text box.
A table appears that displays SVLANs and available ports. The SVLAN profiles that was created
must be applied to a SVLAN and a port. However, make sure the SVLAN has already been associated
with the port via the QinQ tab (For information on how to associate a SVLAN to a port, see the DLP-
G384 Provisioning the QinQ Settings task).
Select the SVLAN for a port and choose the available SVLAN profile from the drop-box.
Click Apply.
Step 4 AIS action must be set on a per-UNI port basis. Select None or Squelch from the AIS action drop-down list.
For detailed instructions, see the DLP-G380 Provisioning Ethernet Settings task.
610
DLP-G289 Provisioning CVLAN Rate Limiting on a Card
DLP-G289 Provisioning CVLAN Rate Limiting on a Card

Purpose This task provisions CVLAN rate limiting on the
Procedure

Step 2 Create or load a CVLAN profile by setting Committed Info Rate, Committed Burst, Excess Info, Excess Burst.
To create a CVLAN Profile see the DLP-G471 Creating SVLAN or CVLAN Profile.
Note You cannot provision CVLAN rate limiting on channel groups.
Step 3 Associate the CVLAN profile to a CVLAN on a UNI port. To do this perform theae steps:
GE_XPE, and 10GE_XPE card. The card view appears.
Click the Provisioning > Profiles Mapping > CVLAN tabs.
Enter the CVLANs or CVLAN range in the CVLANS to View text box.
A table appears that displays CVLANs and available ports. The CVLAN profiles that were created
must be applied to a CVLAN and port. However, make sure the CVLAN has already been associated
with the port via the QinQ tab (For information on how to associate a CVLAN profile to a UNI port,
see the DLP-G384 Provisioning the QinQ Settings).
Select the CVLAN for a given port and choose the available CVLAN profile from the drop-down list.
Click Apply.
NTP-G208 Provisioning SVLAN Rate Limiting on a Card

Purpose This task provisions SVLAN rate limiting on the
611
DLP-G515 Provisioning SVLAN Rate Limiting Using CTC
Procedure
Complete the following tasks, as needed:

NTP-G225 Provision SVLAN Rate Limiting on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Card
Using PCLI

Purpose This task provisions SVLAN rate limiting on the
Procedure

Step 2 Create or load a SVLAN profile by setting Committed Info Rate, Committed Burst, Excess Info, Excess Burst.
To create a SVLAN Profile see the DLP-G471 Creating SVLAN or CVLAN Profile task.
Step 3 Associate the SVLAN profile to a SVLAN on a port. To do this, perform the following steps:
GE_XPE, and 10GE_XPE card. The card view appears.
Click the Provisioning > Profiles Mapping > SVLAN tabs.
Enter the SVLANs or SVLAN range in the SVLAN to View text box.
A table appears that displays SVLANs and available ports. The SVLAN profiles that were created must be
applied to a SVLAN and port. However, make sure the SVLAN has already been associated with the
612
DLP-G471 Creating SVLAN or CVLAN Profile
port via the QinQ tab (For information on how to associate a SVLAN profile to a UNI port, see the
DLP-G384 Provisioning the QinQ Settings task and to a NNI port see the DLP-G382 Adding
SVLANS to NNI Ports task).
Select the SVLAN for a given port and choose the available SVLAN profile from the drop-down list.
Click Apply.
DLP-G471 Creating SVLAN or CVLAN Profile

Purpose This task creates an SVLAN profile.
Note You cannot associate SVLAN or CVLAN profiles to channel groups. You can associate a CVLAN
profile only to a UNI port.
Procedure

Step 2 Click the Provisioning > SVLAN > Profiles tabs.
Step 3 Click Add and a profile is added to the Profiles tab. Modify any of these settings:
Name—The profile name can be up to 32 alphanumeric/special characters.
Committed Info Rate—Sets the guaranteed information rate based on the service-level agreement of the
service provider. The valid value ranges from 0 to 100% with 0.1% granularity. The default value is
100%.
Committed Burst—Sets the maximum number of bits that will be transferred per second.
Peak Info rate—Sets the maximum access rate based on the service-level agreement of the service
provider. The valid value ranges from 0 to 100% with 0.1% granularity. The default value is
100%. However, the value must be greater than or equal to the Committed Info Rate.
Peak Burst Size—The maximum number of bits that are credited for later transfer in the event the
committed burst rate cannot be transmitted.
613
NTP-G204 Enabling IGMP Snooping on a Card
Link Integrity—Enables link integrity for the SVLAN profile. Do not check this check box if you are
creating a CVLAN profile.
NoteWhen you set the Committed Info Rate above 40% on 10GE_XP and 10GE_XPE cards, the
Committed Burst Size and Excess Burst Size must be set to at least 32K. The Committed
Burst Size and Excess Burst Size can be increased based on the packet size and Committed
Info Rate value.
Step 4 Click Store.

In the Store Profile(s) dialog box, choose one of the following:
To Node(s)—Stores the SVLAN profile at one or more network nodes. Choose the network nodes
where you want to store the SVLAN profile. To choose more than one node, press the Shift key, or
click Select All.
To File—Stores the SVLAN profile in a file. Enter a file name, then click Browse to navigate to a local
or network drive where you want to store the file.
Step 5 Click OK.

NTP-G204 Enabling IGMP Snooping on a Card

Purpose This procedure enables Internet Group Management
Protocol (IGMP) snooping on a per-SVLAN basis on
GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE cards.
Procedure

DLP-G511 Enabling IGMP Snooping, Fast Leave, Report Suppression, and Protection
NTP-G220 Enable IGMP Snooping on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards Using PCLI
NTP-G217 Enable IGMP Fast-Leave Processing on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards
Using PCLI
614
DLP-G511 Enabling IGMP Snooping, Fast Leave, Report Suppression, and Protection
NTP-G219 Enable IGMP Report Suppression on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards
Using PCLI
DLP-G511 Enabling IGMP Snooping, Fast Leave, Report

Suppression, and Protection
Purpose This procedure explains how to enable IGMP
snooping, IGMP fast leave and IGMP report
suppression on GE_XP, 10GE_XP, GE_XPE, or
10GE_XPE cards using CTC.
Procedure

Step 2 Click the Provisioning > SVLAN > SVLAN DB tabs. Click Load to load the SVLANs on the card where
IGMP must be enabled.
Step 3 For each SVLAN shown in the table, select the following:
Protection—Check the Protection check box to protect the SVLAN.
Check the Protect All SVLANS check box to protect all the SVLANs. Up to 1024 SVLANs can
be protected.
MAC Learning—(GE_XP card only) Check the MAC Learning check box to enable or disable MAC
learning for the port.
IGMP—Check the IGMP check box to enable IGMP for the selected SVLAN.
IGMP Fast Leave—Checking the IGMP Fast Leave check box causes the switch to immediately
remove a port from the IP multicast group when it detects an IGMP, version 2 (IGMPv2) leave
message on that port.
IGMP Suppression—Check the IGMP Suppression check box to enable a single IGMP report to be
sent to each multicast group in response to a single query.
Step 4 Click Store SVLAN DB.
615
NTP-G206 Enabling MVR on a Card
If card protection is enabled and one or more SVLANs are not protected, CTC informs the user that
protection check box is disabled on one or more SVLANs. This allows the user to check the Protection
check box for SVLANs if required.
In the Store SVLAN DB dialog box, choose one of the following:
To Node/Shelf/Card—Select the node and shelf. All the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE
cards in L2 over DWDM mode are displayed. Select the card where you want to store the SVLAN DB.
Stores the SVLAN database at one or more network nodes. Choose the network nodes where you want to
store the SVLAN database. To choose more than one node, press the Shift key, or click Select All.
To File—Stores the SVLAN database in a file. Enter a file name, then click Browse to navigate to a
local or network drive where you want to store the file.
Select the card on which you want to save the changes made in step 3.
Step 5 Click OK.

Note If you want to add the multicast-capable ports to the forwarding table for every IP multicast,
select the IGMP Static Router Port check box as described in the DLP-G380 Provisioning
Ethernet Settings task.
NTP-G206 Enabling MVR on a Card

Purpose This procedure enables Multicast VLAN Registration
(MVR) on GE_XP, 10GE_XP, GE_XPE, or
10GE_XPE cards.
Procedure

DLP-G513 Enabling MVR Using CTC
NTP-G224 Enable MVR on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards Using PCLI
616

Purpose This procedure enables Multicast VLAN Registration
(MVR) on GE_XP, 10GE_XP, GE_XPE, or
10GE_XPE cards using CTC.
Prerequisite Procedures DLP-G382 Adding SVLANS to NNI Ports
Procedure
Step 1 In node view (single-shelf mode), or shelf view (multishelf mode), double-click the GE_XP,
10GE_XP, GE_XPE, or 10GE_XPE card where you want to enable MVR. The card view appears.
Note At least one SVLAN must be configured on the card.
Step 2 Click the Provisioning > MVR tabs.

Step 3 Check the Enabled check box and enter the following information:
IGMP CVLAN—Check box to enable IGMP snooping on CVLAN. This check box is enabled only
when MVR is enabled through the Enabled check box.
Multicast SVLAN—Select the MVR SVLAN ID. The default value is the SVLAN with the lowest ID
configured on the card. The drop box lists all the SVLANs on the GE_XP, 10GE_XP, GE_XPE, or
10GE_XPE card.
NoteSVLAN selected here can not be used for UNI port, make sure that the corresponding SVLAN on
the NNI port is checked.
Multicast Address—Sets the specified multicast group address as the MVR multicast group. The default
address is 239.255.255.255 and the range is 224.0.0.0 to 239.255.255.255. Except the subrange [224-
239].[0/128].0.x.
Count—Sets the range of any additional multicast group addresses. The default is 1, and range is 1 to 256.
Step 4 Click Apply

617

or 10GE_XPE card trunk port alarm and TCA
thresholds.
Note The GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards have two trunk ports. The GE_XP and GE_XPE
trunk ports are 21-1 and 22-1 on the card graphic and 21 (Trunk) and 22 (Trunk) on the Optics Thresholds
table. The 10GE_XP and 10GE_XPE card trunk ports are 3-1 and 4-1 on the card graphic and 3 (Trunk)
and 4 (Trunk) on the Optics Thresholds table.
Procedure
GE_XPE, or 10GE_XPE card where you want to change the trunk port alarm and TCA settings.
Note The hardware device that plugs into a TXP, MXP, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE or
SFPs/XFPs are hot-swappable input/output devices that plug into a port to link the port with the fiber-
optic network. Multirate PPMs have provisionable port rates and payloads. For more information
about SFPs and XFPs, see the “11.26 SFP, SFP+, XFP, CXP, and CFP Modules” section.
Step 3 If TCA is not selected, click TCA and then click Refresh. When TCA is selected, continue with step 4.
Step 4 Verify the trunk port TCA thresholds are provisioned as shown in table. Provision new thresholds as needed
618
Table 227: GE_XP, 10GE_XP, GE_XPE, or 10GE_XPECard Trunk Interface TCA Thresholds
Pluggable Port TCA RX Power High TCA RX Power Low TCA TX Power High TCA TX Power Low
Module (XFP)
XFP WDM no FEC –7 –23 6 –4
XFP WDM standard –7 –27 6 –4

FEC
XFP WDM –7 –27 6 –4

Enhanced FEC
Step 6 Verify the trunk port alarm thresholds are provisioned as shown in table. Provision new thresholds as needed
Table 228: GE_XP, 10GE_XP, GE_XPE, or 10GE_XPECard Trunk Interface Alarm Thresholds
Pluggable Port Alarm RX Power Alarm RX Power Alarm TX Power Alarm TX Power
XFP WDM no FEC –5 –26 5 –3
XFP WDM standard –5 –30 5 –3

FEC
XFP WDM –5 –30 5 –3

Enhanced FEC
Step 7 Click Apply.

Step 8 Repeat step 3 to step 7 to provision the second trunk port.

thresholds for the GE_XP, 10GE_XP, GE_XPE, and
10GE_XPE cards.
Prerequisite Procedures DLP-G726 Preprovisioning a Multirate PPM

619
Note The GE_XP card has 20 client ports. The ports are 1-1 through 20-1 on the card graphic and 1 (Client)
through 20 (Client) on the Optics Thresholds table. The 10GE_XP card has 2 client ports. The ports are 1-1
and 2-1 on the card graphic and 1 (Client) and 2 (Client) on the Optics Thresholds table.
The hardware device that plugs into the card faceplate to provide a fiber interface to the card is called a Small
Form-factor Pluggable (SFP or XFP). In CTC, SFPs and XFPs are called pluggable port modules (PPMs).
SFPs/XFPs are hot-swappable input/output devices that plug into a port to link the port with the fiber-optic
network. Multirate PPMs have provisionable port rates and payloads. For more information about SFPs and
XFPs, see the SFP, SFP+, QSFP+, XFP, CXP, CFP, CFP2 and CPAK Modules, on page 310 section.
Procedure
GE_XPE, or 10GE_XPE card where you want to change the client port alarm and TCA settings.
If TCA is not selected, click TCA and then click Refresh. When TCA is selected, continue with step 4.
Verify the client port TCA thresholds are provisioned as shown in table. Provision new thresholds as
needed by double-clicking the threshold value you want to change, deleting it, entering a new value,
and hitting Enter.
Table 229: GE_XP, 10GE_XP, GE_XPE, or 10GE_XPECard Client Interface TCA Thresholds
Pluggable Port TCA RX Power High TCA RX Power Low TCA TX Power High TCA TX Power Low
Module (XFP)
10GE LAN PHY 1 –14 5 –12
10GBASE-LR
1000Base-SX 0 –17 3 –16
15
(1Gbps)
1
1000Base-LX –3 –20 3 –16
Gigabit Ethernet client
Note You must modify 15 Min and 1 Day independently. To do so, choose the appropriate
radio button and click Refresh.
Step 4 Verify the client port Alarm thresholds are provisioned as shown in table. Provision new thresholds as
needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and hitting Enter.
620
Table 230: GE_XP, 10GE_XP, GE_XPE, or 10GE_XPEcard Client Interface Alarm Thresholds
Pluggable Port Alarm RX Power Alarm RX Power Alarm TX Power Alarm TX Power
10GE LAN PHY 3 –16 1 –8

10GBASE-LR
1000Base-SX 3 –20 –2 –12
16
(1Gbps)
1000Base-SX 3 –18 –2 –12
1
(2Gbps)
1
1000Base-LX 0 –23 –1 –12
Gigabit Ethernet client
Step 5 Click Apply.
Step 6 Repeat step 3 to step 5 to provision each additional client port.

or 10GE_XPE card RMON threshold settings.
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), display the GE_XP, 10GE_XP, GE_XPE,
or 10GE_XPE card where you want to change the RMON thresholds.
Step 2 Click the Provisioning > RMON Thresholds tabs.
Step 4 From the Port drop-down list, choose an individual port, or choose All to provision RMON thresholds for all
ports.
Step 5 From the Variable drop-down list, choose an Ethernet variable. See the table for a list of available Ethernet
RMON variables.
621
Note Variable descriptions were obtained from the following Internet Engineering Task Force
(IETF) Requests for Comment (RFCs): RFC 3635, RFC 2233, and RFC 1757. Refer to the
RFCs for additional information.
Table 231: Gigabit Ethernet RMON Variables
ifInUcastPkts The number of packets, delivered by this sub-layer to

a higher (sub-)layer, which were not addressed to a
multicast or broadcast address at this sub-layer.
ifInMulticastPkts The number of packets, delivered by this sub-layer to

a higher (sub-)layer, which were addressed to a
multicast address at this sub-layer. For a MAC layer
protocol, this includes both Group and Functional
addresses.
ifInBroadcastPkts The number of packets, delivered by this sub-layer to

a higher (sub-)layer, which were addressed to a
broadcast address at this sub-layer.
ifInDiscards The number of inbound packets which were chosen

to be discarded even though no errors had been
detected to prevent their being deliverable to a
higher-layer protocol. One possible reason for
discarding such a packet could be to free up buffer
space.


ifOutMulticastPkts The total number of packets that higher-level protocols

requested be transmitted, and which were addressed
to a multicast address at this sub-layer, including those
that were discarded or not sent. For a MAC layer
protocol, this includes both group and functional
addresses.
ifOutBroadcastPkts The total number of packets that higher-level protocols

requested be transmitted, and which were addressed
to a broadcast address at this sub-layer, including
those that were discarded or not sent.
622
ifOutDiscards The number of outbound packets which were chosen

detected to prevent their being transmitted. One
possible reason for discarding such a packet could be
to free up buffer space.
IfOutErrors Number of outbound packets or transmission units

that could not be transmitted because of errors.
dot3StatsFCSErrors A count of frames received on a particular interface

that are an integral number of octets in length but do
not pass the FCS check.
dot3StatsFrameTooLong A count of frames received on a particular interface

that exceed the maximum permitted frame size.
dot3ControlInUnknownOpCode A count of MAC control frames received on this

interface that contain an opcode that is not supported
by this device.

operation.
dot33StatsFCSErrors A count of frames received on a particular interface

dot3StatsFrameTooLong A count of frames received on a particular interface

dot3ControlInUnknownOpCode A count of MAC control frames received on this

interface that contain an opcode that is not supported
by this device.

operation.
dot3OutPauseFrames A count of MAC Control frames transmitted on this

operation.
etherStatsCRCAlignErrors Total number of packets received that had a length

(excluding framing bits, but including FCS octets) of
between 64 and 1518 octets, inclusive, but had either
a bad FCS with an integral number of octets (FCS
Error) or a bad FCS with a non-integral number of
octets (Alignment Error).
623
etherStatsUndersizePkts The total number of packets received that were less

than 64 octets long (excluding framing bits, but
including FCS octets) and were otherwise well
formed.
etherStatsFragments The total number of packets received that were less

than 64 octets in length (excluding framing bits but
including FCS octets) and had either a bad Frame
Check Sequence (FCS) with an integral number of
octets (FCS Error) or a bad FCS with a non-integral.
etherStatsPkts The total number of packets (including bad packets,

broadcast packets, and multicast packets) received.
etherStatsPkts64Octets The total number of packets (including bad packets)

etherStatsPkts65to127Octets The total number of packets (including error packets)

octets).

FCS octets).

FCS octets).

FCS octets).

FCS octets).

FCS octets).
Note This variable is supported only on client
ports.
624
etherStatsBroadcastPkts The total number of good packets received that were

directed to the broadcast address
etherStatsMulticastPkts The total number of good packets received that were

address.
etherStatsOversizePkts The total number of packets received that were longer

than 1518 octets (for untagged packets) or 1522 octets
(for tagged packets) (excluding framing bits, but
including FCS octets) and were otherwise well
formed.
etherStatsJabbers The total number of packets received that were longer

than 1518 octets (for untagged packets) or 1522 octets
(for tagged packets) (excluding framing bits, but
including FCS octets), and were not an integral
number of octets in length or had a bad FCS.
etherStatsOctets The total number of octets of data (including those in

to use the number of occurrences in the user-set sample period. Absolute sets the threshold to use the
total number of occurrences, regardless of time period.
Step 11 Click OK.

Step 12 To view all RMON thresholds, click Show All RMON thresholds.
625

Purpose This task changes the optical transport network (OTN)
settings for the GE_XP, 10GE_XP, GE_XPE, and
10GE_XPE cards.
Procedure
10GE_XP, GE_XPE, or 10GE_XPE card where you want to change the OTN settings.
Step 3 Modify any of the settings described in the tables.
The table describes the values on the Provisioning > OTN > OTN Lines tab.
Table 232: GE_XP, 10GE_XP, GE_XPE, or 10GE_XPECard OTN Line Settings

Port (Display only) Port number and 3 (Trunk) and 4 (Trunk).
description: 10GE_XP and 10GE_XPE cards
21 (Trunk) and 22 (Trunk).
GE_XP and GE_XPE cards
ITU-T G.709 OTN Sets the OTN lines according to • Enable

ITU-T G.709.
• Disable

correction (FEC).
• Enhanced
626

bit error rate.

rate.
• 1E-6
• 1E-7
• 1E-8
• 1E-9
The table describes the values on the Provisioning > OTN > ITU-T G.709 Thresholds tab.
Table 233: GE_XP, 10GE_XP, GE_XPE, or 10GE_XPECard ITU-T G.709 Threshold Settings


627

The table describes the values on the Provisioning > OTN > FEC Threshold tab.
Table 234: GE_XP, 10GE_XP, GE_XPE, or 10GE_XPECard FEC Threshold Settings

The table describes the values on the Provisioning > OTN > Trail Trace Identifier tab.
Table 235: GE_XP, 10GE_XP, GE_XPE, and 10GE_XPECard Trail Trace Identifier Settings

• Path

• Manual
to Hex).
628
NTP-G314 Adding a Card on FAPS Ring

is checked.

changes to Hex).
panel updated.
Step 4 Click Apply.

NTP-G314 Adding a Card on FAPS Ring

Purpose This procedure adds a GE_XP or 10GE_XP card on
a FAPS ring.
Tools/Equipment Installed GE_XP or 10GE_XP cards.

“NTP-G15 Install the Common Control Cards” in the
Cisco ONS 15454 Hardware Installation Guide
Complete the "NTP-G179 Install the Transponder and
Muxponder Cards" procedure in "Turn up a node"
chapter.
DLP-G379 Changing the GE_XP, 10GE_XP,
GE_XPE, and 10GE_XPE Card Mode, on page 315
629
DLP-G687 Adding a Card Facing the Master Card on FAPS Ring
Procedure

DLP-G688 Adding a Card Between Slave Cards on FAPS Ring

Purpose This procedure adds a GE_XP or 10GE_XP card that
faces the master card on a FAPS ring.
Procedure
Step 1 Verify that the GE_XP or 10GE_XP card is installed according to the requirements specified in table in
DLP-G375 Installing Fiber-Optic Cables on the Y-Cable Modules in the FlexLayer Shelf task.
Step 2 Insert the new GE-XP card with XFP on the slot.
Step 3 Change the GE_XP card mode to L2-over-DWDM. See DLP-G379 Changing the GE_XP, 10GE_XP, GE_XPE,
and 10GE_XPE Card Mode, on page 315.
Step 4 Create and store an SVLAN database on the new GE_XP card. See the DLP-G421 Creating and Storing an
SVLAN Database task.
Step 5 Enable FAPS protection on the new card.
Step 6 Attach SVLAN to the trunk ports of the new card.
Step 7 Choose OOS,DSBLD from the Admin State column for port 22 on the master card that is facing toward the
new card. This action places port 22 in the blocking state and port 21 in the forwarding state.
Note FAPS configuration mismatch alarm is raised on the master card.
630
Step 8 Switch the traffic to the protect path.

Step 9 Choose OOS,DSBLD from the Admin State column for port 21 on the slave card that is facing toward the
new card.
Step 10 Connect the fiber from the slave card (that is facing toward the new card) to the new card in segment B.
Step 11 Connect the fiber from the master card to the new card in segment A.
Step 12 Choose IS from the Admin State column for port 21 on the slave card that is facing toward the new card.
Step 13 Choose IS from the Admin State column for port 22 on the new card to bring up segment B.
Step 14 Choose IS from the Admin State column for port 21 on the new card.
Note The FAPS state of the new card will be in the forwarding state for both the ports and port 21 of the
slave card will be in the blocking state.
Step 15 Choose IS from the Admin State column for port 22 on the master card to bring up segment A.
Note The FAPS state of port 21 on the master card will be in the blocking state and port 22 will be in the
forwarding state. The trunk ports of the remaining GE_XP cards will be in the forwarding state.
The port 21 of the slave card (that is facing toward the new card) will change to the forwarding
state.

Purpose This procedure adds a GE_XP or 10GE_XP card
between the two slave cards on a FAPS ring.
Procedure
Step 1 Verify that the GE_XP or 10GE_XP card is installed according to the requirements specified in table in the
DLP-G375 Installing Fiber-Optic Cables on the Y-Cable Modules in the FlexLayer Shelf task.
Step 2 Insert the new GE-XP card with XFP on the slot.
Step 3 Change the GE_XP card mode to L2-over-DWDM. See the DLP-G379 Changing the GE_XP, 10GE_XP,
GE_XPE, and 10GE_XPE Card Mode, on page 315.
Step 4 Create and store an SVLAN database on the new GE_XP card. See the DLP-G421 Creating and Storing an
SVLAN Database task.
Step 5 Attach SVLAN to the trunk ports of the new card.
631
NTP-G197 Provisioning the OTU2_XP Card Line Settings, PM Parameters, and Thresholds
Step 6 Choose OOS, DSBLD from the Admin State column for port 22 on slave card 1, and port 21 on slave card 2
that are facing toward the new card.
Step 7 Connect the fiber from the slave card 1 to the new card in segment A.
Step 8 Connect the fiber from the slave card 2 to the new card in segment B.
Step 9 Choose IS from the Admin State column for port 22 on the slave card 1.
Step 10 Choose IS from the Admin State column for port 21 on the new card to bring up segment A.
Step 11 Choose IS from the Admin State column for port 22 on the new card.
Step 12 Choose IS from the Admin State column for port 21 on the slave card 2 to bring up segment B.
NTP-G197 Provisioning the OTU2_XP Card Line

Settings, PM Parameters, and Thresholds
Purpose This procedure changes line settings, PM parameters,
and threshold setting for the OTU2_XP card.

Muxponder Cards
• DLP-G452 Changing the OTU2_XP Card Mode,
on page 318
Procedure
Step 1 As needed, complete the NTP-G103 Backing Up the Database task, to preserve the existing transmission
settings.
Step 2 In node view (single-shelf mode) or shelf view (multishelf view), double-click the OTU2_XP card.
Step 3 Verify the card mode:
Display the OTU2_XP card in card view.
Click the Provisioning > Card tabs.
Verify that the card mode is set to the mode designated by your site plan:
Transponder
632
DLP-G453 Changing the OTU2_XP Card Settings
Standard Regen
Enhanced FEC
Mixed
10G Ethernet LAN Phy to WAN Phy
If the card mode is set correctly, continue with step 6. If not, complete the DLP-G452 Changing
the OTU2_XP Card Mode, on page 318 task.
Step 4 Refer to the OTU2_XP Card Configuration Rules section on before performing any task listed in step 5.
Step 5 Perform any of the following tasks as needed.
DLP-G454 Changing the OTU2_XP Line Settings
DLP-G455 Changing the OTU2_XP Line Section Trace Settings
DLP-G456 Changing the OTU2_XP Line Thresholds for SONET or SDH Payloads
DLP-G457 Provisioning the OTU2_XP Port Alarm and TCA Threshold
DLP-G462 Changing the OTU2_XP Line RMON Thresholds
DLP-G458 Changing the OTU2_XP OTN Settings
DLP-G523 Changing the OTU2_XP Path Trace Settings
DLP-G524 Provisioning the OTU2_XP Path Settings for 10G Ethernet LAN Phy to WAN Phy
Configuration

Purpose This task changes the card settings for the OTU2_XP
card.
633
Procedure
Step 2 Click the Provisioning > Card tab.
Step 3 Modify any of the settings described in table.
Table 236: OTU2_XP Card Settings
Options
Card Configuration Sets the card • Transponder • Transponder

configuration.
• Standard Regen • Standard Regen
• Enhanced FEC • Enhanced FEC
• Mixed • Mixed
• 10G Ethernet LAN • 10G Ethernet LAN
Phy to WAN Phy Phy to WAN Phy
Port Mode Sets the port configuration • Transponder • Transponder

when the card
• Standard Regen • Standard Regen
configuration is set as
Mixed. For card
configurations other than
Mixed, this is a
display-only parameter.
You can configure Ports
2 and 4 as port mode,
when the card is in 10G
Ethernet LAN Phy to
WAN Phy mode.
Termination Mode Sets the mode of • Transparent • Transparent

operation. (This option is
• Section • Regeneration Section
only available for
SONET/SDH payloads). (RS)
• Line
For Standard Regen and • Multiplex Section
Enhanced FEC card (MS)
configurations, this is a
Framing Type (Display only) The card — —

framing type, either
SONET or SDH.
AIS/Squelch Sets the transparent • AIS • AIS

termination mode
configuration. • Squelch • Squelch
634
Options
Regen Line Name Sets the regeneration line — —

name.
ODU Transparency Sets the ODU overhead • Transparent Standard • Transparent Standard
byte configuration. For Use Use
Transponder card
• Cisco Extended Use • Cisco Extended Use
configuration, this is a
Proactive Protection Enables or disables the • Enable • Enable

Regen proactive protection regen
mode. • Disable • Disable
Step 4 Click Apply.


Purpose This task changes the line settings for OTU2_XP card.
Procedure
Step 2 Click the Provisioning > Line > Ports/SONET/Ethernet tabs.
635
Table 237: OTU2_XP Line Settings
Options
Port (Display only) Displays • 1-1 (OC192/10G • 1-1 (STM-64/10G

the port number. Ethernet WAN Ethernet WAN
Phy/10G Ethernet Phy/10G Ethernet
LAN Phy/10G FC) LAN Phy/10G FC)
• 2-1 (OC192/10G • 2-1 (STM-64/10G
Ethernet WAN Ethernet WAN
• 3-1 (OC192/10G • 3-1 (STM-64/10G
• 4-1 (OC192/10G • 4-1 (STM-64/10G
• IB_5G • IB_5G
default. For more default.
information, see,
For more information, see,
DLP-G104 Assigning a
DLP-G104 Assigning a
Name to a Port
Name to a Port
Admin State Sets the port service state. • IS • Unlocked
• IS,AINS • Unlocked,automaticInService
Administrative and
636
Options

the autonomously
• OOS-MA,DSBLD
State. For more
states, see the
Administrative and
options. • Auto Restart: ALS is • Auto Restart: ALS is
on; the laser on; the laser
resolved. resolved.
resolved. resolved.
testing. testing.
637
Options
Reach Displays the optical reach The Reach options The Reach options depend
distance of the client/trunk depend on the traffic type on the traffic type that has
ports. that has been selected. been selected.
Wavelength Displays the wavelength • First Tunable • First Tunable

of the client/trunk ports. Wavelength Wavelength
• Further wavelengths: • Further wavelengths:
850 nm through 850 nm through
1610 nm, 100-GHz 1610 nm, 100-GHz
ITU spacing; coarse ITU spacing;
wavelength division CWDM spacing
multiplexing
Note Supported
(CWDM) spacing wavelengths
Note Supported are marked
wavelengths by asterisks
are marked (**).
by asterisks
(**).
AINS Soak Sets the automatic • Duration of valid • Duration of valid

Double-click the time and hh.mm format, after hh.mm format, after
use the up and down which the card which the card
arrows to change settings. becomes in service becomes IS
(IS) automatically automatically
• 0 to 48 hours, • 0 to 48 hours,
15-minute 15-minute

signal fail bit error rate. • 1E-4 • 1E-4
• 1E-5 • 1E-5

signal degrade bit error • 1E-6 • 1E-6
rate. • 1E-7 • 1E-7
• 1E-8 • 1E-8
• 1E-9 • 1E-9
638
Options

[ETSI] only) The optical
• SDH • SDH
transport type.
Note When Type
is set to
SDH in a
SONET
(ANSI)
provisioning,
SDCC or
LDCC on
OTU2_XP
cards cannot
be
provisioned.
MTU The maximum size of the • 1548 bytes • 1548 bytes

Ethernet frames accepted
• Jumbo (64 to 9,216 • Jumbo (64 to 9,216
by the port. The port must
be in OOS/locked state. bytes) bytes)
MTU stands for

“Maximum Transmission
Unit” typically meant for
configuring the maximum
frame size allowed.
However, the OTU2_XP
card does not block the
frames based on Ethernet
frame size and Jumbo
frames are supported
irrespective of the MTU
setting. In 10G LAN Phy
to WAN Phy mode, MTU
can be set only to 1548
bytes.
Incoming MAC Address Sets the incoming MAC Value of MAC address. Value of MAC address.
address. Six bytes in hexadecimal Six bytes in hexadecimal
format. format.
639
Options
Flow Control (Only Enables/disables flow • ON (default)—Flow • ON (default)—Flow

when the card is in 10G control messaging with control is enabled. control is enabled.
Ethernet LAN Phy to its peer port. When
enabled, the port can • OFF—Flow control • OFF—Flow control
WAN Phy mode)
send and receive PAUSE is disabled. is disabled.
frames when buffer
congestion occurs. When
disabled, no PAUSE
frames are transmitted
and the PAUSE frames
received are discarded.
Client Distance (Only Sets the fiber distance • 10 km (default) • 10 km (default)
when the card is in between the client of
• 30 km • 30 km
10G Ethernet LAN Phy OTU2_XP card and
to WAN Phy mode) the LAN port that is
connected to the
OTU2_XP client port.
Squelch Hold Off Timer Sets the period in • Disable (0 ms) - • Disable (0 ms) -
milliseconds that the Default value Default value
client interface waits for
resolution of issues on the • 50 ms • 50 ms
trunk side. The client • 100 ms • 100 ms
squelching starts after this
period. • 250 ms • 250 ms
The user can configure the • 500 ms • 500 ms
squelch hold off timer in
CTC only under the
• The card must be
configured in TXP or
MXP operating
modes.
• The client payload
must be 10GE or
100GE.
• The Squelch
drop-down in CTC
must be set to
Squelch.
Step 4 Click Apply.

640

the OTU2_XP card.
Procedure
you want to change the section trace settings.
Table 238: OTU2_XP Section Trace Settings
Options
Port Sets the port number. • 1-1 (OC192) • 1-1 (STM-64)

• 2-1 (OC192) • 2-1 (STM-64)
• 3-1 (OC192) • 3-1 (STM-64)
• 4-1 (OC192) • 4-1 (STM-64)

641
Options
Disable AIS/RDI on If a TIM on Section Checked (AIS/RDI Checked (AIS/RDI

TIM-S overhead alarm arises on TIM-S is on TIM-S is
because of a J0 overhead disabled) disabled)
Unchecked (AIS/RDI Unchecked (AIS/RDI
on TIM-S is not on TIM-S is not
downstream nodes if this
box is checked. disabled) disabled)
This is a display-only
parameter under the
• Received Trace
Mode is Off/None
• Termination Mode is
set to Transparent or
Section (see the
DLP-G453 Changing
the OTU2_XP Card
Settings task).
Transmit Section Trace Sets the trace string size. • 1 byte 1 byte
String Size
• 16 byte 16 byte
right to change the
display mode. Click Hex
hexadecimal (button
changes to ASCII); click
ASCII to change the
display to ASCII (button
changes to Hex).
642
Options
can click the button on the
right to change the
hexadecimal (button
ASCII to change the
changes to Hex).
Refresh to manually
check box to
automatically refresh the
display every 5 seconds.

5 seconds.
Step 4 Click Apply.

Purpose This task changes the line threshold settings for the
OTU2_XP card carrying SONET or SDH payload.
643
Procedure
you want to change the line threshold settings.
Note If you have enabled 10G Ethernet LAN Phy to WAN Phy on the OTU2_XP card, the STS option
is automatically enabled. Only near end STS thresholds are supported. No STS thresholds are
support for Far End.
Step 3 Modify any of the OTU2_XP card path threshold settings on a LAN Phy to WAN Phy mode.
Table 239: OTU2_XP Card Path Threshold Settings on a 10G Ethernet LAN Phy to WAN Phy Mode
Options
Port (Display only) Port • Ports 3-1 (Trunk), • Port 3-1 (Trunk),
number. STS-1 VC4-1
• Ports 4-1 (Trunk), • Port 4-1 (Trunk),
STS-1 VC4-1
Step 4 Modify any of the OTU2_XP Card Line Threshold settings described in table.
Table 240: OTU2_XP Card Line Threshold Settings
Options
Port (Display only) Port • 1-1 (OC192) • 1-1 (STM-64)
number
• 2-1 (OC192) • 2-1 (STM-64)
• 3-1 (OC192) • 3-1 (STM-64)
• 4-1 (OC192) • 4-1 (STM-64)
644
Options
CV Coding violations Numeric. Threshold Numeric. Threshold

• Types—(Near end Types—(Near end
only) Line or Section only) Multiplex
Section or
Choose an option in each Regeneration Section
category and click
Refresh.

Section or
category and click
Refresh.
645
Options

Section or
category and click
Refresh.
FC (Line or Multiplex Section Numeric. Threshold Numeric. Threshold

only) Failure count display options include: display options include:
Section or
category and click
Refresh.
646
Options

Section or
category and click
Refresh.
Step 5 Click Apply.


Purpose This task provisions the OTU2_XP port alarm and
threshold crossing alert (TCA) thresholds.
Procedure
you want to change the trunk port alarm and TCA settings.
Step 3 Under Types, verify that the TCA radio button is checked. If not, select it, then click Refresh.
Step 4 Refer to table to provision the port TCA thresholds for RX Power High, RX Power Low, TX Power High,
and TX Power Low.
647
Table 241: OTU2_XP Port TCA Thresholds
Port TCA RX TCA RX TCA TX TCA TX

1-1 (OC-192/10G 1.0 dBm –14.0 dBm 5.0 dBm –12.0 dBm
Ethernet WAN
Phy/10G Ethernet
LAN Phy/10G
FC/IB_5G)
Ethernet WAN
Phy/10G Ethernet
LAN Phy/10G
FC/IB_5G)
Ethernet WAN
Phy/10G Ethernet
LAN Phy/10G
FC/IB_5G)
Ethernet WAN
Phy/10G Ethernet
LAN Phy/10G
FC/IB_5G)
Step 5 Click Apply.

Step 7 Refer to table to provision the port alarm thresholds for RX Power High, RX Power Low, TX Power
High, and TX Power Low.
648
Table 242: OTU2_XP Port Alarm Thresholds
Port Alarm RX Alarm RX Alarm TX Alarm TX

Ethernet WAN
Phy/10G Ethernet
LAN Phy/10G
FC/IB_5G)
Ethernet WAN
Phy/10G Ethernet
LAN Phy/10G
FC/IB_5G)
Ethernet WAN
Phy/10G Ethernet
LAN Phy/10G
FC/IB_5G)
Ethernet WAN
Phy/10G Ethernet
LAN Phy/10G
FC/IB_5G)
Step 8 Click Apply.


OTU2_XP card carrying the 10G Ethernet or 10G FC
payloads.
649
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the OTU2_XP card where you
want to change the line threshold in the card view.
Step 5 From the Variable drop-down list, choose an Ethernet variable.
Table 243: OTU2_XP Card 10G Ethernet Variables
rxTotalPkts Total number of received packets. rxTotalPkts

increments for 10G FC payload packets with FCS
errors. However, 10G Ethernet LAN Phy payload
packets with CRC errors are not counted.
ifInMulticastPkts Number of multicast frames received error free.
ifInBroadcastPkts Number of packets, delivered by a sublayer to an

higher sublayer, that were addressed to a broadcast
address at this sublayer.

protocol.
dot3StatsFCSErrors Number of frames with frame check errors, that is,

there is an integral number of octets, but an incorrect
Frame Check Sequence (FCS).


650


octets).

FCS octets).

FCS octets).

FCS octets).

FCS octets).


address.
etherStatsOversizePkts Total number of packets received that were longer


FCS octets), and had either a bad FCS with an integral
non-integral number of octets (Alignment Error).

packets) received on the network (excluding framing
bits but including FCS octets).
651
rxControlFrames Number of MAC control frames passed by the MAC

sublayer to the MAC control sublayer.
Table 244: OTU2_XP Card 10G FC Variables

mediaIndStatsRxFramesTruncated Total number of fiber channel frames received that

are less than the minimum 36-byte frame. This is
inclusive of header, SOF, EOF, and CRC with no data
bytes.
mediaIndStatsRxFramesTooLong Total number of fiber channel frames received that

exceed the maximum 2148-byte frame. This is
inclusive of header, SOF, EOF, CRC, and data bytes.
mediaIndStatsRxFramesBadCRC Total number of fiber channel frames received with

CRC errors.
ifInDiscards The number of inbound packets, which were chosen

detected to prevent their being delivered to a
higher-layer protocol. One possible reason for
discarding such a packet could be to free up buffer
1 17
space.
1
1
1
transmitPauseFrames Number of transmitted pause frames.
1
txTotalPkts Total number of transmit packets.
This variable is supported when the 10G Ethernet LAN Phy to WAN Phy mode is enabled on
the OTU2_XP card.
Step 6 From the Alarm Type drop-down list, choose the event triggers. The available options are rising
threshold, falling threshold, or rising and falling thresholds.
Step 7 From the Sample Type drop-down list, choose either Relative or Absolute. Relative restricts the
threshold to use the number of occurrences in the user-set sample period. Absolute sets the threshold to
use the total number of occurrences, regardless of time period.
Step 8 Enter an appropriate number of seconds for the Sample Period.
Step 9 Enter in the appropriate number of occurrences for the Rising Threshold.
652
For a rising type of alarm, the measured value must move from below the falling threshold to above the
rising threshold. For example, if a network is running below a rising threshold of 1000 collisions every 15
seconds and a problem causes 1001 collisions in 15 seconds, the excess occurrences trigger an alarm.
Step 11 Click OK.


Purpose This task changes the OTN line settings for the
OTU2_XP card.
Procedure
you want to change the OTN settings.
Step 2 Click the Provisioning > OTN tabs. Then click one of the following subtabs: OTN Lines, ITU-
T G.709 Thresholds, FEC Thresholds, Trail Trace Identifier, or Proactive Protection Regen.
Note You must modify Near End and Far End independently, 15 Min and 1 Day independently, and
SM and PM independently. To do so, select the appropriate radio button and click Refresh.
The following table describes the values on the Provisioning > OTN > OTN Lines tabs.
653
Table 245: OTU2_XP Card OTN Lines Settings

Port (Display only) Displays the port —
ITU-T G.709 OTN Sets the OTN lines according to Enable

ITU-T G.709. Check the box to
Disable
enable.
FEC Sets the OTN lines FEC mode. Disable—FEC is off.

Enhanced FEC mode can be
Standard—Standard FEC is
enabled to provide greater range
and lower bit error rate. on.
Enhanced—Enhanced FEC is
on.

rate.
• 1E-6
• 1E-7
• 1E-8
• 1E-9
SF BER (Display only) Indicates the signal 1E-5

No Fixed Stuff Sets the insertion of stuffing bytes. Disable

This parameter only applies to 10G
Enable
Ethernet LAN Phy signals in
transponder card configuration.
This is a display-only parameter for
all other card configurations.
When the “No Fixed Stuff”
parameter is disabled, the bit rate
is 11.09 Gbps.
When the “No Fixed Stuff”
parameter is enabled, the bit rate is
11.05 Gbps.
The following table describes the values on the Provisioning > OTN > ITU-T G.709 Thresholds tab.
Table 246: OTU2_XP Card ITU-T G.709 Threshold Settings

654

ES Severely errored seconds. Two Numeric. Threshold display
types of thresholds can be asserted. options include:
Selecting the SM (OTUk) radio Direction—Near End or Far
button selects FEC, overhead
End
management, and PM using OTUk.
Selecting the PM radio button Interval—15 Min (minutes) or
selects path PM using ODUk. 1 day
(ODUk)

ITU-T G.709 optical
order of k overhead
frame used for
management and
performance
is the ITU-T G.709
order of k overhead
performance
monitoring.
SES Severely errored seconds Numeric. Threshold display options

include:
End
1 day
(ODUk)

and click Refresh.
655

UAS Unavailable seconds Numeric. Threshold display
options include:
End
1 day
(ODUk)

and click Refresh.
BBE Background block errors Numeric. Threshold display
options include:
End
1 day
(ODUk)

and click Refresh.
FC Failure counter Numeric. Threshold display
options include:
End
1 day
(ODUk)

and click Refresh.
The following table describes the values on the Provisioning > OTNFEC Thresholds tab.
Table 247: OTU2_XP Card FEC Threshold Settings

656

Bit Errors Corrected Displays the number of bit errors Numeric display. Can be set for
corrected during the selected time 15-minute or one-day intervals.
period.
Uncorrectable Words Displays the number of Numeric display. Can be set for
uncorrectable words in the selected 15-minute or one-day intervals.
time period.
The following table describes the values on the Provisioning > OTN > Trail Trace Identifier tab.
Note You cannot change the Path Trail Trace Identifier settings when the OTU2_XP card is in the
Standard Regen mode, and if the ODU transparency is set to “Transparent Standard Use”. You
can change the Path Trail Trace Identifier settings when the OTU2_XP card is in the Standard
Regen mode, and if the ODU transparency is set to “Cisco Extended Use”.
Table 248: OTU2_XP Card Trail Trace Identifier Settings

Port Sets the port number. —

Path

Manual

Indication (FDI) signal is sent to not enabled)
is checked.
to Hex).
657

changes to Hex).
panel updated.

The following table describes the values on the Provisioning > OTN > Proactive Protection Regen tabs.
Note Proactive protection regen is supported on ports of OTU2_XP only in Standard Regen and
Enhanced FEC mode.
Table 249: OTU2_XP Card Proactive Protection Regen Settings

number and name (optional).
Trigger threshold Sets the maximum BER threshold • 1E-3

to trigger proactive protection.
• 9E-4 to 1E-4
• 9E-5 to 1E-5
• 9E-6 to 1E-6
• 9E-7 to 1E-7
658
Trigger window (ms) Sets the duration for which BER is Time in milliseconds.
monitored before triggering the
proactive protection.
The trigger window value must be
a multiple of:
• 10 ms for trigger thresholds
between 1E-3 and 6E-6
• 100 ms for trigger threshold
between 5E-6 to 1E-7
Trigger window must be less than

or equal to 10000 ms.
Revert Threshold Sets the revert threshold value of • 1E-4

BER.
• 9E-5 to 1E-5
Note Revert Threshold
settings must be less • 9E-6 to 1E-6
than the Trigger • 9E-7 to 1E-7
Threshold values.
• 9E-8 to 5E-8
Revert window (ms) Sets the duration for which BER is Time in milliseconds.
monitored for settings that are less
than the revert threshold value
before which proactive protection
provided to the router is removed.
Revert Window value must be at
least 2000ms and a multiple of:
• 10ms for a Revert Threshold
of 1E-4 to 6E-7
• 100ms for a Revert Threshold
of 5E-7 to 5E-8.
The revert window must be less

than or equal to 10000ms.
Step 4 Click Apply.

659

Purpose This task changes the path trace settings for the
OTU2_XP card.
Procedure
you want to change the path trace settings.
Step 2 Click the Provisioning > Path > J1 Path Trace tabs.
Table 250: OTU2_XP Path Trace Settings
Options
Port Sets the port number. • 3-1 (OC192) • 3-1 (STM-64)

• 4-1 (OC192) • 4-1 (STM-64)

right to change the
hexadecimal (button
ASCII to change the
changes to Hex).
660
DLP-G524 Provisioning the OTU2_XP Path Settings for 10G Ethernet LAN Phy to WAN Phy Configuration
Options
can click the button on the
right to change the
hexadecimal (button
ASCII to change the
changes to Hex).
Refresh to manually
check box to
automatically refresh the

5 seconds.
Step 4 Click Apply.

DLP-G524 Provisioning the OTU2_XP Path Settings for 10G

Ethernet LAN Phy to WAN Phy Configuration
Purpose This task changes the path settings of the OTU2_XP
card for 10G Ethernet LAN Phy to WAN Phy
configuration.
661
NTP-G162 Changing the ALS Maintenance Settings
Procedure
you want to change the path settings.
Step 2 Click the Provisioning > Path > SONET/SDH tab. You can now provision the SF BER and SD BER values.
Step 3 Modify any of the OTU2_XP path settings described in table.
Table 251: OTU2_XP Path Settings
Options
Port Sets the port number. • Port 3-1 (trunk) • Port 3-1 (trunk)
• Port 4-1 trunk • Port 4-1 trunk
SF BER Sets the signal fail bit • 1E-3 • 1E-3

error rate (SONET
[ANSI] or SDH [ETSI]). • 1E-4 • 1E-4
• 1E-5 • 1E-5
SD BER Sets the signal degrade bit • 1E-5 • 1E-5

error rate (SONET
[ANSI] or SDH [ETSI]). • 1E-6 • 1E-6
• 1E-7 • 1E-7
• 1E-8 • 1E-8
• 1E-9 • 1E-9
Step 4 Click Apply.


Purpose This procedure changes the ALS maintenance settings
for the cards.
The automatic laser shutdown (ALS) function is
normally disabled. Enable ALS only when the cards
are directly connected to each other.
662
Note ALS is applicable only for OCn and OTN payloads.
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf mode), double-click the card where you want to
change the ALS maintenance settings.
Step 2 Click the Maintenance > ALS tabs.
Step 3 Modify any of the settings described in table. The provisionable parameters are listed in the Options column
in the table.
Table 252: ALS Settings

name.
ALS Mode Automatic laser shutdown. ALS From the drop-down list,
provides the ability to shut down choose one of the following:
the laser when the card detects an Disable—Deactivates ALS.
LOS or LOS-P.
Auto Restart—(Default) ALS is
active. The power is
automatically shut down when
needed and automatically tries
to restart using a probe pulse
until the cause of the failure is
repaired.
Manual Restart
Manual Restart for Test
OSRI Optical safety remote interlock. From the drop-down list,

When set to On, the OSC TX choose one of the following:
output power is shut down. On
Off
663
NTP-G302 Configuring Loopback on a Card

Recovery Pulse Duration (Display only for Manual Restart —
ALS mode) Displays the duration
of the optical power pulse that
begins when the card restarts.
The Recovery Pulse Duration value
in Manual Restart ALS mode is
always 2.5 seconds. From R10.9,
this value cannot be changed by
CTC.
Currently Shutdown (Display only) Displays the current —

status of the laser.
Request Laser Restart If checked, allows you to restart the Checked or unchecked
laser for maintenance.
Recovery Pulse Interval (Display only) Displays the interval —

between optical power pulses.
Step 4 Click Apply. If the change affects traffic, a warning message displays. Click Yes to complete the change.

Purpose This procedure configures or clears terminal or facility
loopback on the 100G-LC-C, 10x10G-LC, CFP-LC,
MR-MXP, 100G-CK-C, 100G-ME-C, 100ME-CKC,
100GS-CK-LC, 200G-CK-LC, 400G-XP-LC, and
WSE cards. The loopback on the CFP-LC card can
be configured on the backplane of the peer
100G-LC-C card. The facility loopback (drop) can be
configured on the 100G-LC-C, CFP-LC, and
100G-CK-C cards.
Note In WSE card, do not enable encryption
with far-end client loop back. Enabling
encryption with far-ed client loopback will
result in sync loss until the key is
exchanged. The key is exchanged only
after the ODUk-AIS on the trunk is
cleared.
664
Caution This procedure is traffic-affecting.
Procedure
change the loopback settings.
Step 2 Click Maintenance > Loopback tab.
Note In WSE card, do not enable encryption with far-end client loopback. This affects the traffic.
Step 3 Modify any of the settings described in table. The provisionable parameters are listed in the Options column
of the table.
Note Before you configure a loopback, the port admin state must be set to OOS,MT(ANSI) or
Locked,maintenance (ETSI).
Table 253: Loopback Settings

Port (Display only) Name of the port. —
OOS,MT (ANSI) or
administrative states, see the Locked,maintenance (ETSI)
Administrative and Service States OOS,DSBLD (ANSI) or
document. Locked,disabled (ETSI)
IS,AINS (ANSI) or
Unlocked,AutomaticInService
(ETSI)
665
NTP-G299 Configuring Backplane Loopback on a Card

format: Primary State-Primary State Unlocked-disabled,
OOS-MA,MT (ANSI) or
(ETSI)
Loopback Configures or clears a port for a None—Clears loopback

terminal (inward), facility (line),
Terminal (Inward)
facility loopback (drop), or terminal
loopback (drop) on the required Facility (Line)
port.
Facility Loopback (Drop)
Terminal Loopback (Drop)
Step 4 Click Apply.


Purpose This procedure configures or clears the backplane
terminal or facility loopback on the 100G-LC-C,
10x10G-LC, CFP-LC, 100G-CK-C, 100G-ME-C,
100ME-CKC, and 100GS-CK-LC cards. The
backplane facility (drop) loopback can be configured
on the 100G-LC-C, CFP-LC, and 100G-CK-C cards.
Note The loopback on the CFP-LC card can be
configured on the backplane of the peer
100G-LC-C card.
666
Procedure
change the backplane loopback settings. The card view appears.
Step 2 Click Maintenance > Card tabs.
Step 3 Modify any of the settings described in the table. The provisionable parameters are listed in the Options
column in the table.
Note Before you configure a backplane loopback, the port admin state must be set to OOS,MT(ANSI)
or Locked,maintenance (ETSI).
Table 254: Backplane Loopback Settings

OOS,MT (ANSI) or
administrative states, see the Locked,maintenance (ETSI)
Administrative and Service States
document.

OOS-MA,MT (ANSI) or
Locked-
more information about service
states, see the Administrative and
Loopback Configures or clears backplane None

terminal (Inward), facility (Line),or
Backplane Facility
facility (Drop) loopback on the
card. You can configure the Backplane Terminal
backplane loopback only if the card
is removed from service. Backplane Facility (Drop)
Step 4 Click Apply.
667
NTP-G192 Forcing FPGA Update
NTP-G192 Forcing FPGA Update

Purpose This procedure forces an upgrade of the FPGA image
on the MXP_MR_10DME_C and
MXP_MR_10DME_L cards.
Procedure
Step 1 Perform step 1 only if you are updating the node software, else proceed to step 2.
Close the CTC window, if open.
Delete the CTC Cache from the CTC Launcher browser window.
Close the CTC Launcher browser window.
Relaunch the CTC Launcher browser window.
Step 2 In node view (single-shelf mode) or shelf view (multishelf mode), double-click the MXP_MR_10DME_C
or MXP_MR_10DME_L card to be upgraded.
Step 3 For all ports being provisioned on the card, click the Provisioning > Line tabs.
Click the Admin State table cell and choose OOS,DSBLD (ANSI) or Locked,Disabled (ETSI).
Step 5 Change the Card Mode as needed:
FC-GE_ISC—Choose this option if you will provision any of the following PPM port rates: FC1G
(Ports 1-1 through 4-1), FC2G (Ports 1-1 and 3-1 only), FICON1G (Ports 1-1 through 4-1), FICON2G
(Ports 1-1 and 3-1 only), ONE_GE (Ports 1-1 through 4-1), ISC3 COMPAT (Ports 1-1 through 4-1),
ISC3 PEER 1G (Ports 1-1 through 4-1), and ISC3 PEER 2G (Ports 1-1 and 3-1 only).
FC4G—Choose this option if you will provision an FC4G or FICON4G PPM (Port 1-1 only).
Step 6 Click the Force FPGA Update button. This upgrades the FPGA image in the MXP_MR_10DME_C or
MXP_MR_10DME_L card, as appropriate. The MXP_MR_10DME_C or MXP_MR_10DME_L card
reboots and the FPGA now contains the updated image.
Step 7 For all ports being provisioned on the card, click the Provisioning > Line tabs.
668
NTP-G196 Forcing FPGA Update on a Card in Protection Group
Click the Admin State table cell and choose IS (ANSI) or Unlocked (ETSI).
NTP-G196 Forcing FPGA Update on a Card in Protection Group

Purpose This procedure forces an upgrade of the FPGA image
on the MXP_MR_10DME_C and
MXP_MR_10DME_L cards when the card is part of
a protection group.
This procedure applies to a near-end node that has
two MXP_MR_10DME_C or MXP_MR_10DME_L
cards, one card acting as the working card and the
other as the protect card. The far-end node has a
similar configuration. The near-end working card
trunk port is connected to the far-end working card
trunk port. The near-end protect card trunk port is
connected to the far-end protect card trunk port.
Procedure
Step 1 Perform step 1 only if you are updating the node software. Else, proceed to step 2.
a) Close the CTC window, if open.
b) Delete the CTC Cache from the CTC Launcher browser window.
c) Close the CTC Launcher browser window.
d) Relaunch the CTC Launcher browser window.
Step 2 Ensure traffic is running on the near-end and far-end working cards for each protection group on the
MXP_MR_10DME_C or MXP_MR_10DME_L card.
Step 3 In node view (single-node mode) or multishelf view (multishelf mode), click the Provisioning > Protection
tab.
Step 4 For each protection group, verify that the working card client port is reported as working/active and the protect
card client port is reported as protect/standby.
Step 5 Repeat step 6 and step 7 for the far-end node.
669
NTP-G232 Enabling Error Decorrelator
Step 6 For each protection group on the near-end and far-end nodes, complete the DLP-G182 Apply a Lockout task
to prevent traffic from switching to the protect card.
Step 7 At the near-end and far-end nodes, complete the NTP-G192 Forcing FPGA Update task to force an upgrade
of the FPGA image on the protect card.
Step 8 For each protection group on the near-end and far-end nodes, complete the DLP-G183 Clear a Lock-On or
Lockout task to remove a lockout and return a protection group to its usual switching method.
Step 9 For each protection group on the near-end and far-end nodes, complete the DLP-G179 Apply a Force Y-Cable
or Splitter Protection Switch task to move traffic from the working to the protect card.
Step 10 At the near-end and far-end nodes, complete the NTP-G192 Forcing FPGA Update task to force an upgrade
of the FPGA image on the working card.
Step 11 For each protection group on the near-end and far-end nodes, complete the DLP-G180 Clear a Manual or
Force Y-Cable or Splitter Protection Switch task to clear a Force protection switch on the working card. If
the protection group is revertive, this operation causes the traffic to revert to the working card. If the protection
group is non-revertive, this operation causes the traffic to remain on the protect card.
NTP-G232 Enabling Error Decorrelator

Purpose This task enables error decorrelator on a
TXP_MR_10EX_C, MXP_2.5G_10EX_C, or
MXP_MR_10DMEX_C card.
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the TXP_MR_10EX_C,
MXP_2.5G_10EX_C, or MXP_MR_10DMEX_C card where you want to enable error decorrelator.
Step 2 Click the Provisioning > Line > Error Decorrelator Settings tabs.
Step 3 In the Error Decorrelator Settings area, select Enable.
Note To inter-operate with other cards, disable the error decorrelator. Click the Provisioning > Line
> Error Decorrelator Settings tabs and then select Disable.
670
NTP-G315 Enabling the Wavelength Drifted Channel Automatic Shutdown Feature
NTP-G315 Enabling the Wavelength Drifted Channel

Automatic Shutdown Feature
Purpose This procedure allows you to enable or disable the
wavelength drifted channel automatic shutdown
feature for 40-SMR1-C, 40-SMR2-C, 80-WXC-C,
40-WXC-C, and 40-WSS-C cards.
Procedure
Step 1 In the node view (single-shelf mode) or multishelf view (multishelf mode), click the Provisioning >
Defaults tabs. The Node Defaults page opens.
Step 2 Select the card from the Defaults Selector pane where you want to enable or disable the wavelength drifted
channel automatic shutdown feature.
Step 3 Select the <card name>.config.card.WavelengthDrift from the Default Name column. Choose Disable
or Enable from the Default Value drop-down list for the selected card.
For example, if you select 40-SMR2-C card from the Defaults Selector folder, the Default Name column
reads “40-SMR2-C.config.card.WavelengthDrift”.
Step 4 Click Apply to save changes.
NTP-G316 Enabling REP and FAPS on the Same Port

Purpose This task allows you enable REP and FAPS on the
same port for the GE_XP and 10GE_XP cards. You
can configure REP and FAPS on port 22 and 21 for
GE_XP cards, and port 4 and 3 for 10GE_XP cards.
The FAPS master node on the edge ring should never
be the node that has a common FAPS and REP port.
671
NTP-G321 Provisioning Multiple Operating Modes
Procedure
Step 1 To enable REP, complete the following procedures:

Step 2 To enable FAPS, complete the DLP-G381 Provisioning Layer 2 Protection Settings
NTP-G321 Provisioning Multiple Operating Modes

Purpose This procedure enables you to provision multiple
operating modes on the AR_MXP, AR_XP, or
AR_XPE cards.

• DLP-G726 Preprovisioning a Multirate PPM
on page 321
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the AR_MXP, AR_XP,
or AR_XPE card where you want to provision an operating mode. The card view appears.
Step 3 In the Card tab, click Create.
Step 4 From the Card Config Rate Selection section, select Low Rate Mode or High Rate Mode.
672
NTP-G322 Modifying the Card Line Settings and PM Parameter Thresholds
Step 5 In the Card Config Selection section:

Choose the Operating Mode from the drop-down list.
The Operating Mode options vary depending on the Card Type (AR_MXP, AR_XP, or AR_XPE)
and Card Config Rate Selection.
For MXP_DME and MXPP_DME card modes, choose the Client Trunk Mapping from the drop-down
list. For other card modes, CTC automatically selects the client trunk mapping.
Step 6 Click Next.
Step 7 Select the appropriate trunk port that is available and click Next.
Step 8 Select the appropriate client port that is available and click Finish.
The selected operating mode is provisioned on the AR_MXP, AR_XP, or AR_XPE card.
Note When you want to upgrade the FPGA image on the AR_MXP, AR_XP, or AR_XPE card, click
the FPGA/FIRMWARE Upgrade button. This upgrades the FPGA image on the AR_MXP,
AR_XP, or AR_XPE card as appropriate, without the need of upgrading the whole network.
NTP-G322 Modifying the Card Line Settings and PM

Purpose This procedure changes the line and PM parameter
threshold settings of the AR_MXP, AR_XP, or
AR_XPE cards.

Muxponder Cards
necessary)
on page 321
673
DLP-G695 Changing the Card Line Settings
Procedure
settings.
DLP-G698 Changing the AR_MXP, AR_XP, or AR_XPE Card Section Trace Settings
DLP-G699 Enabling Auto-sensing for AR_MXP, AR_XP, or AR_XPE Cards
DLP-G701 Changing the AR_MXP, AR_XP, or AR_XPE Card Line RMON Thresholds
DLP-G702 Provisioning the AR_MXP, AR_XP, or AR_XPE Card with Trunk Port Alarm and TCA
Thresholds
DLP-G703 Provisioning the AR_MXP, AR_XP, or AR_XPE Card Client Port Alarm and TCA Thresholds
DLP-G704 Changing the AR_MXP, AR_XP, or AR_XPE Card OTN Settings

DLP-G734 Viewing the Mapping of ODU Object with Client Port

Purpose This task changes the line settings of the AR_MXP,
AR_XP, or AR_XPE cards.
Procedure
or AR_XPE card where you want to change the line settings.
Step 2 Click the Provisioning > Line > Ports tabs. Tabs and parameter selections vary according to PPM provisioning.
Step 3 Modify any of the line settings in the Ports tab as described in table.
674
Table 255: AR_MXP, AR_XP, or AR_XPE Card Line Settings

Port (Display only) Displays the port 1 through 10
number.
Port Name Assigns a logical name for the User-defined. Name can be up
specified port. to 80 alphanumeric or special
characters, or both. Blank by
default.
See, DLP-G104 Assigning a
Name to a Port
Note You can provision a
string (port name) for
each fiber
channel/FICON interface
on the AR_MXP,
AR_XP, or AR_XPE
card, which allows the
MDS Fabric Manager to
create a link association
between that SAN port
and a SAN port on a
OOS,DSBLD (ANSI) or
IS,AINS (ANSI) or
(ETSI)

gives the overall condition of the OOS-AU,AINS (ANSI) or
Unlocked-disabled,
automaticInService (ETSI)
OOS-MA,MT (ANSI) or
Locked-
675

ALS Mode Sets the ALS function mode. Disabled (default)— ALS is
off; the laser is not
Manual Restart— ALS is on;
loss of signal (LOS) occurs.
However, the laser must be
manually restarted when
conditions that caused the
outage are resolved.
for testing.
AINS Soak Sets the automatic in-service soak Duration of valid input signal, in
period. Double-click the time and hh.mm format, after which the
use the up and down arrows to card state changes to in service
change settings. (IS) automatically.
increments.
676

Reach Sets the optical reach distance of The reach distances that appear in
the client port. the drop-down list depend on the
card:
Autoprovision—The system
automatically provisions the
reach from the pluggable
port module (PPM) reach
value on the hardware.
I1—Intermediate reach
S1—Short reach, up to 15-km
distance
S2—Short reach up to 40-km
distance
L1—long reach, up to 40-km
distance
distance
distance
CWDM— CWDM Reach
MM—
ULH—Ultra long-haul (ULH)
DWDM—DWDM Reach
Wavelength Displays the wavelength of the First Tunable Wavelength

client port.
Further wavelengths:
850 nm through 1561.83
nm
100-GHz ITU spacing
CWDM spacing
Fault Signalling Shuts down the far-end laser in G AIS/Send Local Fault
Squelch/Laser-Off
(Squelch does not apply to ISC
COMPACT payloads.) NOS
None
677
DLP-G696 Changing the AR_MXP, AR_XP, or AR_XPE Card Ethernet Settings
Termination Mode Sets the mode of operation. (This • Transparent

option is only available for
SONET/SDH payloads).
Step 4 Click Apply.


Purpose This task changes the Ethernet settings of the
AR_MXP, AR_XP, or AR_XPE cards.
Procedure
or AR_XPE card where you want to change the Ethernet settings. The card view appears.
Step 3 Modify any of the Ethernet settings in the Ethernet tab as described in table. The parameters that appear
depend on the card mode.
Table 256: AR_MXP, AR_XP, and AR_XPE Card Ethernet Settings
Options
Port (Display only) Displays — —
the port number (n-n) and
rate.
Port Name (Display only) Displays — —

the port Name.
678
Options
MTU Sets the maximum size of Numeric. Default: 9700 Numeric. Default: 9700
the Ethernet frames
Range 64 to 9700 (for Range 64 to 9700 (for
accepted by the port. The R9.4 and later) R9.4 and later)
port must be in
OOS/locked state.
Speed Sets the expected speed of 100 Mbps for FE ports 100 Mbps for FE ports
the ports. and 1000 Mbps for GE and 1000 Mbps for GE
ports ports
Duplex (Display only) Displays Full Full

expected duplex
capability of ports.
Auto negotiation If checked, enables Checked or unchecked Checked or unchecked

autonegotiation on the
same port.
ProvidesSync Sets the ProvidesSync Checked or unchecked Checked or unchecked

card parameter. If
element (NE) timing
reference.
SyncMsgIn Sets the EnableSync card Checked or unchecked Checked or unchecked

parameter.
Enables synchronization
status messages (S1 byte),
which allow the node to
choose the best timing
source.
679
DLP-G697 Changing the AR_MXP, AR_XP, or AR_XPE Card SONET/SDH Settings
Options

• STU—Sync
synchronization
traceability unknown • ST2—Stratum 2 traceability unknown
(STU) value. If the node • TNC—Transit node • G812T—Transit
does not receive an SSM clock node clock traceable
signal, it defaults to STU.
• ST3E—Stratum 3E • G812L—Local node
clock traceable
• ST3—Stratum 3
• SETS—Synchronous
• SMC—SONET
equipment
minimum clock
• DUS—Do not use
• ST4—Stratum 4 for timing
• DUS—Do not use synchronization
for timing
synchronization
• RES—Reserved;
quality level set by
user
Termination Mode (Display-only for
Standard Regeneration — —
and Enhanced FEC card
configurations) Sets the
mode of operation.
Send DoNotUse When checked, sends a Checked or unchecked Checked or unchecked

DUS message on the S1
byte.
ESMC Enable Enables the timing to be Checked or unchecked Checked or unchecked

taken from the Ethernet
port.
Video Type Video — —
DLP-G697 Changing theAR_MXP,AR_XP,orAR_XPECardSONET/SDH Settings

Purpose This task changes the SONET /SDH settings of the
680
Procedure
or AR_XPE card where you want to change the SONET (OC-192)/SDH (STM-64) settings.
Step 2 Click the Provisioning > Line > SONET (ANSI) or SDH (ETSI) tabs. The tabs and parameter selections
vary according to PPM provisioning.
Step 3 Modify any of the settings as described in table.
Table 257: AR_MXP, AR_XP, or AR_XPE Card SONET/SDH Settings

number.
Port Name Assign a name for the specified User-defined. Name can be up
port. to 80 alphanumeric or special
default.
DLP-G104 Assigning a Name to
a Port
IS,AINS (ANSI) or
administrative states, see the Unlocked,automaticInService
OOS,MT (ANSI) or
681

OOS-MA,MT (ANSI) or
(ETSI)
18
1E-4
1E-5
SD BER1 Sets the signal degrade bit error 1E-5

rate.
1E-6
1E-7
1E-8
1E-9
Type Sets the optical transport type. • SONET (ANSI)

• SDH (ETSI)
682

ALS Mode Sets the ALS function mode. The Disabled (default)—ALS is
DWDM transmitter supports ALS off; the laser is not
according to ITU-T G.644 (06/99). automatically shut down
ALS can be disabled or enabled for when traffic outage or loss of
one of the three mode options. signal (LOS) occurs.
Auto Restart—ALS is on; the
laser automatically shuts down
signal (LOS) occurs. It
the conditions that caused the
loss of signal (LOS) occurs.
However, the laser must be
manually restarted when
conditions that caused the
for testing.
use the up and down arrows to the card state changes to in
change settings. service (IS) automatically.
increments.

provisioned as a NE timing
reference.

timing source.
683
Admin SSM In Overrides the synchronization STU

status message (SSM) and the
synchronization traceability
unknown (STU) value. If the node
does not receive an SSM signal, it
defaults to STU.
Reach Sets the optical reach distance of The reach distances that appear in
the client port. the drop-down list depend on the
card:
• Autoprovision—The system
to automatically provision the
module (PPM) reach value on
the hardware.
• I1/IR1—Intermediate Reach
• S1/SR1—Intermediate reach,
• S2/SR2—Intermediate reach
• L1/LR1—long reach, up to
40-km distance
80-km distance
80-km distance
• CWDM—CWDM Reach
• MM
• SR—Short Reach
• ULH—Ultra long-haul (ULH)
• DWDM—DWDM Reach

client port.
• Further wavelengths:
• 850 nm through 1561.83
nm
• 100-GHz ITU spacing
• CWDM spacing
684
SF BER and SD BER thresholds apply only to trunk ports.

Step 4 Click Apply.
DLP-G698 Changing the AR_MXP, AR_XP, or AR_XPE Card

Section Trace Settings
Procedure
or AR_XPE card where you want to change the section trace settings.
PPM provisioning.
Step 3 Modify any of the settings in the Section Trace tab as described in the table.
Table 258: AR_MXP, AR_XP, or AR_XPE Card Line Section Trace Settings

Port (Display only) Displays the port Client Ports (1-8)
number.

Manual
Disable AIS/RDI on TIM-S If a TIM on section overhead alarm Checked (AIS/RDI on TIM-S
arises because of a J0 overhead is disabled)
checked.
685

• 16 byte
Transmit Displays the current transmit string String of trace string size
or sets a new transmit string. Click
the button on the right to change
the display. Its title changes, based
on the current display mode. Click
Hex to change the display to
to Hex).
Note For OCn and OTU
traces, the junk squares
appear in the New
Transmit String field
when you click the
default button. Ignore
the junk squares that
appear in the New
Transmit String field.
Expected Displays the current expected string String of trace string size
or sets a new expected string. Click
to Hex).
Note For OCn and OTU
traces, the junk squares
appear in the New
Expected String field
when you click the
default button. Ignore
the junk squares that
appear in the New
Expected String field.
686
select the Auto-refresh every 5 sec
updated.
Auto-refresh If checked, automatically refreshes Checked or unchecked (default)

Step 4 Click Apply.


Purpose This task enables the auto sensing for AR_MXP,
Procedure
or AR_XPE card where you want to enable auto sensing.
Step 2 Click the Provisioning > Line > Auto Ports tabs. Tabs and parameter selections vary according to
PPM provisioning.
Step 3 Modify any of the settings in the Auto Ports tab as described in table.
Table 259: AR_MXP, AR_XP, or AR_XPE Auto Sensing Settings

Port (Display only) Displays the port Client Ports (1-8)
number.
Auto Sensing If checked, enables auto sensing. Checked or Unchecked
687
DLP-G700 Changing the AR_MXP, AR_XP, or AR_XPE Card SONET/SDH Line Thresholds
Actual Port Type Displays the auto-sensed signal —

type.
DLP-G700 Changing the AR_MXP, AR_XP, or AR_XPE Card

SONET/SDH Line Thresholds
Purpose This task changes the SONET/SDH line threshold
settings of AR_MXP, AR_XP, or AR_XPE cards.
Procedure
or AR_XPE card where you want to change the SONET/SDH line threshold settings.
Step 3 Modify any of the settings as shown in table.
Table 260: AR_MXP, AR_XP, or AR_XPE Card SONET/SDH Line Threshold Settings
Parameter Description Options - ONS 15454 Options - ONS 15454 SDH

Port (Display only) Displays • Client Ports (1-8) • Client Ports (1-8)
the port number.
688

block.
or Far End
(minutes) or 1 day
Section or
(near end only)

category and click
Refresh.
or Far End
(minutes) or 1 day
• Types—Line or
Section (near end
only)

category and click
Refresh.

(near end only)
Refresh.
689

(near end only)
Refresh.
SEFS (Near End Section or — Numeric. Threshold
framing seconds
or Far End
(minutes) or 1 day
Section or
(near end only)

category and click
Refresh.
or Far End
(minutes) or 1 day
Section or
(near end only)

category and click
Refresh.
690

FC (Line or Multiplex Section Numeric. Threshold Numeric. Threshold
only) Failure count display options include: display options include:
(near end only)
Refresh.

(near end only)
Refresh.
Step 4 Click Apply.

DLP-G701 Changing the AR_MXP, AR_XP, or AR_XPE

Card Line RMON Thresholds
AR_MXP, AR_XP, or AR_XPE cards carrying
Ethernet, FC/FICON, or ISC/ISC3 payloads.
691
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the AR_MXP, AR_XP, or
AR_XPE card where you want to change the line RMON threshold settings in card view.
Step 4 From the Port drop-down list, choose the applicable port, either the payload port, for example “1-1 (ONE_GE)”,
or the equivalent ITU-T G.7041 GFP (Generic Frame Procedure) port.
Step 5 From the Variable drop-down list, choose an Ethernet, FC, FICON, or ISC variable. To change the values of
the variables, see the following tables.
Table 261: AR_MXP, AR_XP, or AR_XPE Card Ethernet Variables
ifInUcastPkts Number of packets delivered by this sublayer to a

higher sublayer that are not addressed to a multicast
or broadcast address.
ifInMulticastPkts Number of packets delivered by this sublayer to a

higher sublayer that are addressed to a multicast
address. For a MAC layer protocol, this includes both
group and functional addresses.
ifInBroadcastPkts Number of packets delivered by this sublayer to a

higher sublayer that are addressed to a broadcast
address.

IfOutUcastPkts Total count of good frames transmitted to a unicast

group destination address.
692
ifOutMulticastPkts Total number of packets that higher-level protocols

requested to be transmitted, which were addressed to
a multicast address at this sublayer. These include
packets that were discarded or not sent. For a MAC
layer protocol, this includes both group and functional
addresses.
ifOutBroadcastPkts Total number of packets that higher-level protocols

a broadcast address at this sublayer. These include
packets that were discarded or not sent.
dot3StatsFCSErrors Number of frames received on a particular interface

dot3StatsAlignmentErrors Total number of frames received on a particular

interface that are not an integral number of octets in
length and do not pass the FCS check. This counter
is only valid for FE modes of operation.
dot3StatsFrameTooLong Number of frames received on a particular interface

dot3StatsSymbolErrors Number of frames received on an associated RX_ER

assertion during a data reception error event (MII) or
data reception error event, or carrier extension error
(GMII) from the PCS.
dot3StatsLayer1Errors Number of Layer 1 errors as defined within the

• During Packet Reception—Layer 1 errors are
only counted one time per packet. The Layer 1
error is indicated as a direct result of a line side
protocol violation in which RX_DV is asserted.
This is an uncommon event from which may be
the reason why the device loses synchronization.
• During Interpacket Reception—The Layer 1 error
is indicated as a direct result of a line side
protocol violation in which RX_DV is
de-asserted. This is an uncommon event. The
Layer 1 error is also asserted on detection of a
False Carrier indication and is asserted on
detection of Erred byte (interpacket) signal
encoding. When the Layer 1 error is asserted
during inter-packet reception, it is only
statistically asserted in the vector.
693
dot3StatsLCVErrors Number of received line code violations at the PCS

layer.




octets).

FCS octets).

FCS octets).

FCS octets).

FCS octets).
694
etherStatsPkts1519toMaxSizeOctets Total number of packets (including bad packets)

received that were between 1519 and the maximum
frame size as programmed within the RMAC Max
Frame Length Configuration Register in length
octets).


address.

FCS octets) and were otherwise well-formed.


non-integral number of octets (Alignment Error).

bits, but including FCS octets).
etherStatsPkts1519tomaxOctets Total number of packets (including bad packets)

framing bits, but including FCS octets).
mediaIndStatsTXShortPkts Number of transmitted frames containing less than

the minimum permitted frame size as programmed
with the transmit MAC Min Frame Length
Configuration Register.
Table 262: AR_MXP, AR_XP, or AR_XPE FC/FICON Variables
695
mediaIndStatsRxFramesBadCRC Number of received data frames with payload CRC


mediaIndStatsRxLcvErrors Number of L1 line code violations received for lower

rate FC, which equate to invalid 8b10b ordered sets.
mediaIndStatsTxLcvErrors Number of L1 line code violations transmitted for

lower rate FC, which equate to invalid 8b10b ordered
sets.
rx8b10bWords Number of 8B/10B words received.
tx8b10bWords Number of 8B/10B words transmitted.
Table 263: AR_MXP, AR_XP, and AR_XPE ISC Variables
mediaIndStatsRxLcvErrors Number of L1 line code violations received for

constant bit rate protocols, which equate to invalid
8b10b ordered sets.
mediaIndStatsTxLcvErrors Number of L1 line code violations transmitted for

constant bit rate protocols, which equate to invalid
8b10b ordered sets.
Table 264: AR_MXP, AR_XP, and AR_XPE GFP RMON Variables
gfpStatsRxCRCErrors Total number of CRC errors with the receive

transparent GFP frame.

frame has multiple superblocks which each contain
fiber channel data.
gfpStatsCSFRaised Number of Rx client management frames with Client

Signal Fail indication.
gfpStatsLFDRaised Number of Core HEC CRC Multiple Bit Errors.

Note This count is only for cHEC multiple bit
error when in frame. It is a count of when
the state machine goes out of frame.
696
DLP-G702 Provisioning the AR_MXP, AR_XP, or AR_XPE Card with Trunk Port Alarm and TCA Thresholds
gfpStatscHecRxMBitErrors Number of received GFP frames with single bit errors

in the core header (these errors are uncorrectable).
gfpStatstHecRxMBitErrors Number of received GFP frames with single bit errors

in the tHec (these errors are uncorrectable).
The available options are Rising Threshold, Falling Threshold, and Both Rising and Falling Threshold.
Step 7 From the Sample Type drop-down list, choose either Relative or Absolute.
Relative restricts the threshold to use the number of occurrences in the user-set sample period. Absolute sets
the threshold to use the total number of occurrences, regardless of time period.
Step 8 Enter the appropriate number of seconds in the Sample Period field.
Step 9 Enter the appropriate number of occurrences in the Rising Threshold field.
Step 11 Click OK.

DLP-G702 Provisioning the AR_MXP, AR_XP, or AR_XPE Card

with Trunk Port Alarm and TCA Thresholds
Purpose This task provisions the AR_MXP, AR_XP, or
AR_XPE card with trunk port alarm and TCA
thresholds.
697
Procedure
AR_XPE card where you want to provision the trunk port alarm and TCA threshold settings.
Step 3 If TCA is not checked, check the TCA check box and then click Refresh. If it is checked, continue with
step 4.
Step 4 Verify if the trunk port (Port 9) TCA thresholds are set. Provision new thresholds as needed by double-
clicking the threshold value you want to change, deleting it, entering a new value, and pressing Enter.
Step 6 Verify if the trunk port (Port 9) Alarm thresholds are set. Provision new thresholds as needed by double-
clicking the threshold value you want to change, deleting it, entering a new value, and pressing Enter.
Step 7 Click Apply.
DLP-G703 Provisioning the AR_MXP, AR_XP, or AR_XPE Card

Client Port Alarm and TCA Thresholds
thresholds for the AR_MXP, AR_XP, and AR_XPE
cards.
Prerequisite Procedures DLP-G278 Provisioning the Optical Line Rate

698
Procedure
AR_XPE card where you want to change the client port alarm and TCA threshold settings.
Step 3 Referring to the following table, verify the TCA thresholds for client ports (ports 1 through 8) for RX Power
and click Refresh.
Note The hardware device that plugs into a AR_MXP, AR_XP, or AR_XPE card faceplate to provide a
fiber interface to the card is called a Small Form-factor Pluggable (SFP or XFP). In CTC, SFPs and
XFPs are called pluggable port modules (PPMs). SFPs/XFPs are hot-swappable I/O devices that
plug into a port to link the port with the fiber-optic network. Multirate PPMs have provisionable
port rates and payloads. For more information about SFPs and XFPs, see SFP, SFP+, QSFP+, XFP,
CXP, CFP, CFP2 and CPAK Modules, on page 310.
Table 265: AR_MXP, AR_XP, and AR_XPE Card Client Interfaces TCA Thresholds
FC1G ONS-SE-4G-SM 0 –17 3 –16

ONS-SC-2G-XX.X
ONS-SC-4G-XX.X
FC2G ONS-SE-4G-SM 0 –15 3 –16

ONS-SC-2G-XX.X
ONS-SC-4G-XX.X
FICON1G ONS-SE-4G-SM 0 –17 3 –16

ONS-SC-2G-XX.X
ONS-SC-4G-XX.X

ONS-SC-2G-XX.X
ONS-SC-4G-XX.X
FC4G ONS-SE-4G-SM 0 –12 4 –15

ONS-SC-2G-XX.X
ONS-SC-4G-XX.X
699

ONS-SC-2G-XX.X
ONS-SC-4G-XX.X
FC8G ONS-XC-8G-MM 0 –12 4 –15

ONS-XC-8G-SM
FICON8G ONS-XC-8G-MM 0 –12 4 –15

ONS-XC-8G-SM
1GE ONS-SI-GE-SX
ONS-SI-GE-LX
ONS-SI-GE-ZX
ONS-SE-ZE-EL
FE ONS-SE-GE-BXU
ONS-SE-GE-BXD
ESCON ONS-SE-200-MM
OC3/STM1 ONS-SC-155-EL
ONS-SI-155-SR-MM
ONS-SI-155-I1
ONS-SI-155-L1
ONS-SI-155-L2
OC12 ONS-SI-622-SR-MM
OC12/STM4 ONS-SI-622-I1
ONS-SI-622-L1
ONS-SI-622-L2
OC48/STM16 ONS-SI-2G-S1
ONS-SI-2G-L1
ONS-SI-2G-L2
OTU1 ONS-SI-2G-S1
ONS-SE-Z1
ONS-SI-2G-L2
ONS-SC-2G-xxxx
OTU2 ONS-XC-10G-96C
3G-SDI, ONS-SC-HD3GV-RX=
HD-SDI,
SD-SDI
Step 4 Click Apply.

Step 5 Repeat step 3 and step 4 to provision each additional client port.
700
Table 266: AR_MXP, AR_XP, and AR_XPE Card Client Interface Alarm Thresholds
FC1G ONS-SE-4G-SM 0 –17 3 –16

ONS-SC-2G-XX.X
ONS-SC-4G-XX.X
FC2G ONS-SE-4G-SM 0 –15 3 –16

ONS-SC-2G-XX.X
ONS-SC-4G-XX.X

ONS-SC-2G-XX.X
ONS-SC-4G-XX.X

ONS-SC-2G-XX.X
ONS-SC-4G-XX.X
FC4G ONS-SE-4G-SM 0 –12 4 –15

ONS-SC-2G-XX.X
ONS-SC-4G-XX.X

ONS-SC-2G-XX.X
ONS-SC-4G-XX.X
FC8G ONS-XC-8G-MM 0 –12 4 –15

ONS-XC-8G-SM
FICON8G ONS-XC-8G-MM 0 –12 4 –15

ONS-XC-8G-SM
1GE ONS-SI-GE-SX
ONS-SI-GE-LX
ONS-SI-GE-ZX
ONS-SE-ZE-EL
FE ONS-SE-GE-BXU
ONS-SE-GE-BXD
ESCON ONS-SE-200-MM
701
OC3/STM1 ONS-SC-155-EL
ONS-SI-155-SR-MM
ONS-SI-155-I1
ONS-SI-155-L1
ONS-SI-155-L2
OC12 ONS-SI-622-SR-MM
OC12/STM4 ONS-SI-622-I1
ONS-SI-622-L1
ONS-SI-622-L2
OC48/STM16 ONS-SI-2G-S1
ONS-SI-2G-L1
ONS-SI-2G-L2
OTU1 ONS-SI-2G-S1
ONS-SE-Z1
ONS-SI-2G-L2
ONS-SC-2G-xxxx
3G-SDI, ONS-SC-HD3GV-RX=
HD-SDI,
SD-SDI
Step 8 Click Apply.


Purpose This task changes the OTN settings for the AR_MXP,
702
Procedure
or AR_XPE card where you want to change the OTN settings.
Thresholds, FEC Thresholds, Trail Trace Identifier, or Proactive Protection Regen.
The following table describes the values on the Provisioning > OTN > OTN Lines tab.
Table 267: AR_MXP, AR_XP, and AR_XPE Card OTN Line Settings

Port (Display only) Displays the port All client and trunk ports
number.
G.709 OTN Sets the OTN lines according to Enabled by default

ITU-T G.709.
FEC Sets the OTN lines to forward error • Disable

correction (FEC).
• Standard
• Enhanced-I.4
• Enhanced-I.7
SF BER (Display only) Displays the signal • 1E-5


rate.
• 1E-6
• 1E-7
• 1E-8
• 1E-9
Asynch/Synch Mapping Sets how the ODUk (client • Asynch mapping

channel (OTUk). • Synch mapping
703
OTU Mapping Sets the client payload mapping to • ODU1e

the trunk
• ODU2e
• CBR10G
• ODU1Mux
• ODU1

reference.

timing source.
Admin SSM In Overrides the synchronization STU

defaults to STU.
Send DoNotUse If checked, sends a DUS message Checked or unchecked

on the S1 byte.
ODU Transparency Sets the ODU overhead byte • Transparent Standard Use
configuration.
• Cisco Extended Use
Proactive Protection Regen Enables or disables the proactive • Enable

protection regen mode.
• Disable
The following table describes the values on the Provisioning > OTN > G.709 Thresholds tab.
Table 268: AR_MXP, AR_XP, and AR_XPE ITU-T G.709 Threshold Settings

19
number.
704

(OTUk) or PM (ODUk). Select an
option and click Refresh.


Latency for a 1G-FC payload without ITU-T G.709 is 4 microseconds, and with ITU-T G.709 is
40 microseconds. Latency for a 2G-FC payload without ITU-T G.709 is 2 microseconds, and
with ITU-T G.709 is 20 microseconds. Consider these values when planning a FC network that
is sensitive to latency.
The following table describes the values on the Provisioning > OTN > FEC Threshold tab.
Table 269: AR_MXP, AR_XP, and AR_XPE Card FEC Threshold Settings

number.
705
Table 270: AR_MXP, AR_XP, and AR_XPE Card Trail Trace Identifier Settings

number.

• Path

• Manual
Transmit Displays the current transmit string String of trace string size
or sets a new transmit string. Click
to Hex).
is checked.
Expected Displays the current expected string String of trace string size
or sets a new expected string. Click
to Hex).
panel updated.
706
Auto-refresh If checked, automatically refreshes Checked

Unchecked (default)
Step 4 Click Apply.


Purpose This procedure allows you to view the mapping of
ODU object with the corresponding client port for the
AR_XPE card.
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the AR_XPE card to view
the ODU object mapping with the corresponding client port. The card view appears.
Step 2 Click the Provisioning > Card ODU Interfaces tabs. Displays the parameters as described in the table.
Table 271: ODU Object and Client Port Mapping
Parameter Description
ODU Object Displays the ODUk(k=0) AID that is used to raise the
ODU0 level alarms.
Trunk Port Number Displays the physical trunk port details that map to
the virtual ODUk(k=0) port or object.
ODU1 Displays the ODU1 frame number within the ODU-2

frame, which has the corresponding ODUk(k=0)
frame.
ODU0 Displays the ODU0 frame number within a ODU1

frame.
707
NTP-G235 Provisioning an Operating Mode
Client Port Number Displays the physical client port number that maps to
the virtual ODUk(k=0) port or object.
NTP-G235 Provisioning an Operating Mode

Purpose This procedure enables you to provision an operating
mode on the 100G-LC-C, 100G-CK-C,
100GS-CK-LC, , 200G-CK-LC,100G-ME-C,
100ME-CKC, 10x10G-LC, CFP-LC, or MR-MXP
card.
Procedure
provision an operating mode. The card view appears.
Step 3 In the Card tab, click Create. The Operating Mode Configuration Creation window appears.
Step 4 From the Card Configuration drop-down list, choose the configuration. The card configuration options vary
depending on the card. If the TXP-10G, TXPP-10G, RGN-10G, or LOW LATENCY mode is selected on the
10x10G-LC card, go to Step 7. If the FANOUT-10x10G mode is selected in the 10x10G-LC card, go to Step
8.
For more information about the card configurations, see Key Features of 100G-LC-C, 100G-ME-C, 100G-CK-C,
100ME-CKC, 10x10G-LC, 100GS-CK-LC, 200G-CK-LC, CFP-LC, and MR-MXP Cards, on page 271.
Step 5 Choose the slot number from the Peer Card drop-down list. This field is enabled only if a peer card is required
for the configuration.
Step 6 Choose the slot number from the Skip Peer card drop-down list. This field is enabled only for MXP_200G
and MXP_10x10G_100G operating modes.
Step 7 Select the port pair in the Card Configuration Dialog area.
The 10x10G-LC card supports a maximum of five TXP-10G modes, two TXPP-10G modes, five RGN-10G
modes, five LOW LATENCY modes, or a combination of five TXP-10G, RGN-10G, and LOW LATENCY
708
NTP-G361 Provisioning an Operating Mode on the 400G-XP-LC Card
modes. For the TXPP-10G mode configuration, client ports can be port 3, port 7, or both. Port 4 and port 6
are selected as trunk ports when port 3 is selected as the client port. Port 8 and port 10 are selected as trunk
ports when port 7 is selected as the client port. For MXP_200G, MXP_10x10G_100G, and
MXP_CK_100G operating modes, the required ports are selected by default.
Step 8 Click Finish. The selected operating mode is provisioned on the card.
Step 9 Complete the DLP-G726 Preprovisioning a Multirate PPM task.
Step 10 Complete the DLP-G278 Provisioning the Optical Line Rate, on page 321 task.
NTP-G361 Provisioning an Operating Mode on the

400G-XP-LC Card
mode on the 400G-XP-LC card.
Note Provision the PPM on the trunk ports ( Port 11 and 12) of the 400G-XP-LC card before you provision the
operating mode.
From Release 10.9, MXP 2x150G Operating modes are supported on the 400G-XP-LC card.
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 400G-XP-LC card where
you want to provision an operating mode. The card view appears.
Step 3 In the Card tab, click Create. The Operating Mode Configuration Creation window appears.
Step 4 From the Card Configuration drop-down list, choose the operating mode.
For the OTNXC and the REGEN card modes, both trunk ports are configured with the same rate (100G or
200G). The trunk port configuration that is created for CFP2-11 is copied to CFP2-12. For the MXP 2x150G
card mode, both the trunk ports are configured at 150G.
709
NTP-G361 Provisioning an Operating Mode on the 400G-XP-LC Card
Step 5 To configure the trunk port (CFP2 - 11, CFP2 - 12, or both trunk ports), perform the following steps:
Choose the operating mode from the Trunk Operating Mode drop-down list. If the mode selected is
M_100G, the Slice 1 or Slice 3 fields are disabled. If the mode selected is MXP_2x150G, the Slice 2
field is disabled.
Choose the slice mode from the Slice drop-down list. The 10x10G-LC card is supported on Slice 2 only.
The configuration can be done only from the 400G-XP-LC card.
For more information about the trunk, slice, and port configuration, see Slice Definition and Line
Card Configuration for 400G-XP-LC Card.
Slice configuration is not applicable for the REGEN mode.

The operating mode is provisioned on the card.

To edit an operating mode:
Table 272: Rules for Editing an Operating Mode on the 400G-XP-LC Card
Editing an Op Mode Trunk Port Client Port Restrictions/Information
Modifying a slice mode Allowed with trunk in IS Blocked if client

within a trunk payloads are provisioned
on the slice being edited.
Adding a trunk - - Related trunk PPM
must be provisioned.
Deleting a trunk Blocked if trunk is in IS Blocked if client payloads Blocked, if the trunk to
or if trunk is associated are provisioned for the be deleted is the only
with internal patch cords trunk being deleted provisioned trunk on the
(IPCs) or provisional card.
patch cords (PPCs).
Modifying the trunk Blocked if trunk is in IS Blocked if client payloads The existing OTU4 or
operating mode or if trunk is associated are provisioned for the OTU4C2 trunk port is
IPCs or PPCs. trunk being modified deleted and recreated.
Step 9 In the Card tab, choose the configured operating mode and click Edit. The Operating Mode Configuration
window appears.
The OTNXC and the REGEN card mode cannot be edited after it is configured. To modify the card
mode configuration, you need to delete the existing configuration and create a new one.
Step 10 Choose the trunk port to be edited from the Edit Trunk Configuration drop-down list.
Note Only one trunk port configuration can be edited at a time. The table above details the rules for
editing an operating mode.
The Trunk Operating Mode cannot be edited for REGEN mode.
Step 11 Modify the Trunk Operating Mode and the Slice modes as needed.
710
NTP-G362 Manual FPGA Upgrade on the 400G-XP-LC Card

The operating mode is updated with the new configuration on the card.

Step 15 To delete an operating mode, in the Card tab, choose the configured operating mode and click Delete.
The operating mode is deleted. A card operating mode can be deleted only if client payloads are not
provisioned and the trunk ports in the out-of-service (OOS) state with no IPCs or PPCs associated.
NTP-G362 Manual FPGA Upgrade on the 400G-XP-LC Card

Purpose This procedure manually upgrades the FPGA/
firmware images in the 400G-XP-LC card.
Note The manual FPGA / firmware upgrade is allowed only when there is a version mismatch. A Different FPGA/
firmware image available condition is raised to notify the user of the availability of a new firmware image.
It is recommnded to upgrade the FPGA / firmware on the cards, at both ends of the circuit.
Procedure
you want to provision an operating mode. The card view appears.
Step 3 Click the FPGA/FIRMWARE Upgrade button.
A warning message is displayed.
711
NTP-G366 Viewing the ODU Utilization for ODU Circuits
Step 4 Click Yes.

The card undergoes a cold reset and the FPGA now contains the updated images. To view the FPGA
and firmware versions, click the Card view > Maintenance > Info tabs.
NTP-G366 Viewing the ODU Utilization for ODU Circuits

Purpose This procedure allows you to view the ODU utilization
per 400G-XP-LC card, OTN span, and ILK
consumption for each ODU circuit.
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 400G-XP-LC card.
The card view appears.
Step 3 Click ODU Utilization.
An ODU utilization window for the 400G-XP-LC card is displayed where you can get information about
the availability of each port for ODU circuit creation.
All ODU ports are displayed according to the slice configuration that was configured. Each row represents
100G or ODU4 bandwidth. The client ports are listed first followed by the trunk ports. The ports that are
already used by the ODU circuit are displayed in green, the ports that are available for circuit creation are
displayed in orange and the ports that are not applicable nor configured are displayed in gray.
If a slice is configured with the OPM_100G option, the ODU usage is reserved for ODU4 circuits. If a
slice is configured with the OPM_10x10G option, the ODU usage is reserved for ODU2 circuits.
Step 4 Click the Maintenance > ODU > ODU tabs. The pane displays the ILK consumption for each ODU
circuit as described in the table.
Table 273: ILK Consumption
Circuit Displays the circuit name.
712
NTP-G367 Provisioning Encryption on 400G-XP-LC Card
Source Port Displays the source port number.
Source ODU # Displays the source ODU number in use
Destination Port Displays the destination port number.
Destination ODU # Displays the destination ODU number in use.
ILK Usage Displays the ILK usage for the circuit. All protected
circuits depicted by a tree hierarchy consume one
ILK bandwidth.
Bandwidth Displays the bandwidth for the circuit.
Note The ILK, client, and trunk ODU2e usage per 400G-XP-LC card is also displayed in terms of a
percentage below the table.
Step 5 To view the number of available link ODUs on the source and destination nodes, right-click the OTN span
in the network map in the network view and select the Span Utilization option.
In the case of OTU4 trunk, the first 10 ODUs are not available and are depicted with "-". If the ODU is in
use, it is depicted with an "x" and if the ODU is available, it is depicted with an tick mark. For the link
ODU to be available, both the source and destination ODU must be available. The ODU utilization is also
displayed as a percentage.
NTP-G367 Provisioning Encryption on 400G-XP-LC Card

Purpose This procedure allows you to provision encryption
on the 400G-XP-LC card.
• NTP-G361 Provisioning an Operating Mode on

the 400G-XP-LC Card, on page 709
Security Level Security user or security super user
The encryption feature (Enable/Disable) requires a new hardware FPGA image. The 400G-XP LC card must be
running with FPGA version 1.02 or higher. The FPGA version information can be checked using Card view >
Maintenance > Info > FPGA_HW_VERSION in CTC. A Condition message warns the user about
713
DLP-G817 Configuring GCC2 Settings on 400G-XP-LC Card
availability of a new image. To upgrade the FPGA image, see NTP-G362 Manual FPGA Upgrade on
the 400G-XP-LC Card, on page 711.
The encrypted traffic on 400G-XP-LC card goes down if the Key Exchange Fail (KEY-EX-FAIL)
alarm remains for more than 40 hours.
Procedure

DLP-G817 Configuring GCC2 Settings on 400G-XP-LC Card, on page 714
DLP-G818 Enabling or Disabling Card Authentication and Payload Encryption on 400G-XP-LC Card,
on page 715
DLP-G819 Resetting the Master Key on 400G-XP-LC Card, on page 716
DLP-G820 Changing the Master Key Reset Interval on 400G-XP-LC Card, on page 717
DLP-G817 Configuring GCC2 Settings on 400G-XP-LC Card

Purpose This task configures a GCC2 channel on OTN enabled
trunk ports to establish a connection between two
400G-XP-LC cards by configuring the IP address and
ports of the source and destination cards.
Prerequisite Procedures Disable Card Authentication on 400G-XP-LC Card
Required/As Needed As Needed
Onsite/Remote Onsite or Remote
Note Each card on a node must have unique GCC2 source IP address. This IP address must not match with the
source or destination IP address of other cards on the same node.
Procedure
Step 1 In node view (single shelf mode), or shelf view (multi-shelf mode), double-click the 400G-XP-LC card for
which you want to configure the GCC settings.
Step 2 Go to Provisioning > Encryption > GCC2 Settings.
714
DLP-G818 Enabling or Disabling Card Authentication and Payload Encryption on 400G-XP-LC Card
Step 3 In the Card IP Address field, specify the IP address of the source 400G-XP-LC card.
Step 4 Click on the Destination Card IP entry. Specify the IP address of the destination card.
The range of source and destination IP address is 172.16.0.1 to 172.16.0.255. The destination IP address
must be same for IPort1 and IPort2. The destination IP address must be same for IPort3 and IPort4.
There can be only two destination card IP addresses and destination ports for the 400G-XP-LC card.
Step 5 Click on the Destination Port entry. Specify the port number of the destination card.
The values of Destination Port must be 1 or 3 for IPort1, 2 or 4 for IPort2, 3 or 1 for IPort3, 4 or 2 for
IPort4 depending on the trunk port of the peer card this card is connected.
Step 6 Click Apply.
DLP-G818 Enabling or Disabling Card Authentication and

Payload Encryption on 400G-XP-LC Card
Purpose This task initiates the authentication of a destination
400G-XP-LC card with a source 400G-XP-LC card.
This ensures that the source card communicates only
with the destination card. This task also enables
payload encryption on 400G-XP-LC card.
Prerequisite Procedures DLP-G817 Configuring GCC2 Settings on

Procedure
which you need to enable or disable card authentication and payload encyption.
Step 2 Go to Provisioning > Encryption > Security.
Step 3 From the Port list, choose the port on which card authentication is to be enabled or disabled.
Step 4 Check the Card Authentication checkbox to enable card authentication.
Uncheck the Card Authentication checkbox to disable card authentication.
Note When the Card Authentication check box is checked, the Payload Encryption check box is
automatically checked and vice versa.
715
DLP-G819 Resetting the Master Key on 400G-XP-LC Card
The master key for encryption is exchanged between the source and destination 400G-XP-LC cards and
OTN frames are encrypted.
Step 5 Click Apply.
Step 6 Repeat step 3 to step 5 for each port that carries the encrypted payload, as the card authentication takes
place independently on each port of the source 400G-XP-LC card.
DLP-G819 Resetting the Master Key on 400G-XP-LC Card

Purpose This task allows to reset the master key for each
encrypted stream of the source 400G-XP-LC card.
For more information, see Key Management, on page
307.
Prerequisite Procedures • DLP-G818 Enabling or Disabling Card

Authentication and Payload Encryption on
Procedure
which you want to reset the master key.
Step 2 Go to Provisioning > Encryption > Key Management.
Step 3 Click the Reset Master Key button for a port to reset the master key used for the payload encryption on
that port.
By resetting the master key, a key exchange is enforced by overriding the existing master key reset
interval, and a new interval is calculated from the time the key is reset.
Resetting the master key does not affect traffic.
Step 4 Click Apply.

716
DLP-G820 Changing the Master Key Reset Interval on 400G-XP-LC Card
DLP-G820 Changing the Master Key Reset Interval on 400G-XP-LC Card

Purpose This task allows to change the master key reset
interval between two consecutive resets of the master
key that is used for payload encryption.

Authentication and Payload Encryption on
Procedure
which you want to change the master key reset interval.
Step 3 Click on the Master Key Change Interval entry for each port. Two spin boxes appear in place of the entry.
The box on the left registers the time in hours; the box on the right, the time in minutes.
The master key interval can be set in multiples of 15 minutes between 15 minutes to 24 hours. The default
interval value is 15 minutes.
Step 4 Set the desired values in the boxes.
When the time interval elapses, a new master key is exchanged between the source and destination 400G-
XP-LC cards.
Step 5 Click Apply.
Limitations of Encryption on 400G-XP-LC Card

AES frame size and location for Encryption overhead cannot be changed.
OTN overhead settings such as AES security setting, ESP header and trailer locations, and
Ingress/Egress PRBS generation are not supported.
Advanced settings such as Ingress/Egress BIP8 bypass is not supported.
Payload authentication is not supported.
Encryption PMs such as Sequence Mismatch parameter is not supported.
717
NTP-G236 Modifying the 100G-LC-C, 100G-CK-C, 100G-ME-C, 100ME-CKC, 10x10G-LC, 100GS-CK-LC, , 200G-CK-LC, CFP-LC, WSE,
MR-MXP, or 400G-XP-LC Card Line Settings and PM Parameter Thresholds
When encryption is enabled, the operating mode cannot be disabled.

Each card on a node must have unique GCC2 source IP address. This IP address must not match with
the source or destination IP address of other cards on the same node.
The client/trunk/Iport loopbacks are not supported if encryption is enabled on the corresponding Iport
and vice versa.
The trunk mode or slice modes cannot be edited if encryption is enabled on the corresponding Iports.
NTP-G236 Modifying the 100G-LC-C, 100G-CK-C,

100G-ME-C, 100ME-CKC, 10x10G-LC, 100GS-CK-LC, ,
200G-CK-LC, CFP-LC, WSE, MR-MXP, or 400G-XP-LC
Card Line Settings and PM Parameter Thresholds
threshold settings of the 100G-LC-C, 100G-CK-C,
100G-ME-C, 100ME-CKC, 10x10G-LC, CFP-LC,
100GS-CK-LC, 200G-CK-LC, WSE, MR-MXP, or
400G-XP-LC cards.

• NTP-G179 Installing the Transponder and
Muxponder Cards
necessary)
on page 321
Procedure
settings.
718

DLP-G715 Changing the Card Ethernet Settings
DLP-G716 Changing the 10x10G-LC and WSE Card SONET/SDH Settings
DLP-G717 Changing the 10x10G-LC and WSE Card Section Trace Settings
DLP-G718 Changing the 10x10G-LC and WSE Card SONET/SDH Line Thresholds
DLP-G719 Changing the Card Line RMON Thresholds
DLP-G720 Provisioning the Card with Trunk Port Alarm and TCA Thresholds
DLP-G722 Changing the Card OTN Settings
DLP-G815 Changing the 400G-XP-LC Card ODU Settings, on page 762
DLP-G770 Enabling PRBS Settings, on page 765

Purpose This task changes the line settings of the 100G-LC-C,
100G-CK-C, 100G-ME-C, 100ME-CKC, 10x10G-LC,
100GS-CK-LC, 200G-CK-LC, CFP-LC, MR-MXP,
MR-MXP-LIC, WSE, or 400G-XP-LC cards.
Procedure
change the line settings.
Step 2 Click the Provisioning > Line > Ports tabs. Tabs and parameter selections vary according to pluggable
port modules (PPM) provisioning.
Step 3 Modify any of the line settings in the Ports tab as described in the following table.
719
Table 274: Card Line Settings

Port (Display only) Displays the port 1 through 12
number.
Port Name Assigns a logical name for the User-defined. Name can be up
specified port. to 80 alphanumeric or special
default.
See the"NTP-G104 Assign a
Name to a Port" task in "Maintain
the Node" chapter.
OOS, DSBLD (ANSI) or
Administrative and Service States OOS, MT (ANSI) or
IS, AINS (ANSI) or
(ETSI)

OOS-AU, AINS (ANSI) or
more information about service OOS-MA, DSBLD (ANSI) or
OOS-MA, MT (ANSI) or
(ETSI)
OOS-MA, LPBK&MT
(ANSI) or Locked-
enabled,loopback &
maintenance (ETSI)
720

ALS Mode Sets the automatic laser shutdown Disabled (default)— ALS is
(ALS) function mode. off; the laser is not
Auto Restart-ALS is on; the
LOS occurs. It automatically
resolved.
resolved.
for testing.
AINS Soak Sets the automatic in-service Duration of valid input signal,
(AINS) soak period. Double-click in hh.mm format, after which
the time and use the up and down the card state changes to in-
arrows to change settings. service (IS) automatically.
0 to 48 hours, 15-minutes
increments.
Reach Sets the optical reach distance of Autoprovision—The system

Note The reach distances that

appear in the drop-down
list depends on the card.
Note On the 400G-XP-LC

card, certain processes
may fail if unsupported
PPMs are plugged into
the card.
721

client port.
• 850 nm through 1610 nm
OverClock Enables or disables overclock • OFF

mode.
• ON
Note When an OTU2
payload is
provisioned on the
10x10G-LC card in
the TXP-10G or
RGN-10G
operating mode,
the overclock
parameter is
automatically set to
ON.
Cd (Working Range) Low Sets the threshold for minimum —

chromatic dispersion.
Cd (Working Range) High Sets the threshold for maximum —

chromatic dispersion.
In 200G-CK-LC card, the CD
(Working Range) High and CD
(Working Range) Low thresholds
value in Provisioning > Line >
Ports tab in CTC do not change
automatically after installing the
100G_SD_FEC_OR_CD_RANGE
license. Hence, it is required to
manually change the threshold
values in CTC. Otherwise, the
Chromatic Dispersion (CD) alarm
is raised.
TX SHUTDOWN If checked, the Tx optical power is —

turned off. This can be done when
the port is out of service or in
maintenance.
722
TX Power Sets the Tx power to a specific The range is from -10.0 to 0.25
value. dBm.
400G-XP-LC: The range for 100G
is from -0.5 to -11.5 dBm; The
range for 200G is from -1.5 to -11.5
dBm.
723
Fault Signalling Shuts down the far-end laser in

(Squelch does not apply to ISC
COMPACT payloads.)
724

• AIS/Send Local Fault
Note AIS/Send Local
Fault is not
supported on all
the payloads .
However, this
option is present in
the drop-down
menu in CTC to
allow a proper
software upgrade
from the previous
release.
• Squelch/Laser-Off
Note When the
100G-LC-C,
100G-CK-C,
100G-ME-C,
100ME-CKC,
100GS-CK-LC, ,
100GS-CK-LC,
200G-CK-LC
cards are used in
the standalone
mode or with the
CFP-LC card
configured in the
CFP-TXP mode,
the value can be set
to
Squelch/Laser-Off
or AIS/Send Local
Fault on the trunk
port of the
100G-LC-C,
100G-CK-C,
100G-ME-C,
100GS-CK-LC, ,
200G-CK-LC card.
When the
100G-LC-C,
100G-CK-C,
100G-ME-C,
100GS-CK-LC,
100ME-CKC, and
card is used with
the CFP-LC card
725

configured
CFP-MXP mode,
the value can be set
to AIS on the trunk
port of the
100G-LC-C,
100G-CK-C,
100G-ME-C,
100GS-CK-LC,
200G-CK-LC, and
100ME-CKC card.
• LF/Local Fault —Supported

for 10GE, 40GE, 16GFC and
100GE payloads.
Note For 16GFC, this is
the default mode;
the user can change
this to squelch, if
required.
• Disable/Transparent—Supported
for any data traffic such as
10GE, 8G FC, 10G FC, 40GE,
100GE.
726

Mapping Mode (10x10G-LC and Sets the mapping mode. • CBR
WSE)
Note CBR mapping
mode supports
Sync-E
transparency.
• GFP
Note The mapping mode
can be configured
to GFP for 10GE
payloads. The GFP
port is placed in
service when both
the client and trunk
ports of the
10x10G-LC card
are in service.
Note When the mapping

mode is set to CBR
on the 10x10G-LC
card, the overclock
parameter is set to
On.
When the mapping
mode is set to GFP
on the 10x10G-LC
card, the overclock
parameter is set to
Off.
Termination Mode Sets the termination mode. • Transparent
727

Squelch Hold Off Timer • Disable (0 ms) - Default value
• 50 ms
• 100 ms
• 250 ms
• 500 ms
728

(Only for 100G-LC-C,
100G-CK-C, 100ME-CK-C,
CFP-LC, 10x10G-LC,
100GS-CK-LC, 200G-CK-LC, and
MR-MXP cards) Sets the period in
milliseconds that the client
interface waits for resolution of
issues on the trunk side. The client
squelching starts after this period.
The user can configure the squelch
hold off timer in CTC only under
the following conditions:
The card must be configured
in TXP or MXP operating
modes.
The client payload must be
10GE or 100GE.
The Squelch drop-down in
CTC must be set to Squelch.
Note • The squelch hold

off timer value can
be changed without
changing the port
admin state.
• When the squelch
holdoff timer is set
to a value other
than 0 ms, Y-Cable
cannot be
provisioned.
• When the Squelch
drop-down is
changed from
non-squelch to
squelch, the
squelch holdoff
timer is set to 0 ms.
• When the node is
upgraded to
R10.5.2, the
squelch hold-off
timer is set to 0 ms.
• When the squelch
timer value is
729

changed, the
changed value will
be applicable in the
next squelch
interval.
• When squelch hold
off timer is active,
the OTU2_XP,
TXP_MR_10E ,
and 40E-MXP-C
cards send junk
frames; the
100G-LC-C,
100G-CK-C,
100ME-CK-C,
CFP-LC,
10x10G-LC,
MR-MXP cards
send Local Fault
(LF).
730
Table 275: Reach Distances for 10x10G-LC, 100G-LC-C, 100G-CK-C, CFP-LC, MR-MXP, 100GS-CK-LC, 200G-CK-
LC, 400G-XP-LC, and WSE Cards
Card Payload Reach
10x10G-LC OTU2 SR-MM
P1I1-2D1
P1S1-2D2b
P1L1-2D2
DWDM
OC192 SR-MM
SR-1
IR-2
LR-2
DWDM
10G FC 10GFC-SW
10GFC-LW
10GFC-EW
10GFC-ZW
DWDM
8G FC 8GFC-SW
8GFC-LW
10 GE TEN_GE_SR
TEN_GE_LR
TEN_GE_ER
TEN_GE_ZR
DWDM
IB-5G LX and SR-MM

100G-CK-C 100 GE 100GBASE-SR10 and
100GBASE-LR4
OTU4 4I1-9D1F
40 GE 40GBASE-SR4
731
Card Payload Reach
100G-LC-C 100 GE 100GBASE-SR10
100GS-CK-LC 100 GE 100GBASE-SR10 and

100GBASE-LR4
200G-CK-LC 100 GE 100GBASE-SR10 and

100GBASE-LR4
CFP-LC 40 GE 40GBASE-FR
40GBASE-LR4
100 GE 100GBASE-LR4
OTU3 VSR2000-3R2
C4S1-2D1
OTU4 4I1-9D1F
MR-MXP 10 GE SR
TEN_GE_SR
MR-MXP
TEN_GE_ER
TEN_GE_ZR
DWDM
CX1
CWDM40km
100 GE 100GBASE-SR10
100GBASE-LR4
OTU2 MLR-QSFP+
TEN_GE_LR
TEN_GE_EP
40GE QSFP-SR4
QSFP-LR4
OC192/STM64 MLR-QSFP+
TEN_GE_LR
TEN_GE_EP
732
Card Payload Reach
400G-XP-LC Trunk ports
OTU4 DWDM
OTU4C2
Client ports
100 GE 100GBASE-LR4
100GBASE-SR4
OTU4 4I1-9D1F
10 GE TEN_GE_LR
OTU2 P1I1 2D1
16GFC 16GFC-SW
Step 4 Click Apply.


Purpose This task changes the Ethernet settings of the
100G-LC-C, 100G-CK-C, 100G-ME-C, 100ME-CKC,
10x10G-LC, CFP-LC, 100GS-CK-LC, 200G-CK-LC,
MR-MXP, WSE, or 400G-XP-LC cards.
Note The ethernet settings of the CFP-LC card
can be changed on the virtual port of the
peer 100G-LC-C, 100G-CK-C,
100G-ME-C, or 100ME-CKC card.
733
Procedure
to change the Ethernet settings. The card view appears.
Step 3 Modify any of the Ethernet settings in the Ethernet tab. The parameters that appear depend on the card mode.
Table 276: Card Ethernet Settings

number n (-n) and rate.
Port Name (Display only) Displays the port —

name.
OOS, DSBLD (ANSI) or
Administrative and Service States OOS, MT (ANSI) or
IS, AINS (ANSI) or
(ETSI)

Unlocked-disabled,
(ETSI)
OOS-MA, LPBK&MT
(ANSI) or Locked-
enabled,loopback &
maintenance (ETSI)
734

ALS Mode Sets the automatic laser shutdown Disabled (default)— ALS is
(ALS) function mode. off; the laser is not
resolved.
for testing.
increments.
Reach Sets the optical reach distance of Autoprovision—The system

NoteThe reach distances that
appear in the drop-
down list depend
on the card.

client port.
• 850 nm through 1610 nm
MTU Sets the maximum size of the Numeric. Default: 1548

Ethernet frames accepted by the
port. The port must be in Range 64 to 9700
OOS/locked state.
735
Incoming MAC address Sets the MAC address of the Value of the MAC address. Six
incoming Ethernet signal. bytes in hexadecimal format.
(100G-LC-C and 10x10G-LC)
Mapping Mode Sets the mapping mode. • CBR

(10x10G-LC) • GFP
Termination Mode (Display-only) Sets the mode of • Transparent

operation.
Video Type Video —

(100G-LC-C and 10x10G-LC)
BJ Fec (400G-XP-LC) Enables or disables BJ Fec on 100G Auto (default)
ethernet client interfaces based on NoteWhen the auto mode is
the QSP28 pluggables used used, BJ Fec is set
to Off for
QSFP28-LR4 and
set to On for
QSFP28-SR4.
Force-Fec-On
Force-Fec-Off
Step 4 Click Apply.


Purpose This task changes the SONET (OC-192)/SDH
(STM-64) settings of the 10x10G-LC and WSE cards.
736
Procedure
change the SONET (OC-192)/SDH (STM-64) settings.
Step 2 Click the Provisioning > Line > SONET (ANSI) or SDH (ETSI) tabs. Tabs and parameter selections
vary according to PPM provisioning.
Step 3 Modify any of the settings as described in the table.
Table 277: 10x10G-LC and WSE Card SONET/SDH Settings

number.
Port Name Assign a name for the specified User-defined. Name can be up
port. to 80 alphanumeric or special
default.
DLP-G104 Assigning a Name to
a Port
IS, AINS (ANSI) or
document. OOS, DSBLD (ANSI) or
OOS, MT (ANSI) or

Unlocked-disabled,
Locked-
737
SF BER Sets the signal fail (SF) bit error • 1E-3

rate (BER).
• 1E-4 (default)
• 1E-5
SD BER Sets the signal degrade (SD) bit • 1E-5

error rate (BER).
• 1E-6
• 1E-7 (default)
• 1E-8
• 1E-9
Type Sets the optical transport type. SONET (ANSI)

SDH (ETSI)
ALS Mode Sets the automatic laser shutdown Disabled (default)—ALS is

(ALS) function mode. The DWDM off; the laser is not
transmitter supports ALS according automatically shut down
to ITU-T G.644 (06/99). ALS can when traffic outage or loss of
be disabled or enabled for one of signal (LOS) occurs.
the three mode options.
Auto Restart—ALS is on; the
LOS occurs. It automatically
resolved.
resolved.
for testing.
738

increments.
ProvidesSync Sets the ProvidesSync card Checked

Unchecked
reference.
SyncMsgIn Sets the EnableSync card Checked

Unchecked
timing source.
Send Sets the Send DoNotUse card state. Checked

When checked, sends a do not use
DoNotUse Unchecked
(DUS) message on the S1 byte.
(WSE)
STU
Admin SSM In Overrides the synchronization
defaults to STU.
Reach Sets the optical reach distance of Autoprovision—The system to
the client port. automatically provision the
NoteThe reach distances that
appear in the drop-
down list depend
on the card.

client port.
Step 4 Click Apply.

739
10x10G-LC and WSE cards.
Procedure
PPM provisioning.
Step 3 Modify any of the settings in the Section Trace tab as described in the table.
Table 278: 10x10G-LC and WSE Card Line Section Trace Settings

number.

Manual
Disable AIS/RDI on TIM-S? If a trace identifier mismatch (TIM) Checked (AIS/RDI on TIM-S
on a section overhead alarm arises is disabled)
mismatch, no alarm indication
signal (AIS) is sent to the TIM-S is not disabled)
downstream nodes if this box is
checked.
If the Received Trace Mode field
is set to Manual, the Disable
AIS/RDI on TIM-S? checkbox is
automatically checked.
• 16 byte
740

Transmit Displays the current transmit string Hex Mode— Click to change
or sets a new transmit string. the display to hexadecimal
Note The transmit string (button changes to ASCII
Mode).
cannot be configured
when the termination ASCII Mode— Click to
mode is transparent. change the display to
Hex Mode).
Note The button title

changes based on
the current display
mode.
Expected Displays the current expected string Hex Mode— Click to change
or sets a new expected string. the display to hexadecimal
(button changes to ASCII
Mode).
ASCII Mode— Click to
Hex Mode).

changes based on
the current display
mode.
Received (Display only) Displays the current Hex Mode— Click to change
received string. the display to hexadecimal
Mode).
ASCII Mode— Click to
Hex Mode).

changes based on
the current display
mode.
Auto-refresh If checked, automatically refreshes • Checked

741
Step 4 Click Apply.

Purpose This task changes the SONET/SDH line threshold

settings of the 10x10G-LC card.
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 10x10G-LC card where
you want to change the SONET/SDH line threshold settings.
Step 3 Modify any of the settings as shown in the table.
Note You must modify each of these options independently: Near End and Far End, 15 Min and 1 Day,
and Line and Section. To do so, choose the appropriate radio button and click Refresh.
Table 279: 10x10G-LC and WSE Card SONET/SDH Line Threshold Settings

Port (Display only) Displays • Client Ports • Client Ports
the port number.
742

CV Coding violations (CV) Numeric. Threshold —
or Far End
(minutes) or 1 day
• Types—Line or
Section (near end
only)

category and click
Refresh.
EB Errored Block (EB) — Numeric. Threshold

or Far End
(minutes) or 1 day
Section or
(near end only)

category and click
Refresh.
ES Errored seconds (ES) Numeric. Threshold Numeric. Threshold

(near end only)
Refresh.
743

(SES) display options include: display options include:
(near end only)
Refresh.
only) Failure count (FC) display options include:
or Far End
(minutes) or 1 day
• Types—Line or
Section (near end
only)

category and click
Refresh.
BBE Background block error — Numeric. Threshold

(BBE) display options include:
or Far End
(minutes) or 1 day
Section or
(near end only)

category and click
Refresh.
744

(UAS) • Direction—Near End • Direction—Near End
(near end only)
category and click Choose an option in each
Refresh.
Step 4 Click Apply.


for 100G-LC-C, 100G-CK-C, 100G-ME-C,
100ME-CKC, 10x10G-LC, CFP-LC, 100GS-CK-LC,
200G-CK-LC, MR-MXP, WSE, or 400G-XP-LC
cards carrying Ethernet or FC payloads.
Note The RMON threshold settings for the
CFP-LC card can be changed on the virtual
port of the peer 100G-LC-C, 100G-CK-C,
100G-ME-C, or 100ME-CKC card.
745
Procedure
change the line RMON threshold settings in the card view.
(ONEHUNDRED_GE)” port.
Step 5 From the Variable drop-down list, choose an Ethernet, FC, FICON, or GFP variable. See the following tables
for the list of the available variables.
Table 280: Card Ethernet Variables

ifInUcastPkts 20 Total number of packets delivered by this sublayer to
a higher sublayer that are not addressed to a multicast
or broadcast address.
1
ifInMulticastPkts Total number of packets delivered by this sublayer to
a higher sublayer that are addressed to a multicast
address. For a MAC layer protocol, this includes both
group and functional addresses.
1
ifInBroadcastPkts Total number of packets delivered by this sublayer to
a higher sublayer that are addressed to a broadcast
address.

IfOutUcastPkts Total count of packets transmitted to a unicast group

destination address.

addresses.
746


dot3StatsFCSErrors Total number of frames received on a particular

interface that are an integral number of octets in length
but do not pass the FCS check.
dot3StatsFrameTooLong Total number of frames received on a particular

interface that exceed the maximum permitted frame
size.


64 octets in length (excluding framing bits, but
Note that it is entirely normal for etherStatsFragments
to increment. This is because it counts both runts
(which are normal occurrences due to collisions) and
noise hits.
etherStatsPkts Total number of frames received on an interface in

both Rx and Tx directions.


inclusive (excluding framing bits, but including FCS
octets).

length inclusive (excluding framing bits, but including
FCS octets).

FCS octets).
747

length inclusive (excluding framing bits, but
including FCS octets).
length inclusive (excluding framing bits, but
including FCS octets).
etherStatsBroadcastPkts Total number of good packets received that
were directed to the broadcast address. Note that
this number does not include multicast packets.
directed to a multicast address. Note that this
number does not include packets directed to the
broadcast address.
etherStatsOversizePkts Total number of packets received that were longer than
octets) and were otherwise well-formed.
etherStatsJabbers Total number of packets received that were longer than

octets), and had either a bad FCS with an integral
number of octets (FCS error) or a bad FCS with a non-
integral number of octets (alignment error).
etherStatsOctets Total number of octets of data (including those in

received that were 1591 octets in length
(excluding framing bits, but including FCS octets).
pcs49RxErrBer —
pcs49RxErrDec —
The counter does not increment for traffic with incorrect Ethertype and packet size of more than
64 bytes on the 10x10G-LC and 100G-LC-C cards.
Table 281: 10x10G-LC and WSE FC/FICON Variables
mediaIndStatsRxFramesBadCRC Total number of received data frames with payload

CRC errors when HDLC framing is used.
748
mediaIndStatsTxFramesBadCRC Total number of transmitted data frames with payload


bytes. This value is a part of the high-level data link
control (HDLC) and GFP port statistics.
mediaIndStatsTxFramesTruncated Total number of transmitted data frames that exceed

the MTU. This value is a part of the HDLC and GFP
port statistics.
mediaIndStatsRxFramesTooLong Total number of received frames that exceed the

maximum transmission unit (MTU). This value is a
part of the HDLC and GFP port statistics.
mediaIndStatsTxFramesTooLong Total number of transmitted data frames that are less

than 5 bytes. This value is a part of the HDLC and
GFP port statistics.

including the framing octet.

ifInErrors Total number of inbound packets that contained errors

protocol.
ifOutErrors Total number of outbound packets or transmission

units that could not be transmitted because of errors.
pcs49RxErrBer —
pcs49RxErrDec —
Table 282: 10x10G-LC and WSE GFP RMON Variables
gfpStatsRxFrame Total number of received data frames.
gfpStatsTxFrame Total number of transmitted data frames.
gfpStatsRxCRCErrors Total number of CRC errors with the receive

transparent GFP frame.
gfpStatsRxOctets Total number of GFP data octets received.
gfpStatsTxOctets Total number of GFP data octets transmitted.
749
gfpStatsRxSBitErrors Received GFP frames with single bit errors in the core
header (these errors can be corrected).
gfpStatsRxMBitErrors Received GFP frames with multiple bit errors in the

core header (these errors cannot be corrected).

data.
gfpRxCmfFrame —
gfpRxCmfFrame —
Step 6 From the Alarm Type drop-down list, indicate whether the event will be triggered by the rising threshold,
The available options are Rising Threshold, Falling Threshold, and Rising and Falling Threshold.
Step 8 Enter the appropriate number of seconds in the Sample Period field.
Step 9 Enter the appropriate number of occurrences in the Rising Threshold field.
Step 11 Click OK.

Note To view all RMON thresholds, check the Show All RMON thresholds checkbox.
750
Purpose This task provisions the 100G-LC-C, 100G-CK-C,
100G-ME-C, 100GS-CK-LC, 200G-CK-LC,
100ME-CKC, or 400G-XP-LC cards with trunk port
alarm and TCA thresholds.
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 100G-LC-C, 100G-CK-
C, 100G-ME-C, 100GS-CK-LC, 200G-CK-LC, 100ME-CKC, or 400G-XP-LC card where you want to
provision the trunk port alarm and TCA threshold settings.
Step 3 If TCA is not selected, click the TCA radio button and then click Refresh. If it is checked, continue with
step 4.
Step 4 Verify if the port TCA thresholds are set. Provision new thresholds as needed by double-clicking the
threshold value you want to change, deleting it, entering a new value, and pressing Enter.
Step 6 Verify if the port Alarm thresholds are set. Provision new thresholds as needed by double-clicking the
threshold value you want to change, deleting it, entering a new value, and pressing Enter.
Step 7 Click Apply.
751

thresholds for the 100G-LC-C, 10x10G-LC, CFP-LC,
MR-MXP, 100G-CK-C, 100G-ME-C, 100GS-CK-LC,
, 200G-CK-LC, 100ME-CKC, and 400G-XP-LC
cards.
Note The client port alarm and TCA thresholds
cannot be provisioned on the QSFP+ ports
of the MR-MXP cards.
Prerequisite Procedures • DLP-G278 Provisioning the Optical Line Rate,

on page 321
Procedure
change the client port alarm and TCA threshold settings.
Step 3 Verify if the TCA thresholds for client ports for RX Power High, RX Power Low, TX Power High, and TX
Power Low parameters are set based on the client interface at the other end. Provision new thresholds as
needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and
pressing Enter.
Note The hardware device that plugs into a card faceplate to provide a fiber interface to the card is
called a Small Form-factor Pluggable (SFP, QSFP+, XFP, or CXP) or a C Form-factor Pluggable
(CFP, CFP2, or CPAK). In CTC, SFPs, QSFPs+, XFPs, CXPs, CFPs, and CPAKs are called
pluggable port modules (PPMs). SFPs/QSFPs+/XFPs/CXPs/CFPs/CPAKs are hot-swappable I/O
devices that plug into a port to link the port with the fiber-optic network. Multirate PPMs have
provisionable port rates and payloads. For more information, see SFP, SFP+, QSFP+, XFP, CXP,
CFP, CFP2 and CPAK Modules, on page 310.
Note For multi-lane pluggables (CXP, CFP, CPAK), the thresholds are set on the first lane and
copied on the remaining lanes. You can edit only the first lane.
752
Step 4 Click Apply.

Step 7 Verify if the client port Alarm thresholds for RX Power High, RX Power Low, TX Power High, and TX
Power Low parameters are set based on the client interface that is provisioned. Provision new thresholds as
needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and
hitting Enter.
Step 8 Click Apply.

100G-LC-C, 100G-CK-C, 100G-ME-C, 100ME-CKC,
10x10G-LC, 100GS-CK-LC, 200G-CK-LC, CFP-LC,
or 400G-XP-LC cards.
Note The OTN settings cannot be provisioned
on the virtual port of the MR-MXP card.
Prerequisite Procedures Login to CTC.
Procedure
change the OTN settings.
Step 2 Click the Provisioning > OTN tabs, then choose one of the following subtabs: OTN Lines, ITU-T
G.709 Thresholds, FEC Thresholds, Trail Trace Identifier, or Proactive Protection Regen.
Note You must modify each of these options independently: Near End and Far End, 15 Min and 1
Day, and SM and PM. To do so, choose the appropriate radio button and click Refresh.
The following table describes the values on the Provisioning > OTN > OTN Lines tab.
753
Table 283: Card OTN Line Settings
number.
ITU-T G.709 OTN Sets the OTN lines according to Enabled by default
ITU-T G.709.
FEC Sets the OTN lines to forward error See .

correction (FEC).

fail (SF) bit error rate (BER).

error rate (BER).
• 1E-6
• 1E-7 (Default)
• 1E-8
• 1E-9
ProvidesSync Sets the ProvidesSync card Checked

Unchecked
reference.
SyncMsgIn Sets the EnableSync card Checked

Unchecked
timing source.
Admin SSM In Overrides the synchronization STU—Sync traceability

status message (SSM) and the unknown
ST2—Stratum 2
does not receive an SSM signal, it ST3—Stratum 3
defaults to STU.
SMC—SONET minimum
clock
ST4—Stratum 4
DUS—Do not use for timing
RES—Reserved; quality level
set
754

Interop Mode Enables interoperability between None (default value)
200G-CK linecards and other
Enable
vendor interfaces.
Table 284: ITU-T G.709 Threshold Settings

number.
ES Errored seconds (ES) Numeric. Can be set for Near End

SES Severely errored seconds (SES) Numeric. Can be set for Near End
UAS Unavailable seconds (UAS) Numeric. Can be set for Near End
BBE Background block errors (BBE) Numeric. Can be set for Near End
FC Failure counter (FC) Numeric. Can be set for Near End

The following table describes the values on the Provisioning > OTN > FEC Thresholds tab.
Table 285: Card FEC Threshold Settings

number.
755

Table 286: Card Trail Trace Identifier Settings

Port Displays the port number. —

Path

Manual
Disable FDI on TTIM? If a Trace Identifier Mismatch on Checked (FDI on TTIM is

Note FDI is not supported for
is checked.
TTI-PM but is
This field is enabled only if the applicable for TTI-SM.
Received Trace Mode is set to
Manual.
756

Transmit Displays the current transmit string • Hex Mode—Click to change
(Release 10.1 and earlier releases ) or sets a new transmit string. the display to hexadecimal
Supported in 400G-XP-LC card Mode).
• ASCII Mode—Click to
change the display to ASCII
(button changes to Hex
Mode).
Note Transmit is not
supported for
TTI-PM but is
applicable for
TTI-SM.

changes based on
the current display
mode.
Expected Displays the current expected string • Hex Mode—Click to change

(Release 10.1 and earlier releases) or sets a new expected string. the display to hexadecimal
Mode).
changes based on
the current display
mode.
Received (Display only) Displays the current • Hex Mode—Click to change

(Release 10.1 and earlier releases) received string. the display to hexadecimal
Mode).
changes based on
the current display
mode.
757

In Release 10.3 and later releases:
Transmit Area—The Edit Transmit Area allows you to enter a new transmit string. The Current
Transmit Area displays the current transmit string.
Expected Area—The Edit Expected Area allows you to enter a new expected string. The Current
Expected Area displays the current expected string.
Received Area—The Current Received Area displays the current received string.
SAPI Source Access Point Identifier —

(SAPI) of the TTI.
DAPI Destination Access Point Identifier —

(DAPI) of the TTI.
User Operator Data User operator data of the TTI. —
Edit Mode Sets the transmit or expected string —

type to ASCII or Hex.
Fill from Current Uses the values of the current or —

expected transmit string for the
SAPI, DAPI, and User Operator
Data fields.
Hex Mode When the button label displays —

“Hex Mode”, the strings in the
SAPI, DAPI and User Operator
fields are in ASCII format. Click
the Hex Mode button to display the
string in hexadecimal format. The
button name also changes to
“ASCII Mode”. Click ASCII Mode
to return the strings to ASCII
format.

the display every five seconds.
Note Do not check the
auto-refresh checkbox
while configuring the
TTI strings.
From Release 10.6.2, the 400G-XP line cards support SAPI/ DAPI (and not TTI).
The received trace value in the Provisioning -> OTN -> Trail Trace Identifier tab might be empty (even
when TTI is not OFF and is receiving information) upon the following conditions, for these cards - 100GS-
CK-LC, 200G-CK-LC, 400G-CK-L, MR-MXP :
The user has logged into the node for the first time.
The user has upgraded the node.
758
The user has reset the card.
Click Refresh or Reset to view the received trace value immediately or click Auto-refresh to view
the received trace value after five seconds.
Table 287: Support for Proactive Protection Regeneration
Card Operating Mode Supported Payloads
100G-LC-C and 100G-ME-C TXP-100G or RGN-100G 100GE, OTU4
100G-CK-C and 100ME-CKC TXP-100G or RGN-100G • CPAK-100G-LR4 with

100GE,OTU4
• CPAK-100G-SR10 with
100GE,OTU4
10x10G-LC MXP-10x10G OTU2
CFP-LC CFP-TXP 100GE, OTU4
Note The 100GS-CK-LC and 200G-CK-LC cards do not support proactive protection.
The following table describes the values on the Provisioning > OTN > Proactive Protection Regen tabs.
Table 288: Card Proactive Protection Regen Settings

number and name (optional).
Trigger Threshold Sets the maximum BER threshold • 1E-3

to trigger proactive protection.
• 9E-4 to 1E-4
• 9E-5 to 1E-5
• 9E-6 to 1E-6
• 9E-7 to 1E-7
759

Trigger Window (ms) Sets the duration when BER is Time in milliseconds.
monitored before triggering the
proactive protection.
The trigger window value must be
a multiple of:
• 10 ms for trigger thresholds
between 1E-3 and 6E-6
• 100 ms for trigger threshold
between 5E-6 to 1E-7
Trigger window must be less than

or equal to 500 ms for trigger
thresholds between 1E-3 and 6E-6.
The trigger window must be less
than or equal to 3900 ms for trigger
thresholds between 5E-6 to 1E-7.
Revert Threshold Sets the revert threshold value of 1E-4

BER.
9E-5 to 1E-5
Note The revert threshold
9E-6 to 1E-6
settings must be less
than the trigger 9E-7 to 1E-7
threshold values.
9E-8 to 5E-8
Revert Window (ms) Sets the duration when BER is Time in milliseconds.
monitored for settings that are less
than the revert threshold value
before which proactive protection
provided to the router is removed.
The revert window value must be
at least 2000 ms and a multiple of:
• 10 ms for a revert threshold of
1E-4 to 6E-7
• 100 ms for a revert threshold
of 5E-7 to 5E-8.
The revert window must be less

than or equal to 3900 ms.
760

Enable Proactive Protection Enables proactive protection. The available options for
TXP-100G operating mode on the
100G-LC or 100G-CK card are:
• Disabled—Proactive
protection is not enabled.
• FRR Proactive
Protection—Supported on all
the pluggables except on
ONS-CC-100G-LR4= and
CPAK-100G-LR4 when the
client payload is 100GE-LAN.
• Pre-FEC PSM Proactive
Protection—This option is
supported on the trunk port
only when the client has
ONS-CC-100G-LR4= and
CPAK-100G-LR4. Also, this
option is applicable only when
the card is configured in
TXP-100G and CFP-TXP
operating modes using 100GE
or OTU4 payload.
The available options for
MXP-10x10G operating mode are:
• Enabled
• Disabled
The available options for
10x10G-LC card are:
• Egress Proactive Protection
Enabled
• Egress Proactive Protection
Disabled
Step 4 Click Apply.

761
DLP-G815 Changing the 400G-XP-LC Card ODU Settings

Purpose This task changes the ODU settings for the
400G-XP-LC cards configured in the OTNXC mode.
Note The ODU parameters on the protected
trunk-ODUs cannot be edited
independently. The ports inherit the values
of the working trunk-ODUs.
Note The ODU line and ODU threshold settings
are not applicable for ODU4 interfaces.
The TCAs and conditions are directly
raised on the trunk port.
Prerequisite Procedures Login to CTC.
Procedure
you want to change the ODU settings.
Step 2 Click the Provisioning > ODU tabs, then choose one of the following subtabs: ODU Lines, ODU
Thresholds, or ODU TTI.
Step 3 In the Port drop-down list, choose a port.
Day, and SM and PM. To do so, choose the appropriate radio button and click Refresh.
The following table describes the values on the Provisioning > ODU > ODU Lines tab.
Table 289: Card ODU Line Settings

ODU (Display only) Displays the port trunk ports
number.

fail (SF) bit error rate (BER).
762

error rate (BER).
• 1E-6
• 1E-7 (Default)
• 1E-8
• 1E-9
The following table describes the values on the Provisioning > ODU > ODU Thresholds tab.
Table 290: ODU Threshold Settings
Port (Display only) Displays the port trunk ports

number.
ES Errored seconds (ES) Numeric. Can be set for Near End

one-day intervals. Select an option
and click Apply.
SES Severely errored seconds (SES) Numeric. Can be set for Near End
and click Apply.
UAS Unavailable seconds (UAS) Numeric. Can be set for Near End
and click Apply.
BBE Background block errors (BBE) Numeric. Can be set for Near End
and click Apply.
FC Failure counter (FC) Numeric. Can be set for Near End

or Far End. Select an option and
click Apply.
Note To restore the default values, select a row from the table and click Reset to Default.
The following table describes the values on the Provisioning > ODU > TTI tab.
Table 291: Card Trail Trace Identifier Settings
Port Displays the port number. client ports
763

Level Sets the level. Path

Manual
Disable FDI on TTIM? If a Trace Identifier Mismatch on Checked (FDI on TTIM is

is checked.
This field is enabled only if the
Received Trace Mode is set to
Manual.
Transmit Area—The Edit Transmit Area allows you to enter a new transmit string. The Current
Transmit Area displays the current transmit string.
Expected Area—The Edit Expected Area allows you to enter a new expected string. The Current
Expected Area displays the current expected string.
Received Area—The Current Received Area displays the current received string.
SAPI Source Access Point Identifier —

(SAPI) of the TTI.
DAPI Destination Access Point Identifier —

(DAPI) of the TTI.
User Operator Data User operator data of the TTI. —
Edit Mode Sets the transmit or expected string —

type to ASCII or Hex.
Edit Current Values Uses the values of the current or —

expected transmit string for the
SAPI, DAPI, and User Operator
Data fields.
Hex Mode When the button label displays —

“Hex Mode”, the strings in the
SAPI, DAPI and User Operator
fields are in ASCII format. Click
the Hex Mode button to display the
string in hexadecimal format. The
button name also changes to
“ASCII Mode”. Click ASCII Mode
to return the strings to ASCII
format.
764
DLP-G770 Enabling PRBS Settings

the display every five seconds.
Note Do not check the
auto-refresh checkbox
while configuring the
TTI strings.
Click Refresh or Reset to view the received trace value immediately or click Auto-refresh to view
the received trace value after five seconds.
Step 5 Click Apply.
DLP-G770 Enabling PRBS Settings

Purpose This task enables PRBS settings for the 100G-LC-C,
100G-CK-C, 100G-ME-C, 100ME-CKC,
100GS-CK-LC, and 200G-CK-LC cards.
Procedure
enable the PRBS settings.
Step 2 Click the Maintenance > PRBS tabs.
Table 292: Card PRBS Settings

Port (Display only) Displays the port Trunk ports
number.
765
NTP-G351 Retrieving MAC Addresses on MR-MXP Cards

IS,AINS (ANSI) or
OOS,MT (ANSI) or
Generator Pattern Displays the pattern generated by PRBS_31

the line card.
Detected Pattern Displays the pattern detected by the PRBS_11

line card. PRBS_23
PRBS_31
Only PRBS_31 is supported on
the 100GS-CK-LC and 200G-
CK-LC cards.
Pattern Sync Status Displays the pattern sync status. PATTERN_NONE

PATTERN_OK
PATTERN_ERROR
Step 4 Click Apply.

NTP-G351 Retrieving MAC Addresses on MR-MXP Cards

Purpose This procedure enables you to retrieve the MAC
address of the host connected to the MR-MXP ports
for 10 GE clients using the Link Layer Discovery
Protocol (LLDP).
Prerequisite Procedures NTP-G235 Provisioning an Operating Mode, on page

708
766
NTP-G338 Provisioning an Operating Mode on the WSE Card
Procedure
Step 1 In the node view (single-shelf mode) or shelf view (multishelf view), double-click the MR-MXP card
where you want to retrieve the source MAC addresses.
Step 2 Click the Maintenance > LLDP tabs.
Step 3 Click Retrieve.
The table displays the following fields:
Port-Displays the port number.
Source MAC Address-Displays the MAC address of the node to which the port is connected.
NTP-G338 Provisioning an Operating Mode on the WSE Card

mode on the WSE card.
Security Level Super user
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the WSE card where you
want to provision an operating mode. The card view appears.
Note You cannot edit an existing operating mode on the WSE card.
Step 3 In the Operating Modes tab, click Create.

Step 4 Choose the configuration from the Card Configuration drop-down list. The card configuration options are
TXP-10G and RGN-10G modes.
Step 5 Select the defined port pair in the Card Configuration Dialog area. The WSE card supports a maximum of five
TXP-10G modes, five RGN-10G modes, or a combination of five TXP-10G, and RGN-10G modes.
Step 6 Click Finish. The selected operating mode is provisioned on the WSE card.
767
NTP-G339 Modifying the WSE Card Line Settings and PM Parameter Thresholds
NTP-G339 Modifying the WSE Card Line

Settings and PM Parameter Thresholds
threshold settings of the WSE card.

• NTP-G179 Installing the Transponder and
Muxponder Cards
necessary)
on page 321
Procedure
settings.
DLP-G744 Changing the WSE Card Security Thresholds and Setting Authentication Error Thresholds
DLP-G740 Changing the WSE Card Ethernet Settings
DLP-G745 Changing the WSE Card Line RMON Thresholds
DLP-G746 Provisioning the WSE Card with Port Alarm and TCA Thresholds
DLP-G747 Change the WSE Card OTN Settings
768
DLP-G739 Changing the WSE Card Line Settings

Purpose This task changes the line settings of the WSE card.
Procedure
want to change the line settings.
Tabs and parameter selections vary according to pluggable port modules (PPM) provisioning.
Step 3 Modify any of the line settings in the Ports tab as described in the following table.
Table 293: WSE Card Line Settings
Port (Display only) Displays the port number. 1 through 10
Port Name Assigns a logical name for the specified User-defined. Name can be up to 80 alphanumeric
port. or special characters, or both. Blank by default.
DLP-G104 Assigning a Name to a Port
Admin State Sets the port service state unless network IS (ANSI) or Unlocked (ETSI)
conditions prevent the change. For more
OOS, DSBLD (ANSI) or Locked,disabled
information about administrative states,
see the Administrative and Service States (ETSI)
document. OOS, MT (ANSI) or Locked,maintenance
(ETSI)
IS, AINS (ANSI) or
Unlocked,AutomaticInService (ETSI)
769

Service State (Display only) Identifies the autonomously IS-NR (ANSI) or Unlocked-enabled (ETSI)
generated state that gives the overall
OOS-AU, AINS (ANSI) or Unlocked-
condition of the port. Service states appear
in the format: Primary State-Primary State disabled, automaticInService (ETSI)
Qualifier, Secondary State. For more
information about service states, see the OOS-MA, DSBLD (ANSI) or
Administrative and Service States Locked-enabled,disabled (ETSI)
document.
OOS-MA, MT (ANSI) or Locked-
OOS-MA, LPBK&MT (ANSI) or Locked-
enabled,loopback & maintenance (ETSI)
Disabled (default)— ALS is off; the laser is

ALS Mode Sets the automatic laser shutdown (ALS) not automatically shut down when traffic
function mode. outage or loss of signal (LOS) occurs.
Auto Restart—ALS is on; the laser
automatically shuts down when traffic
outage or LOS occurs. It automatically
restarts when the conditions that caused the
Manual Restart— ALS is on; the laser
automatically shuts down when traffic outage
or LOS occurs. However, the laser must be
manually restarted when conditions that
caused the outage are resolved.
Manual Restart for Test— Manually restarts
the laser for testing.
Duration of valid input signal, in hh.mm

AINS Soak Sets the automatic in-service (AINS) soak format, after which the card state changes
period. Double-click the time and use the to in-service (IS) automatically.
up and down arrows to change settings.
0 to 48 hours, 15-minute increments.
Reach Sets the optical reach distance of the client Autoprovision—The system automatically
port. provisions the reach from the pluggable port
module (PPM) reach value on the hardware.
Wavelength Displays the wavelength of the client port. • First Tunable Wavelength
• – 850 nm through 1610 nm
770

OverClock Enables or disables overclock mode. OFF
ON
Note When an OTU2 payload is

provisioned on the WSE card in the
TXP-10G or RGN-10G operating
mode, the overclock parameter is
automatically set to ON.
Fault Shuts down the far-end laser in response AIS/Send Local Fault
Signalling to certain defects.
Squelch/Laser-Off
Mapping Sets the mapping mode. CBR

Mode In a WSE card with a 10-GE payload, GFP
when a network fault or failure occurs,
and the user sets squelch to the Disable
state, the faults propagated downstream
are different in GFP and CBR mapping.
In GFP mapping, the device connected to
the client reports a momentary local fault,
but in CBR mapping, the local fault is
reported for the entire duration of the
fault.
Termination Sets the termination mode. Transparent

Mode
Table 294: Reach Distances for WSE Card
Card Payload Reach

WSE OTU2 SR-MM
P1I1-2D1
P1S1-2D2b
P1L1-2D2
DWDM
OTU2e TEN_GE_SR
TEN_GE_LR
TEN_GE_ER
TEN_GE_ZR
DWDM
771
Step 4 Click Apply.


Purpose This task changes the ethernet settings of the WSE
card.
Procedure
want to change the ethernet settings.
Tabs and parameter selections vary according to pluggable port modules (PPM) provisioning.
Step 3 Modify any of the line settings in the Ethernet tab as described in the table.
Table 295: WSE Card Ethernet Settings

Port (Display only) Displays the port number --
n-n and rate.
Port Name (Display only) Displays the port name. --
Admin State Sets the port service state unless network IS (ANSI) or Unlocked (ETSI)
conditions prevent the change. For more
OOS, DSBLD (ANSI) or Locked,disabled
information about administrative states,
see the Administrative and Service States (ETSI)
document. OOS, MT (ANSI) or Locked,maintenance
(ETSI)
IS, AINS (ANSI) or
Unlocked,AutomaticInService (ETSI)
772

Service State (Display only) Identifies the IS-NR (ANSI) or Unlocked-enabled (ETSI)
autonomously generated state that gives
the overall condition of the port. Service OOS-AU, AINS (ANSI) or Unlocked-
states appear in the format: Primary disabled, automaticInService (ETSI)
State-Primary State Qualifier, Secondary
State. For more information about OOS-MA, DSBLD (ANSI) or
service states, see the Administrative and Locked-enabled,disabled (ETSI)
OOS-MA, MT (ANSI) or Locked-
OOS-MA, LPBK&MT (ANSI) or Locked-
enabled,loopback & maintenance (ETSI)
Disabled (default)— ALS is off; the laser is

ALS Mode Sets the automatic laser shutdown (ALS) not automatically shut down when traffic
function mode. outage or loss of signal (LOS) occurs.
Manual Restart— ALS is on; the laser
automatically shuts down when traffic outage
or LOS occurs. However, the laser must be
manually restarted when conditions that
caused the outage are resolved.
Manual Restart for Test— Manually restarts
the laser for testing.
Duration of valid input signal, in hh.mm

AINS Soak Sets the automatic in-service (AINS) soak format, after which the card state changes
period. Double-click the time and use the to in-service (IS) automatically.
up and down arrows to change settings. 0 to 48 hours, 15-minute increments.
Reach Sets the optical reach distance of the client Autoprovision—The system automatically
port. provisions the reach from the pluggable port
module (PPM) reach value on the hardware.
Wavelength Displays the wavelength of the client port. • First Tunable Wavelength
• – 850 nm through 1610 nm
MTU Sets the maximum size of the Ethernet Numeric. Default: 1548
frames accepted by the port. The port must Range 64 to 9700
be in OOS/locked state.
Termination (Display-only) Sets the mode of operation. Transparent
Mode
773
DLP-G744 Changing the WSE Card Security Thresholds and Setting Authentication Error Thresholds
Step 4 Click Apply.

DLP-G744 Changing the WSE Card Security Thresholds

and Setting Authentication Error Thresholds
Purpose This task changes the security threshold settings of
the WSE card. This task also sets the payload
authentication error thresholds.
Procedure
want to change the security threshold settings.
Step 2 Click the Provisioning > Security Thresholds tabs.
Step 3 Modify any of the settings as described in the table.
Note You must modify each of these options independently: TCA and Alarm, and 15 Min and 1 Day.
Table 296: WSE Card Security Threshold Settings
Port Selects the port number.
Sequence Mismatch Shows the number of times the Sequence Number

(SEQ) for an AES packet has differed at the
encryption and decryption ends.
Step 4 Click Apply.

Step 5 To set the payload authentication error thresholds, go to Provisioning > Security Thresholds tab and
click the Alarm radio button.
Step 6 Enter the authentication error threshold value in the Payload Authentication Error field.
The default value is 1. The range is 1 to 500.
774
The Payload Authentication Alarm is raised when the payload authentication error PM counter for 10
seconds in the Encryption PM tab exceeds the payload authentication error value set in the Security
Thresholds tab. The Payload Authentication Alarm is not raised if payload authentication is enabled only
on the near end or far end.
Step 7 Click Apply.

for WSE cards carrying Ethernet or FC payloads.
Procedure
want to change the RMON threshold settings in the card view.
(TEN_GE)” port.
Step 5 From the Variable drop-down list, choose an Ethernet variable. See Table 11-230 for a list of available
Ethernet variables.
Table 297: WSE Card Ethernet Variables
etherStatsPkts Total number of frames received on an interface in

both Rx and Tx directions.

bits, but including FCS octets).
775

dot3StatsFCSErrors Total number of frames received on a particular

interface that are an integral number of octets in length
but do not pass the FCS check.

dot3StatsSymbolErrors Contains a count of received frames that have an

associated RX_ER assertion during a data reception
error event (MII) or data reception error event or
carrier extension error (GMII) from the PCS.
dot3StatsFrameTooLong Total number of frames received on a particular

interface that exceed the maximum permitted frame
size.
dot3StatsLCVErrors/mediaIndStatsRxLcvErrors Number of received line code violations at the PCS

layer.
dot3StatsLayer1Errors Number of Layer 1 errors as defined within the

• During Packet Reception—Layer 1 errors are
only counted one time per packet. The Layer 1
error is indicated as a direct result of a line side
protocol violation in which RX_DV is asserted.
This is an uncommon event from which may be
the reason why the device loses synchronization.
• During Interpacket Reception—The Layer 1 error
is indicated as a direct result of a line side
protocol violation in which RX_DV is
de-asserted. This is an uncommon event. The
Layer 1 error is also asserted on detection of a
False Carrier indication and is asserted on
detection of Erred byte (interpacket) signal
encoding. When the Layer 1 error is asserted
during inter-packet reception, it is only
statistically asserted in the vector.

number of octets (FCS error) or a bad FCS with a
non-integral number of octets (alignment error).
776


64 octets in length (excluding framing bits, but
Note that it is entirely normal for etherStatsFragments
to increment. This is because itcounts both runts
(which are normal occurrences due to collisions) and
noise hits.


inclusive (excluding framing bits, but including FCS
octets).

FCS octets).

FCS octets).

FCS octets).

FCS octets).

address.

directed to the broadcast address. Note that this
number does not include multicast packets.
777
ifInUcastPkts Total number of packets delivered by this sublayer

to a higher sublayer that are not addressed to a
(The counter does not increment for traffic with
multicast or broadcast address.
incorrect Ethertype and packet size of more than
64 bytes on the WSE card.)
ifInMulticastPkts Total number of packets delivered by this sublayer
to a higher sublayer that are addressed to a multicast
address. For a MAC layer protocol, this includes
both group and functional addresses.
ifInBroadcastPkts Total number of packets delivered by this sublayer
to a higher sublayer that are addressed to a
broadcast address.
IfOutUcastPkts Total count of packets transmitted to a unicast group

destination address.

addresses.


mediaIndStatsTXFramesBadCRC Total number of transmitted data frames with payload

mediaIndStatsTXShortPkts Number of transmitted frames containing less than

the minimum permitted frame size as programmed
with the transmit MAC Min Frame Length
Configuration Register.
Step 6 Click Apply.
778
Purpose This task provisions the WSE card with port alarm
and TCA thresholds.
Procedure
want to provision the alarm and TCA threshold settings for the port.
Note You must modify 15 Min and 1 Day independently. Choose the appropriate radio button and
click Refresh.
Step 3 If TCA is not selected, select the TCA option and then click Refresh. If it is checked, continue with Step 4.
Step 4 Verify whether the port TCA thresholds for RX Power High, RX Power Low, TX Power High, and TX
Power Low are set.
Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting
Step 6 Verify whether the port alarm thresholds for RX Power High, RX Power Low, TX Power High, and TX
Power Low are set.
Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting
Step 7 Click Apply.
779

Purpose This task changes the OTN settings for the WSE card.
Prerequisite DLP-G46 Log into CTC

Procedures
Procedure
want to change the OTN settings.
Step 2 Click the Provisioning > OTN tabs. Choose one of these subtabs: OTN Lines, ITU-T G.709 Thresholds,
FEC Thresholds, or Trail Trace Identifier.
Step 3 Modify any of the settings described in the tables.
Day, and SM and PM. Choose the appropriate radio button and click Refresh.
The table describes the values on the Provisioning > OTN > OTN Lines tab.
Table 298: WSE Card OTN Line Settings

Port (Display only) Displays the port number. All client and trunk ports
ITU-T G.709 Sets the OTN lines according to ITU-T G.709. Enabled by default
OTN
FEC Sets the OTN lines to forward error correction (FEC). Disable
When an OTN cloud is present between two WSE cards Standard
used in stacked card scenario, it is recommended to
keep the same FEC setting on both ends of the OTN Enhanced
cloud to avoid FEC-MISM alarm on the WSE cards.
SF BER (Display only) Displays the signal fail (SF) bit error rate 1E-5
(BER).
780

SD BER Sets the signal degrade (SD) bit error rate (BER). 1E-5
1E-6
1E-7 (Default)
1E-8
1E-9
ProvidesSync Sets the ProvidesSync card parameter. If checked, the card Checked
is provisioned as a NE timing reference.
Unchecked
SyncMsgIn Sets the EnableSync card parameter. Enables Checked

synchronization status messages (S1 byte), which allow
Unchecked
the node to choose the best timing source.
Admin SSM Overrides the synchronization status message (SSM) and PRS—Primary Reference
In the synchronization traceability unknown (STU) value. If Source
the node does not receive an SSM signal, it defaults to
STU—Sync traceability
STU.
unknown
ST2—Stratum 2
ST3—Stratum 3
SMC—SONET minimum
clock
ST4—Stratum 4
DUS—Do not use for
timing
RES—Reserved; quality
level set
Table 299: WSE ITU-T G.709 Threshold Settings
Port (Display only) Displays the All client and trunk ports
port number.
ES Errored seconds (ES) Numeric. Can be set for Near End or Far End, for 15-minutes or
one-day intervals, or for SM (OTUk) or PM (ODUk). Select an
781
SES Severely errored seconds Numeric. Can be set for Near End or Far End, for 15-minutes or
(SES) one-day intervals, or for SM (OTUk) or PM (ODUk). Select an
UAS Unavailable seconds (UAS) Numeric. Can be set for Near End or Far End, for 15-minutes or
BBE Background block errors Numeric. Can be set for Near End or Far End, for 15-minutes or
(BBE) one-day intervals, or for SM (OTUk) or PM (ODUk). Select an
FC Failure counter (FC) Numeric. Can be set for Near End or Far End, for 15-minutes or
The following table describes the values on the Provisioning > OTN > FEC Thresholds tab.
Table 300: WSE Card FEC Threshold Settings
number.
Bit Errors Corrected Sets the value for bit errors corrected. Numeric. Can be set for 15-minutes or one-day
intervals. Select an option and click Refresh.
Uncorrectable Sets the value for uncorrectable Numeric. Can be set for 15-minutes or one-day
Words words. intervals. Select an option and click Refresh.
Table 301: WSE Card Trail Trace Identifier Settings
Port (Display only) Displays the port number. All client and trunk ports

• Path
Received Trace Sets the trace mode. • Off/None

Mode
• Manual
782

Disable FDI on If a Trace Identifier Mismatch on Checked (FDI on TTIM is disabled)
TTIM? Section overhead alarm arises because
Manual
of a J0 overhead string mismatch, no
Forward Defect Indication (FDI) Unchecked (FDI on TTIM is not disabled)
signal is sent to the downstream nodes
if this box is checked.
This field is enabled only if the Received
Trace Mode is set to Manual.
Transmit Displays the current transmit string or Hex Mode— Click to change the display to
sets a new transmit string. hexadecimal (button changes to ASCII
Mode).
ASCII Mode—Click to change the display
to ASCII (button changes to Hex Mode).
NoteThe button title changes based on the
current display mode.
Expected Displays the current expected string or Hex Mode— Click to change the display to
sets a new expected string. hexadecimal (button changes to ASCII
Mode).
Received (Display only) Displays the current Hex Mode— Click to change the display to
received string. hexadecimal (button changes to ASCII
Mode).
Auto-refresh If checked, automatically refreshes the Checked

Unchecked
Step 4 Click Apply.

783
NTP-G340 Provisioning Encryption on the WSE and MR-MXP Cards
NTP-G340 Provisioning Encryption on the WSE

and MR-MXP Cards
Purpose This procedure enables you to provision
encryption on the WSE and MR-MXP cards.
• NTP-G338 Provisioning an Operating Mode on

the WSE Card
• NTP-G235 Provisioning an Operating Mode, on
page 708
Security Level Security super user
The card authentication and payload encryption must be enabled to check Bit Interleaved Parity-8 (BIP-
8) functionality on encrypted traffic.
Note When BIP-8 functionality is enabled on the MR-MXP card of the source node, the MR-MXP card of the
destination node raises only the ODUk-SD alarm instead of ODUk-SD and ODUk-SF alarms.The WSE
card raises both the ODUk-SD and ODUk-SF alarms for the same scenario.
Procedure

DLP-G759 Configuring GCC2 Settings
DLP-G748 Enabling or Disabling Card Authentication, on page 786
DLP-G749 Enabling Payload Encryption
DLP-G Enabling Payload Authentication, on page 787
DLP-G751 Resetting the Master Key, on page 788
DLP-G752 Changing the Master Key Reset Interval
DLP-G753 Setting AES Secure Packet Configuration
DLP-G754 Specifying ESP Header and Trailer Locations
784
DLP-G755 Enabling PRBS Generation and Monitoring

Purpose This task configures a GCC2 channel on OTN enabled
trunk ports to establish a connection between two
WSE or two MR-MXP cards by configuring the IP
address and ports of the source and destination cards.
Prerequisite Procedures DLP-G748 Enabling or Disabling Card Authentication

The card authentication and payload encryption are
enabled by default and cannot be disabled for
MR-MXP-K9 and MR-MXP-K9= PIDs.
Procedure
Step 1 In node view (single shelf mode), or shelf view (multi-shelf mode), double-click the WSE or MR-XMP
card for which you want to configure the GCC settings.
Step 2 Go to Provisioning > Encryption > GCC2 Settings.
Step 3 In the Card IP Address field, provide the IP address of the source WSE or MR-MXP card.
Step 4 Click on the Destination Card IP entry. Specify the IP address of the destination card.
Step 5 Click on the Destination Port entry. Specify the port number of the destination card.
There can be multiple destination card IPs and destination ports for WSE card and only a single
destination card IP and destination port for MR-MXP card.
Step 6 Click Apply.
To change the MR-MXP or WSE card role from master to slave and vice versa:
Remove only the card IP address or only the destination card IP address or both.
Modify or configure the required IP address in the Card IP Address or Destination Card IP field.
785
DLP-G748 Enabling or Disabling Card Authentication
DLP-G748 Enabling or Disabling Card Authentication

Purpose This task initiates the authentication of a destination
WSE or MR-MXP card with a source WSE or
MR-MXP card. This ensures that the source card
communicates only with the destination card.
Security Level Security Super User
Procedure
Step 1 In node view (single shelf mode), or shelf view (multi-shelf mode), double-click the WSE or MR-MXP
card for which you need to enable or disable card authentication.
Step 3 (Only for WSE card) From the Port list, choose the port on which card authentication is to be enabled
or disabled.
Step 4 Check the Card Authentication checkbox to enable card authentication.
Uncheck the Card Authentication checkbox to disable card authentication.
The master key for encryption is exchanged between the source and destination WSE or MR-MXP cards.
Step 5 Click Apply.

Step 6 (Only for WSE card) Repeat step 3 to step 5 for every port that carries the encrypted payload, as the card
authentication takes place independently on each port of the source WSE card.
DLP-G749 Enabling Payload Encryption

Purpose This task enables encryption of OTN frames emerging
from a port of the source WSE or MR-MXP card.
786
DLP-G Enabling Payload Authentication
Prerequisite Procedures • DLP-G759 Configuring GCC2 Settings, on page

785
• DLP-G748 Enabling or Disabling Card
Authentication, on page 786

Procedure
card for which you want to enable payload encryption.
Step 3 Check the Payload Encryption check box to enable encryption of the OTN frames.
In WSE card, do not enable encryption with far-end client loopback. This affects the traffic. In MR-
MXP card, the client loopback is disabled when encryption is enabled.
When encryption is enabled in the near end and disabled in the far end, the client port of MR-MXP card
raises Local Fault (LF) and the client port of WSE card raises SYNCLOSS alarm.
Step 4 Click Apply.
DLP-G Enabling Payload Authentication

Purpose This task enables payload authentication on the
MR-MXP card to validate the integrity of the received
payloads.
The payload authentication is enabled by default and
can be disabled for MR-MXP-K9 and MR-MXP-K9=
PIDs of MR-MXP card.

Authentication
• DLP-G749 Enabling Payload Encryption
787
DLP-G751 Resetting the Master Key
Security Level Super user
Procedure
Step 1 In node view (single shelf mode), or shelf view (multi-shelf mode), double-click the MR-MXP card for
which you want to enable payload authentication.
Step 2 Go to Provisioning > Encryption > Security tab.
Step 3 Check the Payload Authentication check box to enable payload authentication and click Apply.
DLP-G751 Resetting the Master Key

Purpose This task lets you reset the master key for each
encrypted stream of the source WSE or MR-MXP
card.
For more information, see Key Management, on page
307.

• DLP-G749 Enabling Payload Encryption, on
page 786
Procedure
card for which you want to reset the master key.
Step 3 (For WSE card) Click the Reset Master Key button for a port to reset the master key used for the payload
encryption on that port.
(For MR-MXP card) Click the Reset Master Key button to reset the master key used for the payload
encryption on the card.
788
By resetting the master key, a key exchange is enforced by overriding the existing master key reset
interval, and a new interval is calculated from the time the key is reset.
Step 4 Check the TCA on Key Reset check box to raise TCA notification indicating MASTERKEY-SUCCESS
transient condition of the payload on a port listed in the Port column.
When this check box is checked on both the near end and far end, the Alarms and History tabs are updated
with TCA notifications on both the near end and far end in the specified master key change interval. Two
key resets occur in every key reset interval.
Step 5 Click Apply.

Purpose This task lets you change the master key reset interval
between two consecutive resets of the master key that
is used for payload encryption.

• DLP-G749 Enabling Payload Encryption, on
page 786
Procedure
card for which you want to change the master key reset interval.
Step 3 Click on the Master Key Change Interval entry. For WSE card, two spin boxes appear in place of the entry
and for MR-MXP card, four spin boxes appear.
For WSE card, the box on the left registers the time in hours; the box on the right, the time in minutes.
For MR-MXP card, four boxes register the time in days, hours, minutes, and seconds.
For WSE card, the master key interval can be set in multiples of 15 minutes between 15 minutes to 48 hours.
For MR-MXP card, the master key interval can be set between 50 seconds and 48 hours.
Step 4 Set the desired values in the boxes.
When the time interval elapses, a new master key is exchanged between the source and destination WSE
or MR-MXP cards.
789
Step 5 Check the TCA on Key Reset check box to raise TCA notification indicating MASTERKEY-SUCCESS
transient condition of the payload on a port listed in the Port column.
When this check box is checked on both the near end and far end, the Alarms and History tabs are updated
with TCA notifications on both the near end and far end in the specified master key change interval. Two
key resets occur in every key reset interval.
Step 6 Click Apply.

Purpose This task configures the number of OTN frames per
AES secure packet. The AES secure packet for each
port can be made up of 4 or 8 OTN frames. For more
information, see AES Secure Packet, on page 308

785
• Disable Card Authentication for MR-MXP Card

Procedure
card for which you want to set the AES secure packet configuration.
Step 2 Go to Provisioning > Encryption > OTN Overhead for Packet traffic.
Step 3 Click on the AES Secure Packet entry corresponding to the port where the AES secure packet must
be configured. A dropdown list appears.
Step 4 From the drop-down list, choose either 4 OTN Frame Based or 8 OTN Frame Based.
Step 5 Click Apply.
790

Purpose This task specifies the location of the ESP
(Encapsulating Security Payload) Header and Trailer
in each OTN frame of the AES secure packet.

785
• Disable Card Authentication for MR-MXP Card

Procedure
card for which you want to specify the ESP header and trailer locations.
Step 3 Click on the ESP Header Location entry corresponding to a port.
The locations available are A, B, C, D, E and F. The default values of ESP Header Location and ESP Trailer
Location are location A. The ESP header and trailer require a total of 32 bytes within the OTN overhead.
Step 4 Choose the ESP header location from the predefined values in the list.
The ESP Trailer Location is updated to match the location of the ESP header.
Step 5 Click Apply.

791

Purpose This task lets you enable PRBS generation at the
ingress, and PRBS monitoring at the egress of each
port for the source and destination WSE or MR-MXP
cards.
For MR-MXP card, PRBS Generation and Monitoring
is possible only when card authentication and payload
encryption are disabled.

785
• Disable Card Authentication and Payload
Encryption for MR-MXP Card

Note PRBS does not work for WSE card when client loopback is enabled.
Procedure
card for which you want to enable PRBS generation and PRBS monitoring.
Step 3 Check the Ingress PRBS Generator check box for a port to enable PRBS generation at the ingress of
that port. The ingress of a port is the data path in the encryption block.
Step 4 Check the Egress PRBS Monitor check box for a port to enable PRBS monitoring at the egress of that port.
The egress of a port is the data path in the decryption block.
Step 5 Click Apply.
792
NTP-G342 Provisioning FIPS and CC Mode
NTP-G342 Provisioning FIPS and CC Mode

Purpose This procedure lets you enable the FIPS and CC mode
on the node.
Note Provisioning a FIPS and CC mode is not supported in Macintosh computers.
Procedure

DLP-G761 Enabling FIPS and CC Mode, on page 793
DLP-G761 Enabling FIPS and CC Mode

Purpose This task lets you enable the Federal Information
Processing Standard (FIPS) mode and Common
Criteria (CC) for the node. The CTC can be run in
FIPS and CC mode. It supports FIPS 140-2 level 2
standards of encryption and cryptographic services.
The CC certification ensures that the node is accessed,
managed, monitored and provisioned in a highly
secure manner. In the FIPS and CC mode, only the
algorithms that are approved by FIPS and CC can be
run. When the FIPS and CC mode is selected, the
node reboots and performs a self-test at startup.
Note Use this procedure with caution. Running
FIPS and CC mode in a multi-shelf node
with the WSE card in the master shelf,
might lead to loss of control with the
subtended shelfs if a problem occurs.
793
DLP-G760 Configuring Management of FIPS and CC Mode Enabled NE
Note When FIPS mode is enabled during CTC startup, CTC cache directory path must not contain any space in
the Settings > Cache tab. Otherwise, CTC cannot be launched successfully.
Procedure
Step 1 Select the node for which you want to enable FIPS and CC mode.
Step 2 Secure all the access points:
In the node view, click Provisioning > Security > Access.
Change the Access State of Pseudo IOS Access, Shell Access, EMS Access, TL1 Access , and SNMP
Access to Secure state.
Click Apply.
Step 3 Click the FIPS and CC tab.
Step 4 Select the FIPS and CC Mode check box to enable FIPS and CC mode for that node.
Caution In a situation that warrants a breach into the system, the system can be protected by erasing the
private keys. To erase all the private keys in the WSE, MR-MXP, and TNC cards, click
Zeroise Key. A warning message is displayed with details about the consequence of zeroizing
the keys. This will rewrite all the private keys with zeros. This implementation for the private
keys is a requirement as per the FIPS 140-2 compliance.
Step 5 Click Apply.


Purpose This task configures the requirements to manage the
Federal Information Processing Standard (FIPS) and
Common Criteria (CC) mode enabled network
element.
This procedure also applies to EMS and Shell Secure
mode.
794
Required/As Needed Required to use the FIPS and CC mode
Security Level None
Procedure
Step 1 Install JRE version 7.0.

Uninstall previous versions of JREs from the control panel.
Restart the computer.
Download and install the latest JRE version 7.0. for Windows x64.
Step 2 Go to Java Control Panel and click the Advanced tab. Expand Security > General settings. Perform these
actions:
Uncheck the Use SSL 3.0 check box.
Check the Use TLS 1.0 check box.
Step 3 In the Java Control Panel, click the General tab. Click Settings and perform these actions to clear the JNLP
cache:
Clear the Keep temporary files on my computer check box.
Click Delete Files.
Select the files to delete and click OK.
Click OK and exit the Java Control Panel.
Step 4 Install Java Cryptography Extension (JCE)version 7.0.
Download the JCE.
Extract the contents of the downloaded policy file.
Copy and overwrite the security policy file to C:\Program Files\Java\jre7\lib\security\.
<java-home>/lib/security [Unix]
<java-home>\lib\security [Win32]
where <java-home> is the location where the Jave SE Runtime Environmen (JRE) is installed.
Step 5 Configure the browser settings:

Chrome browser settings:
Go to Chrome > Settings.
Click the Open Proxy settings and click the Advanced tab.
Uncheck the Use SSL 3.0 check box.
Check the Use TLS 1.0 check box and click OK.
Firefox browser settings:

Go to Mozilla Firefox.
795
NTP-G363 Provisioning LSE on Cards
Type about:config in the Address bar.

Type TLS in the Search box.
Enter the value for security.tls.version.max as 0, 1, 2, 3, where 0 refers to SSL 3.0, 1 refers to TLS
1.0, 2 refers to TLS 1.1, 3 refers to TLS 1.2, and so on.
Enter the value for security.tls.version.min as 0, 1, 2,3, where 0 refers to SSL 3.0, 1 refers to TLS
1.0, 2 refers to TLS 1.1, 3 refers to TLS 1.2, and so on.
Click OK twice.
NTP-G363 Provisioning LSE on Cards

Purpose This procedure provisions Locally Significant
Certificates (LSCs) on the WSE and MR-MXP cards.
Onsite/Remote Remote
Note You cannot provision LSCs on MR-MXP trunk cards configured in the 100G-B2B mode.
Procedure
Step 1 Complete DLP-G803 Installing Locally Significant Certificates on Cards, on page 797, as needed.
Step 2 Complete DLP-G804 Switching Between LSC and MIC on Cards, on page 798, as needed.
Step 3 Complete DLP-G805 Viewing Certificates , on page 799, as needed.
796
DLP-G803 Installing Locally Significant Certificates on Cards
DLP-G803 Installing Locally Significant Certificates on Cards

Purpose This task provisions the generation of a CSR and
installation of Locally Significant Certificates (LSCs)
on the WSE and MR-MXP cards.

Secure the Shell Access and EMS Access.
1. In the node view, click Provisioning > Security
> Access.
2. Change the Access State of Shell Access, and
EMS Access to Secure State.
3. Click Apply.
Procedure
Step 1 In the node view (single-shelf mode) or shelf view (multishelf view), click Provisioning > Certificate
> Certificate tabs.
Step 2 To generate the CSR file, perform the following steps:
Click Generate.
The Generate Certificate dialog box appears.
Select the Shelf ID, Slot ID, Encryption Algorithm, and Hashing from the drop-down lists.
Enter the name in the Common Name text box.
This name must be the same on both the near-end and far-end WSE or MR-MXP cards.
(Optional) Click Additional Details.
Enter the Country Name, State Name, Locality Name, Organization Name, Organization Unit Name,
and Mail ID in the corresponding text box.
Click Ok.
Note When the user changes the Shelf ID of SSC through the LCD, the shelf and slot numbers for all
the LSC entries of WSE or MR-MXP cards in a shelf might not be updated. The shelf and slot
numbers might report as Not Applicable (N/A). It is recommended to reset the WSE or MR-MXP
card or to delete the LSC entry and create it again.
After the CSR file is generated, you can view the certificate details by right-clicking on it and selecting
View Details.
If the CSR generation fails, the Comments/Errors field is updated.
797
DLP-G804 Switching Between LSC and MIC on Cards
Step 3 To export the CSR file, perform the following steps:

Select the certificate and click Export. The
Certificate Export dialog box appears.
Click Browse to navigate to a local or network drive where you want to save the file.
Select the File Type from the drop-down list.
Click Ok.
The exported certificate is sent to the Certification Authority (CA) for generation of the LSC.
Step 4 To import the locally signed certificates from local or network drive into the system, perform the
following steps:
Select the certificate and click Import. The
Certificate Import dialog box appears.
Select the Certificate Format and No. of Files from the drop-down lists.
Browse and select the files.
Import the signed files in this sequence: SUDI, MID, and ROOT files.
Click Ok.
If the certificate import fails, the Comments/Errors field is updated.
Step 5 To install and switch to the locally signed certificates in the line card, perform the following steps:
Select the certificate and click Install & Switch.
The Certificate Install & Switch warning message is displayed.
Check the Auto delete after Install check box to auto-delete the entries after installation.
Click Ok.
The certificate undergoes a verification phase where the expired certificates are not installed. If the
verification is successful, the certificate is installed in the line card. After installation, it switches
from the MIC certificate to the LSC certificate.
DLP-G804 Switching Between LSC and MIC on Cards

Purpose To switch between the Manufacturing Installed
Certificate (MIC) and Locally Significant Certificate
(LSC) on the WSE or MR-MXP card.

DLP-G803 Installing Locally Significant Certificates
on Cards, on page 797
798
DLP-G805 Viewing Certificates
Note When the certificate option is switched from MIC to LSC on the client or server MR-MXP card, there is a
peer certification mismatch between the client and server MR-MXP cards. This causes the PEER-CERT-
VERIFICATION-FAILED alarm to be raised on the client MR-MXP card.
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the WSE or MR-MXP card
where you want to change the certificate being used. The card view appears.
Step 2 In the card view, click Provisioning > Certificate > Maintenance tabs.
Step 3 In the Certificate Options area:
Click the Use LSC (Locally Significant Certificate) radio button to switch to LSC for the WSE or
MR-MXP card.
NoteThe LSC-NOT-PRESENT-MIC-IN-USE alarm is raised when the LSC is not installed on the
card and this option is selected in CTC. To generate and install the LSC, see DLP-G803
Installing Locally Significant Certificates on Cards, on page 797.
Click the Use MIC (Manufacturing Installed Certificate) radio button to switch to MIC for the WSE
or MR-MXP card.
Step 4 Click Apply.


Purpose This task enables you to view the details of the
Manufacturing Installed Certificate (MIC) or Locally
Significant Certificate (LSC) that is in use on the WSE
or MR-MXP card.

#unique_666
799
Procedure
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the WSE or MR-MXP
card.The card view appears.
Step 2 In the card view, click Provisioning > Certificate > Detailstabs.
The Certificate List Details area displays the certificate type (MIC/LSC) that is in use. You can choose a
level and view the certificate (in X.509 format) for that level.
800
APPENDIX A
Configuring GE_XP, 10GE_XP, GE_XPE,
and 10GE_XPE Cards Using PCLI
The information in this chapter is in a new location. See Configure GE_XP, 10GE_XP, GE_XPE, and
10GE_XPE Cards Using PCLI for information on how to provision GE_XP, 10GE_XP, GE_XPE,
and 10GE_XPE cards using Pseudo Command Line Interface (PCLI).
801
Configuring GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards Using PCLI
Configuring GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards Using PCLI
802
APPENDIX B
Pseudo Command Line Interface Reference
The information in this chapter is in a new location. See Pseudo Command Line Interface Reference for
information related to Pseudo-IOS command line interface (PCLI) for GE_XP, 10GE_XP, GE_XPE,
and 10GE_XPE cards.
803
804
APPENDIX C
Card Features
This chapter describes features common to the Cisco ONS 15454 suite of cards.
Note The cards described in this chapter are supported on the Cisco ONS 15454, Cisco ONS 15454 M6, Cisco
ONS 15454 M2 platforms, unless noted otherwise.
Note In this chapter, “RAMAN-CTP” refers to the 15454-M-RAMAN-CTP card. “RAMAN-COP” refers to
the 15454-M-RAMAN-COP card.
Note In this chapter, “100G-LC-C card” refers to the 15454-M-100G-LC-C card. “10x10G-LC” refers to the
15454-M-10x10G-LC card. “CFP-LC” refers to the 15454-M-CFP-LC card.

Automatic Laser Shutdown, on page 811
Card-Level Indicators, on page 811
Port-Level Indicators, on page 815
Client Interface, on page 821
DWDM Interface, on page 822
DWDM Trunk Interface, on page 822
FEC, on page 823
Timing Synchronization, on page 826
Multiplexing Function, on page 828
SONET/SDH Overhead Byte Processing, on page 828
Client Interface Monitoring, on page 828
Jitter, on page 829
Lamp Test, on page 829
805
Card Features
Safety Labels
NTP-G335 Performing Lamp Test, on page 829

Onboard Traffic Generation, on page 830
Performance Monitoring, on page 830
Distance Extension, on page 830
Interoperability with Cisco MDS Switches, on page 830
Client and Trunk Ports, on page 830
Automatic Power Control, on page 831
Alarms and Thresholds, on page 831
Card Protection, on page 831
Far-End Laser Control, on page 837
Jitter Considerations, on page 838
Termination Modes, on page 838
Safety Labels
This section explains the significance of the safety labels attached to some cards. The faceplates of the
cards are clearly labeled with warnings about the laser radiation levels. You must understand all warning
labels before working on these cards.
Class 1 Laser Product Cards

The TCC2, TCC2P, TCC3, TNC, TNCE, TSC, TSCE, TNCS, OSCM, OSC-CSM, 32MUX-O, 32DMX-O,
4MD-xx.x, MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, ADM-10G,
GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, and OTU2_XP cards are Class 1 laser products.
The labels that appear on these cards are described in the following sections.
Class 1 Laser Product Label

The Class 1 Laser Product label is shown in the following figure.
Figure 49: Class 1 Laser Product Label
Class 1 lasers are products whose irradiance does not exceed the Maximum Permissible Exposure (MPE) value.
Therefore, for Class 1 laser products the output power is below the level at which it is believed eye damage will
occur. Exposure to the beam of a Class 1 laser will not result in eye injury and can therefore be considered safe.
However, some Class 1 laser products might contain laser systems of a higher Class but there are adequate
engineering control measures to ensure that access to the beam is not reasonably likely. Anyone
806
Card Features
Hazard Level 1 Label
who dismantles a Class 1 laser product that contains a higher Class laser system is potentially at risk
of exposure to a hazardous laser beam.
Hazard Level 1 Label

The Hazard Level 1 label is shown in the following figure. This label is displayed on the faceplate of
the cards.
Figure 50: Hazard Level Label
The Hazard Level label warns users against exposure to laser radiation of Class 1 limits calculated in
accordance with IEC60825-1 Ed.1.2.
Laser Source Connector Label

The Laser Source Connector label is shown in the following figure.
Figure 51: Laser Source Connector Label
This label indicates that a laser source is present at the optical connector where the label has been placed.
FDA Statement Labels

The FDA Statement labels are shown in the following figures. These labels show compliance to FDA
standards and that the hazard level classification is in accordance with IEC60825-1 Am.2 or Ed.1.2.
Figure 52: FDA Statement Label
807
Card Features
Shock Hazard Label
Shock Hazard Label

The Shock Hazard label is shown in the following figure.
Figure 54: Shock Hazard Label
This label alerts personnel to electrical hazard within the card. The potential of shock hazard exists when
removing adjacent cards during maintenance, and touching exposed electrical circuitry on the card itself.
Class 1M Laser Product Cards

The OPT-PRE, OPT-BST, OPT-BST-E, OPT-BST-L, OPT-AMP-L, OPT-AMP-17-C, OPT-AMP-C, OPT-
RAMP-C, OPT-RAMP-CE, OPT-EDFA-17, OPT-EDFA-24, RAMAN-CTP, RAMAN-COP, EDRA-1-26,
EDRA-1-35, EDRA-2-26, EDRA-2-35, TDC-CC, TDC-FC, PSM, 32WSS, 32WSS-L, 32DMX, 32DMX-L, 40-
DMX-C, 40-DMX-CE, 40-MUX-C, 40-WSS-C, 40-WSS-CE, 40-WXC-C, 80-WXC-C, 16-WXC-FS,
40-SMR1-C, 40-SMR2-C, 17 SMR9 FS, 24 SMR9 FS, 34 SMR9 FS, SMR20 FS, MMU, TXP_MR_10G,
TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, TXP_MR_2.5G, TXPP_MR_2.5G,
MXP_MR_2.5G, MXPP_MR_2.5G, MXP_MR_10DME_C, MXP_MR_10DME_L, 40E-TXP-C, 40ME-
TXP-C, 40G-TXP-C, 40G-MXP-C, 40E-MXP-C, 40ME-MXP-C, AR_MXP, AR_XP, AR_XPE, 100G-
LC-C, 10x10G-LC, CFP-LC, 100G-CK-C, 100ME-CKC, 100GS-CK-LC, 100GS-CK-C, 200G-CK-LC,
400G-XP-LC, 17 SMR9 FS, 24 SMR9 FS, 34 SMR9 FS, SMR20 FS, SMR20 FS CV, 12-AD-FS, 16-AD-
FS, and MR-MXP cards are Class 1M laser products.
The labels that appear on these cards are described in the following subsections.
Class 1M Laser Product Statement

The Class 1M Laser Product statement is shown in the following figure.
808
Card Features
Hazard Level 1M Label
Figure 55: Class 1M Laser Product Statement
Class 1M lasers are products that produce either a highly divergent beam or a large diameter beam.
Therefore, only a small part of the whole laser beam can enter the eye. However, these laser products can
be harmful to the eye if the beam is viewed using magnifying optical instruments.
Hazard Level 1M Label

The Hazard Level 1M label is shown in the following figure. This label is displayed on the faceplate of
the cards.
Figure 56: Hazard Level Label
The Hazard Level label warns users against exposure to laser radiation of Class 1 limits calculated in
accordance with IEC60825-1 Ed.1.2.
Laser Source Connector Label

The Laser Source Connector label is shown in the following figure.
Figure 57: Laser Source Connector Label
This label indicates that a laser source is present at the optical connector where the label has been placed.
FDA Statement Labels

The FDA Statement labels are shown in the following figures. These labels show compliance to FDA
standards and that the hazard level classification is in accordance with IEC60825-1 Am.2 or Ed.1.2.
809
Card Features
Shock Hazard Label
Shock Hazard Label

The Shock Hazard label is shown in the following figure.
Figure 60: Shock Hazard Label
This label alerts personnel to electrical hazard within the card. The potential of shock hazard exists when
removing adjacent cards during maintenance, and touching exposed electrical circuitry on the card itself.
Burn Hazard Label

The burn hazard label is shown in the following figure.
Figure 61: Burn Hazard Label
This label is displayed on the RAMAN-CTP and RAMAN-COP cards. The label alerts personnel against skin
exposure to radiation that may cause burns. The potential of the burn hazard exists during handling of fibers.
810
Card Features

The Automatic Laser Shutdown (ALS) procedure is supported on both client and trunk interfaces. On the
client interface, ALS is compliant with ITU-T G.664 (6/99). On the data application and trunk interface,
the switch on and off pulse duration is greater than 60 seconds and is user-configurable.
For information on ALS provisioning, refer the following procedures, as necessary:
DLP-G203 Changing the ALS Maintenance Settings for OSCM and OSC-CSM Cards
DLP-G322 Changing the ALS Maintenance Settings for OPT-BST Card
Card-Level Indicators
Multiple colored LEDs indicate the status of the card.
Card-level LEDs for Transponder, Muxponder and Control Cards

The following table lists the three card-level LEDs on the following cards:
TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE/TNCS
TXP_MR_10G and TXP_MR_10E
TXP_MR_10E_C and TXP_MR_10E_L
TXP_MR_2.5G and TXPP_MR_2.5G
40E-TXP-C and 40ME-TXP-C
MXP_2.5G_10G and MXP_2.5G_10E
MXP_2.5G_10E_C and MXP_2.5G_10E_L
MXP_MR_2.5G and MXPP_MR_2.5G
ADM-10G
OTU2_XP
TXP_MR_10EX_C
MXP_2.5G_10EX_C
MXP_MR_10DMEX_C
PSM
811
Card Features
Card-level LEDs on the AIC-I Card
TDC-CC and TDC-FC

AR_MXP, AR_XP, and AR_XPE
100G-LC-C, 10x10G-LC, CFP-LC, 100G-ME-C, 100G-CK-C, 100GS-CK-LC, , 200G-CK-LC,
100ME-CKC, 400G-XP-LC
Table 302: Card-Level Indicators
Card-Level LED Description
FAIL LED (Red) Red indicates that the card’s processor is not ready.
This LED is on during reset. The FAIL LED flashes
during the boot process. Replace the card if the red
FAIL LED persists.
ACT/STBY LED Green indicates that the card is operational (one or

both ports active) and ready to carry traffic.
Green (Active)
Amber indicates that the card is operational and in
Amber (Standby)
standby (protect) mode.
SF LED (Amber) Amber indicates a signal failure or condition such as

loss of signal (LOS), loss of frame (LOF), or high bit
error rates (BERs) on one or more of the card’s ports.
The amber SF LED is also illuminated if the transmit
and receive fibers are incorrectly connected. If the
fibers are properly connected and the link is working,
the LED turns off.
Card-level LEDs on the AIC-I Card

Table 303: Card-Level Indicators on the AIC-I Card
Card-Level LEDs Description
Red FAIL LED Indicates that the card’s processor is not ready. The
FAIL LED is on during reset and flashes during the
boot process. Replace the card if the red FAIL LED
persists.
Green ACT LED Indicates the AIC-I card is provisioned for operation.
Green/Red PWR A LED The PWR A LED is green when a supply voltage
within a specified range has been sensed on supply
input A. It is red when the input voltage on supply
input A is out of range.
Green/Red PWR B LED The PWR B LED is green when a supply voltage
within a specified range has been sensed on supply
input B. It is red when the input voltage on supply
input B is out of range.
812
Card Features
Card-level LEDs on the MS-ISC-100T Card
Yellow INPUT LED The INPUT LED is yellow when there is an alarm
condition on at least one of the alarm inputs.
Yellow OUTPUT LED The OUTPUT LED is yellow when there is an alarm
condition on at least one of the alarm outputs.
Green RING LED The RING LED on the local orderwire (LOW) side
is flashing green when a call is received on the LOW.
Green RING LED The RING LED on the express orderwire (EOW) side
is flashing green when a call is received on the EOW.
Card-level LEDs on the MS-ISC-100T Card

Table 304: Card-Level Indicators on the MS-ISC-100T Card
FAIL LED (Red) The red FAIL LED indicates that the card processor
is not ready or that a catastrophic software failure
occurred on the card. As part of the boot sequence,
the FAIL LED is turned on until the software deems
the card operational.
ACT LED (Green) The green ACT LED provides the operational status
of the card. If the ACT LED is green, it indicates that
the card is active and the software is operational.
Card-level LEDs on the Multiplexer, Demultiplexer and Optical Amplifier Cards

The following table lists the card-level LEDs on the following cards:
32MUX-O and 32DMX-O
4MD-xx.x
OPT-PRE, OPT-BST, OPT-BST-E, and OPT-BST-L
OPT-AMP-L, OPT-AMP-17-C, and OPT-AMP-C
OPT-RAMP-C and OPT-RAMP-CE
32WSS and 32WSS-L
32DMX, 32DMX-L, 40-DMX-C, 40-DMX-CE, and 40-MUX-C
40-WSS-C, 40-WSS-CE, 40-WXC-C, 80-WXC-C, and 16-WXC-FS
40-SMR1-C, 40-SMR2-C, 17 SMR9 FS, 24 SMR9 FS, 34 SMR9 FS, and SMR20 FS
MMU
813
Card Features
Card-level LEDs on OSCM and OSC-CSM Cards
OPT-EDFA-17 and OPT-EDFA-24

EDRA-1-26, EDRA-1-35, EDRA-2-26, and EDRA-2-35
Table 305: Card-Level Indicators
Card-Level Indicators Description
Red FAIL LED The red FAIL LED indicates that the card’s processor
is not ready or that there is an internal hardware
failure. Replace the card if the red FAIL LED persists.
Green ACT LED The green ACT LED indicates that the card is carrying
traffic or is traffic-ready.
Amber SF LED The amber SF LED indicates a signal failure on one

or more of the card’s ports. The amber SF LED also
illuminates when the transmit and receive fibers are
incorrectly connected. When the fibers are properly
connected, the light turns off.
Card-level LEDs on OSCM and OSC-CSM Cards

Table 306: Card-Level Indicators on the OSCM and OSC-CSM Cards
Card-Level Indicators Description
Red FAIL LED The red FAIL LED indicates that the card’s processor
is not ready or that there is an internal hardware
failure. Replace the card if the red FAIL LED persists.
Green ACT LED The green ACT LED indicates that the OSCM or
OSC-CSM is carrying traffic or is traffic-ready.
Amber SF LED The amber SF LED indicates a signal failure or

condition such as loss of signal (LOS), loss of frame
alignment (LOF), line alarm indication signal (AIS-L),
or high BER on one or more of the card’s ports. The
amber signal fail (SF) LED also illuminates when the
transmit and receive fibers are incorrectly connected.
When the fibers are properly connected, the light turns
off.
814
Card Features
Port-Level Indicators
Port-Level Indicators
Port-level LEDs
For the following cards, the status of the card ports is indicated on the LCD screen of the ONS 15454 fan-
tray assembly that displays the number and severity of alarms for a given port or slot.
OPT-PRE, OPT-BST, OPT-BST-E, and OPT-BST-L
OPT-AMP-L, OPT-AMP-17-C, and OPT-AMP-C
OPT-RAMP-C and OPT-RAMP-CE
RAMAN-CTP and RAMAN-COP
EDRA-1-26, EDRA-1-35, EDRA-2-26, and EDRA-2-35
OSCM and OSC-CSM
32MUX-O and 32DMX-O
4MD-xx.x
32WSS and 32WSS-L
32DMX, 32DMX-L, 40-DMX-C, 40-DMX-CE, and 40-MUX-C
40-WSS-C, 40-WSS-CE, 40-WXC-C, 80-WXC-C, and 16-WXC-FS
40-SMR1-C, 40-SMR2-C, 17 SMR9 FS, 24 SMR9 FS, 34 SMR9 FS, and SMR20 FS
MMU
OPT-EDFA-17 and OPT-EDFA-24
In some cards, multiple colored LEDs indicate the status of the port.
Port-Level LEDs for AR_MXP, AR_XP, and AR_XPE cards depend on the configured card mode.
The following table lists the port-level LEDs on the following cards:
TXP_MR_10E, TXP_MR_10E_C, and TXP_MR_10E_L
TXP_MR_2.5G and TXP_MR_10EX_C
40E-TXP-C and 40ME-TXP-C
MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, and MXP_2.5G_10EX_C
815
Card Features
Port-level LEDs on the TXP_MR_10G and MXP_2.5G_10G Cards
Table 307: Port-Level Indicators
Port-Level LED Description
Green Client LED The green Client LED indicates that the client port is
in service and that it is receiving a recognized signal.
The MXP_2.5G_10E, MXP_2.5G_10E_C,
MXP_2.5G_10E_L, and MXP_2.5G_10EX_C cards
have four client ports, and so have four client LEDs.
Green DWDM LED The green DWDM LED indicates that the DWDM
port is in service and that it is receiving a recognized
signal.
Port-level LEDs on the TXP_MR_10G and MXP_2.5G_10G Cards

Table 308: Port-Level Indicators on the TXP_MR_10G and MXP_2.5G_10Gcards
The MXP_2.5G_10G card has four client ports, and
so has four client LEDs.
port is in service and that it is receiving a recognized
signal.
Green Wavelength 1 LED Each port supports two wavelengths on the DWDM
side. Each wavelength LED matches one of the
wavelengths. This LED indicates that the card is
configured for Wavelength 1.
Green Wavelength 2 LED Each port supports two wavelengths on the DWDM
side. Each wavelength LED matches one of the
wavelengths. This LED indicates that the card is
configured for Wavelength 2.
Port-level LEDs on the TXPP_MR_2.5G Card

Table 309: Port-Level Indicators on the TXPP_MR_2.5G card
816
Card Features
Port-level LEDs on the GE_XP, 10DME and 40G Cards
Green DWDM A LED The green DWDM A LED indicates that the DWDM
A port is in service and that it is receiving a
recognized signal.
Green DWDM B LED The green DWDM B LED indicates that the DWDM
B port is in service and that it is receiving a recognized
signal.
Port-level LEDs on the GE_XP, 10DME and 40G Cards

The following table lists the port-level LEDs on the following cards:
MXP_MR_10DME_C, MXP_MR_10DME_L, and MXP_MR_10DMEX_C

Port LEDs (eight LEDs, four for each group, one Green—The client port is either in service and
for each SFP/XFP) receiving a recognized signal (that is, no signal fail),
or Out of Service and Maintenance (OOS,MT or
Green/Red/Amber/Off
locked, maintenance) in which case the signal fail
and alarms will be ignored.
Red—The client port is in service but is receiving
a signal fail (LOS).
Amber—The port is provisioned and in a
standby state.
Off—The SFP is either not provisioned, out of service,
not properly inserted, or the SFP hardware has failed.
port is in service and that it is receiving a
recognized signal.
817
Card Features
Port-level LEDs on the MXP_MR_2.5G and MXPP_MR_2.5G Cards
Port-level LEDs on the MXP_MR_2.5G and MXPP_MR_2.5G Cards

Table 311: Port-Level Indicators on the MXP_MR_2.5G and MXPP_MR_2.5G cards
Client LEDs (eight LEDs) Green indicates that the port is carrying traffic (active)
on the interface. Amber indicates that the port is
carrying protect traffic (MXPP_MR_2.5G). Red
indicates that the port has detected a loss of signal.
DWDM LED (MXP_MR_2.5G) Green indicates that the card is carrying traffic (active)
on the interface.
Green (Active)
A red LED indicates that the interface has detected
Red (LOS)
an LOS or LOC.
DWDMA and DWDMB LEDs (MXPP_MR_2.5G) Green indicates that the card is carrying traffic (active)
on the interface.
Green (Active)
When the LED is amber, it indicates that the interface
Amber (Protect Traffic) is carrying protect traffic in a splitter protection card
Red (LOS) (MXPP_MR_2.5G).
A red LED indicates that the interface has detected
an LOS or LOC.
Port-level LEDs on the ADM-10G and OTU2_XP Cards
Note Client or trunk ports can each be in active or standby mode as defined in the related section for each specific
protection type. For example, fiber-switched protection has active or standby trunk ports; 1+1 APS protection
has active or standby client ports, and client 1+1 protection does not utilize active or standby ports.
Table 312: Port-Level Indicators on the ADM-10G and OTU2_XP cards (client and trunk ports)
Port-Level Status Tri-color LED Description

The port-level LED is active and unprotected. If a port is in OOS/locked state for any reason,
the LED is turned off.
If a port is in IS/unlocked state and the PPM is
preprovisioned or is physically equipped with
no alarms, the LED is green.
If a port is in IS state and the PPM is physically
equipped but does have alarms, the LED is red.
818
Card Features
Port-level LEDs on the 100G-LC-C, 10x10G-LC, CFP-LC, 100GS-CK-LC, 200G-CK-LC, 100G-CK-C, 100G-ME-C, 100ME-CKC, and 400G-XP-LC Cards
Port-Level Status Tri-color LED Description

The port-level LED is in standby. If a port is in OOS/locked state for any reason,
the LED is turned off.
If a port is in the IS/unlocked state and the PPM
is preprovisioned or is physically equipped
with no alarms, the LED is amber.
If a port is in IS state and physically equipped but
does have alarms, the LED is red.
Port-level LEDs on the 100G-LC-C, 10x10G-LC, CFP-LC, 100GS-CK-LC,

200G-CK-LC, 100G-CK-C, 100G-ME-C, 100ME-CKC, and 400G-XP-LC Cards
Port LEDs ( Green—The client port is either in service and

receiving a recognized signal (that is, no signal fail),
Green/Red/Amber/Off or Out of Service and Maintenance (OOS,MT or
locked, maintenance) in which case the signal fail and
alarms will be ignored.
Red—The client port is in service but is receiving a
signal fail (LOS).
Amber—The port is provisioned and in a standby
state.
Off—The pluggable is either not provisioned, out of
service, not properly inserted, or the pluggable
hardware has failed.
DWDM LED Green indicates that the card is carrying traffic (active)
on the interface.
Green (Active)
When the LED is amber, it indicates that the interface
Amber (Protect Traffic)
is carrying protect traffic in a splitter protection card.
Red (LOS) A red LED indicates that the interface has detected
an LOS or LOF.
819
Card Features
Power-level LEDs on the Control Cards
Power-level LEDs on the Control Cards

Table 314: Power-Level Indicators on the Control Cards
Power-Level LEDs Definition
Green/Amber/Red PWR A LED The PWR A LED is green when the voltage on supply
input A is between the low battery voltage
(LWBATVG) and high battery voltage (HIBATVG)
thresholds. The LED is amber when the voltage on
supply input A is between the high battery voltage
and extremely high battery voltage (EHIBATVG)
thresholds or between the low battery voltage and
extremely low battery voltage (ELWBATVG)
thresholds. The LED is red when the voltage on supply
input A is above extremely high battery voltage or
below extremely low battery voltage thresholds.
Green/Amber/Red PWR B LED The PWR B LED is green when the voltage on supply
input B is between the low battery voltage and high
battery voltage thresholds. The LED is amber when
the voltage on supply input B is between the high
battery voltage and extremely high battery voltage
thresholds or between the low battery voltage and
extremely low battery voltage thresholds. The LED
is red when the voltage on supply input B is above
extremely high battery voltage or below extremely
low battery voltage thresholds.
Note The power-level LEDs are either green or red. The LED is green when the voltage on supply inputs is
between the extremely low battery voltage and extremely high battery voltage thresholds. The LED is red
when the voltage on supply inputs is above extremely high battery voltage or below extremely low battery
voltage thresholds.
Network-level LEDs on the Control Cards

Table 315: Network-Level Indicators on the Control Cards
System-Level LEDs Definition
Red CRIT LED Indicates critical alarms in the network at the local
terminal.
Red MAJ LED Indicates major alarms in the network at the local
terminal.
Yellow MIN LED Indicates minor alarms in the network at the local
terminal.
820
Card Features
Ethernet Port-level LEDs on the Control Cards
System-Level LEDs Definition
Red REM LED Provides first-level alarm isolation. The remote (REM)
LED turns red when an alarm is present in one or more
of the remote terminals.
Green SYNC LED Indicates that node timing is synchronized to an

external reference.
Green ACO LED After pressing the alarm cutoff (ACO) button, the
ACO LED turns green. The ACO button opens the
audible alarm closure on the backplane. ACO is
stopped if a new alarm occurs. After the originating
alarm is cleared, the ACO LED and audible alarm
control are reset.
Ethernet Port-level LEDs on the Control Cards

Table 316: Ethernet Port-Level Indicators on the TNC/TNCE/TSC/TSCE/TNCS Cards
Port-Level LEDs Definition
Green LINK LED Indicates the connectivity status.
Amber ACT LED Indicates data reception.
SFP LEDs on TNC, TNCE, and TNCS Cards

Table 317: TNC, TNCE, and TNCS SFP Indicators
Port Type Link LED Activity LED
OC3 • RED - No link —

• GREEN - Link
FE • RED - No link Blinks on packet flow

• GREEN - Link
GE • RED - No link Blinks on packet flow

• GREEN - Link
Client Interface
The client interface in TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, and TXP_MR_10EX_C cards is
implemented with a separately orderable XFP module. The module is a tri-rate transceiver, providing a
821
Card Features
DWDM Interface
single port that can be configured in the field to support an OC-192 SR-1 (Telcordia GR-253-CORE) or
STM-64 I-64.1 (ITU-T G.691) optical interface, as well as 10GE LAN PHY (10GBASE-LR), 10GE
WAN PHY (10GBASE-LW), 10G FC signals or IB_5G signals (TXP_MR_10EX_C only).
The client side XFP pluggable module supports LC connectors and is equipped with a 1310-nm laser.
The MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, and MXP_2.5G_10EX_C cards provide four
intermediate- or short-range OC-48/STM-16 ports per card on the client side. Both SR-1 or IR-1 optics can be
supported and the ports use SFP connectors. The client interfaces use four lasers of 1310-nm wavelength.
The client interface in AR_MXP, AR_XP, and AR_XPE cards are implemented with a separately orderable
XFP/SFP module. The module can be single-rate or tri-rate transceiver, providing a single port that can be
configured in the field to support available payloads. For the list of supported payloads, see the section.
DWDM Interface
The MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, and MXP_2.5G_10EX_C cards serve as
an OTN multiplexer, transparently mapping four OC-48 channels asynchronously to ODU1 into one 10-
Gbps trunk. The tunable wavelengths for the DWDM trunk is as follows:
MXP_2.5G_10E—Tunable for transmission over four wavelengths in the 1550-nm, ITU 100-GHz
spaced channel grid.
MXP_2.5G_10E_C and MXP_2.5G_10EX_C—Tunable for transmission over the entire C-band and
the channels are spaced at 50-GHz on the ITU grid.
MXP_2.5G_10E_L—Tunable for transmission over the entire L-band and the channels are spaced at
50-GHz on the ITU grid.
AR_MXP, AR_XP, and AR_XPE—The wavelengths for the DWDM trunk is based on the pluggable.
100G-LC-C, 10X10G-LC, CFP-LC, 100G-ME-C, 100GS-CK-LC, 200G-CK-LC, 100G-CK-C,
and 100ME-CKC—Tunable on 96 wavelength channels spaced at 50-GHz on the ITU grid over
the entire C band.
Caution You must use a 20-dB fiber attenuator (15 to 25 dB) when working with the
card in a loopback on the trunk port. Do not use direct fiber loopbacks as it can
cause irreparable damage to the card.
Note On the MXP_2.5G_10EX_C card, you cannot disable ITU-T G.709 on the
trunk side. If ITU-T G.709 is enabled, then FEC cannot be disabled.

On the trunk side, the TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, and TXP_MR_10EX_C cards
provide a 10-Gbps STM-64/OC-192 interface. There are four tunable channels available in the 1550-nm band or
eight tunable channels available in the 1580-nm band on the 50-GHz ITU grid for the DWDM interface.
822
Card Features
FEC
The card provides 3R (retime, reshape, and regenerate) transponder functionality for this 10-Gbps
trunk interface. Therefore, the card is suited for use in long-range amplified systems. The DWDM
interface is complaint with ITU-T G.707, ITU-T G.709, and Telcordia GR-253-CORE standards.
The DWDM trunk port operates at a rate that is dependent on the input signal and the presence or absence
of the ITU-T G.709 Digital Wrapper/FEC. The possible trunk rates are:
OC192 (9.95328 Gbps)
OTU2 (10.70923 Gbps)
10GE (10.3125 Gbps) or 10GE into OTU2 (ITU G.sup43 11.0957 Gbps)
10G FC (10.51875 Gbps) or 10G FC into OTU2 (nonstandard 11.31764 Gbps)
(TXP_MR_10EX_C only) Proprietary rate at the trunk when the client is provisioned as IB_5G.
regenerators is nominally rated at 23 dB over C-SMF fiber. This rating is not a product specification, but is
given for informational purposes. It is subject to change.
On the trunk side, the AR_MXP, AR_XP, and AR_XPE cards provide a 10-Gbps OTU2 or 2.5-Gbps
OTU1 or 4-Gbps FC interfaces. The trunk wavelength can be tuned to any C-band wavelength, based on
the pluggable inserted. The card provides 3R (retime, reshape, and regenerate) transponder functionality for
this 10-Gbps trunk interface. Therefore, the card is suited for use in the long-range amplified systems. The
DWDM interface is complaint with ITU-T G.707, ITU-T G.709, and Telcordia GR-253-CORE standards.
The DWDM trunk port operates at a rate that is dependent on the input signal and the presence or absence
of the ITU-T G.709 Digital Wrapper/FEC.
regenerators is nominally rated at 23 dB over C-SMF fiber. This rating is not a product specification, but is
given for informational purposes. It is subject to change.
FEC
Forward error correction (FEC) is a feature used for controlling errors during data transmission. This
feature works by adding data redundancy to the transmitted message using an algorithm. This redundancy
allows the receiver to detect and correct a limited number of errors occurring anywhere in the message,
instead of having to ask the transmitter to resend the message.
FEC Modes for the TXP_MR_10E and MXP_2.5G_10E Cards

For the TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, MXP_2.5G_10E, MXP_2.5G_10E_C,
MXP_2.5G_10E_L, TXP_MR_10EX_C, or MXP_2.5G_10EX_C card, you can configure the forward
error correction in three modes: NO FEC, FEC, and E-FEC modes.
The E-FEC mode has a higher level of error detection and correction than the FEC mode. As a result, using
the E-FEC mode allows higher sensitivity (that is, a lower optical signal-to-noise ratio [OSNR]) with a
lower bit error rate than what the FEC mode allows. The E-FEC mode also enables longer distance trunk-
side transmission than what the FEC enables.
The output bit rate is always 10.7092 Gbps as defined in the ITU-T G.709 standard, but the error coding
performance can be provisioned in this way:
823
Card Features
FEC Modes for the AR_MXP, AR_XP and AR_XPE Cards
NO FEC—No forward error correction

FEC—Standard ITU-T G.975 Reed-Solomon algorithm
E-FEC—Standard ITU-T G.975.1 I.7, two orthogonally concatenated BCH super FEC code. This FEC
scheme contains three parameterizations of a single scheme of two orthogonally interleaved BCH.
The constructed code is decoded iteratively to achieve the expected performance.
FEC Modes for the AR_MXP, AR_XP and AR_XPE Cards

For the AR_MXP, AR_XP, and AR_XPE cards you can configure forward error correction on 10 Gbps trunk
XFP ports in four modes: NO FEC, FEC, I.4 E-FEC, and I.7 E-FEC. The 2.5Gbps SFP OTN ports have only two
modes of operation: NO FEC and FEC. The output bit rate varies depending on the provisioned payload and the
configured FEC. The details of the error-coding performance that can be provisioned are:
NO FEC—No forward error correction
FEC—Standard ITU-T G.975 Reed-Solomon algorithm
I.4 E-FEC—Standard G.975.1 I.4 two interleaved codes (RS and BCH) super FEC codes
I.7 E-FEC— Standard G.975.1 I.7 two orthogonally concatenated block (BCH) super FEC codes; this
FEC scheme contains three parameterizations of a single scheme of two BCH codes, with the
constructed code decoded iteratively to achieve expected performance.
Note G.709 OTN is enabled by default for all trunk ports, except for a 4GFC
transponder.
FEC Modes for 100G-LC-C, CFP-LC, 100G-CK-C, 100GS-CK-LC,

200G-CK-LC, and 400G-XP-LC Cards
The cards support multiple FEC modes on its trunk and client interfaces.
FEC—Standard ITU-T G.975 Reed-Solomon algorithm with 7% overhead.
I.7 FEC—Standard G.975.1 I.7 two orthogonally concatenated block (BCH) super FEC codes; this FEC
scheme contains three parameterizations of a single scheme of two BCH codes, with the constructed
code decoded iteratively to achieve expected performance.
Soft Decision FEC—Employs an advanced differential encoding and cycle slip-aware algorithm offering
excellent performance and robustness against high cycle slip rates. The SD-FEC is suitable for applications
where maintaining sufficient signal to noise ratio is important. Examples include long haul and ultra-long
haul 100G transmission, and wavelengths employing high order modulation schemes such as 16QAM.
High Gain FEC—High Gain FEC with 7% or 20% overhead provides better performance than the
standard G.975.1. The HG-FEC is suitable for all applications where 100G wavelengths are passing
through a high number of ROADM nodes, with limited pass-band performance.
824
Card Features
Card Features
Note G.709 OTN is enabled by default for OTU payloads.
Hard Decision FEC—The HD-FEC with 7% overhead can be provisioned on the 100GS-CK-LC and
200G-CK-LC cards to allow trunk interoperability with the 100G-LC-C and 100G-CK-LC (older
Line Cards). The 100GS-CK-LC and 200G-CK-LC cards provisioned with 7% HD-FEC has 0.5dB
better B2B OSNR sensitivity than the 100G-LC-C and 100G-CK-LC cards. This FEC mode is
available for all 100G operating modes.
Table 318: Supported FEC Modes for 100G-LC-C, 10x10G-LC, CFP-LC, 100G-CK-C, 100GS-CK-LC, 200G-CK-LC, and 400G-XP-LC Cards
Card Supported FEC Modes
100G-LC-C • Standard
• 7% High Gain
• 20% High Gain
CFP-LC • GFEC
100G-CK-C • Standard
• 7% High Gain
• 20% High Gain
100GS-CK-LC • Standard
• 7% Hard Decision
• 20% Soft Decision
200G-CK-LC • Standard
• 7% Hard Decision
• 20% Soft Decision
400G-XP-LC • 15% Soft Decision Differential Encoding (DE)

OFF
• 25% Soft Decision Differential Encoding (DE)
OFF
ON
ON
825
Card Features
FEC Threshold Bit Error Correction Values
FEC Threshold Bit Error Correction Values

The maximum bit error correction value in R9.6.0.3 is lesser than the maximum bit error correction value
in earlier releases. During an upgrade to R9.6.0.3, the value of the Bit Errors Corrected does not change. In
CTC, the maximum bit error correction value can be manually reconfigured in the card view > Provisioning
> OTN > FEC Threshold tab using the values provided in the following table.
Table 319: FEC Threshold Bit Error Correction Values
Data Rate Bit Error Correction Frames per Second Bit Error Correction Maximum Bit Error
per Second Correction per 15
Seconds
Releases earlier than R9.6.0.3

Any data rate 122368 82026 10037357568 9033621811200
R9.6.0.3
OTU1 4096 20421 83644416 75279974400
OTU2 4096 82026 335978496 302380646400
OTU3 4096 329492 1349599232 1214639308800
OTU4 4096 856164 3506847744 3156162969600
The TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, TXP_MR_10EX_C, AR_MXP, AR_XP, and
AR_XPE cards can perform ODU2-to-OCh mapping, which allows operators to provision data payloads
in a standard way across 10-Gbps optical links. Additionally, the AR_MXP, AR_XP, and AR_XPE cards
can perform ODU1-to-OCh mapping across 2.5 Gbps optical links.
Digital wrappers that define client side interfaces are called Optical Data Channel Unit 2 (ODU2) entities
in ITU-T G.709. Digital wrappers that define trunk side interfaces are called Optical Channels (OCh) in
ITU-T G.709. ODU2 digital wrappers can include Generalized Multiprotocol Label Switching (G-MPLS)
signaling extensions to ITU-T G.709 (such as Least Significant Part [LSP] and Generalized Payload
Identifier [G-PID] values) to define client interfaces and payload protocols.
The TCC2/TCC2P/TCC3 card performs all system-timing functions for each ONS 15454. The
TNC/TNCE/TSC/TSCE/TNCS card performs all the system-timing functions for the ONS 15454 M2,
ONS 15454 M6, and ONS 15454 M15 shelves.
826
Card Features
Card Features
The control card monitors the recovered clocks from each traffic card and two BITS ports for frequency
accuracy. The control card selects a recovered clock, a BITS, or an internal Stratum 3 reference as the
system-timing reference. You can provision any of the clock inputs as primary or secondary timing sources.
A slow-reference tracking loop allows the control card to synchronize with the recovered clock, which
provides holdover if the reference is lost. The control card supports 64/8K composite clock and 6.312 MHz
timing output.
Note The TNC/TNCE/TSC/TSCE/TNCS card supports the BITS-1 and BITS-2 external timing interfaces on the ONS
15454 M6 and NCS 2015 shelves. The card supports the BITS-1 interface on the ONS 15454 M2 shelf.
The TNC/TNCE/TSC/TSCE/TNCS card supports SNTP operation that allows the nodes to synchronize the
system clock automatically with a reference SNTP server following system reboots, card resets, and
software upgrades.
For more information on the timing function, see Timing Reference document.
The MXP_2.5G_10G card is synchronized to the the control card clock during normal conditions and
transmits the ITU-T G.709 frame using this clock. The control card can operate from an external building
integrated timing supply (BITS) clock, an internal Stratum 3 clock, or from clock recovered from one of the
four valid client clocks. If clocks from both the control cards are not available, the MXP_2.5G_10G card
switches automatically (with errors, not hitless) to an internal 19.44 MHz clock that does not meet SONET
clock requirements. This will result in a clock alarm.
The MXP_2.5G_10E and MXP_2.5G_10EX_C cards are synchronized to the control clock and the
MXP_2.5G_10E_C and MXP_2.5G_10E_L cards are synchronized to the control card clock during
normal conditions and transmits the ITU-T G.709 frame using this clock. No holdover function is
implemented. If neither control clock is available, the cards switch automatically (hitless) to the first of the
four valid client clocks with no time restriction as to how long it can run on this clock. The cards continue
to monitor the control card. If a control card is restored to working order, the cards revert to the normal
working mode of running from the control-card clock. If no valid control-card clock is available and all of
the client channels become invalid, the cards wait (no valid frames processed) until the control card
supplies a valid clock. In addition, the cards can select the recovered clock from one active and valid client
channel and supply that clock to the control card card.
The AR_MXP, AR_XP, and AR_XPE cards are able to transparently transport synchronization and timing
information for payload enveloped within ODU-1 and ODU-2. The AR_MXP and AR_XP cards are
synchronized to the control card clock during normal conditions and transmit the ITU-T G.709 frame using this
clock. The AR_XPE card is synchronized to the control card clock during normal conditions and transmit the
ITU-T G.709 frame using this clock. The AR_MXP, AR_XP, and AR_XPE cards select its synchronization
source between an optical line, an external synchronization input, and the internal source. The optical line can be
either OCN, OTN or Ethernet based. The AR_MXP and AR_XP cards transmit the SyncE information from an
incoming SyncEthernet (ITU-T G.8262 and G.8264 ESMC) signal to the node controller (TNC).
The 100G-LC-C, 10x10G-LC, CFP-LC, 100G-ME-C, 100G-CK-C, and 100ME-CKC cards are
synchronized to TNC/TSC/TNCE/TSCE/TNCS clock during normal conditions and transmits the ITU-T
G.709 frame using this clock.
The 100GS-CK-LC and 200G-CK-LC cards cannot be used as a timing reference source.
Note Only one port per card can be selected as a timing reference. The OTN ports configured as clients shall not
be provisionable as timing source.
827
Card Features
The muxponder is an integral part of the reconfigurable optical add/drop multiplexer (ROADM) network.
The key function of the MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, MXP_2.5G_10EX_C,
AR_MXP, AR_XP, and AR_XPE cards is to multiplex 4 OC-48/STM16 signals onto one ITU-T G.709
OTU2 optical signal (DWDM transmission). The multiplexing mechanism allows the signal to be
terminated at a far-end node by another similar card.
Termination mode transparency on the muxponder is configured using OTUx and ODUx OH bytes. The ITU-T
G.709 specification defines OH byte formats that are used to configure, set, and monitor frame alignment, FEC
mode, section monitoring, tandem connection monitoring, and termination mode transparency.
The card performs ODU to OTU multiplexing as defined in ITU-T G.709. The ODU is the framing
structure and byte definition (ITU-T G.709 digital wrapper) used to define the data payload coming into
one of the SONET/SDH client interfaces on the card. The term ODU1 refers to an ODU that operates at
2.5-Gbps line rate. On the card, four client interfaces can be defined using ODU1 framing structure and
format by asserting an ITU-T G.709 digital wrapper.
The output of the muxponder is a single 10-Gbps DWDM trunk interface defined using OTU2. It is within the
OTU2 framing structure that FEC or E-FEC information is appended to enable error checking and correction.

The MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, MXP_2.5G_10EX_C, AR_MXP,
AR_XP, AR_XPE, 100G-LC-C, 10x10G-LC, CFP-LC, 100G-CK-C, 100GS-CK-LC, 200G-CK-LC,
100G-ME-C, and 100ME-CKC cards pass the incoming SONET/SDH data stream and its overhead bytes
for the client signal transparently. The card can be provisioned to terminate regenerator section overhead.
This is used to eliminate forwarding of unneeded layer overhead. It can help reduce the number of alarms
and help isolate faults in the network.

The following parameters are monitored on the MXP_2.5G_10E, MXP_2.5G_10E_C,
MXP_2.5G_10E_L, MXP_2.5G_10EX_C, AR_MXP, AR_XP, AR_XPE, 100G-LC-C, 10x10G-LC, CFP-
LC, 100G-CK-C, 100GS-CK-LC, , 200G-CK-LC, 100G-ME-C, and 100ME-CKC cards:
Laser bias current is measured as a PM parameter
LOS is detected and signaled
Transmit (TX) and receive (RX) power are monitored
The following parameters are monitored in real time mode (one second):
Optical power transmitted (client)
Optical power received (client)
In case of loss of communication (LOC) at the DWDM receiver or far-end LOS, the client interface
behavior is configurable. AIS can be invoked or the client signal can be squelched.
828
Card Features
Jitter
Jitter
For SONET and SDH signals, the MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L,
MXP_2.5G_10EX_C, AR_MXP, AR_XP, AR_XPE cards comply with Telcordia GR-253-CORE,
ITU-T G.825, and ITU-T G.873 for jitter generation, jitter tolerance, and jitter transfer. For more
information, see the Jitter Considerations, on page 838.
Lamp Test
The MXP_2.5G_10E, MXP_2.5G_10E_C and MXP_2.5G_10E_L, MXP_2.5G_10EX_C, AR_MXP,
AR_XP, AR_XPE, TDC-CC, TDC-FC, TNC, TNCE, TSC, TSCE, TNCS, RAMAN-CTP, and RAMAN-
COP cards support lamp test function activated from the shelf front panel or through CTC to ensure that all
LEDs are functional.
The Lamp Test is run during the initial node turn-up, periodic maintenance routine, identification of
specific cards, or LED testing.
NTP-G335 Performing Lamp Test

Purpose This procedure performs lamp test at the shelf and
card levels.
Security Level Superuser only
Procedure
Step 1 In node view (single-shelf mode) or multishelf view (multishelf mode), click the Maintenance>
Diagnostic tab.
Step 2 Click the Lamp Test button. The Lamp Test dialog box appears.
Step 3 Perform lamp test at the shelf level.
Select the All option.
Click Lamp Test.
Step 4 Perform lamp test at the card level.

• Select the Lamp Test For Slot option
829
Card Features
Choose the required Slot ID or card from the drop-down list.

Click Slot Lamp Test.
Note Cards in pre-provisioned or improper removal state are not listed in the drop-down list.

The MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, and MXP_2.5G_10EX_C cards provide
internal traffic generation for testing purposes according to pseudo-random bit sequence (PRBS),
SONET/SDH, or ITU-T G.709.
Performance Monitoring
GFP-T performance monitoring (GFP-T PM) in MXP_MR_2.5G, MXPP_MR_2.5G, AR_MXP, AR_XP,
AR_XPE, 100G-LC-C, 10x10G-LC, 100G-CK-C, 100GS-CK-LC, 200G-CK-LC, 100G-ME-C, and 100ME-
CKC cards are available via remote monitoring (RMON), and trunk PM is managed according to Telcordia
GR-253-CORE and ITU G.783/826. Client PM is achieved through RMON for FC and GE.
Distance Extension
In MXP_MR_2.5G and MXPP_MR_2.5G cards, buffer-to-buffer credit management scheme provides FC
flow control. When this feature is enabled, a port indicates the number of frames that can be sent to it (its
buffer credit), before the sender is required to stop transmitting and wait for the receipt of a “ready”
indication The MXP_MR_2.5G and MXPP_MR_2.5 cards support FC credit-based flow control with a
buffer-to-buffer credit extension of up to 1600 km (994.2 miles) for 1G FC and up to 800 km (497.1 miles)
for 2G FC. The feature can be enabled or disabled, as necessary.
Interoperability with Cisco MDS Switches

You can provision a string (port name) for each fiber channel/FICON interface on the MXP_MR_2.5G
and MXPP_MR_2.5G cards, which allows the MDS Fabric Manager to create a link association between
that SAN port and a SAN port on a Cisco MDS 9000 switch.
Client and Trunk Ports

The MXP_MR_2.5G card features a 1550-nm laser for the trunk/line port and a 1310-nm or 850-nm laser
(depending on the SFP) for the client ports. The card contains eight 12.5 degree downward tilt SFP modules for
the client interfaces. For optical termination, each SFP uses two LC connectors, which are labeled TX and RX on
the faceplate. In a MXP_MR_2.5G card, the trunk port is a dual-LC connector with a 45 degree
830
Card Features
Automatic Power Control
downward angle. In a MXPP_MR_2.5G card, there are two trunk port connectors (one for working and one
for protect), each a dual-LC connector with a 45-degree downward angle.
Automatic Power Control

A transient gain range of 20 to 23 dB is available to APC in order to permit other amplifiers to reach their
expected set points. However, operation in this range is not continuous. At startup, the OPT-AMP-17-C
card caps the gain at a maximum of 20 dB.
Note When the OPT-AMP-17-C operates as a booster amplifier, APC does not control its gain.
Alarms and Thresholds

The following table lists the alarms and its related thresholds for the OSC-CSM card.
Table 320: Alarms and Thresholds
Port Alarms Thresholds
LINE RX LOS None
LOS-P LOS-P Fail Low
LOS-O LOS-O Fail Low
LINE TX None None
OSC TX OPWR-DEG-HIGH OPWR-DEG-HIGH Th
OPWR-DEG-LOW OPWR-DEG-LOW Th
OPWR-FAIL-LOW OPWR-FAIL-LOW Th
OSC RX None None
COM TX None None
COM RX LOS-P LOS-P Fail Low
Card Protection
Y-Cable and Splitter Protection
Y-cable and splitter protection are two main forms of card protection that are available for TXP, MXP,
AR_MXP, AR_XP, AR_XPE, and Xponder (GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, and OTU2_XP)
831
Card Features
Y-Cable Protection Availability on TXP, MXP, and Xponder Cards
cards when they are provisioned in TXP or MXP mode. Y-cable protection is provided at the client port level.
Splitter protection is provided at the trunk port level.
Note GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards use VLAN protection when they are provisioned in L2-
over-DWDM mode. For more information, see the Layer 2 Over DWDM Protection, on page 837. The ADM-
10G card uses path protection and 1+1 protection. For more information, see the Protection section.
Y-Cable Protection Availability on TXP, MXP, and Xponder Cards

Y-cable protection is available for the following ONS 15454 TXP, MXP, and Xponder cards:
TXP_MR_10G
TXP_MR_10E
TXP_MR_2.5G
40E-TXP-C
40ME-TXP-C
MXP_2.5G_10G
MXP_2.5G_10E
MXP_2.5G_10E_C
MXP_2.5G_10E_L
MXP_MR_2.5G
MXP_MR_10DME_C
MXP_MR_10DME_L
40G-MXP-C
40E-MXP-C
40ME-MXP-C
GE_XP and GE_XPE (when in 10GE or 20GE MXP card mode)
10GE_XP and 10GE_XPE (when in 10GE TXP card mode)
OTU2_XP (when in Transponder card configuration)
AR_MXP
AR_XP
AR_XPE
10x10G-LC (when in TXP-10G or MXP-10G mode)—The client ports of the 10x10G-LC cards are
provisioned with OC192/STM-64, 10GE-LAN, OTU2, OTU2e, 8G FC, and 10G FC payloads.
832
Card Features
Setting-up Y-Cable Protection
Y-cable protection is supported when the 10x10G-LC card is configured in MXP-10x10G operating
mode with 200G-CK-LC card and the 10x10G-LC card is provisioned with 10GE, OC-192/STM-
64 payloads. This configuration uses the ONS-SC+-10G-LR and ONS-SC+-10G-SR pluggables.
Note A hardware reset or a hardware failure of the active 10x10G-LC card configured in
the TXP-10G or MXP-10G mode in a Y-cable configuration causes a protection
switchover that may result in a traffic hit of more than 50 msec.
CFP-LC (when in CFP-TXP mode)—The client ports of the CFP-LC cards are provisioned with 100GE
payloads. This configuration uses only the CFP LR4 pluggable.
CFP-LC (when in CFP-MXP mode)—The client ports of the CFP-LC cards are provisioned with 40GE
payloads. This configuration uses only the CFP LR4 pluggable.
200G-CK-LC (when in TXP-100G mode)—Y-cable protection is supported when the 200G-CK-LC
card is configured in TXP-100G operating mode and the 100G client CPAK ports are provisioned with
100GE payload. This configuration uses the CPAK-100G-LR4 pluggable.
100G-CK-C—The client ports of the 100G-CK-C cards are provisioned with 100GE/OTU4 payloads.
This configuration uses only the CPAK-100G-LR4 pluggable.
100GS-CK-LC and 200G-CK-LC—Y-cable protection is supported in MXP-10x10G operating mode.
Setting-up Y-Cable Protection

To set up Y-cable protection, create a Y-cable protection group for two TXP, MXP, or Xponder cards using
Cisco Transport Controller (CTC). Next, connect the client ports of the two cards physically with a Y-cable. The
single client signal is sent into the RX Y-cable and is split between the two TXP, MXP, or Xponder cards. The
two TX signals from the client side of the TXP, MXP, or Xponder cards are combined in the TX Y-cable into a
single client signal. Only the active card signal passes through as the single TX client signal. CTC automatically
turns off the laser on the protect card to avoid signal interference where the Y-cable joins.
On the GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, and OTU2_XP cards, the Y-cable protection
mechanism is provisionable and can be set ON or OFF (OFF is the default mode).
When a signal fault is detected, the protection mechanism software automatically switches between paths.
Y-cable protection also supports revertive and nonrevertive mode.
When an MXP_MR_2.5G, MXP_MR_10DME_C, MXP_MR_10DME_L, AR_MXP, AR_XP, or
AR_XPE card that is provisioned with Y-cable protection is used on a storage ISL link (ESCON, FC1G,
FC2G, FC4G, FICON1G, FICON2G, FICON4G, or ISC-3 1/2G), a protection switchover resets the
standby port to active. This reset reinitialises the end-to-end link to avoid any link degradation caused due
to loss of buffer credits during switchover and results in an end-to-end traffic hit of 15 to 20 seconds.
When using the MXP_MR_10DME_C or MXP_MR_10DME_L card, enable the fast switch feature and
use it with a Cisco MDS storage switch to avoid this 15 to 20 second traffic hit. When enabling fast switch
on the MXP_MR_10DME_C or MXP_MR_10DME_L card, ensure that the attached MDS switches have
the buffer-to-buffer credit recovery feature enabled.
You can also use the TXP_MR_2.5G card to avoid this 15 to 20 second traffic hit. When a Y-cable
protection switchover occurs, the storage ISL link does not reinitialize and results in an end-to-end traffic
hit of less than 50 ms.
833
Card Features
Card Features
AR_MXP, AR_XP, and AR_XPE cards support Y-cable protection on the client ports, which are part of
an unprotected card mode. The Y-cable protection is not supported for video and auto payloads.
When using the AR_MXP, AR_XP, or AR_XPE card on storage ISL link, use it with a Cisco MDS
storage switch to avoid this 15 to 20 second traffic hit.
When the active AR_MXP, AR_XP, AR_XPE card is removed from the shelf, there is a traffic hit of 60
to 100 ms.
Note Y-cable connectors will not work with electrical SFPs because Y-cables are made up of optical connectors
and it is not possible to physically connect them to an electrical SFP. Y-cable protection is not supported
on IB_5G.
Note There is a traffic hit of up to a of couple hundred milliseconds on the MXP_MR_2.5G and MXP_MR_10DME
cards in Y-cable configuration when a fiber cut or SFP failure occurs on one of the client ports.
Note If you create a GCC on either card of the protect group, the trunk port stays permanently active, regardless
of the switch state. When you provision a GCC, you are provisioning unprotected overhead bytes. The
GCC is not protected by the protect group.
Note Loss of Signal–Payload (LOS-P) alarms, also called Incoming Payload Signal Absent alarms, can occur
on a split signal if the ports are not in a Y-cable protection group.
Note Removing an SFP from the client ports of a card in a Y-cable protection group card causes an
IMPROPRMVL (PPM) alarm. The working and protected port raises the IMPROPRMVL alarm. The
severity on the client ports is changed according to the protection switch state.
Note On the OTU2_XP card, when the 10G Ethernet LAN Phy to WAN Phy conversion feature is enabled, Y-
cable protection is not supported on the LAN to WAN interface (ports 1 and 3).
834
Card Features
Splitter Protection
Note When using fixed DWDM or tunable XFPs for Y-cable protection, the protection switch time may exceed
50 ms.
The following figure shows the Y-cable signal flow.
Figure 62: Y-Cable Protection
Splitter Protection
Splitter protection, shown in the following figure, is provided with TXPP cards, MXPP cards, and
OTU2_XP cards (on trunk ports that are not part of a regenerator group). You can create and delete splitter
protection groups in OTU2_XP card.
To implement splitter protection, a client injects a single signal into the client RX port. An optical splitter
internal to the card then splits the signal into two separate signals and routes them to the two trunk TX
ports. The two signals are transmitted over diverse optical paths. The far-end MXPP or TXPP card uses an
optical switch to choose one of the two trunk RX port signals and injects it into the TX client port. When
using splitter protection with two MXPP or TXPP cards, there are two different optical signals that flow
over diverse paths in each direction. In case of failure, the far-end switch must choose the appropriate
signal using its built-in optical switch. The triggers for a protection switch are LOS, LOF, SF, or SD.
In the splitter protected 10G Ethernet LAN Phy to WAN Phy mode, AIS-P and LOP-P acts as trigger
(when G.709 is enabled) for the Protection Switch, in addition to the existing switching criteria.
In the OTU2_XP card, the STS parameters such as, SF /SD thresholds, Path PM thresholds, and Path Trace is
set for the working path (Port 3). The same parameters are also applicable for the protected path (Port 4).
835
Card Features
1+1 Protection
Figure 63: Splitter Protection
1+1 Protection
The 1+1 protection is available for the GE_XP, GE_XPE, 10GE_XP, and 10GE_XPE cards:
The 1+1 protection is provided in the Layer 2 (L2) card mode to protect against client port and card failure.
1+1 protection is supported in both single shelf and multishelf setup. This means that the working card can
be in one shelf and the protect card can be in another shelf of a multishelf setup. Communication between
the two cards is across 10 Gigabit Ethernet interconnection interface using Ethernet packets. The Inter link
(ILK) trunk or internal pathcord must be provisioned on both the cards. This link is used to transmit
protection switching messages and data.
Note With 1+1 protection mechanisms, the switch time of a copper SFP is 1 second.
With 1+1 protection, ports on the protect card can be assigned to protect the corresponding ports on the
working card. A working card must be paired with a protect card of the same type and number of ports. The
protection takes place on the port level, and any number of ports on the protect card can be assigned to
protect the corresponding ports on the working card.
To make the 1+1 protection scheme fully redundant, enable L2 protection for the entire VLAN ring. This
enables Fast Automatic Protection Switch (FAPS). The VLAN configured on the 1+1 port must be
configured as protected SVLAN.
1+1 protection can be either revertive or nonrevertive. With nonrevertive 1+1 protection, when a failure
occurs and the signal switches from the working card to the protect card, the signal remains on the protect
card until it is manually changed. Revertive 1+1 protection automatically switches the signal back to the
working card when the working card comes back online. 1+1 protection uses trunk ports to send control
traffic between working and protect cards. This trunk port connection is known as ILK trunk ports and can
be provisioned via CTC.
The standby port can be configured to turn ON or OFF but the traffic coming to and from the standby port
will be down. If the laser is ON at the standby port, the other end port (where traffic originates) will not
be down in a parallel connection. Traffic is blocked on the standby port.
1+1 protection is bidirectional and nonrevertive by default; revertive switching can be provisioned using CTC.
836
Card Features
Layer 2 Over DWDM Protection
Layer 2 Over DWDM Protection

The Layer 2 Over DWDM protection is available for the following cards:
GE_XP and GE_XPE
10GE_XP and 10GE_XPE
When the card is in L2-over-DWDM card mode, protection is handled by the hardware at the Layer 1 and
Layer 2 levels. Fault detection and failure propagation is communicated through the ITU-T G.709 frame
overhead bytes. For protected VLANs, traffic is flooded around the 10 Gigabit Ethernet DWDM ring. To
set up the Layer 2 protection, you identify a node and the card port that is to serve as the master node and
port for the VLAN ring on the card view Provisioning > Protection tab. If a failure occurs, the node and
port are responsible for opening and closing VLAN loops.
Note The Forced option in the Protection drop-down list converts all the SVLANs to protected SVLANs
irrespective of the SVLAN protection configuration in the SVLAN database. This is applicable to a point-
to-point linear topology. The SVLAN protection must be forced to move all SVLANs, including protected
and unprotected SVLANs, to the protect path irrespective of provisioned SVLAN attributes.
A FAPS switchover happens in the following failure scenarios:

DWDM line failures caused by a fiber cut
Unidirectional failure in the DWDM network caused by a fiber cut
Fiber pull on the master card trunk port followed by a hard reset on the master card
Hard reset on the master card
Hard reset on the slave card
An OTN failure is detected (LOS, OTUK-LOF, OTUK-LOM, OTUK-LOM, OTUK-SF, or OTUK-BDI
on the DWDM receiver port in the case of ITU-T G.709 mode)
Trunk ports are moved to OOS,DSBLD (Locked,disabled) state
Improper removal of XFPs
A FAPS switchover does not happen in the following scenarios:

Slave card trunk port in OOS,DSBLD (Locked,disabled) state followed by a hard reset of the slave card
OTN alarms raised on the slave card trunk port followed by a hard reset of the slave card
Far-End Laser Control

The cards provide a transparent mode that accurately conveys the client input signal to the far-end client output
signal. The client signal is normally carried as payload over the DWDM signals. Certain client signals, however,
cannot be conveyed as payload. In particular, client LOS or LOF cannot be carried. Far-end laser control (FELC)
is the ability to convey an LOS or LOF from the near-end client input to the far-end client output.
837
Card Features
If an LOS is detected on the near-end client input, the near-end trunk sets the appropriate bytes in the OTN
overhead of the DWDM line. These bytes are received by the far-end trunk, and cause the far-end client
laser to be turned off. When the laser is turned off, it is said to be squelched. If the near-end LOS clears, the
near-end trunk clears the appropriate bytes in the OTN overhead, the far-end detects the changed bytes, and
the far-end client squelch is removed.
FELC also covers the situation in which the trunk port detects that it has an invalid signal; the client is
squelched so as not to propagate the invalid signal.
Payload types with the 2R mode preclude the use of OTN overhead bytes. In 2R mode, an LOS on the
client port causes the trunk laser to turn off. The far end detects the LOS on its trunk receiver and squelches
the client.
FELC is not provisionable. It is always enabled when the DWDM card is in transparent termination mode.
However, FELC signaling to the far-end is only possible when ITU-T G.709 is enabled on both ends of
the trunk span.
Jitter introduced by the SFPs used in the transponders and muxponders must be considered when cascading
several cards. With TXP_MR_2.5G, TXPP_MR_2.5G, MXP_MR_2.5G, MXPP_MR_2.5G, TXP_MR_10E,
100G-LC-C, 10x10G-LC, CFP-LC, 100G-CK-C, 200G-CK-LC, 100GS-CK-LC, 100G-ME-C, 100ME-CKC,
AR_MXP, AR_XP, AR_XPE cards several transponders can be cascaded before the cumulative jitter violates the
jitter specification. The recommended limit is 20 cards. With TXP_MR_10G cards, you can also cascade several
cards, although the recommended limit is 12 cards. With MXP_2.5G_10G and MXP_2.5G_10E cards, any
number of cards can be cascaded as long as the maximum reach between any two is not exceeded. This is
because any time the signal is demultiplexed, the jitter is eliminated as a limiting factor.
The maximum reach between one transponder and the other must be halved if a Y cable is used. For
more information on Y-cable operation, see the Y-Cable and Splitter Protection.
Termination Modes
Transponder and Muxponder cards have various SONET and SDH termination modes that can be
configured using CTC. The termination modes are summarized in the following table.
838
Card Features
Card Features
Table 321: Termination Modes
Cards Termination Mode Description

All TXP, MXP, and OTU2_XP Transparent Termination All the bytes of the payload pass
cards, with the exception of the transparently through the cards.
MXP_2.5G_10G card (see next
row) Section Termination In line termination mode, the
section and line overhead bytes for
SONET and the overhead bytes for
the SDH multiplex and regenerator
sections are terminated. None of
the overhead bytes are passed
through. They are all regenerated,
including the SONET SDCC and
line DCC (LDCC) bytes and the
SDH RS-DCC and multiplexer
section DCC (MS-DCC) bytes.
MXP_2.5G_10G (Clients operating Transparent Termination All client bytes pass transparently
at the OC48/STM16 rate are except the following: B1 is
multiplexed into an OC192/STM64 rebuilt, S1 is rewritten, A1 to A2
frame before going to OTN or are regenerated, and H1 to H3 are
DWDM.) regenerated.
Section Termination The SONET TOH section bytes
and the SDH regenerator section
overhead bytes are terminated.
None of these section overhead
bytes are passed through. They
are all regenerated, including the
SONET TOH section DCC bytes
and the SDH RS-DCC bytes. In
the section termination mode, the
SONET TOH line and SDH
multiplex section overhead bytes
are passed transparently.
Line Termination In the line termination mode, the

section and line overhead bytes for
SONET and the overhead bytes for
the SDH multiplex and regenerators
sections are terminated. None of the
overhead bytes are passed through.
They are all regenerated, including
the SONET SDCC and LDCC bytes
and the SDH RS-DCC and MS-
DCC bytes.
For TXP and MXP cards, adhere to the following conditions while DCC termination provisioning:
For SDCC/RS-DCC provisioning, the card should be in the Section/RS-DCC or Line/MS-DCC
termination mode.
839
Card Features
Card Features
• For LDCC/MS-DCC provisioning, the card should be in the Line/MS-DCC termination mode.
840
APPENDIX D
Card Specifications
The information in this chapter is in a new location. See Hardware Specifications for information related
to hardware and software specifications for the cards.
841
Card Specifications
Card Specifications
842
APPENDIX E
The information in this chapter is in a new location. See Administrative and Service States for an
understanding of administrative and service states for DWDM cards, optical payload ports, out-of-band
optical service channel (OSC) ports, optical channel network connections (OCHNCs), and
transponder/muxponder cards and ports.
843
844
APPENDIX F
SNMP
The information in this chapter is in a new location. See SNMP for information related to Simple
Network Management Protocol (SNMP).
845
SNMP
SNMP
846
APPENDIX G
CTC Enhancements, Operations, and Shortcuts
The information in this chapter is in a new location. See CTC Enhancements, Operations, and Shortcuts for
information on Cisco Transport Controller (CTC) views, menus options, tool options, shortcuts, table
display options, and shelf inventory data presented in CTC.
847
848
APPENDIX H
The information in this chapter is in a new location. See Network Element Defaults for information
related to factory-configured (default) network element (NE) settings.
849
850

B Ons Line Card Configuration

Uploaded by

Copyright:

Available Formats

B Ons Line Card Configuration

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

B Ons Line Card Configuration

Uploaded by

Copyright:

Available Formats

Cisco ONS 15454 DWDM Line Card Configuration Guide, Release 10.x.

Increase the separation between the equipment and receiver.

Consult the dealer or an experienced radio/TV technician for help.

PREFACE Preface xxvii

Document Objectives xxviii

Document Organization xxviii

Document Conventions xxix

Related Documentation xxxv

Obtaining Optical Networking Information xxxvi

Where to Find Safety and Warning Information xxxvi

Obtaining Documentation and Submitting a Service Request xxxvi

PREFACE Cisco ONS Documentation Roadmap for Release 10.x.x xxxvii

PREFACE New and Changed Information xxxix

CHAPTER Setting Up Optical Service Channel Cards 1

CHAPTER Provisioning Optical Amplifier Cards 7

Related Procedures for OPT-PRE Card 12

Related Procedures for OPT-RAMP-C and OPT-RAMP-CE Cards 21

Important Notes Regarding Patchcord Installation 22

EDRA Workflow Diagram 28

EDRA-1-xx and EDRA-2-xx Cards Power Monitoring 29

Related Procedures for EDRA-1-xx and EDRA-2-xx Cards 30

Provisioning Multiplexer and Demultiplexer Cards 31

CHAPTER Setting Up Tunable Dispersion Compensating Units 49

Provisioning Protection Switching Module 53

PSM Card-Level Indicators 54

CHAPTER Provisioning Optical Add/Drop Cards 59

CHAPTER Provisioning Reconfigurable Optical Add/Drop Cards 69

Channel Allocation Plans 71

32WSS and 32 WSS-L Power Monitoring 75

32DMX and 32DMX-L ROADM Functionality 79

SMR-C Card Key Features 106

40-SMR1-C Card 107

CHAPTER Provisioning Transponder and Muxponder Cards 121

Card Overview 123

Faceplates and Block Diagram 144

MXP_MR_2.5G and MXPP_MR_2.5G Functions 162

Related Procedures for MXP_MR_2.5G and MXPP_MR_2.5G Cards 163

MXP_MR_10DME_C and MXP_MR_10DME_L Functions 167

Related Procedures for MXP_MR_10DME_C and MXP_MR_10DME_L Cards 170

40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards 170

Key Features 172

Wavelength Identification 173

Related Procedures for 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards 175

Protocol Compatibility list 179

Client Interface 180

Advantages of LACP 189

LACP Limitations and Restrictions 190

Related Procedure for LACP 190

ADM-10G Card 198

Faceplate and Block Diagram 202

MXP_2.5G_10EX_C card 224

AR_MXP, AR_XP, and AR_XPE Functions and Features 257

Key Features 259

Operating Modes for 100G-LC-C, 100G-ME-C, 100G-CK-C, 100GS-CK-LC, 200G-CK-LC,

Operating Modes for 10x10G-LC Card 262

CFP-LC Card 265

Key Features 266

Operating Modes for CFP-LC Card 266

MR-MXP Card 267