Configuration Guide for Cisco NCS 1004, IOS XR Release 25.x.x

PDF

Configuration Guide for Cisco NCS 1004, IOS XR Release 25.x.x

Muxponder configurations

Updated: July 31, 2026

Want to summarize with AI?

Log in

This section explains the muxponder configurations available on the OTN-XP card, including the LC mode, client port rate, client-to-trunk port mapping, and trunk rate for each supported configuration.

A muxponder configuration is a hardware module operating mode for the OTN-XP card that

  • maps multiple client port signals onto one or two trunk ports through mxponder-slice 0 and mxponder-slice 1,

  • supports independent slice configurations with different client rates per slice, and

  • uses CFP2 DCO trunk ports (ports 12 and 13) or QDD ZRP trunk ports (ports 9 and 11) depending on the LC mode.

The OTN-XP card has two trunk ports and 12 client ports. The muxponder configuration supports two slices, 0 and 1. You can configure mxponder-slice 0, mxponder-slice 1, or both. Each mxponder-slice supports 10 client interfaces.

From Release 7.3.1, the OTN-XP card supports two trunk ports for CFP2 DCO on port 12 and port 13, and 8 client ports.

From Release 7.3.2, the OTN-XP card supports two trunk ports for QDD ZRP on port 9 and port 11, and 8 client ports.

From Release 7.5.1, the OTN-XP card supports two trunk ports for QDD ZRP on port 9 and port 11, and the supported operating modes are 400G-TXP-DD, 3X100GE MXP, and 2X100GE MXP. The client rates 2x100GE and 3x100G are supported as part of the 4x100GE-MXP-DD mode.

Table 1. Feature History

Feature Name

Release Information

Description

400 TXP or MXP modes with CFP2 DCO for OTN-XP Card

Cisco IOS XR Release 7.3.1

On the OTN-XP card, you can configure a single 400GE or 4x100G payload that is received over the client port as a 400G signal over DWDM on the line side.

The card improves efficiency, performance, and flexibility for customer networks allowing 400GE or 4x100G client transport over 400G WDM wavelength.

Commands modified:

  • controller coherentDSP

  • show controller coherentDSP

OC192 and STM64 clients on OTN-XP card

Cisco IOS XR Release 7.10.1

40x10G-4x100G-MXP card mode on the OTN-XP card now supports OC192/STM64 clients in the 40x10G mode. This allows you to use the OTN-XP card to handle OC192 SONET and STM64 SDH payloads.
Table 2. Hardware module configuration with client to trunk mapping

Hardware module configuration

Line card mode

Client port rate

Client to trunk mapping

Trunk rate

10G Grey Muxponder

10G-GREY-MXP

OTU2, OTU2e, or 10 GE

Mxponder-slice 0—Client ports 4, 5, and 2 are mapped to the trunk port 0.

Mxponder-slice 1—Client ports 7, 6, and 11 are mapped to the trunk port 1.

Each client port consists of four lanes, 1, 2, 3, and 4. The lanes 3 and 4 can only be configured for ports 2 and 11. It is not mandatory to configure all 10 client lanes for a slice.

100G

400G-MXP

4x100G-MXP -400G-TXP

100GE, OTU4

Mxponder-slice 0—Client ports 1, 6, 7, and 10 are mapped to the trunk port 12.

Mxponder-slice 1—Client ports 0, 4, 5, and 8 are mapped to the trunk port 13.

400G

400G-TXP

4x100G-MXP -400G-TXP

400GE

Mxponder-slice 0—Client port 10 is mapped to the trunk port 12.

Mxponder-slice 1—Client port 8 is mapped to the trunk port 13.

400G

40x10G

40x10G-4x100G-MXP

STM64, OC192, OTU2, OTU2e, or 10 GE

Mxponder-slice 0—10G Client ports 0, 1, 2, 3, 4, 5, 6, 7, 9, and 11 mapped to the trunk port 12.

Each client port consists of four lanes, 1, 2, 3, and 4.

400G CFP2

30x10G

40x10G-4x100G-MXP

OTU2, OTU2e, or 10 GE

Mxponder-slice 0—10G Client ports 0, 1, 2, 3, 4, 5, 9, and 11 are mapped to the trunk port 12.

The client ports 0, 1, 2, 3, 4, 5, and 9 are configured for all four lanes, 1, 2, 3, and 4.

The client port 11 is configured for lanes 1 and 2.

300G CFP2

20x10G + 2x100G

40x10G-4x100G-MXP

10 GE, 100 GE, OTU2, OTU2e, or OTU4

Mxponder-slice 0—The following 100G and 10G client ports are mapped to trunk port 12.

  • 100G client port—0 and 1

  • 10G client port—4, 5, 6, and 7 are configured for all four lanes, 1, 2, 3, and 4.

  • 10G client port—11 and 2 are configured for lanes 3 and 4.

400G CFP2

10x10G + 3 x 100G

40x10G-4x100G-MXP

10GE, 100GE, OTU4, OTU2, or OTU2e

Mxponder-slice 0—The following 100G and 10G client ports are mapped to a trunk port 12.

  • 100G client port—0, 1, and 6

  • 10G client port—4 and 5 are configured for all four lanes, 1, 2, 3, and 4.

  • 10G client port—2 are configured for lanes 3 and 4.

400G CFP2

20x10G + 1 x 100G

40x10G-4x100G-MXP

10 GE, 100 GE, OTU2, OTU2e, or OTU4

Mxponder-slice 0—The following 100G and 10G client ports are mapped to trunk port 12.

  • 100G client port—0

  • 10G client port—1, 4,5 and 9 are configured for all four lanes, 1, 2, 3, and 4.

  • 10G client port—2 is configured for lanes 3 and 4 and 11 is configured for lanes 1 and 2.

300G CFP2

30x10G + 1 x 100G

40x10G-4x100G-MXP

10 GE, 100 GE, OTU2, OTU2e, or OTU4

Mxponder-slice 0—The following 100G and 10G client ports are mapped to trunk port 12.

  • 100G client port—6

  • 10G client port—0, 1, 2, 3, 4, 5, and 9 are configured for all four lanes, 1, 2, 3, and 4.

  • 10G client port—11 is configured for lanes 1 and 2.

400G CFP2

10x10G + 2 x 100G

40x10G-4x100G-MXP

10 GE, 100 GE, OTU2, OTU2e, or OTU4

Mxponder-slice 0—The following 100G and 10G client ports are mapped to trunk port 12.

  • 100G client port—0 and 1

  • 10G client port—4, and 5 are configured for all four lanes, 1, 2, 3, and 4.

  • 10G client port—2 is configured for lanes 3 and 4.

300G CFP2

10x10G + 1 x 100G

40x10G-4x100G-MXP

10 GE and 100 GE

Mxponder-slice 0—The following 100G and 10G client ports are mapped to trunk port 12.

  • 100G client port—0

  • 10G client port—4, and 5 are configured for all four lanes, 1, 2, 3, and 4.

  • 10G client port—2 is configured for lanes 3 and 4.

  • Mxponder-slice 1—The following 100G and 10G client ports are mapped to trunk port 13.

    • 100G client port—1

    • 10G client port—6, and 7 are configured for all four lanes, 1, 2, 3, and 4.

    • 10G client port—11 is configured for lanes 3 and 4.

200G CFP2

200G Muxponder

200G-FOIC2-oFEC-QPSK-1-S

200G-FOIC2-oFEC-8QAM-1-E

OTU4, 100GE

Mxponder-slice 0—Client ports 7 and 10 mapped to the trunk port 12.

Mxponder-slice1—Client ports 5 and 8 mapped to the trunk port 13.

200G CFP2

QDD ZRP

4x100GE-MXP-DD

100GE

Mxponder-slice 0—Client ports 1, 6, 7, and 10 are mapped to the trunk port 11.

Mxponder-slice 1—Client ports 0, 4, 5, and 8 are mapped to the trunk port 9.

400G

QDD ZRP

400GE-TXP-DD

400GE

Mxponder-slice 0—Client port 10 is mapped to the trunk port 11.

Mxponder-slice 1—Client port 8 is mapped to the trunk port 9.

400G

4x100GE-MXP-DD

100GE

Mxponder-slice 0—Client ports 1, 7, and 10 are mapped to the trunk port 11.

Mxponder-slice 1—Client ports 4, 5, and 8 are mapped to the trunk port 9.

300G

4x100GE-MXP-DD

100GE

Mxponder-slice 0—Client ports 7, and 10 are mapped to the trunk port 11.

Mxponder-slice 1—Client ports 4 and 5 are mapped to the trunk port 9.

200G
Note

OC192 and STM64 are supported only on Cisco 4x10G QSFP+ MLR Pluggable Optics Module as the client pluggable.

QDD ZRP limitations

  • Hold of timer and Idle insertion are not supported on 400GE Client for 400G-TXP mode.

  • Local Fault and Remote Fault ethernet alarms are not supported on 400GE Client for 400G-TXP mode.

  • Far-end PM counters on Coherent DSP controllers are not supported for 400G-TXP and 4x100G MXP modes.

  • QDD ZRP alarms appear with Flexo label due to absence of a separate ZRP layer.

Limitations for STM64 and OC192 in 40x10G-4x100G-MXP mode

  • OC192 and STM64 are available only in 400G trunk mode and only slice 0 is supported.

  • Data communication channel for STM64 and OC192 is available only in path monitoring mode.

  • PRBS, AINS, and SNMP are not supported for OC192 and STM64.

  • The OC192 and STM64 controllers do not support the controller description command.

  • Current and History PM counters do not support flex and 30 second bucket types.

  • OOF alarm (out-of-frame) is not supported.

Configure the muxponder mode for 10G grey muxponder

Set up an OTN-XP card in 10G grey muxponder mode to combine multiple 10G client signals into a single 100G trunk.

Before you begin

Ensure the LC mode is configured to 10G-GREY-MXP on the OTN-XP card before performing this configuration. For details, see Configure the LC mode.

Follow these steps to configure muxponder mode for a 10G grey muxponder:

Procedure

1.

Run the configure hw-module location location mxponder-slice mxponder-slice-number trunk-rate 100G client-port-rate client-port-number lane lane-number client-type { 10GE | OTU2 | OTU2e} command to the OTN-XP card in the muxponder mode.

Example:

This is a sample in which the OTN-XP card is configured with mixed client rates in the mxponder-slice 0 mode.


RP/0/RP0/CPU0:ios#config
Tue Apr 21 09:21:44.460 UTC
RP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder-slice 0
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#trunk-rate 100G
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 2 lane 3 client-type OTU2
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 2 lane 4 client-type OTU2
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#commit
2.

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

Example:

This is a sample to verify the muxponder configuration in the OTN-XP card.


RP/0/RP0/CPU0:ios#show hw-module location 0/1 mxponder
Tue Apr 21 09:26:12.308 UTC

Location:             0/1
Slice ID:             0
Client Bitrate:       MIXED
Trunk  Bitrate:       100G
Status:               Provisioned
LLDP Drop Enabled:    FALSE
ARP Snoop Enabled:    FALSE
Client Port   Mapper/Trunk Port    Peer/Trunk Port    OTU40/0/0/0
              Traffic Split Percentage
OTU20/0/0/2/3            NONE          ODU20/0/0/0/2/3       100
OTU20/0/0/2/4            NONE          ODU20/0/0/0/2/4       100
TenGigECtrlr0/0/0/4/1 ODU2E0/0/0/0/4/1       NONE            100

The OTN-XP card is configured in 10G grey muxponder mode. The mixed 10G client traffic is aggregated onto a 100G trunk.

Configure the DAC rate for 400G muxponder modes

Configure the DAC rate on the optics controller (OTN-XP card) for 400G muxponder modes, aligning baud rate and pluggable settings for optimal optical performance.

Table 3. Feature History

Feature Name

Release

Description

DAC Configuration Support for 400GE, 4x100G, or 400G Regen modes

Cisco IOS XR Release 7.5.2

On the OTN-XP card, you can configure the Digital-to-Analog (DAC) rate for the 400GE, 4x100G, or 400G Regen modes with CFP2 DCO pluggable. Based on the DAC rate configured, pulse shaping and modem setting is set on the CFP2 DCO trunk pluggable.

