Cisco Systems 15600 User Manual 2

Release Notes for Cisco ONS 15600 Release 8.0

October 15, 2007

Note The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms

do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration.
Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's
path protection feature, which may be used in any topological network configuration. Cisco does not
recommend using its path protection feature in any particular topological network configuration.

Release notes address closed (maintenance) issues, caveats, and new features for the Cisco ONS 15600. For
detailed information regarding features, capabilities, hardware, and software introduced with this release,
refer to Release 8.0 of the Cisco ONS 15600 Procedure Guide, Cisco ONS 15600 Reference Manual, Cisco
ONS SONET TL1 Command Guide, and Cisco ONS 15600 Troubleshooting Guide. For the most current
version of the Release Notes for Cisco ONS 15600 Release 8.0, visit the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/ong/15600/600relnt/index.htm
Cisco also provides Bug Toolkit, a web resource for tracking defects. To access Bug Toolkit, visit the

following URL:
http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl

Contents

• Changes to the Release Notes, page 2

• Caveats, page 2

• Resolved Caveats for Release 8.0, page 8

• New Features and Functionality, page 10

• Related Documentation, page 36

• Obtaining Optical Networking Information, page 36

• Obtaining Documentation, Obtaining Support, and Security Guidelines, page 37

Corporate Headquarters:
Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA

Copyright © 2007 Cisco Systems, Inc. All rights reserved.

Changes to the Release Notes

Changes to the Release Notes

This section documents supplemental changes that have been added to the Release Notes for Cisco ONS
15600 Release 8.0 since the production of the Cisco ONS 15600 System Software CD for Release 8.0.

Following change has been made to the release notes for Release 8.0.
OC192/STM64 4 Port ITU C-Band Card is not supported in this release.

Caveats

Review the notes listed below before deploying the ONS 15600. Caveats with tracking numbers are
known system limitations that are scheduled to be addressed in a subsequent release. Caveats without
tracking numbers are provided to point out procedural or situational considerations when deploying the
product.

Hardware

ONS-SE-2G-xx.x

The ONS-SE-2G-xx.x complies with performance criteria for all intra-facility fiber cables and
connectors per TelcordiaGR-326-CORE,Issue3Sept.1999.Ciscorecommendsthefollowingapproved
suppliers for intrafacility fiber cables to use with this product:

• Volex

• Fitel

• Sumitomo

• Fujikura

• Tyco

Maintenance and Administration

Caution VxWorksisintendedforqualified Cisco personnel only.CustomeruseofVxWorksisnotrecommended,

nor is it supported by Cisco's TechnicalAssistanceCenter.InappropriateuseofVxWorkscommandscan
have a negative and service affecting impact on your network. Please consult the troubleshooting guide
for your release and platform for appropriate troubleshooting procedures. To exit without logging in,
enter a Control-D (hold down the Control and D keys at the same time) at the Username prompt. To exit
after logging in, type “logout” at the VxWorks shell prompt.

Release Notes for Cisco ONS 15600 Release 8.0

2

OL-10906-01

CSCsd84932

Caveats

Note When the Cisco ONS 15600 is used in the Data Communications Network (DCN) as a Gateway Network

Element (GNE), Cisco Systems, Inc. recommends that:

a. Each Cisco ONS 15600 GNE should cater to no more than 64 Data Communications Channels
(DCC)-connected External Network Elements (ENE).
b. No ENE should be more than 8 DCC hops away from its GNE.
c. With large networks, the Cisco Transport Controller (CTC) Java Virtual Machine (JVM) Heap Size
should be set to 512 MB (default is 128 MB).
d. When running R7.2.1 and above, the ONS 15600 GNE should be declared a SOCKS proxy in CTC
preferences.
e. The number of simultaneous CTC sessions on the network should be limited to five.

When an ASAP card 1PIO that has STS1 circuits on it is removed,the downstreamNE will see UNEQ-P
on the STS1 circuits instead of AIS-P, as expected. Concatenated circuits will see AIS-P, as expected.
This issue does not occur with 4PIO removals, or with concatenated circuits. This issue will be resolved
in a future release.

CSCsb96697

CSCeh84908

CSCeg57163

CSCdy58342

