cisco - global home page - configuring the card mode · trunkpayload fec minbps maxbps mingbd...

8
Configuring the Card Mode This chapter lists the supported configurations and the procedures to configure the card mode on the line cards. 1.2T and 1.2TL Line Cards, on page 1 OTN-XP Card, on page 7 1.2T and 1.2TL Line Cards The following section describes the supported configurations and procedures to configure the card modes on the line cards. Card Modes The line cards support module and slice configurations. The line cards have two trunk ports (0 and 1) and 12 client ports (2 through 13) each. You can configure the line card in two modes: • Muxponder—In this mode, both trunk ports are configured with the same trunk rate. The client-to-trunk mapping is in a sequence. • Muxponder slice—In this mode, each trunk port is configured independent of the other with different trunk rates. The client-to-trunk mapping is fixed. For Trunk 0, the client ports are 2 through 7. For Trunk 1, the client ports are 8 through 13. Supported Data Rates The following data rates are supported on the line card. . LLDP drop, L1 encryption, and AINS are not supported on the OTU4 configuration. The following table displays the client and trunk ports that are enabled for the muxponder configuration. Client Ports Trunk Ports Client Data Rate (100GE, OTU4) Card Support Trunk Data Rate 2, 3, 4, 5 0, 1 100GE, OTU4 1.2T 200 Configuring the Card Mode 1

Upload: others

Post on 14-Mar-2021

3 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Cisco - Global Home Page - Configuring the Card Mode · TrunkPayload FEC MinBPS MaxBPS MinGBd MaxGBd 400G 27% 3.8671875 6 46.2900663 71.8197392 500G 27% 4.8281250 6 57.8625828 71.9068991

Configuring the Card Mode

This chapter lists the supported configurations and the procedures to configure the card mode on the linecards.

• 1.2T and 1.2TL Line Cards, on page 1• OTN-XP Card, on page 7

1.2T and 1.2TL Line CardsThe following section describes the supported configurations and procedures to configure the card modes onthe line cards.

Card ModesThe line cards support module and slice configurations.

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

• Muxponder—In this mode, both trunk ports are configured with the same trunk rate. The client-to-trunkmapping is in a sequence.

• Muxponder slice—In this mode, each trunk port is configured independent of the other with differenttrunk rates. The client-to-trunk mapping is fixed. For Trunk 0, the client ports are 2 through 7. For Trunk1, the client ports are 8 through 13.

Supported Data RatesThe following data rates are supported on the line card.

. LLDP drop, L1 encryption, and AINS are not supported on the OTU4 configuration.

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

Client PortsTrunk PortsClient Data Rate(100GE, OTU4)

Card SupportTrunk Data Rate

2, 3, 4, 50, 1100GE, OTU41.2T200

Configuring the Card Mode1

Page 2: Cisco - Global Home Page - Configuring the Card Mode · TrunkPayload FEC MinBPS MaxBPS MinGBd MaxGBd 400G 27% 3.8671875 6 46.2900663 71.8197392 500G 27% 4.8281250 6 57.8625828 71.9068991

Client PortsTrunk PortsClient Data Rate(100GE, OTU4)

Card SupportTrunk Data Rate

2, 3, 4, 5, 6, 70, 1100GE, OTU41.2T300

2, 3, 4, 5, 6, 7, 8, 90, 1100GE1.2T400

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

0, 1100GE1.2T500

2, 3, 4, 5, 6, 7, 8, 9,10, 11, 12, 13

0, 1100GE1.2T600

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

Client PortsTrunk PortsClient Data RateCard SupportTrunk Data Rate

201.2T100

2, 301.2T200

2, 3, 401.2T300

2, 3, 4, 501.2T400

2, 3, 4, 5, 601.2T500

2, 3, 4, 5, 6, 701.2T600

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

Client PortsTrunk PortsClient Data RateCard SupportTrunk Data Rate

811.2T100

8, 911.2T200

8, 9, 1011.2T300

8, 9, 10, 1111.2T400

8, 9, 10, 11, 1211.2T500

8, 9, 10, 11, 12, 1311.2T600

