Release Notes for Cisco ONS 15454, Release 8.5.4

Table Of Contents

Release Notes for Cisco ONS 15454
Release 8.5.4

Contents

Changes to the Release Notes

Caveats

Alarms

CSCsv30867—The alarms do not clear after XC side switch

CTC

CSCsy14945—CTC cannot manage either nodes of the same version of higher maintenance version, than its core version

CSCsv14375—Shared secret key corrupt after upgrade

Data I/O Cards

CSCsx49481—Fiber SFP port reports CARLOSS Alarm in CEMR-6 card

CSCsy16814—Traffic Drop is observed when port state change from OOS-DSBLD to IS

CSCsx75218—VC12 VCAT circuit members may not come-up and report LOP alarm

DWDM

CSCsx17868—The MXP-MR-10DME card continuously reboots after FPGA upgrade

CSCsu81842—Circuit not created through add and drop node with by-pass patchcords

CSCsv01621—Unable to open the card configuration panel

CSCta49163—Unsupported Y-cable allowed through TL1

CSCtb16483—PPC created through TL1 is not discovered properly in the CTC

CSCsz94689—Incoming traffic received through any port on the affected card may flow to other Service Provider VLANs

CSCtb33916 —After an upgrade, traffic is discarded on a newly created VLAN

Optical I/O Cards

CSCsu80809—Data rate can be changed when there are active circuits and DCC connections

Path Protection

CSCta44268—In ADM10G, for UPSR protected circuits on STSs greater than 3, traffic hit of around 2000ms is observed

CSCsv30593— AIS-V alarm does not clear

TL1

CSCsv45464—The rtrv-ochnc command with access identifier (aid) =all, does not return any information about the existing cross connections

CSCsv71398—The RTRV-MOD command displays LBC and OPT parameters with invalid values

CSCsz81750—Traffic loss for 50 ms on MXPP-MR2.5G and TXPP-MR-2.5G cards

Resolved Caveats for Release 8.5.4

Alarms

CSCta72945—SWMTXMOD Alarm on MRC Cards

CSCsz84817—High Laser bias and Rx power alarms seen on Finisar XFP

CSCta72945—SWMTXMOD Alarm on MRC Cards

CSCsy69110—ADD Port Alarm not Raised

CSCsz67629—On E1-42 protection switching, LOS alarms on ports 23 and 27 are cleared

Common Control Cards

CSCsx37297—FTP port issue for TCP connect scan

CSCsy91761—Constant TCC Reset

CSCsz39798—Constant TCC Reboot

CSCsz08846—Generation of two Contradictory Logs

CSCsz81891—Issue in Database Partitions not Reported

CTC

CSCsx81421—Trouble to Manage SoTL1 Tunnels using CTC

CSCsy74949—Incorrect NE Default Values Downloaded

CSCsy82228—CTC Network discovery is slow

CSCsw96807—PPC cannot be deleted in secure mode node

CSCsm85843—CTC displays the STS circuit in ROLL_PENDING state when a bridge and roll is Performed

CSCsq73116—PPC is not working on secure mode node

CSCsr01562— PPC Links Disassembled

Data I/O Cards

CSCta44387—UNEQ-P does not trigger link integrity on CCAT circuits

CSCsl65143—Traffic outage on G1K and G1000 cards

CSCtc66943—Link does not come up when autonegotiation is enabled

DWDM

CSCsj97288—PROV-MISMATCH alarm raised on TXP_MR_10E Card

CSCsq78337—Cannot provision ONS-SE-G2F-LX= SFP for ISC3

Electrical I/O Cards

CSCsl81293—Traffic loss on DS1 card

CSCsu92843—BERT on DS3-XM12 card does not inject bit errors

CSCsz59607—Traffic drops on DS3-XM card when Signal Degrade alarm threshold is cleared

CSCta24511—LoF on DS3-XM6 card does not cause DS1 AIS

CSCta24511—LoF on DS3-XM6 card does not cause DS1 AIS

Hardware

CSCsm55562—Payload PM not reported on active gigabit Ethernet port when CARLOSS is raised

Optical I/O Cards

CSCta42253—MRC card remains in OOF state

CSCsv54817—UNEQ-P alarm is raised on STS-96c circuits with OC-192 XFP

Path Protection

CSCsy26595—Traffic does not recover after active and protect paths fail

CSCsx17026—Traffic on Protect Path not Restored

CSCsk46370—Error Rate Injection non functional

CSCsz06764—SF-V condition does not clear

