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

• MXP-10x10G (10x10G Muxponder)

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

• Low Latency

• Fanout-10X10G

• TXPP-10G

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

The 10x10G-LC card can be configured as a 10x10G muxponder. It can be connected with a 100G-LC-C, 100G-CK-C, or 100GS-CK-C card to support 10-port 10 G muxponder capabilities. The 100G-LC-C, 100G-CK-C, 100GS-CK-C, or 200G-CK-C card can be connected through the chassis backplane (no client CXP/CPAK is required) with the 10x10G-LC card to provide OTN multiplexing of the 10 G data streams into a single 100 G DWDM OTU4 wavelength. When the 10x10G-LC card is configured with the 100GS-CK-C card, and 10 Gigabit Ethernet LAN PHY payloads are supported. The allowed slot pairs are 2-3, 4-5, 6-7, 8-9, 10-11, 12-13, or 14-15.

The 10x10G muxponder mode supports client signals that are a combination of any 10 Gigabit Ethernet LAN-PHY or OTU2 data rates.

The 10x10G-LC card works as a standalone card, supporting the multitransponder functionality. The 10 Gbps SFP+ ports should be paired to provide the 10 G transponder functionality for each port of the port pair. 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 six 10x10G-LC cards are supported on the Cisco NCS 2006 chassis allowing for 30 10 Gbps transponders in a single shelf.

All ports can be equipped with or without the G.709 Digital Wrapper function that provides wide flexibility in terms of the supported services.

As the client and trunk ports are completely independent, it is also possible to equip both 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 ports are trunk ports.

It is not a constraint to provision five pairs of TXP-10G mode or five pairs of RGN-10G mode. A mix of TXP-10G and RGN-10G modes can be configured. For example, pairs 1-2 and 5-6 can be configured as TXP-10G mode and the remaining pairs as RGN-10G mode.

The 10x10G-LC card can be configured in low latency mode. This configuration minimizes the time spent by the signal to cross the card during the regeneration process. Athough each SFP port functions as a unidirectional regenerator, adjacent SFP ports must be selected while provisioning this mode. 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 data rates. The same payload must be provisioned on both SFP ports involved in this operating mode. GCC cannot be provisioned on the ports used in low latency mode. The low latency mode does not support terminal and facility loopback.

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

Splitter protection can be implemented on the 10x10G-LC card in TXPP-10G mode. The 10x10G-LC card supports up to two splitter protection groups with one client and two trunk ports. The client and trunk ports on the two groups are:

• Port 3 (client), port 4, and port 6 (trunks) on the first protection group

• Port 7 (client), port 8, and port 10 (trunks) on the second protection group

Port 1 and port 2 are available for unprotected transponders and can be configured in the standard TXP-10G mode, with the first port selected as the trunk and the other port selected as the client. Two ports, port 5 and port 9, are left unused. A Y-Cable protection group cannot be defined on the same 10x10G-LC card when it is provisioned in the TXPP-10G mode. The splitter protection is supported only for 10GE traffic, with trunk ports set to disabled FEC, standard FEC, or enhanced FEC (E-FEC) mode.

The following figure shows the 10x10G-LC card configured for splitter protection.

For more information about the 10x10G-LC card, see http://www.cisco.com/en/US/prod/collateral/optical/ps5724/ps2006/data_sheet_c78-713296.html.

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

The CFP-LC card is a double-slot card and can be installed in Slot 3 or Slot 5 in the Cisco NCS 2006 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 NCS 2002 chassis, the system raises an EQPT::MEA (Mismatch of Equipment Alarm) notification. Up to two CFP-LC cards per Cisco NCS 2006 shelf assembly can be installed, 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 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 NCS 2006 chassis in order to provide two 100 G transponders configurations.

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. Key Features of 100G-LC-C, 100G-CK-C, 100GS-CK-C, 200G-CK-C, 10x10G-LC, CFP-LC, and MR-MXP Cards lists the valid port pair for a specific operating mode and the supported payloads, and describes how each mode can be configured.