All configurations can be accomplished by using appropriate values for client bitrate and trunk bitrate parametersof the hw-module command.

The following table displays the trunk parameter ranges for the 1.2T card.

Max GBdMin GBdMax BPSMin BPSFECTrunk Payload

69.4331.514.40625227%200G

71.868135234.717549762.898437527%300G

Configuring the Card Mode2

Configuring the Card ModeSupported Data Rates

Page 3: Cisco - Global Home Page - Configuring the Card Mode · TrunkPayload FEC MinBPS MaxBPS MinGBd MaxGBd 400G 27% 3.8671875 6 46.2900663 71.8197392 500G 27% 4.8281250 6 57.8625828 71.9068991

Max GBdMin GBdMax BPSMin BPSFECTrunk Payload

71.819739246.290066363.867187527%400G

71.906899157.862582864.828125027%500G

71.9552971--5.257812515%600G

To configure the BPS, see Configuring the BPS, on page 6.

Configuring the Card ModeYou can configure the line card in the module (muxponder) or slice configuration (muxponder slice).

To configure the card in the muxponder mode, use the following commands.

configure

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

hw-module location location mxponder trunk-rate {200G | 300G | 400G | 500G | 600G }

commit

To configure the card in the muxponder slice mode, use the following commands.

configure

hw-module location location mxponder-slice mxponder-slice-number client-rate 100GE

hw-module location location mxponder-slice trunk-rate { 200G | 300G | 400G | 500G | 600G }

commit

Examples

The following is a sample in which the card is configured in the muxponder mode with a 500G trunk payload.

RP/0/RP0/CPU0:ios#configSun Feb 24 14:09:33.989 UTCRP/0/RP0/CPU0:ios(config)#hw-module location 0/2 mxponder client-rate OTU4RP/0/RP0/CPU0:ios(config)#hw-module location 0/2 mxponder trunk-rate 500GRP/0/RP0/CPU0:ios(config)#commit

The following is a sample in which the card is configured in the muxponder slice 0 mode with a 500G trunkpayload.

RP/0/RP0/CPU0:ios#configRP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder-slice 0 client-rate 100GERP/0/RP0/CPU0:ios(config)#hw-module location 0/1 mxponder-slice 0 trunk-rate 500GRP/0/RP0/CPU0:ios(config)#commit

The following is a sample in which the card is configured in the muxponder slice 1 mode with a 400G trunkpayload.

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

Configuring the Card Mode3

Configuring the Card ModeConfiguring the Card Mode

Page 4: Cisco - Global Home Page - Configuring the Card Mode · TrunkPayload FEC MinBPS MaxBPS MinGBd MaxGBd 400G 27% 3.8671875 6 46.2900663 71.8197392 500G 27% 4.8281250 6 57.8625828 71.9068991

Verifying the Card Configuration

RP/0/RP0/CPU0:ios#show hw-module location 0/2 mxponderFri Mar 15 11:48:48.344 IST

Location: 0/2Client Bitrate: 100GETrunk Bitrate: 500GStatus: ProvisionedLLDP Drop Enabled: FALSEClient Port Mapper/Trunk Port CoherentDSP0/2/0/0 CoherentDSP0/2/0/1

Traffic Split Percentage

HundredGigECtrlr0/2/0/2 ODU40/2/0/0/1 100 0HundredGigECtrlr0/2/0/3 ODU40/2/0/0/2 100 0HundredGigECtrlr0/2/0/4 ODU40/2/0/0/3 100 0HundredGigECtrlr0/2/0/5 ODU40/2/0/0/4 100 0HundredGigECtrlr0/2/0/6 ODU40/2/0/0/5 100 0HundredGigECtrlr0/2/0/7 ODU40/2/0/1/1 0 100HundredGigECtrlr0/2/0/8 ODU40/2/0/1/2 0 100HundredGigECtrlr0/2/0/9 ODU40/2/0/1/3 0 100HundredGigECtrlr0/2/0/10 ODU40/2/0/1/4 0 100HundredGigECtrlr0/2/0/11 ODU40/2/0/1/5 0 100

The following is a sample ouput of all the muxponder slice 0 configurations.