When you perform a Manual Switch To Protect and then an SD-L condition is raised on the Protect port
that preempts the Manual Switch To Protect, the CTC Maintenance > Protection tab shows
“APS_CLEAR.” When you click Clear in that tab while the SD-L is still present on the protect port, the
K bytes will change to “No Request” for about 400-1000 frames before redeclaring the SD-L condition.
This issue can occur on ONS 15600 ASAP cards with 1+1 protection. It does not affect other cards or
protection schemes. This issue does not affect traffic. This issue can only occur when using the CTC
Maintenance > Protection tab under the aforementioned conditions. To avoid this issue, do not click
Clear when the CTC Maintenance > Protection tab shows “APS_CLEAR” and SD-L is present on the
protect port. This issue will be resolved in a future release.

A CTC client session can disconnect from an ONS node during simultaneous deletion of large numbers
of VT level circuits (3000+). Connectivity to the node will recover without any user action. If the
condition persists, restart the CTC session to reconnect. This issue is under investigation.

ONS platforms support only a single OSPF virtual link. This issue will be resolved in a future release.

OL-10906-01

Network connectivity could be lost if a backbone area becomes segmented into multiple GNEs. This
occurs only if multiple ONS 15600 nodes and routers are connected to the same LAN in OSPF area 0.
If a link between two routers breaks, the CTC session connected to Router 1 will not be able to
communicate with the ONS 15600 connected to Router 2. To resolve, you must repair the link between
the routers or provide another form of redundancy in the network. This is as designed.

Release Notes for Cisco ONS 15600 Release 8.0

3

Caveats

CSCdz07098

CSCdy25142

CSCeb49407

If OSPF on LAN is enabled with an area ID that is the same as the area ID of any of the DCC Links,
CTC will not be able to discover any of the DCC Connected Nodes. To avoid this issue, set the OSPF on
LAN area ID to an area other than any of those already occupied by a DCC link. This is as designed.

Equipment alarms are always reported based on the activity of the particular card, without taking card
redundancy into consideration. Thus, an equipment alarm such as CTNEQPT-PB-0 may be raised
against a line card as CR(SA) even though the traffic is protected. This issue will not be resolved.

Choosing certain qualities of RES settings in the CTC Provisioning tab, Timing subtab, may trigger a
reference failure. Specifically, this can occur if you select the quality of RES level such that any of the
following are true.

• ST3 < RES < ST3E

• ST4 < RES < SMC

• RES < ST4

When you then input an actual reference signal lower than ST3E quality, the failure is triggered. This
issue will not be resolved.

CSCsd38344

CSCsg37635

Executing an SNMP Walk on cerentGenericPmThresholdTableon an ONS 15600 node with many cards
causes Alarm CONTBUS-IO-B is raised unexpectedly.

ONS 15600 SDH is unreachable through CTC, during a system reset when performing an upgrade after
the activate step but before the accept step. A system soft reset is a controlled sequence of soft resetting
all the boards in the shelf. During the upgrade the introduction of this system reset causes
communication problemswithbothTSCs;thesystemdoesnot know which TSC is supposed to be active.
There is a procedure for an upgrade where a shelf reset should not be done by the operator. There is no
way for an automatic shelf reset to occur. On any power-down, the system comes up on the old code
without any issues involved. A workaround is to avoid a system reset during upgrade process.

Release Notes for Cisco ONS 15600 Release 8.0

4

OL-10906-01

Optical IO Cards

CSCse08282

When the Active XC is removed, the traffic from the line card might be lost. If the line card is an ASAP
card, the lack of traffic will cause a low transition signal density to enter the ASAP line card ASIC on
the backplane egress interface. The downstream FPGA on the ASAP 1PIO daughter card will begin
detecting B1 errors. These B1 errors will cause unexpected path protection switches. These errors will
also be reported as equipment failures.

To avoid this issue ensure that the Active XC is in OOS-MT state before removing it. If this issue does
occur,reset the 1PIO ASAP daughter card to clear the errored state. Resetting the ASAP carrier card will
also clear the errored state. This issue will be resolved in a future release.

CSCsc51518