From Release 7.5.2, you can configure DAC rate to set the bookended mode for the 400GE, 4x100G, or 400G Regen modes on the OTN-XP card.

These operating modes are supported on the CFP2 coherent pluggable module for the OTN-XP card:

Table 4. DAC supported modes

Network configuration mode

Trunk rate

Data path

Line framing

FEC type

Modulation format

BPS

Baud rate (GBd)

Pulse shaping

Mode type

400G

400G

400G TXP, 4x100G MXP, 400G Regen

FlexO-4

oFEC

16 QAM

4

63.1

1

Enhanced

This table provides the pulse shaping and modem setting values for the respective DAC rates.

Table 5. DAC rate

DAC rate

Pulse shape

Modem setting

1

0

Standard

1.25

1

Enhanced

1.5

1

Standard

2

0

Enhanced
Note

The default pulse shaping is 1.5 and mode type is Standard for the supported modes.

Follow these steps to configure the DAC rate for 400G muxponder modes:

Procedure

1.

Run the configure controller optics Rack/Slot/Instance/Port dac-rate 1x1.25 command to configure the DAC rate for OTN-XP card in the 400G TXP, 4x100G MXP, and 400G Regen modes.

Example:

This is a sample in which DAC rate is configured.


RP/0/RP0/CPU0:ios(config)#
RP/0/RP0/CPU0:ios(config)#controller optics 0/0/0/12 dac-Rate 1x1.25
RP/0/RP0/CPU0:ios(config-Optics)#commit
2.

Run the commit command to save and apply the configuration changes.
3.

Run the show controllers optics command to verify the DAC rate configuration for the 400G TXP, 4x100G MXP, and 400G Regen modes in the OTN-XP card.

Example:


RP/0/RP0/CPU0:ios#show controllers optics 0/2/0/12
Wed Apr 13 15:00:10.044 UTC
Controller State: Up
Transport Admin State: In Service
Laser State: On
LED State: Red
DAC RATE: 1x1.25
Configured DAC RATE: 1x1.25

The DAC rate is configured on the trunk port optics controller. The optical module operates at the baud rate associated with the configured DAC rate value, ensuring optimal performance for 400G muxponder operation.

Configure the muxponder mode for 4x100G MXP

Note

The LC mode must be configured to 4x100G-MXP-400G-TXP on the OTN-XP card before you perform this configuration. See Configure the LC mode.

Follow these steps to configure the OTN-XP card in 4x100G muxponder mode:

Procedure

1.

Run the configurehw-module location location mxponder-slicemxponder-slice-number trunk-rate 400Gclient-port-rate client-port-number client-type {100GE | OTU4} command to configure the OTN-XP card in the 4x100 muxponder mode.

Example:

This is a sample in which the OTN-XP card is configured with 400G trunk rate on the mxponder-slice 0 mode.


RP/0/RP0/CPU0:ios#config
Tue Apr 21 09:21:44.460 UTC
RP/0/RP0/CPU0:ios(config)#hw-module location 0/2 mxponder-slice 0
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#trunk-rate 400G
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 1 client-type 100GE

This is a sample in which the OTN-XP card is configured with 400G trunk rate on the mxponder-slice 1 mode.


RP/0/RP0/CPU0:ios#config
Tue Apr 21 09:21:44.460 UTC
RP/0/RP0/CPU0:ios(config)#hw-module location 0/2 mxponder-slice 1
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#trunk-rate 400G
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 8 client-type OTU4
2.

Run the commit command to save and apply the 4x100G MXP configuration.

Example:

RP/0/RP0/CPU0:ios(config-hwmod-mxp)#commit
3.

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

Example:

This is a sample to verify the muxponder configuration in the OTN-XP card.


RP/0/RP0/CPU0:ios#show hw-module location 0/1 mxponder
Mon Nov 30 01:32:57.338 UTC
Location: 0/1
Slice ID: 0
Client Bitrate: 100GE
Trunk Bitrate: 400G
Status: Provisioned
LLDP Drop Enabled: FALSE
ARP Snoop Enabled: FALSE
Client Port Mapper/Trunk Port CoherentDSP0/1/0/12
Traffic Split Percentage
HundredGigECtrlr0/1/0/1 ODU40/1/0/12/1 100
Location: 0/1
Slice ID: 1
Client Bitrate: OTU4
Trunk Bitrate: 400G
Status: Provisioned
Client Port Peer/Trunk Port CoherentDSP0/1/0/13
Traffic Split Percentage
OTU40/1/0/8 ODUC40/1/0/13 100

The OTN-XP card is successfully configured in 4x100G MXP mode. Four 100GE or OTU4 client ports are mapped to a 400G trunk per slice.

Configure the muxponder mode for 400G TXP

Configure the OTN-XP card in 400G transponder (TXP) mode so a single 400GE client port is mapped to a 400G trunk.

Note

The LC mode must be configured to 4x100G-MXP-400G-TXP on the OTN-XP card before you perform this configuration.

Follow these steps to configure the muxponder mode for 400G TXP:

Procedure

1.

Run the hw-module location location mxponder-slice mxponder-slice-numbertrunk-rate 400G client-port-rate client-port-number client-type 400GE command to configure the OTN-XP card in the 400G TXP mode.

Example:

This is a sample in which the OTN-XP card is configured with 400G trunk rate on the mxponder-slice 0 mode.


RP/0/RP0/CPU0:ios#config
Tue Apr 21 09:21:44.460 UTC
RP/0/RP0/CPU0:ios(config)#hw-module location 0/2 mxponder-slice 0
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#trunk-rate 400G
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 10 client-type 400GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#commit

This is a sample in which the OTN-XP card is configured with 400G trunk rate on the mxponder-slice 1 mode.


RP/0/RP0/CPU0:ios#config
Tue Apr 21 09:21:44.460 UTC
RP/0/RP0/CPU0:ios(config)#hw-module location 0/2 mxponder-slice 1
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#trunk-rate 400G
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 8 client-type 400GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#commit
2.

Run the commit command to save and apply the 400G TXP configuration.

Example:

RP/0/RP0/CPU0:ios(config-hwmod-mxp)#commit
3.

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

Example:

This is a sample to verify the muxponder configuration in the OTN-XP card.


RP/0/RP0/CPU0:ios#show hw-module location 0/1 mxponder
Mon Nov 30 01:36:14.514 UTC

Location: 0/1
Slice ID: 0
Client Bitrate: 400GE
Trunk Bitrate: 400G
Status: Provisioned
LLDP Drop Enabled: FALSE
ARP Snoop Enabled: FALSE
Client Port Mapper/Trunk Port CoherentDSP0/1/0/12
Traffic Split Percentage
FourHundredGigECtrlr0/1/0/10 ODU-FLEX0/1/0/12/10 100

Location: 0/1
Slice ID: 1
Client Bitrate: 400GE
Trunk Bitrate: 400G
Status: Provisioned
LLDP Drop Enabled: FALSE
ARP Snoop Enabled: FALSE
Client Port Mapper/Trunk Port CoherentDSP0/1/0/13
Traffic Split Percentage
FourHundredGigECtrlr0/1/0/8 ODU-FLEX0/1/0/13/8 100

The OTN-XP card is configured in 400G TXP mode. A single 400GE client port is mapped to the 400G trunk, and the configuration status shows "Provisioned".

Static TPN and TS allocation for TXP-MXP-grey muxponder modes

Provide clear and detailed static reference tables for TPN and TS allocations in various TXP-MXP-grey muxponder operating modes.

These tables provide static reference information on the mapping of tributary port numbers (TPN), tributary slots (TS), and clients for various TXP and MXP configurations used in the OTN-XP card.

400GE TXP configuration

Table 6. TPN-TS mapping in 400GE TXP configuration

Slice

Client port

Client rate

Trunk port

Trunk rate

TPN

TS

0

10

400GE

12

400G

1

1.1 to 4.20

1

8

400GE

13

400G

1

1.1 to 4.20

4x100GE/OTU4 MXP configuration

Table 7. TPN-TS mapping in 400GE TXP configuration

Slice

Client port

Client rate

Trunk port

Trunk rate

TPN

TS

0

10

100GE/OTU4

12

400G

1

1.1 to 1.20

7

100GE/OTU4

2

2.1 to 2.20

6

100GE/OTU4

3

3.1 to 3.20

1

100GE/OTU4

4

4.1 to 4.20

1

8

100GE/OTU4

13

400G

1

1.1 to 1.20

5

100GE/OTU4

2

2.1 to 2.20

4

100GE/OTU4

3

3.1 to 3.20

0

100GE/OTU4

4

4.1 to 4.20

10x10G grey muxponder configuration

Table 8. TPN-TS mapping in 10 X 10G grey muxponder configuration

Slice

Client port

Client lane

Client rate

Trunk port

Trunk rate

TPN

TS

0

4

1

10GE/OTU2/OTU2e

0

100G

1

1–8

2

10GE/OTU2/OTU2e

2

9–16

3

10GE/OTU2/OTU2e

3

17–24

4

10GE/OTU2/OTU2e

4

25–32

5

1

10GE/OTU2/OTU2e

5

33–40

2

10GE/OTU2/OTU2e

6

41–48

3

10GE/OTU2/OTU2e

7

49–56

4

10GE/OTU2/OTU2e

8

57–64

2

3

10GE/OTU2/OTU2e

9

65–72

4

10GE/OTU2/OTU2e

10

73–80

1

7

1

10GE/OTU2/OTU2e

1

100G

1

1–8

2

10GE/OTU2/OTU2e

2

9–16

3

10GE/OTU2/OTU2e

3

17–24

4

10GE/OTU2/OTU2e

4

25–32

6

1

10GE/OTU2/OTU2e

5

33–40

2

10GE/OTU2/OTU2e

6

41–48

3

10GE/OTU2/OTU2e

7

49–56

4

10GE/OTU2/OTU2e

8

57–64

11

3

10GE/OTU2/OTU2e

9

65–72

4

10GE/OTU2/OTU2e

10

73–80

Configure the muxponder mode for 40x10G muxponder

Aggregate up to 40 10G client lanes onto a 400G CFP2 DCO trunk on the OTN-XP card using muxponder mode.

Follow these steps to configure the OTN-XP card in 40x10G muxponder mode:

Procedure

1.

Run the configure hw-module location location mxponder-slicemxponder-slice-number trunk-rate 400Gclient-port-rate client-port-number lane lane-number client-type {10GE | OTU2 | OTU2E | STM64 | OC192}command to configure the OTN-XP card in the 40x10G muxponder mode.

Example:

This is a sample in which the OTN-XP card is configured with 400G trunk rate on the mxponder-slice 0 mode.


RP/0/RP0/CPU0:ios#config
Tue Apr 21 09:21:44.460 UTC
RP/0/RP0/CPU0:ios(config)#hw-module location 0/3 mxponder-slice 0
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#trunk-rate 400G
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 0 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 0 lane 2 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 0 lane 3 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 0 lane 4 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 1 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 1 lane 2 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 1 lane 3 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 1 lane 4 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 2 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 2 lane 2 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 2 lane 3 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 2 lane 4 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 3 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 3 lane 2 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 3 lane 3 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 3 lane 4 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 lane 2 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 lane 3 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 lane 4 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 5 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 5 lane 2 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 5 lane 3 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 5 lane 4 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 6 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 6 lane 2 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 6 lane 3 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 6 lane 4 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 7 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 7 lane 2 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 7 lane 3 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 7 lane 4 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 9 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 9 lane 2 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 9 lane 3 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 9 lane 4 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 11 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 11 lane 2 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 11 lane 3 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 11 lane 4 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#commit

This is a sample in which the port 0 lane 1 has OC192 payload and lane 2 has STM64 payload. Only slice 0 configuration is supported for OC192/STM64.


RP/0/RP0/CPU0:ios#config
Tue Apr 21 09:21:44.460 UTC
RP/0/RP0/CPU0:ios(config)#hw-module location 0/0 mxponder-slice 0
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#trunk-rate 400G
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 0 lane 1 client-type oc192
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 0 lane 2 client-type stm64
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#commit
2.

