• Pluggable Port Module Support

  The MR-MXP card supports the ONS-QSFP-4X10-MLR= pluggable.

  The 400G-XP card supports ONS-QC-16GFC-SW= and ONS-QSFP-4X10-MLR= pluggable.

  Note	The maximum transmit launch power (per lane) of the ONS-QC-16GFC-SW= pluggable is +1dBm (the lowest being -7.6dBm).

  For details, see the guide.

• TCC2 / TCCP2 Card Support

  The nodes with the TCC2/TCC2P cards in releases prior to R10.6.2 cannot be upgraded to R10.6.2 as the size of the software package exceeds the size of the TCC2/TCC2P flash drive. Hence, R10.6.2 does not have the TCC2/TCC2P software package. If the user wants to continue with the ONS 15454 chassis, it is recommended to use the TCC3 control card. If the user wants to upgrade to a ONS 15454 M6 or NCS 2015 chassis, it is recommended to use the TNCS or TNCS-O control cards.

  ONS 15454 is supported in Flex NCS node as MSM-SSC only to NCS 2006 or NCS 2015 MSM-NC. Only TCC3 controller is supported on the ONS 15454 shelf.

  For more information on TCC2 / TCCP2 card support, see the Installing the Control Cards chapter in the Cisco ONS 15454 DWDM Control Card and Node Configuration Guide, Release 10.x.x.

This section lists the software features and enhancements introduced in Release 10.6.2.

• MR-MXP Enhancements

  OC192/STM64 and OTU2 client payloads are supported on the MR-MXP card in MXP-200G, MXP-10x10G-100G, MXP-CK-100G, and MXP-100G operating modes. OC192/STM64 and OTU2 client payloads are supported only when the sub OpMode is OPM_10x10G on the MR-MXP card.

  For more information on the MR-MXP enhancements, see the Provisioning Transponder and Muxponder Cards chapter in the

• Node Recovery Enhancements

  Two enhancements have been introduced to recover the node without traffic loss.

  • Provisioning Database: When provisioning database loss occurs, the following alarms are raised at the node level.

    • The BAD-DB-DETECTED critical alarm is raised when provisioning database loss occurs during reboot of control cards, switchovers, or upgrades. To clear this alarm, restore a previously saved database or use the "Reset NE to Factory Defaults" option in CTC.

    • The NODE-FACTORY-MODE critical alarm is raised when provisioning database loss occurs during system mode conversions, reset to factory defaults, or in new installations. To clear this alarm, restore a previously saved database or use the Rebuild DB option in the Maintenance > Database tabs in CTC.

  • System Database: When system database loss occurs on the active or standby control card, an INVALID SYSDB alarm is raised on the control card. To clear the alarm do any of the following actions:

    • If the alarm is raised only on the active control card, reboot the active card.

    • If the alarm is raised only on the standby control card, reboot the standby card.

    • If the alarm is raised on both the active and standby control cards, contact TAC for support.

  For more information about the node recovery feature, see the Maintaining the Node chapter in the

• 400G-XP LC Enhancements

  • Support for 16G-Fiber Channel payload- This payload is supported only on the ONS-QC-16GFC-SW= pluggable. A new operating mode, OPM_6x16G_FC is introduced to support this payload on ports 1, 2, 3, 4, 5, and 6. This operating mode can be provisioned on any slice, with trunk configuration set to M_100G and M_200G.

  • Support for OTU2 payload- This payload is supported only on the QSFP-4X10G-MLR pluggable. The payload can be provisioned for the OPM_10x10G slice mode for any trunk configuration.

  • Support for trunk PM parameters-Second Order PMD (SOPMD) and Polarization Depended Loss (PDL).

  For more information about the payloads, see the Provisioning Transponder and Muxponder Cards chapter in the

• Optical PM Monitoring on QSFP+

  The optics PM parameters are enabled on QSFP+ ports of the MR-MXP cards.

• ROADM Configurations

  A set of MF-6AD-CFS passive splitter/coupler modules are connected to the SMR-20 EXP-TX/RX ports to obtain a colorless (and gridless) directional A/D stage. The interconnection can be done either with a break-out cable, ONS-MPO-16-LC2=, or with an adapter module, MF-MPO-16LC. The various configurations are colorless terminal ROADM, 2-degrees colorless ROADM and 8-degrees colorless ROADM.

  For more information, see the Node Reference chapter in the