In ASAP card view, the PIM graphic might not update with the correct color after an alarm is cleared.
This can occur anytime there is an alarm raised against the PIM or any of its subcomponents (PPM or
port). To recover from this state, you must either click the Synchronize button, or change to node view
and then back to card view. This issue will be resolved in a future release.

Caveats

CSCef20813

No graphical representations of LEDs for ASAP ports are displayed in the CTC card view. SD and SF
LED representations are also absent from the CTC node view for some legacy OCn cards. There are no
plans to resolve this issue.

BLSR Functionality

CSCsd62731

When you create a circuit in IS,AINS state while a BLSR is in the switch state the circuit will not
transition from IS/AINS to IS. To avoid this ensure that the BLSR is in a stable state before creating a
circuit. This issue will be resolved in a future release.

CSCeh49665

Connections might still exist after circuit deletions on BLSR DRI rings for which the primary node is
isolated. For BLSR DRI rings with several types of DRI circuits, if you isolate the primary node by
deleting the database, reseat the I/O cards, then delete all BLSR DRI circuits, the SSXCs still show
connections. To avoid this issue, do not delete or create BLSR DRI circuits when a node on the BLSR
DRI ring is isolated. This issue will not be resolved.

OL-10906-01

Release Notes for Cisco ONS 15600 Release 8.0

5

Caveats

Interoperability

CSCdx61916 and CSCeg20536

If, using CTC, you attempt to create a protected VT1.5 circuit that originates on one ONS 15454 that is
connected to the ONS 15600 via path protection to another ONS 15454 that is connected to the ONS
15600 via 1+1 or BLSR, the circuit creation request will be denied because of mixed protection domains.
CTC is currently incapable of routing VT circuits across the ONS 15600 when mixed protection schemes
are involved. VT traffic can be routed across the ONS 15600 when mixed protection schemes are
involved by performing the following:

Step 1 On the ONS 15600, create an STS level cross connect with the requisite path selectors.
Step 2 Use CTC to create a VT circuit from the source node to the trunk ports that interface to the 15600.
Step 3 Use CTC to create a VT circuit between the destination node and the trunk ports that interface with the

15600.

CSCdy68110

CSCdx94969

Note While this workaround provides the ability to route VT traffic across the ONS 15600 when mixed

protection domains exist, the traffic must be managed as three separate circuits instead of one single
end-to-end circuit.

This issue will be resolved in a future release.

When you attempt to configure VT circuits on a test configuration consisting of two ONS 15454 nodes
and one ONS 15600 node, when both ONS 15454s are connected to the ONS 15600 node using a dual
path protection connection configuration, and when the ONS 15600 node serves as an intermediate node
between the two ONS 15454 nodes, you may be unable to create a VT circuit from one ONS 15454 to
the ONS 15600 and then to the other ONS 15454. VT Tunnels are created, but the VT circuit is not
created. A mixed protection domain error message is raised when this occurs. To avoid this issue, create
the VT tunnels manually, so that the two tunnels do not create a topology where the working and protect
tunnels share the same I/O card. After the tunnels have been created, the VT circuit can be successfully
added. This issue will be resolved in future release.

Physical PM parameters can not be retrieved through the SNMP interface. MIBs released with the ONS
15600 do not have entries for the following physical PM parameters.

• LBC

• OPR

• OPT

The standard SONET Generic MIB does not have entries for these. To work around this issue, use CTC
to retrieve the values. SNMP support for these parameters may be considered for a future release.

Release Notes for Cisco ONS 15600 Release 8.0

6

OL-10906-01

CSCdy54737

Caveats

The following PM parameters can not be retrieved through SNMP.

• Line:

–

FC-L

• Path:

–

FC-P

–

PPJC-Pdet

–

NPJC-Pdet

–

PPJC-Pgen

–

NPJC-Pgen

• Protection groups:

–

PSC

–

PSD

• Far End counts for line and path

• 1-Day PM counts

To retrieve these counts, use CTC. SNMP support for these parameters may be considered for a future
release.

Bridge and Roll

CSCdy14265

The manual bridge and roll feature allows you to perform the END command once the roll operation
transitions from a ROLL PENDING to ROLL condition, even if the roll to port has an invalidsignal. To
avoid traffic impact, ensure that the roll-to line is alarm-free. If an alarm exists, you can choose to do
nothing and wait for the alarm to clear, to delete the roll, or to proceed in spite of the alarm. This issue
will not be resolved.