Run the commit command to save and apply the 40x10G muxponder configuration.

Example:

RP/0/RP0/CPU0:ios(config-hwmod-mxp)#commit
3.

Run the show hw-module location command to verify the 40x10G muxponder configuration in the OTN-XP card.

Example:


RP/0/RP0/CPU0:ios#show hw-module location 0/3 mxponder
Wed Jun  2 17:57:36.647 UTC

Location:             0/3
Slice ID:             0
Client Bitrate:       10GE
Trunk  Bitrate:       400G
Status:               Provisioned
LLDP Drop Enabled:    FALSE
ARP Snoop Enabled:    FALSE
Client Port                     Mapper/Trunk Port          CoherentDSP0/3/0/12  
                                Traffic Split Percentage

TenGigECtrlr0/3/0/0/1           ODU2E0/3/0/12/0/1                             100
TenGigECtrlr0/3/0/0/2           ODU2E0/3/0/12/0/2                             100
TenGigECtrlr0/3/0/0/3           ODU2E0/3/0/12/0/3                             100
TenGigECtrlr0/3/0/0/4           ODU2E0/3/0/12/0/4                             100
TenGigECtrlr0/3/0/1/1           ODU2E0/3/0/12/1/1                             100
TenGigECtrlr0/3/0/1/2           ODU2E0/3/0/12/1/2                             100
TenGigECtrlr0/3/0/1/3           ODU2E0/3/0/12/1/3                             100
TenGigECtrlr0/3/0/1/4           ODU2E0/3/0/12/1/4                             100
TenGigECtrlr0/3/0/2/1           ODU2E0/3/0/12/2/1                             100
TenGigECtrlr0/3/0/2/2           ODU2E0/3/0/12/2/2                             100
TenGigECtrlr0/3/0/2/3           ODU2E0/3/0/12/2/3                             100
TenGigECtrlr0/3/0/2/4           ODU2E0/3/0/12/2/4                             100
TenGigECtrlr0/3/0/3/1           ODU2E0/3/0/12/3/1                             100
TenGigECtrlr0/3/0/3/2           ODU2E0/3/0/12/3/2                             100
TenGigECtrlr0/3/0/3/3           ODU2E0/3/0/12/3/3                             100
TenGigECtrlr0/3/0/3/4           ODU2E0/3/0/12/3/4                             100
TenGigECtrlr0/3/0/4/1           ODU2E0/3/0/12/4/1                             100
TenGigECtrlr0/3/0/4/2           ODU2E0/3/0/12/4/2                             100
TenGigECtrlr0/3/0/4/3           ODU2E0/3/0/12/4/3                             100
TenGigECtrlr0/3/0/4/4           ODU2E0/3/0/12/4/4                             100
TenGigECtrlr0/3/0/5/1           ODU2E0/3/0/12/5/1                             100
TenGigECtrlr0/3/0/5/2           ODU2E0/3/0/12/5/2                             100
TenGigECtrlr0/3/0/5/3           ODU2E0/3/0/12/5/3                             100
TenGigECtrlr0/3/0/5/4           ODU2E0/3/0/12/5/4                             100
TenGigECtrlr0/3/0/6/1           ODU2E0/3/0/12/6/1                             100
TenGigECtrlr0/3/0/6/2           ODU2E0/3/0/12/6/2                             100
TenGigECtrlr0/3/0/6/3           ODU2E0/3/0/12/6/3                             100
TenGigECtrlr0/3/0/6/4           ODU2E0/3/0/12/6/4                             100
TenGigECtrlr0/3/0/7/1           ODU2E0/3/0/12/7/1                             100
TenGigECtrlr0/3/0/7/2           ODU2E0/3/0/12/7/2                             100
TenGigECtrlr0/3/0/7/3           ODU2E0/3/0/12/7/3                             100
TenGigECtrlr0/3/0/7/4           ODU2E0/3/0/12/7/4                             100
TenGigECtrlr0/3/0/9/1           ODU2E0/3/0/12/9/1                             100
TenGigECtrlr0/3/0/9/2           ODU2E0/3/0/12/9/2                             100
TenGigECtrlr0/3/0/9/3           ODU2E0/3/0/12/9/3                             100
TenGigECtrlr0/3/0/9/4           ODU2E0/3/0/12/9/4                             100
TenGigECtrlr0/3/0/11/1          ODU2E0/3/0/12/11/1                            100
TenGigECtrlr0/3/0/11/2          ODU2E0/3/0/12/11/2                            100
TenGigECtrlr0/3/0/11/3          ODU2E0/3/0/12/11/3                            100
TenGigECtrlr0/3/0/11/4          ODU2E0/3/0/12/11/4                            100

The output shows Client Bitrate as MIXED (or 10GE/OTU2), Trunk Bitrate as 400G, and all mapped TenGigECtrlr and OTU2 controllers with ODU2 assignments to CoherentDSP trunk port 12.

The OTN-XP card is now configured in 40x10G muxponder mode. Up to 40 10G client lanes are aggregated onto a single 400G CFP2 DCO trunk per slice.

Configure the muxponder mode for 30x10G muxponder

Enable high-capacity multiplexing on the OTN-XP card by configuring 30x10G muxponder mode, allowing multiple 10G client lanes to be aggregated onto a single 300G trunk.

Follow these steps to configure 30x10G muxponder mode:

Procedure

1.

Run the configure hw-module locationlocation mxponder-slicemxponder-slice-number trunk-rate 300Gclient-port-rate client-port-number lane lane-number client-type {10GE | OTU2E | OTU2} command to configure the OTN-XP card in the 30x10G muxponder mode.

Example:

This is a sample in which the OTN-XP card is configured with 300G trunk rate on the mxponder-slice 0 mode.


RP/0/RP0/CPU0:ios#config
Tue Apr 21 09:21:44.460 UTC
RP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder-slice 0
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#trunk-rate 300G
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 0 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 0 lane 2 client-type OTU2E
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 0 lane 3 client-type OTU2
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 0 lane 4 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 1 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 1 lane 2 client-type OTU2E
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 1 lane 3 client-type OTU2
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 1 lane 4 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 2 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 2 lane 2 client-type OTU2E
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 2 lane 3 client-type OTU2
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 2 lane 4 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 3 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 3 lane 2 client-type OTU2E
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 3 lane 3 client-type OTU2
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 3 lane 4 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 lane 2 client-type OTU2E
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 lane 3 client-type OTU2
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 lane 4 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 5 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 5 lane 2 client-type OTU2E
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 5 lane 3 client-type OTU2
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 5 lane 4 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 9 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 9 lane 2 client-type OTU2E
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 9 lane 3 client-type OTU2
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 9 lane 4 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 11 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 11 lane 2 client-type OTU2E
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#commit
2.

Run the commit command to save and apply the 30x10G muxponder configuration.

Example:

RP/0/RP0/CPU0:ios(config-hwmod-mxp)#commit
3.

Run the show hw-module location command to verify the 30x10G muxponder configuration in the OTN-XP card.

Example:


RP/0/RP0/CPU0:ios#show hw-module location 0/1 mxponder
Wed Jun  2 17:56:40.574 UTC

Location:             0/1
Slice ID:             0
Client Bitrate:       MIXED
Trunk  Bitrate:       300G
Status:               Provisioned
LLDP Drop Enabled:    FALSE
ARP Snoop Enabled:    FALSE
Client Port                     Mapper/Trunk Port   Peer/Trunk Port        CoherentDSP0/1/0/12  
                                Traffic Split Percentage

OTU20/1/0/0/3                         NONE      ODU20/1/0/12/0/3                              100
OTU20/1/0/1/3                         NONE      ODU20/1/0/12/1/3                              100
OTU20/1/0/2/3                         NONE      ODU20/1/0/12/2/3                              100
OTU20/1/0/3/3                         NONE      ODU20/1/0/12/3/3                              100
OTU20/1/0/4/3                         NONE      ODU20/1/0/12/4/3                              100
OTU20/1/0/5/3                         NONE      ODU20/1/0/12/5/3                              100
OTU20/1/0/9/3                         NONE      ODU20/1/0/12/9/3                              100
OTU2E0/1/0/0/2                        NONE      ODU2E0/1/0/12/0/2                             100
OTU2E0/1/0/1/2                        NONE      ODU2E0/1/0/12/1/2                             100
OTU2E0/1/0/2/2                        NONE      ODU2E0/1/0/12/2/2                             100
OTU2E0/1/0/3/2                        NONE      ODU2E0/1/0/12/3/2                             100
OTU2E0/1/0/4/2                        NONE      ODU2E0/1/0/12/4/2                             100
OTU2E0/1/0/5/2                        NONE      ODU2E0/1/0/12/5/2                             100
OTU2E0/1/0/9/2                        NONE      ODU2E0/1/0/12/9/2                             100
TenGigECtrlr0/1/0/0/1           ODU2E0/1/0/12/0/1             NONE                            100
TenGigECtrlr0/1/0/0/4           ODU2E0/1/0/12/0/4             NONE                            100
TenGigECtrlr0/1/0/1/1           ODU2E0/1/0/12/1/1             NONE                            100
TenGigECtrlr0/1/0/1/4           ODU2E0/1/0/12/1/4             NONE                            100
TenGigECtrlr0/1/0/2/1           ODU2E0/1/0/12/2/1             NONE                            100
TenGigECtrlr0/1/0/2/4           ODU2E0/1/0/12/2/4             NONE                            100
TenGigECtrlr0/1/0/3/1           ODU2E0/1/0/12/3/1             NONE                            100
TenGigECtrlr0/1/0/3/4           ODU2E0/1/0/12/3/4             NONE                            100
TenGigECtrlr0/1/0/4/1           ODU2E0/1/0/12/4/1             NONE                            100
TenGigECtrlr0/1/0/4/4           ODU2E0/1/0/12/4/4             NONE                            100
TenGigECtrlr0/1/0/5/1           ODU2E0/1/0/12/5/1             NONE                            100
TenGigECtrlr0/1/0/5/4           ODU2E0/1/0/12/5/4             NONE                            100
TenGigECtrlr0/1/0/9/1           ODU2E0/1/0/12/9/1             NONE                            100
TenGigECtrlr0/1/0/9/4           ODU2E0/1/0/12/9/4             NONE                            100

The OTN-XP card is configured in 30x10G muxponder mode, allowing up to 30 10G client lanes to be multiplexed onto a 300G CFP2 DCO trunk.

Hybrid modes using 40x10G-4x100G-MXP

Available hybrid modes

A hybrid mode is a muxponder configuration on the OTN-XP card in 40x10G-4x100G-MXP LC mode that

  • simultaneously carries a mix of 10GE and 100GE client signals on the same trunk wavelength,

  • allows flexible combinations such as 20x10G + 2x100G or 10x10G + 3x100G on a 400G CFP2 trunk, and

  • reduces wasted trunk capacity by combining different client granularities in a single slice.

Table 9. Feature History

Feature Name

Release Information

Description

Hybrid Modes Using 40x10G-4x100G-MXP

Cisco IOS XR Release 7.3.2

With the 40x10G-4x100G-MXP muxponder mode support, you can configure the following hybrid modes:

  • 20x10G + 2x100G

  • 10x10G + 3 x 100G

With the 40x10G-4x100G-MXP muxponder mode support, you have flexibility to choose a combination of 10G and 100G client rates across different OTN and Ethernet client rates.
Table 10. Feature History

Feature Name

Release Information

Description

Support for 10x10G + 2 x 100G, 20x10G + 1 x 100G, and 30x10G + 1 x 100G Hybrid Modes

Cisco IOS XR Release 7.5.1

You can configure different client rates across the ports depending on the bandwidth requirement, using the following hybrid modes:

  • 30x10G + 1 x 100G

  • 10x10G + 2 x 100G

  • 20x10G + 1 x 100G

Hybrid modes for the 40x10G-4x100G-MXP line cards include:

  • 20x10G + 2x100G

  • 10x10G + 3 x 100G

  • 30x10G + 1 x 100G

  • 10x10G + 2 x 100G

  • 20x10G + 1 x 100G