The CFP-LC card can be configured as a 2-port 40 G muxponder. It can be connected with the 100G-LC-C or 100G-CK-C card to support 2-port 40 G muxponder capabilities. The 100G-LC-C or 100G-CK-C card can be connected through the Cisco NCS 2006 backplane (no client CXP/CPAK required) with the CFP-LC card to provide OTN multiplexing of the 40 G data streams into a single 100 G WDM OTU4 wavelength. The 2x40G muxponder mode supports client signals that are a mix and combination of any 40 Gigabit Ethernet LAN-PHY or OTU3 data rates.

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

The CFP-LC card can be connected through the Cisco NCS 2006 backplane with up to two 100G-LC cards placed in the upper or lower slot of the same shelf to provide the equivalent functionalities of two 100 G LR4 transponders, leveraging on CFP pluggables as the client interface.

For more information about the CFP-LC card, see http://www.cisco.com/en/US/prod/collateral/optical/ps5724/ps2006/data_sheet_c78-713295.html

The card key features are listed in the Key Features of 100G-LC-C, 100G-CK-C, 100GS-CK-C, 200G-CK-C, 10x10G-LC, CFP-LC, and MR-MXP Cards.

For a detailed list of the supported pluggables, see, http://www.cisco.com/c/en/us/td/docs/optical/spares/gbic/guides/b_ncs_pluggables.html

The MR-MXP card supports the following 200G operating modes:

• MXP-200G

• MXP-10x10G-100G

• MXP-CK-100G

Each operating mode can be configured using specific set of cards and client payloads. The operating mode is configured on the companion trunk card (100GS-CK-C or 200G-CK-C). For more information about these operating modes, see Key Features of 100G-LC-C, 100G-CK-C, 100GS-CK-C, 200G-CK-C, 10x10G-LC, CFP-LC, and MR-MXP Cards.

The MR-MXP card supports the following 100G operating modes:

• MXP-100G

• TXP-100G

• 100G-B2B

Note	All 100G and 200G operating modes support the encryption feature except for the MXP-CK-100G mode.

The MXP-100G operating mode is provisioned with MR-MXP card on the client side and the adjacent 200G-CK-C card or 100GS-CK-C card on the trunk side. The operating mode can be provisioned only from the client side but can be deleted from both client and trunk sides. This mode supports 10GE as the payload. This mode uses the SFP+ and QSFP+ ports on MR-MXP client card and the DWDM port on the 200G-CK-C card or 100GS-CK-C card. The aggregate signal from the client is sent to trunk through the backplane.

The MXP-100G operating mode is also provisioned with MR-MXP card on the client side and the adjacent 200G-CK-C card on the trunk side. The operating mode can be provisioned only from the client side but can be deleted from both client and trunk sides. This mode supports 2X10GE+2X40GE as the payload. This mode uses the SFP+ and QSFP+ ports on MR-MXP client card and the DWDM port on the 200G-CK-C card. The aggregate signal from the client is sent to trunk through the backplane.

The operating mode can be provisioned on the following slots:

• NCS 2006: Slots 2 and 3, 4 and 5, 6 and 7

• NCS 2015: Slots 2 and 3, 4 and 5, 6 and 7, 8 and 9, 10 and 11, 12 and 13, 14 and 15

TXP-100G operating mode is provisioned with MR-MXP card on the client side and the adjacent 200G-CK-C card or 100GS-CK-C card on the trunk side. The operating mode can be provisioned only from the client side but can be deleted from both client and trunk sides. This mode supports 100GE as the payload. This mode uses the CPAK port on MR-MXP client card and the DWDM port on the 200G-CK-C card or 100GS-CK-C card. The aggregate signal from client is sent to trunk through the backplane.

The operating mode can be provisioned on the following slots:

• NCS 2006: Slots 2 and 3, 4 and 5, 6 and 7

• NCS 2015: Slots 2 and 3, 4 and 5, 6 and 7, 8 and 9, 10 and 11, 12 and 13, 14 and 15

