Cisco NCS 1002 is a 2Tbps muxponder that addresses the growing bandwidth needs of data center DWDM applications. The muxponder is 2 RU. It provides dense, low power, and cost-optimized DWDM transport for 10G, 40G, and 100G clients. The trunk ports can operate at 100G, 200G, and 250G traffic. NCS 1002 is ROHS6 compliant.

NCS 1002 has four independent slices. A slice is a group of client and trunk ports operating homogeneously. Each slice contains five QSFP+/QFSP28 client optical ports and two CFP2 DWDM trunk ports. Each slice delivers up to 500 Gbps traffic. NCS 1002 has one controller card, two Solid State Disks (SSD), 1+1 redundant 1800W AC power supply modules, and 2+1 redundant fans.

NCS 1002 delivers the following benefits:

• Supports up to 2 Tbps capacity

• Transports 100, 200, or 250Gbps per wavelength on the same platform through software provisioning

• Transports 10 GE, 40 GE, and 100 GE on the same platform through software provisioning

• Supports grid-less tuning for flex-grid dense wavelength-division multiplexing (DWDM)

• Supports different modulation formats (PM-QPSK or PM-16QAM)

• Supports 7% or 20% Soft Decision (SD) FEC for maximum optical performance

• Allows for automated installation, configuration and monitoring

• Supports machine-to-machine (M2M) APIs based on YANG models for ease of configuration

• Supports a telemetry agent for a pub-sub model of device monitoring

The slices are numbered from 0 to 3. The ports are numbered across the different slices from 0 to 27. The port numbers against blue background represent client ports; port numbers against green background represent trunk ports.

The following configurations are supported on client and trunk ports in each slice. Each slice contains up to twenty Ethernet client ports operating at 10G, or five Ethernet client ports operating at 100G, or five Ethernet client ports operating at 40G. The client ports map to two trunk ports operating at 100G, 200G, or 250G that provides muxponder functionality.

40G client ports are supported from R6.0.1.

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

You can configure the slice with traffic on client and trunk ports. Both the trunk ports are always set with the same FEC mode. The slice can be configured to send encrypted traffic from R6.1.1.

See the Supported Configurations in Encrypted Mode section to determine the supported configurations on the client and trunk ports in each slice configured in encrypted mode

Note	When the slice is configured in encrypted mode, the drop-lldp cannot be enabled.

Note

When NCS 1002 is installed in a system where both the trunk interfaces in a slice are used, the two 250Gb 16QAM signals need to be co-routed on the same fiber (mandatory when the 5x100Gb client port is provisioned). Also, it is recommended to use adjacent wavelengths when the line modulation is set to 250Gb 16QAM. The reason for this is that the chromatic dispersion generates skew between wavelengths. Assuming a Dispersion of 10000 ps/nm, a span of 500 km, and using adjacent channel, the skew is evaluated in less than 200 ns and it is compensated by the deskew capability of NCS 1002. If the delta between the used channels is increased, the skew increases and it might exceed the skew compensation done by NCS 1002.

To configure the slice with unencrypted traffic, use the following commands.

configure

hw-module location location slice [slice_number | all ] client bitrate { 10G | 40G | 100G } trunk bitrate { 100G | 200G | 250G } fec { softdecision7 | softdecision20 }

commit

To configure the slice with encrypted traffic, use the following commands.

configure

hw-module location location slice [slice_number | all ] client bitrate { 10G | 40G | 100G } trunk bitrate { 100G | 200G } fec { softdecision7 | softdecision20 } [ encrypted ]

commit

configure
hw-module location 0/RP0/CPU0 slice 0 client bitrate 100G trunk bitrate 200G softdecision7 encrypted
commit

configure
hw-module location 0/RP0/CPU0 slice 0 client bitrate 10G trunk bitrate 100G softdecision20 encrypted
commit

configure
hw-module location 0/RP0/CPU0 slice 0 client bitrate 40G trunk bitrate 100G softdecision20 encrypted
commit

configure
hw-module location 0/RP0/CPU0 slice all client bitrate 10G trunk bitrate 100G fec softDecision7
commit

configure
hw-module location 0/RP0/CPU0 slice all client bitrate 40G trunk bitrate 100G fec softDecision7
commit

configure
hw-module location 0/RP0/CPU0 slice all client bitrate 100G trunk bitrate 200G fec softDecision7
commit

configure
no hw-module location 0/RP0/CPU0 slice all client bitrate 10G trunk bitrate 100G fec softDecision7 
commit

configure
no hw-module location 0/RP0/CPU0 slice all client bitrate 40G trunk bitrate 100G fec softDecision7
commit

configure
no hw-module location 0/RP0/CPU0 slice all client bitrate 100G trunk bitrate 200G fec softDecision7
commit

The following table describes the client and trunk ports in slice 0 that are enabled or disabled for each supported configuration.

E indicates that the port is enabled; D indicates that the port is disabled.

The following illustrations describe the mapping of traffic from client to trunk ports for certain configurations.

Client: 5 x 100G Trunk: 2 x 250G

Client: 4 x 100G Trunk: 2 x 200G

Client: 20 x 10G Trunk: 2 x 100G