Configure the hybrid muxponder mode for 20x10G + 2x100G over 400G

Set up the OTN-XP card in hybrid muxponder mode for efficient multiplexing of 20x10G and 2x100G client connections over a 400G trunk.

Follow these steps to configure hybrid muxponder mode for 20x10G and 2x100G clients over a 400G trunk:

Procedure

1.

Run the configure hw-module location location mxponder-slicemxponder-slice-number trunk-rate 400Gclient-port-rate client-port-number client-type {100GE | OTU4} client-port-rate client-port-number lane lane-number client-type {10GE | OTU2 | OTU2E} command to configure the OTN-XP card in the 20x10G-2x100G muxponder mode.

Example:

This is a sample in which the OTN-XP card is configured with 400G trunk rate on the mxponder-slice 0 mode.


RP/0/RP0/CPU0:ios#config
Tue Apr 21 09:21:44.460 UTC
RP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder-slice 0
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#trunk-rate 400G
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 0 client-type 100GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 1 client-type OTU4
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 2 lane 3 client-type OTU2E
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 2 lane 4 client-type OTU2E
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 lane 1 client-type OTU2E
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 lane 2 client-type OTU2E
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 lane 3 client-type OTU2E
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 lane 4 client-type OTU2E
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 5 lane 1 client-type OTU2E
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 5 lane 2 client-type OTU2E
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 5 lane 3 client-type OTU2E
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 5 lane 4 client-type OTU2E
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 6 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 6 lane 2 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 6 lane 3 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 6 lane 4 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 7 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 7 lane 2 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 7 lane 3 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 7 lane 4 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 11 lane 3 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 11 lane 4 client-type 10GE
2.

Run the commit command to save and apply the hybrid 20x10G + 2x100G configuration.

Example:

RP/0/RP0/CPU0:ios(config-hwmod-mxp)#commit
3.

Run the show hw-module location command to verify the 20x10G-2x100G muxponder configuration in the OTN-XP card.

Example:


RP/0/RP0/CPU0:ios#show hw-module location 0/1 mxponder
Wed Jun  2 18:00:58.201 UTC
Location:             0/1
Slice ID:             0
Client Bitrate:       MIXED
Trunk  Bitrate:       400G
Status:               Provisioned
LLDP Drop Enabled:    FALSE
ARP Snoop Enabled:    FALSE
Client Port                     Mapper/Trunk Port   Peer/Trunk Port        CoherentDSP0/1/0/12
                                Traffic Split Percentage

OTU40/1/0/1                           NONE      ODU40/1/0/12/1                        100
OTU2E0/1/0/2/3                        NONE      ODU2E0/1/0/12/2/3                             100
OTU2E0/1/0/2/4                        NONE      ODU2E0/1/0/12/2/4                             100
OTU2E0/1/0/4/1                        NONE      ODU2E0/1/0/12/4/1                             100
OTU2E0/1/0/4/2                        NONE      ODU2E0/1/0/12/4/2                             100
OTU2E0/1/0/4/3                        NONE      ODU2E0/1/0/12/4/3                             100
OTU2E0/1/0/4/4                        NONE      ODU2E0/1/0/12/4/4                             100
OTU2E0/1/0/5/1                        NONE      ODU2E0/1/0/12/5/1                             100
OTU2E0/1/0/5/2                        NONE      ODU2E0/1/0/12/5/2                             100
OTU2E0/1/0/5/3                        NONE      ODU2E0/1/0/12/5/3                             100
OTU2E0/1/0/5/4                        NONE      ODU2E0/1/0/12/5/4                             100
TenGigECtrlr0/1/0/6/1           ODU2E0/1/0/12/6/1                             100
TenGigECtrlr0/1/0/6/2           ODU2E0/1/0/12/6/2                             100
TenGigECtrlr0/1/0/6/3           ODU2E0/1/0/12/6/3                             100
TenGigECtrlr0/1/0/6/4           ODU2E0/1/0/12/6/4                             100
TenGigECtrlr0/1/0/7/1           ODU2E0/1/0/12/7/1                             100
TenGigECtrlr0/1/0/7/2           ODU2E0/1/0/12/7/2                             100
TenGigECtrlr0/1/0/7/3           ODU2E0/1/0/12/7/3                             100
TenGigECtrlr0/1/0/7/4           ODU2E0/1/0/12/7/4                             100
TenGigECtrlr0/1/0/11/3           ODU2E0/1/0/12/11/3                             100
TenGigECtrlr0/1/0/11/4           ODU2E0/1/0/12/11/4                             100
HundredGigECtrlr0/1/0/0         ODU40/1/0/12/0        NONE                            100

The OTN-XP card is configured in hybrid muxponder mode with 20x10G and 2x100G clients multiplexed over a 400G CFP2 DCO trunk port on slice 0.

Configure the hybrid muxponder mode for 10x10G + 3x100G over 400G

Enable the OTN-XP card to operate in hybrid muxponder mode, combining multiple client ports for efficient transport over a single 400G trunk.

Follow these steps to configure hybrid muxponder mode for 10x10G + 3x100G clients:

Procedure

1.

Run the configure hw-module location location mxponder-slicemxponder-slice-number trunk-rate 400Gclient-port-rate client-port-number client-type {100GE | OTU4} client-port-rate client-port-number lane lane-number client-type {10GE | OTU2 | OTU2E} command to configure the OTN-XP card in the 10 x 10G and 3 x 100G muxponder mode.

Example:

This is a sample in which the OTN-XP card is configured with 400G trunk rate on the mxponder-slice 0 mode.


RP/0/RP0/CPU0:ios#config
Tue Apr 21 09:21:44.460 UTC
RP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder-slice 0
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#trunk-rate 400G
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 0 client-type 100GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 1 client-type OTU4
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 2 lane 3 client-type OTU2E
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 2 lane 4 client-type OTU2E
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 lane 1 client-type OTU2E
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 lane 2 client-type OTU2E
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 lane 3 client-type OTU2E
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 lane 4 client-type OTU2E
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 5 lane 1 client-type OTU2E
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 5 lane 2 client-type OTU2E
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 5 lane 3 client-type OTU2E
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 5 lane 4 client-type OTU2E
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 6 client-type 100GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#commit
2.

Run the commit command to save and apply the hybrid 10x10G + 3x100G configuration.
3.

Run the show hw-module location command to verify the 10 x 10G and 3 x 100G muxponder configuration in the OTN-XP card

Example:


RP/0/RP0/CPU0:ios#show hw-module location 0/1 mxponder
Wed Jun  2 18:00:58.201 UTC

Location:             0/1
Slice ID:             0
Client Bitrate:       MIXED
Trunk  Bitrate:       400G
Status:               Provisioned
LLDP Drop Enabled:    FALSE
ARP Snoop Enabled:    FALSE
Client Port                     Mapper/Trunk Port   Peer/Trunk Port        CoherentDSP0/1/0/12
                                Traffic Split Percentage

OTU40/1/0/1                           NONE      ODU40/1/0/12/1                        100
OTU2E0/1/0/2/3                        NONE      ODU2E0/1/0/12/2/3                             100
OTU2E0/1/0/2/4                        NONE      ODU2E0/1/0/12/2/4                             100
OTU2E0/1/0/4/1                        NONE      ODU2E0/1/0/12/4/1                             100
OTU2E0/1/0/4/2                        NONE      ODU2E0/1/0/12/4/2                             100
OTU2E0/1/0/4/3                        NONE      ODU2E0/1/0/12/4/3                             100
OTU2E0/1/0/4/4                        NONE      ODU2E0/1/0/12/4/4                             100
OTU2E0/1/0/5/1                        NONE      ODU2E0/1/0/12/5/1                             100
OTU2E0/1/0/5/2                        NONE      ODU2E0/1/0/12/5/2                             100
OTU2E0/1/0/5/3                        NONE      ODU2E0/1/0/12/5/3                             100
OTU2E0/1/0/5/4                        NONE      ODU2E0/1/0/12/5/4                             100
HundredGigECtrlr0/1/0/0         ODU40/1/0/12/0        NONE                            100
HundredGigECtrlr0/1/0/6         ODU40/1/0/12/6        NONE                            100

The OTN-XP card is configured in hybrid muxponder mode, with 10x10G and 3x100G clients multiplexed over a 400G CFP2 DCO trunk on slice 0.

Configure the hybrid muxponder mode for 20x10G + 1x100G over 300G

Use this procedure to configure the OTN-XP card in hybrid mode with 20x10G and 1x100G client ports multiplexed over a 300G CFP2 DCO trunk on slice 0.

Procedure

1.

Run the configure hw-module location location mxponder-slice mxponder-slice-number trunk-rate 300Gclient-port-rate client-port-number client-type {100GE | OTU4} client-port-rate client-port-number lane lane-number client-type {10GE | OTU2 | OTU2E} command to configure the OTN-XP card in the 20x10G + 1x100G muxponder mode.

Example:

This is a sample in which the OTN-XP card is configured with the 20x10G + 1x100G mode on the mxponder-slice 0 mode.


RP/0/RP0/CPU0:ios#configure 
Sun Jul 25 12:43:00.399 UTC
RP/0/RP0/CPU0:ios(config)#
RP/0/RP0/CPU0:ios(config)#hw-module location 0/2 mxponder-slice 0
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#trunk-rate 300G 
RP/0/RP0/CPU0:ios#configure 
Sun Jul 25 12:43:00.399 UTC
RP/0/RP0/CPU0:ios(config)#
RP/0/RP0/CPU0:ios(config)#hw-module location 0/2 mxponder-slice 0
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#trunk-rate 300G 
/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 0 client-type 100GE 
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 1 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 1 lane 2 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 1 lane 3 client-type otu2
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 1 lane 4 client-type otu2e
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 2 lane 3 client-type otu2 
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 2 lane 4 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 lane 2 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 lane 3 client-type OTU2
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 lane 4 client-type OTU2
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 5 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 5 lane 2 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 5 lane 3 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 5 lane 4 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 9 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 9 lane 2 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 9 lane 3 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 9 lane 4 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 11 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 11 lane 2 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#commit
2.

Run the commit command to save and apply the hybrid 20x10G + 1x100G configuration.

Example:

RP/0/RP0/CPU0:ios(config-hwmod-mxp)#commit
3.

Run the show hw-module location command to verify the 20x10G + 1x100G muxponder configuration in the OTN-XP card.

Example:


RP/0/RP0/CPU0:ios#sh hw-module location 0/2 mxponder-slice 0
Sun Jul 25 13:11:01.829 UTC

Location:             0/2
Slice ID:             0
Client Bitrate:       MIXED
Trunk  Bitrate:       300G
Status:               Provisioned
LLDP Drop Enabled:    FALSE
ARP Snoop Enabled:    FALSE
Client Port                     Mapper/Trunk Port   Peer/Trunk Port        CoherentDSP0/2/0/12  
                                Traffic Split Percentage

OTU20/2/0/1/3                         NONE      ODU20/2/0/12/1/3                              100
OTU20/2/0/2/3                         NONE      ODU20/2/0/12/2/3                              100
OTU20/2/0/4/3                         NONE      ODU20/2/0/12/4/3                              100
OTU20/2/0/4/4                         NONE      ODU20/2/0/12/4/4                              100
OTU2E0/2/0/1/4                        NONE      ODU2E0/2/0/12/1/4                             100
OTU2E0/2/0/2/1                        NONE      ODU2E0/2/0/12/2/1                             100
OTU2E0/2/0/2/2                        NONE      ODU2E0/2/0/12/2/2                             100
TenGigECtrlr0/2/0/1/1           ODU2E0/2/0/12/1/1             NONE                            100
TenGigECtrlr0/2/0/1/2           ODU2E0/2/0/12/1/2             NONE                            100
TenGigECtrlr0/2/0/2/4           ODU2E0/2/0/12/2/4             NONE                            100
TenGigECtrlr0/2/0/4/1           ODU2E0/2/0/12/4/1             NONE                            100
TenGigECtrlr0/2/0/4/2           ODU2E0/2/0/12/4/2             NONE                            100
TenGigECtrlr0/2/0/5/1           ODU2E0/2/0/12/5/1             NONE                            100
TenGigECtrlr0/2/0/5/2           ODU2E0/2/0/12/5/2             NONE                            100
TenGigECtrlr0/2/0/5/3           ODU2E0/2/0/12/5/3             NONE                            100
TenGigECtrlr0/2/0/5/4           ODU2E0/2/0/12/5/4             NONE                            100
TenGigECtrlr0/2/0/9/1           ODU2E0/2/0/12/9/1             NONE                            100
TenGigECtrlr0/2/0/9/2           ODU2E0/2/0/12/9/2             NONE                            100
TenGigECtrlr0/2/0/9/3           ODU2E0/2/0/12/9/3             NONE                            100
TenGigECtrlr0/2/0/9/4           ODU2E0/2/0/12/9/4             NONE                            100
TenGigECtrlr0/2/0/11/1          ODU2E0/2/0/12/11/1            NONE                            100
TenGigECtrlr0/2/0/11/2          ODU2E0/2/0/12/11/2            NONE                            100
HundredGigECtrlr0/2/0/0        ODU40/2/0/12/0        NONE                            100 
                          100 