CSCsw49064—GR3 protection is not triggered by SD or SF alarms on trunk ports

New Features and Functionality

Link Integrity Soak Timer

TL1 Gateway and ENE Sessions

Related Documentation

Release-Specific Documents

Platform-Specific Documents

Obtaining Optical Networking Information

Where to Find Safety and Warning Information

Cisco Optical Networking Product Documentation CD-ROM

Obtaining Documentation and Submitting a Service Request

Release Notes for Cisco ONS 15454
Release 8.5.4

---

April 2010

Release notes address closed (maintenance) issues, caveats, and new features for the Cisco ONS 15454 SONET platform. For detailed information regarding features, capabilities, hardware, and software introduced with this release, refer to the Release 8.5.x version of the Cisco ONS 15454 DWDM Installation and Operations Guide; and the Release 8.5.1 version of the Cisco ONS 15454 Procedure Guide; Release 8.5.x version of the Cisco ONS 15454 Reference Manual; Release 8.5.x version of the Cisco ONS 15454 Troubleshooting Guide; and Release 8.5.1 version of the Cisco ONS 15454 SONET TL1 Command Guide. For the most current version of the Release Notes for Cisco ONS 15454 Release 8.5.4, see the following URL:

http://www.cisco.com/en/US/products/hw/optical/ps2006/prod_release_notes_list.html

Cisco also provides Bug Toolkit, a web resource for tracking defects. To access Bug Toolkit, see the following URL:

http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs

Contents

Changes to the Release Notes

Caveats

Resolved Caveats for Release 8.5.4

New Features and Functionality

Related Documentation

Obtaining Optical Networking Information

Obtaining Documentation and Submitting a Service Request

Changes to the Release Notes

This section documents supplemental information that has been added to the Release Notes for Cisco ONS 15454 Release 8.5.4 since the production of the Cisco ONS 15454 System Software CD for Release 8.5.4.

Caveats

Review the notes listed below before deploying the Cisco ONS 15454. 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.

---

Note The use of 40WXC units is supported only in the networks running software Release 8.5.1 and later.

---

Alarms

This section documents caveats for Alarms in Release 8.5. 4.

CSCsv30867—The alarms do not clear after XC side switch

When any VT level alarms are raised, an XC side switch is performed to eliminate the alarm. The alarms do not clear after XC side switch. The workaround is to reset XC card to clear the alarm. This issue will be resolved in a future release.

CTC

This section documents caveats for CTC in Release 8.5. 4.

CSCsy14945—CTC cannot manage either nodes of the same version of higher maintenance version, than its core version

CTC cannot manage either nodes of the same version of higher maintenance version, than its core version. Specifically the nodes are not accessible by CTC. The workaround is to upgrade the CTC core version or manually clean the CTC jar cache and then ensure no nodes of the specified version above are encountered. This issue will be resolved in a future release.

CSCsv14375—Shared secret key corrupt after upgrade

Longer than 16 character shared secret key gets corrupted after an upgrade from 7.20 to 8.54. To avoid this, use radius server key less than 16 character length before upgrade or:

On the node with EnableNodeAsFinalAuthenticator attribute enabled, do the following as workaround:

1. Launch CTC.

2. Delete the corrupted secret key record in CTC (node view->Provisioning->Security->RADIUS Server).

3. Recreate it with an appropriate key.

This issue will be resolved in a future release.

Data I/O Cards

This section documents caveats for Data I/O Cards in Release 8.5. 4.

CSCsx49481—Fiber SFP port reports CARLOSS Alarm in CEMR-6 card

Plug-out copper SFP in OOS,DSBLD state and plug-in Fiber SFP and move the port state to IS. Fiber SFP port reports CARLOSS Alarm in CEMR-6 card. To recover from CARLOSS, plug-out and plug-in Fiber SFP again. This issue will be resolved in a future release.

CSCsy16814—Traffic Drop is observed when port state change from OOS-DSBLD to IS

Traffic Drop is observed when port state change from OOS-DSBLD to IS. The workaround is to perform IS->OOS-> IS transition until problem is fixed. This issue will be resolved in a future release.

CSCsx75218—VC12 VCAT circuit members may not come-up and report LOP alarm

Create VC4-2c/ VC4-3c/ VC4-4c/ VC4-8c/ VC4-16c or any of the CCAT and the delete the CCAT circuit. Create VC12 VCAT circuit using the same VC4 members as previously deleted CCAT circuits. Some VC12 VCAT circuit members may not come-up and report LOP alarm. The workaround is to hard-reset CEMR-10/CEMR-6/MLMR-10 cards. This issue will be resolved in a future release.

