|
|
Table Of Contents
Release Notes for Cisco ONS 15540 ESPx
for Cisco IOS Release 12.1(10)EVDetermining the Software Version
Obtaining Technical Assistance
Release Notes for Cisco ONS 15540 ESPx
for Cisco IOS Release 12.1(10)EV
This document describes caveats for Cisco IOS Release 12.1(10)EV for the Cisco ONS 15540 ESPx.
Date: July 8, 2002
Text Part Number: OL-2266-01
Contents
This document includes the following information:
•
Caveats
•
•
Introduction
The Cisco ONS 15540 ESPx is an optical transport platform that employs DWDM (dense wavelength division multiplexing) technology. With the Cisco ONS 15540 ESPx, users can take advantage of the availability of dark fiber to build a common infrastructure that supports data, SANs (storage area networks), and TDM (time-division multiplexing) traffic. The system uses an enhanced chassis with front fiber-optic cable access for optical interconnections between transponders and optical mux/demux modules. For more information about DWDM technology and applications, refer to the Introduction to DWDM Technology publication and the Cisco ONS 15540 ESPx Planning and Design Guide.
System Requirements
This section describes the system requirements for Cisco IOS Release 12.1(10)EV, and it includes the following sections:
•
Memory Requirements
The DRAM memory configuration is 128 MB, which is the default for the Cisco ONS 15540 ESPx.
Hardware Supported
Table 1 lists the hardware components supported on the Cisco ONS 15540 ESPx and the minimum software version required. See the "Determining the Software Version" section for information on determining your software version.
Determining the Software Version
Note
To determine the version of Cisco IOS software currently running on a Cisco ONS 15540 ESPx system, log in to the system and enter the show version EXEC command.
Upgrading the System Image
To ensure proper system functioning, follow the system image upgrading procedure described in the Cisco ONS 15540 ESPx Software Upgrade Guide.
Note
Caution
Feature Set Table
The Cisco IOS Release software is packaged in feature sets (also called software images) depending on the platform. Each feature set contains a specific set of Cisco IOS features. Table 2 lists the Cisco IOS software feature sets available for the Cisco ONS 15540 ESPx.
Table 2 Feature Sets Supported by the Cisco ONS 15540 ESPx
Gigabit Ethernet
X
Fast Ethernet
X
Ethernet
X
ATM OC-3/STM-1, OC-12/STM-4, and OC-48/STM-16
X
X
POS3
X
Fibre Channel (1 Gbps)
X
Fibre Channel (2 Gbps)
X
FDDI4
X
ESCON5 SM (200 Mbps)
X
FICON6 (800 Mbps)
X
Token Ring
X
SNMP
X
CiscoView
X
Cisco Transport Manager
X
CDP7
X
IP packets
X
OSCP8
X
APS9 protocol packets
X
Point-to-point
X
Hubbed ring
X
Meshed ring
X
Sysplex
X
GDPS10
X
Unidirectional path switching
X
Bidirectional path switching
X
1 SONET = Synchronous Optical Networking
2 SDH = Synchronous Digital Hierarchy
3 POS = Packet over SONET
4 FDDI = Fiber Distributed Data Interface
5 ESCON = Enterprise Systems Connection
6 FICON = Fiber Connection
7 CDP = Cisco Discovery Protocol
8 OSCP = Optical Supervisory Channel Protocol
9 APS = Automatic Protection Switching
10 GDPS = Geographically Dispersed Parallel Sysplex
Caveats
This section lists the caveats and corrected caveats for each release. Use Table 3 to determine the status of a particular caveat. In the tables, "C" indicates a corrected caveat, and "O" indicates an open caveat.
This section describes the caveats in the Cisco ONS 15540 ESPx.
Symptom: When there is a constant stream of loss of sync alarms, a port fail notification is not generated.
Although both signal failure and signal degrade thresholds are applied, only signal degrade is observed. The signal failure threshold is monitored by hardware registers. When the signal failure threshold is exceeded, the hardware normally generates a port fail notification. Because the loss of sync alarms are constant, the threshold exceeded cannot generate a port fail notification. The signal degrade is reported because it is monitored by software and does not need any notifications from hardware.
Workaround: Disable and reenable monitoring once with the no monitor/monitor enable command sequence to generate the port fail notification.
Symptom: The SRC reprogram for the standby processor card fails.
Workaround: Run the SRC reprogram on the active processor card, enable the processor switchover after switchover, and then run the SRC reprogram on the new active processor card. Remove and reinsert the processor card for the new FPGA to become effective.
Symptom: Loss of signal might occur before SD (signal degrade) and SF (signal failure) thresholds are exceeded and traffic may still continue to pass transparently.
The loss of signal detection is taken from the OE (optical to electrical) conversion subsystem which is different from the source of the SD and SF counters. The loss of light sensitivity is a characteristic of the OE conversion unit and it may vary from unit to unit but is always < -30dBm.
Workaround: None.
Symptom: When the Rx port fiber is removed from the transponder module, ingress alarms are reported and cleared repeatedly. The alarm should not clear and the alarm should be reported only once.
Workaround: None
Symptom: Processor card gets into a nonresponsive state.
Workaround: None
Symptom: Processor card gets into a nonresponsive state for an extended interval, during which time the active/standby LEDs may not indicate the correct active/standby state.
Workaround: If the processor card has not been reset by the redundant processor card, the non-responsive processor card can be removed and re-inserted in the chassis. This may cause a brief hit to data traffic, but the redundant processor card should take over and bring the system back up.
Symptom: The encapsulation fastethernet command fails on multimode transponders. The clock rate 100000 command succeeds but then pings over the signal fail intermittently.
Workaround: None.
Symptom: The show interface command output for a wave interface displays an "up" state but the Signal Quality shows loss of sync.
Workaround: None.
Symptom: CiscoView might display a different receive LED status on transponders from what is actually seen on the device.
Workaround: None.
Symptom: Client transmit enabled upon insertion disrupts y-cable clients.
Workaround: Remove client transmit fiber (y-cable leg) from the standby transponder before reinserting. Connect it back a few seconds after re-insertion of the standby transponder.
Symptom: The first time you OIR the OSC linecard, the card is brought admindown state.
Workaround: Enter the no shutdown command when the interface recovers.
Limitations and Restrictions
This section contains limitations and restrictions that apply to the Cisco ONS 15540 ESPx.
Transponder Modules
This section contains limitations and restrictions that apply to transponder modules.
•
•
Data errors or link-down conditions for 2-Gbps Fibre Channel might occur when used with certain client laser sources. Transmitters in some client GBIC and SFP transceiver units might send large overshoots in optical power with signal bit transitions, causing momentary overload conditions on the transponder client side receiver. The average transmitted power level from the GBIC does not violate the overload specification of the transponder client side receiver, so a power meter does not detect the overload.
The workaround is to attenuate the signal from the client equipment to a recommended level of -12 dBm when transmitting 2-Gbps Fibre Channel services.
•
–
–
–
–
Note
Related Documentation
Refer to the following documents for more information about the Cisco ONS 15540 ESPx:
•
•
•
•
•
•
•
Obtaining Documentation
The following sections explain how to obtain documentation from Cisco Systems.
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at the following URL:
Translated documentation is available at the following URL:
http://www.cisco.com/public/countries_languages.shtml
Documentation CD-ROM
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.
Ordering Documentation
Cisco documentation is available in the following ways:
•
http://www.cisco.com/cgi-bin/order/order_root.pl
•
http://www.cisco.com/go/subscription
•
Documentation Feedback
If you are reading Cisco product documentation on Cisco.com, you can submit technical comments electronically. Click Leave Feedback at the bottom of the Cisco Documentation home page. After you complete the form, print it out and fax it to Cisco at 408 527-0730.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:
Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.
Cisco.com
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you to
•
•
•
•
•
You can self-register on Cisco.com to obtain customized information and service. To access Cisco.com, go to the following URL:
Technical Assistance Center
The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two types of support are available through the Cisco TAC: the Cisco TAC Web Site and the Cisco TAC Escalation Center.
Inquiries to Cisco TAC are categorized according to the urgency of the issue:
•
•
•
•
Which Cisco TAC resource you choose is based on the priority of the problem and the conditions of service contracts, when applicable.
Cisco TAC Web Site
The Cisco TAC Web Site allows you to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to the following URL:
All customers, partners, and resellers who have a valid Cisco services contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to the following URL to register:
http://www.cisco.com/register/
If you cannot resolve your technical issues by using the Cisco TAC Web Site, and you are a Cisco.com registered user, you can open a case online by using the TAC Case Open tool at the following URL:
http://www.cisco.com/tac/caseopen
If you have Internet access, it is recommended that you open P3 and P4 cases through the Cisco TAC Web Site.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses issues that are classified as priority level 1 or priority level 2; these classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer will automatically open a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to the following URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled; for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). In addition, please have available your service agreement number and your product serial number.
Posted: Tue Jun 8 13:04:20 PDT 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
