Cisco ONS 15454 DWDM Configuration Guide, Release 9.6.x
Chapter 11, Provision Transponder and Muxponder Cards
Downloads: This chapterpdf (PDF - 7.55MB) The complete bookPDF (PDF - 29.09MB) | Feedback

Provision Transponder and Muxponder Cards

Table Of Contents

Provision Transponder and Muxponder Cards

11.1  Card Overview

11.1.1  Card Summary

11.1.2  Card Compatibility

11.2  Safety Labels

11.3  TXP_MR_10G Card

11.3.1  Faceplate and Block Diagram

11.3.2  TXP_MR_10G Functions

11.3.3  Related Procedures for TXP_MR_10G Card

11.4  TXP_MR_10E Card

11.4.1  Key Features

11.4.2  Faceplate and Block Diagram

11.4.3  TXP_MR_10E Functions

11.4.4  Related Procedures for TXP_MR_10E Card

11.5  TXP_MR_10E_C and TXP_MR_10E_L Cards

11.5.1  Key Features

11.5.2  Faceplates and Block Diagram

11.5.3  TXP_MR_10E_C and TXP_MR_10E_L Functions

11.5.4  Related Procedures for TXP_MR_10E_C and TXP_MR_10E_L Cards

11.6  TXP_MR_2.5G and TXPP_MR_2.5G Cards

11.6.1  Faceplates and Block Diagram

11.6.2  TXP_MR_2.5G and TXPP_MR_2.5G Functions

11.6.3  Related Procedures for TXP_MR_2.5G and TXPP_MR_2.5G Cards

11.7  40E-TXP-C and 40ME-TXP-C Cards

11.7.1  Faceplates and Block Diagram

11.7.2  40E-TXP-C and 40ME-TXP-C Functions

11.7.3  Related Procedures for 40E-TXP-C and 40ME-TXP-C Cards

11.8  MXP_2.5G_10G Card

11.8.1  Faceplates and Block Diagram

11.8.2  MXP_2.5G_10G Functions

11.8.3  Related Procedures for MXP_2.5G_10G Card

11.9  MXP_2.5G_10E Card

11.9.1  Key Features

11.9.2  Faceplates and Block Diagram

11.9.3  MXP_2.5G_10E Functions

11.9.4  Related Procedures for MXP_2.5G_10E Card

11.10  MXP_2.5G_10E_C and MXP_2.5G_10E_L Cards

11.10.1  Key Features

11.10.2  Faceplates and Block Diagram

11.10.3  MXP_2.5G_10E_C and MXP_2.5G_10E_L Functions

11.10.4  Related Procedures for MXP_2.5G_10E_C and MXP_2.5G_10E_L Cards

11.11  MXP_MR_2.5G and MXPP_MR_2.5G Cards

11.11.1  Faceplates and Block Diagram

11.11.2  MXP_MR_2.5G and MXPP_MR_2.5G Functions

11.11.3  Related Procedures for MXP_MR_2.5G and MXPP_MR_2.5G Cards

11.12  MXP_MR_10DME_C and MXP_MR_10DME_L Cards

11.12.1  Key Features

11.12.2  Faceplates and Block Diagram

11.12.3  MXP_MR_10DME_C and MXP_MR_10DME_L Functions

11.12.4  Related Procedures for MXP_MR_10DME_C and MXP_MR_10DME_L Cards

11.13  40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards

11.13.1  Key Features

11.13.2  Faceplate and Block Diagram

11.13.3  40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Functions

11.13.4  Related Procedures for 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards

11.14  GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards

11.14.1  Key Features

11.14.2  Protocol Compatibility list

11.14.3  Faceplate and Block Diagram

11.14.4  GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Functions

11.14.5  IGMP Snooping

11.14.6  Multicast VLAN Registration

11.14.7  MAC Address Learning

11.14.8  MAC Address Retrieval

11.14.9  Link Integrity

11.14.10  Ingress CoS

11.14.11  CVLAN Rate Limiting

11.14.12  DSCP to CoS Mapping

11.14.13  Link Aggregation Control Protocol

11.14.14  Ethernet Connectivity Fault Management

11.14.15  Ethernet OAM

11.14.16  Resilient Ethernet Protocol

11.14.17  Related Procedures for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards

11.15  ADM-10G Card

11.15.1  Key Features

11.15.2  ADM-10G POS Encapsulation, Framing, and CRC

11.15.3  Faceplate and Block Diagram

11.15.4  Port Configuration Rules

11.15.5  Client Interfaces

11.15.6  Interlink Interfaces

11.15.7  DWDM Trunk Interface

11.15.8  Configuration Management

11.15.9  Security

11.15.10  Protection

11.15.11  Circuit Provisioning

11.15.12  ADM-10G CCAT and VCAT Characteristics

Available Circuit Sizes

11.15.13  Intermediate Path Performance Monitoring

11.15.14  Pointer Justification Count Performance Monitoring

11.15.15  Performance Monitoring Parameter Definitions

11.15.16  ADM-10G Functions

11.15.17  Related Procedures for ADM-10G Card

11.16  OTU2_XP Card

11.16.1  Key Features

11.16.2  Faceplate and Block Diagram

11.16.3  OTU2_XP Card Interface

11.16.4  Configuration Management

11.16.5  OTU2_XP Card Configuration Rules

11.16.6  Security

11.16.7  ODU Transparency

11.16.8  OTU2_XP Functions

11.16.9  Related Procedures for OTU2_XP Card

11.17  TXP_MR_10EX_C Card

11.17.1  Key Features

11.17.2  Faceplate and Block Diagram

11.17.3  TXP_MR_10EX_C Functions

11.17.4  Related Procedures for TXP_MR_10EX_C Card

11.18  MXP_2.5G_10EX_C card

11.18.1  Key Features

11.18.2  Faceplate and Block Diagram

11.18.3  MXP_2.5G_10EX_C Functions

11.18.4  Related Procedures for MXP_2.5G_10EX_C Card

11.19  MXP_MR_10DMEX_C Card

11.19.1  Key Features

11.19.2  Faceplate and Block Diagram

11.19.3  MXP_MR_10DMEX_C Functions

11.19.4  Related Procedures for MXP_MR_10DMEX_C Card

11.20  AR_MXP, AR_XP, and AR_XPE Cards

11.20.1  Key Features

11.20.2  Faceplate and Block Diagram

11.20.3  Multiple 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)

RGN (OTU1/OTU2 Regenerator)

MXP-VD-10G (Video Muxponder)

11.20.4  Scenarios of Different Operational mode Configurations on a AR_MXP, AR_XP, or AR_XPE Card

Scenario 1

Scenario 2

Scenario 3

Scenario 4

Scenario 5

11.20.5  AR_MXP, AR_XP, and AR_XPE Functions and Features

11.20.6  Related Procedures for AR_MXP, AR_XP, and AR_XPE Cards

11.21  100G-LC-C,10x10G-LC, and CFP-LC Cards

11.21.1  100G-LC-C Card

11.21.2  10x10G-LC Card

11.21.3  CFP-LC Card

11.22  Related Procedures for 100G-LC-C, 10x10G-LC, and CFP-LC Cards

11.23  MLSE UT

11.23.1  Error Decorrelator

11.24  SFP, SFP+, XFP, CXP, and CFP Modules

11.25  Procedures for Transponder and Muxponder Cards

11.25.1  Before You Begin

NTP-G128 Manage Pluggable Port Modules

DLP-G235 Change the 2.5G Data Muxponder Card Mode

DLP-G332 Change the 10G Data Muxponder Port Mode

DLP-G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode

DLP-G411 Provision an ADM-10G PPM and Port

DLP-G452 Change the OTU2_XP Card Mode

DLP-G274 Verify Topologies for ETR_CLO and ISC Services

DLP-G278 Provision the Optical Line Rate

NTP-G33 Create a Y-Cable Protection Group

NTP-G199 Create a Splitter Protection Group for the OTU2_XP Card

NTP-G198 Create 1+1 Protection for GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards

NTP-G461 Create a 1+1 Protection Group for GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards

NTP-G98 Provision the 2.5G Multirate Transponder Card Line Settings and PM Parameter Thresholds

DLP-G229 Change the 2.5G Multirate Transponder Card Settings

DLP-G230 Change the 2.5G Multirate Transponder Line Settings

DLP-G231 Change the 2.5G Multirate Transponder Line Section Trace Settings

DLP-G367 Change the 2.5G Multirate Transponder Trunk Wavelength Settings

DLP-G232 Change the 2.5G Multirate Transponder SONET or SDH Line Threshold Settings

DLP-G320 Change the 2.5G Multirate Transponder Line RMON Thresholds for 1G Ethernet or 1G FC/FICON Payloads

DLP-G305 Provision the 2.5G Multirate Transponder Trunk Port Alarm and TCA Thresholds

DLP-G306 Provision the 2.5G Multirate Transponder Client Port Alarm and TCA Thresholds

DLP-G234 Change the 2.5G Multirate Transponder OTN Settings

NTP-G96 Provision the 10G Multirate Transponder Card Line Settings, PM Parameters, and Thresholds

DLP-G365 Provision the TXP_MR_10G Data Rate

DLP-G712 Provision the TXP_MR_10E or TXP_MR_10EX_C Data Rate

DLP-G216 Change the 10G Multirate Transponder Card Settings

DLP-G217 Change the 10G Multirate Transponder Line Settings

DLP-G218 Change the 10G Multirate Transponder Line Section Trace Settings

DLP-G368 Change the 10G Multirate Transponder Trunk Wavelength Settings

DLP-G219 Change the 10G Multirate Transponder Line Thresholds for SONET or SDH Payloads Including 10G Ethernet WAN Phy

DLP-G319 Change the 10G Multirate Transponder Line RMON Thresholds for 10G Ethernet LAN Phy Payloads

DLP-G301 Provision the 10G Multirate Transponder Trunk Port Alarm and TCA Thresholds

DLP-G302 Provision the 10G Multirate Transponder Client Port Alarm and TCA Thresholds

DLP-G221 Change the 10G Multirate Transponder OTN Settings

NTP-G292 Provision the 40G Multirate Transponder Card Line Settings, PM Parameters, and Thresholds

DLP-G656 Provision the 40E-TXP-C and 40ME-TXP-C Data Rate

DLP-G657 Change the 40G Multirate Transponder Card Settings

DLP-G658 Change the 40G Multirate Transponder Line Settings

DLP-G659 Change the 40G Multirate Transponder SONET, SDH, or Ethernet Line Settings

DLP-G660 Change the 40G Multirate Transponder Line Section Trace Settings

DLP-G692 Change the 40G Multirate Transponder OTU Settings

DLP-G661 Change the 40G Multirate Transponder Line Thresholds for SONET or SDH Payloads Including 40G Ethernet WAN Phy

DLP-G663 Provision the 40G Multirate Transponder Trunk Port Alarm and TCA Thresholds

DLP-G664 Provision the 40G Multirate Transponder Client Port Alarm and TCA Thresholds

DLP-G665 Change the 40G Multirate Transponder OTN Settings

NTP-G170 Provision the ADM-10G Card Peer Group, Ethernet Settings, Line Settings, PM Parameters, and Thresholds

DLP-G403 Create the ADM-10G Peer Group

DLP-G469 Provision the ADM-10G Card Ethernet Settings

DLP-G397 Change the ADM-10G Line Settings

DLP-G398 Change the ADM-10G Line Section Trace Settings

DLP-G399 Change the ADM-10G Line Thresholds for SONET and SDH Payloads

DLP-G412 Change the ADM-10G Line RMON Thresholds for the 1G Ethernet Payload

DLP-G400 Provision the ADM-10G Interlink or Trunk Port Alarm and TCA Thresholds

DLP-G401 Provision the ADM-10G Client Port Alarm and TCA Thresholds

DLP-G402 Change the ADM-10G OTN Settings

NTP-G333 Add an ADM-10G card to an Existing Topology

NTP-G97 Modify the 4x2.5G Muxponder Card Line Settings and PM Parameter Thresholds

DLP-G222 Change the 4x2.5G Muxponder Card Settings

DLP-G223 Change the 4x2.5G Muxponder Line Settings

DLP-G224 Change the 4x2.5G Muxponder Section Trace Settings

DLP-G225 Change the 4x2.5G Muxponder Trunk Settings

DLP-G369 Change the 4x2.5G Muxponder Trunk Wavelength Settings

DLP-G226 Change the 4x2.5G Muxponder SONET/SDH Line Thresholds Settings

DLP-G303 Provision the 4x2.5G Muxponder Trunk Port Alarm and TCA Thresholds

DLP-G304 Provision the 4x2.5G Muxponder Client Port Alarm and TCA Thresholds

DLP-G228 Change the 4x2.5G Muxponder Line OTN Settings

NTP-G99 Modify the 2.5G Data Muxponder Card Line Settings and PM Parameter Thresholds

DLP-G236 Change the 2.5G Data Muxponder Client Line Settings

DLP-G237 Change the 2.5G Data Muxponder Distance Extension Settings

DLP-G238 Change the 2.5G Data Muxponder SONET (OC-48)/SDH (STM-16) Settings

DLP-G239 Change the 2.5G Data Muxponder Section Trace Settings

DLP-G370 Change the 2.5G Data Muxponder Trunk Wavelength Settings

DLP-G240 Change the 2.5G Data Muxponder SONET or SDH Line Thresholds

DLP-G321 Change the 2.5G Data Muxponder Line Thresholds for 1G Ethernet or 1G FC/FICON Payloads

DLP-G307 Provision the 2.5G Data Muxponder Trunk Port Alarm and TCA Thresholds

DLP-G308 Provision the 2.5G Data Muxponder Client Port Alarm and TCA Thresholds

NTP-G148 Modify the 10G Data Muxponder Card Line Settings and PM Parameter Thresholds

DLP-G333 Change the 10G Data Muxponder Client Line Settings

DLP-G334 Change the 10G Data Muxponder Distance Extension Settings

DLP-G340 Change the 10G Data Muxponder Trunk Wavelength Settings

DLP-G335 Change the 10G Data Muxponder SONET (OC-192)/SDH (STM-64) Settings

DLP-G336 Change the 10G Data Muxponder Section Trace Settings

DLP-G341 Change the 10G Data Muxponder SONET or SDH Line Thresholds

DLP-G337 Change the 10G Data Muxponder Line RMON Thresholds for Ethernet, 1G FC/FICON, or ISC/ISC3 Payloads

DLP-G338 Provision the 10G Data Muxponder Trunk Port Alarm and TCA Thresholds

DLP-G339 Provision the 10G Data Muxponder Client Port Alarm and TCA Thresholds

DLP-G366 Change the 10G Data Muxponder OTN Settings

NTP-G293 Modify the 40G Muxponder Card Line Settings and PM Parameter Thresholds

DLP-G662 Change the 40G Multirate Muxponder Card Settings

DLP-G666 Change the 40G Muxponder Line Settings

DLP-G735 Provision the 40G Muxponder Ethernet Settings

DLP-G667 Change the 40G Muxponder SONET (OC-192)/SDH (STM-64) Settings

DLP-G668 Change the 40G Muxponder Section Trace Settings

DLP-G691 Change the 40G Muxponder OTU Settings