DWDM

This section documents caveats for DWDM in Release 8.5. 4.

CSCsx17868—The MXP-MR-10DME card continuously reboots after FPGA upgrade

The MXP-MR-10DME card continuously reboots after FPGA upgrade. Forcing an FPGA upgrade on an MXP-MR-10DME results in a status where the card reboots continuously. The workaround is to reset the card. This issue will be resolved in a future release.

CSCsu81842—Circuit not created through add and drop node with by-pass patchcords

The OCHNC circuit is not created through channel add and drop node with by-pass patchcords. When the traffic matrix of the network requires BYPASS connection between AD-XC cards, the APC domain is not properly discovered. The workaround is to remove the bypass patchcords in the node and create two separated OCH-NC circuits. This issue will be resolved in a future release.

CSCsv01621—Unable to open the card configuration panel

The user cannot open the card configuration panel for any WXC card inserted or pre-provisioned in the system. The workaround is to physically remove the deleted WXC cards from their slots. This issue will be resolved in a future release.

CSCta49163—Unsupported Y-cable allowed through TL1

TL1 allows Y-cable protection to be configured between the cards that are already in another Y-cable group and on the third card that is not part of the original Y-cable group. The CTC does not allow this operation, but TL1 lets it through. This issue will be resolved in a future release.

CSCtb16483—PPC created through TL1 is not discovered properly in the CTC

The provisionable patchcords (PPC) created using TL1 between nodes in secure mode and normal mode are not discovered in CTC. The workaround is to use CTC to create PPC. This issue will be resolved in a future release.

CSCsz94689—Incoming traffic received through any port on the affected card may flow to other Service Provider VLANs

Incoming traffic received through any port on the affected card may flow to other Service Provider VLANs (svlan) if the Customer VLAN (cvlan) ID on the incoming packet belongs to any VLAN range configured on the card. This issue may occur even if the packet is received via a Network to Network Interface (NNI) port. This issue will be resolved in a future release.

CSCtb33916 —After an upgrade, traffic is discarded on a newly created VLAN

The traffic does not flow in a newly created VLAN under the following conditions:

•Software upgraded from R8.5 to R9.0 or R9.0.1

•After a soft reset of the card.

This issue will be resolved in a future release.

Optical I/O Cards

This section documents caveats for Optical I/O Cards in Release 8.5. 4.

CSCsu80809—Data rate can be changed when there are active circuits and DCC connections

The data rate on a 15454 or 15310 node that uses ONS-SE-Z1 pluggables can be changed while there are active circuits and DCC connections. This issue will be resolved in a future release.

Path Protection

This section documents caveats for Path Protection in Release 8.5. 4.

CSCta44268—In ADM10G, for UPSR protected circuits on STSs greater than 3, traffic hit of around 2000ms is observed

In ADM10G, for UPSR protected circuits on STSs greater than 3, traffic hit of around 2000ms is observed, when the card reboots with traffic switched to protect due to defects on working. The conditions are:

1. Create UPSR protected Circuit on STS > 3 on Optical ports of ADM10G.

2. Inject defect on working such that traffic switches to protect

3. Reboot the ADM10G card. A traffic hit of around 2000ms is observed during reboot of card.

This issue will be resolved in a future release.

CSCsv30593— AIS-V alarm does not clear

The AIS-V alarm does not clear on VT1.5 cross connect circuits under the following conditions:

1. Create a VT1.5 path protected circuit.

2. Raise an SF-P alarm by injecting path errors.

3. AIS-V alarm is raised on the VT1.5 circuit.

4. Change the circuit state from IS to OOS-MT or OOS-DSBLD.

5. Change the circuit state back to IS.

6. Clear the SF-P alarm, the AIS-V alarm does not clear.

The workaround is to soft reset the cross connect card. This issue will be resolved in a future release.

TL1

This section documents caveats for TL1 in Release 8.5. 4.

CSCsv45464—The rtrv-ochnc command with access identifier (aid) =all, does not return any information about the existing cross connections

The rtrv-ochnc command with the access identifier (aid) =all, does not return any information about the existing cross connections. The workaround is to provide the rtrv-ochnc command with aid = LINEWL-x-all, where x is the slot number in which the 40-WXC card is provisioned. This issue will be resolved in a future release.

CSCsv71398—The RTRV-MOD command displays LBC and OPT parameters with invalid values

The RTRV-MOD command displays LBC and OPT parameters with invalid values for pluggables that do not support these values. The workaround is to use CTC. This issue will be resolved in a future release.

