|
|
Table Of Contents
Release Notes for Cisco ONS 15530
for Cisco IOS Release 12.2(22)SV1Determining the Software Version
New Features in Release 12.2(22)SV
New Features in Release 12.2(18)SV2
New Features in Release 12.2(18)SV1
New Features in Release 12.2(18)SV
Resolved Caveats in Release 12.2(22)SV1
Open Caveats in Release 12.2(22)SV
Resolved Caveats in Release 12.2(22)SV
Resolved Caveats in Release 12.2(18)SV2
Resolved Caveats in Release 12.2(18)SV1
Resolved Caveats in Release 12.2(18)SV
Obtaining Technical Assistance
Obtaining Additional Publications and Information
Release Notes for Cisco ONS 15530
for Cisco IOS Release 12.2(22)SV1
This document describes caveats for Cisco IOS Release 12.2(22)SV1 for the Cisco ONS 15530.
Date: July 30, 2005
Text Part Number: OL-4891-04 Rev. C0 Rev C0
Contents
This document includes the following information:
•
Caveats
•
•
•
Introduction
The Cisco ONS 15530 is a DWDM multiservice aggregation platform that maximizes the carrying capacity of fiber by performing service aggregation of protocols such as ESCON, Fibre Channel, FICON, and Gigabit Ethernet. With the Cisco ONS 15530, users can take advantage of the availability of dark fiber to build a common infrastructure that supports data, SAN (storage area networking), 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 ONS 15530 IOS Release 12.2(22)SV 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.
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.2(22)SV <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.
You can find the system images for the Cisco ONS 15530 at the following URL:
http://www.cisco.com/kobayashi/sw-center/sw-optical.shtml
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
Inband message channel
12.1(10)EV2
Gigabit Ethernet
12.1(10)EV2
Fast Ethernet
12.1(10)EV2
Ethernet
12.1(10)EV2
ATM OC-3/STM-1, OC-12/STM-4, and OC-48/STM-16
12.1(10)EV2
12.1(10)EV2
POS3
12.1(10)EV2
IBM Sysplex coupling link
12.1(10)EV2
Fibre Channel (1 Gbps)
12.1(10)EV2
Fibre Channel (2 Gbps)
12.1(10)EV2
FDDI4
12.1(10)EV2
ESCON5 aggregation (2.5 Gbps)
12.1(10)EV2
FICON6 (800 Mbps)
12.1(10)EV2
FICON (1 Gbps)
12.1(12c)EV3
Token ring
12.1(10)EV2
SNMP
12.1(10)EV2
CiscoView
12.1(10)EV2
Cisco Transport Manager
12.1(10)EV2
IP packets
12.1(10)EV2
OSCP7
12.1(10)EV2
APS8 channel protocol
12.1(10)EV2
Point-to-point
12.1(10)EV2
Hubbed ring
12.1(10)EV2
Meshed ring
12.1(10)EV2
IBM Sysplex ETR/CLO9
12.1(10)EV2
1 Gbps Fibre Channel/FICON aggregation into 2.5 Gbps
12.1(12c)EV
1 Gbps IBM Sysplex Coupling Link aggregation into 2.5 Gbps
12.2(18)SV
Gigabit Ethernet aggregation (2.5 Gbps)
12.1(12c)EV
Buffer credits for 8-port FC/GE aggregation card
12.2(18)SV
2-Gbps Fibre Channel protocol monitoring on transponder line cards
12.2(18)SV
2-Gbps FICON protocol monitoring on transponder line cards
12.2(18)SV
Functional image version diagnostics
12.2(18)SV
Autonegotiation for Gigabit Ethernet between the 8-port FC/GE aggregation card and the client equipment
12.2(18)SV
ISC links peer mode aggregation (2.5 Gbps)
12.2(18)SV
2-Gbps ISC links peer mode protocol monitoring on transponder line cards
12.2(22)SV
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
9 ETR/CLO = external timer reference/control link oscillator
New and Changed Information
This section lists new features that appear in this and previous releases of Cisco IOS Release 12.2. The new features are sorted by release number.
New Features in Release 12.2(22)SV
The following new software feature is available for the Cisco ONS 15530 in Cisco IOS Release 12.2(22)SV:
•
New Features in Release 12.2(18)SV2
No new features are available for this release.
New Features in Release 12.2(18)SV1
No new features are available for this release.
New Features in Release 12.2(18)SV
The following new software features are available for the Cisco ONS 15530 in Cisco IOS Release 12.2(18)SV:
•
Note
•
•
•
Note
release 1.A3.•
•
•
•
•
Caveats
This section describes open and resolved severity 1 and 2 caveats and some severity 3 caveats. The "Open Caveats" section lists open caveats that apply to the current release and may apply to previous releases. The "Resolved Caveats" sections list caveats resolved in a particular release, but open in previous releases.
Resolved Caveats in Release 12.2(22)SV1
•
Cisco Internetwork Operating System (IOS) software is vulnerable to a Denial of Service (DoS) and potentially an arbitrary code execution attack from a specifically crafted IPv6 packet. The packet must be sent from a local network segment. Only devices that have been explicitly configured to process IPv6 traffic are affected. Upon successful exploitation, the device may reload or be open to further exploitation.
Cisco has made free software available to address this vulnerability for all affected customers.
More details can be found in the security advisory that is posted at http://www.cisco.com/warp/public/707/cisco-sa-20050729-ipv6.shtml.
Open Caveats in Release 12.2(22)SV
•
Symptom: The ethernetdcc interface loses connectivity when splitter protection is configured and the waveethernetphy interface is shut down while the protection wavepatch interface is active and the working wavepatch interface is down.
Workaround: Do not shut down the waveethernetphy interface when the working wavepatch interface is down.
•
Symptom: After booting the system, power coming out of the OSC module seems to be null even though the laser is enabled.
Workaround: Perform an online removal and insertion of the OSC module or carrier motherboard.
•
Symptom: The OSC wave interface does not come back up after resolving a trunk fiber break if laser safety control was configured after the trunk fiber break occurred.
Workaround: Disable and then enable laser safety control again to bring up the OSC wave interface.
•
Symptom: The 8-port GE/FC aggregation card laser is not in the proper state when a Tx-CRC threshold has been exceeded and FLC is configured.
Workaround: Issue the shutdown/no shutdown command sequence on the affected interface.
•
Symptom: The values returned for entPhysicalVendorType and entPhysicalName are wrong when a low-band single-mode SFP is present in an ESCON aggregation card. The values returned show a low-band multimode SFP instead.
Workaround: None.
•
Symptom: In a y-cable APS configuration, interfaces on the 8-port GE/FC aggregation card configured for FICON encapsulation change to GE encapsulation when the saved configuration file is copied to the running configuration.
Workaround: Change the encapsulation back to FICON.
•
Symptom: If the transparent interface on a multimode transponder line card is configured for Sysplex ETR traffic (encap sysplex etr command), the show interfaces transparent command output shows that forward laser control is set to OFF. Forward laser control is automatically enabled for Sysplex ETR.
Workaround: Add client input traffic and the trunk side laser will function.
•
Symptom: End-to-end GE autonegotiation is not supported by the 8-port FC/GE aggregation card.
Link defects such as a broken fiber from the 8-port FC/GE aggregation card to the client device at one end, which are not directly detected by the Cisco ONS 15530 and cause the client at one end to initiate autonegotiation, are not propagated to the client at the other end.
Any upper-layer processes that depend on bidirectional defect detection and propagation at the transport level might fail for certain classes of link defects.
Workaround: None.
•
Symptom: Issuing a show connect intermediate command results in spurious memory access after configuring a patch between a wavepatch interface and a wdmrelay interface.
Workaround: Do not issue the show connect intermediate command when a patch between a wavepatch interface and a wdmrelay interface is configured.
•
Symptom: The patch configuration between oscfilter interfaces and voaout interfaces is not supported by the CLI.
Workaround: None.
•
Symptom: The command for configuring optical thresholds on a voain interface is broken in 12.2(22)SV image for the Cisco ONS 15530. The command should be in the form:
optical threshold power receive after-attenuation [low|high] [alarm|warning] <val>
But in 12.2(22)SV images only the following command can be specified in the interface configuration mode:
optical threshold power receive [low|high] [alarm|warning] <val>
The command is stored in earlier format in the running configuration for the interface, hence upon reloading the chassis these threshold configurations are lost
Workaround: Configure the optical threshold using the format :
optical threshold power receive [low|high] [alarm|warning] <val>
If the chassis has to be reloaded then reconfigure the threshold command again when the box is rebooted.
Resolved Caveats in Release 12.2(22)SV
•
Symptom: A spurious memory access might occur when you enter the show connect intermediate privileged EXEC command after configuring a patch between a wavepatch interface and a wdmrelay interface. The symptom does not affect any functionality.
Workaround: Do not enter the show connect intermediate privileged EXEC command.
•
Symptom: The system might reload unexpectedly when a faulty optical add/drop multiplexer (OADM) module is present in the chassis.
Workaround: Replace the faulty OADM module.
•
Symptom: A system might reload unexpectedly when you perform an online removal and reinsertion of a wide-band variable optical attenuator (WB-VOA) module.
Workaround: Do not remove and reinsert a WB-VOA module.
•
Symptom: The system might reload unexpectedly when you configure the alarm threshold on a waveethernetphy interface of a 2.5-Gbps ITU trunk card.
This symptom occurs after the following events:
1.
2.
3.
After you have performed these steps, the shelf reloads.
Workaround: None.
•
Symptom: An APS switchover from a working interface to a protect interface might not occur for the following modules:
–
–
–
This symptom occurs with the following configurations:
–
–
–
Workaround: Do not configure CDL HEC error thresholds, CRC error thresholds, or both. Instead, configure code violation running disparity (CVRD) error thresholds. In a configuration in which an APS switchover of a working interface to a protect interface is based on CDL HEC error thresholds, CRC error thresholds, or both, there is no workaround.
•
Symptom: OSC wave interface that is configured for laser safety control does not recover when the OSC link is down due to Loss of Light.
This occurs after the following sequence of events:
–
–
–
–
This problem does not appear if laser safety control is configured when the OSC wave interface is up.
Workaround: Issue a no laser control safety command and a laser control safety enable command on the OSC wave interface.
•
Symptom: An optical supervisory channel (OSC) module may not provide power even though the laser is enabled after you have booted the shelf.
Workaround: Remove and reinsert the carrier motherboard.
•
Symptom: If a row is created in cApsChanConfigTable using createAndWait, a set operation on an instance of cApsChanConfigIfIndex might modify another instance of that object.
Workaround: Use createAndGo to create the row.
Resolved Caveats in Release 12.2(18)SV2
•
Symptom: In some instances the system crashes when it attempts to parse IP SNMP related commands.
Workaround: None.
•
Symptom: Bidirectional APS fails when the ethernetdcc interface is used as a message channel for trunk based protection if the PSM is connected directly to a wavepatch interface on an ITU trunk card or transponder line card rather than to the wdm interface on an OADM module.
Workaround: None.
•
Symptom: Link initialization failure due to Loss of Lock might occur for ESCON traffic on some transponder line cards due to a transient failure of the clock recovery unit. Only some transponder line cards are susceptible to this failure and not all. This is an initialization failure and not a run-time failure.
Workaround: None.
Resolved Caveats in Release 12.2(18)SV1
•
Symptom: While performing an online removal and insertion of a protection card in a y-cable configuration, the local and remote working ports are flooded with CRC errors.
Workaround: Disconnect the standby branch of the y-cable configuration during the insertion of the standby line card or SFP optics.
•
Symptom: Tracebacks related to CPU hog issues are seen when reprogramming the 2.5-Gbps transponder line card functional image.
Workaround: None.
•
Symptom: Performing an online removal and insertion on a tengigethernetphy interface or waveethernetphy interface when loopback is configured causes a loss of the loopback information on the hardware. However, the loopback CLI configuration is still present in the software.
Workaround: Remove and reinsert the line card, and then issue the loopback command.
•
Symptom: Issuing a Ctrl-U when connected to a raw TL1 port causes the system to crash.
Workaround: If a TL1port is unused, apply an IP ACL to the management Ethernet interface that blocks the incoming TCP connections to ports 3082 and 3083.
•
Symptom: Power-on diagnostics fail on the CPU switch module if a 2.5-ITU trunk card is installed in slot 1.
Workaround: None.
Resolved Caveats in Release 12.2(18)SV
•
A Cisco device running IOS and enabled for the Border Gateway Protocol (BGP) is vulnerable to a Denial of Service (DOS) attack from a malformed BGP packet. The BGP protocol is not enabled by default, and must be configured in order to accept traffic from an explicitly defined peer. Unless the malicious traffic appears to be sourced from a configured, trusted peer, it would be difficult to inject a malformed packet. BGP MD5 is a valid workaround for this problem.
Cisco has made free software available to address this problem. For more details, please refer to this advisory, available at http://www.cisco.com/warp/public/707/cisco-sa-20040616-bgp.shtml.
•
Symptom: OFC (open fibre control) is not supported with Fibre Channel on the 8-port FC/GE aggregation card. The link might not initialize if an 8-port FC/GE aggregation card is used with older Fibre Channel equipment that employ OFC laser safety mechanisms.
Workaround: None.
•
A Cisco device running IOS and enabled for the Border Gateway Protocol (BGP) is vulnerable to a Denial of Service (DOS) attack from a malformed BGP packet. The BGP protocol is not enabled by default, and must be configured in order to accept traffic from an explicitly defined peer. Unless the malicious traffic appears to be sourced from a configured, trusted peer, it would be difficult to inject a malformed packet. BGP MD5 is a valid workaround for this problem.
Cisco has made free software available to address this problem. For more details, please refer to this advisory, available at http://www.cisco.com/warp/public/707/cisco-sa-20040616-bgp.shtml.
•
Symptom: An 8-port FC/GE aggregation card client interface laser may be off when it is configured in a disabled y-cable APS group.
Workaround: Enable and then disable the APS group. This activates the client interface laser.
•
Symptom: If the flow identifier on an esconphy interface is changed without deleting the old flow identifier, both the old and the new flow identifiers are present in the lookup table of the ESCON aggregation card. As a result, the old flow identifier cannot be reused on this ESCON aggregation card.
Workaround: Perform an online removal and insertion of the ESCON aggregation card or issue the following sequence of commands in interface configuration mode:
1. no cdl flow identifier
2. cdl flow identifier [OLD IDENTIFIER]
3. no cdl flow identifier
4. cdl flow identifier [NEW IDENTIFIER]
•
Symptom: Continuous optical power monitoring alarms cause memory leaks that lead to bus error exceptions and an unexpected reload.
Workaround: None.
Limitations and Restrictions
This section provides limitations and restrictions for Cisco ONS 15530 hardware and software.
Transponder Line Cards
This section contains limitations and restrictions that apply to transponder line cards.
•
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.
•
8-Port FC/GE Aggregation Card
This section contains limitation and restrictions that apply to 8-port FC/GE aggregation cards.
•
The FICON Bridge port (on the ESCON Director) expects to be connected directly to an N_Port of the Host. Therefore, the Bridge port expects the N_Port to send a minimum of six Primitive Signals (Idles and R_RDYs) between frames. Anything less than six Primitive Signals causes IFCCs to be generated on the ESCON Director, which in turn are logged on the Host. The 8-port FC/GE aggregation card is pure transport and needs to delete and insert one IPG for frequency compensation. Hence, depending on the card, sometimes either five or seven idles are sent between frames. The 8-port FC/GE aggregation card cannot maintain six idles between every frame if the card is on slower side of the clock.
The workaround is to enable flow control using the flow control command on the gigabitphy interfaces.
CPU Switch Modules
This section contains limitations and restrictions that apply to CPU switch modules.
•
Note
Related Documentation
Refer to the following documents for more information about the Cisco ONS 15530:
•
•
•
•
•
•
•
•
•
•
•
•
•
Obtaining Documentation
Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
Cisco.com
You can access the most current Cisco documentation on the World Wide Web at this URL:
http://www.cisco.com/univercd/home/home.htm
You can access the Cisco website at this URL:
International Cisco websites can be accessed from this URL:
http://www.cisco.com/public/countries_languages.shtml
Ordering Documentation
You can find instructions for ordering documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
You can order Cisco documentation in these ways:
•
http://www.cisco.com/en/US/partner/ordering/index.shtml
•
Documentation Feedback
You can submit e-mail comments about technical documentation to bug-doc@cisco.com.
You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Obtaining Technical Assistance
For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, the Cisco Technical Assistance Center (TAC) provides 24-hour-a-day, award-winning technical support services, online and over the phone. Cisco.com features the Cisco TAC website as an online starting point for technical assistance. If you do not hold a valid Cisco service contract, please contact your reseller.
Cisco TAC Website
The Cisco TAC website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The Cisco TAC website is available 24 hours a day, 365 days a year. The Cisco TAC website is located at this URL:
Accessing all the tools on the Cisco TAC website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a login ID or password, register at this URL:
http://tools.cisco.com/RPF/register/register.do
Opening a TAC Case
Using the online TAC Case Open Tool is the fastest way to open P3 and P4 cases. (P3 and P4 cases are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Case Open Tool automatically recommends resources for an immediate solution. If your issue is not resolved using the recommended resources, your case will be assigned to a Cisco TAC engineer. The online TAC Case Open Tool is located at this URL:
http://www.cisco.com/tac/caseopen
For P1 or P2 cases (P1 and P2 cases are those in which your production network is down or severely degraded) or if you do not have Internet access, contact Cisco TAC by telephone. Cisco TAC engineers are assigned immediately to P1 and P2 cases to help keep your business operations running smoothly.
To open a case by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447For a complete listing of Cisco TAC contacts, go to this URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
TAC Case Priority Definitions
To ensure that all cases are reported in a standard format, Cisco has established case priority definitions.
Priority 1 (P1)—Your network is "down" or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Priority 2 (P2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Priority 3 (P3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Priority 4 (P4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•
http://www.cisco.com/go/marketplace/
•
http://cisco.com/univercd/cc/td/doc/pcat/
•
•
•
http://www.cisco.com/go/iqmagazine
•
•
http://www.cisco.com/en/US/learning/index.html
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
CCSP, CCVP, the Cisco Square Bridge logo, Follow Me Browsing, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Access Registrar, Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, StrataView Plus, TeleRouter, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website 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. (0502R)
Copyright © 2003-2005 Cisco Systems, Inc. All rights reserved.
Posted: Sat Jul 30 21:39:40 PDT 2005
All contents are Copyright © 1992--2005 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