DLP-G669 Change the 40G Muxponder SONET or SDH Line Thresholds

DLP-G670 Change the 40G Muxponder Line RMON Thresholds for Ethernet, 8G FC, or 10G FC Payloads

DLP-G671 Provision the 40G Muxponder Trunk Port Alarm and TCA Thresholds

DLP-G672 Provision the 40G Muxponder Client Port Alarm and TCA Thresholds

DLP-G673 Change the 40G Muxponder OTN Settings

NTP-G281 Manage the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Channel Group Settings

DLP-G611 Create a Channel Group Using CTC

DLP-G612 Modify the Parameters of the Channel Group Using CTC

DLP-G613 Add or Remove Ports to or from an Existing Channel Group Using CTC

Before You Begin

DLP-G614 Delete a Channel Group Using CTC

DLP-G615 Retrieve Information on Channel Group, REP, CFM, and EFM Using CTC

DLP-G616 View Channel Group PM Parameters for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards Using CTC

DLP-G617 View Channel Group Utilization PM Parameters for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards Using CTC

DLP-G618 View Channel Group History PM Parameters for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards Using CTC

NTP-G283 Manage the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card CFM Settings

DLP-G621 Enable or Disable CFM on the Card Using CTC

DLP-G622 Enable or Disable CFM for Each Port Using CTC

DLP-G623 Create a Maintenance Domain Profile Using CTC

Before You Begin

DLP-G624 Delete a Maintenance Domain Profile Using CTC

DLP-G625 Create a Maintenance Association Profile Using CTC

DLP-G626 Modify a Maintenance Association Profile Using CTC

DLP-G627 Delete a Maintenance Association Profile Using CTC

DLP-G628 Map a Maintenance Association Profile to a Maintenance Domain Profile Using CTC

DLP-G629 Create a MEP Using CTC

DLP-G630 Delete a MEP Using CTC

DLP-G631 Create a MIP Using CTC

DLP-G632 Delete a MIP Using CTC

DLP-G633 Ping MEP Using CTC

DLP-G634 Traceroute MEP Using CTC

NTP-G285 Manage the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card EFM Settings

DLP-G639 Enable or Disable EFM for Each Port Using CTC

Before You Begin

DLP-G640 Configure EFM Parameters Using CTC

DLP-G641 Configure EFM Link Monitoring Parameters Using CTC

DLP-G642 Enable Remote Loopback for Each Port Using CTC

NTP-G287 Manage the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card REP Settings

DLP-G713 Provision Administrative VLAN for Ports in a REP Segment Using CTC

DLP-G645 Create a Segment Using CTC

Before You Begin

DLP-G646 Edit a Segment Using CTC

DLP-G647 Activate VLAN Load Balancing Using CTC

DLP-G648 Deactivate VLAN Load Balancing Using CTC

NTP-G165 Modify the GE_XP, 10GE_XP, GE_XPE, 10GE_XPE Cards Ethernet Parameters, Line Settings, and PM Thresholds

DLP-G380 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Ethernet Settings

DLP-G684 Provision the GE_XPE Card PDH Ethernet Settings

DLP-G685 Provision the GE_XPE Card Electrical Lines Settings

DLP-G381 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Layer 2 Protection Settings

DLP-G507 Enable a Different GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Card as the Master Card

DLP-G382 Add and Remove SVLANS to/from GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE NNI Ports

DLP-G383 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Quality of Service Settings

DLP-G470 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Class of Service (CoS) Settings

DLP-G384 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE QinQ Settings

DLP-G221 Enable MAC Address Learning on SVLANs for GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards

DLP-G460 Enable MAC Address Learning on SVLANs for GE_XPE or 10GE_XPE Cards Using CTC

DLP-G385 Provision the MAC Filter Settings for GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Card

NTP-G237 Retrieve and Clear MAC Addresses on SVLANs for GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards

DLP-G546 View Card MAC Addresses on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards

NTP-G311 Provision the Storm Control Settings for GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards

NTP-G205 Enable Link Integrity on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards

DLP-G509 Enable Link Integrity on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards Using CTC

NTP-G289 Provision CVLAN Rate Limiting on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Card

NTP-G208 Provision SVLAN Rate Limiting on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Card

DLP-G515 Provision SVLAN Rate Limiting on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Card Using CTC

DLP-G471 Create a SVLAN or CVLAN Profile

NTP-G204 Enable IGMP Snooping on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards

DLP-G511 Enable IGMP Snooping, IGMP Fast Leave and IGMP Report Suppression on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards Using CTC

NTP-G206 Enable MVR on a GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Card

DLP-G513 Enable MVR on a GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Card Using CTC

DLP-G386 Provision the Gigabit Ethernet Trunk Port Alarm and TCA Thresholds

DLP-G387 Provision the Gigabit Ethernet Client Port Alarm and TCA Thresholds

DLP-G388 Change the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Card RMON Thresholds

DLP-G389 Change the Gigabit Ethernet Optical Transport Network Settings

NTP-G314 Add a GE_XP or 10GE_XP Card on a FAPS Ring

DLP-G687 Add a GE_XP or 10GE_XP Card Facing Master Card on a FAPS Ring

DLP-G688 Add a GE_XP or 10GE_XP Card Between the Slave Cards on a FAPS Ring

NTP-G197 Provision the OTU2_XP Card Line Settings, PM Parameters, and Thresholds

DLP-G453 Change the OTU2_XP Card Settings

DLP-G454 Change the OTU2_XP Line Settings

DLP-G455 Change the OTU2_XP Line Section Trace Settings

DLP-G456 Change the OTU2_XP Line Thresholds for SONET or SDH Payloads

DLP-G457 Provision the OTU2_XP Port Alarm and TCA Thresholds

DLP-G462 Change the OTU2_XP Line RMON Thresholds for the 10G Ethernet and 10G FC Payloads

DLP-G458 Change the OTU2_XP OTN Settings

DLP-G523 Change the OTU2_XP Path Trace Settings

DLP-G524 Provision the OTU2_XP Path Settings for 10G Ethernet LAN Phy to WAN Phy Configuration

NTP-G162 Change the ALS Maintenance Settings

NTP-G302 Configure Loopback on 100G-LC-C, 10x10G-LC, and CFP-LC Cards

NTP-G299 Configure the Backplane Loopback on 100G-LC-C, 10x10G-LC, and CFP-LC Cards

NTP-G192 Force FPGA Update

NTP-G196 Force FPGA Update When the Card is Part of a Protection Group

NTP-G232 Enabling Error Decorrelator

NTP-G315 Enable or Disable the Wavelength Drifted Channel Automatic Shutdown Feature

NTP-G316 Enable REP and FAPS on the same port

NTP-G321 Provision Multiple Operating Modes on AR_MXP, AR_XP, or AR_XPE Cards

NTP-G322 Modify the AR_MXP, AR_XP, or AR_XPE Card Line Settings and PM Parameter Thresholds

DLP-G695 Change the AR_MXP, AR_XP, or AR_XPE Card Line Settings

DLP-G696 Change the AR_MXP, AR_XP, or AR_XPE Card Ethernet Settings

DLP-G697 Change the AR_MXP, AR_XP, or AR_XPE Card SONET/SDH Settings

DLP-G698 Change the AR_MXP, AR_XP, or AR_XPE Card Section Trace Settings

DLP-G699 Enable Auto Sensing for AR_MXP, AR_XP, or AR_XPE Cards

DLP-G700 Change the AR_MXP, AR_XP, or AR_XPE Card SONET/SDH Line Thresholds

DLP-G701 Change the AR_MXP, AR_XP, or AR_XPE Card Line RMON Thresholds

DLP-G702 Provision the AR_MXP, AR_XP, or AR_XPE Card with Trunk Port Alarm and TCA Thresholds

DLP-G703 Provision the AR_MXP, AR_XP, or AR_XPE Card Client Port Alarm and TCA Thresholds

DLP-G704 Change the AR_MXP, AR_XP, or AR_XPE Card OTN Settings

DLP-G734 View the Mapping of ODU Object with Client Port

NTP-G235 Provision an Operating Mode on the 100G-LC-C, 10x10G-LC, or CFP-LC Card

NTP-G236 Modify the 100G-LC-C, 10x10G-LC, or CFP-LC Card Line Settings and PM Parameter Thresholds

DLP-G714 Change the 100G-LC-C, 10x10G-LC, or CFP-LC Card Line Settings

DLP-G715 Change the 100G-LC-C, 10x10G-LC, or CFP-LC Card Ethernet Settings

DLP-G716 Change the 10x10G-LC Card SONET/SDH Settings

DLP-G717 Change the 10x10G-LC Card Section Trace Settings

DLP-G718 Change the 10x10G-LC Card SONET/SDH Line Thresholds

DLP-G719 Change the 100G-LC-C, 10x10G-LC, or CFP-LC Card Line RMON Thresholds

DLP-G720 Provision the 100G-LC-C Card with Trunk Port Alarm and TCA Thresholds

DLP-G721 Provision the 100G-LC-C, 10x10G-LC, or CFP-LC Client Port Alarm and TCA Thresholds

DLP-G722 Change the 100G-LC-C Card OTN Settings


Provision Transponder and Muxponder Cards



Note The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration. Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's path protection feature, which may be used in any topological network configuration. Cisco does not recommend using its path protection feature in any particular topological network configuration.


This chapter describes Cisco ONS 15454 transponder (TXP), muxponder (MXP), GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, ADM-10G, OTU2_XP, 100G-LC-C, 10x10G-LC, CFP-LC, 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 CPT and Cisco ONS Platforms.


Note Unless otherwise specified, "ONS 15454" refers to both ANSI and ETSI shelf assemblies.



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 The procedures and tasks described in this chapter for the Cisco ONS 15454 platform is applicable to the Cisco ONS 15454 M2 and Cisco ONS 15454 M6 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.


Chapter topics include:

Card Overview

Safety Labels

TXP_MR_10G Card

Related Procedures for TXP_MR_10G Card

TXP_MR_10E Card

Related Procedures for TXP_MR_10E Card

TXP_MR_10E_C and TXP_MR_10E_L Cards

Related Procedures for TXP_MR_10E_C and TXP_MR_10E_L Cards

TXP_MR_2.5G and TXPP_MR_2.5G Cards

Related Procedures for TXP_MR_2.5G and TXPP_MR_2.5G Cards

40E-TXP-C and 40ME-TXP-C Cards

Related Procedures for 40E-TXP-C and 40ME-TXP-C Cards

MXP_2.5G_10G Card

Related Procedures for MXP_2.5G_10G Card

MXP_2.5G_10E Card

Related Procedures for MXP_2.5G_10E Card

MXP_2.5G_10E_C and MXP_2.5G_10E_L Cards

Related Procedures for MXP_2.5G_10E_C and MXP_2.5G_10E_L Cards

MXP_MR_2.5G and MXPP_MR_2.5G Cards

Related Procedures for MXP_MR_2.5G and MXPP_MR_2.5G Cards

MXP_MR_10DME_C and MXP_MR_10DME_L Cards

Related Procedures for MXP_MR_10DME_C and MXP_MR_10DME_L Cards

40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards

Related Procedures for 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards

GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards

Related Procedures for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards

ADM-10G Card

Related Procedures for ADM-10G Card

OTU2_XP Card

Related Procedures for OTU2_XP Card

TXP_MR_10EX_C Card

Related Procedures for TXP_MR_10EX_C Card

MXP_2.5G_10EX_C card

Related Procedures for MXP_2.5G_10EX_C Card

MXP_MR_10DMEX_C Card

Related Procedures for MXP_MR_10DMEX_C Card

AR_MXP, AR_XP, and AR_XPE Cards

100G-LC-C,10x10G-LC, and CFP-LC Cards

Related Procedures for 100G-LC-C, 10x10G-LC, and CFP-LC Cards

MLSE UT

SFP, SFP+, XFP, CXP, and CFP Modules


Note Cisco ONS 15454 DWDM supports IBM's 5G DDR (Double Data Rate) InfiniBand1 interfaces.


11.1  Card Overview

The card overview section lists the cards described in this chapter and provides compatibility information.


Note Each card is marked with a symbol that corresponds to a slot (or slots) on the ONS 15454 shelf assembly. The cards are then installed into slots displaying the same symbols. For a list of slots and symbols, see the "Card Slot Requirements" section in the Cisco ONS 15454 Hardware Installation Guide.


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 Table G-19 for details.


11.1.1  Card Summary

Table 11-1 lists and summarizes the functions of each TXP, TXPP, MXP, MXPP, AR_MXP, AR_XP, AR_XPE, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, 100G-LC-C, 10x10G-LC, CFP-LC, ADM-10G, and OTU2_XP card.

Table 11-1 Cisco ONS 15454 Transponder and Muxponder Cards 

Card
Port Description
For Additional Information
TXP_MR_10G

The TXP_MR_10G card has two sets of ports located on the faceplate.

See the "TXP_MR_10G Card" section.

TXP_MR_10E

The TXP_MR_10E card has two sets of ports located on the faceplate.

See the "TXP_MR_10E Card" section.

TXP_MR_10E_C and TXP_MR_10E_L

The TXP_MR_10E_C and TXP_MR_10E_L cards have two sets of ports located on the faceplate.

See the "TXP_MR_10E_C and TXP_MR_10E_L Cards" section.

TXP_MR_2.5G

The TXP_MR_2.5G card has two sets of ports located on the faceplate.

See the "TXP_MR_2.5G and TXPP_MR_2.5G Cards" section.

TXPP_MR_2.5G

The TXPP_MR_2.5G card has three sets of ports located on the faceplate.

See the "TXP_MR_2.5G and TXPP_MR_2.5G Cards" section.

40E-TXP-C, and 40ME-TXP-C

The 40E-TXP-C and 40ME-TXP-C cards have two ports located on the face plate.

See the "40E-TXP-C and 40ME-TXP-C Cards" section.

MXP_2.5G_10G

The MXP_2.5G_10G card has nine sets of ports located on the faceplate.

See the "MXP_2.5G_10G Card" section.

MXP_2.5G_10E

The MXP_2.5G_10E card has nine sets of ports located on the faceplate.

See the "MXP_2.5G_10E Card" section.

MXP_2.5G_10E_C and
MXP_2.5G_10E_L

The MXP_2.5G_10E_C and MXP_2.5G_10E_L cards have nine sets of ports located on the faceplate.

See the "MXP_2.5G_10E_C and MXP_2.5G_10E_L Cards" section.

MXP_MR_2.5G

The MXP_MR_2.5G card has nine sets of ports located on the faceplate.

See the "MXP_MR_2.5G and MXPP_MR_2.5G Cards" section.

MXPP_MR_2.5G

The MXPP_MR_2.5G card has ten sets of ports located on the faceplate.

See the "MXP_MR_2.5G and MXPP_MR_2.5G Cards" section.

MXP_MR_10DME_C and MXP_MR_10DME_L

The MXP_MR_10DME_C and MXP_MR_10DME_L cards have eight sets of ports located on the faceplate.

See the "MXP_MR_10DME_C and MXP_MR_10DME_L Cards" section.

40G-MXP-C
40E-MXP-C
and
40ME-MXP-C