CSCsz81750—Traffic loss for 50 ms on MXPP-MR2.5G and TXPP-MR-2.5G cards

Traffic loss for 50 ms on MXPP-MR2.5G and TXPP-MR-2.5G cards under the following conditions:

1. Splitter protection with protect active.

2. Manual reset of the card causes traffic loss.

This issue will be resolved in a future release.

Resolved Caveats for Release 8.5.4

This section documents caveats resolved in Release 8.5.4.

Alarms

This section documents resolved caveats for Alarms in Release 8.5.4.

CSCta72945—SWMTXMOD Alarm on MRC Cards

Frequent and continuous side switching of the XC-VT cards result in SWMTXMOD alarm on the MRC cards. This issue has been resolved.

CSCsz84817—High Laser bias and Rx power alarms seen on Finisar XFP

High Laser bias and Rx power alarms are seen on the finisar XFP. The alarms do not clear even after replugging the XFP. Continous I2C errors are seen on the console. This issue has been resolved.

CSCta72945—SWMTXMOD Alarm on MRC Cards

Frequent and continuous side switching of the XC-VT cards result in SWMTXMOD alarm on the MRC cards. This issue has been resolved.

CSCsy69110—ADD Port Alarm not Raised

Add Port alarm is not raised on ports 27 and 23 of 40-WSS card when the 40-WSS card is inserted in slot 3 of an SDH shelf. This issue has been resolved.

CSCsz67629—On E1-42 protection switching, LOS alarms on ports 23 and 27 are cleared

When all the ports of E1-42 card are moved to IS state, the LOS alarm is reported against all ports as expected. On E1-42 protection switching, the LOS alarms on ports 23 and 27 are cleared. This issue has been resolved.

Common Control Cards

This section documents resolved caveats for Common Control Cards in Release 8.5.4.

CSCsx37297—FTP port issue for TCP connect scan

The following issues occur when the FTP server of TCC card blocks the external FTP socket because of execution of port scanners:

•Line cards does not boot

•Software download to the node fails

•Database sync between Active and Standby TCC cards fail

This issue has been resolved.

CSCsy91761—Constant TCC Reset

When a node with DS3XM-12 having multiple portless DS3s in the terminal loopback is upgraded, there is constant TCC reset after activation and the upgrade fails. This issue has been resolved.

CSCsz39798—Constant TCC Reboot

When the DS3XM12 or DS3XM6 port transitions from the AINS state to IS state, TCC reboots constantly. This issue has been resolved.

CSCsz08846—Generation of two Contradictory Logs

When the value of LI Timer value on the CE-MR card is modified, the audit logs generated are contradictory. There re are two logs for one event—Pass/Compld and Fail/Deny. Even if the values are valid, two logs are generated. This behavior is unexpected as only one log should be generated. This issue has been resolved.

CSCsz81891—Issue in Database Partitions not Reported

When there is any problem in the database partitions of the compact flash, the problem is not reported unless a provisioning change is attempted. This issue has been resolved.

CTC

This section documents resolved caveats for CTC in Release 8.5.4.

CSCsx81421—Trouble to Manage SoTL1 Tunnels using CTC

There are multiple SoTL1 tunnels provisioned using CTC. Trying to open or close a particular tunnel from CTC is not possible in certain scenarios. This issue has been resolved.

CSCsy74949—Incorrect NE Default Values Downloaded

When using the re-init tool to upgrade a node from Release 6.2.2 to Release 8.5.4, incorrect NE default values are downloaded. This issue has been resolved.

CSCsy82228—CTC Network discovery is slow

CTC Network discovery is very slow when it is disabled and NEs are added one at a time. This issue has been resolved.

CSCsw96807—PPC cannot be deleted in secure mode node

PPCs cannot be deleted if one of the ends is a secure mode node. This issue has been resolved.

CSCsm85843—CTC displays the STS circuit in ROLL_PENDING state when a bridge and roll is Performed

The Circuit tab in CTC displays the STS circuit in the ROLL_PENDING state when a Bridge and Roll is performed under the following conditions:

1. Starting a Bridge and Roll on an STS circuit that is on the only circuit bearing port on a MRC card or a fixed rate card.

2. During a manual Bridge and Roll, performing the COMPLETE step but not the FINISH step.

3. Deleting the fixed rate card or the port or PPM on the MRC card.

