Revision History
Date | Notes |
---|
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Note |
Explore the Content Hub, the all new portal that offers an enhanced product documentation experience.
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.
Date | Notes |
---|
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
This section highlights new features for Release 10.0. For detailed documentation of each of these features, see the user documentation.
These hardware units have been introduced in Release 10.0:
The double-slot EDRA-1-xx and EDRA-2-xx cards are erbium-doped Raman amplifiers (EDRAs) that support Raman amplification on long unregenerated spans. The EDRA cards support an ultra-low noise figure that is critical for long-distance, high-bit-rate transmission. Each EDRA card can manage up to 96 channels, 50-GHz-spaced from 196.1 GHz (1528.77nm) to 191.35 GHz (1566.72 nm). The EDRA cards are plug-in modules that provide the reach and optical performance required to meet the most demanding distance requirements of service provider and enterprise networks.
The EDRA cards have four versions:
For more information about the EDRA cards, see the chapter in the .
The double-slot cross connect 16-port Flex Spectrum ROADM line card (16-WXC-FS) can be used at the core of the network. The card is used to build ROADM nodes with 96 channels spaced at 50-GHz, flex spectrum channels, or a combination of the two. The card provides the flex spectrum capability, which allows the user the flexibility to allocate channel bandwidth and increase the network scalability. The channel bandwidth is not fixed, but can be defined arbitrarily, with a given granularity and within a given range. Attenuation and power values are defined for each sub-range. The frequency ranges from 191'350 Ghz (1566 .72 nm) to 196'100 Ghz (1528 .77 nm). The 16-WXC-FS card can be used in point-to-point, ring, multi-ring, or mesh topologies. The 16-WXC-FS card supports up to 16 directions for each ROADM node.
For more information about the 16-WXC-FS card, see the chapter in the .
A new generation of passive optical modules can be used to accommodate ROADM nodes built with the 16-WXC-FS and EDRA cards. Three types of modules are available: patch panel modules, add/drop modules, and adapter modules. All the modules fit into four slots of a 1-rack-unit (1RU) mechanical frame chassis (MF-1RU). Their passive nature helps ensure extremely high availability in a small, low-power footprint. ECU3 is required for these passive modules.
The passive modules are:
For more information about the ROADM passive modules, see the document.
The 100G-CK-C and 100ME-CKC cards are tuneable over the entire C-band. The 100G-CK-C card works similar to the 100G-LC-C card. The 100G-CK-C card has the new CPAK client interface replacing the CXP client interface of the 100G-LC-C card.
The 100G-CK-C and 100ME-CKC cards support the CPAK-100G-SR10 client interface with 100GE/OTU4 and 40GE/OTU3 payloads. Both the cards support the CPAK-100G-LR4 client interface with 100GE/OTU4 payloads. The CPAK client interface enables different payload combinations such that the 100G-CK-C card can be used instead of the 100G-LC-C and CFP-LC cards.
The 100ME-CKC is a metro edge version of the 100G-CK-C card. The 100ME-CKC card has chromatic dispersion of +/-5000 ps/nm and does not support 20% FEC.
For more information about the 100G-CK-C and 100ME-CKC cards, see the chapter in the .
The Pluggable Port Modules supported on the 100G-CK-C and 100ME-CKC cards are:
For more information about the Pluggable Port Modules support, see the document.
These software features have been introduced in Release 10.0:
The control plane supports the Label Switch Path (LSP) priority signaling on the UNI interface. The LSP priority can be set using CTC or TL1. The LSP priority is used to resolve a conflict on any network resource when two or more LSPs are set at the same time, and requires the same resources. The LSP priority is critical during circuit creation and restoration.
The LSP priority is used to decide the GMPLS restoration in a multiple channel setup, and optimizes the restoration time for an LSP with a higher priority. The restoration is dynamic, managed by the head node and simplifies network operations. In a circuit failure, the dynamic optical restoration enables the automatic re-routing of the optical circuit over a new route. The GMPLS intelligence embedded in the circuit enables the DWDM layer to dynamically validate the feasibility of the new route. This ensures a successful network connectivity and eliminates the dependancy on additional design tools.
The regenerators in the network minimize the signal loss, and helps to establish an uninterrupted connection between the source and destination. The control plane uses LSP setup and the regenerators in the circuit to create segments during failure in the optical path. A regenerator connects each segment in the network. The wavelength changes at each regenerator, if the wavelength continuity between the two end points is not available. A regenerator failure triggers the restoration process.
The optical impairments in full coherent networks follow the LOGO model (Local Optimization Global Optimization) that is applicable to 100G full coherent networks. The optical impairment is calculated node by node, and can be identified by adding the local contribution penalty of the nodes or spans in the path. The crosstalk between optical channels can be pre-defined in network design phase and considered as a constant by the control plane. The need to signal the values of all the optical parameters to the egress node (to calculate the channel feasibility and the residual margins of existing channels) is eliminated. Each add or drop domain is associated a value that represents the penalty calculated due to signal loss. This operation is done during network setup or network upgrade.
CTC notifies the user when duplicate patchcords are created, either manually or by using the NE Update configuration file. The user can choose to retain the existing patchcord or overwrite the existing patchcord with the new patchcord.
For more information about the software enhancements, see the chapter in the .
The MXP_MR_S (Unprotected Multirate Muxponder-Static) and MXPP_MR_S (Protected Multirate Muxponder-Static) operating modes are introduced for the AR_MXP, AR_XP, and AR_XPE cards. These modes are similar to the existing MXP_MR and MXPP_MR operating modes except for static timeslot and ODU allocation. A specific set of client payloads or a mix of client playloads can be used only if the trunk bandwidth and timeslot are available as per the static allocation mapping. For example, the MXP_MR_S and MXPP_MR_S modes can be used to provision a dual 4xOC-48 or a mix of 2-OC-48 + 2-GE or 1-OC-48 + 6-GE into one OTU2 muxponder.
For more information about the operating modes, see the chapter in the .
This section contains a list of new commands, command syntax changes, and command response changes that have been introduced in Release 10.0. For detailed information on TL1, see the .
These TL1 commands are added in Release 10.0:
The syntax of these commands have changed in Release 10.0:
CHG-EQPT | DLT-OPMODE | DLT-RMONTH-MOD2 | DLT-RMONTH-OTU |
ED-CPS | ED-EQPT | ED-OCH | ED-OPMODE |
ED-OTS | ED-OTU | ED-UNICFG | ED-WDMANS |
ENT-CPS | ENT-EQPT | ENT-OPMODE | ENT-RMONTH-OTU |
ENT-UNICFG | ENT-WDMANS | INIT-REG-MOD2 | REPT-ALM-EQPT |
REPT-ALM-MOD2ALM | REPT-ALM-SYNCN | REPT-EVT-EQPT | REPT-EVT-MOD2ALM |
REPT-EVT-SYNCN | REPT-PM-MOD2 | SET-TH-MOD2 |
The command responses of these commands have changed in Release 10.0:
RTRV-CPS | RTRV-EQPT | RTRV-MAP-NETWORK | RTRV-NE-WDMANS |
RTRV-OCH | RTRV-OMS | RTRV-OPMODE | RTRV-OTS |
RTRV-OTU | RTRV-PM-ALL | RTRV-PM-MOD2 | RTRV-RMONTH-OTU |
RTRV-TH-ALL | RTRV-TH-MOD2 | RTRV-UNICFG | RTRV-WDMANS |
Use the Bug Search Tool (BST) to view the list of outstanding and resolved bugs in a release.
BST, the online successor to Bug Toolkit, is designed to improve the effectiveness in network risk management and device troubleshooting. The tool allows partners and customers to search for software bugs based on product, release, and keyword, and aggregates key data such as bug details, product, and version. The tool has provision to filter bugs based on credentials to provide external and internal bug views for the search input.
The BST is available at Bug Search. To search for a specific bug, go to https://tools.cisco.com/bugsearch/bug/bugid. For more information on BST, see Bug Search Help.
Follow the instructions below to search bugs specific to a software release in BST.
Step 1 |
Go to https://tools.cisco.com/bugsearch/. You will be prompted to log into Cisco.com. After successful login, the Bug Toolkit page opens. |
Step 2 |
To search for release specific bugs, enter the following parameters in the page:
|
Step 3 |
Press Enter. Note:
|
Use this document in conjunction with the other release-specific documentation listed in the table below:
Link | Description |
---|---|
The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds. Access to most tools on the Cisco Support website requires a Cisco.com user ID and password. |