The 40G-MXP-C, 40E-MXP-C and 40ME-MXP-C cards have five ports located on the faceplate.

See the "40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards" section.

AR_MXP, AR_XP, and
AR_XPE

The AR_MXP, AR_XP, and AR_XPE cards have ten ports located on the faceplate.

See the "AR_MXP, AR_XP, and AR_XPE Cards" section.

GE_XP and GE_XPE

The GE_XP and GE_XPE cards have twenty Gigabit Ethernet client ports and two 10 Gigabit Ethernet trunk ports.

See the "GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards" section.

10GE_XP and 10GE_XPE

The 10GE_XP and 10GE_XPE cards have two 10 Gigabit Ethernet client ports and two 10 Gigabit Ethernet trunk ports.

See the "GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards" section.

100G-LC-C

The 100G-LC-C card has one DWDM port and one CXP port.

See the "100G-LC-C Card" section.

10x10G-LC

The 10x10G-LC card has 10-ports SFP+ based (gray, colored, coarse wavelength division multiplexing (CWDM), and DWDM optics available)) and one 100G CXP based port.

See the"10x10G-LC Card" section.

CFP-LC

The CFP-LC card has two 100G CFP pluggable modules and a cross-bar embedded switch module.

See the "CFP-LC Card" section.

ADM-10G

The ADM-10G card has 19 sets of ports located on the faceplate.

See the "ADM-10G Card" section.

OTU2_XP

The OTU2_XP card has four ports located on the faceplate.

See the "OTU2_XP Card" section.

TXP_MR_10EX_C

The TXP_MR_10EX_C card has two sets of ports located on the faceplate.

See the "TXP_MR_10EX_C Card" section.

MXP_2.5G_10EX_C

The MXP_2.5G_10EX_C card has nine sets of ports located on the faceplate.

See the "MXP_2.5G_10EX_C card" section.

MXP_MR_10DMEX_C

The MXP_MR_10DMEX_C card has eight sets of ports located on the faceplate.

See the "MXP_MR_10DMEX_C Card" section.


11.1.2  Card Compatibility

Table 11-2 lists the platform and Cisco Transport Controller (CTC) software compatibility for each TXP, TXPP, MXP, MXPP, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, ADM-10G, and OTU2_XP card.

Table 11-2 Platform and Software Release Compatibility for Transponder and Muxponder Cards

Card Name
R4.5
R4.6
R4.7
R5.0
R6.0
R7.0
R7.2
R8.0
R8.5
R9.0
R9.1
R9.2
R9.2.1
R9.3
R9.4
R9.6.x

TXP_MR_10G

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

TXP_MR_10E

No

No

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

TXP_MR_10E_C

No

No

No

No

No

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

TXP_MR_10E_L

No

No

No

No

No

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

TXP_MR_2.5G

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

TXPP_MR_2.5G

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

MXP_2.5G_10G

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

MXP_2.5G_10E

No

No

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

MXP_2.5G_10E_C

No

No

No

No

No

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

MXP_2.5G_10E_L

No

No

No

No

No

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

MXP_MR_2.5G

No

No

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

MXPP_MR_2.5G

No

No

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

MXP_MR_10DME_C

No

No

No

No

No

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

MXP_MR_10DME_L

No

No

No

No

No

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

GE_XP

No

No

No

No

No

No

No

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

10GE_XP

No

No

No

No

No

No

No

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

GE_XPE

No

No

No

No

No

No

No

No

No

15454-DWDM

15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

10GE_XPE

No

No

No

No

No

No

No

No

No

15454-DWDM

15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

ADM-10G

No

No

No

No

No

No

No

15454-DWDM

15454-DWDM

15454-DWDM

15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

OTU2_XP

No

No

No

No

No

No

No

No

No

15454-DWDM

15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

TXP_MR_10EX_C

No

No

No

No

No

No

No

No

No

No

15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

MXP_2.5G_10EX_C

No

No

No

No

No

No

No

No

No

No

15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

MXP_MR_10DMEX_C

No

No

No

No

No

No

No

No

No

No

15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

40E-TXP-C

No

No

No

No

No

No

No

No

No

No

No

No

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

40ME-TXP-C

No

No

No

No

No

No

No

No

No

No

No

No

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

40G-MXP-C

No

No

No

No

No

No

No

No

No

No

No

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

40E-MXP-C

No

No

No

No

No

No

No

No

No

No

No

No

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

40ME-MXP-C

No

No

No

No

No

No

No

No

No

No

No

No

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

AR_MXP

No

No

No

No

No

No

No

No

No

No

No

No

No

No

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

AR_XP

No

No

No

No

No

No

No

No

No

No

No

No

No

No

15454-M2, 15454-M6, 15454-DWDM

15454-M2, 15454-M6, 15454-DWDM

AR_XPE

No

No

No

No

No

No

No

No

No

No

No

No

No

No

No

15454-M2, 15454-M6, 15454-DWDM

100G-LC-C

No

No

No

No

No

No

No

No

No

No

No

No

No

No

No

15454-M2, 15454-M6

10x10G-LC

No

No

No

No

No

No

No

No

No

No

No

No

No

No

No

15454-M2, 15454-M6

CFP-LC

No

No

No

No

No

No

No

No

No

No

No

No

No

No

No

15454-M6


11.2  Safety Labels

For information about safety labels, see the "Safety Labels" section.

11.3  TXP_MR_10G Card

(Cisco ONS 15454 only)

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/single node control point (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:

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

11.3.1  Faceplate and Block Diagram

Figure 11-1 shows the TXP_MR_10G faceplate and block diagram.

Figure 11-1 TXP_MR_10G Faceplate and Block Diagram

For information about safety labels for the card, see the "Class 1M Laser Product Cards" section.

11.3.2  TXP_MR_10G Functions

The functions of the TXP_MR_10G card are:

Automatic Laser Shutdown

Card level indicators—Table G-1

Port level indicators—Table G-7

11.3.3  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:

G96 Provision the 10G Multirate Transponder Card Line Settings, PM Parameters, and Thresholds

G33 Create a Y-Cable Protection Group

NTP-G75 Monitor Transponder and Muxponder Performance

11.4  TXP_MR_10E Card

(Cisco ONS 15454 only)

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 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 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 configured for transparent termination mode.

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 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 card must be installed in Slots 6, 7, 12 or 13)


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.

11.4.1  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)

OC-192 to ITU-T G.709 OTU2 provisionable synchronous and asynchronous mapping

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.

11.4.2  Faceplate and Block Diagram

Figure 11-2 shows the TXP_MR_10E faceplate and block diagram.

Figure 11-2 TXP_MR_10E 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 15-dB fiber attenuator (10 to 20 dB) when working with the TXP_MR_10E card in a loopback on the trunk port. Do not use direct fiber loopbacks with the TXP_MR_10E card. Using direct fiber loopbacks causes irreparable damage to the TXP_MR_10E card.

11.4.3  TXP_MR_10E Functions

The functions of the TXP_MR_10E card are:

Automatic Laser Shutdown

Card level indicators—Table G-1

Port level indicators—Table G-6

Client Interface

DWDM Trunk Interface

FEC

Client-to-Trunk Mapping

11.4.4  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:

G96 Provision the 10G Multirate Transponder Card Line Settings, PM Parameters, and Thresholds

G33 Create a Y-Cable Protection Group

NTP-G75 Monitor Transponder and Muxponder Performance

11.5  TXP_MR_10E_C and TXP_MR_10E_L Cards

TXP_MR_10E_L: (Cisco ONS 15454 only)

The TXP_MR_10E_C and TXP_MR_10E_L cards are multirate transponders for the ONS 15454 platform. The 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 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.

11.5.1  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)

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.

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.

11.5.2  Faceplates and Block Diagram

Figure 11-3 shows the TXP_MR_10E_C and TXP_MR_10E_L faceplates and block diagram.

Figure 11-3 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.

11.5.3  TXP_MR_10E_C and TXP_MR_10E_L Functions

The functions of the TXP_MR_10E_C and TXP_MR_10E_L cards are:

Automatic Laser Shutdown

Card level indicators—Table G-1

Port level indicators—Table G-6.

Client Interface

DWDM Trunk Interface

FEC

Client-to-Trunk Mapping

11.5.4  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:

G96 Provision the 10G Multirate Transponder Card Line Settings, PM Parameters, and Thresholds

G358 Provision TXP_MR_10E_L and TXP_MR_10E_C Cards for Acceptance Testing

NTP-G75 Monitor Transponder and Muxponder Performance

11.6  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 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. Table 11-50 shows the possible combinations of client interfaces, input bit rates, 2R and 3R modes, and ITU-T G.709 monitoring.

Table 11-3 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 (2G-FC)/fiber connectivity (FICON)

2.125 Gbps

3R1

On or Off

High-Definition Television (HDTV)

1.48 Gbps

2R

Gigabit Ethernet (GE)

1.25 Gbps

3R

On or Off

1 Gigabit Fibre Channel (1G-FC)/FICON

1.06 Gbps

3R

On or Off

OC-12/STM-4

622 Mbps

3R

On or Off

OC-3/STM-1

155 Mbps

3R

On or Off

Enterprise System Connection (ESCON)

200 Mbps

2R

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

1 No monitoring



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. Table 11-4 lists the calculated trunk bit rates for the client interfaces with ITU-T G.709 enabled.

Table 11-4 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

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.

11.6.1  Faceplates and Block Diagram

Figure 11-4 shows the TXP_MR_2.5G and TXPP_MR_2.5G faceplates.

Figure 11-4 TXP_MR_2.5G and TXPP_MR_2.5G Faceplates

For information about safety labels for the cards, see the "Class 1M Laser Product Cards" section.

Figure 11-5 shows a block diagram of the TXP_MR_2.5G and TXPP_MR_2.5G cards.

Figure 11-5 TXP_MR_2.5G and TXPP_MR_2.5G Block Diagram


Caution You must use a 20-dB fiber attenuator (15 to 25 dB) when working with the TXP_MR_2.5G and TXPP_MR_2.5G cards in a loopback on the trunk port. Do not use direct fiber loopbacks with the TXP_MR_2.5G and TXPP_MR_2.5G cards. Using direct fiber loopbacks causes irreparable damage to the TXP_MR_2.5G and TXPP_MR_2.5G cards.

You can install TXP_MR_2.5G and TXPP_MR_2.5G cards in Slots 1 to 6 and 12 to 17. 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.

11.6.2  TXP_MR_2.5G and TXPP_MR_2.5G Functions

The functions of the TXP_MR_2.5G and TXPP_MR_2.5G cards are:

Automatic Laser Shutdown

Card level indicators—Table G-1

Port level indicators—Table G-6 (for TXP_MR_2.5G)

Port level indicators—Table G-8 (for TXPP_MR_2.5G)

11.6.3  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:

G98 Provision the 2.5G Multirate Transponder Card Line Settings and PM Parameter Thresholds

G33 Create a Y-Cable Protection Group (TXP_MR_2.5G only)

NTP-G75 Monitor Transponder and Muxponder Performance

11.7  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.

The trunk port of the 40E-TXP-C and 40ME-TXP-C cards are tunable between 1529.55 nm through 1561.83 nm, ITU 50-GHz range.

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.


Caution You must use a 15-dB fiber attenuator (10 to 20 dB) when working with the 40E-TXP-C, and 40ME-TXP-C cards in a loopback on the trunk port. Do not use direct fiber loopbacks with the 40E-TXP-C, and 40ME-TXP-C cards. Using direct fiber loopbacks causes irreparable damage to the these cards.

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.


Note The maximum ambient operating temperature for 40E-TXP-C, and 40ME-TXP-C cards is 500 Celsius.


11.7.1  Faceplates and Block Diagram

Figure 11-6 shows the 40E-TXP-C and 40ME-TXP-C faceplate and block diagram.

Figure 11-6 40E-TXP-C and 40ME-TXP-C Faceplate and Block Diagram

For information about safety labels for the card, see the "Class 1M Laser Product Cards" section.

11.7.2  40E-TXP-C and 40ME-TXP-C Functions

The functions of the 40E-TXP-C and 40ME-TXP-C cards are:

Automatic Laser Shutdown (supported on a client interface)

Card level indicators—Table G-1

Port level indicators—Table G-6.

11.7.3  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:

G292 Provision the 40G Multirate Transponder Card Line Settings, PM Parameters, and Thresholds

G33 Create a Y-Cable Protection Group

NTP-G75 Monitor Transponder and Muxponder Performance

11.8  MXP_2.5G_10G Card

(Cisco ONS 15454 only)

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 OC-1 (STS-1) fiber optic signals defined in Telcordia GR-253-CORE. An OC-1 signal is the equivalent of one DS-3 channel transmitted across optical fiber. OC-1 is primarily used for trunk interfaces to phone switches in the United States. There is no SDH equivalent for SONET OC-1.

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.


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.


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.


11.8.1  Faceplates and Block Diagram

Figure 11-7 shows the MXP_2.5G_10G faceplate.

Figure 11-7 MXP_2.5G_10G Faceplate

For information about safety labels for the card, see the "Class 1 Laser Product Cards" section.

Figure 11-8 shows a block diagram of the MXP_2.5G_10G card.

Figure 11-8 MXP_2.5G_10G Card Block Diagram

11.8.2  MXP_2.5G_10G Functions

The functions of the MXP_2.5G_10G card are:

Timing Synchronization

Automatic Laser Shutdown

Card level indicators—Table G-1

Port level indicators— Table G-7

11.8.3  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:

G97 Modify the 4x2.5G Muxponder Card Line Settings and PM Parameter Thresholds

G33 Create a Y-Cable Protection Group

NTP-G75 Monitor Transponder and Muxponder Performance

11.9  MXP_2.5G_10E Card

The faceplate designation of the card is "4x2.5G 10E MXP." The MXP_2.5G_10E card is a DWDM muxponder for the ONS 15454 platform 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 digital wrapper function (ITU-T G.709 compliant) formats the DWDM wavelength so that it can be used to set up generic communications channels (GCCs) for data communications, enable FEC, or facilitate performance monitoring.