The Roll object still exists on the node even though the parent object is deleted and no pool for the rollFrom Path field exits in the Roll Object database. The Circuit tab in CTC will display the circuit in the ROLL_PENDING state and the Roll tab will not have an entry to finish the roll. The workaround is to complete all the steps of the ROLL process including the FINISH step. This issue has been resolved.

CSCsq73116—PPC is not working on secure mode node

When a PPC terminating on a secure mode node is created, a new "unknown" node appears and the PPC is not shown on the network map. This issue has been resolved.

CSCsr01562— PPC Links Disassembled

When a node configured with TXP card on a Cisco ONS 15454 DWDM platform without any DDC,GCC, and OSC terminations is moved from normal to secure mode, the PPC links created between the two nodes are disassembled. The two ends of each PPC link are reported as two separate lines in the PPC patchcord terminations list, with each second end point reported as unknown. This issue has been resolved.

Data I/O Cards

This section documents resolved caveats for Data I/O Cards in Release 8.5.4.

CSCta44387—UNEQ-P does not trigger link integrity on CCAT circuits

When UNEQ-P condition is raised on CE-100T-8 card with CCAT circuits provisioned and link integrity timer enabled, the far-end Ethernet port does not go down. This issue has been resolved.

CSCsl65143—Traffic outage on G1K and G1000 cards

A SONET/SDH error, that is 50 ms more than the configured link integrity soak timer, causes traffic outage of about 5 sec occurs on G1K and G1000 cards connected to the Cisco Catalyst 6000 switch with auto negotiation enabled. This issue has been resolved.

CSCtc66943—Link does not come up when autonegotiation is enabled

The link fails to come up when the CE-1000-4 card and the HP ProCurve Switch are connected, and autonegotiation is enabled on both ends of the circuit. This issue has been resolved.

DWDM

This section documents resolved caveats for DWDM in Release 8.5.4.

CSCsj97288—PROV-MISMATCH alarm raised on TXP_MR_10E Card

The PROV-MISMATCH alarm is raised on the TXP_MR_10E card using the ONS-XC-10G-L2 XFP module, when ZR (zero reach) is provisioned for 10GE. This issue has been resolved.

CSCsq78337—Cannot provision ONS-SE-G2F-LX= SFP for ISC3

Cannot provision ONS-SE-G2F-LX= SFP (PID 10-2273-02) on a TXP-MR-2.5G card for ISC3. This issue has been resolved.

Electrical I/O Cards

This section documents resolved caveats for Electrical I/O Cards in Release 8.5.4.

CSCsl81293—Traffic loss on DS1 card

Traffic is lost on the VT circuit DS1 card inside a portless circuit when changing backplane capacity from STS12 to STS48 mode. This issue has been resolved.

CSCsu92843—BERT on DS3-XM12 card does not inject bit errors

BERT on DS3-XM12 card does not inject bit errors. This issue has been resolved.

CSCsz59607—Traffic drops on DS3-XM card when Signal Degrade alarm threshold is cleared

Traffic drops on DS3 port of DS3-XM card when Signal Degrade alarm threshold is cleared. This issue has been resolved.

CSCta24511—LoF on DS3-XM6 card does not cause DS1 AIS

When LoF is raised on DS3-XM6 card does not cause AIS condition on DS1 card at destination. This issue has been resolved.

CSCta24511—LoF on DS3-XM6 card does not cause DS1 AIS

When LoF is raised on DS3-XM6 card does not cause AIS condition on DS1 card at destination. This issue has been resolved.

Hardware

This section documents resolved caveats for Hardware in Release 8.5.4.

CSCsm55562—Payload PM not reported on active gigabit Ethernet port when CARLOSS is raised

When Loss of Signal or Loss of Sync is raised on MXP-MR-10DME gigabit Ethernet port, the payload PM is not updated. This issue has been resolved.

Optical I/O Cards

This section documents resolved caveats for Optical I/O Cards in Release 8.5.4.

CSCta42253—MRC card remains in OOF state

MRC card remains in OOF state when OC-48 SFP is used in port 1. This issue has been resolved.

CSCsv54817—UNEQ-P alarm is raised on STS-96c circuits with OC-192 XFP

The UNEQ-P alarm is raised on STS-96c circuits when STS-96c circuit is provisioned with one end of circuit on OC-192XFP card or using OC-192XFP as trunk card. This issue has been resolved.

Path Protection

This section documents resolved caveats for Path Protection in Release 8.5.4.

CSCsy26595—Traffic does not recover after active and protect paths fail

Traffic does not recover after both the active and protect paths in a ring fail. This issue has been resolved.

