Configuration Guide for Cisco NCS 1014, IOS XR Releases 26.x.x

PDF

Configuration Guide for Cisco NCS 1014, IOS XR Releases 26.x.x

2-QDD-C line cards

Updated: June 18, 2026

Want to summarize with AI?

Log in

This section explains the features, supported configurations, and key capabilities of the 2-QDD-C line cards used with NCS 1014.

Table 1. Feature History
Feature Release Information Description
NCS1K4-2-QDD-C-K9 C-Band Line Card Cisco IOS XR Release 25.2.1

NCS 1014 now supports the NCS1K4-2-QDD-C-K9 C-Band line card. This card features eight client ports (QSFP28 and QSFP-DD) and two software-configurable DWDM dual sub-channel module trunk ports. Each trunk port supports line rates of 200, 300, and 400 Gbps with precise control over modulation format, baud rate, and forward error correction.

Additionally, the line card supports both module and slice configurations, enhancing network flexibility and performance.

This section describes the supported configurations and procedures to configure the card modes on the 2-QDD-C line card.

Limitations for 2-QDD-C

  • Flex Ethernet is not supported.

  • A single 400GE cannot be split and use as 4x 100GE due to hardware limitations.

2-QDD-C card modes

A 2-QDD-C card mode is an operational configuration for 2-QDD-C line cards that support module and slice configurations.

The line cards have two trunk ports (0 and 1) and 8 client ports (2 through 9) each. You can configure the line card in two modes:

  • Muxponder mode: Both trunk ports are configured with the same trunk rate. The client-to-trunk mapping is in a sequence in vertical order.

  • Muxponder slice mode: Each trunk port is configured independently of the other with different trunk rates. The client-to-trunk mapping is fixed in vertical order. For Trunk 0, the client ports are 2 through 5. For Trunk 1, the client ports are 6 through 9.

Sub 50G configuration

You can configure sub 50G muxponder mode in these combination of trunk and client rates:

  • 100GE Muxponder mode:

    • 1x100GE and 2x50G

    • 3x100GE and 2x150G

    • 5x100GE and 2x250G

    • 7x100GE and 2x350G

  • OTU4 Muxponder mode:

    • 1xOTU4 and 2x50G

    • 3xOTU4 and 2x150G

    • 5xOTU4 and 2x250G

    • 7xOTU4 and 2x350G

This table displays the port configuration for the supported data rates.

Trunk data rate (per trunk)

Total configured data rate

Trunk ports

Client ports for trunk 0 (100G)

Shared client port (50G per trunk)

Client ports for trunk 1 (100G)

50G

100G

0, 1

-

2

-

150G

300G

0, 1

2

3

4

250G

500G

0, 1

2, 3

4

5, 6

350G

700G

0, 1

2, 3, 4

5

6, 7, 8

From Release 7.5.2, 2-QDD-C cards support an alternate port configuration for Sub 50G (split client port mapping) that you configure using CLI. The following table displays the port configuration for the supported data rates.

Trunk data rate (per trunk)

Total configured data rate

Trunk ports

Client ports for trunk 0 (100G)

Shared client port (50G per trunk)

Client ports for trunk 1 (100G)

50G

100G

0, 1

-

5

-

150G

300G

0, 1

2

5

6

250G

500G

0, 1

2, 3

5

6, 7

350G

700G

0, 1

2, 3, 4

5

6, 7, 8

For information on how to configure split client port mapping, see Configure Split Client Port Mapping .

Coupled mode restrictions

These restrictions apply to the coupled mode configuration:

  • Both trunk ports must be configured with the same bits-per-symbol or baud rate and must be sent over same fiber and direction.

  • The chromatic dispersion must be configured to the same value for both trunk ports.

  • When trunk internal loopback is configured, it must be done for both trunk ports. Configuring internal loopback on only one trunk results in traffic loss.

  • Fault on a trunk port of a coupled pair may cause errors on all clients including those running only on the unaffected trunk port.

Supported data rates for 2-QDD-C card

These tables display the supported data rates for the 2-QDD-C card.

This table displays the client and trunk ports that are enabled for the muxponder configuration.

Trunk data rate

Card support

Client data rate

Client optics

Trunk ports

Client ports

200

2-QDD-C

100GE, OTU4

QSFP-28

0, 1

2, 3, 4, 5

300

2-QDD-C

100GE, OTU4

QSFP-28

0, 1

2, 3, 4, 5, 6, 7

400

2-QDD-C

100GE, OTU4

QSFP-28

0, 1

2, 3, 4, 5, 6, 7, 8, 9

200

2-QDD-C

400GE

 QSFP-DD

0, 1

4

400

2-QDD-C

400GE

QSFP-DD

0, 1

4,8

This table displays the client and trunk ports that are enabled for the muxponder slice 0 configuration.

Trunk data rate

Card support

Client data rate

Trunk ports

Client ports

200

2-QDD-C