The MXP_2.5G_10E works with optical transport network (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_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. 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 configured for transparent termination mode.

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.


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.


11.9.1  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 (237,255) 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 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 Cisco TransportPlanner 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 TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE card. If for some reason, such as maintenance or upgrade activity, the TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE 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.

11.9.2  Faceplates and Block Diagram

Figure 11-9 shows the MXP_2.5G_10E faceplate.

Figure 11-9 MXP_2.5G_10E Faceplate

For information about safety labels for the card, see the "Class 1 Laser Product Cards" section.

Figure 11-10 shows a block diagram of the MXP_2.5G_10E card.

Figure 11-10 MXP_2.5G_10E Block Diagram

11.9.3  MXP_2.5G_10E Functions

The functions of the MXP_2.5G_10E card are:

Client Interface

DWDM Interface

Multiplexing Function

Timing Synchronization

FEC

SONET/SDH Overhead Byte Processing

SONET/SDH Overhead Byte Processing

Client Interface Monitoring

Automatic Laser Shutdown

Jitter

Lamp Test

Onboard Traffic Generation

Card level indicators—Table G-1

Port level indicators—Table G-6.

11.9.3.1  Wavelength Identification

The card uses trunk lasers that are wave-locked, which allows the trunk transmitter to operate on the ITU grid effectively. Table 11-5 describes the required trunk transmit laser wavelengths. The laser is tunable over eight wavelengths at 50-GHz spacing or four at 100-GHz spacing.

Table 11-5 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


11.9.4  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:

G97 Modify the 4x2.5G Muxponder Card Line Settings and PM Parameter Thresholds

G33 Create a Y-Cable Protection Group

NTP-G75 Monitor Transponder and Muxponder Performance

11.10  MXP_2.5G_10E_C and MXP_2.5G_10E_L Cards

MXP_2.5G_10E_L: (Cisco ONS 15454 only)

The MXP_2.5G_10E_C and MXP_2.5G_10E_L cards are DWDM muxponders for the ONS 15454 platform 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. 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 configured for transparent termination mode.

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.


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.


11.10.1  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 (237,255) 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 TCC2/TCC2P/TCC3 card. If for some reason, such as maintenance or upgrade activity, the TCC2/TCC2P/TCC3 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 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 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.

11.10.2  Faceplates and Block Diagram

Figure 11-11 shows the MXP_2.5G_10E_C and MXP_2.5G_10E_L faceplates and block diagram.

Figure 11-11 MXP_2.5G_10E _C and MXP_2.5G_10E_L Faceplates and Block Diagram

For information about safety labels for the cards, see the "Class 1 Laser Product Cards" section.

11.10.3  MXP_2.5G_10E_C and MXP_2.5G_10E_L Functions

The functions of the MXP_2.5G_10E_C and MXP_2.5G_10E_L cards are:

Client Interface

DWDM Interface

Multiplexing Function

Timing Synchronization

FEC

SONET/SDH Overhead Byte Processing

SONET/SDH Overhead Byte Processing

Client Interface Monitoring

Automatic Laser Shutdown

Jitter

Lamp Test

Onboard Traffic Generation

Card level indicators—Table G-1

Port level indicators—Table G-6.

11.10.3.1  Wavelength Identification

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.

Table 11-6 describes the required trunk transmit laser wavelengths for the 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 11-6 MXP_2.5G_10E_C Trunk Wavelengths 

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

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

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


Table 11-7 describes the required trunk transmit laser wavelengths for the 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.

Table 11-7 MXP_2.5G_10E_L Trunk Wavelengths 

Channel Number
Frequency (THz)
Wavelength (nm)
Channel Number
Frequency (THz)
Wavelength (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

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


11.10.4  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:

G97 Modify the 4x2.5G Muxponder Card Line Settings and PM Parameter Thresholds

G33 Create a Y-Cable Protection Group

NTP-G75 Monitor Transponder and Muxponder Performance

11.11  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.


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. The card versions along with their corresponding wavelengths are shown in Table 11-8.

Table 11-8 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.


Table 11-9 shows the input data rate for each client interface, and the encapsulation method. 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.

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 11-9 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 11-10 shows some of the mix and match possibilities on the various client ports. The table is intended to show the full client payload configurations for the card.

Table 11-10 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


11.11.1  Faceplates and Block Diagram

Figure 11-12 shows the MXP_MR_2.5G and MXPP_MR_2.5G faceplates.

Figure 11-12 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.

Figure 11-13 shows a block diagram of the MXP_MR_2.5G card. 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 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 11-13 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.

11.11.2  MXP_MR_2.5G and MXPP_MR_2.5G Functions

The functions of the MXP_MR_2.5G and MXPP_MR_2.5G cards are:

Performance Monitoring

Distance Extension

Slot Compatibility

Interoperability with Cisco MDS Switches

Client and Trunk Ports

Automatic Laser Shutdown

Card level indicators—Table G-1

Port level indicators—Table G-10

11.11.3  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:

G99 Modify the 2.5G Data Muxponder Card Line Settings and PM Parameter Thresholds

G33 Create a Y-Cable Protection Group (MXP_MR_2.5G only)

NTP-G75 Monitor Transponder and Muxponder Performance

11.12  MXP_MR_10DME_C and MXP_MR_10DME_L Cards

MXP_MR_10DME_L: (Cisco ONS 15454 only)

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

2-Gigabit Fibre Channel

4-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.

The MXP_MR_10DME_C and MXP_MR_10DME_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_MR_10DME_C and MXP_MR_10DME_L cards work with the 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.


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 MXP_MR_10DME_C and MXP_MR_10DME_L cards in Slots 1 to 6 and 12 to 17.


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 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.

Table 11-11 shows the input data rate for each client interface, and the encapsulation method. 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 11-11 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

2G FC

2.125 Gbps

Yes

1G FC

1.06 Gbps

Yes

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

2.125 Gbps

Yes

1G FICON/1G ISC-Compatible (ISC-1)/ 1G ISC-Peer (ISC-3)

1.06 Gbps

Yes

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. Table 11-12 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 11-12 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_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.

11.12.1  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 (237,255) 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" section for more detailed information.

High level provisioning support: The cards are initially provisioned using Cisco TransportPlanner software. Subsequently, the card can be monitored and provisioned using CTC software.

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 "G162 Change 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 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_MR_10DME_C and MXP_MR_10DME_L cards normally synchronize from the TCC2/TCC2P/TCC3 card. If for some reason, such as maintenance or upgrade activity, the TCC2/TCC2P/TCC3 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 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 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.

11.12.2  Faceplates and Block Diagram

Figure 11-14 shows the MXP_MR_10DME_C and MXP_MR_10DME_L faceplates and block diagram.

Figure 11-14 MXP_MR_10DME_C and MXP_MR_10DME_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 20-dB fiber attenuator (15 to 25 dB) 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 MXP_MR_10DME_C and MXP_MR_10DME_L cards.

11.12.3  MXP_MR_10DME_C and MXP_MR_10DME_L Functions

The functions of the MXP_MR_10DME_C and MXP_MR_10DME_L cards are:

Card level indicators—Table G-1

Port level indicators—Table G-9

11.12.3.1  Wavelength Identification

The card uses trunk lasers that are wavelocked, which allows the trunk transmitter to operate on the ITU 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.

Table 11-13 describes the required trunk transmit laser wavelengths for the MXP_MR_10DME_C card. The laser is tunable over 82 wavelengths in the C band at 50-GHz spacing on the ITU grid.

Table 11-13 MXP_MR_10DME_C Trunk Wavelengths 

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

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

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


Table 11-14 describes the required trunk transmit laser wavelengths for the MXP_MR_10DME_L card. The laser is fully tunable over 80 wavelengths in the L band at 50-GHz spacing on the ITU grid.

Table 11-14 MXP_MR_10DME_L Trunk Wavelengths 

Channel Number
Frequency (THz)
Wavelength (nm)
Channel Number
Frequency (THz)
Wavelength (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

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


11.12.4  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:

G148 Modify the 10G Data Muxponder Card Line Settings and PM Parameter Thresholds

G33 Create a Y-Cable Protection Group

NTP-G75 Monitor Transponder and Muxponder Performance

11.13  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.


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:

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.

The 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C muxponders pass all SONET/SDH overhead bytes transparently, section, or line termination.

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 performance monitoring. The 40G-MXP-C, 40E-MXP-C and 40ME-MXP-C cards work with the OTN devices defined in ITU-T G.709. The card supports ODTU23 multiplexing, an industry standard method for asynchronously mapping client payloads into a digitally wrapped envelope. See the "Multiplexing Function" section.

You can install and provision the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-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

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 client port of 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards does 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 11-15 lists the FEC configuration supported on OTU2/OTU2e protocol for 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards.

Table 11-15 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

Port 2

Standard and Enhanced FEC

Port 3

Standard and Enhanced FEC

Port 4

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-TXP-C and 40ME-TXP-C cards, the recovery from PSM protection switch takes about 3 to 4 minutes.

The 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards is tunable over C-band on the trunk port. The 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards support pluggable XFPs on the client ports on the card faceplate. The card uses dual LC connectors on the trunk side, and XFP modules on the client side for optical cable termination. The XFP pluggable modules are SR, LR, MM, DWDM, or CWDM and support an LC fiber connector. The 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards contains four XFP modules for the client interfaces. For optical termination, each XFP uses two LC connectors, which are labeled TX and RX on the faceplate. The trunk port is a dual LC connector facing downward at 45 degrees.

Table 11-16 shows the input data rate for each client interface.

Table 11-16 Client Interface Input Data Rates for 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards

Client Interface
Input Data Rate

8-Gigabit Fibre Channel

8.48 Gbps

10-Gigabit Fibre Channel

10.519 Gbps

10-GigabitEthernet LAN-Phy

10.312 Gbps

10-GigabitEthernet WAN-Phy

9.953 Gbps

OC-192/STM-64

9.953 Gbps

OTU2

10.709 Gbps

OTU2e

11.096 Gbps


11.13.1  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, seethe "Y-Cable and Splitter Protection" 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.


Figure 11-15 shows a typical unidirectional regeneration configuration.

Figure 11-15 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 software. Subsequently, the card can be monitored and provisioned using CTC software.

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 "G162 Change the ALS Maintenance Settings" section.

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 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards synchronize to the TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE cards. Because of a maintenance or upgrade activity, if the TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE 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.

11.13.2  Faceplate and Block Diagram

Figure 11-16 shows the faceplate and block diagram of the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards.

Figure 11-16 Faceplate and Block Diagram of the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards

For information about safety labels for the cards, 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 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 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards.

11.13.3  40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Functions

The functions of the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards are:

Card level indicators—Table G-1

Port level indicators—Table G-9

11.13.3.1  Wavelength Identification

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.

Table 11-17 lists the required trunk transmit laser wavelengths for the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards. The laser is tunable over 82 wavelengths in the C-band at 50-GHz spacing on the ITU grid.

Table 11-17 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Trunk Wavelengths 

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

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

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


11.13.4  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:

G293 Modify the 40G Muxponder Card Line Settings and PM Parameter Thresholds

G33 Create a Y-Cable Protection Group

NTP-G75 Monitor Transponder and Muxponder Performance

11.14  GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards

GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards are Gigabit Ethernet Xponders for the ONS 15454 ANSI and ETSI platforms.


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.

You can install and provision the GE_XP, and GE_XPE 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

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). Table 11-18 shows the card modes supported by each card.


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.


Table 11-18 GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Modes

Card Mode
Cards
Description

Layer 2 Ethernet switch

GE_XP

10GE_XP

GE_XPE

10GE_XPE

Provides capability to switch between any two ports irrespective of client or trunk port. Supported Ethernet protocols and services include 1+1 protection, QoS (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

10GE_XPE

Provides a point-to-point application in which each 10 Gigabit Ethernet client port is mapped to a 10 Gigabit Ethernet trunk port.

10GE MXP

20GE MXP

GE_XP

GE_XPE

Provides the ability to multiplex the twenty Gigabit Ethernet client ports 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).


11.14.1  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).

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 over the ONS 15454 DWDM platform.

Compatible with the ONS 15454 ANSI high-density shelf assembly, the ONS 15454 ETSI shelf assembly, ONS 15454 ETSI high-density shelf assembly, ONS 15454 M2, and the ONS 15454 M6 shelf assemblies. Compatible with TCC2, TCC2P, TCC3, TNC, TNCE, TSC, and TSCE cards.

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-Soloman (RS) (255,237) 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.

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.

11.14.2  Protocol Compatibility list

Table 11-19 lists the protocol compatibility for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards.

Table 11-19 Protocol Compatibility List for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards

Protocol
L1
1+1
FAPS
IGMP
REP
LACP
CFM
EFM
L1
 

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

 

11.14.3  Faceplate and Block Diagram

Figure 11-17 shows the GE_XP faceplate and block diagram. The GE_XPE faceplate and block diagram looks the same.

Figure 11-17 GE_XP and GE_XPE Faceplates and Block Diagram

The GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards have two trunk ports. The GE_XP and GE_XPE trunk ports are displayed as follows:

Trunk 1 and Trunk 2 on the faceplate

21-1 and 22-1 on CTC

21 (Trunk) and 22 (Trunk) on the Optics Thresholds table

Figure 11-18 shows the 10GE_XP faceplate and block diagram. The 10 GE_XPE faceplate and block diagram looks the same.

Figure 11-18 10GE_XP and 10GE_XPE Faceplates and Block Diagram

The 10GE_XP and 10GE_XPE card trunk ports are displayed as follows:

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

For information about safety labels for the cards, 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 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 GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards.

11.14.4  GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Functions

The functions of the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards are:

Card level indicators—Table G-1

Port level indicators—Table G-9

11.14.4.1  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) (GE_XPE only)

SFP - Fast Ethernet over DS3/E3 - SM - LC (PID ONS-SC-EOP3) (GE_XPE only)

SFP - E1/DS1 over Fast Ethernet - SM - LC (PID ONS-SC-E1-T1-PW) (GE_XPE only)

SFP - E3/DS3 PDH over Fast Ethernet - SM - LC (PID ONS-SC-E3-T3-PW) (GE_XPE only)


Note The recommended topology for using ONS-SC-E1-T1-PW and ONS-SC-E3-T3-PW SFPs is shown in Figure 11-19.

Figure 11-19 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.


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)

11.14.4.2  DWDM Trunk Interface

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.

11.14.4.3  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.


11.14.4.4  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.

11.14.4.5  Card Protection

The following card protection schemes are available for the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards.

Y-Cable Protection—See the "Y-Cable Protection" section.

1+1 Protection—See the "1+1 Protection" section.

Layer 2 Over DWDM Protection—See the "Layer 2 Over DWDM Protection" section.

11.14.4.5.1  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:

G33 Create a Y-Cable Protection Group

G198 Create 1+1 Protection for GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards

G381 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Layer 2 Protection Settings

11.14.5  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 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" section.

11.14.5.1  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 Troubleshooting Guide.

11.14.5.2  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.

11.14.5.3  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.

11.14.5.4  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.

11.14.5.5  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.

11.14.5.6  Related Procedure for Enabling IGMP Snooping

To enable IGMP snooping on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards, see the "G204 Enable IGMP Snooping on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards" section.

11.14.6  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.


11.14.6.1  Related Procedure for Enabling MVR

To enable MVR on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards, see the "G206 Enable MVR on a GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Card" section.

11.14.7  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.

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.

11.14.7.1  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 "G221 Enable MAC Address Learning on SVLANs for GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards" section.

11.14.8  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.

11.14.8.1  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 "G237 Retrieve and Clear MAC Addresses on SVLANs for GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards" section.

11.14.9  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.


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.

11.14.9.1  Related Procedure for Enabling Link Integrity

To enable link integrity on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards, see the "G205 Enable Link Integrity on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards" section.

11.14.10  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.

11.14.10.1  Related Procedure for Enabling Ingress CoS

To enable Ingress CoS on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards, see the:

"G380 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Ethernet Settings" section

"G612 Modify the Parameters of the Channel Group Using CTC" section

11.14.11  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

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).

11.14.11.1  Related Procedure for Provisioning CVLAN Rate

To provision CVLAN rate on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards, see the "G289 Provision CVLAN Rate Limiting on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Card" section.

11.14.12  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