Alarms

CSCsd52527

The AS-MT and the AS-CMD alarms do not show up on the alarm profilein CTC, so you cannot change
the severity of these alarm using CTC. This issue will be resolved in a future release.

OL-10906-01

Release Notes for Cisco ONS 15600 Release 8.0

7

Resolved Caveats for Release 8.0

TL1

CSCsd59138

CSCsb72582

CSCeb46234

The wrong SSMs for additional references are displayed in the TL1 RTRV-SYNCN command response
for a 1+1 working line when that line is used as the primary reference for a node. References including
SYNC-NE 2 and 3, and SYNC-BITS are incorrectly reported. To avoid confusion, use CTC to view the
correct SSMs. This issue will be resolved in a future release.

You cannot perform an ENT-EQPT for a valid card type when the current equipment state is
OOS-AUMA,MEA&UAS. When the fault PPM comes up as OOS-AUMA,MEA&UAS and then the
ENT-EQPT command is entered using TL1, the command is rejected. This issue will be resolved in a
future release.

A TL1 user cannot preprovision IO cards when a filler card is in the slot. Removal of the filler card will
clear the slot and allow the TL1 user to preprovision the IO card. This is by design.

Resolved Caveats for Release 8.0

The following caveats were resolved in Release 8.0.

Maintenance and Administration

CSCsd45025

PPM hardware part numbers are displayed incorrectly in the inventory column. This issue is resolved in
Release 8.0.

Optical Cards

CSCsd88186

A MFGMEM alarm might be incorrectly raised when using an ASAP card with the PIO4 with one SFP,
then replacing that with a PIO1 and an XFP, then returning to the original configuration.When the alarm
is mistakenly raised, it does not clear. You must remove and reinsert the SFP to clear the alarm. This
issue is resolved in Release 8.0.

Release Notes for Cisco ONS 15600 Release 8.0

8

OL-10906-01

TL1

CSCsd52415

CSCsd95331

CSCsg77314

Resolved Caveats for Release 8.0

You cannot set the GIGE admin state to IS,AINS using the TL1 ED-GIGE command for the ONS 15600
ASAP card. The TL1 ED-GIGE command denies attempts to change the ADMIN state to IS,AINS this
card. CTC, however, can execute the state change. This issue is resolved in Release 8.0.

The status field incorrectly displays IS-NR when performing a RTRV-EQPT TL1 command where the
AID is of type PIM (Pluggable I/O Module) or PPM (Pluggable Port Module). Since PIMs and PPMs do
not support equipment protection, the status field should display NA. This issue is resolved in Release

8.0.

Standby TSC deletes DB without a sync from Active TSC causing an outage on the default DB. If the
Standby shelf controller reboots, by design it deletes its DB and syncs. If It cannot sync, it creates a
default DB. If it is called upon to be the active shelf controller, traffic is dropped. This issue has been
resolved in this release and in future releases.

CSCse40756

CSCsf01341

For multiple downloads, DNLD status is only updated for one node on network view.
When downloading six 600 nodes at the same time, the download status field on CTC was updated
properly on just one of the six 600 nodes. The workaround is to check-in the individual status of the
download on each node. This issue is resolved in Release 8.0.

Some circuits might be displayed as PARTIAL after one or more ONS 15600SDH nodes is upgraded to
Release 8.0 from Release 1.40. This can occur when the ONS 15600SDH has circuits with their drops
on the ONS 15600SDH nodes. The workaround is to run "Circuit Reconfigure"on the affected PARTIAL
circuits. This issue is resolved in Release 8.0.

OL-10906-01

Release Notes for Cisco ONS 15600 Release 8.0

9

New Features and Functionality

New Features and Functionality

This section highlights new features and functionality for Release 8.0. For detailed documentation of
each feature, consult the user documentation.

New Hardware Features

OC192/STM64 4 Port ITU C-Band Card

