Release Notes

Note

Explore the Content Hub, the all new portal that offers an enhanced product documentation experience.

Use faceted search to locate content that is most relevant to you.
Create customized PDFs for ready reference.
Benefit from context-based recommendations.

Get started with the Content Hub at content.cisco.com to craft a personalized documentation experience.

Do provide feedback about your experience with the Content Hub.

This Release Notes document contains information about new features and enhancements, in the Cisco platforms.

Cisco also provides Bug Search Tool, a web resource for tracking defects. To access Bug Search Tool, visit the following URL: https://tools.cisco.com/bugsearch.

Revision History

Table 1. Revision History
Date	Notes
November 2018	Added the Critical Bug Fixes section for R10.7.0.2.
March 2018	Added the Critical Bug Fixes section for R10.7.0.1.
September 2017	This is the first release of this publication.

Software and Hardware Requirements

Before you begin to install the software, you must check whether your system meets the following minimum software and hardware requirements:

Hardware—Intel Core i5, i7, or faster processor. A minimum of 4 GB RAM, 100 GB hard disk with 250 MB of available hard drive space.
One of the following operating systems:
- Windows 7, Windows Server 2008, or later
- Apple Mac OS X
- UNIX workstation with Solaris Version 9 or 10 on an UltraSPARC-III or faster processor, with a minimum of 1 GB RAM and a minimum of 250 MB of available hard drive space.
- Ubuntu 12.10
Java Runtime Environment—JRE 1.8 and later.
Java version 8.0
Browser:
- Internet Explorer
- Mozilla Firefox
- Safari
- Google Chrome

Critical Bug Fixes

Critical Bug Fixes in R10.7.0.2

The following critical issues have been resolved in Release 10.7.0.2:


Caveat ID Number	Description
CSCvj08074	When a SSC is added in a 48 VDC environment, it raises a Extreme Low Voltage Battery (EHIBATVG) alarm that cannot be cleared.
CSCvj11222	The Circuit Diagnostic of CPO R10.7.0.1 does not work with network elements of NCS 2000.
CSCvj13778	If one or more clients continously tries to connect to the SOCKS server, the server msg pipe is filled causing the tProxyS task to be blocked forever.
CSCvj67003	The Circuit Diagnostic of CPO shows blank with the network elements of NCS 2000 in secure mode.
CSCvj33045	When the node is upgraded from R10.6.0.1 to R10.7.0.2, traffic is affected as RAMAN calibration is not completed.
CSCvj37433	CTC does not report the newly created LMPs under the LMP pane.
CSCvj48759	Controllers reboot periodically in a mixed release with WSON circuit that is down.
CSCvj76671	When the node is upgraded from R10.6.0.1 to R10.7.0.2 with ECU-S on NCS 2006, the voltage thresholds are replaced with incorrect values.

Critical Bug Fixes in R10.7.0.1

The following critical issues have been resolved in Release 10.7.0.1:

The client ports are not listed during WSON OCHCC creation.
When circuits are restored, the ROADM node that has twenty degree restarts.
An ‘Operation Failed’ error message occurs while creating a media channel group containing an OCHNC circuit.
When the TNC card force reloads, NE discovery takes longer time on CTC after the card switches over.
When the 24 SMR9 FS card is reset, the traffic is affected on the AD circuits.
The restoration of OCH Trail causes the node controller to reboot.
When ONS 15454 M12 and ONS 15454 M6 node controllers with TCC3 card and 40-WSS card are upgraded to R10.7.0.1, the nodes perform roll reboot.
The MR-MXP card does not recognize the QSFP-40G-LR4 pluggable.
The SSON circuit restoration does not work on the 20-SMR card due to wrong carrier allocation.
The Optical Power Failure Low (OPWR-LFAIL) alarm is raised on the SMR-20 card after the restoration or revert of OCHCC WSON circuit.
The circuit creation fails from CTC NFV view as the source and destination ports are not completely defined.
The TNC card resets when APC domains are selected and Refresh button is clicked in the Card View > Maintenance > APC > Refresh.

JRE Compatibility

The table displays the JRE compatibility with software releases.

Supported Pluggables

The document at the following URL lists the GBIC, SFP, SFP+, QSFP, XFP, CXP, CFP, and CPAK modules that are supported on the Cisco platforms:

New Features in Release 10.7

This section highlights the new features in Release 10.7. For detailed information of each of these features, see the user documentation.

Hardware

Pluggable Port Module Support

The 400G-XP card supports the QSFP-40G-SR4 and the QSFP-100G-SM-SR= pluggable.

Software Features

Note

Before you dive into this release's features, we invite you to content.cisco.com to experience the features of the Cisco Content Hub. Here, you can, among other things:

Create customized books to house information that’s relevant only to you.
Collaborate on notes and share articles by experts.
Benefit from context-based recommendations.
Use faceted search to close in on relevant content.

And, if you are already experiencing the Content Hub, we'd like to hear from you!

Click the Feedback icon on the page and let your thoughts flow!

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

Third Party Certificates on MR-MXP Card

The MR-MXP card supports the generation of a Certificate Signing Request (CSR) and the installation of Locally Significant Certificates (LSCs) that can be used to authenticate the peer card connection. Third party certificates also referred to as Locally Significant Certificates (LSCs) are certificates that are signed by a Certification Authority (CA) other than Cisco Certificate Authority. LSCs allow customers to have their own Public Key Infrastructure (PKI) to provide better security, 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 be signed by a CA (customer owned or a third party) after which, the signed certificates are imported or installed via a trusted and secure channel or method into the target system. After the signed certificates are installed, it can be used in conjunction with the private key to authenticate any remote connection before exchanging sensitive information with the same.