RP/0/RP0/CPU0:ios#show lc-module location 0/2 lcmode 
Sun Jul 25 15:28:16.324 UTC

Node    Lcmode_Supported    Owner    Running                         Configured
--------------------------------------------------------------------------------
0/2                      Yes                 CLI      40x10G-4x100G-MXP      40x10G-4x100G-MXP

The OTN-XP card is now configured in hybrid muxponder mode with 20x10G + 1x100G clients on slice 0, multiplexed over a 300G trunk port, ready for operation.

Configure the hybrid muxponder mode for 30x10G + 1x100G over 400G

Enable the OTN-XP card to operate in hybrid muxponder mode, supporting 30x10G and 1x100G client ports over a 400G trunk.

Follow these steps to configure the hybrid muxponder mode:

Procedure

1.

Run the configurehw-module locationlocation mxponder-slicemxponder-slice-numbertrunk-rate 400Gclient-port-rate client-port-number client-type {100GE | OTU4}client-port-rate client-port-number lanelane-number client-type {10GE | OTU2 | OTU2E} command to configure the OTN-XP card in the 30x10G + 1x100G muxponder mode.

Example:

This is a sample in which the OTN-XP card is configured with 300G trunk rate on the mxponder-slice 0 mode.


RP/0/RP0/CPU0:ios#configure 
Sun Jul 25 12:43:00.399 UTC
RP/0/RP0/CPU0:ios(config)#
RP/0/RP0/CPU0:ios(config)#hw-module location 0/2 mxponder-slice 0
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#trunk-rate 400G 
RP/0/RP0/CPU0:ios#configure 
Sun Jul 25 12:43:00.399 UTC
RP/0/RP0/CPU0:ios(config)#
RP/0/RP0/CPU0:ios(config)#hw-module location 0/2 mxponder-slice 0
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#trunk-rate 400G 
/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 6 client-type 100GE 
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 0 lane 1 client-type 10GE 
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 0 lane 2 client-type otu2 
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 0 lane 3 client-type otu2e
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 0 lane 4 client-type 10GE 
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 1 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 1 lane 2 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 1 lane 3 client-type otu2
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 1 lane 4 client-type otu2e
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 2 lane 1 client-type otu2e
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 2 lane 2 client-type otu2e
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 2 lane 3 client-type otu2 
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 2 lane 4 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 3 lane 1 client-type 10GE 
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 3 lane 2 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 3 lane 3 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 3 lane 4 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 lane 2 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 lane 3 client-type OTU2
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 lane 4 client-type OTU2
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 5 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 5 lane 2 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 5 lane 3 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 5 lane 4 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 9 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 9 lane 2 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 9 lane 3 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 9 lane 4 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 11 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 11 lane 2 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#commit
2.

Run the commit command to save and apply the hybrid 30x10G + 1x100G configuration.

Example:

RP/0/RP0/CPU0:ios(config-hwmod-mxp)#commit
3.

Run the show hw-module location command to verify the 30x10G + 1x100G muxponder configuration in the OTN-XP card.

Example:

This is a sample to verify the 30x10G + 1x100G muxponder configuration in the OTN-XP card.


RP/0/RP0/CPU0:ios#sh hw-module location 0/2 mxponder-slice 0
Sun Jul 25 13:11:01.829 UTC

Location:             0/2
Slice ID:             0
Client Bitrate:       MIXED
Trunk  Bitrate:       400G
Status:               Provisioned
LLDP Drop Enabled:    FALSE
ARP Snoop Enabled:    FALSE
Client Port                     Mapper/Trunk Port   Peer/Trunk Port        CoherentDSP0/2/0/12  
                                Traffic Split Percentage

OTU20/2/0/0/2                         NONE      ODU20/2/0/12/0/2                              100
OTU20/2/0/1/3                         NONE      ODU20/2/0/12/1/3                              100
OTU20/2/0/2/3                         NONE      ODU20/2/0/12/2/3                              100
OTU20/2/0/4/3                         NONE      ODU20/2/0/12/4/3                              100
OTU20/2/0/4/4                         NONE      ODU20/2/0/12/4/4                              100
OTU2E0/2/0/0/3                        NONE      ODU2E0/2/0/12/0/3                             100
OTU2E0/2/0/1/4                        NONE      ODU2E0/2/0/12/1/4                             100
OTU2E0/2/0/2/1                        NONE      ODU2E0/2/0/12/2/1                             100
OTU2E0/2/0/2/2                        NONE      ODU2E0/2/0/12/2/2                             100
TenGigECtrlr0/2/0/0/1           ODU2E0/2/0/12/0/1             NONE                            100
TenGigECtrlr0/2/0/0/4           ODU2E0/2/0/12/0/4             NONE                            100
TenGigECtrlr0/2/0/1/1           ODU2E0/2/0/12/1/1             NONE                            100
TenGigECtrlr0/2/0/1/2           ODU2E0/2/0/12/1/2             NONE                            100
TenGigECtrlr0/2/0/2/4           ODU2E0/2/0/12/2/4             NONE                            100
TenGigECtrlr0/2/0/3/1           ODU2E0/2/0/12/3/1             NONE                            100
TenGigECtrlr0/2/0/3/2           ODU2E0/2/0/12/3/2             NONE                            100
TenGigECtrlr0/2/0/3/3           ODU2E0/2/0/12/3/3             NONE                            100
TenGigECtrlr0/2/0/3/4           ODU2E0/2/0/12/3/4             NONE                            100
TenGigECtrlr0/2/0/4/1           ODU2E0/2/0/12/4/1             NONE                            100
TenGigECtrlr0/2/0/4/2           ODU2E0/2/0/12/4/2             NONE                            100
TenGigECtrlr0/2/0/5/1           ODU2E0/2/0/12/5/1             NONE                            100
TenGigECtrlr0/2/0/5/2           ODU2E0/2/0/12/5/2             NONE                            100
TenGigECtrlr0/2/0/5/3           ODU2E0/2/0/12/5/3             NONE                            100
TenGigECtrlr0/2/0/5/4           ODU2E0/2/0/12/5/4             NONE                            100
TenGigECtrlr0/2/0/9/1           ODU2E0/2/0/12/9/1             NONE                            100
TenGigECtrlr0/2/0/9/2           ODU2E0/2/0/12/9/2             NONE                            100
TenGigECtrlr0/2/0/9/3           ODU2E0/2/0/12/9/3             NONE                            100
TenGigECtrlr0/2/0/9/4           ODU2E0/2/0/12/9/4             NONE                            100
TenGigECtrlr0/2/0/11/1          ODU2E0/2/0/12/11/1            NONE                            100
TenGigECtrlr0/2/0/11/2          ODU2E0/2/0/12/11/2            NONE                            100
HundredGigECtrlr0/2/0/6         ODU40/2/0/12/0        NONE                            100 
                       100 

RP/0/RP0/CPU0:ios#show lc-module location 0/2 lcmode 
Sun Jul 25 15:28:16.324 UTC

Node    Lcmode_Supported    Owner    Running                         Configured
--------------------------------------------------------------------------------
0/2                      Yes                 CLI      40x10G-4x100G-MXP      40x10G-4x100G-MXP

The OTN-XP card is now configured in hybrid muxponder mode, enabling 30x10G and 1x100G client ports on slice 0, multiplexed over a 400G CFP2 DCO trunk port.

Configure the hybrid muxponder mode for 10x10G + 2x100G over 300G

Enable hybrid multiplexing for 10x10G and 2x100G client ports on an OTN-XP card, mapped to a 300G trunk, for flexible transport and optimized bandwidth usage.

Follow these steps to configure hybrid muxponder mode for 10x10G + 2x100G over 300G:

Procedure

1.

Run the configure hw-module location location mxponder-slicemxponder-slice-number trunk-rate 300Gclient-port-rate client-port-number client-type {100GE | OTU4} client-port-rate client-port-number lane lane-number client-type {10GE | OTU2 | OTU2E} command to configure the OTN-XP card in the 10x10G + 2x100G muxponder mode.

Example:

This is a sample in which the OTN-XP card is configured with 300G trunk rate on the mxponder-slice 0 mode.


RP/0/RP0/CPU0:ios#configure 
Sun Jul 25 12:43:00.399 UTC
RP/0/RP0/CPU0:ios(config)#
RP/0/RP0/CPU0:ios(config)#hw-module location 0/2 mxponder-slice 0
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#trunk-rate 300G 
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 0 client-type 100GE 
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 1 client-type otu4
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 2 lane 3 client-type 10GE 
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 2 lane 4 client-type OTU2e
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 lane 2 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 lane 3 client-type OTU2
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 lane 4 client-type OTU2
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 5 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 5 lane 2 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 5 lane 3 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 5 lane 4 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#commit
2.

Run the commit command to save and apply the hybrid 10x10G + 2x100G configuration.

Example:

RP/0/RP0/CPU0:ios(config-hwmod-mxp)#commit
3.

Run the show hw-module location command to verify the 10x10G + 2x100G muxponder configuration in the OTN-XP card.

Example:


RP/0/RP0/CPU0:ios#show hw-module location 0/2 mxponder-slice 0
Sun Jul 25 14:57:40.806 UTC

Location:             0/2
Slice ID:             0
Client Bitrate:       MIXED
Trunk  Bitrate:       300G
Status:               Provisioned
LLDP Drop Enabled:    FALSE
ARP Snoop Enabled:    FALSE
Client Port                     Mapper/Trunk Port   Peer/Trunk Port        CoherentDSP0/2/0/12  
                                Traffic Split Percentage

OTU40/2/0/1                           NONE      ODU40/2/0/12/1                        100
OTU2e0/2/0/2/4                         NONE      ODU2e0/2/0/12/2/4                              100
OTU20/2/0/4/3                         NONE      ODU20/2/0/12/4/3                              100
OTU20/2/0/4/4                         NONE      ODU20/2/0/12/4/4                              100
TenGigECtrlr0/2/0/2/3           ODU2E0/2/0/12/2/3             NONE                            100
TenGigECtrlr0/2/0/4/1           ODU2E0/2/0/12/4/1             NONE                            100
TenGigECtrlr0/2/0/4/2           ODU2E0/2/0/12/4/2             NONE                            100
TenGigECtrlr0/2/0/5/1           ODU2E0/2/0/12/5/1             NONE                            100
TenGigECtrlr0/2/0/5/2           ODU2E0/2/0/12/5/2             NONE                            100
TenGigECtrlr0/2/0/5/3           ODU2E0/2/0/12/5/3             NONE                            100
TenGigECtrlr0/2/0/5/4           ODU2E0/2/0/12/5/4             NONE                            100
HundredGigECtrlr0/2/0/0         ODU40/2/0/12/0        NONE                            100 

RP/0/RP0/CPU0:ios#show lc-module location 0/2 lcmode 
Sun Jul 25 15:28:16.324 UTC

Node    Lcmode_Supported    Owner    Running                         Configured
--------------------------------------------------------------------------------
0/2                      Yes                 CLI      40x10G-4x100G-MXP      40x10G-4x100G-MXP