RP/0/RP0/CPU0:ios#show hw-module location 0/1 mxponder-slice 0Fri Mar 15 06:04:18.348 UTC

Location: 0/1Slice ID: 0Client Bitrate: 100GETrunk Bitrate: 500GStatus: ProvisionedLLDP Drop Enabled: FALSEClient Port Mapper/Trunk Port CoherentDSP0/1/0/0

Traffic Split Percentage

HundredGigECtrlr0/1/0/2 ODU40/1/0/0/1 100HundredGigECtrlr0/1/0/3 ODU40/1/0/0/2 100HundredGigECtrlr0/1/0/4 ODU40/1/0/0/3 100HundredGigECtrlr0/1/0/5 ODU40/1/0/0/4 100HundredGigECtrlr0/1/0/6 ODU40/1/0/0/5 100

The following is a sample ouput of all the muxponder slice 1 configurations.

RP/0/RP0/CPU0:ios#show hw-module location 0/1 mxponder-slice 1Fri Mar 15 06:11:50.020 UTC

Location: 0/1Slice ID: 1Client Bitrate: 100GETrunk Bitrate: 400GStatus: ProvisionedLLDP Drop Enabled: TRUEClient Port Mapper/Trunk Port CoherentDSP0/1/0/1

Traffic Split Percentage

HundredGigECtrlr0/1/0/8 ODU40/1/0/1/1 100HundredGigECtrlr0/1/0/9 ODU40/1/0/1/2 100HundredGigECtrlr0/1/0/10 ODU40/1/0/1/3 100HundredGigECtrlr0/1/0/11 ODU40/1/0/1/4 100

Configuring the Card Mode4

Configuring the Card ModeConfiguring the Card Mode

Page 5: Cisco - Global Home Page - Configuring the Card Mode · TrunkPayload FEC MinBPS MaxBPS MinGBd MaxGBd 400G 27% 3.8671875 6 46.2900663 71.8197392 500G 27% 4.8281250 6 57.8625828 71.9068991

The following is a sample ouput of the muxponder slice 1 configuration with client configured as OTU4.RP/0/RP0/CPU0:ios#sh hw-module location 0/0 mxponder-slice 1

Wed Mar 11 13:59:11.073 UTC

Location: 0/0Slice ID: 1Client Bitrate: OTU4Trunk Bitrate: 200GStatus: ProvisionedClient Port Peer/Trunk Port CoherentDSP0/0/0/1

Traffic Split PercentageOTU40/0/0/8 ODU40/0/0/1/1 100OTU40/0/0/9 ODU40/0/0/1/2 100

Use the following command to clear alarm statistics on the optics or coherent DSP controller.

clear counters controller controllertype R/S/I/P

The following is a sample in which the alarm statistics are cleared on the coherent DSP controller.

RP/0/RP0/CPU0:ios#show controller coherentDSP 0/1/0/0Tue Jun 11 05:15:12.540 UTC

Port : CoherentDSP 0/1/0/0Controller State : UpInherited Secondary State : NormalConfigured Secondary State : NormalDerived State : In ServiceLoopback mode : NoneBER Thresholds : SF = 1.0E-5 SD = 1.0E-7Performance Monitoring : Enable

Alarm Information:LOS = 1 LOF = 1 LOM = 0OOF = 1 OOM = 1 AIS = 0IAE = 0 BIAE = 0 SF_BER = 0SD_BER = 2 BDI = 2 TIM = 0FECMISMATCH = 0 FEC-UNC = 0Detected Alarms : None

Bit Error Rate InformationPREFEC BER : 8.8E-03POSTFEC BER : 0.0E+00

TTI :Remote hostname : P2B8Remote interface : CoherentDSP 0/1/0/0Remote IP addr : 0.0.0.0

FEC mode : Soft-Decision 15

AINS Soak : NoneAINS Timer : 0h, 0mAINS remaining time : 0 secondsRP/0/RP0/CPU0:ios#clear counters controller coherentDSP 0/1/0/0Tue Jun 11 05:17:07.271 UTCAll counters are clearedRP/0/RP0/CPU0:ios#show controllers coherentDSP 0/1/0/1Tue Jun 11 05:20:55.199 UTC

