Before you begin to
install the software, you must check whether your system meets the minimum
software and hardware requirements.
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 these
Windows Server 2008, or later
Apple Mac OS
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
Critical Bug Fixes
in Release 10.1.0.2
The following critical
issues have been resolved in Release 10.1.0.2:
USB-WRITE-FAIL alarm is raised when the node is loaded with multiple parallel
operations such as:
Performance Monitoring retrieval
Insertion and Removal of the LCD module
Reset of the
Shelf Controller fails to activate and the USB-WRITE-FAIL alarm is raised due
to sudden disconnect or Data Migration Assistant (DMA) timeout during software
BKUPMEMP, and EQPT-FAIL alarms are raised when standby controller card (TNC/TSC
and TNC-E/TSC-E) loses all the raw file system descriptors.
When soft reboot
is performed on the active TNC card from gateway network element (GNE), the End
Network Element (ENE) is not discovered in CTC.
100G-LC-C, 100G-CK-C, 100GS-CK-LC, and 200G-CK-LC cards reset automatically
without traffic loss.
alarm is raised on WSE card due to improper socks update on GNE.
Critical Bug Fixes
in Release 10.1.0.1
The following critical
issues have been resolved in Release 10.1.0.1:
alarm is raised on the control card when the nodes are upgraded to R10.0.2.
shelf controller with TCC2 card in ONS 15454 shelf running the R10.1 software
does not work with the node controller with TNC/TSC/TNC-E/TSC-E card in ONS
15454 M6 shelf running the software earlier than R10.1.
transient alarm is raised and clears on the control card occasionally during
the software upgrade.
When the subtended
shelf controller in
ONS 15454 M6
shelf is reset after the software upgrade, the
active and standby control card does not communicate.
element loses connectivity with CTC after the node is upgraded from R18.104.22.168 to
R10.0.2. The control card is also reset and the EQPT-FAIL alarm is raised on
the control card.
The TNC card
reloads due to invalid address or content of the messages in the Alarm module
provisionable patch cord (PPC) creation fails when CTC attempts to create the
PPC from the Network View > Provisioning > PPC > Create PPC Term pane.
New Features for
This section highlights new features
for Release 10.1. For detailed documentation of each of these features, see the
These hardware units
have been introduced in Release 10.1:
The 15454-M6-DC40 power
module delivers up to 1920 W (nominally 40 Amp at 48 VDC and 32 Amp at 60 VDC).
The FLD-OSC is a
passive unit used to combine the optical service channel (OSC) wavelengths to
form the DWDM aggregated signal, or split the OSC wavelengths from the DWDM
aggregated signal. The passive unit occupies a single slot in the rack mounting
bracket. The passive unit is introduced due to the end-of-sale of the OSC-CSM
card in the MSTP platform.
card is a tunable DWDM trunk card that simplifies the integration and transport
of the 100 Gigabit Ethernet interfaces and services on the enterprise or
service provider optical networks.
card provides the following benefits:
choosing 100G QPSK as the modulation format at the line side.
SD (Soft Decision) FEC encoding and Nyquist filtering for best performance and
optimal band usage.
access either through the local 100G CPAK interface or through backplane lines
that allow interconnection with an adjacent 10x10G-LC card.
features have been introduced in Release 10.1:
The split ROADM
node feature allows the ROADM node to have separate Network Elements (NEs) for
each line side leading to the separation of different ROADM degrees. When a
node split is configured, each line side is treated as a separate NE. The whole
NE manageability is not lost in case of failure. In a 4-degree ROADM node, the
four sides are split into four NEs and in an 8-degree ROADM node, the eight
sides are split into eight NEs. Virtual passive devices are used to manage
these nodes. The virtual passive devices are connected using virtual PPCs that
can be configured using CTC. The legacy ROADM configurations can be migrated to
split ROADM configurations using CTC and CTP.
information about split ROADM nodes, see the
Node Reference chapter
15454 DWDM Network Configuration Guide, Release 10.x.x .
The user can
assign and edit a rack label to each rack through CTC. The rack label can be up
to 20 characters.
The CTC in ONS
15454 M6 shelf view displays the three ports of the MS-ISC card, and EMS and
circuit ports present on the ECU.
When the user
selects a circuit in the Circuits tab, the corresponding circuit in the network
map is highlighted. When the user deselects a circuit in the Circuits tab, the
corresponding circuit in the network map is also deselected.
The user can
search for a node using the node name. When the user selects a node in the Find
Node in CTC dialog, the corresponding node is centered in the network map.
When the GMPLS circuit
creation fails due to optical validation, a detailed error message with
diagnostic logs is displayed that explains the causes of the failure.
TACACS is supported on MSTP.
However, this is not supported in GNE-ENE setup.
The system can be reset to
factory defaults. This option removes the data in the node and resets to
factory values. The system database is retained; hence, the IP address of the
node and multi-shelf configurations are retained.
The bandwidth usage of the
STS timeslots on the interlink interfaces in the ADM-10G double-card
configuration is displayed.
The client ports on the
10x10G-LC card can be configured with STM-64 or OC-192 payloads in MXP-10x10G
and TXP-5x10G operating modes.
CTC works with Ubuntu 12.10
and JRE 1.7.
The circuits between AR-XP(E)
and AR-MXP cards with different trunk ports and client ports in TXP
configurations can be created.
The syntax of these
commands have changed in Release 10.1:
responses of these commands have changed in Release 10.1:
Cisco Bug Search
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.
You will be
prompted to log into Cisco.com. After successful login, the Bug Toolkit page
To search for
release specific bugs,
enter the following parameters in the page:
Search For ―
15454 in the text box.
Enter the appropriate release number.
Show Bugs ―
Fixed in these Releases.
the search results include bugs with all severity levels and statuses, and bugs
that were modified during the life cycle of the bug. After you perform a
search, you can filter your search results to meet your search requirements.
set of 25 search results is shown in the bottom pane. Drag the scroll bar to
display the next set of 25 results. Pagination of search results is not
Use this document in
conjunction with the other release-specific documentation listed in this table:
Support website provides extensive online resources, including documentation
and tools for troubleshooting and resolving technical issues with Cisco
products and technologies.
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)
most tools on the Cisco Support website requires a Cisco.com user ID and