The OC192/STM64 4 Port ITU C-Band card provides four Telcordia GR-253-CORE compliant, SONET
OC-192 ports per card. The ports operate at 9953.28 Mbps over single-mode fiber. The OC192/STM64
4 Port ITU C-Band card has four physical connector adapters with two fibers per connector adapter. The
card supports STS-1 payloads and concatenated payloads at STS-3c, STS-12c, STS-24c, STS-48c, or
STS-192c signal levels.

The OC192/STM64 4 Port ITU C-Band card features a tunable 1550-nm C-band laser on the trunk port.
The laser is tunable across 82 wavelengths on the ITU grid with 50-GHz spacing between wavelengths.

OC192/STM64 4 Port ITU C-Band Card Slots and Connectors

You can install OC192/STM64 4 Port ITU C-Band cards in Slots 1 through 4 and 11 through 14. The
card provides four bidirectional SC-type connector adapters on the faceplate (angled downward),
carrying two fiber strands (one transmit and one receive). Only one transmit and receive pair is used per
connector adapter. On a breakout cable, use port three with fiber 4 (transmit) and fiber 3 (receive).

Any Service Any Port (ASAP) Card New SFP

The ASAP card provides up to 16 Telcordia GR-253-CORE compliant, SONET OC-3, OC-12, OC-48,
or Gigabit Ethernet ports, or up to 4 Telcordia GR-253-CORE compliant, SONET OC-192 ports, in any
combination of line rates. The ASAP card, when used with the 4-Port I/O (4PIO) module, has up to 16
physical connector adapters (known as Small Form-factor Pluggables [SFPs]). The SFP ports operate at
up to 2488.320 Mbps over a single-mode fiber. The ASAP card, when used with the 1-Port I/O (1PIO)
module, has up to 4 physical connector adapters (known as 10Gigabit Small Form Factor Pluggables
[XFPs]). The XFP ports operate at up to 9953.280 Mbps over a single-mode fiber. Both XFP and SFP
physical connector adapters have two fibers per connector adapter (transmit [Tx] and receive [Rx]). The
ASAP card supports STS-1 payloads and concatenated payloads at STS-3c, STS-6c, STS-9c, STS-12c,
STS-24c, STS-48c and STS-192c signal levels. The ASAP card is interoperable with ONS 15454
E-Series, G-Series, and ML-Series Ethernet cards.

There are three major components to the ASAP card:

• Carrier card, which can be installed in Slots 1 through 4 and 11 through 14

• 4PIO and 1PIO modules, also called Pluggable Input/Output Module (PIMs), which plug into the

ASAP carrier card

• SFPs/XFPs, called Pluggable Port Modules (PPMs) in CTC, which plug into the 4PIO or 1PIO

(PIM) module and provide the fiber interface using a female LC connector

A new SFP is available for use on the ASAP card. It is the ONS-SI-2G-S1, which operates at
OC48/STM16 rates.

10

Release Notes for Cisco ONS 15600 Release 8.0

OL-10906-01

Customer Access Panel

The Customer Access Panel (CAP or CAP2) is located in the middle on the rear of the shelf. The CAP
and CAP2 provide an alarm pin field, timing, and LAN connections. The CAP or CAP2 plugs into the
backplane using 2mm Hard Metric connectors with 752 pins and is held in place with one large captive
bolt and multiple screws.

The CAP2 has the additional capability of providing provisionable power monitoring.

Note The ONS 15600 supports only T1 (100 ohm) building integrated timing supply (BITS).

The ONS 15600 CAP and CAP2 provide the following features:

• BITS T1 (100 ohm) interfaces via wire-wrap pins.

• Two Ethernet interfaces via RJ-45 connectors with internal transformer isolation.

• An EIA/TIA-232 craft interface via DB-9 connectors. This interface is surge-protected and provides

• EMI filtering. Two interfaces are provided for redundancy.

• Four audio alarm interfaces via a DB-15 connector that is surge-protected and EMI-filtered. The

audio alarm indication is provided by the Timing and Shelf Controller (TSC) card and this interface
can receive a signal to disable the audio alarm.

• Four visual alarm interfaces via a DB-15 connector that is surge-protected and EMI-filtered. The

visual alarm indication is provided by the TSC card and the signal is connected to the PDU where
LEDs indicate the alarm status and severity.