CSCsx17026—Traffic on Protect Path not Restored

Traffic on protect path is not restored after the circuit state transitions from IS to OOS-DSBLD and OOS-DSBLD to IS. This issue has been resolved.

CSCsk46370—Error Rate Injection non functional

The error rate injection does not work in 1:N or 1:1 protection group of DS3-XM12 or DS1-E156 cards. This issue has been resolved.

CSCsz06764—SF-V condition does not clear

When the circuit state is changed from IS->OOS,DSBLD->IS with the SF-V condition present on the VT UPSR destination working path, the SF-V condition does not clear on the protect path. This issue has been resolved.

CSCsw49064—GR3 protection is not triggered by SD or SF alarms on trunk ports

GR3 protection is not triggered by SD/SF alarms on trunk ports under the following conditions:

1. Configure a GR3 protection on a ring of muxponder cards.

2. Generate an SF or an SD on a trunk. The protection is not triggered.

This issue has been resolved.

New Features and Functionality

This section documents new software features in Cisco ONS 15454 Software Release 8.5.4.

Link Integrity Soak Timer

All the mapper cards (G1000-4, CE-1000-4, CE-100-8, and CE-MR-10 cards supported on Cisco ONS 15454 platform) support end-to-end Ethernet link integrity. If any part of the end-to-end path fails, the mapper card soaks the defect for a fixed duration of 200 ms. In certain network configurations, the restoration time after a protection switch can be more than 200 ms. Such disruptions necessitates that the link integrity be initiated at an interval greater than 200 ms.

The Link Integrity Soak Timer enhancement allows you to configure link integrity soak timer on per port basis. To allow link integrity to be initiated at an interval greater than 200 ms, set the link integrity timer in the range between 200 and 10000 ms, in multiples of 100 ms.

The Link Integrity Disable enhancement allows you to disable support for end-to-end Ethernet link integrity on a per port basis.

---

Note When the link integrity timer value on CE-1000-4 card with VCAT circuit is more than 1400 ms, the transition from IS > OOS > IS causes a delay of 1100 ms.

---

TL1 Gateway and ENE Sessions

The Cisco ONS 15454 Software Release 8.5.4 increases the maximum number of ENE sessions over a OSI DCC from 20 to 176. If you use a combination of IP and OSI ENE sessions, it is important to remember that the maximum number of ENEs supported per GNE is equal to the maximum number of IP ENEs.

Related Documentation

Release-Specific Documents

•Release Notes for the Cisco ONS 15454, Release 8.5.3

•Release Notes for the Cisco ONS 15454 SDH, Release 8.5.4

•Release Notes for the Cisco ONS 15310-MA SDH, Release 8.5.4

•Release Notes for the Cisco ONS 15310-MA, Release 8.5.4

•Cisco ONS 15454 Software Upgrade Guide, Release 8.5.x

Platform-Specific Documents

•Cisco ONS 15454 Procedure Guide
Provides installation, turn up, test, and maintenance procedures

•Cisco ONS 15454 Reference Manual
Provides technical reference information for SONET/SDH cards, nodes, and networks

•Cisco ONS 15454 DWDM Installation and Operations Guide
Provides technical reference information for DWDM cards, nodes, and networks

•Cisco ONS 15454 Troubleshooting Guide
Provides a list of SONET alarms and troubleshooting procedures, general troubleshooting information, transient conditions, and error messages

•Cisco ONS SONET TL1 Command Guide
Provides a comprehensive list of TL1 commands

•Cisco ONS SONET TL1 Reference Guide
Provides general information, procedures, and errors for TL1

•Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide
Provides software feature and operation information for Ethernet cards

Obtaining Optical Networking Information

This section contains information that is specific to optical networking products. For information that pertains to all of Cisco, refer to the Obtaining Documentation and Submitting a Service Request section.

Where to Find Safety and Warning Information

For safety and warning information, refer to the Cisco Optical Transport Products Safety and Compliance Information document that accompanied the product. This publication describes the international agency compliance and safety information for the Cisco ONS 15454 system. It also includes translations of the safety warnings that appear in the ONS 15454 system documentation.

Cisco Optical Networking Product Documentation CD-ROM

Optical networking-related documentation, including Cisco ONS 15xxx product documentation, is available in a CD-ROM package that ships with your product. The Optical Networking Product Documentation CD-ROM is updated periodically and may be more current than printed documentation.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.

This document is to be used in conjunction with the documents listed in the "Related Documentation" section.

Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

© 2010 Cisco Systems, Inc. All rights reserved.