Port : CoherentDSP 0/1/0/1Controller State : Up

Configuring the Card Mode5

Configuring the Card ModeConfiguring the Card Mode

Page 6: Cisco - Global Home Page - Configuring the Card Mode · TrunkPayload FEC MinBPS MaxBPS MinGBd MaxGBd 400G 27% 3.8671875 6 46.2900663 71.8197392 500G 27% 4.8281250 6 57.8625828 71.9068991

Inherited Secondary State : NormalConfigured Secondary State : NormalDerived State : In ServiceLoopback mode : NoneBER Thresholds : SF = 1.0E-5 SD = 1.0E-7Performance Monitoring : Enable

Alarm Information:LOS = 0 LOF = 0 LOM = 0OOF = 0 OOM = 0 AIS = 0IAE = 0 BIAE = 0 SF_BER = 0SD_BER = 0 BDI = 0 TIM = 0FECMISMATCH = 0 FEC-UNC = 0Detected Alarms : None

Bit Error Rate InformationPREFEC BER : 1.2E-02POSTFEC BER : 0.0E+00

TTI :Remote hostname : P2B8Remote interface : CoherentDSP 0/1/0/1Remote IP addr : 0.0.0.0

FEC mode : Soft-Decision 15

AINS Soak : NoneAINS Timer : 0h, 0mAINS remaining time : 0 seconds

Configuring the BPSYou can configure the Bits per Symbol (BPS) to 3.4375 to support 300G trunk configurations on 75 GHznetworks using the following commands:

configure

controller optics R/S/I/P bits-per-symbol 3.4375

commit

The following is a sample in which the BPS is configured to 3.4375.

RP/0/RP0/CPU0:ios#configureWed Mar 27 14:12:49.932 UTCRP/0/RP0/CPU0:ios(config)#controller optics 0/3/0/0 bits-per-symbol 3.4375RP/0/RP0/CPU0:ios(config)#commit

Viewing BPS and Baud Rate Ranges

To view the the BPS for a specific range use the following command:

show controller optics R/S/I/P bps-range bps-range | include data-rate | include fec-type

RP/0/RP0/CPU0:ios#show controllers optics 0/3/0/0 bps-range 3 3.05 | include 300G | includeSD27Thu Mar 28 03:01:39.751 UTC300G SD27 3.0000000 69.4350994300G SD27 3.0078125 69.2547485300G SD27 3.0156250 69.0753320300G SD27 3.0234375 68.8968428300G SD27 3.0312500 68.7192736

Configuring the Card Mode6

Configuring the Card ModeConfiguring the BPS

Page 7: Cisco - Global Home Page - Configuring the Card Mode · TrunkPayload FEC MinBPS MaxBPS MinGBd MaxGBd 400G 27% 3.8671875 6 46.2900663 71.8197392 500G 27% 4.8281250 6 57.8625828 71.9068991

300G SD27 3.0390625 68.5426174300G SD27 3.0468750 68.3668671

To view the baud for a specific range use the following command:

show controller optics R/S/I/P baud-rate-range baud-range | include data-rate | include fec-type

RP/0/RP0/CPU0:ios#show controllers optics 0/3/0/0 baud-rate-range 43 43.4 | include 300G |include SD27Thu Mar 28 03:12:36.521 UTC300G SD27 4.8046875 43.3545986300G SD27 4.8125000 43.2842178300G SD27 4.8203125 43.2140651300G SD27 4.8281250 43.1441394300G SD27 4.8359375 43.0744397300G SD27 4.8437500 43.0049648

OTN-XP CardThe following section describes the supported configurations and procedures to configure the card modes onthe line card.

Configuring the Card Mode7

Configuring the Card ModeOTN-XP Card

Page 8: Cisco - Global Home Page - Configuring the Card Mode · TrunkPayload FEC MinBPS MaxBPS MinGBd MaxGBd 400G 27% 3.8671875 6 46.2900663 71.8197392 500G 27% 4.8281250 6 57.8625828 71.9068991

Configuring the Card Mode8

Configuring the Card ModeOTN-XP Card