|
|
Table Of Contents
Release Notes for Cisco ONS 15540 ESPx
for Cisco IOS Release 12.1(12c)EV2Determining the Software Version
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)EV3
New Features in Release 12.1(10)EV2
Obtaining Technical Assistance
Obtaining Additional Publications and Information
Release Notes for Cisco ONS 15540 ESPx
for Cisco IOS Release 12.1(12c)EV2
This document describes caveats for Cisco IOS Release 12.1(12c)EV2 for the Cisco ONS 15540 ESPx.
Date: June 16, 2004
Text Part Number: OL-3404-05
Contents
This document includes the following information:
•
Caveats
•
•
•
Introduction
The Cisco ONS 15540 ESPx is an optical transport platform that employs DWDM (dense wavelength division multiplexing) technology. With the Cisco ONS 15540 ESPx, users can take advantage of the availability of dark fiber to build a common infrastructure that supports data, SANs (storage area networks), and TDM (time-division multiplexing) traffic. The system uses an enhanced chassis with front fiber optic cable access for optical interconnections between transponder modules and optical mux/demux modules. For more information about DWDM technology and applications, refer to the Introduction to DWDM Technology publication and the Cisco ONS 15540 ESPx Planning Guide.
System Requirements
This section describes the system requirements for Cisco IOS Release 12.1(12c)EV2 and includes the following sections:
•
Memory Requirements
The DRAM memory configuration is 128 MB, which is the default for the Cisco ONS 15540 ESPx.
Hardware Supported
Table 1 lists the hardware components supported on the Cisco ONS 15540 ESPx and the minimum software version required. See the "Determining the Software Version" section.
Determining the Software Version
Note
To determine the version of Cisco IOS software currently running on a Cisco ONS 15540 ESPx system, log in to the system and enter the show version EXEC command.
Upgrading the System Image
To ensure proper system functioning, follow the system image upgrading procedure described in the Cisco ONS 15540 ESPx Software Upgrade Guide.
Note
Caution
Feature Set Table
The Cisco IOS Release software is packaged in feature sets (also called software images) depending on the platform. Each feature set contains a specific set of Cisco IOS software features. Table 2 lists the Cisco IOS software feature sets available for the Cisco ONS 15540 ESPx.
Table 2 Feature Sets Supported by the Cisco ONS 15540 ESPx
Gigabit Ethernet
X
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
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 SM (200 Mbps)
X
X
X
X
X
X
FICON6 (800 Mbps)
X
X
X
X
X
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
CDP7
X
X
X
X
X
X
IP packets
X
X
X
X
X
X
OSCP8
X
X
X
X
X
X
APS9 protocol packets
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
X
X
X
X
X
X
IBM GDPS 10 coupling link
X
X
X
X
X
X
Unidirectional path switching
X
X
X
X
X
X
Bidirectional path switching
X
X
X
X
X
X
CDL over 10 GE
X
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 CDP = Cisco Discovery Protocol
8 OSCP = Optical Supervisory Channel Protocol
9 APS = Automatic Protection Switching
10 GDPS = Geographically Dispersed Parallel Sysplex
11 ETR/CLO = external timer reference/control link oscillator
New and Changed Information
This section lists new features that appear in Cisco IOS Release 12.1.
New Features in Release 12.1(12c)EV2
The following new feature is available for the Cisco ONS 15540 ESPx in Cisco IOS Release 12.1(12c)EV2:
•
New Features in Release 12.1(12c)EV1
The following new feature is available for the Cisco ONS 15540 ESPx in Cisco IOS Release 12.1(12c)EV1:
•
New Features in Release 12.1(12c)EV
The following new feature is available for the Cisco ONS 15540 ESPx in Cisco IOS Release 12.1(12c)EV:
•
New Features in Release 12.1(10)EV3
No new features are available for the Cisco ONS 15540 ESPx in Cisco IOS Release 12.1(10)EV3.
New Features in Release 12.1(10)EV2
The following new features are available for the Cisco ONS 15540 ESPx in Cisco IOS Release 12.1(10)EV2:
•
–
–
–
•
–
Caveats
This section lists the caveats and corrected caveats for each release. Use Table 3 to determine the status of a particular caveat. In the table, "C" indicates a corrected caveat, and "O" indicates an open caveat.
This section describes the caveats in the Cisco ONS 15540 ESPx.
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: Loss of signal might occur before SD (signal degrade) and SF (signal failure) thresholds are exceeded and traffic may still continue to pass transparently.
The loss of signal detection is taken from the O-E (optical to electrical) conversion subsystem, which is different from the source of the SD and SF counters. The loss of light sensitivity is a characteristic of the OE conversion unit, and it may vary from unit to unit but is always < -30 dBm.
Workaround: None.
Symptom: When the Rx port fiber is removed from the 2.5-Gbps transponder module, ingress alarms are reported and cleared repeatedly. The alarm should not clear and the alarm should be reported only once.
Workaround: None
Symptom: The processor card is not responsive.
Workaround: None
Symptom: The processor card is not responsive for an extended period of time, during which time the ACTIVE and STANDBY LEDs might not indicate the correct active and standby state.
Workaround: If the processor card has not been reset by the redundant processor card, the nonresponsive processor card can be removed and reinserted in the chassis. This may cause a brief disruption to data traffic, but the redundant processor card should take over and bring the system back up.
Symptom: Reprogramming the standby processor card fails.
Workaround: Run the reprogram on the active processor card, enable the processor switchover after switchover, and then run the reprogram on the new active processor card. Remove and reinsert the processor card for the new functional image to become effective.
Symptom: The encapsulation fastethernet command fails on multimode transponder modules. The clock rate 100000 command succeeds but then pings over the signal fail intermittently.
Workaround: None.
Symptom: The show interfaces command output for a wave interface displays an UP state, but the signal quality shows loss of sync.
Workaround: None.
Symptom: Multiple %METOPT-2-PORTFAIL messages are seen when using the y-cable APS configuration with single auto-failover. However, this does not affect the functionality.
Workaround: None.
Symptom: CiscoView might display a different receive LED status on 2.5-Gbps transponder modules from what is actually seen on the device.
Workaround: None.
Symptom: Inserting a transponder module with the client equipment connected and transmission enabled disrupts y-cable clients.
Workaround: Remove client transmit fiber (y-cable leg) from the standby transponder module before reinserting. Connect it back a few seconds after reinsertion of the standby transponder module.
Symptom: Topology neighbor configuration is lost on mux-demux motherboard online removal and reinsertion.
Workaround: The topology neighbor is viewable after reconfiguring the wdm interface.
Symptom: Interface reports up/up even when there is no light source connected.
Workaround: Perform a shutdown /no shutdown command sequence on the interface.
Symptom: A transparent interface carrying Gigabit Ethernet traffic and configured with 1-Gbps 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: Removing and reinserting the 2.5-Gbps transponder module will bring it to the correct state.
Symptom: The LOF alarms do not reassert in the show facility-alarm status command output after a shutdown/no shutdown command sequence.
Workaround: Disabling and reenabling the monitoring for the transparent interface brings back the alarms.
Symptom: The show facility-alarm status command output does not report existing LoF/LoSync/LoLock alarms after online removal and reinsertion or a hw-module subslot power off/hw-module subslot power on command sequence.
Workaround: Disable and enable monitoring back reasserts existing alarms in the show facility-alarm status command output.
Symptom: After removing and reinserting (OIR) a 2.5-Gbps transponder module, the laser frequency is not programmed correctly, resulting in a wavelength filter mismatch and the wavelength not coming out of the filter.
Workaround: Configure the wave interface for the alternate frequency and then program it back to the desired frequency using the laser frequency command.
Symptom: The line card motherboard functional image version in the show hardware command output should return the hexadecimal value.
Workaround: None.
Symptom: The processor card becomes nonresponsive waiting for the console UART TxReady to be set. Normally a watchdog timeout forces recovery, but in some instances the standby processor card does not recover on its own.
Workaround: Remove and reinsert the standby processor card.
Symptom: Under some situations the erratas of the system controller used on the processor card (GT64120A) can cause the following conditions:
–
–
–
Workaround: None.
Symptom: Processor card becomes nonresponsive and does not respond to an NMI.
Workaround: Update processor card functional image to version 1.25 or higher.
Symptom: A compatibility problem was detected in the released images that caused them to reject communication with the new images with a different cpu_red client version. This causes the active processor card to reset the peer processor card.
Workaround: Because this problem comes into existence only if the cpu_red client version is different between two images, this problem doesn't exist in the old released images. Because the new images with the incremented capered client version contains the fix for compatibility as well, this bug should not cause any impact in the field.
Symptom: Information appears in show hardware command output for processor cards that have been removed.
Workaround: None.
Symptom: If a client interface is configured for CDL but is connected to a non-CDL device, the CDL message channel is down.
Workaround: Ensure that the client interface is configured correctly.
Symptom: Under some circumstances, single bit ECC errors occur and are corrected by the system controller, but are not recorded; the user is unaware of these occurrences.
Workaround: None.
Symptom: If a module is inserted during a processor card switchover, then the module and its interfaces might not come up properly.
Workaround: Remove and reinsert module after switchover is complete.
Symptom: The system might crash when using the is_optical_ifstatus_up command; this is an intermittent problem.
Workaround: None.
Symptom: In a configuration where a Cisco ONS 15540 ESPx has 10-GE downlinks to two Cisco ONS 15530 systems, the tengigethernetphy interface is administratively shut down and the ESCON ports associated with the first Cisco ONS 15530 are also shut down. However, the ESCON ports connected to the second Cisco ONS 15530 remain up.
Workaround: Shut down the tengigethernetphy interface associated with the second Cisco ONS 15530.
Symptom: Following a processor card crash and switchover, if a show redundancy command is issued on the new active processor card, it currently shows "Reported Switchover Reason" as "Not known". If a show version is issued on the standby processor card that crashed, it shows additional troubleshooting information.
Workaround: None.
Symptom: The active processor card becomes nonresponsive and cannot be enabled from the standby processor.
Workaround: Remove and reinsert the active processor card.
Symptom: A getmany command on the ifMIB hangs in a loop.
Workaround: None.
Symptom: Mode-mismatch events or traps are set or generated 15 minutes after the misconfiguration that causes it is configured on the system.
Workaround: None.
Symptom: From SNMP, ptopoConnEntry can be created with entPhysicalIndex, which does not correspond to any valid interface on the system.
Workaround: None.
Symptom: Configuring both the client side and the trunk side for loopback on the 10-GE transponder module disrupts the traffic flow.
Workaround: Reconfigure the 10-GE transponder module with loopback only on the client side or the trunk side, not both. Remove and reinsert the 10-GE transponder module to restore traffic.
Symptom: Incorrect OPM alarm status information for the standby wavepatch interface displays in the show interfaces command output.
Workaround: None.
Symptom: CDL HEC counters are displayed in the show interfaces tengigethernetphy command output when CDL is disabled.
Workaround: None.
Symptom: Traffic disruption on bootup or switchover occurs if 10-Gbps ITU trunk card client side is CDL disabled but has cdl defect-indication force hop-endpoint configured on both the client and trunk.
Workaround: Use the no cdl defect-indication force hop-endpoint command on the client side.
Symptom: Unable to manage a system configured with EIGRP after a processor card switchover.
Workaround: Connect to the console port and remove the passive-interface config in EIGRP configuration.
Symptom: The DI error message does not indicate DI bit status.
Workaround: None.
Symptom: Line laser failure is not reported in the show facility-alarm status command output when the SFP optics in an extended range transponder module is removed and inserted online.
Workaround: None.
Symptom: Some interfaces are not available to the NMS station because the agent does not create them when the module is removed and reinserted.
Workaround: Reload the system after removal and reinsertion of the modules.
Symptom: APS message channel configured for UDP/IP does not work over more than two IP hops. The UDP/IP packet is dropped at the end of the second hop.
Workaround: None.
Symptom: The show patch detail command output does not reflect the correct patch status for the ITU direct insertion module and the mux/demux module after the online removal and insertion of a 10-GE transponder module.
Workaround: None.
Symptom: Traceback @optical_idb_wave_ethernet_phy_report.
Workaround: None.
Symptom: Both active and standby lasers in a bidirectional y-cable APS configuration on modules in subslot 0 turn on erroneously.
Workaround: This bug has been fixed by using the correct format for programming the switchover-command register.
Symptom: The redundancy reload shelf command on the active processor card can cause a switchover if the peer processor card is in ROM monitor mode.
Workaround: Use the reload command to reload the active processor card, if the peer processor card is in ROM monitor mode.
Symptom: All OPM interval entries are not returned by the getnext command.
Workaround: None.
Symptom: ciscoFlashDeviceChangeTrap is not generated when a removable Flash device is removed or inserted.
Workaround: None.
Symptom: When the forward laser control is enabled on the 10-GE transponder module and the waveethernetphy interface laser is shut by this safety feature, the laser soft-start procedure has to be followed when the laser is enabled again.
Workaround: None.
Symptom: The egress loss of signal alarm is not reasserted in the show facility-alarm status command output after using a hw-module subslot power command to turn the module power off or on.
Workaround: None.
Symptom: The wave interface remains down when the signal quality is GOOD after using a hw-module subslot power command to turn the module power off or on.
Workaround: None.
Symptom: The Rx power display in some cases is off by ±4 dBm in comparison with the real reading using power meter.
Workaround: Use a calibrated transponder module.
Symptom: The default laser frequencies of the 2.5-Gbps transponder modules in an odd numbered subslots (for example, x/1 or x/3) are not restored correctly after the second online removal and insertion. The laser frequencies are stored correctly for the first online removal and insertion only.
For example, when inserting a 2.5-Gbps transponder module (channel n and channel n+1) to subslot x/1 the first time, the default laser frequency is n+1 (correct). Remove this 2.5-Gbps transponder module and insert another (channel m and channel m+1); the default laser frequency becomes m (incorrect; it should be m+1).
Workaround: Remove and reinsert the 2.5-Gbps transponder module.
Symptom: While performing an aps switch force command on a splitter APS group for 10-GE transponder modules, an erroneous alarm clear message displays for a different slot/subslot card that is not part of the APS group.
Workaround: None.
Symptom: The Rx power display in some cases is off by ±4 dBm in comparison with the real reading using a power meter.
Workaround: Use calibrated 2.5-Gbps transponder modules.
Symptom: The wavepatch interfaces are stuck in the down state after using the shutdown/no shutdown command sequence on the corresponding wave interface with splitter APS after loss of light occurs.
Workaround: None.
Symptom: System crashes due to PCI master abort while doing a Sandisk removal and insertion.
Workaround: None.
Symptom: The low warning threshold alarm is not cleared in the show facility-alarm status command output.
Workaround: None.
Symptom: After a fiber cut, the OSC interface remains up with signal quality good.
Workaround: Issue the shutdown/no shutdown command.
Symptom: For the Sysplex protocol, forward laser control does not work after removing and reinserting the 2.5-Gbps transponder module and reprogramming the functional image.
Workaround: Using the no encapsulation and encapsulation sysplex etr commands on the transparent interface programs it correctly.
Symptom: When APS communication goes down, and an APS failure is subsequently detected, APS may switch over even though the communication is down. Based on this type of failure, there may be a unidirectional switchover. For IBM Sysplex CLO/ETR applications, unidirectional switchover may lead to data corruption.
Workaround: None.
Symptom: In a point-to-point bidirectional configuration, when the trunk Rx on both NEs are pulled and one of them is later replaced, APS might fluctuate between working and protection. Under certain conditions the driver declares both working and protection as down when the wave interface goes down.
In bidirectional APS this essentially means that the local side may inform the remote side that working/protection is down when it is not really down. APS has the ability to settle down on the good side; however, due to the bidirectional message (DO-NOT-REVERT in this case) from the far side; the local side switches away from the good side, and the cycle repeats. Note that this problem does not always happen, and requires certain timing for it to happen.
Workaround: Usea force switch or lockout to force the receive to the good side or temporarily change the direction from bidirectional to unidirectional after disabling the APS group.
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: In a preconfigured APS group (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 are defined in the APS group are created or remove the revertive configuration from the preconfigured APS group and then enable the group.
Symptom: Attempting to read a Flash card formatted on another system causes advisory messages to be continuously printed to the console.
Workaround: None.
Symptom: Attempting to read a Flash device formatted on another system causes advisory messages to be continuously printed to the console.
Workaround: None.
Symptom: Both working and protection client Tx are active in a y-cable APS configuration.
Workaround: None.
Symptom: The hw-module subslot power on/off command should not be supported for 10-GE transponder modules.
Workaround: None.
Symptom: Data traffic is disrupted during the processor card switchover when the splitter APS is configured.
Workaround: None.
Symptom: In y-cable bidirectional APS configuration using 10-GE transponder modules, whenever many CVRD errors are received on the standby trunk due to a bad signal (but still signal quality is GOOD in show interfaces command output), all four FDI-H/E and BDI-H/E bits in the DECCSR register might get latched. This generates interrupts and the console is flooded with messages for that interface such as the following:
00:15:17: %APS-3-PORT_FAIL: External Port Fail On WaveEthernetPhy10/1Workaround: Improve the quality of the signal by removing some attenuation and/or cleaning the optical connectors so that CVRD errors are not seen.
Symptom: Spurious memory access occurs on online removal and reinsertion of a 10-GE transponder module.
Workaround: None.
Symptom: When an invalid channel number is detected by the OSCP client while it processes the client message received from peer, OSCP does not free the message buffer. This results in buffer starvation over a period of time and connectivity through the Network Management interface and backplane Ethernet (IPC and OSCP) interface are lost.
Workaround: None.
Symptom: The optical alarms are not asserted or cleared correctly when the wave is in the administrative down state.
Workaround: Issue the shutdown/no shutdown command sequence on the active wavepatch, or issue the no shutdown command on wave interface to clear the false alarms.
Symptom: Receiver power low alarm and warning are not asserted on the wavepatch interface after switchover from the active wavepatch interface to the standby wavepatch interface.
Workaround: None.
Symptom: Continuous "SRC poll failure" messages are generated after removing a calibrated 2.5-Gbps transponder module and inserting an uncalibrated 2.5-Gbps transponder module or ITU direct insertion module.
Workaround: None.
Symptom: Using the no shutdown command on the tengigethernetphy or waveethernetphy interfaces (which is DOWN due to loss of lock) brings the interface state to UP, even though the loss of lock is still asserted.
Workaround: Issue the shutdown/no shutdown command sequence on the interface for it to show the DOWN state.
Symptom: Loss of sync is not reasserted on a tengigethernetphy interface after a shutdown/no shutdown command sequence has been issued on the interface, or on an online removal and reinsertion of the 10-GE transponder module.
Workaround: None.
Symptom: The ethernetdcc interface for 10-GE transponder module is not in the administrative down state on the initial online removal and reinsertion of the module.
Workaround: None.
Symptom: Loss of lock persists on a client interface that runs Sysplex CLO/ETR protocols.
Workaround: Issue the shutdown/no shutdown command sequence on the client interface to clear the loss of lock.
Symptom: Threshold group line is missing in the show interfaces waveethernetphy command output.
Workaround: None.
Symptom: The hardware reports spurious LoLock when the signal quality is good for the ETR encap after OIR (Online Insertion and Removal) of the transponder.
Workaround: Issue a no encapsulation command and configure the encapsulation back to Sysplex ETR.
Symptom: PSMs are incorrectly recognized as a mux/demux module with system images that do not support the PSM.
Workaround: Upgrade software to 12.1(12c)EV.
Symptom: The tengigEthernetPhy interface is getting BDI_H while the in-band message channel is disabled.
Workaround: None.
Symptom: Traffic loss of 30 to 45 seconds may occur when a y-cable APS configuration with protection switchover is used with the Catalyst 6000 family.
Workaround: Disable autonegotiation and enable debounce timer with a 100-ms delay on Catalyst 6000 family using the set port debounce mod/port enable command.
Symptom: When y-cable APS is configured, shutting off the power to the transponder module using the hw-module subslot power off command brings the power back on again immediately.
Workaround: Remove the APS configuration and perform power off.
Symptom: The signal monitoring information is missing for the GE encapsulation in the show interfaces command output.
Workaround: None.
Symptom: When both wavepatch interfaces are in an ADMIN DOWN state, the signal quality is unknown but the show facility-alarm status command reports Loss of Signal.
Workaround: None.
Symptom: APS switchover time (50 ms) is not guaranteed for loss of lock, loss of sync, or loss of frame. It is only guaranteed for loss of light.
Workaround: None.
Symptom: The output of the show waveethernetphy interface command sometimes shows a high receive power value when there is no input signal connected to the card.
Workaround: OIR the card.
Symptom: Could not get a wave interface power reading graph with CiscoView 2.0/2.1 for an uncalibrated transponder module.
Workaround: Use a calibrated transponder module.
Symptom: When the 10-GE transponder module (waveethernetphy) laser is down due to a forward laser control action, removing the forward laser control configuration does not turn the laser back on.
Workaround: None.
Symptom: OPM (optical power monitoring) feature does not work on uncalibrated 2.5-Gbps transponder modules.
Workaround: None.
Symptom: Cannot disable SNMP-server traps for TTY messages on a global basis.
Workaround: Configure traps on a per SNMP-server host basis.
Symptom: An internal error and a traceback result when a threshold group with transmit-CRC failure and transmit-CRC degrade is modified such that the index reaches 63 and the new Tx-CRC threshold is attempted to be added.
Workaround: None.
Symptom: The standby processor card in the CiscoView shelf display shows a 100-Mbps connection even though the NME port is connected to a 10-Mbps hub or switch.
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: The optical power monitoring alarms and configuration are missing across a 2.5-Gbps transponder module online removal and insertion.
Workaround: 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 requiring a manual intervention to enable the ports.
Workaround: None.
Symptom: A spurious memory access at manopt_tl1_report_aps_defect occurs during the processor switchover when APS is configured.
Workaround: None.
Symptom: The transponder module traceback messages might flood the console, causing processor usage to increase to the point that it becomes unresponsive to the console and to network access.
Workaround: OIR the transponder module (or the entire line card motherboard if all the transponder modules on the line card motherboard are failing. Ensure that all modules and line cards are seated properly and locked or screwed down.
Symptom: When a client loss of signal (loss of light/loss of lock) condition occurs on an extended range transponder module, typically by disconnecting the client from the transponder module or when the client device halts transmission briefly during an initialization sequence, the following might occur:
–
–
Neither of these conditions affect the functioning or life span of the laser. The laser power output will stabilize and return to normal operation when a valid client signal is connected.
Workaround: Enable forward laser control using the laser control forward enable command on the wave interface. Or keep the wave interface shutdown when there is no client signal, but issue the no shutdown command on the wave interface when the client signal is reconnected.
Symptom: The extended range transponder configured with FDDI encapsulation when connected with FDDI ports on a Catalyst 5000 causes the Catalyst 5000 port to take more than seven seconds to initialize if an Rx fiber break and insertion is done at the transponder client receive end.
Workaround: None.
Symptom: With particular OC48 SFPs in a Y cable APS setup with extended range transponders, the Tx default on the SFP does not allow the client laser to enable because of the BLC.
Workaround: None.
Symptom: MPL for splitter and y cable APS protection schemes should indicate losync/loframe/lolock instead of lolight
Workaround: None
Symptom: The OPM alarms (low warning and low alarm) are not being reasserted after issuing a the shutdown/no shutdown command sequence on the wavepatch x/y/0 interface.
Workaround:OIR the subcard to reassert the alarms.
Symptom: Enabling CDL on the tengigethernetphy interface on the 10-Gbps transponder module might result in traceback messages. This does not affect the system.
Workaround: None.
Symptom: Inserting the 10-Gbps transponder module and reloading IOS results in SRC %SRC-3-LC_CMI_INTF_FAULT error messages.
Workaround: None.
Limitations and Restrictions
This section provides limitations and restrictions for Cisco ONS 15540 ESPx hardware and software.
Transponder Modules
This section contains limitations and restrictions that apply to transponder modules.
•
•
Data errors or link-down conditions for 2-Gbps Fibre Channel might occur on single-mode transponder modules 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 module client side receiver. The average transmitted power level from the GBIC does not violate the overload specification of the transponder module client side receiver, so a power meter does not detect the overload.
The workaround is to attenuate the signal from the client equipment to a recommended level of -12 dBm when transmitting 2-Gbps Fibre Channel services.
•
•
–
–
–
–
Note
Related Documentation
Refer to the following documents for more information about the Cisco ONS 15540 ESPx:
•
•
•
•
•
•
•
•
•
•
•
•
•
Obtaining Documentation
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.
Posted: Wed Nov 3 16:29:41 PST 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