The OTN-XP card is fully configured in hybrid muxponder mode, combining 10x10G and 2x100G clients on slice 0 onto a 300G CFP2 DCO trunk port.

Configure the hybrid muxponder mode for 10x10G + 1x100G over 200G

Configure the OTN-XP card with a combination of 10x10G and 1x100G client ports per slice, multiplexed over a single 200G CFP2 DCO trunk.

Table 11. Feature History

Feature Name

Release Information

Description

10x10G + 1x100G Hybrid Mode for OTN-XP Card

Cisco IOS XR Release 7.7.1

A new hybrid mode 10x10G + 1x100G over 200G trunk rate is introduced for OTN-XP card. This mode is configurable on both slice 1 and slice 0. This feature provides you the flexibility to choose a combination of 10G and 100G client rates simultaneously on both slices of the OTN-XP card.

Follow these steps to configure hybrid muxponder mode on OTN-XP:

Procedure

1.

Run the configure hw-module location location mxponder-slicemxponder-slice-number trunk-rate 200Gclient-port-rate client-port-number client-type {100GE | OTU4} client-port-rate client-port-number lane lane-number client-type {10GE | 100GE} command to configure the OTN-XP card in the 10 x 10G and 1 x 100G muxponder mode.

Example:

This is a sample in which the OTN-XP card is configured with 200G trunk rate on the mxponder-slice 0 mode.


RP/0/RP0/CPU0:ios#config
Tue Apr 22 10:51:44.460 UTC
RP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder-slice 0
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#trunk-rate 200G
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 0 client-type 100GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 lane 2 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 lane 3 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 lane 4 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 5 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 5 lane 2 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 5 lane 3 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 5 lane 4 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 2 lane 3 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 2 lane 4 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#commit

Example:

This is a sample in which the OTN-XP card is configured with 200G trunk rate on the mxponder-slice 1 mode.


RP/0/RP0/CPU0:ios#config
Tue Apr 22 11:01:44:55.250 UTC
RP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder-slice 1
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#trunk-rate 200G
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 1 client-type 100GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 6 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 6 lane 2 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 6 lane 3 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 6 lane 4 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 7 lane 1 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 7 lane 2 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 7 lane 3 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 7 lane 4 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 11 lane 3 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 11 lane 4 client-type 10GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#commit
2.

Run the show hw-module location command to verify the 10 x 10G and 1 x 100G muxponder configuration in the OTN-XP card.

Example:


RRP/0/RP0/CPU0:ios#sh hw-module location 0/2 mxponder-slice 0
Fri Jun 17 15:55:43.520 UTC

Location:             0/2
Slice ID:             0
Client Bitrate:       MIXED
Trunk  Bitrate:       200G
Status:               Provisioned
LLDP Drop Enabled:    FALSE
ARP Snoop Enabled:    FALSE
Client Port                     Mapper/Trunk Port          CoherentDSP0/2/0/12  
                                Traffic Split Percentage

TenGigECtrlr0/2/0/2/3           ODU2E0/2/0/12/2/3                             100
TenGigECtrlr0/2/0/2/4           ODU2E0/2/0/12/2/4                             100
TenGigECtrlr0/2/0/4/1           ODU2E0/2/0/12/4/1                             100
TenGigECtrlr0/2/0/4/2           ODU2E0/2/0/12/4/2                             100
TenGigECtrlr0/2/0/4/3           ODU2E0/2/0/12/4/3                             100
TenGigECtrlr0/2/0/4/4           ODU2E0/2/0/12/4/4                             100
TenGigECtrlr0/2/0/5/1           ODU2E0/2/0/12/5/1                             100
TenGigECtrlr0/2/0/5/2           ODU2E0/2/0/12/5/2                             100
TenGigECtrlr0/2/0/5/3           ODU2E0/2/0/12/5/3                             100
TenGigECtrlr0/2/0/5/4           ODU2E0/2/0/12/5/4                             100
HundredGigECtrlr0/2/0/0         ODU40/2/0/12/0                        100

RP/0/RP0/CPU0:ios#

The OTN-XP card is successfully configured in hybrid muxponder mode, supporting 10x10G and 1x100G client ports per slice, multiplexed over a 200G CFP2 DCO trunk.

Configure the muxponder mode for 200G muxponder

Enable high-rate transmission on the OTN-XP card by configuring it for 200G muxponder operation.

Table 12. Feature History

Feature Name

Release Information

Description

Muxponder Configuration for 200G Trunk with QPSK and 8QAM Modulation

Cisco IOS XR Release 7.3.2

The OTN-XP card supports up to 200G trunk rate with QPSK and 8QAM modulation using CFP2. This feature enhances the signal reachability with reduced noise and can support the 50GHz network.

Commands modified:

  • hw-module (OTN-XP Card)
Follow these steps to configure the OTN-XP card for 200G muxponder mode:

Procedure

1.

Run the configure hw-module location location mxponder-slice mxponder-slice-number trunk-rate 200G to configure the OTN-XP card in the 200G muxponder mode.

Example:

This is a sample configuration of 200G trunk rate on the mxponder-slice 0 mode for OTN-XP card:


RP/0/RP0/CPU0:ios#config
Wed Jun  2 17:17:59.409 UTC
RP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder-slice 0
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#trunk-rate 200G
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 7 client-type 100GE 
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 10 client-type 100GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#commit

This is a sample configuration of 200G trunk rate on the mxponder-slice 1 mode for OTN-XP card:


RP/0/RP0/CPU0:ios#config
Wed Jun  2 17:17:59.409 UTC
RP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder-slice 1
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#trunk-rate 200G
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 5 client-type 100GE 
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 8 client-type 100GE
2.

Run the commit command to save and apply the 200G muxponder configuration.

Example:

RP/0/RP0/CPU0:ios(config-hwmod-mxp)#commit
3.

Run the show hw-module location command to verify the supported client rates for each trunk rate configured in muxponder slice 0 and slice 1.

Example:

This is the sample output for verifying the supported client rates for each trunk rate configured in muxponder slice 0:


RP/0/RP0/CPU0:ios#show hw-module location 0/1 xponder-capabilities mxponder-slice 0
Wed Jun  2 17:02:33.088 UTC

Location: 0/1

Trunk-Port(s): 12

Port Group Restrictions:
Shared-Client-Group-Bandwidth    Shared-Group-Client-Ports
     400G                          1, 6, 7, 10

Trunk-bandwidth: 400G
Client-port                       Supported client rates
     1                             OTU4, 100GE
     6                             OTU4, 100GE
     7                             OTU4, 100GE
     10                            OTU4, 100GE, 400GE

Trunk-bandwidth: 300G
Client-port                       Supported client rates
     6                             OTU4, 100GE
     7                             OTU4, 100GE
     10                            OTU4, 100GE

Trunk-bandwidth: 200G
Client-port                       Supported client rates
     7                             OTU4, 100GE
     10                            OTU4, 100GE

This is the sample output for verifying the supported client rates for each trunk rate configured in muxponder slice 1:


RP/0/RP0/CPU0:ios#show hw-module location 0/1 xponder-capabilities mxponder-slice 1
Wed Jun  2 17:02:50.133 UTC
Location: 0/1
Trunk-Port(s): 13
Port Group Restrictions:
Shared-Client-Group-Bandwidth    Shared-Group-Client-Ports
     400G                          0, 4, 5, 8
Trunk-bandwidth: 400G
Client-port                       Supported client rates
     0                             OTU4, 100GE
     4                             OTU4, 100GE
     5                             OTU4, 100GE
     8                             OTU4, 100GE, 400GE

Trunk-bandwidth: 300G
Client-port                       Supported client rates
     4                             OTU4, 100GE
     5                             OTU4, 100GE
     8                             OTU4, 100GE

Trunk-bandwidth: 200G
Client-port                       Supported client rates
     5                             OTU4, 100GE
     8                             OTU4, 100GE

The OTN-XP card is successfully configured in 200G muxponder mode. Each slice maps two 100GE client ports to a 200G CFP2 DCO trunk port, enabling high-capacity transmission.

Configure the 8QAM modulation for 200G muxponder mode

Change the modulation format on the DP04CFP2 module from QPSK to 8QAM for 200G muxponder mode.

By default, QPSK modulation is used when you configure the 200G trunk rate. The DP04CFP2 coherent pluggable module supports multiple operating modes for 200G muxponder operations

This table lists the supported operating modes on the DP04CFP2 coherent pluggable module.

Table 13. DP04CFP2 supported modes

Network configuration mode

Client type

Trunk rate

Data path

Line framing

FEC type

Modulation format

BPS

Baud rate (GBd)

Pulse shaping

Mode sype

200G-FOIC2-oFEC-QPSK-1-S (Default mode)

2xFOIC1.2

200G

FlexO Str

FlexO-2

oFEC

QPSK

2

63.1

1

Standard

200G-FOIC2-oFEC-8QAM-1-E

2xFOIC1.2

200G

FlexO Str

FlexO-2

oFEC

8QAM

3

42.1

1

Enhanced

Procedure

1.

Run the configure controller optics Rack/Slot/Instance/Port bits-per-symbol commands to change the modulation format to 8QAM.

Example:

This is a sample in which 8QAM modulation is configured.


RP/0/RP0/CPU0:ios#config
Wed Jun  2 17:21:59.409 UTC
RP/0/RP0/CPU0:ios(config)#controller optics0/1/0/12 bits-per-symbol 3
2.

Run the commit command to save and apply the 8QAM modulation configuration.

Example:

RP/0/RP0/CPU0:ios(config-optics)#commit
3.

Run the show controllers optics command to verify the modulation configuration.

Example:


RP/0/RP0/CPU0:ios#show controllers optics 0/1/0/12 
Wed Jun  2 17:17:29.652 UTC
 Controller State: Up 
 Transport Admin State: In Service 
 Laser State: On 
 LED State: Green 
 
 Optics Status 

         Optics Type:  <Unknown> DWDM
         DWDM carrier Info: C BAND, MSA ITU Channel=61, Frequency=193.10THz,
         Wavelength=1552.524nm 

         Alarm Status:
         -------------
         Detected Alarms: None

         LOS/LOL/Fault Status:

         Alarm Statistics:
          
         -------------
         HIGH-RX-PWR = 0            LOW-RX-PWR = 1          
         HIGH-TX-PWR = 0            LOW-TX-PWR = 1          
         HIGH-LBC = 0               HIGH-DGD = 0          
         OOR-CD = 0                 OSNR = 1          
         WVL-OOL = 0                MEA  = 0          
         IMPROPER-REM = 0          
         TX-POWER-PROV-MISMATCH = 0          
         Laser Bias Current = 0.0 %
         Actual TX Power = 0.97 dBm 
         RX Power = 1.47 dBm 
         RX Signal Power = 17.67 dBm 
         Frequency Offset = 82 MHz 
         Performance Monitoring: Enable 
         THRESHOLD VALUES
         ----------------

         Parameter                 High Alarm  Low Alarm  High Warning  Low Warning
         ------------------------  ----------  ---------  ------------  -----------
         Rx Power Threshold(dBm)          3.0      -31.5           0.0          0.0
         Tx Power Threshold(dBm)          3.0      -12.0           0.0          0.0
         LBC Threshold(mA)                N/A        N/A          0.00         0.00
         LBC High Threshold = 90 % 
         Configured Tx Power = 1.00 dBm 
         Configured CD High Threshold = 96000 ps/nm 
         Configured CD lower Threshold = -96000 ps/nm 
         Configured OSNR lower Threshold = 13.70 dB 
         Configured DGD Higher Threshold = 67.00 ps 
         Baud Rate =  42.2082633972 GBd
         Bits per Symbol = 3.0000000000  bits/symbol 
         Modulation Type: 8QAM 
         Chromatic Dispersion 2 ps/nm 
         Configured CD-MIN -48000 ps/nm  CD-MAX 48000 ps/nm 
         Polarization Mode Dispersion = 0.0 ps 
         Second Order Polarization Mode Dispersion = 72.00 ps^2 
         Optical Signal to Noise Ratio = 34.10 dB 
         SNR = 18.40 dB 
         Polarization Dependent Loss = 1.20 dB 
         Polarization Change Rate = 0.00 rad/s 
         Differential Group Delay = 2.00 ps 
 Transceiver Vendor Details
          
         Form Factor            : Not set
         Fiber Connector Type: Not Set 
         Otn Application Code: Not Set 
         Sonet Application Code: Not Set 
         Ethernet Compliance Code: Not set 
 Transceiver Temperature : 46 Celsius
 
 AINS Soak                : None 
 AINS Timer               : 0h, 0m
 AINS remaining time      : 0 seconds

