|
|
Table Of Contents
Release Notes for Cisco ONS 15530
for Cisco IOS Release 12.1(12c)EV3Determining the Software Version
New Features in Release 12.1(12c)EV3
New Features in Release 12.1(12c)EV2
New Features in Release 12.1(12c)EV1
New Features in Release 12.1(12c)EV
New Features in Release 12.1(10)EV4
Obtaining Technical Assistance
Obtaining Additional Publications and Information
Release Notes for Cisco ONS 15530
for Cisco IOS Release 12.1(12c)EV3
This document describes caveats for Cisco IOS Release 12.1(12c)EV3 for the Cisco ONS 15530.
Date: September 2, 2003
Text Part Number: OL-3630-04
Contents
This document includes the following information:
•
Caveats
•
•
•
Introduction
The 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 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(12c)EV3 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.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.
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
X
X
X
X
X
X
Gigabit Ethernet
X
X
X
X
X
X
Fast Ethernet
X
X
X
X
X
X
Ethernet
X
X
X
X
X
X
ATM OC-3/STM-1, OC-12/STM-4, and OC-48/STM-16
X
X
X
X
X
X
X
X
X
X
X
X
POS3
X
X
X
X
X
X
IBM Sysplex coupling link
X
X
X
X
X
X
Fibre Channel (1 Gbps)
X
X
X
X
X
X
Fibre Channel (2 Gbps)
X
X
X
X
X
X
FDDI4
X
X
X
X
X
X
ESCON5 aggregation (2.5 Gbps)
X
X
X
X
X
X
FICON6 (800 Mbps)
X
X
X
X
X
X
FICON (1 Gbps)
X
Token ring
X
X
X
X
X
X
SNMP
X
X
X
X
X
X
CiscoView
X
X
X
X
X
X
Cisco Transport Manager
X
X
X
X
X
X
IP packets
X
X
X
X
X
X
OSCP7
X
X
X
X
X
X
APS8 channel protocol
X
X
X
X
X
X
Point-to-point
X
X
X
X
X
X
Hubbed ring
X
X
X
X
X
X
Meshed ring
X
X
X
X
X
X
IBM Sysplex ETR/CLO9
X
X
X
X
X
X
Fibre Channel/FICON aggregation (2.5 Gbps)
X
X
X
X
Gigabit Ethernet aggregation (2.5 Gbps)
X
X
X
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
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.1. The new features are sorted by release number.
New Features in Release 12.1(12c)EV3
The following new feature is available for the Cisco ONS 15530 in Cisco IOS Release 12.1(12c)EV3:
•
–
–
–
–
•
–
–
•
CSCeb03740 · ·, CSCeb19410 · ·, CSCeb27146 · ·, CSCeb62199 · ·, CSCec03715 · ·, CSCec05746 · ·, CSCec09014 · ·, CSCec15086 · ·, CSCin41925 · ·
New Features in Release 12.1(12c)EV2
The following new feature is available for the Cisco ONS 15530 in Cisco IOS Release 12.1(12c)EV2.
The Cisco ONS 15530 power-on diagnostics now support testing of the following components:
•
•
•
New Features in Release 12.1(12c)EV1
The following new features are available for the Cisco ONS 15530 in Cisco IOS Release 12.1(12c)EV1:
•
•
•
•
Note
New Features in Release 12.1(12c)EV
The following new hardware features are available for the Cisco ONS 15530 in Cisco IOS Release 12.1(12c)EV:
•
•
–
–
•
•
The following new software features are available for the Cisco ONS 15530 in Cisco IOS Release 12.1(12c)EV:
•
•
•
•
•
•
–
–
–
–
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 each 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.
This section describes the caveats in the Cisco ONS 15530.
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: Unchecked buffer boundary in NTP.
Workaround: None.
Symptom: When the NME is connected to an auto-sensing switch or hub, going from 10 Mbps and half-duplex to 100 Mbps and half-duplex (or similarly 10 Mbps and full-duplex to 100 Mbps and full-duplex) 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 might not be detected if the condition is temporary and does not last for more than a second.
Workaround: None
Symptom: If you swap the ESCON aggregation card with the 10-Gbps ITU trunk 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 is 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: Issue the shutdown/no shutdown command sequence on the wavepatch interface.
Symptom: Interface reports up/up even when there is no light source connected.
Workaround: Issue a shutdown/no shutdown command sequence on the interface.
Symptom: A transparent interface carrying Gigabit Ethernet traffic and configured with gigabit Fibre Channel encapsulation shows a good quality signal on the show interfaces transparent command output and does not assert any ingress alarms. The wave interface asserts loss of lock and loss of sync alarms.
Workaround: OIR 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 line card.
Workaround: Disable and reenable monitoring on the transparent interface to reassert the alarms.
Symptom: The show facility-alarm status command status does not report existing LoF/LoSync/LoLock alarms after an OIR.
Workaround: Disable and enable monitoring back to reassert existing alarms in the show facility-alarm status command output.
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 a CPU switch module that has been removed from the system.
Workaround: None.
Symptom: Ethernetdcc and OSC wave interfaces come up with default traffic-shaping parameters. Because this is the default, by removing the configuration using the no form of the command, the parameter value should revert 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 might not come up properly.
Workaround: Insert the line card after switchover is complete.
Symptom: The system might crash at is_optical_ifstatus_up.
Workaround: None.
Symptom: Issuing a shutdown command on the active wavepatch of a nonsplitter card brings the waveethernetphy interface down and reports loss of light in the output of the show interfaces command, but traffic continues to flow.
Workaround: If the intent is to stop traffic, issue a shutdown command on the waveethernetphy interface or wave interface.
Symptom: Following a CPU switch module crash and switchover, the show redundancy command issued on the new active CPU switch module displays "Not known" for the Reported Switchover Reason field.
Workaround: Enter show version from the standby CPU switch module console to see additional information.
Symptom: The default value of the switchover-enable min-interval timer for an APS group is 3 seconds. However, this value is incorrectly stated in CISCO-APS-EXT-MIB.my as 2 seconds for the object cApsConfigSwitchoverEnableInterval, which corresponds to the switchover-enable min-interval timer.
Workaround: None
Symptom: The getnext and getbulk commands do not function properly after a CPU switch module switchover.
Workaround: None.
Symptom: AN APS trap mode mismatch takes 30 minutes for completion.
Workaround: None.
Symptom: Low alarm is not cleared on the wavepatch interface on a transponder line card.
Workaround: Issue a shutdown/no shutdown command sequence on the wavepatch interface where the alarm is seen.
Symptom: On the 10-Gbps ITU trunk card, the CDL HEC and CRC error counters are not incremented upon reaching the threshold limits.
Workaround: None.
Symptom: When trying to modify the cApsConfigSpan object through an SNMP set to an unsupported value, the value is not set but no error is reported.
Workaround: None.
Symptom: Administrative shutdown on a waveethernetphy subinterface does not take affect. The command output indicates "admin shut" but all the traffic flows through and the subinterface is fully functional.
Workaround: None.
Symptom: After removing and reconnecting the fiber cable, the active wavepatch on the transponder line card is down even after issuing an no shutdown command on the wave interface.
Workaround: Use a shutdown command to clear the alarms on the wave interface.
Symptom: Spurious memory access is seen when issuing the show tech command on the standby CPU switch module.
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: The 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 CompactFlash (disk0), a transient error with the following message might appear and read/write access to CompactFlash is terminated:
ATA_Status timeout waiting for <1/2/3>
Workaround: None.
Symptom: Defect-indication error messages do not indicate 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 because the agent does not create them on OIR.
Workaround: Reload the system 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 are dropped at the end of the second hop.
Workaround: None.
Symptom: Loopback interfaces cannot be deleted from configuration.
Workaround: None.
Symptom: The power-on diagnostics do not identify the 2.5-Gbps ITU trunk card.
Workaround: Upgrade the system image to release 12.1(12c)EV2 or later.
Symptom: Switch fabric protection is not disabled if the standby CPU switch module is in ROM monitor mode. As a result if an RxFail is noticed on any fabric port, that fabric port switches over its receive to the standby 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 CompactFlash card.
Workaround: None.
Symptom: No ciscoFlashDeviceChangeTrap trap is generated when a CompactFlash device is removed or inserted.
Workaround: None.
Symptom: When forward laser control is disabled on all 10 esconphy ports and they are administratively shut down, packets are still sent to the backplane.
Workaround: None.
Symptom: OPM feature does not work for nonsplitter transponder line cards.
Workaround: None.
Symptom: Invalid mac-address or ip-address values 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 command output after the hardware module power is turned off and turned back on.
Workaround: None.
Symptom: Incorrect alarms are reported on wavepatch interfaces when the parent wave interface is administratively shut.
Workaround: None.
Symptom: If a system is rebooted and a transient link failure condition occurs on 10-Gbps ITU trunk cards or 10-Gbps uplink cards, the system might continuously send backward defect indications.
Workaround: None.
Symptom: Error messages appear when a 10-Gbps ITU trunk card or 10-Gbps uplink card with cross connects to the switch fabric is removed.
Workaround: None.
Symptom: The wavepatch interfaces are stuck in the down state after using the shutdown/no shutdown command sequence on the wave interface with splitter APS after the trunk fiber has been cut.
Workaround: None.
Symptom: If the peer node is rebooted, the interfaces connected to that node experience some flaps in the bootup sequence. These flaps trigger unnecessary APS flaps in the near-end node.
Workaround: None.
Symptom: A Border Gateway Protocol (BGP) session reset occurs because of a notification that indicates a defective OPEN message.
Workaround: Configure only the receive or send options of the neighbor-orf prefix- filter command.
Symptom: After a fiber cut, the OSC wave interface remains up with signal quality GOOD.
Workaround: Use the shutdown/no shutdown command sequence on the OSC wave interface.
Symptom: When APS communication is down and an APS failure is detected, APS might switch over even though the communication is down resulting in a unidirectional switchover. For IBM Sysplex CLO/ETR applications, a unidirectional switchover might lead to data corruption.
Workaround: None.
Symptom: The standby CPU switch module can be stuck in trying to register control ports.
Workaround: Enter the redundancy reload peer command on the active CPU switch module.
Symptom: In bidirectional APS, if both NEs (network elements) 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 a working interface with an invalid cross connect and protection interface with an active cross connect, APS erroneously sets the APS channel request on the 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 in protection until an event (that has higher priority than WTR) is triggered.
Workaround: None.
Symptom: Splitter APS protection comes up as active on system 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 (such as when the interfaces do not exist), if the group is configured for revertive mode, it cannot be enabled.
Workaround: Enable the group after the interfaces defined in the APS group are created or remove the revertive configuration from the preconfigured APS group and then enable the group.
Symptom: The CPU switch module crashes after midnight with optical performance monitoring on when an interface capable of performance monitoring is shut down before 00-00 hrs and unshut after midnight.
Workaround: None.
Symptom: In unidirectional revertive APS, after online removal is followed by online insertion of working and protection elements on both NEs, the active signal might be received from the protection line instead of the working line.
Workaround: Do a manual or force switch to the working line.
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: A connection to a different subinterface on the same 10-Gbps ITU trunk card or 10-Gbps uplink card is accepted, but a cross connection fails in the switch fabric.
Workaround: None.
Symptom: The MTU setting on the 10-Gbps ITU trunk card interface is not displayed in the show interfaces command output. Transmit side is reporting oversized frames.
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 in the interfaces. You can also perform an aps disable/aps enable command sequence to the APS group.
Symptom: Y-cable transponder protection does not come up as active after removing lockout.
Workaround: Perform an aps disable/aps enable command sequence 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 to correct the CDR loss of lock reporting.
Symptom: Tx-CRC and CDL-HEC error counters do not show the proper values in the show interfaces command output for the waveethernetphy interface.
Workaround: None.
Symptom: The power-on diagnostics do not identify the 8-port FC/GE aggregation card. After booting the following message appears:
Unexpected fru_type (0x110B) in: pod_get_namelist_num_tests
Workaround: Upgrade the system image to release 12.1(12c)EV2 or later.
Symptom: Wave interfaces see continuous flapping when the wavepatch interface on a nonsplitter card is shut.
Workaround: None.
Symptom: If two different trunk cards in the same slot are hot-swapped, the newly inserted trunk card inherits the configuration of the ethernetdcc interface from the removed trunk card.
Example: If a user swaps a 2.5-Gbps ITU trunk card with a 10-Gbps ITU trunk card in the same slot, the ethernetdcc interface for the newly inserted 10-Gbps ITU trunk card inherits the ethernetdcc interface configuration from the removed 2.5-Gbps ITU trunk card.
Workaround: None.
Symptom: Wavepatch interface configurations are retained when swapping a 10-Gbps ITU trunk card, 2.5-Gbps ITU trunk card, or transponder line card.
Workaround: None.
Symptom: The ethernetdcc interface loses connectivity when splitter protection is configured and the waveethernetphy interface is shut down while protection on the wavepatch is active and the working wavepatch is down.
Workaround: Do not shut down the waveethernetphy interface while the working wavepatch is down.
Symptom: If bidirectional nonrevertive splitter APS is configured on the 10-Gbps or 2.5-Gbps trunk cards, a simultaneous OIR of the local and remote cards might cause the APS to switch to protection wavepatch when the card comes up.
Workaround: Enable revertive mode if the working wavepatch comes up as active.
Symptom: The PSM is incorrectly recognized as an OADM module by Cisco IOS images that do not support the PSM.
Workaround: Upgrade software to release 12.1(12c)EV.
Symptom: When lockout on the protection path is removed with a signal failure on working, the splitter switches back and forth between protection and working on 2.5-Gbps and 10-Gbps splitter ITU trunk cards.
Workaround: None.
Symptom: While performing an OIR 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: The 10-Gbps ITU trunk card fails during power-on diagnostics at the Quadphy loopback test (qphy-fabric-lb) and the om-fifo test.
Workaround: None.
Symptom: Update alarms and add new alarms for new cards.
Workaround: None.
Symptom: Controller type for the backplane is not displayed in the show hardware detail command output.
Workaround: None.
Symptom: The following problems might occur on 8-port FC/GE aggregation cards:
- The interface is missing from the running-configuration after the insertion of SFP optics. The system message for the insertion is not printed to the console.
- The interface is present in the running-configuration after the removal of SFP optics. The system message for the removal is not printed to the console.
Workaround: OIR the 8-port FC/GE aggregation card to recover from the problematic state.
Symptom: The show optical filter command output shows invalid information regarding the interface wavelength for filters.
Workaround: None.
Symptom: The system crashes when WB-VOA and PB-OE modules are removed.
Workaround: None.
Symptom: If the primary CPU switch module crashes due to a send break after executing POD and before booting the system image completely, the new primary CPU switch module comes up in Cisco IOS with junk entries programmed in the SII lookup tables of the 10-Gbps ITU trunk cards present in the chassis. As a result, all 10-Gbps ITU trunk cards are stuck in the decoder and the floating channels are enabled.
Workaround: None.
Symptom: Transmit failure is cleared before APS is notified of failure and does not take correct action.
Workaround: Issue a shutdown/no shutdown command sequence on the interface.
Symptom: Disconnecting a 10-port ESCON or 8-port FC/GE aggregation card from a 2.5-Gbps ITU trunk card can cause two ports to have the same flow identifier.
Workaround: Avoid assigning the same flow identifier to the ports in the portgroup.
Symptom: The gt-interrupt and interrupt0 tests on the CPU switch module fail.
Workaround: None.
Symptom: Incompatibility messages might appear on the standby processor card when upgrading images on the active processor card.
Workaround: None.
Symptom: The WB-VOA module functional image version is different in the show hardware and show controllers command outputs.
Workaround: None.
Symptom: On a splitter APS switchover based on a CVRD SF condition, the SF threshold exceeded count is not incremented. There is also no log or event on the console that differentiates between switches overdue to CVRD SF or loss of lock.
Workaround: None.
Symptom: High alarm and low alarm status not cleared for WB-VOA or PB-OE modules when optical power is in a high warning or low warning state.
Workaround: None.
Symptom: When a new line card is inserted and the backplane connection does not happen properly or there is some other accessibility issue, the driver sees card access failure. But no alarm is raised to the Network Management station.
Workaround: None.
Symptom: A y-cable switchover from working to protection does not work. The show aps group command output shows that "auto fail over" is disabled and transmitting sf-lp from protection port.
Workaround: None.
Symptom: Removing the configured threshold for CDL HEC and CRC removes the template (and default values) resulting in CDL HEC and CRC errors.
Workaround: Apply a threshold group for CRC/CDLHEC from CLI and remove it.
Symptom: When removing a 2.5-Gbps ITU trunk card from the shelf, the following error message might appear:
%LC_2P5G-3-INTERNAL_CRITICAL: physubcard/idprom NULL in city_island_get_laser_frequencyWorkaround: None.
Symptom: After a CPU switch module switchover, sometimes ptopMIB and ptopoExtnMibs are not readable or settable through SNMP.
Workaround: The values can be read or set by using the CLI.
Symptom: When a waveethernetphy interface on a 2.5-Gbps ITU trunk card with splitter APS configured is shut down, loss of lock and loss of sync alarms are reported in the output of the show facility-alarm status command.
Workaround: None.
Symptom: A fan tray removal does not trigger any alarms.
Workaround: None.
Symptom: If ESCON data traffic is mixed with Gigabit Ethernet traffic cross connected to the same 10-GE ITU trunk card, ESCON traffic experiences errors. Ports on the ESCON director might not even come up.
Workaround: Assign valid flow identifiers to all 10 ports on the ESCON aggregation card.
Symptom: Currently the Tx-buffer configuration is allowed on the port group interface on the ESCON aggregation card. This CLI has to be moved to the client interface.
Workaround: Configure the CLI from the portgroup interface on the ESCON aggregation card.
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.
Symptom: The system can reload unexpectedly if there are APS groups configured on 8-port FC/GE aggregation card interfaces and there is a state change of one or more of the ports or cross-connected interfaces.
Workaround: None.
Symptom: If multiple APS groups are configured, and one group is in not associated state because there are working and protection ports in the admin down state, any Rx fail and recover of other groups causes both lasers to turn on in those groups.
Workaround: Disable the APS group if ports of any APS groups are in admin down state.
Symptom: The show facility-alarm status command output does not show loss of sync, loss of light, or signal failure alarms on a waveethernetphy interface on a 10-Gbps ITU trunk card or 2.5-Gbps ITU trunk card after a shutdown/no shutdown command sequence on the interface. The show interfaces command displays that the alarm persists.
Workaround: None.
Symptom: You cannot reconfigure new cross connections after reinserting a 10-Gbps ITU trunk card if a card fails due to low voltage of another hardware failure and is removed, the flow identifier values programmed in the 10-Gbps ITU trunk card are not cleared. Flow identifier mismatch errors are displayed and cross connections are not established.
Workaround: OIR the 10-Gbps ITU trunk card.
Symptom: Cannot disable SNMP-server traps for TTY messages on a global basis.
Workaround: Configure traps on a per SNMP-server host basis.
Symptom: Both working and protection interfaces come up as the standby when configuring splitter APS using ENT-FFP-OCH. Both of the wavepatch interfaces are up in the transponder line card.
Workaround: Issue an aps enable/disable command sequence or OIR the transponder line card.
Symptom: The y-cable connection does not come up while connected to a Brocade switch.
Workaround: None.
Symptom: If multiple cross connections are created and deleted on an 8-port FC/GE aggregation card, the local or remote system might reload unexpectedly. This rarely happens.
Workaround: None.
Symptom: The no form of VOA attenuation commands might wipe out positive forms those commands
Workaround: None.
Symptom: If a TL1 command is partially successful, an error code for the parameter that cannot be modified is displayed.
Workaround: None.
Symptom: An internal error and a traceback results when a threshold group with Tx-CRC failure and Tx-CRC degrade is modified such that the index reaches 63 and there is an attempt to add a new Tx-CRC threshold.
Workaround: None.
Symptom: If a card with a bad IDPROM is detected in the system, the system crashes during bootup or online insertion.
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: If a timer is rebooted and the CLO link is up and running, the link briefly turns off the lasers. This is seen as loss of light and the FLC turns off the transmitter laser on the transponder line card. When the timer is back on, the FLC does not turn the transmitter laser on.
Workaround: Issue the shutdown/no shutdown command sequence or OIR the card.
Symptom: If the connect command is executed, which results in traffic intermixing between ESCON/ Fibre Channel/ FICON and Gigabit Ethernet/ ESCON/Fibre Channel/FICON, traffic might slow down if the proper preconfiguration commands are not configured for the corresponding line cards.
Workaround: Configure the required preconfiguration commands.
Symptom: BDI-E (Backward Defect Indication) is asserted on FC/GE interfaces when there is no remote Tx fault. This does not affect functionality.
Workaround: None
Symptom: After a CPU switch module switchover, persistent alarms on an administratively shut interface might be erroneously reported when they exist. When a port interface is administratively down, alarm conditions should not be reported for that interface even though they exist.
Workaround: After a CPU switch module switchover, issue a no shutdown/shutdown command sequence on the already administratively shut interfaces. This ceases to report alarm conditions persistent on the administratively shut interfaces.
Symptom: If an ESCON aggregation card cross connected to a 10-Gbps ITU trunk card is removed and reserved flow identifier configured, reserved flow identifiers are not removed.
Workaround: OIR the 10-Gbps ITU trunk card to clear the flow identifiers.
Symptom: Catalyst 5000 FDDI link does not come up when connected over a Cisco ONS 15530 point-to-point topology using multimode transponders.
Workaround: Set the clock rate to 500 MHz.
Symptom: The show cdl flow identifier does not show the reserved flow ID configured under the portgroup.
Workaround: Use the show interfaces portgroup x/y/z command to display the configured group.
Symptom: After a CPU switch module switchover, if the no shutdown command is issued on the OSC wave interface, it is in the UP state even when the OSC module is not connected to the OADM module.
Workaround: Issue the shutdown/no shutdown command sequence on the OSC wave interface.
Symptom: APS state is not correct after an online removal and reinsertion of the local ESCON aggregation card. This happens only if the following sequence of events occurs:
1. Shut down of the remote laser (working path)
2. Removal of the ESCON aggregation card (local)
3. Shut down of the local laser (working path)
4. Insertion of the ESCON aggregation card (local)
After the local ESCON aggregation card is reinserted, the protection waveethernetphy interface does not become active. At this point, the working interface is active even though it is in the down state.
Workaround: Remove and reinsert the protection and working 2.5-Gbps ITU trunk cards.
Symptom: The 10-Gbps ITU trunk card waveethernetphy interface does not come up after the peer laser is turned back on after a CPU switch module switchover. This happens only if a laser shut is carried across the CPU switch module switchover on the local system.
Workaround: Issue a shutdown/no shutdown command sequence on the local waveethernetphy interface
Symptom: If a Cisco ONS 15530 system with a 7.x hardware version of the 10-Gbps ITU trunk card is booted with the ons15530-i-mz.121-12c.ev image, the following warning displays:
Power-on Diagnostics: --------------------- ...................FF.. . ... POD-CRITICAL_WARNING: Slot: 3, Hardware and Firmware are not compatible. ........... .F...... End of POD.Workaround: Turn off power-on diagnostics, save the configuration, and reboot to get rid of the warning.
Symptom: With the duplicate reserved flow identifiers configured and OIR of the ESCON aggregation card, cross connection is rejected, but the client flow identifiers are not removed.
Workaround: OIR the 10-Gbps ITU trunk card.
Symptom: When the active 10-Gbps ITU trunk card in a line card protected configuration is removed, the following warning message displays:
idprom_get_line_wavelength: Unexpected card type: 4360Workaround: None.
Symptom: Both active and standby lasers are on for a few seconds on a y-cable. This condition can cause Brocade ports to be disabled which requires a manual intervention to enable the ports.
Workaround: None.
Symptom: The wave interface goes down after restoring protection trunk failure followed by working trunk failure and restore on a transponder line card configured for unidirectional y-cable protection.
Workaround: Issue a shutdown/ no shutdown command sequence on the wave interface.
Symptom: After booting the system, power coming out of the OSC module seems to be null even though the laser is enabled.
Workaround: OIR the OSC module or carrier motherboard.
Symptom: The protection interface comes up first after an OIR of the 2.5-Gbps ITU trunk card, causing APS to switch to the protection channel after the OIR of the card.
Workaround: None.
Symptom: With the duplicate reserved flow identifiers configured, if line card protection is configured, both 10-Gbps ITU trunk cards end up in active state.
Workaround: Assign unique reserved flow identifiers to the ESCON aggregation card ports.
Symptom: The TL1 ENT-FFP-OCH and ED-FFP-OCH commands allow incorrect configuration of an APS splitter or Y-cable group for the 2.5-Gbps transponder line card with the in-band message channel set as the APS message channel.
Workaround: None.
Symptom: No autonomous messages are generated in TL1 for clearing alarms when an ESCON port is shut down.
Workaround: None
Symptom: Backplane Ethernet loopback test fails occasionally on 10-Gbps ITU trunk cards.
Workaround: None.
Symptom: With reserved flow identifiers configured under a port group, after a CPU switch module switchover is performed both client and reserved flow identifiers are programmed.
Workaround: None.
Symptom: A keepalive timeout results on an 8-port FC/GE aggregation card interface configured with FC encapsulation even with the correct flow identifier, cross connects, and trunk connections. The hardware registers show an uplink FIFO full condition in the peer FC interface. No traffic flows out of the peer interface.
Workaround: Change the encapsulation to GE and then change it back to FC or remove and insert the SFP optics to reset the FIFOs and clear the full condition.
Symptom: The om-fifo and ponte-serdes-lb power-on diagnostic tests fail for the 2.5-Gbps ITU trunk card when the bcom-sco-config test for the CPU switch module and the backplane-eth-lb test for the 2.5-Gbps ITU trunk card are both disabled.
Workaround: None.
Symptom: Power-on diagnostics report a failure for the cpu-serdes-lb power-on diagnostic test of the 2.5-Gbps ITU trunk card during the first reload after a power cycle.
Workaround: None.
Symptom: The hudjr-internal-lb and serdes-lb tests for the OSC module fail during the first reload after a power cycle when the backplane-eth-lb test for the carrier motherboard is disabled.
Workaround: None.
Symptom: The signal failure threshold exceeded alarm is not reported when a CDL-HEC degrade, CVRD degrade, or failure condition exists on the waveethernetphy interface of a 10-Gbps ITU trunk card.
Workaround: Disconnect and then reconnect the receive cable.
Symptom: If flo_ons is running on the active processor card and the EV throttle version is running on the standby processor card and wr mem is done, the configuration sync fails.
Workaround: None.
Symptom: Trailing spaces in a password are not recognized when attempting to log in using the ACT-USER command in TL1.
Workaround: Enter the password without the trailing spaces.
Symptom: A message "Duplicate reserved flow identifier..." is printed. It does not affect the functionality or the operation of the card.
Workaround: None.
Symptom: Laser is turned off but it is not indicated by the show interface command output, or by any message to the console.
Workaround: Use the show controllers command to check the laser status.
Symptom: A warning message is required if the same proxy interface is used for configuring a dynamic topology on two WDM interfaces.
Workaround: None.
Symptom: The "wavelength used for inband management" field appears as NO in the show interface command output on the WaveEthernetPhy interface for the 10-Gbps ITU and 2.5-Gbps ITU trunk cards.
Workaround: None.
Symptom: System crashes when inserting an OADM into the Cisco ONS 15530 chassis after a CPU switch module switchover.
Workaround: None.
Symptom: An OADM is not recognized after a CPU switch module switchover if there is only one OADM present in the chassis.
Workaround: Reload the shelf.
Symptom: The 2.5-Gbps ITU trunk card with revision F QPHY is not working properly. Traffic cannot pass through it and a lot of CRC/HEC errors occur.
Workaround: None.
Symptom: The 8-port GE/FC aggregation card portgroup SII mismatch error counter increments when connected to a 2.5-Gbps ITU trunk card. This does not cause problems for client traffic.
Workaround: None.
Symptom: When the running-configuration or startup-configuration is copied to the network, the following messages appear on the console:
01:29:17:%CPU_REDUN-6-RUNNING_CONFIG_CHG: Running config on this CPU has possibly changed 01:29:18: %CPU_REDUN-5-RCSF_SYNCED: Running config successfully synced to standbyWorkaround: Use the Cisco IOS CLI to avoid these messages. Copying the configurations (running or startup) through the command-line interface does not result in these messages.
Symptom: When configuring SII on the 10-Gbps ITU trunk card, a loss of SII results in the look up table.
Workaround: OIR the ESCON card to regain and reprogram the SII look up table of the 10-Gbps ITU trunk card.
Symptom: The system may reload unexpectedly during a CPU switchover.
Workaround: Remove the non-recognized 8-port GE/FC aggregation card and then perform the CPU switchover.
Symptom: The OSC wave interface does not come up when a trunk cable breaks and you configure LSC and trunk insertion.
Workaround: Disable and then enable LSC again to bring up the OSC wave interface.
Symptom: A client interface laser may be off when it is configured in a disabled y-cable APS group.
Workaround: Enable then disable the APS group. This activates the client interface laser.
Symptom: Laser safety control does not enable on the wave interface in FPGA after reprogramming the FPGA in an OSC daughter card.The running configuration shows laser safety control enabled on the OSC wave interface.
Workaround: Enable and disable laser safety control on the wave interface to enable it in the FPGA.
Symptom: Performing an OIR of the 10-Gbps ITU trunk card on the chassis results in the display of an LRC ID check fail error message.
Workaround: None.
Symptom: Performing a CPU switchover while ESCON traffic is flowing through results in continuous CRC errors received on the 2.5-Gbps ITU trunk card Tx FPGA from the backplane.
Workaround: OIR the 2.5-Gbps ITU trunk card.
Symptom: In a redundant CPU switch module system, removing the active CPU switch module and reinserting it does not immediately list the inserted CPU switch module in the show hardware command output after the configuration sync. The show redundancy output displays that the system is in hot standby and a CPU switch module switchover will happen correctly. An OIR-detect message appears on the console 5 minutes after the configuration sync and the show hardware command output lists both the CPU switch modules from this point.
Workaround: None
Symptom: When an ESCON transceiver is removed and the card is cross connected to a 2.5-Gbps ITU trunk card, there are continuous messages on the console.
Workaround: None.
Symptom: When trying to boot from 12.1(12c)EV1 code in the bootflash, the reload fails and the 15530 is booted into ROMMON mode.
Workaround: Disable the Power On Diagnostics in ROMMON Mode and reload the 15530. Or remove the large number of "*"s in the banner.
Symptom: When performing a CPU switch module reload, a crash might occur.
Workaround: None.
Symptom: Performing an OIR of an 2.5-Gbps or 10-Gbps ITU trunk card might result in an unexpected system reload.
Workaround: None.
Symptom: The following OSC module errors occur at a CPU switch module switchover:
%SRC-3-LC_REG_READ_FAIL: Register read failed for slot 7, addr 0x540100 due to RCI timeout%SRC-3-LC_REG_WRITE_FAIL: Register write failed for slot 7, addr 0x540100 due to RCI timeoutWorkaround: Upgrade the system image to release 12.1(12c)EV3 or later.
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 LUT of the ESCON aggregation card. As a result, the old flow-identifier cannot be re-used on the this ESCON aggregation card.
Workaround:
Workaround 1
Issue the following sequence of commands in the 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] >
Workaround 2:
OIR the ESCON aggregation card.
Symptom: In a point-to-point network topology setup where bidirectional PSM trunk fiber protection APS is configured, and the message-channel is configured for inband dcc and the controller type of the OADM filter is 0x1104 (4-channel OADM without OSC), APS is unable to track a valid ethernetDcc interface. Therefore the group cannot be associated.
Workaround: Do not configure message-channel as inband dcc for PSM APS if the corresponding OADM module does not have OSC ports (controller type 0x1104).
Symptom: Y-cable switchover fails when a TX fault is asserted for a very short while due to the SFP optics on the 8-port FC/GE aggregation card causing the BLC to kick in and shut down the laser.
Workaround: Replace the SFP optics.
Symptom: Upon recovery from a shut down due to fan failure, the Cisco ONS 15530 does not recognize all line cards.
Workaround: Re-boot or power cycle the Cisco ONS 15530.
Symptom: The correct hexadecimal value does not display for cifthIfThresholdsFired object for some particular bitmap patterns.
Workaround: None.
Symptom: Power-on diagnostics do not recognize the PSM.
Workaround: Upgrade the system image to release 12.1(12c)EV2 or later.
Symptom: Failures are seen on the bp-idprom-test of the CPU switch module.
Workaround: None.
Symptom: The system reloads during power-on diagnostics with the 8-port FC/GE aggregation card POD configurations and when booted with release 12.1(12c)EV1 or earlier. This issue is not seen with release 12.1(12c)EV2 which supports POD for the 8-port FC/GE aggregation card.
Workaround: Disable the power-on diagnostics in ROM monitor mode by setting POD_DISABLE=yes. Remove the power-on diagnostic configuration for the 8-port FC/GE aggregation card before reload or switchover.
Symptom: Power-on diagnostics may fail the credit-buffer-memory test for the 8-port FC/GE aggregation card on the first boot after power cycling the box. Subsequent reboots without power cycling pass the test. These test failures are spurious and can be ignored.
Workaround: Upgrade you Cisco ONS 15530 software to Cisco IOS Release 12.2(23)SV or later.
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.
•
CPU Switch Modules
This section contains limitations and restrictions that apply to transponder modules.
•
Note
Related Documentation
Refer to the following documents for more information about the Cisco ONS 15530:
•
•
•
•
•
•
•
•
•
•
•
•
•
Obtaining Documentation
Cisco provides several ways to obtain documentation, 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
Documentation CD-ROM
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which may have shipped with your product. The Documentation CD-ROM is updated regularly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual or quarterly subscription.
Registered Cisco.com users can order a single Documentation CD-ROM (product number DOC-CONDOCCD=) through the Cisco Ordering tool:
http://www.cisco.com/en/US/partner/ordering/ordering_place_order_ordering_tool_launch.html
All users can order monthly or quarterly subscriptions through the online Subscription Store:
http://www.cisco.com/go/subscription
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 comments electronically on Cisco.com. On the Cisco Documentation home page, click Feedback at the top of the page.
You can e-mail your comments 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
Cisco provides Cisco.com, which includes the Cisco Technical Assistance Center (TAC) website, as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from the Cisco TAC website. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC website, including TAC tools and utilities.
Cisco.com
Cisco.com offers a suite of interactive, networked services that let you access Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com provides a broad range of features and services to help you with these tasks:
•
•
•
•
•
To obtain customized information and service, you can self-register on Cisco.com at this URL:
http://tools.cisco.com/RPF/register/register.do
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: the Cisco TAC website and the Cisco TAC Escalation Center. The type of support that you choose depends on the priority of the problem and the conditions stated in service contracts, when applicable.
We categorize Cisco TAC inquiries according to urgency:
•
•
•
•
Cisco TAC Website
The Cisco TAC website provides online documents and tools to help troubleshoot and resolve technical issues with Cisco products and technologies. To access the Cisco TAC website, go to this URL:
All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC website. Some services on the Cisco TAC website require 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 this URL to register:
http://tools.cisco.com/RPF/register/register.do
If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC website, you can open a case online at this URL:
http://www.cisco.com/tac/caseopen
If you have Internet access, we recommend that you open P3 and P4 cases online so that you can fully describe the situation and attach any necessary files.
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 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.
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/en/US/products/products_catalog_links_launch.html
•
•
http://www.cisco.com/go/packet
•
http://www.cisco.com/go/iqmagazine
•
http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html
•
http://www.cisco.com/en/US/learning/le31/learning_recommended_training_list.html
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
CCIP, CCSP, the Cisco Arrow logo, the Cisco Powered Network mark, Cisco Unity, Follow Me Browsing, FormShare, 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 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, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, MGX, MICA, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, ScriptShare, SlideCast, SMARTnet, StrataView Plus, Stratm, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, 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. (0304R)
Copyright © 2003 Cisco Systems, Inc. All rights reserved.
Printed in the USA on recycled paper containing 10% postconsumer waste.
Posted: Sat Jul 31 12:52:27 PDT 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