11.14.12.1  Related Procedure for Provisioning CoS Based on DSCP

To provision CoS based on DSCP on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards, see the "G384 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE QinQ Settings" section.

11.14.13  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" section.

11.14.13.1  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.

11.14.13.2  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.

11.14.13.3  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.

11.14.13.4  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.

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.

11.14.13.5  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.


11.14.13.6  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.

11.14.13.7  Related Procedure for LACP

To provision Channel Group using LACP, see the "G281 Manage the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Channel Group Settings" section.

11.14.14  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" section. The following sections contain conceptual information about Ethernet CFM.

11.14.14.1  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.

11.14.14.2  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.


11.14.14.3  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).

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.

11.14.14.4  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.

11.14.14.5  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.

11.14.14.6  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.

11.14.14.7  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 "G283 Manage the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card CFM Settings" section.

11.14.15  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" section.

11.14.15.1  Components of the Ethernet OAM

Ethernet OAM consists of two major components, the OAM Client and the OAM Sublayer.

11.14.15.1.1  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.

11.14.15.1.2  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.

11.14.15.2  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

11.14.15.3  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.

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.

11.14.15.4  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.


11.14.15.5  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 "G285 Manage the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card EFM Settings" section.

11.14.16  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" section.

11.14.16.1  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.

11.14.16.2  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.

11.14.16.3  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.

11.14.16.4  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.

11.14.16.5  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.

11.14.16.6  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.

11.14.16.7  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.


11.14.16.8  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.

Enabling REP on trunk ports allows protection at the edge layer when the cards are connected in a ring.

11.14.16.9  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).

11.14.16.10  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 "G287 Manage the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card REP Settings" section.

11.14.17  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:

G165 Modify the GE_XP, 10GE_XP, GE_XPE, 10GE_XPE Cards Ethernet Parameters, Line Settings, and PM Thresholds

G311 Provision the Storm Control Settings for GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards

G208 Provision SVLAN Rate Limiting on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Card

G314 Add a GE_XP or 10GE_XP Card on a FAPS Ring

NTP-G75 Monitor Transponder and Muxponder Performance

11.15  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

Slot 2 in ONS 15454 M2 chassis

Slots 2 to 6 in ONS 15454 M6 chassis


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.

11.15.1  Key Features

The ADM-10G card has the following high-level features:

Operates with the TCC2, TCC2P, TCC3, TNC, TNCE, TSC, or TSCE.

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 TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE 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" section for more detailed information.

11.15.2  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 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.

11.15.2.1  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 ONS 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.

11.15.2.2  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.

11.15.2.2.1  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.

11.15.2.2.2  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."

11.15.2.3  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.

11.15.2.4  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).

11.15.3  Faceplate and Block Diagram

Figure 11-20 shows the ADM-10G card faceplate.

Figure 11-20 ADM-10G Card Faceplate and Block Diagram

11.15.4  Port Configuration Rules

ADM-10G card client and trunk port capacities are shown in Figure 11-21.

Figure 11-21 ADM-10G Card Port Capacities

Port 17 acts as trunk2 or ILK1 interface based on single-card or double-card configuration.

11.15.5  Client Interfaces

The ADM-10G card uses LC optical port connectors and, as shown in Figure 11-21, 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=)

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)

11.15.6  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.

11.15.7  DWDM Trunk Interface

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)

11.15.8  Configuration Management

When using OC-48/STM-16 traffic, some contiguous port configurations, listed in Table 11-20, are unavailable due to hardware limitations. This limitation does not impact the Gigabit Ethernet payload.


Note The ADM-10G card cannot be used in the same shelf with SONET or SDH cross-connect cards.


Table 11-20 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

OC-48/STM-16 on Port 14

No OC-N/STM-N on Port 4 through Port 6

OC-48/STM-16 on Port 15

No OC-N/STM-N on Port 7 through Port 9

OC-48/STM-16 on Port 16

No OC-N/STM-N on Port 10 through Port 12



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.


Note In ADM-10G cards, the Gigabit Ethernet port does not support flow control.


11.15.9  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.

11.15.10  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.

11.15.10.1  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.

11.15.10.2  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.

11.15.11  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:

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.


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 15. 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.

11.15.12  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.


Available Circuit Sizes

Table 11-21 and Table 11-22 show the circuit sizes available for the ADM-10G card.

Table 11-21 Supported SONET Circuit Sizes of ADM-10G card on ONS 15454

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 11-22 Supported SDH Circuit Sizes of ADM-10G card on ONS 15454 SDH

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.


11.15.12.1  Related Procedure for VCAT Circuit

The following is the list of procedures related to creating VCAT circuits:

G245 Create an Automatically Routed VCAT Circuit

G246 Create a Manually Routed VCAT Circuit

11.15.13  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.

11.15.13.1  Related Procedure for IPPM

To enable IPPM on the ADM-10G card, see the "G247 Enable or disable Path Performance Monitoring on Intermediate Nodes" section.

11.15.14  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.

11.15.15  Performance Monitoring Parameter Definitions

This section describes the STS and VC-4 path performance monitoring parameters that ADM-10G card support.

Table 11-23 lists the STS near-end path performance monitoring parameters.

Table 11-23 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.

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 11-24 gives the VC-4 near-end path performance monitoring parameters definition that ADM-10G card support.

Table 11-24 VC-4 Near-end Path Performance Monitoring Parameters

Parameter
Definition

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.

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 available time during a fixed measurement interval.

HP-SESR

High-Order Path Severely Errored Second Ratio (HP-SESR) is the ratio of SES to total seconds in available time during a fixed measurement interval.

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.

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.


11.15.16  ADM-10G Functions

The functions of the ADM-10G card are:

Automatic Laser Shutdown

Card level indicators—Table G-1

Port level indicators—Table G-11

11.15.17  Related Procedures for ADM-10G Card

The following is the list of procedures and tasks related to the configuration of the ADM-10G card:

G170 Provision the ADM-10G Card Peer Group, Ethernet Settings, Line Settings, PM Parameters, and Thresholds

G200 Create, Delete, and Manage STS or VC Circuits for the ADM-10G Card

NTP-G75 Monitor Transponder and Muxponder Performance

G333 Add an ADM-10G card to an Existing Topology

11.16  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 for the ONS 15454 ANSI and ETSI platforms. The OTU2_XP card supports multiple configurations.

Table 11-25 describes the different configurations supported by the OTU2_XP card and the ports that must be used for these configurations.

Table 11-25 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 regenerator (with enhanced FEC (E-FEC) only on one port)

Trunk port 1

Trunk port 2

Trunk port 1

Trunk port 2

10 GE LAN Phy to WAN Phy

Client port

Client port in transponder or trunk port in regenerator configuration

Trunk port

Trunk port in transponder or regenerator configuration

1 x 10G E-FEC regenerator
(with E-FEC on two ports)

Not used

Not used

Trunk port

Trunk port

1 x 10G splitter protected transponder

Client port

Not used

Trunk port (working)

Trunk port (protect)


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 through 6 or 12 through 17. 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.

11.16.1  Key Features

The OTU2_XP card has the following high-level features:

10G transponder, regenerator, and splitter protection capability on the ONS 15454 DWDM platform.

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.

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-Soloman (RS) (255,237) 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.

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. 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.

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.

11.16.2  Faceplate and Block Diagram

Figure 11-22 shows the OTU2_XP card faceplate and block diagram.

Figure 11-22 OTU2_XP Card Faceplate and Block Diagram


Note The Swan FPGA is automatically loaded when the LAN Phy to WAN Phy conversion feature is enabled on the OTU2_XP card. The Barile FPGA is automatically loaded when the LAN Phy to WAN Phy conversion feature is disabled on the OTU2_XP card.


11.16.3  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 11-25). This following section describes the client and trunk rates supported on the OTU2_XP card for different card configurations:

11.16.3.1  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

11.16.3.2  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

10G Ethernet LAN Phy

10G Fibre Channel

OTU2 G.709

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.


11.16.4  Configuration Management

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.

AIS/Squelch—Provisionable AIS/Squelch mode configuration when the card configuration is set as either Transponder, Mixed, or Standard Regen. The AIS/Squelch mode configuration can be chosen as AIS or Squelch. For Enhanced FEC card configuration, CTC automatically sets the AIS/Squelch mode configuration as AIS. For 10G Ethernet LAN Phy to WAN Phy mode, the CTC automatically selects the AIS/Squelch of port pair (1-3) as Squelch. You cannot provision the AIS/Squelch parameter.


Note When AIS/Squelch is enabled in Standard Regen configuration with port pairs (1-3) and (2-4), Squelch is supported on ports 1 and 2 and AIS on ports 3 and 4.



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 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" section 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.

11.16.5  OTU2_XP Card Configuration Rules

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.

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 listed in the Table 11-26. For more information on editing the NE Default values, see the "NTP-G135 Edit Network Element Defaults" task.

Table 11-26 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 11-27 provides a summary of transitions allowed for the OTU2_XP card configurations.

Table 11-27 Card Configuration Transition Summary 

Card Configuration
Transition To
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

10G Ethernet LAN Phy to WAN Phy

Yes

Yes

No

The 10G Ethernet LAN 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.


11.16.6  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.

11.16.7  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.


Note The Forward Error Correction (FEC) Mismatch (FEC-MISM) alarm will not be raised on OTU2_XP card when you choose Transparent Standard Use.


11.16.8  OTU2_XP Functions

The functions of the OTU2_XP card are:

Automatic Laser Shutdown

Y-Cable and Splitter Protection

Card level indicators—Table G-1

Port level indicators—Table G-11

11.16.9  Related Procedures for OTU2_XP Card

The following is the list of procedures and tasks related to the configuration of the OTU2_XP card:

G197 Provision the OTU2_XP Card Line Settings, PM Parameters, and Thresholds

G33 Create a Y-Cable Protection Group

G199 Create a Splitter Protection Group for the OTU2_XP Card

NTP-G75 Monitor Transponder and Muxponder Performance

11.17  TXP_MR_10EX_C Card

The TXP_MR_10EX_C card is a multirate transponder for the ONS 15454 platform. 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. 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)


On its faceplate, the TXP_MR_10EX_C card contains two transmit and receive connector pairs, one for the trunk port and one for the client port. Each connector pair is labeled.

11.17.1  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.

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.

11.17.2  Faceplate and Block Diagram

Figure 11-23 shows the TXP_MR_10EX_C faceplate and block diagram.

Figure 11-23 TXP_MR_10EX_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 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.

11.17.3  TXP_MR_10EX_C Functions

The functions of the TXP_MR_10EX_C card are:

Client Interface

DWDM Trunk Interface

FEC

Client-to-Trunk Mapping

Automatic Laser Shutdown

Card level indicators—Table G-1

Port level indicators—Table G-6.

11.17.4  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:

G96 Provision the 10G Multirate Transponder Card Line Settings, PM Parameters, and Thresholds

NTP-G75 Monitor Transponder and Muxponder Performance

11.18  MXP_2.5G_10EX_C card

The MXP_2.5G_10EX_C card is a DWDM muxponder for the ONS 15454 platform that 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 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. 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.


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, which are necessary to provision the 4xOC-48 OCHCC circuit.


11.18.1  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 (237,255) 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 software. Subsequently, the card can be monitored and provisioned using CTC software.

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.

Control of layered SONET/SDH transport overhead: The card is provisionable to terminate regenerator 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 TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE card. If for some reason, such as maintenance or upgrade activity, the TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE 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.

11.18.2  Faceplate and Block Diagram

Figure 11-24 shows the MXP_2.5G_10EX_C faceplate and block diagram.

Figure 11-24 MXP_2.5G_10EX_C Faceplate and Block Diagram

For information about safety labels for the card, see the "Class 1 Laser Product Cards" section.

11.18.3  MXP_2.5G_10EX_C Functions

The functions of the MXP_2.5G_10EX_C card are:

Client Interface

DWDM Interface

FEC

Multiplexing Function

Timing Synchronization

SONET/SDH Overhead Byte Processing

SONET/SDH Overhead Byte Processing

Client Interface Monitoring

Automatic Laser Shutdown

Jitter

Lamp Test

Onboard Traffic Generation

Card level indicators—Table G-1

Port level indicators—Table G-6

11.18.3.1  Wavelength Identification

The card uses trunk lasers that are wavelocked, which allows the trunk transmitter to operate on the ITU 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.

Table 11-28 describes the required trunk transmit laser wavelengths for the MXP_2.5G_10EX_C card. The laser is tunable over 82 wavelengths in the C-band at 50-GHz spacing on the ITU grid.

Table 11-28 MXP_2.5G_10EX_C Trunk Wavelengths 

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

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

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


11.18.4  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:

G97 Modify the 4x2.5G Muxponder Card Line Settings and PM Parameter Thresholds

NTP-G75 Monitor Transponder and Muxponder Performance

11.19  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 Fibre Channel

2-Gigabit Fibre Channel

4-Gigabit Fibre Channel

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 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.


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.

Table 11-29 shows the input data rate for each client interface, and the encapsulation method. 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 11-29 MXP_MR_10DMEX_C Client Interface Data Rates and Encapsulation 

Client Interface
Input Data Rate
GFP-T G.7041 Encapsulation

2G FC

2.125 Gbps

Yes

1G FC

1.06 Gbps

Yes

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

2.125 Gbps

Yes

1G FICON/1G ISC-Compatible (ISC-1)/ 1G ISC-Peer (ISC-3)

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. Table 11-30 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 11-30 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.

11.19.1  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 (237,255) 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" section for more detailed information.

High-level provisioning support: The card is initially provisioned using Cisco TransportPlanner software. Subsequently, the card can be monitored and provisioned using CTC software.

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 "G162 Change the ALS Maintenance Settings" section.

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.

Control of layered SONET/SDH transport overhead: The card is provisionable to terminate regenerator 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 TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE card. If for some reason, such as maintenance or upgrade activity, the TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE 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.

11.19.2  Faceplate and Block Diagram

Figure 11-25 shows the MXP_MR_10DMEX_C faceplate and block diagram.

Figure 11-25 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.

11.19.3  MXP_MR_10DMEX_C Functions

The functions of the MXP_MR_10DMEX_C card are:

Card level indicators—Table G-1

Port level indicators—Table G-9

11.19.3.1  Wavelength Identification

The card uses trunk lasers that are wavelocked, which allows the trunk transmitter to operate on the ITU grid effectively. The MXP_MR_10DMEX_C card uses a C-band version of the MLSE-based UT module.

Table 11-31 describes the required trunk transmit laser wavelengths for the MXP_MR_10DMEX_C card. The laser is tunable over 82 wavelengths in the C-band at 50-GHz spacing on the ITU grid.

Table 11-31 MXP_MR_10DMEX_C Trunk Wavelengths 

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

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

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


11.19.4  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:

G148 Modify the 10G Data Muxponder Card Line Settings and PM Parameter Thresholds

NTP-G75 Monitor Transponder and Muxponder Performance

11.20  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, ONS 15454 M2, and ONS 15454 M6 platforms. 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.

The cards support aggregation of the following signal types:

SONET/SDH:

STM-1/OC-3

STM-4/OC-12

STM-16/OC-48

OTN:

OTU-1

OTU-2 (OTU1E/OTU2E)

Ethernet:

Fast Ethernet (FE)

Gigabit Ethernet (GE)

SAN:

Enterprise Systems Connection (ESCON)

1 Gigabit Fiber Channel or fiber connectivity (FICON)

2 Gigabit Fiber Channel or FICON

4 Gigabit Fiber Channel or FICON

8 Gigabit Fiber Channel or FICON

1G ISC3-STP

2G ISC3-STP

Video:

SD-SDI (270 Mbps)

HD-SDI (1.485 Gbps)

Third-generation SDI (3G-SDI) (2.970 Gbps)

The AR_MXP, AR_XP, and AR_XPE cards pass all SONET/SDH overhead bytes transparently.


Caution The AR_MXP, AR_XP, and AR_XPE cards can be damaged if dropped. Handle it safely.

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 AR_MXP, AR_XP, and AR_XPE cards work with the OTN devices defined in ITU-T G.709. The client can be OTU1 with standard G.975 FEC or disabled FEC. The cards provide standard 4 x OTU1 to OTU2 multiplexing. The card is equipped with standard G.709 FEC, E-FEC I.4, E-FEC I.7 and disabled FEC. The cards support ODU0/ODU1 to OTU1 or OTU2 multiplexing, an industry standard method for asynchronously mapping a SONET/SDH payload into a digitally wrapped envelope. For more details on multiplexing, see "Multiplexing Function" section.

Table 11-32 shows the input data rate for each client interface, and the encapsulation method.

Table 11-32 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

2GFC

2.125 Gbps

GFP-T

4GFC

4.25 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

HD-SDI

1.485 Gbps

GFP-F

SD-SDI

270 Mbps

GFP-F

3G-SDI

2.970 Gbps

GFP-F


11.20.1  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 Multiple Operating Modes.

Operating Mode to Client Payload Mapping—Each operating mode supports a specific set of client payloads. Table 11-33 and Table 11-34 lists the supported payloads for each operating mode.

Table 11-33 AR_MXP, AR_XP, and AR_XPE Card Supported Client-Payload Mapping—SONET/SDH, Ethernet, OTU1, and FC

Card Mode
Rate
SONET/SDH
Ethernet
OTU
FC
OC3/STM1
OC12/STM4
OC48/STM16
FE
GE
10 GE
OTU1
OTU2e
FICON1G/FC1G
FICON2G/FC2G
FICON4G/FC4G
FICON8G/FC8G
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

TXPP_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

MXP_DME

HIGH

No

No

No

No

Yes

N/A

No

No

Yes

Yes

Yes

No

No

MXPP_DME

HIGH

No

No

No

No

Yes

N/A

No

No

Yes

Yes

Yes

No

No

MXP_MR

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

MXPP_MR

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

MXP-4x2.5-10G

HIGH

No

No

Yes

No

No

N/A

Yes

No

No

No

No

No

No

MXPP-4x2.5-10G

HIGH

No

No

Yes

No

No

N/A

Yes

No

No

No

No

No

No

MXP-VD-10G

HIGH

No

No

No

No

No

N/A

No

No

No

No

No

No

No

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 11-34 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)

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 shelf and ten 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. For more detailed information, see "Y-Cable Protection" 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. 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 Cisco ONS 15454 DWDM Licensing Configuration Guide.

11.20.2  Faceplate and Block Diagram

Figure 11-26 shows the AXP_MXP, AR_XP, and AR_XPE faceplates.

The AR_MXP, AR_XP, and AR_XPE cards have eight SFP and two XFP ports. The client and trunk ports are either SFP (2.5 G) or XFP (10 G) based ports.

The AR_MXP, AR_XP, or AR_XPE card can be tuned to any wavelength over the C-band by inserting the required DWDM SFP or XFP on client or trunk ports. For optical termination, each XFP/SFP uses two LC connectors, which are labeled TX and RX on the faceplate.

Figure 11-26 AR_MXP, AR_XP, and AR_XPE Faceplates

Figure 11-27 shows the AXP_MXP, AR_XP, and AR_XPE block diagram.

Figure 11-27 AR_MXP, AR_XP, and AR_XPE Block Diagram

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 AXP_MXP, AR_XP, or AR_XPE card.

The AR_MXP, AR_XP, and AR_XPE cards can be installed in Slot 1 to Slot 6 and Slot 12 to Slot 17 in the Cisco ONS 15454 chassis, the Slot 2 to Slot 7 in the Cisco ONS 15454 M6 chassis, and Slot 2 and Slot 3 in the Cisco ONS 15454 M2 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.

11.20.3  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:

The OCHCC circuit should 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.

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.60, 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)

RGN (OTU1/OTU2 Regenerator)

MXP-VD-10G (Video Muxponder)

TXP_MR (Unprotected Transponder)

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 (Figure 11-28). 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:

1. 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.

2. Ports 2, 4, 5, 6, 7, or 8 can be configured as trunk ports.

3. 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 11-28 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 (Figure 11-29). 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:

1. XFP ports 9 and 10 must be grouped.

2. Port 10 must be configured as a trunk port.

3. Port 9 must be configured as a client port.

Figure 11-29 High-Rate TXP_MR Card Operating Mode Configuration

TXPP_MR (Protected Transponder)

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 (Figure 11-30). 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:

1. Three SFP ports must be grouped. The allowed port pairs are 1-5-6 or 2-7-8, or both.

2. 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.

3. Ports 1 and 2 must be configured as client ports.

Splitter protection is automatically created between ports 5-6 and 7-8.

Figure 11-30 Low-Rate TXPP_MR Card Operating Mode Configuration

MXP_DME (Unprotected Data Muxponder)

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 (Figure 11-31). 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:

1. 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.

2. Port 9 or 10 must be configured as a trunk port.

3. 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 (Figure 11-31). 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:

1. Eight SFP ports and one XFP port must be grouped. The allowed port pairs are 1-2-3-4-5-6-7-8-9.

2. Port 9 must be configured as a trunk port.

3. Ports 1 to 8 must be configured as client ports.

Figure 11-31 High-Rate MXP_DME Card Operating Mode Configuration

MXPP_DME (Protected Data Muxponder)

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 (Figure 11-32). 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:

1. 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.

2. Ports 9 and 10 must be configured as trunk ports.

3. 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 (Figure 11-32). 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:

1. 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.

2. Ports 9 and 10 must be configured as trunk ports.

3. Ports 1 to 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.

Figure 11-32 High-Rate MXPP_DME Card Operating Mode Configuration

MXP_MR (Unprotected Multirate Muxponder)

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 (Figure 11-33). 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:

1. N:1 muxponder must be created, where N varies from client ports 2 to 7.

2. Only ports 5, 6, 7, or 8 can be configured as trunk ports.

3. 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.

Figure 11-33 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 (Figure 11-34). 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:

1. N:1 muxponder must be created, where N varies from client ports 2 to 8.

2. Only ports 9 and 10 can be configured as trunk ports.

3. 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.

Figure 11-34 High-Rate MXP_MR Card Operating Mode Configuration

MXPP_MR (Protected Multirate Muxponder)

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 (Figure 11-35). 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:

1. N:2 muxponder must be created, where N varies from client ports 2 to 6.

2. Only ports 5 and 6 or 7 and 8, or both can be configured as trunk port.

3. 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.

Figure 11-35 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 (Figure 11-36). 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 following provisioning rules:

1. N:2 muxponder must be created, where N varies from client ports 2 to 8.

2. Only ports 9 and 10 can be configured as trunk ports.

3. Ports 1 to 8 can 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.

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.

Figure 11-36 High-Rate MXPP_MR Card Operating Mode Configuration

MXP-4x2.5-10G (OC48/OTU1 Unprotected Muxponder)

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 (Figure 11-37).

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:

1. The allowed port pairs are 1-2-3-4-9 or 5-6-7-8-10, or both.

2. Ports 9 and 10 can be configured as trunk ports.

3. Ports 1-2-3-4 or 5-6-7-8 can be configured as client ports.

Figure 11-37 High-Rate MXP-4x2.5-10G Card Operating Mode Configuration

MXPP-4x2.5-10G (OC48/OTU1 Protected Muxponder)

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 (Figure 11-38).

The AR_XP or AR_XPE card can be configured as MXPP-4x2.5-10G card by adhering to the following provisioning rules:

1. 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.

2. Only ports 9 and 10 can be configured as trunk ports.

3. Ports 1-2-3-4 or 5-6-7-8 can 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.

Figure 11-38 High-Rate MXPP-4x2.5-10G Card Operating Mode Configuration

RGN (OTU1/OTU2 Regenerator)

The AR_MXP, AR_XP, or AR_XPE card can be configured as a low-rate or high-rate RGN card mode.

Low Rate—A maximum of four RGN configurations can be provisioned on a single AR_MXP, AR_XP, or AR_XPE card (Figure 11-39). 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:

1. The allowed port pairs are 1-2, 3-4, 5-6, 7-8 or 1-5, 2-6, 3-7, 4-8.

Figure 11-39 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 (Figure 11-40). 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:

1. The allowed port pairs are 9-10.

Figure 11-40 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.


Note Payload PMs are not supported in this operating mode.


MXP-VD-10G (Video Muxponder)

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 (Figure 11-41).

The AR_XP or AR_XPE card can be configured as MXP-VD-10G card by adhering to the following provisioning rules:

1. The allowed port pairs are 1-2-3-9 or 5-6-7-10.

2. Only ports 9 and 10 can be configured as trunk ports.

3. Ports 1-2-3 and 5-6-7 can be configured as client ports.

Figure 11-41 High-Rate MXP-VD-10G Card Operating Mode Configuration

11.20.4  Scenarios of Different Operational mode Configurations on a AR_MXP, 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_MXP, AR_XP, or AR_XPE card:

Scenario 1

In this example (Figure 11-43), the following three operational modes are configured on the AR_MXP 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)

Figure 11-42 Scenario 1

Scenario 2

In this example (Figure 11-43), 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)

Figure 11-43 Scenario 2

Scenario 3

In this example (Figure 11-44), 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)

Figure 11-44 Scenario 3

Scenario 4

In this example (Figure 11-45), 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)

Figure 11-45 Scenario 4

Scenario 5

In this example (Figure 11-46), 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)

Figure 11-46 Scenario 5

11.20.5  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:

Client Interface—Client Interface

DWDM Interface—DWDM Interface

DWDM Trunk Interface—DWDM Trunk Interface

FEC Feature—FEC

Timing Synchronization—Timing Synchronization

Y-Cable Protection—Y-Cable Protection

Jitter Considerations—Jitter Considerations

Card level indicators—Table G-1

Port level indicators—Table G-9

11.20.6  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:

"G321 Provision Multiple Operating Modes on AR_MXP, AR_XP, or AR_XPE Cards" section.

"G322 Modify the AR_MXP, AR_XP, or AR_XPE Card Line Settings and PM Parameter Thresholds" section.

NTP-G75 Monitor Transponder and Muxponder Performance

11.21  100G-LC-C,10x10G-LC, and CFP-LC Cards

11.21.1  100G-LC-C Card

The 100G-LC-C card is a tunable DWDM trunk card, which simplifies the integration and transport of 100 Gigabit Ethernet and OTU-4 interfaces and services into enterprises or service provider optical networks. The 100G-LC-C card is supported on Cisco ONS 15454 M2 and Cisco ONS 15454 M6 platforms.

The 100G-LC-C card transports 100 Gigabit Ethernet LAN-PHY and Optical Transport Network (OTN) Optical Transport Unit Level 4 (OTU4) over a 50-GHz spaced, 50-GHz stabilized, ITU-compliant wavelength. The card has a pluggable client interface that is used to provide transponder capabilities, mapping the client signal to a single DWDM line interface. The client port supports a standard CXP format pluggable compliant with 100G-BASE-SR10 LAN PHY or OTU4 equivalent interface.

The card is tunable on 96 wavelength channels spaced at 50-GHz over the entire C-band. The card provides advanced capabilities necessary to deliver 100-Gbps services, which includes protocol transparency, wavelength tunability, flow-through timing, management and performance monitoring capabilities.

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 performance monitoring. The 100G-LC-C card works with the OTN devices defined in ITU-T G.709.

The trunk ports on the 100G-LC-C card support the Ultra Forward Error Correction (UFEC) standard G.975.1 (sub-clause I.7) with 20% overhead. The UFEC provides an estimated gain between 0.5 dB to 1 dB for each span on the trunk interfaces with a resultant extension of the transmission range on these interfaces. The UFEC leverages on two orthogonally concatenated block code (BCH) algorithm super FEC codes. The constructed code is iteratively decoded to rebuild the original frame.

11.21.1.1  Benefits

The 100G-LC-C card provide the following benefits:

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.

Provides a 100 G DWDM trunk interface that supports up to 70000 ps/nm of CD robustness.

Enables configuration of the CD dispersion tolerance to 50000 ps/nm and 30000 ps/nm to reduce power consumption.

The card supports the following client signal types:

100 Gigabit Ethernet and OTU4

OTU4 from BP OTL4.10 (interconnect with 100G-LC-C and CFP client)

100 Gigabit Ethernet 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 Gigabit Ethernet from BP XLAUI (interconnect with CFP client)

11.21.1.2  Key Features

The key features of 100G-LC-C card are listed in the "Key Features of 100G-LC-C, 10x10G-LC, and CFP-LC Cards" section.

11.21.1.3  Faceplate

Figure 11-47 shows the 100G-LC-C faceplate.

Figure 11-47 100G-LC-C Faceplate

11.21.1.4  100G-LC-C Block Diagram

For information on safety labels for the cards, see the "Class 1M Laser Product Cards" section.


Caution A 20-dB fiber attenuator (15 to 25 dB) must be used when working with the cards in a loopback, on the trunk port. Do not use direct fiber loopbacks with the cards because it causes irreparable damage to the 100G-LC-C card.

The 100G-LC-C card is a single-slot card and can be installed in Slot 2 to Slot 7 in the Cisco ONS 15454 M6 chassis and Slot 2 and Slot 3 in the Cisco ONS 15454 M2 chassis. The card has one DWDM port and one CXP port.

The 100G-LC-C card interoperates with 10x10G-LC and CFP-LC cards through an ONS 15454 M6 or ONS 15454 M2 backplane.

Up to six 100G-LC-C cards can be installed per ONS 15454 M6 shelf assembly, supporting up to 42 100-Gbps interfaces per 42-rack units (RU) bay frame. It is possible to place up to two 100 G 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) or 15454-M2-FTA2 (for the M2 chassis) must be installed in the shelf where a 100G-LC-C 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.


11.21.1.5  Operating Modes for 100G-LC-C Card

The 100G-LC-C card supports the following operating modes:

TXP-100G (Standalone 100GE Transponder)

RGN-100G (100G Regenerator)

Each operating mode can be configured using the specific set of cards and client payloads. Table 11-36 describes how each mode can be configured, the supported payloads, and the valid port pair for a specific operating mode.

11.21.1.5.1  TXP-100G (Standalone 100GE Transponder)

The 100G-LC-C card can be configured as a standalone 100 Gigabit Ethernet transponder. The 100 Gigabit Ethernet traffic is supported on the CXP and coherent optical trunk. The 100 Gigabit Ethernet or OTU4 payload traffic is routed from the CXP 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.