The optics controller is configured with 8QAM modulation.

Muxponder modes for 4x100GE-MXP-DD

A 4x100GE-MXP-DD muxponder mode is an operating configuration on the OTN-XP card that

  • uses QSFP-DD ZRP pluggables on trunk ports 9 and 11 for 400G trunk transmission,

  • supports 4x100GE, 3x100GE, 2x100GE client rates (from Release 7.5.1) and 400GE transponder (400GE-TXP-DD) mode, and

  • applies port group restrictions for client port mapping that limit which ports can carry traffic together.

Table 14. Feature History

Feature Name

Release Information

Description

4X100GE MXP modes with QDD ZRP for OTN-XP Card

Cisco IOS XR Release 7.3.2

On the OTN-XP card, you can configure a single 4x100GE payload that isreceived over the client port as a 400GE signal over DWDM on the line side.

The card improves efficiency, performance, and flexibility for customer networksallowing 4x100GE client transport over 400GE WDM wavelength.

From Release 7.3.2 , you can configure the 4x100GE-MXP-DD muxponder mode on the OTN-XP card.

Restrictions for port group mapping

This topic provides the port group mapping restrictions for the 4x100GE-MXP-DD mode on the OTN-XP card, defining which client ports can be active simultaneously in each muxponder slice.

This table explains about the port mapping when the mxponder-slice 0 is at the near end and is connected to the mxponder-slice 1 at the far end:

Table 15. Port goup mapping for Shared-Client-Group-Bandwidth

Slice configuration - client port

Shared-client-group-bandwidth

Shared-group-client-ports

Slice 0

400G

1, 6, 7, 10

Slice 1

400G

8, 0, 4, 5
Table 16. Port group mapping for trunk-bandwidth

Trunk-bandwidth

Slice configuration - client port

Supported client rates

Client-ports

400G

Slice 0

100G

1, 6, 7, 10

Slice 1

100G

8, 0, 4, 5

300G

Slice 0

100G

6, 7, 10

Slice 1

100G

8, 4, 5

200G

Slice 0

100G

7, 10

Slice 1

100G

4, 5

The traffic flows from the near-end slice-0 to the far-end slice-1 client ports:

  • The port 1 traffic reaches port 8

  • The port 6 traffic reaches port 0

  • The port 7 traffic reaches port 4

  • The port 10 traffic reaches port 5

This table describes the QSFP DD trunk port to the slice-0 client port and slice-1 client port mapping:

Table 17. QSFP DD trunk port to the slice-0 and slice-1 client port mapping

QSFP-DD trunk port

Slice 0 - client port

Slice 1 - client port

0

Port 10

Port 5

1

Port 7

Port 4

2

Port 6

Port 0

3

Port 1

Port 8

Configure the muxponder mode for 4x100GE-MXP-DD

Provision the OTN-XP card in muxponder mode so you can aggregate four 100GE client signals onto a single 400G trunk, enabling efficient high-capacity network transport.

Procedure

1.

Run the configure hw-module location location mxponder-slicemxponder-slice-number trunk-rate 400Gclient-port-rate client-port-number client-type 100GE to configure the OTN-XP card in the 4x100GE-MXP-DD muxponder mode.

Example:

This is a sample in which the OTN-XP card is configured with 400G trunk rate on the mxponder-slice 0 mode.


RP/0/RP0/CPU0:ios#configure 
Tue Jun 15 20:20:17.227 UTC
RP/0/RP0/CPU0:ios(config)#hw-module location 0/0 mxponder-slice 0
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#trunk-rate 400G 
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 1 client-type 100GE 
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 6 client-type 100GE 
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 7 client-type 100GE 
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 10 client-type 100GE 
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#commit
Tue Jun 15 20:20:57.532 UTC
2.

Run the commit command to save and apply the 4x100GE-MXP-DD configuration.
3.

Run the show hw-module location command to verify the 4x100GE-MXP-DD muxponder configuration in the OTN-XP card.

Example:


RP/0/RP0/CPU0:ios#show hw-module location 0/0 mxponder-slice 1
Tue Jun 15 20:23:06.217 UTC

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

HundredGigECtrlr0/0/0/0                  -                            100
HundredGigECtrlr0/0/0/4                  -                            100
HundredGigECtrlr0/0/0/5                  -                            100
HundredGigECtrlr0/0/0/8                  -                            100



RP/0/RP0/CPU0:ios#show hw-module location 0/0 mxponder
Tue Jun 15 20:23:46.650 UTC

Location:             0/0
Slice ID:             0
Client Bitrate:       100GE
Trunk  Bitrate:       400G
Status:               Provisioned
LLDP Drop Enabled:    FALSE
ARP Snoop Enabled:    FALSE
Client Port                     Mapper/Trunk Port          CoherentDSP0/0/0/11  
                                Traffic Split Percentage

HundredGigECtrlr0/0/0/1                  -                            100
HundredGigECtrlr0/0/0/6                  -                            100
HundredGigECtrlr0/0/0/7                  -                            100
HundredGigECtrlr0/0/0/10                 -                            100


Location:             0/0
Slice ID:             1
Client Bitrate:       100GE
Trunk  Bitrate:       400G
Status:               Provisioned
LLDP Drop Enabled:    FALSE
ARP Snoop Enabled:    FALSE
Client Port                     Mapper/Trunk Port          CoherentDSP0/0/0/9   
                                Traffic Split Percentage
          
HundredGigECtrlr0/0/0/0                  -                            100
HundredGigECtrlr0/0/0/4                  -                            100
HundredGigECtrlr0/0/0/5                  -                            100
HundredGigECtrlr0/0/0/8                  -                            100
The OTN-XP card is provisioned in 4x100GE-MXP-DD muxponder mode. All four 100GE client controllers per slice should show “Provisioned” status and appear correctly mapped to QDD ZRP trunk ports.

Configure the muxponder mode for 2x100GE-MXP-DD

Configure OTN-XP cards for 2x100GE-MXP-DD muxponder mode to efficiently transport two 100GE client signals over a single 200GE DWDM wavelength.

Table 18. Feature History

Feature Name

Release Information

Description

2X100GE MXP modes with QDD ZRP for OTN-XP Card

Cisco IOS XR Release 7.5.1

On the OTN-XP card, you can configure two 2x100GE payloads that are received over the client port as a 200GE signal over DWDM on the line side.

The 2x100GE-MXP-DD muxponder mode improves efficiency, performance, and flexibility for customer networks allowing 2x100GE client transport over 200GE WDM wavelength.

From Release 7.5.1, you can configure the 2x100GE-MXP-DD muxponder mode on the OTN-XP card.

Note

The LC mode must be configured to 4x100GE-MXP-DD on the OTN-XP card before you perform this configuration.

Two slices of 2x100GE-MXP-DD can be configured with the same LC mode on the OTN-XP card.

Restrictions on the port group mapping exist when the mxponder-slice 0 is at the near end and is connected to the mxponder-slice 1 at the far end.

Procedure

1.

Run the configure hw-module location location mxponder-slicemxponder-slice-number trunk-rate 200Gclient-port-rate client-port-number client-type 100GE commands to configure the OTN-XP card in the 2x100GE-MXP-DD muxponder mode.

Example:

This is a sample in which the OTN-XP card is configured with 200G trunk rate on the mxponder-slice 1 mode.


RP/0/RP0/CPU0:ios#configure 
Tue Jun 15 20:20:17.227 UTC
RP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder-slice 1
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#trunk-rate 200G
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 client-type 100GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 5 client-type 100GE
2.

Run the commit command to save and apply the 2x100GE-MXP-DD configuration.

Example:

RP/0/RP0/CPU0:ios(config-hwmod-mxp)#commit
3.

Run the show hw-module location command to verify the supported client rates for each trunk rate configured in muxponder slice 0.

Example:

Verifying the supported client rates for each trunk rate

This is the sample output for verifying the supported client rates for each trunk rate configured in muxponder slice 0.


RP/0/RP0/CPU0:ios#show hw-module location 0/0 xponder-capabilities mxponder-slice 0
Fri Jul 23 15:35:43.059 UTC​

Location: 0/0

Trunk-Port(s): 11

Port Group Restrictions:
Shared-Client-Group-Bandwidth    Shared-Group-Client-Ports
     400G                          1, 6, 7, 10

Trunk-bandwidth: 400G
Client-port                       Supported client rates
     1                             100GE
     6                             100GE
     7                             100GE
     10                            100GE

Trunk-bandwidth: 300G
Client-port                       Supported client rates
     6                             100GE
     7                             100GE
     10                            100GE

Trunk-bandwidth: 200G
Client-port                       Supported client rates
     7                             100GE
     10                            100GE

This is the sample output for verifying the supported client rates for each trunk rate configured in muxponder slice 1.


RP/0/RP0/CPU0:ios#show hw-module location 0/0 xponder-capabilities mxponder-slice 1
Wed Sep 15 00:30:47.433 UTC

Location: 0/0

Trunk-Port(s): 9

Port Group Restrictions:
Shared-Client-Group-Bandwidth    Shared-Group-Client-Ports
     400G                          8, 0, 4, 5

Trunk-bandwidth: 400G
Client-port                       Supported client rates
     8                             100GE
     0                             100GE
     4                             100GE
     5                             100GE

Trunk-bandwidth: 300G
Client-port                       Supported client rates
     8                             100GE
     4                             100GE
     5                             100GE

Trunk-bandwidth: 200G
Client-port                       Supported client rates
     4                             100GE
     5                             100GE

Example:

Verifying the running configuration

This is a sample to verify the provisioned slice and client port information for 2x100GE-MXP-DD muxponder configuration in the OTN-XP card.

RP/0/RP0/CPU0:ios#show running config
hw-module location 0/2​
 mxponder-slice 0​
  trunk-rate 200G​
  client-port-rate 1 client-type 100GE​
  client-port-rate 7 client-type 100GE​​
 !​
hw-module location  0/1​
 mxponder-slice 1​
  trunk-rate 200G​
  client-port-rate 4 client-type 100GE​
  client-port-rate 5 client-type 100GE​
 !​
!​

Example:

Verifying the muxponder configuration

This is a sample to verify the 2x100GE-MXP-DD muxponder configuration in the OTN-XP card for mxponder-slice 0.


RP/0/RP0/CPU0:ios#show hw-module location 0/0 mxponder-slice 0​
Fri Jul 23 16:04:42.279 UTC

Location:             0/0
Slice ID:             0
Client Bitrate:       100GE
Trunk  Bitrate:       200G
Status:               Provisioned
LLDP Drop Enabled:    FALSE
ARP Snoop Enabled:    FALSE
Client Port                     Mapper/Trunk Port          CoherentDSP0/0/0/11  
                                Traffic Split Percentage

HundredGigECtrlr0/0/0/7                  -                            100
HundredGigECtrlr0/0/0/10                 -                            100

This is a sample to verify the 2x100GE-MXP-DD muxponder configuration in the OTN-XP card for mxponder-slice 1.


RP/0/RP0/CPU0:ios#show hw-module location 0/0 mxponder-slice 1​
Tue Jun 15 20:21:46.587 UTC

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

HundredGigECtrlr0/0/0/4                  -                            100
HundredGigECtrlr0/0/0/5                  -                            100

The OTN-XP card operates in 2x100GE-MXP-DD muxponder mode, enabling efficient transport of two 100GE client signals per slice over a 200G wavelength.

Configure the muxponder mode for 3x100GE-MXP-DD

Configure the OTN-XP card to operate in 3x100GE-MXP-DD muxponder mode, enabling efficient transport of three 100GE client ports per slice over a 300G QDD ZRP trunk..

Table 19. Feature History

Feature Name

Release Information