100GE, OTU4

0

2, 3

300

2-QDD-C

100GE, OTU4

0

2, 3, 4

400

2-QDD-C

100GE, OTU4

0

2, 3, 4, 5

400

2-QDD-C

400GE

0

4

This table displays the client and trunk ports that are enabled for the muxponder slice 1 configuration.

Trunk data rate

Card support

Client data rate

Trunk ports

Client ports

200

2-QDD-C

100GE, OTU4

1

6, 7

300

2-QDD-C

100GE, OTU4

1

6, 7, 8

400

2-QDD-C

100GE, OTU4

1

6, 7, 8, 9

400

2-QDD-C

400GE

1

8

This table displays the trunk parameter ranges for the 2-QDD-C card.

Trunk payload

FEC

Min BPS

Max BPS

Min GBd

Max GBd

150G

27%

1.453125

4.335938

24.02079

71.67494

200G

27%

2

4.40625

31.51

69.43

250G

27%

2.414063

6

28.93129

71.9069

300G

27%

2.8984375

6

34.7175497

71.8681352

350G

27%

3.382813

6

40.5038

71.84047

400G

27%

3.8671875

6

46.2900663

71.8197392

150G

15%

1.320313

3.9375

24.02079

71.67494

200G

15%

1.7578125

5.25

24.02079115

71.74209625

250G

15%

2.195313

6

26.27274

71.80592

300G

15%

3.8203125

6

31.52728839

49.51525048

350G

15%

3.070313

6

36.78184

71.87901

400G

15%

3.8671875

6

42.03638452

71.9018782
Note

The recommended value for 6 BPS for corresponding line rates are listed below:

Trunk payload

FEC

BPS

GBd

300G

27%

6

34.7175

350G

27%

6

40.5038

400G

15%

6

42.0364

Configure the card mode for 2-QDD-C card

Use this task to configure a 2-QDD-C line card in either muxponder mode or muxponder slice mode. This configuration defines the client rate and the trunk rate for the line card.

Procedure

1.

Run these commands to configure the 2-QDD-C card in muxponder mode. Set the client rate and the trunk rate as specified.

  • hw-module location location mxponder client-rate {100GE | OTU4 }

  • hw-module location location mxponder trunk-rate {100G | 150G | 200G | 250G | 300G | 350G | 400G }

  • hw-module location location mxponder client-rate { 400GE}

  • hw-module location location mxponder trunk-rate { 200G | 400G }

Example:

This is a sample in which the card is configured in the muxponder mode with a 400G trunk rate. 


RP/0/RP0/CPU0:ios#config
Tue Oct 15 01:24:56.355 UTC
RP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder client-rate 100GE
RP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder trunk-rate 400G
RP/0/RP0/CPU0:ios(config)#commit

This is a sample in which the card is configured in the muxponder mode with a 400GE trunk rate.

RP/0/RP0/CPU0:west#configure   
Thu Oct  7 11:43:01.914 IST
RP/0/RP0/CPU0:west(config)#hw-module location 0/2 mxponder trunk-rate 4
400G  450G  
RP/0/RP0/CPU0:west(config)#hw-module location 0/2 mxponder trunk-rate 400G    
RP/0/RP0/CPU0:west(config)#hw-module location 0/2 mxponder client-rate 400GE 
RP/0/RP0/CPU0:west(config)#commit
2.

Run these commands to configure the 2-QDD-C card in muxponder slice mode. Set the slice number, client rate, and trunk rate as required.

  • hw-module location location mxponder-slice mxponder-slice-number client-rate { 100GE | 400GE}

  • hw-module location location mxponder-slice mxponder-slice-number trunk-rate { 100G | 200G | 300G | 400G}

Example:

This is a sample in which the card is configured in the muxponder slice 0 mode with a 400G trunk rate.


RP/0/RP0/CPU0:ios#config
RP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder-slice 0 client-rate 100GE
RP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder-slice 0 trunk-rate 400G
RP/0/RP0/CPU0:ios(config)#commit

This is a sample in which the card is configured in the muxponder slice 1 mode with a 400G trunk rate.


RP/0/RP0/CPU0:ios#config
RP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder-slice 1 client-rate 100GE
RP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder-slice 1 trunk-rate 400G
RP/0/RP0/CPU0:ios(config)#commit

The 2-QDD-C card is configured in the specified muxponder or muxponder slice mode with the defined client and trunk rates.

Configure mixed client traffic mode

Use this task to configure the client traffic mode on each trunk in a line card independently. This provides flexibility for the same card to carry both OTN and Ethernet client traffic at the same time across two slices.

100G, 200G, and 300G trunk rates are supported on both slices (slice 0 and slice 1) with different client modes, including 100GE and OTU4.

From Release 7.10.1, you can configure both Ethernet and OTU interfaces on different client ports for each trunk in the 2-QDD-C line card. This enhancement allows the same line card to carry both OTN and Ethernet client traffic at the same time in a single slice for each trunk rate.