• Environmental (external) alarms and controls (16 inputs and 16 outputs) via wire-wrap pins. The

interface is surge-protected and provides isolation by using an opto-isolator for alarm inputs and
relays for alarm outputs. By connecting to different wire-wrap pins on the CAP/CAP2, the alarm
outputs can be configuredfor either normally open (NO) or normally closed (NC) operation. Alarms
are initiated by shorting these contacts. The alarm input interface provides a pair of positive and
negative wire-wrap pins.

The isolation and termination meet the intra-building lightning surge specification in Telcordia
GR-1089. The CAP and CAP2 have –48 VDC monitoring with an I2Cinterface and nonvolatilememory
to store the CAP/CAP2 revision information.

If the CAP/CAP2 fails, the node raises an EQPT alarm. You can replace the CAP/CAP2 on an in-service
node without affecting traffic. Toreplace a CAP,refer to the Cisco ONS 15600 ProcedureGuide. Always
replace the CAP during a maintenance window.

New Features and Functionality

New Software Features

SFP Management Completion

Supported services (rates, wavelengths,formats, reach, and so on) are encoded in the EEPROMs of SFPs
and XFPs following industry standards. PPMs (SFPs or XFPs) that do not follow this standard cannot
be read by the platform and are referred to as Unrecognized PPMs.

PPMs that are inserted into a card may be checked for the validity of an MD5 security code. PPMs failing
this test are referred to as non-Cisco PPMs. PPMs passing this test as referred to in this document as
Cisco PPMs.

OL-10906-01

Release Notes for Cisco ONS 15600 Release 8.0

11

New Features and Functionality

Different cards are tested with a limited subset of Cisco PPMs. Customers are encouraged to use these
PPMs, referred to as Qualified Cisco PPMs (for the particular card). Since each card supports different
services (rates and formats), a PPM qualified for one card is not necessarily qualified for another. For
example, a PPM qualified to work on a DWDM card may not be qualified to work on a SONET card.
Cisco PPMs that are not recommended for use with a particular card are termed UnqualifiedCisco PPMs
(for the particular card).

Note This feature may not be described in the Release 8.0 documentation

DISA Password Complexity, Max Password Length, Min Password Length.

The password length, by default, must be set to a minimum of six and a maximum of 20 characters. You
can configure the default values in node view through Provisioning > NE Defaults > Node > security >
passwordComplexity. The minimum length can be set to eight, ten or twelve characters, and the
maximum length to 80 characters. The password must be a combination of alphanumeric (a-z, A-Z, 0-9)
and special (+, #,%) characters, where at least two characters are nonalphabetic and at least one character
is a special character. For TL1 compatibility, the password must be 6 to 10 characters. The password
must not contain the user name.

Required JRE Version is 5.0

JRE version 5.0 was optional in Release 7.0. It is required for release 8.0 that JRE be version 5.0.

Solaris 10 Supported.

Solaris 10 is supported in release 8.0

Mozilla 1.7 Supported on Solaris 9 with Java plug-in 5.0.

Mozilla 1.7 on Solaris 9 with Java plug-in 5.0 is supported in release 8.0.

IPv6

Cisco ONS 15xxx products can function in an IPv6 network when an internet router that supports
Network Address Translation - Protocol Translation (NAT-PT) is positioned between the GNE, such as
an ONS 15454, and the client workstation. NAT-PT is defined in RFC-2766. IPv4 and IPv6 nodes
communicate with each other using NAT-PT by allowing both IPv6 and IPv4 stacks to interface between
the IPv6 DCN and the IPv4 DCC networks.

NAT-PT binds addresses in IPv6 networks with addresses in IPv4 networks and vice versa to provide
transparent routing for the packets traveling between address types. This requires no changes to end
nodes and IP packet routing is completely transparent to end nodes. It does, however, require NAT-PT
to track the sessions it supports and mandates that inbound and outbound datagrams pertaining to a
session traverse the same NAT-PT router. Protocol translation is used to extend address translation with
protocol syntax/semantics translation.

12

Note Only Mozilla 1.7 is supported on clients interfacing with IPv6 networks.

Release Notes for Cisco ONS 15600 Release 8.0

OL-10906-01