Description

3x100GE MXP modes with QDD ZRP for OTN-XP Card

Cisco IOS XR Release 7.5.1

On the OTN-XP card, you can configure two 3x100GE payloads that are received over the client port as a 300GE signal over DWDM on the line side.

The 3x100GE-MXP-DD muxponder mode improves efficiency, performance, and flexibility for customer networks allowing 3x100GE client transport over 300GE WDM wavelength.

From Release 7.5.1, you can configure the 3x100GE-MXP-DD muxponder mode on the OTN-XP card.

Note

The LC mode must be configured to 4x100GE-MXP-DD on the OTN-XP card before you perform this configuration.

Two slices of 3x100GE-MXP-DD can be configured with the same LC mode on the OTN-XP card.

Restrictions on the port group mapping exist when the mxponder-slice 0 is at the near end and is connected to the mxponder-slice 1 at the far end.

Procedure

1.

Run the configure hw-module location location mxponder-slicemxponder-slice-number trunk-rate 300Gclient-port-rate client-port-number client-type 100GE to configure the OTN-XP card in the 3x100GE-MXP-DD muxponder mode.

Example:

This is a sample in which the OTN-XP card is configured with 300G trunk rate on the mxponder-slice 1 mode.


RP/0/RP0/CPU0:ios#configure 
Tue Jun 15 20:20:17.227 UTC
RP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder-slice 1
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#trunk-rate 300G 
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 4 client-type 100GE 
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 5 client-type 100GE 
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 8 client-type 100GE
2.

Run the commit command to save and apply the 3x100GE-MXP-DD configuration.

Example:

RP/0/RP0/CPU0:ios(config-hwmod-mxp)#commit

The output shows 3x100GE client controllers mapped to QDD ZRP trunk ports at 300G per slice.
3.

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

Example:

Verify the supported client rates for each trunk rate

This is the sample output for verifying the supported client rates for each trunk rate configured in muxponder slice 0.


RP/0/RP0/CPU0:ios#show hw-module location 0/0 xponder-capabilities mxponder-slice 0
Fri Jul 23 15:35:43.059 UTC​

Location: 0/0

Trunk-Port(s): 11

Port Group Restrictions:
Shared-Client-Group-Bandwidth    Shared-Group-Client-Ports
     400G                          1, 6, 7, 10

Trunk-bandwidth: 400G
Client-port                       Supported client rates
     1                             100GE
     6                             100GE
     7                             100GE
     10                            100GE

Trunk-bandwidth: 300G
Client-port                       Supported client rates
     6                             100GE
     7                             100GE
     10                            100GE

Trunk-bandwidth: 200G
Client-port                       Supported client rates
     7                             100GE
     10                            100GE

This is the sample output for verifying the supported client rates for each trunk rate configured in muxponder slice 1.


RP/0/RP0/CPU0:ios#show hw-module location 0/0 xponder-capabilities mxponder-slice 1
Wed Sep 15 00:30:47.433 UTC

Location: 0/0

Trunk-Port(s): 9

Port Group Restrictions:
Shared-Client-Group-Bandwidth    Shared-Group-Client-Ports
     400G                          8, 0, 4, 5

Trunk-bandwidth: 400G
Client-port                       Supported client rates
     8                             100GE
     0                             100GE
     4                             100GE
     5                             100GE

Trunk-bandwidth: 300G
Client-port                       Supported client rates
     8                             100GE
     4                             100GE
     5                             100GE

Trunk-bandwidth: 200G
Client-port                       Supported client rates
     4                             100GE
     5                             100GE

Example:

Verifying the running configuration

This is a sample to verify the provisioned slice and client port information for 3x100GE-MXP-DD muxponder configuration in the OTN-XP card.


RP/0/RP0/CPU0:ios#show running config
hw-module location 0/2​
 mxponder-slice 0​
  trunk-rate 300G​
  client-port-rate 1 client-type 100GE​
  client-port-rate 7 client-type 100GE​
  client-port-rate 10 client-type 100GE​
 !​
hw-module location  0/1​
 mxponder-slice 1​
  trunk-rate 300G​
  client-port-rate 4 client-type 100GE​
  client-port-rate 5 client-type 100GE​
  client-port-rate 8 client-type 100GE​
 !​
!​

Example:

Verifying the muxponder configuration

This is a sample to verify the 3x100GE-MXP-DD muxponder configuration in the OTN-XP card for mxponder-slice 0.


RP/0/RP0/CPU0:ios#show hw-module location 0/0 mxponder-slice 0​
Tue Jun 15 20:21:46.587 UTC

Location:             0/0
Slice ID:             0
Client Bitrate:       100GE
Trunk  Bitrate:       300G
Status:               Provisioned
LLDP Drop Enabled:    FALSE
ARP Snoop Enabled:    FALSE
Client Port                     Mapper/Trunk Port          CoherentDSP0/0/0/11  
                                Traffic Split Percentage

HundredGigECtrlr0/0/0/1                  -                            100
HundredGigECtrlr0/0/0/7                  -                            100
HundredGigECtrlr0/0/0/10                 -                            100

This is a sample to verify the 3x100GE-MXP-DD muxponder configuration in the OTN-XP card for mxponder-slice 1.


RP/0/RP0/CPU0:ios#show hw-module location 0/0 mxponder-slice 1​
Tue Jun 15 20:21:46.587 UTC

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

HundredGigECtrlr0/0/0/8                  -                            100
HundredGigECtrlr0/0/0/4                  -                            100
HundredGigECtrlr0/0/0/5                  -                            100

The OTN-XP card is configured in 3x100GE-MXP-DD muxponder mode, with three 100GE client ports per slice mapped to QDD ZRP trunk ports at a 300G trunk rate.

Configure the muxponder mode for 400GE-TXP-DD

Set up the OTN-XP card to operate in 400GE-TXP-DD muxponder mode, enabling efficient transport of 400GE client traffic over DWDM on the line side.

Table 20. Feature History

Feature Name

Release Information

Description

400GE TXP mode with QDD ZRP for OTN-XP Card

Cisco IOS XR Release 7.5.1

On the OTN-XP card, you can configure two 400GE payloads that are received over the client port as a 400GE signal over DWDM on the line side.

The 400GE-TXP-DD muxponder mode improves efficiency, performance, and flexibility for customer networks allowing 400GE client transport over 400GE WDM wavelength.

From Release 7.5.1, you can configure the 400GE-TXP-DD transponder mode on the OTN-XP card.

Note

The LC mode must be configured to 400GE-TXP-DD on the OTN-XP card before you perform this configuration.

Two slices of 400GE-TXP-DD can be configured with the same LC mode on the OTN-XP card.

Restrictions on the port group mapping exist when the mxponder-slice 0 is at the near end and is connected to the mxponder-slice 1 at the far end.

Follow these steps to configure the muxponder mode for a 400GE-TXP-DD card:

Procedure

1.

Run the configure hw-module location location mxponder-slicemxponder-slice-number trunk-rate 400Gclient-port-rate client-port-number client-type 100GE to configure the OTN-XP card in the 400GE-TXP-DD transponder mode.

Example:

This is a sample in which the OTN-XP card is configured with 400G trunk rate on the mxponder-slice 1 mode.


RP/0/RP0/CPU0:ios#configure 
Tue Jun 15 20:20:17.227 UTC
RP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder-slice 1
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#trunk-rate 400G
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#client-port-rate 8 client-type 400GE
RP/0/RP0/CPU0:ios(config-hwmod-mxp)#commit
Tue Jun 15 20:20:57.532 UTC
2.

Run the commit command to save and apply the 400GE-TXP-DD configuration.

Example:

RP/0/RP0/CPU0:ios(config-hwmod-mxp)#commit
3.

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

Example:

Verify the supported client rates for each trunk rate

This is the sample output for verifying the supported client rates for each trunk rate configured in muxponder slice 0.


RP/0/RP0/CPU0:ios#show hw-module location 0/0 xponder-capabilities mxponder-slice 0
Wed Oct 27 16:14:35.693 UTC​

Location: 0/0

Trunk-Port(s): 11

Port Group Restrictions:
Shared-Client-Group-Bandwidth    Shared-Group-Client-Ports
     400G                          10

Trunk-bandwidth: 400G
Client-port                       Supported client rates
     10                            100GE

This is the sample output for verifying the supported client rates for each trunk rate configured in muxponder slice 1.

RP/0/RP0/CPU0:ios#show hw-module location 0/0 xponder-capabilities mxponder-slice 1
Wed Oct 27 16:16:37.524 UTC

Location: 0/0

Trunk-Port(s): 9

Port Group Restrictions:
Shared-Client-Group-Bandwidth    Shared-Group-Client-Ports
     400G                          8

Trunk-bandwidth: 400G
Client-port                       Supported client rates
     8                             400GE

Example:

Verify the running configuration

This is a sample to verify the provisioned slice and client port information for 400GE-TXP-DD transponder configuration in the OTN-XP card.


RP/0/RP0/CPU0:ios#show running config
hw-module location 0/0​
 mxponder-slice 0​
  trunk-rate 400G​
  client-port-rate 10 client-type 100GE
 !​
hw-module location  0/0​
 mxponder-slice 1​
  trunk-rate 400G​
  client-port-rate 8 client-type 100GE​
 !​
!​

Example:

Verify the muxponder configuration

Example:

This is a sample to verify the 400GE-TXP-DD transponder configuration in the OTN-XP card for mxponder-slice 0.


RP/0/RP0/CPU0:ios#show hw-module location 0/0 mxponder-slice 0​
Fri Jul 23 16:04:42.279 UTC

Location:             0/0
Slice ID:             0
Client Bitrate:       400GE
Trunk  Bitrate:       400G
Status:               Provisioned
LLDP Drop Enabled:    FALSE
ARP Snoop Enabled:    FALSE
Client Port                     Mapper/Trunk Port          CoherentDSP0/0/0/11  
                                Traffic Split Percentage

HundredGigECtrlr0/0/0/1                  -                            100
HundredGigECtrlr0/0/0/6                  -                            100
HundredGigECtrlr0/0/0/7                  -                            100
HundredGigECtrlr0/0/0/10                 -                            100

This is a sample to verify the 400GE-TXP-DD transponder configuration in the OTN-XP card for mxponder-slice 1.


RP/0/RP0/CPU0:ios#show hw-module location 0/0 mxponder-slice 1​
Tue Jun 15 20:21:46.587 UTC

Location:             0/0
Slice ID:             1
Client Bitrate:       400GE
Trunk  Bitrate:       400G
Status:               Provisioned
LLDP Drop Enabled:    FALSE
ARP Snoop Enabled:    FALSE
Client Port                     Mapper/Trunk Port          CoherentDSP0/0/0/9  
                                Traffic Split Percentage

HundredGigECtrlr0/0/0/8                  -                            100
HundredGigECtrlr0/0/0/0                  -                            100
HundredGigECtrlr0/0/0/4                  -                            100
HundredGigECtrlr0/0/0/5                  -                            100

Example:

Verify the client ethernet controller status​

This is a sample to verify the Client Ethernet Controller Status​ of the 400GE-TXP-DD transponder configuration in the OTN-XP card.


P/0/RP0/CPU0:ios#show controller hundredGigECtrlr 0/0/0/1​
Fri Jul 23 16:07:11.541 UTC​
Operational data for interface HundredGigECtrlr0/0/0/1:​
​State:​
    Administrative state: enabled​
    Operational state: Up​
    LED state: Green On​
    Maintenance: Disabled​
    AINS Soak: None​
      Total Duration: 0 hour(s) 0 minute(s)​
      Remaining Duration: 0 hour(s) 0 minute(s) 0 second(s)​
    Laser Squelch: Disabled​
​Phy:​
    Media type: Not known​

Autonegotiation disabled.​
​
Operational values:​
    Speed: 100Gbps​
    Duplex: Full Duplex​
    Flowcontrol: None​
    Loopback: None (or external)​
    BER monitoring:​
        Not supported​
    Holdoff Time: 0ms​

The OTN-XP card operates in 400GE-TXP-DD transponder mode. Each slice maps a single 400GE client port to a 400G QDD ZRP trunk port.