11.21.1.5.2  RGN-100G (100G Regenerator)

The 100G-LC-C card can be configured as a regenerator. Two 100G-LC-C cards can be connected to work in a back-to-back mode connecting through the Cisco ONS 15454 M6 or Cisco ONS 15454 M2 backplane in the same shelf. The allowed port pairs are 2-3, 4-5, or 6-7.

The client signals supported are 100 Gigabit Ethernet or OTU4. Regeneration is performed leveraging on the OTU4 backplane interconnection supported by the Cisco ONS 15454 M6 or Cisco ONS 15454 M2 chassis; 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.

11.21.2  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 provide 10 Gbps services to support 10x10G-LC card.

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)

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 performance monitoring. The 10x10G-LC card works with the OTN devices defined in ITU-T G.709.

11.21.2.1  Key Features

The key features of 10x10G-LC card are listed in Key Features of 100G-LC-C, 10x10G-LC, and CFP-LC Cards.

11.21.2.2  Faceplate

Figure 11-48 shows the 10x10G-LC faceplate.

Figure 11-48 10x10G-LC Faceplate

11.21.2.3  10x10G-LC Block Diagram

For information on safety labels for the cards, see the "Class 1M Laser Product Cards" section.


Caution A 20-dB fiber attenuator (15 to 25 dB) must be used when working with the cards in a loopback, on the trunk port. Do not use direct fiber loopbacks with the cards because it causes irreparable damage to the 10x10G-LC card.

The 10x10G-LC card is a single-slot card and can be installed in Slot 2 to Slot 7 in the Cisco ONS 15454 M6 chassis and Slot 2 and Slot 3 in the Cisco ONS 15454 M2 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 an ONS 15454 M6 or ONS 15454 M2 backplane.


Note The fan-tray assembly 15454-M6-FTA2 (for the M6 chassis) or 15454-M2-FTA2 (for the M2 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.


11.21.2.4  Operating Modes for 10x10G-LC Card

The 10x10G-LC card supports the following operating modes:

MXP-10x10G (10x10G Muxponder)

RGN-10G (5x10G Transponder)/TXP-10G (5x10G Regenerator)

Low Latency

Fanout-10X10G

Each operating mode can be configured using the specific set of cards and client payloads. Table 11-36 describes how each mode can be configured, the supported payloads, and the valid port pair for a specific operating mode.

11.21.2.4.1  MXP-10x10G (10x10G Muxponder)

The 10x10G-LC card can be configured as a 10x10G muxponder. It can be connected with a 100G-LC-C card to support 10-port 10 G muxponder capabilities. The 100G-LC-C card can be connected through the Cisco ONS 15454 M6 or Cisco ONS 15454 M2 backplane (no client CXP required) with the 10x10G-LC card to provide OTN multiplexing of the 10 G data streams into a single 100 G DWDM OTU4 wavelength. The allowed port pairs are 2-3, 4-5, or 6-7.

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.

11.21.2.4.2  RGN-10G (5x10G Transponder)/TXP-10G (5x10G Regenerator)

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 11-35 shows the supported payload mapping on a particular port and its corresponding peer.

Table 11-35 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


11.21.2.4.3  Low Latency

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.

11.21.2.4.4  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)

11.21.3  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 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.

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.

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 performance monitoring.

11.21.3.1  Key Features

The key features of CFP-LC card are listed in Key Features of 100G-LC-C, 10x10G-LC, and CFP-LC Cards.

11.21.3.2  Faceplate

Figure 11-49 shows the CFP-LC faceplate.

Figure 11-49 CFP-LC Faceplate

11.21.3.3  Block Diagram

For information on safety labels for the cards, see the "Class 1M Laser Product Cards" section.


Caution A 20-dB fiber attenuator (15 to 25 dB) must be used when working with the cards in a loopback, on the trunk port. Do not use direct fiber loopbacks with the cards because it causes irreparable damage to the CFP-LC card.

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 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.


11.21.3.4  Operating Modes for CFP-LC Card

The CFP-LC card supports the following operating modes:

2x40G Muxponder

CFP-TXP (100G Transponder)

Each operating mode can be configured using the specific set of cards and client payloads. Table 11-36 describes how each mode can be configured, the supported payloads, and the valid port pair for a specific operating mode.

11.21.3.4.1  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 card to support 2-port 40 G muxponder capabilities. The 100G-LC card can be connected through the Cisco ONS 15454 M6 backplane (no client CXP 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.

11.21.3.4.2  CFP-TXP (100G Transponder)

The CFP-LC card can be configured as a 100 G transponder. It can be connected with the 100G-LC-C card to support 100GE-BASE-LR4 client interface for the 100-Gbps transponder capabilities. The 100G CXP pluggable available on the 100G-LC card supports only 100GE-BASE-SR10 client interface, while the 100GE-BASE-LR4 is supported using a CFP form factor only.

The CFP-LC card can be connected through the Cisco ONS 15454 M6 backplane 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.

11.21.3.5  Key Features of 100G-LC-C, 10x10G-LC, and CFP-LC Cards

The 100G-LC-C, 10x10G-LC, and CFP-LC cards support the following key features:

Operating Modes—The 100G-LC-C, 10x10G-LC, and CFP-LC 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 100G-LC-C, 10x10G-LC, or CFP-LC 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.

Each operating mode can be configured using the specific set of cards and client payloads. Table 11-36 describes how each mode can be configured, the supported payloads, and the valid port pair for a specific operating mode.

Table 11-36 Operating Modes and Supported Payloads for 100G-LC-C, 10x10G-LC, and CFP-LC Cards

Card (provisioning executed on this card)
Operational Mode
Peer Card (connected through backplane)
Supported Client Payloads
Valid Card Slot
Valid Peer Card Slot
100G-LC-C

TXP-100G (Standalone 100GE Transponder)

100GE, OTU4

M2—Slots 2 and 3
M6—Slots 2 to 7

RGN-100G (100G Regenerator)

100G-LC-C card


Regeneration of any 100 G configuration

M2—Slot-2
M2-—Slot-3


M6—Slot-2
M6—Slot-3
M6—Slot-4
M6—Slot-5
M6—Slot-6
M6—Slot-7

M2—Slot-3
M2—Slot-2


M6—Slot-3
M6—Slot-2
M6—Slot-5
M6—Slot-4
M6—Slot-7
M6—Slot-6

10x10G-LC

MXP-10x10G (10x10G Muxponder)

100G-LC-C card

OC192/STM-64, 10GE-LAN Phy, 10GE-WAN Phy (using OC192), OTU2, OTU2e, 8G FC, 10G FC, FICON

M2—Slot-2
M2-—Slot-3


M6—Slot-2
M6—Slot-3
M6—Slot-4
M6—Slot-5
M6—Slot-6
M6—Slot-7

M2—Slot-3
M2—Slot-2


M6—Slot-3
M6—Slot-2
M6—Slot-5
M6—Slot-4
M6—Slot-7
M6—Slot-6

RGN-10G (5x10G Transponder)

10GE-LAN Phy, OTU2

M2—Slots 2 and 3

M6—Slots 2 to 7

TXP-10G (5x10G Regenerator)

10GE-LAN Phy, OTU2e, OTU2, OC192/STM-64, 8G FC, 10G FC

M2—Slots 2 and 3

M6—Slots 2 to 7

Low Latency

10GE, 10G FC

M2—Slots 2 and 3

M6—Slots 2 to 7

Fanout-10X10G

10GE

M2—Slots 2 and 3

M6—Slots 2 to 7

CFP-LC

2x40G Muxponder

100G-LC-C card

OTU3/40GE-LAN Phy

M6—Slot-3
M6—Slot-5

M6—Slot 2 or 5
M6—Slot 4 or 7

CFP-TXP (100G Transponder)—One port

CFP-TXP (100G Transponder)—Two ports

100G-LC-C card

OTU4, 100GE

M6—Slot-3
M6—Slot-5

M6—Slot 2 or 5
M6—Slot 4 or 7

 

Two 100G-LC-C cards

OTU4, 100GE

M6—Slot-3
M6—Slot-5

M6—Slot 2 or 5
M6—Slot 4 or 7


For operating modes of the respective cards, see the "Operating Modes for 100G-LC-C Card" section, "Operating Modes for 10x10G-LC Card" section, and "Operating Modes for CFP-LC Card" section.

Protocol Transparency—The 100G-LC-C card delivers any 100 Gbps services for cost-effective, point-to-point networking for the Cisco ONS 15454 platform. Table 11-37 shows the transponder client configurations and mapping for 100G-LC-C card. The 10x10G-LC card delivers any 10 Gbps services for cost-effective, point-to-point networking for the Cisco ONS 15454 platform. In case of 100 G muxponder clients that are mapped into OTU4 DWDM wavelength, Table 11-38 shows the transponder client configurations and mapping for the 10x10G-LC card. Table 11-39 shows the transponder client configurations and mapping for the CFP-LC card.

Table 11-37 Transponder Client Configurations and Mapping for 100G-LC-C Card

Client
 
Trunk
Format
Rate (Gbps)
Mapping
Format
Rate with 7% GFEC, 20% GFEC, or EFEC OH (Gbps)

100GE LAN-PHY

101.125

Bit transparent through standard G.709v3 mapping

OTU4         111.809    

OTU4

111.809

Transparent G.709 standard


Table 11-38 Transponder Client Configurations and Mapping for 10x10G-LC Card

Client
Mapping
Format
Rate (Gbps)
 

10GE LAN-PHY

10.3125

CBR-BMP clause 17.2.4 (ex G sup43 7.1) + GMP ODU2e to OPU3e4

10GE LAN-PHY

10.3125

GFP-F clause 17.4.1 (ex G sup43 7.3) + GMP ODU2 to OPU3e4

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


Table 11-39 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 through standard G.709v3 mapping


OTU4         111.809

OTU4

111.809

Transparent G.709 standard

40GE LAN-PHY

41.250

1024b/1027b transc + OPU4 GMP G709 Appendix VIII

OTU3

43.018

Transparent G.709 standard


Flow-Through Timing—The 100G-LC-C, 10x10G-LC, and CFP-LC 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 100G-LC-C, 10x10G-LC, and CFP-LC cards. For more information on FELC, see the "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-LC-C card. 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 and 10x10G-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. 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 card.

Generalized Multiprotocol Label Switching — The Generalized Multiprotocol Label Switching (GMPLS) circuit can be created on the 100G-LC-C and 10 x10G-LC cards. However, this circuit cannot be created when the card is in 100 G regenerator mode. When the card is configured in MXP-10 x 10G 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 card) of the CFP-LC card, and the OTU4 client and trunk ports of the 100G-LC-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.

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 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 cards when the trunk port in out of service or in maintenance. The 100G-LC-C cards have the ability to receive optical signals even when the TX power is turned off.

Licensing—The 100G-LC-C card adds the capability to cost-effectively transport the 10 G 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 10 G service. For more information on licensing, see the Cisco ONS 15454 DWDM Licensing Configuration Guide.


Note Licensing is not supported on the CFP-LC card.


11.21.3.6  Functions and Features

The cards have the following functions and features:

FEC Feature—FEC

Timing Synchronization—Timing Synchronization

Jitter Considerations—Jitter Considerations

Card level indicators—Table G-1

Port level indicators—Table G-12

11.22  Related Procedures for 100G-LC-C, 10x10G-LC, and CFP-LC Cards

"G235 Provision an Operating Mode on the 100G-LC-C, 10x10G-LC, or CFP-LC Card" section.

"G236 Modify the 100G-LC-C, 10x10G-LC, or CFP-LC Card Line Settings and PM Parameter Thresholds" section.

NTP-G75 Monitor Transponder and Muxponder Performance.

11.23  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.

11.23.1  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.

11.24  SFP, SFP+, XFP, CXP, and CFP Modules

Small Form-factor Pluggable (SFP), Enhanced Small-Form-factor Pluggable (SFP+), 10-Gbps SFP (XFP), CXP, and C Form-factor pluggable (CFP) 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+, XFP, CXP, and CFP modules and for a list of SFP, SFP+, XFP, CXP, and CFP modules supported by the transponder and muxponder cards, see the Installing the GBIC, SFP, SFP+, XFP, CXP, and CFP Optical Modules in Cisco ONS Platforms.

In CTC, SFP, SFP+, XFP, CXP, and CFP modules are called pluggable port modules (PPMs). To provision SFP, SFP+, XFP, CXP, or CFP module and change the line rate for multirate PPMs, see the DLP-G726 Preprovisioning a Multirate PPM task.

11.25  Procedures for Transponder and Muxponder Cards

The procedures described below explain how to provision transponder (TXP), muxponder (MXP), Xponder (GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE), and ADM-10G cards. The provisioning must be performed before you provision the dense wavelength division multiplexing (DWDM) network and create circuits.

11.25.1  Before You Begin

Before performing any of the following procedures, investigate all alarms and clear any trouble conditions. Refer to the Cisco ONS 15454 DWDM Troubleshooting Guide as necessary.


Caution Provisioning TXP and MXP cards can be service affecting. You should make all changes during a scheduled maintenance window.

This section lists the chapter procedures (NTPs). Turn to a procedure for applicable tasks (DLPs).

1. G128 Manage Pluggable Port Modules—Complete this procedure to provision a multirate pluggable port module (PPM), provision or change the optical line rate of a PPM, or delete a PPM. PPMs provide the fiber interface to the TXP, MXP, and ADM-10G cards. With the exception of the TXP_MR_10G card, all TXPs, MXPs, and ADM-10G cards accept PPMs.

2. G33 Create a Y-Cable Protection Group—As needed, complete this procedure for TXP, MXP, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, or OTU2_XP cards that will be protected with Y-cable protection.

3. G199 Create a Splitter Protection Group for the OTU2_XP Card—As needed, complete this procedure to create a splitter protection group for an OTU2_XP card.

4. G198 Create 1+1 Protection for GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards—As needed, complete this procedure to create 1+1 protection for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards.

5. G98 Provision the 2.5G Multirate Transponder Card Line Settings and PM Parameter Thresholds—As needed, complete this procedure to change the transmission settings for TXP_MR_2.5G and TXPP_MR_2.5G cards.

6. G96 Provision the 10G Multirate Transponder Card Line Settings, PM Parameters, and Thresholds—As needed, complete this procedure to change the transmission settings for TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, and TXP_MR_10EX_C cards.

7. NTP-G292 Provision the 40G Multirate Transponder Card Line Settings, PM Parameters, and Thresholds, page 6-72—As needed, complete this procedure to change the transmission settings for 40E-TXP-C and 40ME-TXP-C cards.

8. G170 Provision the ADM-10G Card Peer Group, Ethernet Settings, Line Settings, PM Parameters, and Thresholds—As needed, complete this procedure to provision the transmission settings for ADM-10G cards.

9. G97 Modify the 4x2.5G Muxponder Card Line Settings and PM Parameter Thresholds—As needed, complete this procedure to change the transmission settings for MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, and MXP_2.5G_10EX_C cards.

10. G99 Modify the 2.5G Data Muxponder Card Line Settings and PM Parameter Thresholds—As needed, complete this procedure to change the transmission settings for MXP_MR_2.5G and MXPP_MR_2.5G cards.