An additional 400G trunk rate is supported on both slices (slice 0 and slice 1) with different client modes, such as 100GE and OTU4.

Procedure

1.

Run these commands to configure the card for mixed client traffic mode with different slices (slice 0 and slice 1).

  • hw-module locationlocationmxponder-slicemxponder-slice-number trunk-rate {100G | 200G | 300G | 400G| }

  • hw-module locationlocationmxponder-slicemxponder-slice-number client-rate { | OTU4 | 100GE}

Example:

This is a sample in which the card is configured with mixed client rates in the muxponder slice 0 and 1 mode.


RP/0/RP0/CPU0:ios#configure
Mon Mar 23 06:10:22.227 UTC
RP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder-slice 0 client-rate OTU4 trunk-rate 400G 
RP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder-slice 1 client-rate 100GE trunk-rate 400G
RP/0/RP0/CPU0:ios(config)#commit

This is a sample configuration of the mixed client traffic mode in different slices.

hw-module location 0/0
 mxponder-slice 0
  trunk-rate 400G
  client-rate OTU4
 !
 mxponder-slice 1
  trunk-rate 400G
  client-rate 100GE
 !
!

This is a sample configuration in which both the slices use the same client mode.

hw-module location 0/3
 mxponder
  trunk-rate 350G
  client-rate 100GE
 !
!
2.

Run the show hw-module location mxponder command to verify the card configuration.

Example:

This is a sample to verify the mixed client traffic mode in different slices.

Location:             0/0
Slice ID:             0
Client Bitrate:       OTU4
Trunk  Bitrate:       400G
Status:               Provisioned
Client Port                     Peer/Trunk Port            CoherentDSP0/0/0/0   
                                Traffic Split Percentage

OTU40/0/0/2                     ODU40/0/0/0/1                      100
OTU40/0/0/3                     ODU40/0/0/0/2                      100
OTU40/0/0/4                     ODU40/0/0/0/3                      100
OTU40/0/0/5                     ODU40/0/0/0/4                      100


Location:             0/0
Slice ID:             1
Client Bitrate:       100GE
Trunk  Bitrate:       400G
Status:               Provisioned
Client Port                     Peer/Trunk Port            CoherentDSP0/0/0/1   
                                Traffic Split Percentage
HundredGigECtrlr0/0/0/6         ODU40/0/0/1/1                         100
HundredGigECtrlr0/0/0/7         ODU40/0/0/1/2                         100
HundredGigECtrlr0/0/0/8         ODU40/0/0/1/3                         100
HundredGigECtrlr0/0/0/9         ODU40/0/0/1/4                         100

This is a sample to verify both the slices using the same client mode.


RP/0/RP0/CPU0:ios#show hw-module location 0/3 mxponder
Fri Nov 26 12:21:16.174 UTC

Location:             0/3
Client Bitrate:       100GE
Trunk  Bitrate:       350G
Status:               Provisioned
LLDP Drop Enabled:    FALSE
ARP Snoop Enabled:    FALSE
Client Port                     Mapper/Trunk Port          CoherentDSP0/3/0/0   CoherentDSP0/3/0/1      
                                Traffic Split Percentage

HundredGigECtrlr0/3/0/2         ODU40/3/0/0/1                         100                        0
HundredGigECtrlr0/3/0/3         ODU40/3/0/0/2                         100                        0
HundredGigECtrlr0/3/0/4         ODU40/3/0/0/3                         100                        0
HundredGigECtrlr0/3/0/5         ODU40/3/0/0/4                          50                       50
HundredGigECtrlr0/3/0/6         ODU40/3/0/1/1                           0                      100
HundredGigECtrlr0/3/0/7         ODU40/3/0/1/2                           0                      100
HundredGigECtrlr0/3/0/8         ODU40/3/0/1/3                           0                      100
3.

Run this command to configure the card for mixed client traffic mode in the same slice.

  • hw-module location location mxponder-slice mxponder-slice-number trunk-rate {100G | 200G | 300G | 400G|}

Example:

This is a sample in which the card is configured with mixed client rates in the muxponder slice 0 mode.


RP/0/RP0/CPU0:ios#configure
Mon Mar 23 06:10:22.227 UTC
RP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder-slice 0 client-port-rate 2 client-type OTU4 trunk-rate 400G 
RP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder-slice 0 client-port-rate 3 client-type 100GE trunk-rate 400G
RP/0/RP0/CPU0:ios(config)#commit

This is a sample configuration of the mixed client port rate in same slice.


hw-module location 0/0
 mxponder-slice 0
  trunk-rate 200G
  client-port-rate 2 client-type 100G
  client-port-rate 3 client-type otu4
 !
 mxponder-slice 1
  trunk-rate 400G
  client-port-rate 4 client-type 100G
  client-port-rate 8 client-type otu4
 !
!