The 100G-B2B operating mode can be provisioned with MR-MXP card on the client side and the adjacent MR-MXP card card on the trunk side. The operating mode performs encryption of an 100GE client signal taken from the CPAK interface or 10x10GE client signal taken from the two QSFP and SFP interfaces of the client MR-MXP card and maps it to an OTU4 signal with encryption. The OTU4 signal is passed to the trunk MR-MXP card in the peer slot through the back plane. The trunk MR-MXP card converts the OTU4 signal to grey wavelength with either an SR-10 or an LR-4 through the CPAK interface of the trunk card. The 100GE client payload can be divided into either four or 10 sub-lanes.

The CPAK port or two QSFP and 2 SFP+ ports can be selected on the client card during the provisioning. The operating mode can be provisioned from any MR-MXP card in the peer slot pair. When the operating mode is created, the card that the user selects to create operating mode acts as the client card and the peer card for that card acts as the trunk card.

The operating mode can be provisioned on the following slots:

• NCS 2006: Slots 2 and 3, 4 and 5, 6 and 7

• NCS 2015: Slots 2 and 3, 4 and 5, 6 and 7, 8 and 9, 10 and 11, 12 and 13, 14 and 15

The provisioning operations like payload/operating mode creation and FEC settings in 100G-B2B operating mode of MR-MXP card takes longer when compared to other operating modes.

Sub Operating Modes

The sub OpMode in MR-MXP cards determines the operating mode on the card client ports. For example, the QSFP+ port can be provisioned either as a 40GE port or can be divided into four 10G ports. This provisioning is controlled by the sub OpMode. The sub OpMode is created by default when the operating mode is configured on the card.

• OPM_10x10G—This is the default sub OpMode for the MXP-100G, MXP-200G, and MXP-10x10G-100G operating modes. In this sub OpMode, the SFP and QSFP+ ports are divided in such a way that 10 10GE payloads can be provisioned. When a PPM is provisioned on a QSFP+ port, four internal ports are created. A 10 GE payload can be provisioned on each of these ports. The OPM-10x10G operating mode is provisioned with MR-MXP card on the client side and the adjacent MR-MXP card on the trunk side. The operating mode can be provisioned only from the client side but can be deleted from both client and trunk sides. The aggregate signal from client is sent to trunk through the backplane.

• OPM_100G—This is the default sub OpMode for the MXP-CK-100G operating mode where the CPAK port can be provisioned with a 100GE or OTU4 payload. The 100GE payload can be divided into either four or ten sub-lanes. For 100GE payload, the OPM-100G operating mode is provisioned with MR-MXP card on the client side and the adjacent MR-MXP card on the trunk side. For OTU4 payload, the OPM-100G operating mode is provisioned with MR-MXP card on the client side and the adjacent 200G-CK-C card on the trunk side.The operating mode can be provisioned only from the client side but can be deleted from both client and trunk sides. The aggregate signal from client is sent to trunk through the backplane.

• OPM_2x40G_2x10G—This sub OpMode is provisioned for the MXP-100G operating mode to support the 2X10GE+2X40GE payload. This operating mode is provisioned with MR-MXP card on the client side and the adjacent 200G-CK-C card on the trunk side. The operating mode can be provisioned only from the client side but can be deleted from both client and trunk sides. The aggregate signal from client is sent to trunk through the backplane.

  This sub OpMode is also provisioned for the MXP-200G operating mode to support the following sub OpMode combinations on both peer and skip MR-MXP cards.

  • OPM_10x10G and OPM_10x10G

  • OPM_2x40G_2x10G and OPM_2x40G_2x10G

  • OPM_2x40G_2x10G and OPM_10x10G

  • OPM_10x10G and OPM_2x40G_2x10G

The 400G-XP card supports the following key feature:

• • Operating Modes—The card can be configured in various operating modes. The cards can be equipped with pluggables for client and trunk ports, and offer a large variety of configurations. When you configure the card, make sure that the following tasks are completed:

    • The trunk port PPMs must be preprovisioned before configuring the card operating mode. When the 400G-XP card is paired with the 10x10G-LC card, all the operating mode provisioning must performed on the 400G-XP card. The client payloads can be provisioned after configuring the operational mode on the card.

    The table below details the configurations supported on the 400G-XP card for the supported card modes.

    Table 6. Configuration Options for the 400G-XP Card Modes

    Configuration	Options
    Card configuration	MXP	OTNXC 1	REGEN	MXP_2x150G (8QAM)
    Trunk configuration ( per trunk)	None	None	None	M_150G
    	M_100G	M_100G	M_100G
    	M_200G	M_200G	M_200G
    Slice configuration	None	None	Slice configuration is not supported	None
    	OPM_2x40G_2x10G	OPM_100G		OPM_100G
    	OPM_100G	OPM_10x10G		OPM_10x10G
    	OPM_10x10G			OPM_6x16G_FC
    	OPM_6x16G_FC
    	OPM_PEER_ODU2 (Available only for Slice 2 when 400G-XP is paired with 10x10G-LC)
    	OPM_PEER_ODU2e (Available only for Slice 2 when 400G-XP is paired with 10x10G-LC)

    ¹ Not supported in R12.0

    For more information about the trunk and slice configuration, see Slice Definition and Line Card Configuration for 400G-XP Card.

• Each trunk port functions as a muxponder instance has the following features:

  • The trunk port supports Analog Coherent Optical (ACO) CFP2 coherent pluggable.

    Note	Before removing the CFP2 pluggable from any of two trunk ports, ensure that the relevant trunk port is set to the OOS (Out-of-service) state. Wait until the trunk port LED turns off. Wait for a further 120 seconds before extracting the CFP2 pluggable.

  • Configurable trunk capacity:

    • 100 Gbps coherent DWDM transmission with quadrature phase shift keying (QPSK )modulation.

    • 200 Gbps coherent DWDM transmission with 16-state quadrature amplitude modulation (16-QAM) modulation.

  • Configurable trunk FEC: SD-FEC with 15% or 25% overhead.

  • Configurable differential/non-differential line encoding.

  • Nyquist shaping if channels at trunk TX.

  • Flex spectrum tunability over the full extended C-Band.

  • 100 Gbps through 100 Gbps QSFP28 client ports.

  • 10 Gbps through 4x 10 Gbps QSFP+ client ports.

  • 16 Gbps through 4 x 16 Gbps QSFP+ client ports.

• The supported CD ranges are detailed in the table below:

  Table 7. CD Range for 400G-XP Card

  	200G 16-QAM		100G QPSK
  	Low	High	Low	High
  Default Working CD Range	-10000	50000	-20000	90000
  Default CD Thresholds	-9000	45000	-18000	72000
  Allowed CD Range ( Working and Thresholds)	-60000	60000	-280000	280000

• Loopback—The following loopback types are supported:

  • Client ports - Terminal (Inward), Facility (Line)

  • Trunk ports - Terminal (Inward)

  • Iports - Facility (Line), Terminal loopback (Drop)

    Note	Before you provision loopback on the iports, place the relevant trunk ports in the OOS-MT state. This causes the iports to move to the OOS-MT state.

• Automatic Laser Shutdown (ALS) can be configured on all the ports.

• 100GE ethernet client ports can be provisioned with or without IEEE 802.3 bj FEC. The options are Auto, Force-Fec-On, Force-Fec-Off.

• Trail Trace Identifier (TTI)—TTI in the section monitoring overhead is supported . Source Access Point Identifer (SAPI), Destination Access Point Identifer (DAPI), and User Operator Data fields are supported in Release 10.6.2 and later releases.

• Trunk Port Interworking—The two CFP2 trunk ports can interoperate with each other when the source and destination 400G-XP cards have the same trunk mode and slice mode configuration. For more information, see Trunk Port Interworking in 400G-XP Cards.

• GCC0 Support—The 400G-XP card supports provision of GCC0 channel on the trunk port. For more information, see GCC0 Support on the 400G-XP Card.

• Interoperability—The 400G-XP card is interoperable with the NC55-6X200-DWDM-S card supported on NCS 5500 and the NCS4K-4H-OPW-QC2 Card supported on NCS 4000.

  The following table describes the configurations, payload types, and pluggables supported for interoperability between the 400G-XP card and the NCS4K-4H-OPW-QC2 card.

  Table 8. 400G-XP Interoperability with the NCS4K-4H-OPW-QC2 card.

  Payload type	Trunk configuration	Pluggables for trunk ports on 400G-XP	Pluggables for client ports on 400G-XP	Pluggables for trunk ports on 4H-OPW-QC2	Pluggables for client ports on 4H-OPW-QC2
  100GE	OTU4	CFP2	QSFP-100G-SR4-S	CFP2	QSFP-100G-SR4-S
  100GE	OTU4C2	CFP2	QSFP-100G-SR4-S	CFP2	QSFP-100G-SR4-S
  OTU2	OTU4	CFP2	ONS-QSFP-4X10 MLR	CFP2	ONS-QSFP28-LR4
  OTU2	OTU4C2	CFP2	ONS-QSFP-4X10 MLR	CFP2	ONS-QSFP28-LR4
  10GE	OTU4	CFP2	ONS-QSFP-4X10 MLR	CFP2	ONS-QSFP-4X10 MLR
  10GE	OTU4C2	CFP2	ONS-QSFP-4X10 MLR	CFP2	ONS-QSFP-4X10 MLR

  The following table describes the configurations, payload types, and pluggables supported for interoperability between the 400G-XP card and the NC55-6X200-DWDM-S card.

  Table 9. 400G-XP Interoperability with the NC55-6X200-DWDM-S card.

  Payload type	Trunk configuration	Pluggables for trunk ports on 400G-XP	Pluggables for client ports on 400G-XP	Pluggables for trunk ports on 6X200-DWDM-S	Pluggables for client ports on 6X200-DWDM-S
  100GE	OTU4	CFP2	QSFP-100G-SR4-S	CFP2	QSFP-100G-SR4-S
  100GE	OTU4C2	CFP2	QSFP-100G-SR4-S	CFP2	QSFP-100G-SR4-S

For a detailed list of the supported pluggables, see http://www.cisco.com/c/en/us/td/docs/optical/spares/gbic/guides/b_ncs_pluggables.html .

The image below displays the client and trunk ports of the 400G-XP card.

The trunk ports can be configured with either 100G or 200G rates. The client ports are grouped into four slices. The slice mode defines the aggregation capacity and can be configured independently.

The configuration of each of the two trunk ports is independent of the configuration of the other and is done using either one of the two trunk operating modes.

Trunk Operating Modes (trunk capacity)

• M-100G: 100G QPSK. One slice is enabled on the trunk. Slice 2 is enabled for Trunk 1 and Slice 4 is enabled on Trunk 2.

• M-200G: 200G 16 QAM. Two slices are enabled on the trunk.

• provision a ONS-QC-16GFC-SW= pluggable on the shared ports and have 6x 16G-FC payloads and 8x 10G payloads (10GE or OTU2)

• provision a QSFP-4X10G-MLR (or ONS-QSFP-4X10G-LR-S) pluggable on the shared ports and have 4x 16G-FC + 10x 10G payloads (10GE and/or OTU2)

Traffic from the client ports are aggregated on the 100G or 200G trunk at the intermediate ports. There are four intermediate ports (iports), two per trunk. The iports are automatically configured when the slices are configured.

The relation between the two trunk ports (Ports 11 and 12), client ports (Ports 1 through 10) and the four slices are represented in the tables below.

The OPM-6x16G_FC mode is referred to as 6x16G_FC and OPM_2x40G_2x10G mode is referred to as 2x40G_2x10G in this table.

The OPM-6x16G_FC mode is referred to as 6x16G_FC and OPM_2x40G_2x10G mode is referred to as 2x40G_2x10G in this table.