11. G148 Modify the 10G Data Muxponder Card Line Settings and PM Parameter Thresholds—As needed, complete this procedure to change the transmission settings for MXP_MR_10DME_C, MXP_MR_10DME_L, and MXP_MR_10DMEX_C cards.

12. G293 Modify the 40G Muxponder Card Line Settings and PM Parameter Thresholds—As needed, complete this procedure to change the transmission settings for 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards.

13. G281 Manage the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Channel Group Settings—As needed, complete this procedure to change the channel group settings for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards.

14. G283 Manage the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card CFM Settings—As needed, complete this procedure to change the CFM settings for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards.

15. G285 Manage the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card EFM Settings—As needed, complete this procedure to change the EFM settings for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards.

16. G287 Manage the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card REP Settings—As needed, complete this procedure to change the REP settings for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards.

17. G165 Modify the GE_XP, 10GE_XP, GE_XPE, 10GE_XPE Cards Ethernet Parameters, Line Settings, and PM Thresholds—As needed, complete this procedure to change the transmission settings for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards.

18. G314 Add a GE_XP or 10GE_XP Card on a FAPS Ring—As needed, complete this procedure to add a GE_XP or 10GE_XP Card on a FAPS Ring.

19. G197 Provision the OTU2_XP Card Line Settings, PM Parameters, and Thresholds—As needed, complete this procedure to change the transmission settings for OTU2_XP cards.

20. G162 Change the ALS Maintenance Settings—As needed, complete this procedure to change the automatic laser shutdown settings for a TXP or MXP card.

21. G302 Configure Loopback on 100G-LC-C, 10x10G-LC, and CFP-LC Cards—As needed, complete this procedure to configure the loopback on the 100G-LC or 10x10G-LC card.

22. G299 Configure the Backplane Loopback on 100G-LC-C, 10x10G-LC, and CFP-LC Cards—As needed, complete this procedure to configure the backplane loopback on the 100G-LC or 10x10G-LC card.

23. G192 Force FPGA Update—As needed, complete this procedure to force an upgrade of the FPGA image on the MXP_MR_10DME_C, MXP_MR_10DME_L, and MXP_MR_10DMEX_C cards.

24. G196 Force FPGA Update When the Card is Part of a Protection Group—As needed, complete this procedure to force an upgrade of the FPGA image on the MXP_MR_10DME_C, MXP_MR_10DME_L, and MXP_MR_10DMEX_C cards when the card is part of a protection group.

25. G232 Enabling Error Decorrelator—As needed, complete this procedure to enable error decorrelator on a TXP_MR_10EX_C, MXP_2.5G_10EX_C, or MXP_MR_10DMEX_C card.

NTP-G128 Manage 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.

Tools/Equipment

None

Prerequisite Procedures

DLP-G723 Install PPM on a Line Card

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



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.



Note The hardware device that plugs into a TXP, MXP, AR_MXP, AR_XP, AR_XPE, 100G-LC-C, 10x10G-LC, CFP-LC, 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). In CTC, SFPs, XFPs, CXPs, and CFPs are called pluggable port modules (PPMs). SFPs/XFPs/CXPs/CFPs 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, XFPs, and CXPs, see the "SFP, SFP+, XFP, CXP, and CFP Modules" section.



Step 1 Complete the DLP-G46 Log into CTC task to log into an ONS 15454 on the network. If you are already logged in, continue with Step 2.

Step 2 Click the Alarms tab:

a. Verify that the alarm filter is not turned on. See the "DLP-G128 Disable Alarm Filtering" task as necessary.

b. Verify that no unexplained conditions appear. If unexplained conditions appear, resolve them before continuing. Refer to the Cisco ONS 15454 DWDM Troubleshooting Guide.

Step 3 If you are provisioning a MXP_MR_2.5G or MXPP_MR_2.5G card, complete the "DLP-G235 Change the 2.5G Data Muxponder Card Mode" task. If not, continue with Step 4

Step 4 If you are provisioning a MXP_MR_10DME_C, MXP_MR_10DME_L, or MXP_MR_10DMEX_C card, complete the "DLP-G332 Change the 10G Data Muxponder Port Mode" task. If not, continue with Step 5.

Step 5 If you are provisioning a GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE card, complete the "DLP-G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode" task. If not, continue with Step 6.

Step 6 If you are provisioning a OTU2_XP card, complete the "DLP-G452 Change the OTU2_XP Card Mode" task. If not, continue with Step 7.

Step 7 If you are provisioning a PPM on an ADM-10G card, complete the "DLP-G411 Provision an ADM-10G PPM and Port" task. If not, continue with Step 10.

Step 8 If you are provisioning a PPM on an AR_MXP, AR_XP, or AR_XPE card, complete the "NTP-G321 Provision Multiple Operating Modes on AR_MXP, AR_XP, or AR_XPE Cards" task. If not, continue with Step 10.

Step 9 If you are provisioning a PPM on an 100G-LC-C, 10x10G-LC, or CFP-LC card, complete the "NTP-G235 Provision an Operating Mode on the 100G-LC-C, 10x10G-LC, or CFP-LC Card" task. If not, continue with Step 10.

Step 10 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, 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 11 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 Verify Topologies for ETR_CLO and ISC Services" task. Otherwise, continue with Step 12.

Step 12 Complete the "DLP-G278 Provision the Optical Line Rate" task to assign a line rate to a TXP, MXP, AR_MXP, AR_XP, AR_XPE, 100G-LC-C, 10x10G-LC, CFP-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 13 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 Change 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.

Tools/Equipment

None

Prerequisite Procedures

DLP-G46 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



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:

a. Click the Admin State table cell and choose OOS,DSBLD (ANSI) or Locked,Maintenance (ETSI).

b. 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:

a. Click the Admin State table cell and choose OOS,DSBLD (ANSI) or Locked,Maintenance (ETSI).

b. Click Apply, then Yes.

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).

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.


Note The 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.

Step 9 Return to your originating procedure (NTP).


DLP-G332 Change the 10G Data Muxponder Port Mode

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.

Tools/Equipment

None

Prerequisite Procedures

DLP-G46 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



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).



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 2 Click the Provisioning > Card tabs.

Step 3 Change the port mode as described in Table 11-40.


Note The PPM port rates are provisioned in the DLP-G726 Preprovisioning a Multirate PPM task.


Table 11-40 10G Data Muxponder Card Port Modes 

Parameter
Description
Options

Port 1-4 Mode

Sets the mode of operation for Ports 1-1 through 4-1.

Chose one of the following:

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 Ports 5-1 through 8-1.

Chose one of the following:

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.


Step 4 Click Apply.

Step 5 Return to your originating procedure (NTP).



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.


DLP-G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode

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.

Tools/Equipment

None

Prerequisite Procedures

DLP-G46 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



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.

a. For the first port that is not out of service, in the Admin State column, choose OOS,DSBLD (ANSI) or Locked,disabled (ETSI).

b. Repeat Step a for each port that is not out of service.

c. Click Apply.

Step 4 Click the Provisioning > Card tabs.

Step 5 Choose one of the card modes shown in Table 11-41.

Table 11-41 GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Modes

Mode
Cards
Description

L2 over DWDM

GE_XP

10GE_XP

GE_XPE

10GE_XPE

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

10GE TXP

10GE_XP

10GE_XPE

Provisions the 10GE_XP or 10GE_XPE as a 10 Gigabit 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

GE_XPE

Provisions the GE_XP or GE_XPE as a 10 Gigabit Ethernet 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 Gigabit Ethernet client Ports 11-1 through 20-1 is multiplexed and sent to 10 Gigabit Ethernet trunk Port 22-1.

20GE MXP

GE_XP

GE_XPE

Provisions the GE_XP or GE_XPE as a 20 Gigabit Ethernet muxponder. Traffic received on Gigabit Ethernet client Ports 1-1 through 20-1 is multiplexed and sent to 10 Gigabit Ethernet trunk 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 the "DLP-G380 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Ethernet Settings" task.

Step 6 Click Apply, then click Yes in the confirmation dialog box.

Step 7 Return to your originating procedure (NTP).


DLP-G411 Provision an ADM-10G PPM and Port

Purpose

This task provisions a fixed-rate PPM and port on an ADM-10G PPM card.

Tools/Equipment

None

Prerequisite Procedures

DLP-G46 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



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 name.

Step 6 In the Pluggable Ports area, click Create. The Create Ports dialog box appears.

Step 7 In the Create Ports 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.

Step 10 Return to your originating procedure (NTP).


DLP-G452 Change 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.

Tools/Equipment

None

Prerequisite Procedures

DLP-G46 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



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.


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 tab.

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.

a. For the first port that is not out of service, in the Admin State column, choose OOS, DSBLD (ANSI) or Locked, disabled (ETSI).

b. Repeat Step a for each port that is not out of service.

c. Click Apply.

Step 4 Click the Provisioning > Card tab.

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.

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.


Note If 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-181 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.

Step 7 Return to your originating procedure (NTP).


DLP-G274 Verify Topologies for ETR_CLO and ISC Services

Purpose

This task verifies that the DWDM network topology can support the IBM ETR_CLO and ISC services.

Tools/Equipment

Cisco TransportPlanner site plan

Prerequisite Procedures

DLP-G46 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



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

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 11-50 shows a single-span topology as displayed in Cisco TransportPlanner.

Figure 11-50 Single-Span Topology

Point-to-Point—Two terminal sites with one of the following sets of cards installed:

32MUX-O and 32DMX-O cards

32WSS and 32DMX cards

32WSS and 32-DMX-O cards

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

Line amplifiers can be installed between the terminal sites, but intermediate (traffic terminating) sites cannot be installed. Figure 11-51 shows a point-to-point topology as shown in Cisco TransportPlanner.

Figure 11-51 Point-to-Point Topology

Two hubs—Two hub nodes in a ring with one of the following sets of cards installed:

32MUX-O and 32DMX-O cards

32WSS and 32DMX cards

32WSS and 32-DMX-O cards

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

Line amplifiers can be installed between the hubs. Figure 11-52 shows two hub nodes with no line amplifier nodes installed. Figure 11-53 shows two hub nodes with line amplifier nodes installed.

Figure 11-52 Hubs with No Line Amplifiers

Figure 11-53 Hubs with Line Amplifiers

Step 3 Return to your originating procedure (NTP).


DLP-G278 Provision the Optical Line Rate

Purpose

This task provisions the line rate for TXP, MXP, AR_MXP, AR_XP, AR_XPE, 100G-LC-C, 10x10G-LC, CFP-LC, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, ADM-10G, and OTU2_XP cards.

Tools/Equipment

None

Prerequisite Procedures

DLP-G46 Log into CTC

DLP-G726 Preprovisioning a Multirate PPM

G274 Verify Topologies for ETR_CLO and ISC Services, if you are provisioning an ETR_CLO service.

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher



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.



Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the TXP, MXP, AR_MXP, AR_XP, AR_XPE, 100G-LC-C, 10x10G-LC, CFP-LC, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, or OTU2_XP 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.

a. Click the Provisioning > OTN > OTN Lines tabs.

b. In the ITU-T G.709 OTN field for the respective PPM, choose Disable.

c. In the FEC field for the respective PPM, choose Disable.

d. 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 4 Click the Provisioning > Pluggable Port Modules tabs.

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 11-42 for definitions of the supported rates on the TXP, MXP, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, OTU2_XP, 100G-LC-C, 10x10G-LC, CFP-LC, AR_MXP, AR_XP, or AR_XPE card.

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.

Table 11-42 PPM Port Types 

Card
Port Type

TXP_MR_2.5G

TXPP_MR_2.5G

OC-3/STM1—155 Mbps

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

MXP_2.5G_10E

MXP_2.5G_10E_C

MXP_2.5G_10E_L

MXP_2.5G_10EX_C

OC-48/STM16—2.48 Gbps1

TXP_MR_10G2

SONET (OC-192)/SDH (STM-64) including 10G Ethernet WAN Phy

10G Ethernet LAN Phy

TXP_MR_10E

TXP_MR_10E_C

TXP_MR_10E_L

TXP_MR_10EX_C

SONET (OC-192)/SDH (STM-64) including 10G Ethernet WAN Phy—10 Gbps

10G Ethernet LAN Phy—10 Gbps Ethernet

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)

40G Ethernet LAN Phy

OTU3

MXP_MR_2.5G

MXPP_MR_2.5G

If the card mode is FC_GE:

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)

FICON2G ISL—Fiber connectivity 2.125 Gbps (IBM signal) (Port 1-1 only)

ONE_GE—One Gigabit Ethernet 1.125 Gbps (Ports 1-1 and 2-1 only)

If the card mode is Mixed:

FC1G ISL—Fibre Channel 1.06 Gbps (Port 1-1 only)

FICON1G ISL—Fiber connectivity 1.06 Gbps (IBM signal) (Port1-1 only)

ONE_GE—One Gigabit Ethernet 1.125 Gbps (Port 1-1 only)

ESCON—Enterprise System Connection 200 Mbps (IBM signal) (Ports 5-1 through 8-1)

If the card mode is ESCON:

ESCON—Enterprise System Connection 200 Mbps (IBM signal) (Ports 1-1 through 8-1)

MXP_MR_10DME_C

MXP_MR_10DME_L

MXP_MR_10DMEX_C

If the port mode is FC_GE_ISC:

FC1G—Fibre Channel 1.06 Gbps (Ports 1-1 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.)

FICON4G—Fiber connectivity 4.25 Gbps (IBM 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

GE_XP

10GE_XP

GE_XPE

10GE_XPE

GE_XP and GE_XPE client ports1

10GE_XP and 10GE_XPE client and trunk ports; GE_XP and GE_XPE trunk ports1

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

Note If 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.

AR_MXP

AR_XP

AR_XPE

OC-3/STM1—155 Mbps

OC-12/STM4—622 Mbps

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

FC2G—Fibre Channel 2.125 Gbps

FC4G—Fibre Channel 4.25 Gbps

FC8G—Fibre Channel 8.5 Gbps

FICON1G—Fiber connectivity1.06 Gbps (IBM signal)

FICON2G—Fiber connectivity 2.125 Gbps (IBM signal)

FICON4G—Fiber connectivity 4.25 (IBM signal)

FICON8G—Fiber connectivity 8.5 Gbps (IBM 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

100G-LC-C

10x10G-LC

CFP-LC

SONET (OC-192)/SDH (STM-64)

10G Ethernet LAN Phy

40G Ethernet LAN Phy

100 GE

FC 8G

FC 10G

OTU2

OTU3

OTU4

1 Automatically provisioned when the PPM is created if the trunk port is out of service.

2 Provisioned on the Data Rate Selection tab.


Step 9 Return to your originating procedure (NTP).


NTP-G33 Create 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, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, or OTU2_XP cards when the cards are provisioned in the TXP or MXP mode. For additional information about Y-cable protection, see "Y-Cable Protection" section.

Tools/Equipment

Installed TXP, MXP, AR_MXP, AR_XP, AR_XPE, 10x10G-LC, CFP-LC, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, or OTU2_XP card.

Cisco TransportPlanner Traffic Matrix

Prerequisite Procedures

In the Cisco ONS 15454 Hardware Installation Guide: