|
|
Table Of Contents
Release Notes for Cisco ONS 15540 ESP
for Cisco IOS Release 12.1(12c)EV1Determining the Software Version
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
New Features in Release 12.1(12c)E1
New Features in Release 12.1(12c)E
New Features in Release 12.1(11b)E1
New Features in Release 12.1(11b)E
New Features in Release 12.1(7a)EY3
New Features in Release 12.1(7a)EY2
Obtaining Technical Assistance
Obtaining Additional Publications and Information
Release Notes for Cisco ONS 15540 ESP
for Cisco IOS Release 12.1(12c)EV1
This document describes caveats for Cisco IOS Release 12.1(12c)EV1 for the Cisco ONS 15540 ESP (Extended Services Platform).
Date: March 31, 2003
Text Part Number: OL-3341-04
Contents
This document includes the following information:
•
Caveats
•
•
Introduction
The Cisco ONS 15540 ESP is an optical transport platform that employs DWDM (dense wavelength division multiplexing) technology. With the Cisco ONS 15540 ESP, users can take advantage of the availability of dark fiber to build a common infrastructure that supports data, SAN (storage area networking), and TDM (time-division multiplexing) traffic. For more information about DWDM technology and applications, refer to the Introduction to DWDM Technology publication and the
Cisco ONS 15540 ESP Planning and Design Guide.System Requirements
This section describes the system requirements for Cisco IOS Release 12.1(12c)EV and includes the following sections:
•
Memory Requirements
The DRAM memory configuration is 128 MB, which is the default for the Cisco ONS 15540 ESP.
Hardware Supported
Table 1 lists the hardware components supported on the Cisco ONS 15540 ESP 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 ESP 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-15540 Software (ONS15540-I-M), Version 12.1(12c)EV <Information deleted>Upgrading the System Image
To ensure proper system functioning, follow the system image upgrading procedure described in the Cisco ONS 15540 ESP Configuration Guide and Command Reference.
Note
Caution
Feature Set Table
The Cisco IOS Release software is packaged in feature sets (also called software images) depending on the platform. Each feature set contains a specific set of Cisco IOS features. Table 2 lists the Cisco IOS software feature sets available for the Cisco ONS 15540 ESP.
Table 2 Feature Sets Supported by the Cisco ONS 15540 ESP
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
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 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
IP packets
X
X
X
X
X
X
OSCP7
X
X
X
X
X
X
APS8 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 9 coupling link
X
X
X
X
X
X
CDL over 10-GE
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 GDPS = Geographically Dispersed Parallel Sysplex
10 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)EV1
The following new feature is available for the Cisco ONS 15540 ESP in Cisco IOS Release 12.1(12c)EV1:
•
New Features in Release 12.1(12c)EV
No new features are available for the Cisco ONS 15540 ESP 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 ESP 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 ESP in Cisco IOS Release 12.1(10)EV2:
•
–
–
–
•
–
New Features in Release 12.1(12c)E1
No new features are available for the Cisco ONS 15540 ESP in Cisco IOS Release 12.1(12c)E1.
New Features in Release 12.1(12c)E
No new features are available for the Cisco ONS 15540 ESP in Cisco IOS Release 12.1(12c)E.
New Features in Release 12.1(11b)E1
No new features are available for the Cisco ONS 15540 ESP in Cisco IOS Release 12.1(11b)E1.
New Features in Release 12.1(11b)E
The following new features are available for the Cisco ONS 15540 ESP in Cisco IOS Release 12.1(11b)E:
•
–
–
–
–
–
–
–
New Features in Release 12.1(7a)EY3
The following new software features are available for the Cisco ONS 15540 ESP in Cisco IOS Release 12.1(7a)EY3:
•
•
•
•
•
•
•
•
•
•
•
•
•
New Features in Release 12.1(7a)EY2
The following new features are available for the Cisco ONS 15540 ESP in Cisco IOS Release 12.1(7a)EY2:
•
•
•
•
•
•
•
•
•
•
•
•
•
Caveats
This section lists the caveats and corrected caveats for each release. Use Table 3 and Table 4 to determine the status of a particular caveat. In the tables, "C" indicates a corrected caveat, and "O" indicates an open caveat.
This section describes the caveats in the Cisco ONS 15540 ESP.
Symptom: Cisco routers and switches running Cisco IOS software and configured to process Internet Protocol version 4 (IPv4) packets are vulnerable to a Denial of Service (DoS) attack. A rare sequence of crafted IPv4 packets sent directly to the device may cause the input interface to stop processing traffic once the input queue is full. No authentication is required to process the inbound packet. Processing of IPv4 packets is enabled by default. Devices running only IP version 6 (IPv6) are not affected.
Workaround: Cisco has made software available, free of charge, to correct the problem. This advisory is available at http://www.cisco.com/warp/public/707/cisco-sa-20030717-blocked.shtml.
Symptom: Cannot disable SNMP-server traps for TTY messages on a global basis.
Workaround: Configure traps on a per SNMP-server host basis.
Symptom: OPM (optical power monitoring) feature does not work on uncalibrated 2.5-Gbps transponders modules.
Workaround: None.
Symptom: The optical power monitoring alarms and configuration are missing across the 2.5-Gbps transponder module online removal and insertion.
Workaround: None.
Symptom: If you attempt to change or edit a threshold in the threshold list that is already associated with an interface, the threshold is applied to that interface even when no changes are made to it.
Workaround: Issue the clear counters command.
Symptom: If CiscoView files are extracted on a Flash disk (disk0: or disk1:), the package does not work.
Workaround: Install CiscoView on a Flash PC Card (slot0: or slot1:).
Symptom: When there is a constant stream of loss of sync alarms, a port fail notification is not generated.
Although both signal failure and signal degrade thresholds are applied, only signal degrade is observed. The signal failure threshold is monitored by hardware registers. When the signal failure threshold is exceeded, the hardware normally generates a port fail notification. Because the loss of sync alarms are constant, the threshold exceeded cannot generate a port fail notification. The signal degrade is reported because it is monitored by software and does not need any notifications from hardware.
Workaround: Disable and reenable monitoring once with the no monitor/monitor enable command sequence to generate the port fail notification.
Symptom: Upon switchover, the active processor card might become nonresponsive. The processor card Active LED remains on, even though it is no longer actively controlling the system.
Workaround: OIR the processor card to correct the fault.
Symptom: The ROM monitor might continuously loop in an attempt to autoboot a missing system image.
Continuous looping happens when autoboot is configured in the configuration register (0x2102), but the system image corresponding to the system boot filename command in the startup configuration is missing and no alternate system boot filename command is configured for an existing system image.
During normal system functioning, the system first checks for system image file names in the startup configuration system boot filename commands. If there are none, or the images are not valid, the system checks the Flash device in slot0: and then bootflash for loadable images before stopping its attempts to autoboot.
Workaround: Configure at least one system boot filename command for an existing system image on both processor cards before reloading either processor card.
If autoboot looping occurs, issue a console send break command during the first few seconds of a reload attempt to stop autobooting. Then manually boot the system using a valid system image in Flash memory or on the network.
Upgrade the processor card ROMMON image to release 12.1(11r)E3 or later.
Symptom: If during a netboot attempt the processor card fails to netboot or the peer processor card changes its Active/Standby state, any further changes to the peer processor card Active/Standby state are ignored until a reset command is issued at the processor card ROMMON prompt.
Workaround: Issue a reset command at the ROMMON prompt after failing to netboot.
Upgrade the processor card ROMMON image to release 12.1(11r)E3 or later.
Symptom: An error can occur with management protocol processing. Please see the following URL for more information:
http://www.cisco.com/cgi-bin/bugtool/onebug.pl?bugid=CSCdw65903Workaround: None
Symptom: Following a Cisco IOS software crash, a second ROMMON exception might cause the original stack trace to be lost. This happens if a pending PCI (peripheral component interconnect) bus interrupt was in progress but was not handled before the IOS crash.
Workaround: Upgrade the processor card ROMMON image to release 12.1(11r)E3 or later.
Symptom: The following errors might occur:
–
–
–
–
Workaround: None.
Symptom: The system power cycles and the standby processor card startup configuration is not synchronized with the active processor card startup configuration. If this occurs, then the previous standby processor card might become the active processor card and a different set of connections might be set up.
The standby processor card startup configuration can become outdated when it is in maintenance mode.
Workaround: Remove the standby processor card from the shelf when it is not in use.
Upgrade the processor card ROMMON image to release 12.1(11r)E3 or later.
Symptom: Loopback cannot be configured on the wave interface of an extended range transponder module if no transceiver is present. The loopback command is accepted but the loopback is not configured.
Workaround: Insert a transceiver before configuring the loopback on the wave interface.
Symptom: When laser safety control is enabled on the OSC wave 0 interface or wave 1 interface, the OSC trunk laser does not shut down when a fiber cut occurs.
Workaround: None
Symptom: Loss of Signal may be encountered before SD (signal degrade) and SF (signal failure) thresholds are exceeded and traffic may still continue to pass transparently.
The loss of signal detection is taken from the OE conversion subsystem which is different from the source of the SD and SF counters. The OE conversion is not gated by its loss of light indication so the data and clock extraction continues and the signal is regenerated transparently. The loss of light sensitivity is a characteristic of the OE conversion unit and it may vary from unit to unit but is always < -30dBm.
Workaround: None.
Symptom: The alarm LED is not raised or cleared by SD/SF indications.
Workaround: None.
Symptom: If the configuration register autoboot field is set to either 0x1 or 0x2 and the first file in bootflash memory is not a loadable system image, then the system continues to try to reboot.
Workaround: Use the send break command on the console CLI to stop the autoboot cycling, and then manually boot a loadable system image. Make sure the first image in bootflash memory is a valid system image.
Upgrade the processor card ROMMON image to release 12.1(11r)E3 or later.
Symptom: With APS y-cable protection, SD condition on the working channel does not clear the lower priority manual-switch condition on the protection channel. This causes the manual switch to persist after the SD condition was removed and APS to switch back to the working channel.
Workaround: None.
Symptom: Customer installed mismatching wavelength 2.5-Gbps transponder modules and did not receive a wavelength mismatch alarm.
Workaround: None.
Symptom: When the Rx port fiber is removed, ingress alarms are reported and cleared repeatedly. The alarm should not clear and the alarm should be reported only once.
Workaround: None.
Symptom: Processor card gets into a nonresponsive state.
Workaround: None.
Symptom: No alarm is raised when the 2.5-Gbps transponder module channel does not match the channels supported by the mux/demux module.
Workaround: None.
Symptom: The reprogram for 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 FPGA to become effective.
Symptom: CTM is flooded with traps every second when hardware port flap alarms occur.
Workaround: None.
Symptom: The encapsulation fastethernet command fails on multimode transponder modules. The clock rate 100000 command succeeds but pings over the signal fail intermittently.
Workaround: None.
Symptom: The OSC intermittently drops IP packets because of an erroneous calculation of the FCS-16 (frame check sequence 16).
Workaround: None.
Symptom: The system image on the standby processor card cannot be upgraded to a new system image because the format of the redundancy messages from the active processor card are not recognized on the standby processor card. The standby processor card fails to boot and returns to ROMMON mode.
Workaround: None.
Symptom: Multiple %METOPT-2-PORTFAIL messages are seen when using the y-cable APS configuration with single AFOV. However, this does not affect the functionality.
Workaround: None.
Symptom: Topology neighbor configuration is lost on mux-demux motherboard OIR.
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: Issue a shutdown/no shutdown command on the interface.
Symptom: The transparent interface of an extended range transponder module continues to report good signal quality even after the transceiver is removed and reinserted.
Workaround: Issue a shutdown/no shutdown command sequence on the transparent 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: Remove and reinsert the 2.5-Gbps 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 2.5-Gbps transponder module.
Workaround: Disable and reenable monitoring on the transparent interface to reassert the alarms.
Symptom: The show facility-alarm status command output does not report existing LoF/LoSync/LoLock alarms after OIR/hw-mod power off/on.
Workaround: Disable and enable monitoring will reassert existing alarms in the show facility-alarm status.
Symptom: After removing and reinserting (OIR) of a 2.5-Gbps transponder module, the laser frequency is not programmed to the 2.5-Gbps transponder module correctly, which results 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: A line laser failure alarm is asserted but not cleared when an extended range transponder module is removed and reinserted. The show facility-alarm status command output shows a message similar to the following:
Source: TranspdrSC 2/3 Severity: MAJOR Description: 2 Line laser failure detectedWorkaround: None.
Symptom: The SF (signal failure) alarms are not cleared from the show facility-alarm status command output after monitoring is disabled.
Workaround: None.
Symptom: An ingress LoF alarm on a transparent interface is not asserted when an SEF (severely errored frames) alarm is present due to the alarm priority handling error in the driver.
Workaround: A shutdown/no shutdown command sequence on the transparent interface will reassert the ingress LoF alarm.
Symptom: The line card motherboard functional image version in the show hardware command output should return the hexadecimal value.
Workaround: None.
Symptom: Under some situations the erratas of the system controller used on the processor card (GT64120A) can cause the following conditions:
–
–
–
Workaround: None.
Symptom: The active processor card reset the standby processor card because of a compatibility problem detected in the system images.
Workaround: None.
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 two Cisco ONS 15530 systems are linked to a Cisco ONS 15540 ESP through 10-GE connections, the tengigethernetphy interface on one side is administratively shut down and the ESCON ports are down. However, the ESCON ports associated with the other Cisco ONS 15530 are still up.
Workaround: Shut down the tengigethernetphy interface associated with the second Cisco ONS 15530.
Symptom: Following a processor card crash and switchover, a show redundancy command issued on the new active processor card shows "Reported Switchover Reason" as "Not known". A show version command issued on the standby processor card that crashed shows additional troubleshooting information.
Workaround: None.
Symptom: A few kinds of software exceptions on the active processor card can disable the ability for the standby processor card to reset the active processor card if the active processor card becomes nonresponsive.
Workaround: None.
Symptom: The getmany command on the ifMIB causes the system to hang 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: The signal monitoring information is missing for the GE encapsulation in the show interface output.
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 will occur 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 configuration 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 will not be available to the NMS station since 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: None,
Symptom: The redundancy reload shelf command on the active processor card can cause a switchover if the standby processor card is in ROM monitor mode.
Workaround: Use the reload command to reload the active processor card, if the standby 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 +/-4dBm in comparison with the real reading using power meter.
Workaround: Use a calibrated 2.5-Gbps 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 a aps switch force command on 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 +/-4dBm in comparison with the real reading using power meter.
Workaround: Use a 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 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 the signal quality good.
Workaround: Issue the shutdown/no shutdown command sequence.
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 will program it correctly.
Symptom: When APS communication goes down, and an APS failure is subsequently detected, APS might switch over even though the communication is down. Based on this type of failure, a unidirectional switchover might occur. For IBM Sysplex CLO/ETR applications, a unidirectional switchover might 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 in order for it to happen.
Workaround: Use 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 pre-configured APS group and then enable the group.
Symptom: Attempting to read a flash device formatted on another system causes advisory messages to be continuously printed to the console.
Workaround: None.
Symptom: The processor crashes after midnight with optical performance monitoring on when an interface capable of performance monitoring is shutdown before 00-00hrs and unshut after midnight.
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/1
Workaround: 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 a peer, OSCP does not free the message buffer. This results in buffer starvation over a period of time and connectivity on 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 interface 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 a 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 admin down state on the initial online removal and reinsertion of the module.
Workaround: None.
Symptom: The threshold group line is missing in the show interfaces waveethernetphy command output.
Workaround: None.
Symptom: The hardware reports spurious Loss of Lock errors when the signal quality is good for the Sysplex ETR encapsulation after online removal and insertion of the 2.5-Gbps transponder module.
Workaround: Issue a no encapsulation command and configure the encapsulation back to Sysplex ETR.
Symptom: The tengigethernetphy interface is getting BDI-H while the in-band message channel is disabled.
Workaround: None.
Symptom: A traffic loss of 30 to 45 seconds might 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 100 ms delay on Catalyst 6000 family using the set port debounce mod/port enable command sequence.
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 interfaces waveethernetphy command sometimes shows a high receiver power value when there is no input signal connected to the card.
Workaround: OIR the card.
Symptom: Could not get a wave power reading graph with CiscoView 2.0/2.1 for an uncalibrated 2.5-Gbps transponder module.
Workaround: Use a calibrated 2.5-Gbps 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.
Limitations and Restrictions
This section provides limitations and restrictions for Cisco ONS 15540 ESP 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 when used with certain client laser sources. Transmitters in some client GBIC and SFP transceiver units might send large overshoots in optical power with signal bit transitions, causing momentary overload conditions on the transponder client side receiver. The average transmitted power level from the GBIC does not violate the overload specification of the transponder client side receiver, so a power meter does not detect the overload.
The workaround is to attenuate the signal from the client equipment to a recommended level of -12 dBm when transmitting 2-Gbps Fibre Channel services.
•
–
–
–
–
Note
Related Documentation
Refer to the following documents for more information about the Cisco ONS 15540 ESP:
•
•
•
•
•
•
•
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 web sites 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 monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.
Registered Cisco.com users can order the Documentation CD-ROM (product number DOC-CONDOCCD=) 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
•
http://www.cisco.com/go/subscription
•
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 your comments by mail by using the response card 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:
Technical Assistance Center
The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisco TAC website and the Cisco TAC Escalation Center. The avenue 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
You can use the Cisco TAC website to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC 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/en/US/support/index.html
If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC website so that you can describe the situation in your own words 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 level of Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.
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/en/US/about/ac123/ac114/about_cisco_packet_magazine.html
•
http://business.cisco.com/prod/tree.taf%3fasset_id=44699&public_view=true&kbns=1.html
•
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, the Cisco Systems Verified logo, Cisco Unity, Follow Me Browsing, FormShare, iQ Net Readiness Scorecard, Networking Academy, and ScriptShare are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, The Fastest Way to Increase Your Internet Quotient, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, Fast Step, GigaStack, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, LightStream, MGX, MICA, the Networkers logo, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, SlideCast, SMARTnet, StrataView Plus, Stratm, SwitchProbe, TeleRouter, 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. (0303R)
Copyright © 2003 Cisco Systems, Inc. All rights reserved.
Posted: Sat Nov 6 11:29:47 PST 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
