|
|
Table Of Contents
Release Notes for Cisco ONS 15530
for Cisco IOS Release 12.1(10)EV4Determining the Software Version
New Features in Release 12.1(10)EV4
Obtaining Technical Assistance
Release Notes for Cisco ONS 15530
for Cisco IOS Release 12.1(10)EV4
This document describes caveats for Cisco IOS Release 12.1(10)EV4 for the Cisco ONS 15530.
Date: December 9, 2002
Text Part Number: OL-2508-03
Contents
This document includes the following information:
•
Caveats
•
•
Introduction
The Cisco ONS 15530 is a modular, scalable optical switching and aggregation platform designed to supplement the Cisco ONS 15540 ESP. With the Cisco ONS 15540 ESP, users can take advantage of the availability of dark fiber to build a common infrastructure that supports data, SAN (storage area network), and TDM (time-division multiplexing) traffic. For more information about DWDM technology and applications, refer to the Introduction to DWDM Technology publication and the Cisco ONS 15530 Planning Guide.
System Requirements
This section describes the system requirements for Cisco IOS Release 12.1(10)EV4 and includes the following sections:
•
Memory Requirements
The DRAM memory configuration is 64 MB, which is the default for the Cisco ONS 15530.
Hardware Supported
Table 1 lists the hardware components supported on the Cisco ONS 15530 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 15530 system, log in to the system and enter the show version EXEC command. The following sample output is from the show version command. The software version number is shown on the second line of the sample output.
Switch# show versionCisco Internetwork Operating System SoftwareIOS (tm) ONS-15530 Software (ONS15530-I-M), Version 12.1(10)EV4
<Information deleted>Upgrading the System Image
To ensure proper system functioning, follow the system image upgrading procedure described in the Cisco ONS 15530 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 15530.
Table 2 Feature Sets Supported by the Cisco ONS 15530
In-band message channel
X
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
Coupling link
X
Fibre Channel (1 Gbps)
X
Fibre Channel (2 Gbps)
X
FDDI4
X
ESCON5 aggregation (2.5 Gbps)
X
FICON6 (800 Mbps)
X
Token Ring
X
SNMP
X
CiscoView
X
Cisco Transport Manager
X
IP packets
X
OSCP7
X
APS8 channel protocol
X
Point-to-point
X
Hubbed ring
X
Meshed ring
X
Sysplex
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 OSCP = Optical Supervisory Channel Protocol
8 APS = Automatic Protection Switching
New and Changed Information
This section lists new features that appear in this and previous releases of Cisco IOS Release 12.1. The new features are sorted by release number.
New Features in Release 12.1(10)EV4
No new features are available for the Cisco ONS 15530 in Cisco IOS Release 12.1(10)EV4.
Caveats
This section lists the caveats for the12.1(10)EV4 release. Use Table 3 to determine the status of a particular caveat. In the table, "C" indicates a corrected caveat, and "O" indicates an open caveat.
Table 3 Caveat Matrix for the Cisco ONS 15530
C
C
O
O
C
C
C
C
C
C
C
C
O
C
C
O
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
O
C
C
C
O
C
C
O
C
C
C
C
C
C
C
C
O
C
C
C
C
C
C
O
C
C
O
C
This section describes the caveats in the Cisco ONS 15530.
Symptom: Unchecked buffer boundary in NTP.
Workaround: None.
Symptom: When the NME is connected to an auto-sensing switch/hub, going from 10 Mbps/half to 100 Mbps/half (or similarly 10 Mbps/full to 100 Mbps/full) on FastEthernet0 results in the link going down.
Workaround: Configure FastEthernet0 as duplex auto and speed auto.
Symptom: A change in optical threshold condition at a WB-VOA or PB-OE module power monitor may not be detected if the condition is temporary and does not last for more than a second.
Workaround: None
Symptom: When swapping the ESCON line card with the 10-G ITU trunk line card in a given slot, the following error message is seen four times:
%BPE-3-NOT_REGISTERED: Interface[EthernetDcc9/0/0] MAC is not registered.
Workaround: None.
Symptom: The CPU switch module LED for alarms is not cleared even though the Optical Power Monitoring alarm gets cleared. There is no functionality problem. On a CPU switch module switchover this alarm LED is cleared and gives the correct alarm status.
Workaround: OIR the card on which the alarm was generated.
Symptom: When both wavepatch interfaces are in an administrative down state, a low alarm does not appear on the standby wavepatch interface after a no shutdown is done on the wave interface.
Workaround: Do a shutdown and a no shutdown command sequence on the interface; the low alarm is then reported for this interface.
Symptom: Interface reports up/up even when there is no light source connected.
Workaround: Perform a shut and then a no shut on the interface.
Symptom: A transparent interface carrying Gigabit Ethernet traffic and configured with gigabit Fibre Channel encapsulation shows good quality signal on the show interfaces transparent command output and does not assert any ingress alarms. The wave interface assert loss of lock and loss of sync alarms.
Workaround: Remove and reinsert the transponder module to bring it to the correct state.
Symptom: LoF (loss of frame) alarms are not reasserted after a shutdown/no shutdown command sequence on both the transparent and wave interfaces on the transponder module.
Workaround: Disable and reenable monitoring on the transparent interface to reassert the alarms.
Symptom: The show facility-alarm command status does not report existing LoF/LoSync/LoLock alarms after
OIR/hw-mod power off/on.
Workaround: Disable and enable monitoring back will reassert existing alarms in the show facility-alarm status.
Symptom: A software compatibility problem causes the active CPU switch module to reset the standby CPU switch module.
Workaround: None.
Symptom: The show hardware command output displays information about the CPU switch module that has been removed from the system.
Workaround: None.
Symptom: OSC wave and ethernetdcc interfaces come up with default traffic-shaping parameters. Since this is considered as default, on removing the configuration using the no form of the command, the parameter value should revert back to the default value, which is not being done.
Workaround: Reconfigure the traffic-shaping parameters.
Symptom: If a line card that was removed prior to switchover is inserted during switchover, the line card may not come up properly.
Workaround: Insert the line card after switchover is complete.
Symptom: The system crashes at is_optical_ifstatus_up.
Workaround: None.
Symptom: Performing a shutdown command on the active wavepatch interface of a nonsplitter card brings the waveethernetphy interface down and reports "Loss of Light" in the output of the show interface command, but the traffic continues to flow.
Workaround: If the intent is to stop traffic, do a shutdown on the waveethernetphy interface.
Symptom: Following a CPU switch module crash and switchover, the show redundancy command shows "Not known", without any additional information.
Workaround: Enter show version from the standby CPU switch module console to see the additional information.
Symptom: The getnext and getbulk commands do not function properly after a CPU switch module switchover.
Workaround: None.
Symptom: APS traps mode mismatch takes 30 minutes for completion.
Workaround: None.
Symptom: Low alarm is not cleared on the wavepatch interface for the transponder.
Workaround: Perform a shutdown/no shutdown command sequence on the wavepatch where it is seen.
Symptom: CVRD, CRC or CDL HEC error counters are not incremented, but the CDL HEC SF condition is exceeded.
Workaround: None.
Symptom: When trying to modify cApsConfigSpan through SNMP set to an unsupported value, no error is reported.
Workaround: None.
Symptom: Alarms are created on the wave interface by pulling out the cable.
Workaround: The shutdown command will clear all of the alarms on the wave interface.
Symptom: Spurious memory access is seen when issuing the show tech command on the standby CPU switch module; the show align command shows an increase in the spurious memory errors after each show tech command is issued.
Workaround: None
Symptom: PTOPO configuration rows can be configured for nonexistent interfaces.
Workaround: None.
Symptom: The show connect intermediate command output does not display all the protection paths when a switch fabric cross connect is used.
Workaround: Display the information using the show connect command.
Symptom: Active CPU switch module incorrectly detects a faulty switch fabric port, causing a switchover to the standby CPU switch module.
Workaround: None.
Symptom: When copying or reading a file to or from Compact flash (disk0), a transient error with the following message may appear and read/write access to compact flash is terminated:
ATA_Status timeout waiting for <1/2/3>
Workaround: None.
Symptom: Defect-indication error message does not give information if the defect-indication bit was cleared or asserted for that interface.
Workaround: None.
Symptom: Some interfaces are not be available to the NMS station since the agent does not create them on OIR.
Workaround: Reload the box after removal/insertion of the cards.
Symptom: APS message channel configured for UDP/IP does not work over two IP hops. The UDP/IP packets get dropped at the end of the second hop.
Workaround: None.
Symptom: Switch fabric protection is not disabled if the nonactive CPU switch module is in ROM monitor mode. As a result if an RxFail is noticed on any fabric port, that fabric port will switch over its receive to the nonactive CPU switch module.
Workaround: None.
Symptom: The redundancy reload shelf command on the active CPU switch module can cause a switchover if the peer CPU switch module is in ROM monitor mode.
Workaround: Use the reload command to reload the active CPU switch module, if the peer CPU switch module is in ROM monitor mode.
Symptom: Issuing getbulk command to retrieve PM parameters returns 0 row.
Workaround: None.
Symptom: The ciscoFlashPartitionFileCount returns an incorrect number of files on the flash card.
Workaround: None.
Symptom: ciscoFlashDeviceChangeTrap should be supported on ONS155xx platforms since it is a basic operation. Whenever a removable flash device is removed or inserted, this trap should be generated.
Workaround: None.
Symptom: When FLC is disabled on all 10 esconphy ports and they are administratively shut down, packets are still being sent to the backplane.
Workaround: None.
Symptom: OPM feature does not work for nonsplitter transponders.
Workaround: None.
Symptom: Invalid mac-address or ip-address can be made via SNMP. No error check is done.
Workaround: Delete the entry through SNMP or with the topology neighbor disable command.
Symptom: Egress Loss of Signal alarm is not reasserted in the show facility alarm status output after the hardware module power is turned off and turned back on.
Workaround: None.
Symptom: The wave interface remains down when the signal quality is GOOD, after the hardware module power is turned off and turned back on.
Workaround: None.
Symptom: When wave interface is in SHUT mode, the corresponding active wavepatch interface is brought down and a low alarm is asserted.
Workaround: None.
Symptom: When IOS is rebooted on a system and a transient link failure condition occurs on 10 G DWDM Uplink cards, system may continuously send the backward defect indication.
Workaround: None.
Symptom: The wavepatch interfaces are stuck in the down state after using the show wave interface command with splitter APS after the trunk fiber has been cut.
Workaround: None.
Symptom: After a fiber cut, the OSC interface remains up with signal quality good.
Workaround: Use the shut/no shut command.
Symptom: The standby CPU switch module can get stuck in trying to register control ports.
Workaround: Enter redundancy reload peer on the active CPU switch module.
Symptom: In bidirectional APS, if both NEs have the same priority request, the master/slave determination fails, leading to both claiming the control and resulting in not sending a REVERSE-REQUEST.
Workaround: None.
Symptom: When a shutdown/no shutdown command sequence is done on a waveethernetphy interface that is in the UP state, the Signal Condition shows Loss of Lock.
Workaround: None.
Symptom: In bidirectional line card protection, if the APS group is associated with working cross connect invalid and protection cross connect 'active', APS erroneously sets the aps channel request on working to WAIT-TO-RESTORE. This does not recover even when the working cross connect is made dormant by the connection manager. As a result both NEs are pegged to protection until an event (that has higher priority than WTR) is triggered.
Workaround: None.
Symptom: Splitter APS protection comes up as active on bootup.
Workaround: None.
Symptom: Dynamic discovery of topology via CDP on the tengigethernetphy interface is not configurable.
Workaround: None.
Symptom: In a preconfigured APS group (for the case when the interfaces do not exist), if the group is configured for revertive mode, it cannot be enabled.
Workaround: None.
Symptom: The CPU switch module crashes after midnight with optical performance on when an interface capable of performance monitoring is not shut down.
Workaround: None.
Symptom: In unidirectional revertive APS, after OIR removal followed by OIR insertion of working and protection elements on both NEs, the active signal may be received from the Protection line instead of working line.
Workaround: Do a manual or force switch to working line.
Symptom: When an invalid channel number is detected by the OSCP client while it processes the client message received from the peer, OSCP does not free the message buffer. This results in buffer starvation over a period of time and connectivity via the network management interface and back plane ethernet (IPC and OSCP) interface are lost.
Workaround: None.
Symptom: SEF errors are repeatedly asserted on the console and are not soaked.
Workaround: None.
Symptom: When an interface is shut down administratively, the show aps detail command shows the channel request as sf-lp; however, a get on the object cApsChanStatusCurrent does not reflect sf-lp in the corresponding bits.
Workaround: None.
Symptom: Connection to a different subinterface on the same 10-Gbps ITU trunk card is accepted, but crossconnection fails in the switch fabric.
Workaround: None.
Symptom: APS group is displayed as "not associated" in show aps detail command output.
Workaround: Do a shutdown/no shutdown command sequence to either or both interfaces in the APS group. This causes a state change of the interfaces. You can also do a disable/enable to the APS group.
Symptom: Y-cable transponder protection does not come up as active after removing lockout.
Workaround: Do a disable/enable to the APS group.
Symptom: With line card protection configured, the switch fabric on both the active CPU switch module and the standby CPU switch module are out of sync.
Workaround: Insert all the cards and perform a no connect command and then connect command.
Symptom: CDR loss of lock is not reported after Sysplex CLO/ETR encapsulation on a transparent interface.
Workaround: Perform a shutdown/no shutdown command sequence on the interface will correct the CDR loss of lock reporting.
Limitations and Restrictions
This section provides limitations and restrictions for Cisco ONS 15540 ESP hardware and software.
•
Note
Related Documentation
Refer to the following documents for more information about the Cisco ONS 15530:
•
•
•
•
•
•
•
•
•
•
•
•
•
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 priority level 1 or priority level 2 issues. 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 automatically opens a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this 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). When you call the center, please have available your service agreement number and your product serial number.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
CCIP, the Cisco Arrow logo, the Cisco Powered Network mark, the Cisco Systems Verified logo, Cisco Unity, Follow Me Browsing, FormShare, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, Networking Academy, ScriptShare, SMARTnet, TransPath, and Voice LAN are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That's Possible, The Fastest Way to Increase Your Internet Quotient, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, Fast Step, GigaStack, Internet Quotient, IOS, IP/TV, LightStream, MGX, MICA, the Networkers logo, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, SlideCast, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.
All other trademarks mentioned in this document or Web site 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. (0208R)
Posted: Tue Jun 8 12:11:53 PDT 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