• Multivendor Interoperability

  The 200G-CK LC can be configured to interoperate with other vendor devices.

• Duplicate Node Controller

  When a TNC/TNC-E/TSC/TSC-E/TNCS/TNCS-O node controller connects to the same switch where an NCS 2006 or NCS 2015 node controller exists, both the node controllers raise the critical Duplicate Node Controller (DUP-NC) alarm. The subtending shelves of both the node controllers raise the Shelf Communication Failure (SHELF-COMM-FAIL) alarm. Both the node controllers and their subtending shelves shut down their ports on ASIC towards the MSM ports in ECU. However, the traffic is not affected. This feature enables the original node to operate seamlessly in case of such misconfigurations, without the risk of its subtending shelves treating the new node controller as its primary.

  For more information on the duplicate node controller, see the Managing the Shelf chapter in the

• Thirty Party Certificates for WSE Card

  From Release 10.6.2, the WSE card supports the generation of a CSR and installation of Locally Significant Certificates (LSCs) that can be used to authenticate the peer card connection.Third Party Certificates also called Locally Significant Certificates (LSCs) are certificates that are signed by a Certification Authority (CA) other than Cisco Certificate Authority (CA). LSCs allow customers to have their own public key infrastructure (PKI) to provide better security and to have control of their own CA, and to define policies, restrictions, and usages on the generated certificates.

  A public-private key is generated inside the target system and then the generated public key along with other product or customer specific information (collectively called as a Certificate Signing Request) is then sent to get signed by a CA (customer owned or a third party). Once signed, the signed certificates are imported or installed (via a trusted and secure channel/method) into the target system. Once installed, the signed certificates in conjunction with the Private Key can be used to authenticate any remote connection/peer before exchanging sensitive information with the same.The Certificate Signing Request (CSR) is exported from the target system and the signed certificates are imported/installed back into the target system.

  For more information, see the Provisioning Transponder and Muxponder Cards chapter in the

• OTDR Enhancements

  • The OTDR scan starts automatically after the LOS alarm is raised and cleared, To perform this, enable the Automatic Scan on LOS Raise and Clear radio button. For more information, see the

  • The default value for the automatic OTDR scan to begin is 3 minutes. For more information, see the Cisco ONS 15454 Network Configuration Guide, Release 10.x.x

  • Location [km] in the Reflection table or the Insertion Loss table is enhanced with the Accuracy (km) details.

    For more information, see the Manage the Node document.

• MSM Supported Configurations

  The following configurations are supported:

  • 40 400G-XP-LC cards provisioned with 10GE payloads. The total number of client interfaces is 1600.

  • 20 400G-XP-LC, 36 200G-CK-LC, and 72 MR-MXP cards provisioned with 10GE payloads. The total number of client interfaces is 1520.

  • 70 400G-XP-LC cards provisioned with 100GE payloads. The total number of client interfaces is 280.

  • 20 400G-XP-LC cards provisioned with 100GE payloads along with 36 200G-CK-LC and 72 MR-MXP cards provisioned with 10GE payloads. The total number of client interfaces is 800.

  Recommendations have been provided for optimum system performance.

  For more information about this feature, see the Provisioning Transponder and Muxponder Cards chapter in the

• Alarms

  The alarms introduced in 10.6.2 are:

  • USB-PORTS-DOWN

  • LOCAL-CERT-CHAIN-VERIFICATION-FAILED

  • PEER-CERT-VERIFICATION-FAILED

  • EPROM-SUDI-SN-MISMATCH

  • LOCAL-CERT-EXPIRED

  • INVALID-SYSDB

  • NODE-FACTORY-MODE

  • BAD-DB-DETECTED

  • LOCAL-CERT-ISSUED-FOR-FUTURE-DATE

  • LOCAL-CERT-EXPIRING-WITHIN-30-DAYS

  • LOCAL-SUDI-CERT-VERIFICATION-FAILED

  • LSC-NOT-PRESENT-MIC-IN-USE

  For more information about the alarms , see the Alarm Troubleshooting chapter of the

• TL1 Commands

  The TL1 commands introduced in 10.6.2 are:

  • RTRV-EQPT-HOLDERTL1