Guest

Cisco ONS 15454 Series Multiservice Provisioning Platforms

Release Notes for Cisco ONS 15454 SDH, Release 8.6

  • Viewing Options

  • PDF (564.2 KB)
  • Feedback
Release Notes for Cisco ONS 15454 SDH Release 8.6

Table Of Contents

Release Notes for Cisco ONS 15454 SDH
Release 8.6

About Release 8.6

Contents

Changes to the Release Notes

Caveats

Alarms

CSCed28167— AU-LOP critical alarm raised when VC_LOW_PATH_TUNNEL only contains unidirectional circuits

CSCsu40460—External remote alarm relay is not set correctly

CSCef63240— LP TIM alarm displays its severity as NR instead of MJ in CTC

CSCsl88037— Improper removal alarm is not consistent on slot 24

CSCsq26495— CARLOSS alarm reported when VC circuit is created on port with copper SFP on CE-MR-10 card

CSCsq60390—Memory leak issue in alarm agent code

Common Control and Cross-Connect Cards

CSCec82148— Traffic hits occur on TCC2/TCC2P card removal

CTC

CSCsr89201—Unable to launch CTC with emsAccessState=secure after upgrade

CSCsr47355—Unable to cut new hybrid node into an existing hybrid MSTP ring

CSCsq73116—PPC does not work on secure mode node

CSCsv01621—It is not possible to enter in the WXC card panel

CSCsq88986—Filler card prevents enabling MSTP multishelf

Data I/O Cards

CSCsu02307—Unable to add members with SD-P alarm present on one member

CSCsw64346—UNEQ raised on CEMR-10 HW LCAS circuit after XC switch

CSCsu02236—Members of the VC11 LCAS circuits are in idle state

CSCsr67830—High traffic hit seen with larger HW-LCAS circuits with fibre pull

CSCsq55568—High traffic hit while upgrading from pre 9.00 load on CE-MR-10, CE-MR-6 cards

CSCsr06085—Error message on CPU switching packets greater than 1500 bytes in length

CSCsr41260—RPR convergence time is more than expected (50 ms) in ML-100X

CSCsm09512—Packet drop and VCG-DEG condition observed after hard reset of CE-MR-10 card

CSCsm99133— Packet loss on CE-MR-10 cards running more than 8.5 Gbps traffic during software upgrade

CSCsm78387— PDI-P alarm causes the Ethernet port to go down when members are deleted on open-ended HW-LCAS VCAT circuit

CSCso54993 —SF-V condition is not detected on VC12-nv circuits

CSCso55327—TCC switch on CE-MR-10 and ML-MR-10 cards causes a traffic hit of up to 180 ms

CSCso66424—LCAS VCG Member Rx side in Add State condition persists after hard reset of CE-MR-10 card

CSCso94644—LCAS VCG Member Rx side in Add State condition persists after hard reset of CE-MR-10 card or ML-MR-10 card

CSCsq24264—Traffic hit on CE-100T-8 cards during an upgrade from Release 8.5.0 to release 8.5.2 or 8.6

CSCsq02815—Negative values for gfpStatsRxCRCErrors and ifInPayloadCrcErrors parameters in CTC for CE-MR-10 cards

CSCsq05285—Traffic hit of 180 ms on CE-MR-10 cards with VCAT LCAS circuits during software upgrade

CSCsq12616—PDI-P alarm from the far-end NE causes Ethernet port to go down

CSCsq16464 —Traffic on nodes duplicates on ML-series cards

CSCsq20532 —Traffic hit of 25 ms occurs in a low-order LCAS circuit

CSCsq24903—First data frame sent on POS circuit is lost on CE-MR-10 card

CSCsq42702 —Traffic on HW-LCAS circuit with split-fibre routing on CE-100T-8 card in GFP mode goes down if the fibre carrying the first member is unplugged

CSCsq52786—Link Integrity does not work for HW-LCAS circuits

CSCsq77755—UNEQ alarmed HW-LCAS member will go into In-Group when CTX or XC card is reset

DWDM

CSCsu06528—GE_XP and 10GE_XP Trail Trace receive incorrect message

CSCsx49926—Egress WRR scheduling does not work for frames > ~1500 on GE_XP card

CSCsx55119—Ingress COS remarking not working for NNI ports on GE_XP card

CSCsw49064—GR3 protection is not triggered by SD or SF alarms on trunk ports

CSCsu49109—Y-cable does not switch for client syncloss on TXP-MR-10E card

CSCsr60270—Upgrade issues in GE_XP/10GE_XP cards

CSCsr22181—IPG change for Copper SFP

CSCsq99089—Traffic does not flow on the fast automatic protection switching (FAPS) circuit

CSCsq99680—Unwanted PM updates and alarms occur

CSCsq78030—Continuous squelch asserts or clears are observed on MXP-MR-2.5G card

CSCsq78337—Unable to provision ONS-SE-G2F-LX= (10-2273-02) on a TXP-MR-2.5G card for ISC3

CSCsg10008—Y-cable protection switch time higher than 50 ms in GE_XP and 10GE_XP cards

CSCsg22669—Traffic hit greater than 50 ms but less than 60 ms on MXP-2.5G-10E in Y-cable configuration with fibre cut

CSCsf04299—WTR time does not trigger switch back of protection

CSCse97200—Local and Express order-wire circuits do not work on ADM-10G cards

CSCsm82422—CARLOSS alarm not raised when power is turned off on MXP-MR-10DME cards

CSCsq46283—Packet loss on MXP-MR-10DME cards provisioned with 4G or 4G FICON

CSCei19148—Client momentarily enabled and emits light before squelching due to the trunk locked,disabled condition

CSCei87554—IfInErrors counter does not report performance parameters

CSCsb47323—Unexpected RFI condition raised with OTUK-BDI for MXP-MR-10DME-C and MXP-MR-10DME-L cards

CSCsb94736—MXP_MR_10DME card fails to detect the login message after fault condition

CSCsc36494—Manual Y-cable switches with squelching turned off in the MXP-MR-10G card causes Fibre Channel link with Brocade switches to go down

CSCsc60472—CTC is not able to discover TL1 OCHCC circuit provisioned over ITU-T line card

CSCsq33614 —Hard reset of MXP-MR-10DME and MXP-2.5G-10E cards raises IMPROPRVML alarm

CSCee45443 —FICON bridge in the MXP-MR-2.5G card transitions to SERV MODE

CSCef54670— SQUELCHED condition not raised when nonenhanced MXP card is in MS termination mode

CSCeh94567—OTUK-LOF and OTUK-IA alarms reported on both MXP-2.5G-10G trunk ports

CSCsl70268—Severity is not cleared when the raised alarm is cleared

CSCso82618— UT module does not report the wavelength error when the error is caused by a laser drift

CSCso92518—TIM alarm is not cleared on TXP-MR-10E and MXP-MR-10DME cards

CSCsq16317—GE_XP card in L1 mode reports FEC Uncorrected Word (UNC-WORD) condition

Electrical I/O Cards

CSCeg80233—Long traffic hits occur on E1-42 when using cross-connect FIT cards

CSCeg81428—Long traffic hit (117 ms) occurs on E1-42 after XC side-switch

CSCeg19255—DS3I VC3 traffic takes a hit greater than 60 ms during cross-connect card soft reset

CSCsu31027—J1 path trace does not work for E3 and DS3I from port 5 onward

Hardware

CSCei36415—Retrieving Gigabit Interface Converter (GBIC) inventory for FC_MR-4 returns nothing for CLEI code

CSCeb36749—In a Y-cable configuration, CARLOSS alarm is major and affects service even though traffic is fine

CSCed18803—Nonenhanced muxponder unit does not pass jitter tolerance test from trunk port to client port

Linear Multiplex Section Protection

CSCsr91312— Traffic hit of more than 2 seconds on upgrade when UPSR is active on protect

CSCee53579— Traffic hits occur in unprotected to Linear Multiplex Section protection topology upgrade in unidirectional routing

Maintenance and Administration

CSCse38590—Station reports "remote WTR" on a space even though the neighboring station is not advertising Wait to Restore (WTR) state

CSCsd44081—Series of crashes and reboots occur when policy-map includes approximately 200 class-map entries and policers

CSCse23518 —RPR SPAN-MISMATCH alarm not reported correctly

CSCse53133—RTRV-COND-VCn does not display path alarms on MS-SPR protect path

CSCsg10963—Connections remain in unlocked-disabled,failed after roll is canceled

CSCsg16500—ROLL-PEND condition seen for VC low-order path circuits on CTC conditions pane

CSCse91968—Automatic inservice to unlock transition on MS-SPR four-fibre protect does not function properly

CSCeh92201—IDRI circuit created with wrong span selection

CSCef53317—Traffic hit occurs during clock reference switch

CSCsg42366—Traffic outage occurs when FPGA upgrade is done with manual switch on Y-cable

MS-SP Ring Functionality

CSCdv53427— Protection vulnerabilities in two-ring, two-fibre MS-SP ring configuration

NCP

CSCdu82934—Failure of VC low-order path circuit creation

CSCsu10564—DCN-EXT: OTS PPC problem with OSPF enabled on LAN

Optical I/O Cards

CSCsr76682—Bit errors observed on STM64 XFP after both XC cards reboots

CSCsr13870— Traffic hit of around 18 ms on STM4_4 card when node is upgraded

CSCei26718—Different alarm behavior between one-way and two-way VC circuit creation on linear multiplex section protection

CSCin29274—Same static route on two interfaces fails

CSCsv54817—VC4-32c circuits do not work with STM64 XFP cards

CSCee17695—STM1-8 card fails to read MFG EEPROM and shows MEA in CTC

CSCsu50003—Traffic loss when concatenated unidirectional circuit is provisioned through 1 + 1 protected clients

TL1

CSCsc41650 —Node reboots during DS3XM card pre-provisioning

Resolved Caveats for Release 8.6

Alarms

CSCsv30867—Alarms do not clear after XC side-switch or switch-duplex of matrix cards

CSCsl34189—PDI-P is not detected by ADM-10G card

CSCsj96051—CE100 port transitions from Automatic In Service to unlocked when CARLOSS alarm is raised

Common Control Cards

CSCso58291—TCC2P card resets and goes into EQUIPMENT FAIL state

CSCsr41128—TCC card reboots when many sockets are created

CTC

CSCsi29266— CTC displays BIC_UNKNOWN

CSCsl68680— CTC indicates AIS insert on terminal loopback as default setting

CSCsk59570—CTC does not display warning message regarding unauthorized access

Data I/O Cards

CSCsl10070—Gigabit Ethernet interface with autonegotiation disabled is down after shut and no shut commands are issued

CSCsm21404—Packet loss with soft reset of CE-MR-6/CE-MR-10 card

CSCsq14370—ifspeed query results in incorrect value for circuit size

CSCsg92555— 20% CPU utilization without any configuration on ML100X-8 card

CSCsk04872— Multiple low-order VCATs do not transition to unlocked when created in TL1 or CTC

CSCsg35077—Cisco IOS crashes while processing malformed ISAKMP message

DWDM

CSCsl50180—ADM-10G card reboots after creating 1S-2D circuits

CSCsm73009—HW FAIL alarm is raised when optical module is not recognized

CSCso92457—4G-FC switching on MXP-MR-10DME card takes longer time

CSCsq65534—CRC error on TX interface

CSCsr41096—Traffic is affected on 4G-FC switching on MXP-MR-10DME

CSCsr75681—Packet drop for high throughput on MXP-MR-10DME card

CSCsm82513—Support of far-end laser control

CSCsq16653—Far-end port will be in squelched state on GE_XP card until the card is reset

CSCsu26568—Traffic loss on 1G port of the GE_XP card

CSCsd80965—Traffic hit on TXP-MR-2.5G cards while upgrading the nodes from 5.0 or 6.0 to 7.xx versions

CSCsr91742—Maximum bandwidth of data communication channel (DCC) in subshelf is less than the bandwidth in the node controller

Linear Multiplex Section Protection

CSCsv30593—AIS-V alarm does not clear in VC11 cross-connect circuits

CSCsw86999 —AIS-V alarm does not clear for VC high-order path that does not have circuit created on VT-1

Maintenance and Administration

CSCsk42322—Pointer justification counter increments only for port 1 on MRC-12 card

CSCsr50786—Optical threshold defaults reset when software is upgraded

CSCsv13893—Admin state change from unlocked,enabled to locked,disabled fails

CSCsk84133—Unable to archive audit log

CSCsv14375— Shared secret key greater than 16 characters corrupts after an upgrade

NCP

CSCsx37297—FTP port issue for TCP Connect Scan

Optical I/O Cards

CSCsr99947—Unable to retrieve VC high-order path PM values and thresholds on ports 2, 3, and 4

CSCsm44367—False line PM values reported on facility loopback for STM4-1 card

TL1

CSCsw92329—TL1 does not initialize PM counts on all ports of MRC card

New Features and Functionality

Related Documentation

Release-Specific Documents

Platform-Specific Documents

Obtaining Optical Networking Information

Where to Find Safety and Warning Information

Cisco Optical Networking Product Documentation CD-ROM

Obtaining Documentation and Submitting a Service Request


Release Notes for Cisco ONS 15454 SDH
Release 8.6


OL-19081-01

March 2009

Release notes address closed (maintenance) issues, caveats, and new features for the Cisco ONS 15454 SDH. For detailed information regarding features, capabilities, hardware, and software introduced with this release, refer to the Release 8.5.x version of the Cisco ONS 15454 DWDM Installation and Operations Guide; and the Release 8.5.x version of the Cisco ONS 15454 SDH Procedure Guide; Release 8.5.x version of the Cisco ONS 15454 SDH Reference Manual; Release 8.5.x version of the Cisco ONS 15454 SDH Troubleshooting Guide; and Release 8.5.x version of the Cisco ONS 15454 SDH TL1 Command Guide. For the most current version of the Release Notes for Cisco ONS 15454 SDH Release 8.6, see the following URL:

http://www.cisco.com/en/US/products/hw/optical/ps2006/prod_release_notes_list.html

Cisco also provides Bug Toolkit, a web resource for tracking defects. To access Bug Toolkit, see the following URL:

http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs

About Release 8.6

Cisco ONS 15454 SDH Release 8.6 does not include any new features.

Cisco ONS 15454 SDH Release 8.6 is based on Cisco ONS 15454 SDH Release 8.5.2 and Cisco ONS 15454 SDH Release 8.5.3. The Release Notes for Cisco ONS 15454 SDH Release 8.6 contain closed (maintenance) issues and caveats found in Cisco ONS 15454 SDH Release 8.5.2 and 8.5.3. Some bug fixes made in Cisco ONS 15454 SDH Release 8.5.2 are not available in Cisco ONS 15454 SDH Release 8.5.3 and vice versa. For detailed information on bugs fixed refer to the respective sections in this document.

Contents

Changes to the Release Notes

Caveats

Resolved Caveats for Release 8.6

New Features and Functionality

Related Documentation

Obtaining Optical Networking Information

Obtaining Documentation and Submitting a Service Request

Changes to the Release Notes

This section documents supplemental information that has been added to the Release Notes for Cisco ONS 15454 SDH Release 8.6 since the production of the Cisco ONS 15454 SDH System Software CD for Release 8.6.

Added CSCsg42366—Traffic outage occurs when FPGA upgrade is done with manual switch on Y-cable, under Maintenance and Administration sub-section of the Caveats section.

Caveats

Review the notes listed below before deploying Cisco ONS 15454. Caveats with tracking numbers are known system limitations that are scheduled to be addressed in a subsequent release. Caveats without tracking numbers are provided to point out procedural or situational considerations when deploying the product.

Alarms

This section documents caveats for Alarms in Release 8.6.

CSCed28167— AU-LOP critical alarm raised when VC_LOW_PATH_TUNNEL only contains unidirectional circuits

When a VC_LOW_PATH_TUNNEL only contains unidirectional circuits, an AU-LOP critical alarm is raised. This alarm can occur when a bidirectional tunnel goes through at least three nodes, and the AU-LOP alarm is shown on the intermediate node on the direction not used.

Tunnels are bidirectional. If a tunnel does not have traffic in both directions, it will raise an alarm. The alarm will be cleared when a bidirectional circuit is added to the tunnel. This issue will not be resolved.

CSCsu40460—External remote alarm relay is not set correctly

The External Alarm Relay (ERA) (A1/B1 VIS/AUD on the backplane) on a node created on the Cisco ONS 15454 platform indicates incorrectly set remote alarms when remote nodes are raised or alarms are cleared. This issue occurs under the following conditions:

1. The node is stable with no MN/MJ/CR alarms on the entire network on a Cisco ONS 15454 platform.

2. Another node on the network raises an MN/MJ/CR alarm, but it does not update the REM ALARM VIS/AUD contact pins on the backplane.

3. The issue occurs when the remote nodes clear their alarms also. (This issue has been observed since Release 7.0).

The workaround is to create and clear an alarm or modify the severity of the already raised alarm (if raised) on the node using the alarm profile.

This issue will be resolved in a future release.

CSCef63240— LP TIM alarm displays its severity as NR instead of MJ in CTC

Rarely, an LP TIM alarm displays its severity as NR instead of MJ in Cisco Transport Controller (CTC). This situation can occur when a VC3 circuit is created on port 5 and I/O has detected a VC4 PLM alarm. This issue will not be resolved.

CSCsl88037— Improper removal alarm is not consistent on slot 24

The improper removal alarm (IMPROPRMVL) is raised on slot 24 upon activation even when a card is not present in slot 24 before activation. The workaround is to connect slots 23 and 24 to power modules.

CSCsq26495— CARLOSS alarm reported when VC circuit is created on port with copper SFP on CE-MR-10 card

On a CE-MR-10 card, a CARLOSS alarm is reported on the near end when a VC-12 circuit is created between a port having a copper SFP at the near end and a fibre SFP at the far end. This issue is seen under the following conditions:

A VC-12 VCAT circuit is created between two ports on a CE-MR-10 card.

Loopback (Tx to Rx) is applied at the far end using a fibre SFP.

The near end reports a CARLOSS alarm and the far end reports a TPTFAIL alarm.

The state of the port with the copper SFP changes continuously.

This issue is seen only for a VC-12 circuit and if loopback is applied to the far end.

No workaround is available for this issue. This issue will be resolved in a future release.

CSCsq60390—Memory leak issue in alarm agent code

E1-42 cards leak memory when they receive an alarm resoak request. This issue causes a traffic hit, but the E1-42 card may eventually set in Release 6.2. It is much less likely in later releases for E1-42 cards to reset (that is, the issue may not be seen at all.).

In Release 6.2, for the following setups, electrical cards get continuous resoak messages. While processing these messages, E1-42 cards leak memory due to a bug.

There are two conditions when this issue is seen. Respective workarounds for each conditions are provided below.

Condition 1:

1. Create 1+1 OCN protection between two STM cards with no traffic on the ports (that is, these ports have LOS or LOF alarms raised).

2. Create VC-12 circuits on any E1-42 card on the node.

The workaround for this condition is as follows:

1. Make sure no service-affecting alarms are raised on optical ports that are in 1+1 protection.

2. Delete the 1+1 protection if it is not being used.

Before deleting the protection, make sure that you have switched the traffic that uses this entire 1+1 setup.

Condition 2:

1. Create one or more 1+1 OCN protections between two STM cards, and at least one with locked, disabled.

2. Create one or more VC-12 circuits between the 1+1 OCN protection and an E1-42 card on the node.

The two workarounds for this condition are as follows:

1. Put 1+1 OCN protection into unlocked.

2. Delete the VC-12 circuits between the 1+1 OCN protection and the E1-42 card on the node.

This issue will be resolved in a future release.

Common Control and Cross-Connect Cards

This section documents caveats for Common Control and Cross-Connect Cards in Release 8.6.

CSCec82148— Traffic hits occur on TCC2/TCC2P card removal

Rarely, traffic hits can occur when TCC2/TCC2P cards are removed. To avoid this issue, remove the card quickly. To recover from this issue, soft reset the TCC2/TCC2P card. This issue will not be resolved.

CTC

This section documents CTC caveats in Release 8.6.

CSCsr89201—Unable to launch CTC with emsAccessState=secure after upgrade

After a release upgrade, CTC does not launch on certain `custom packages.' This issue occurs only on the custom package and while upgrading with the EMS access state set to secure.

The workaround is to use TL1 to change the EMS access state to secure, or delete the database and reboot the node. This issue will be resolved in a future release.

CSCsr47355—Unable to cut new hybrid node into an existing hybrid MSTP ring

When cutting a new node into an existing hybrid ring, the user is unable to run the Update Circuits With New Node Wizard from CTC, and receives the following error message:

EID-2034

Network Circuits Could Not Be Added: cerent.cms.ncp.missingLinks: No Reverse Link!

This issue occurs under the following condition:

The node being cut into the ring must be a hybrid (MSTP/MSPP) shelf with OSC-CSMs created and unlocked. The problem appears only after OSC connectivity has been established between the new node and the adjacent nodes.

The workaround for this issue is to either manually build cross-connects through a new node using CTC/TL1, or disable OSC on the new node and the adjacent nodes and then run the Update Circuits With New Node Wizard in CTC.

CSCsq73116—PPC does not work on secure mode node

PPC does not work on a secure mode node under the following condition:

Create a PPC that terminates on a secure mode node. At this point, a new "unknown" node appears and the PPC is not shown on the network map.

No workaround is available for this issue. This issue will be resolved in a future release.

CSCsv01621—It is not possible to enter in the WXC card panel

The user cannot open the card configuration panel for any WXC inserted or pre-provisioned in the system. This issue occurs under the following conditions:

1. Configure a multidegree node with WXC.

2. Some WXC cards are inserted in the system but are then "deleted."

The workaround is to physically remove the "deleted" WXC cards from the slots.

This issue will be resolved in a future release.

CSCsq88986—Filler card prevents enabling MSTP multishelf

Cannot enable MSTP multishelf under the following condition:

At least one Filler card plugged in the shelf

The workaround is to perform the following steps in the specified order.

1. Unplug all the Filler cards.

2. Enable multishelf. TCCs will reload.

3. After TCCs reload completed, plug all the required Filler cards.

This issue will be resolved in a future release.

Data I/O Cards

This section documents caveats for Data I/O Cards in Release 8.6.

CSCsu02307—Unable to add members with SD-P alarm present on one member

The ADD condition persists when adding more members to the LCAS circuit signal degrade-path (SD-P) is present on a member. This issue occurs under the following conditions:

1. Create an VC3-2v VCAT, HW-LCAS between a Cisco ONS 15310-MA and Cisco ONS 15454 node.

2. Put the test set in through mode (Agilent VCAT test set).

3. Inject SD-P or SF-P toward the Cisco ONS 15310-MA node. As expected, members go into outOfGroup.

4. Add some more members (for example, 5) on the span that does not have the test set. As expected, members should be added; however, members are not added to the VCAT group, causing the ADD condition to persist.

5. Add more members when SD-P is present on one of the members and SD-P is injected through the Agilent test set.


Note This issue is seen only with the Agilent GFP test set.


The workaround is to use the OTN test set or variable attenautor to inject SD-P.

This issue will be resolved in a future release.

CSCsw64346—UNEQ raised on CEMR-10 HW LCAS circuit after XC switch

AIS-P conditions change to UNEQ-P on a trunk card that corresponds to members of a HW-LCAS circuit after the XC is switched under the following conditions:

1. Create the circuit with POS ports in unlocked state. Later, the POS port on one end is placed in locked,disabled state.

2. Perform the XC side-switch is performed.

The workaround is to place the locked, disabled port in unlocked state.

CSCsu02236—Members of the VC11 LCAS circuits are in idle state

On an ML-MR-10 card, injecting a signal degrade (SD) or signal fail-V (SF-V) on one member and switching the cross-connect (XC) main causes a few members of the VC11 LCAS circuits to become stuck in the Idle state. This issue occurs under the following conditions:

1. Configure two ML-MR-10 cards, that is, ML-MR-10 card A and ML-MR-10 card B.

2. Create a VC11-64V circuit between ML-MR-10 card A and ML-MR-10 card B.

3. Inject an SD/SF-P on one member and observe that traffic is reduced on the affected member.

4. Switch the XC main and observe the Stuck Idle state (with sequence number 63) on a few members.

The workaround is to recover from the Stuck Idle condition, move the affected members outOfGroup (OOG), and then back to inGroup (IG).

CSCsr67830—High traffic hit seen with larger HW-LCAS circuits with fibre pull

A high traffic hit is seen on fibre pull for a HW-LCAS, split-fibre circuit on CE-MR-10, CE-MR-6, and ML-MR-10 cards under the following condition:

For larger-member HW-LCAS, split-fibre circuits on CE-MR-10, CE-MR-6, and ML-MR-10 cards, a high traffic hit is seen when pulling a fibre on one span.

No workaround is available for this issue. This issue will be resolved in a future release.

CSCsq55568—High traffic hit while upgrading from pre 9.00 load on CE-MR-10, CE-MR-6 cards

A high traffic hit occurs while upgrading from pre 9.00 load on CE-MR-10 and CE-MR-6 cards. No workaround is available for this issue. This issue will be resolved in a future release.

CSCsr06085—Error message on CPU switching packets greater than 1500 bytes in length

An error message on CPU switching packets greater than 1500 bytes in length occurs under the following conditions:

When an IP multicast packet of size > 1500 bytes is received on a BVI interface, an error message is displayed on the console/vty and packets are dropped.

No workaround is available for this issue. This issue will be resolved in a future release.

CSCsr41260—RPR convergence time is more than expected (50 ms) in ML-100X

RPR convergence time is more than expected (50 ms) in ML-100X cards and is noticed under the following condition:

RX fibre cut occurs on trunk of RPR-IEEE 802.17 ring.

No workaround is available for this issue. This issue will be resolved in a future release.

CSCsm09512—Packet drop and VCG-DEG condition observed after hard reset of CE-MR-10 card

The VC11-64v or VC11-63v circuit moves to VCG degraded state following the hard reset of a CE-MR-10 card. The number of members that are not available for use is approximately 6 to 10. The following workarounds apply:

To recover from the VCG-DEG condition, transition members to locked, outOfGroup state, delete them in locked, outOfGroup state, and then re-add them.

Disabling and reenabling associated ports recovers from this condition. This workaround causes a one-time traffic hit.

This issue will be resolved in a future release.

CSCsm99133— Packet loss on CE-MR-10 cards running more than 8.5 Gbps traffic during software upgrade

Upgrading software on a Cisco ONS 15454 from Release 8.5.0 or 8.5.1 to a later version causes packet loss on CE-MR-10 cards running more than 8.5 Gbps of traffic. The workaround is to do a hard reset on the CE-MR-10 card, which may result in a traffic outage for a few minutes. This issue will not be resolved.

CSCsm78387— PDI-P alarm causes the Ethernet port to go down when members are deleted on open-ended HW-LCAS VCAT circuit

A path payload defect indication (PDI-P) alarm is raised and the Ethernet port to goes down when members are deleted in an open-ended HW-LCAS VCAT circuit under the following conditions:

A VC-12-63v open-ended HW-LCAS circuit exists between two network elements (NEs).

All members on the CE-MR-10 card are placed in the locked,outOfGroup state and the last 45 members are deleted.

The remaining 18 members on the CE-MR-10 card are placed in unlocked state.

These conditions result in an unbalanced virtual concatenation group (VCG). The traffic is lost and a PDI-P alarm is raised on the card where members were deleted.

The workaround is to place members in the outOfGroup state on both ends. When members are being placed in the inGroup state, place them in the inGroup state on both ends of the circuit. This issue will be resolved in a future release.

CSCso54993 —SF-V condition is not detected on VC12-nv circuits

The SF-V condition is not detected on VC12-nv circuits provisioned with SFBER = 1e-3, SDBER = 1e-5 on CE-MR-10 and ML-MR-10 cards. No workaround is available for this issue. This issue will be resolved in a future release.

CSCso55327—TCC switch on CE-MR-10 and ML-MR-10 cards causes a traffic hit of up to 180 ms

A reset of a TCC switch on CE-MR-10 and ML-MR-10 cards causes a traffic hit of up to 180 ms on all circuits with software earlier than Release 9.0. No workaround is available for this issue. This issue will be resolved in a future release.

CSCso66424—LCAS VCG Member Rx side in Add State condition persists after hard reset of CE-MR-10 card

The LCAS VCG Member on the Rx side continues to be in a Add State condition even after a hard reset of a CE-MR-10 card carrying a VC12 HW-LCAS circuit with a high member count. The workaround is to place all the affected circuit members in the locked,outOfGroup state, and then put them back in the unlocked state. This issue will be resolved in a future release.

CSCso94644—LCAS VCG Member Rx side in Add State condition persists after hard reset of CE-MR-10 card or ML-MR-10 card

The LCAS VCG Member on the Rx side continues to be in the Add State condition even after a hard reset of a CE-MR-10 card or an ML-MR-10 card carrying a HW-LCAS circuit with loopback on split fibre routing. The workaround is to place all the affected circuit members in the locked,outOfGroup state. After all the members have been placed in locked,outOfGroup state, place them back in the unlocked state. This issue will be resolved in a future release.

CSCsq24264—Traffic hit on CE-100T-8 cards during an upgrade from Release 8.5.0 to release 8.5.2 or 8.6

An upgrade on Cisco ONS 15454 from Release 8.5.0 to Release 8.5.2 or 8.6 followed by a power cycle of the node causes a traffic hit on CE-100T-8 cards. The workaround is to change the Admin state of the CE-100T-8 card to the Maintenance state, followed by a hard reset. This issue will be resolved in a future release.

CSCsq02815—Negative values for gfpStatsRxCRCErrors and ifInPayloadCrcErrors parameters in CTC for CE-MR-10 cards

The gfpStatsRxCRCErrors and ifInPayloadCrcErrors performance monitoring parameters in CTC for CE-MR-10 cards can contain negative values. The workaround is to either refresh the Performance > Statistics pane by clicking the Refresh button or by clearing the PM parameters by clicking the Clear button. This issue may be resolved in a future release.

CSCsq05285—Traffic hit of 180 ms on CE-MR-10 cards with VCAT LCAS circuits during software upgrade

Upgrading software on a Cisco ONS 15454 from Release 8.5.0 or 8.5.1 to Release 8.5.2 or 8.6 sometimes causes a traffic hit of 180 ms on CE-MR-10 cards with VCAT LCAS circuits. No workaround is available for this issue. This issue will be resolved in a future release.

CSCsq12616—PDI-P alarm from the far-end NE causes Ethernet port to go down

A path payload defect indication (PDI-P) alarm is raised from the far-end NE, causing the Ethernet port to go down. This situation happens when all the LCAS members on the near-end NE are changed to locked,outOfGroup state while all the members on the far-end NE are still unlocked. This problem occurs while provisioning an open- ended VCAT circuit using CTC or TL1 and modifying the near- end NE of the LCAS circuit, without making modifications to the far- end NE.

The workaround is to perform provisioning steps on both ends, in sequence, rather than completing the near end, and then provisioning the far end. For example, to remove members of a VCG, perform the following steps:

1. On the near-end NE, move members to be deleted to the locked,outOfGroup state.

2. On the far-end NE, move members to be deleted to the locked,outOfGroup state.

3. Delete members on the near-end NE.

4. Delete members on the far-end NE.

5. Put other members in the unlocked state on the near-end NE, if required.

6. Put other members in the unlocked state on the far-end NE, if required.

This issue will be resolved in a future release.

CSCsq16464 —Traffic on nodes duplicates on ML-series cards

On ML-series cards, if a priority-multicast is configured and a wrap occurs on the shared packet ring (SPR), traffic on some nodes will be duplicated, which can result in sequencing issues in the multicast stream. Multicast video may experience deterioration in clarity. The workaround is to configure the video reception device so that it does not act on the duplicate stream, or if no congestion is present on the ring, the priority-multicast configuration can be removed. This issue will be resolved in a future release.

CSCsq20532 —Traffic hit of 25 ms occurs in a low-order LCAS circuit

A traffic hit of about 25 ms may occur in a low-order LCAS circuit if members in the locked,outofGroup state are deleted in CE-MR-10, CE-MR-6, or ML-MR-10 cards. No workaround is available for this issue. This issue will be resolved in a future release.

CSCsq24903—First data frame sent on POS circuit is lost on CE-MR-10 card

On CE-MR-10 cards, the first data frame that is sent on a POS circuit is lost under the following conditions:

For a new provisioned POS circuit

If the data frame is large.

No workaround is available for this issue. This issue will not be resolved.

CSCsq42702 —Traffic on HW-LCAS circuit with split-fibre routing on CE-100T-8 card in GFP mode goes down if the fibre carrying the first member is unplugged

The HW-LCAS circuit with split-fibre routing on a CE-100T-8 card in the GFP framing mode goes down and the GFP-LFD alarm is raised if the fibre carrying the first member is unplugged, which causes the circuit to not carry any traffic. If the port on which the circuit is provisioned is in the HDLC framing mode, members of the working span do not carry traffic when the fibre carrying the first member is unplugged. The HW-LCAS circuit does not go down and no alarm is raised corresponding to those working path members.

This issue is seen in the following conditions:

The fibre on the path that is carrying the first member is cut.

The Tx and Rx fibre is unplugged from the span.

The workaround is to place members of the span in the locked,outOfGroup state before the fibre is unplugged. This issue will be resolved in a future release.

CSCsq52786—Link Integrity does not work for HW-LCAS circuits

The far-end port does not go down when an AIS-P, AIS-V, or LOP alarm is injected into the HW-LCAS circuit on CE-MR-10 and CE-MR-6 cards. A TPTFAIL alarm is raised on the injected port and the port goes down. No workaround is available for this issue. This issue will be resolved in a future release.

CSCsq77755—UNEQ alarmed HW-LCAS member will go into In-Group when CTX or XC card is reset

Resetting the CTX/XC card while a HW-LCAS member has the UNEQ alarm raised causes the HW-LCAS member to go into In-Group state. This issue occurs under the following conditions:

1. Create a HW-LCAS circuit on a CE-MR-10/CE-MR-6/ML-MR-10 card.

2. Inject UNEQ on a HW-LCS member. Because of this defect, the member will be taken outOfGroup.

3. Reset the CTX/XC card. HW-LCAS members with the UNEQ alarm raised will go into inGroup.

No workaround is available for this issue. This issue will be resolved in a future release.

DWDM

This section documents caveats for DWDM in Release 8.6.

CSCsu06528—GE_XP and 10GE_XP Trail Trace receive incorrect message

An incorrect "received string" message is displayed on the CTC card TTI panel continually when TTI is enabled even though the line card receives the correct string and correct alarm behavior. This issue occurs under the following conditions:

1. Set up a node with two GE_XP cards.

2. Connect card A on port 21 to card B on the same port, and card A on port 22 to card B on port 22 card.

3. Enable TTI on both trunks. The strings are received correctly.

4. Disable TTI on port 22. Port 21 reports an incorrect received string.

No workaround is available for this issue. This issue will be resolved in a future release.

CSCsx49926—Egress WRR scheduling does not work for frames > ~1500 on GE_XP card

Egress WRR scheduling does not work for frames more than approximately 1500 on GE_XP card. No workaround is available for this issue. This issue will be resolved in a future release.

CSCsx55119—Ingress COS remarking not working for NNI ports on GE_XP card

Ingress COS remarking does not work for NNI ports on GE_XP cards. No workaround is available for this issue. This issue will be resolved in a future release.

CSCsw49064—GR3 protection is not triggered by SD or SF alarms on trunk ports

GR3 protection is not triggered by SD/SF alarms on trunk ports under the following conditions:

1. Configure a GR3 protection on a ring of muxponder cards.

2. Generate an SF or an SD on a trunk. The protection is not triggered.

No workaround is available for this issue. This issue will be resolved in a future release.

CSCsu49109—Y-cable does not switch for client syncloss on TXP-MR-10E card

On TXP_MR_10E cards, the SYNCLOSS alarm on the client port does not cause the Y- cable switch under the following conditions:

1. Install a Y-cable with G709 on a 10GE/10GFC card.

2. Inject a SYNCLOSS alarm in the client receiving fibre on the far-end working card. The near-end protection does not perform a switch to protection.

No workaround is available for this issue. This issue will be resolved in a future release.

CSCsr60270—Upgrade issues in GE_XP/10GE_XP cards

The following issues are noticed:

Electrical SFP

If a copper SFP has a link flap (cable disconnect or autoneg restart) the link will come up but traffic will not flow.

VLAN range issue

After an upgrade, if the user tries to add or configure a new VLAN range, it does not work. Also, previously configured VLAN ranges will not work

Selective configuration

When there is a sequence of add and delete selective operations followed by a reset, new selective operations might not work after reset.

Metering on port1

If a VLAN range is configured, after an upgrade, metering on port 1 will not work anymore. Traffic will flow, but metering is not applied.

These issues occur when the software is upgraded from Release 8.0 to 8.5.

The workaround for each issue is as follows:

Electrical SFP issue:unlocked>locked>unlocked.

VLAN range issue: Cold boot card.

Selective configuration: Cold boot card.

Metering on port1: Remove VLAN range entry, change metering parameters on port 1, and reapply metering.

This issue will be resolved in a future release.

CSCsr22181—IPG change for Copper SFP

Upgrading the software from a software release with CRC errors issue for traffic on a copper PPM does not automatically fix the issue. This issue occurs under the following conditions:

In a release that includes a copper-card pair, most of the packets are dropped due to CRC errors (even in normal working condition).

Upgrade the software to a new release to fix this issue for new copper PPMs.

Copper PPMs with CRC issues that were already installed before the software upgrade will again drop packets.

The workaround is to change the port state to locked and unlocked. This issue will be resolved in a future release.

CSCsq99089—Traffic does not flow on the fast automatic protection switching (FAPS) circuit

Traffic does not flow on the fast automatic protection switching (FAPS) circuit when the master node is powered up after being powered down. This issue occurs under the following conditions:

1. Enable GR3/FAPS.

2. Remove the fibre from the working trunk (trunk_1). The card switches to the protected trunk (trunk_2) and traffic is up and running.

3. Power down the master node.

4. Power up the master node.

5. The master node is up and running, but traffic does not flow.

No workaround is available for this issue. This issue will be resolved in a future release.

CSCsq99680—Unwanted PM updates and alarms occur

While an LOS (or TRAIL-SIGNAL-FAIL) alarm is present, the following unwanted PM updates and alarms occur:

FEC-PM continues increment.

UNC-WORD alarm is raised.

This issue occurs under the following conditions:

1. Enable a 10GE-XP trunk port, configured with FEC on and G709 on.

2. The trunk port reports an LOS alarm due to a valid reason.

No workaround is available for this issue. This issue will be resolved in a future release.

CSCsq78030—Continuous squelch asserts or clears are observed on MXP-MR-2.5G card

Continuous squelch asserts or clears are observed on an MXP-MR-2.5G card. This issue occurs under the following condition:

SYNCLOSS alarm is present on the peer card.

No workaround is available for this issue. This issue will be resolved in a future release.

CSCsq78337—Unable to provision ONS-SE-G2F-LX= (10-2273-02) on a TXP-MR-2.5G card for ISC3

ONS-SE-G2F-LX= (10-2273-02) on a TXP-MR-2.5G card for ISC3 cannot be provisioned while using the Release 8.5.x software version.

The workaround for this issue is to either:

Use 10-1832-03 --> 15454-SFP-GE+-LX= on the TXP-MR-2.5G card.

Use 10-2273-01 --> ONS-SE-G2F-LX= on the ADM-10G card.

This issue will be resolved in a future release.

CSCsg10008—Y-cable protection switch time higher than 50 ms in GE_XP and 10GE_XP cards

The Y-cable protection switch time is higher than 50 ms in GE_XP and 10GE_XP cards under the following conditions:

RX fibres extracted from client pluggable port module (PPM).

The Trunk PPM status is locked,disabled.

Loss of Signal (LoS), both LOS-P and SIGLOSS, when extracting the RX fibre on Trunk PPM port.

User command (for example, FORCE) is issued.

No workaround is available for this issue.

CSCsg22669—Traffic hit greater than 50 ms but less than 60 ms on MXP-2.5G-10E in Y-cable configuration with fibre cut

When a fibre is cut on MXP-2.5G-10E cards in Y-cable configurations, a traffic hit of greater than 50 ms but less than 60 ms occurs. This issue will be resolved in a future release.

CSCsf04299—WTR time does not trigger switch back of protection

When triggering the switch of optimized 1+1 protection and the failure is cleared, the WTR condition is raised, but after the WTR time expires the switch back of protection is not triggered. The workaround is to manually force back the protection. This issue will be resolved in a future release.

CSCse97200—Local and Express order-wire circuits do not work on ADM-10G cards

On ADM-10G cards, attempts to preprovision local and express order-wire circuits on trunk ports are not successful. E1/E2 order-wire is not supported. This issue will be resolved in a future release.

CSCsm82422—CARLOSS alarm not raised when power is turned off on MXP-MR-10DME cards

On MXP-MR-10DME cards, the CARLOSS alarm is not raised when the power is turned off on the copper SFP due to squelching of that port. No workaround is available for this issue. This issue will not be resolved.

CSCsq46283—Packet loss on MXP-MR-10DME cards provisioned with 4G or 4G FICON

Continuous packet loss is seen for 10 to 15 minutes on MXP-MR-10DME cards provisioned with 4G or 4G FICON and the port is moved from unlocked state to locked,maintenance state, and then back to unlocked state. The workaround is to move the port to locked,disabled state and then to unlocked state. This issue will be resolved in a future release.

CSCei19148—Client momentarily enabled and emits light before squelching due to the trunk locked,disabled condition

When a port is placed in unlocked state while the conditions necessary to squelch the port are present (for example, when the trunk port on a DWDM card is in locked,disabled state and a client port is placed in unlocked state) the client will momentarily enable, emitting light, before squelching due to the trunk locked,disabled condition. The pulse is approximately 500 ms. This issue will not be resolved.

CSCei87554—IfInErrors counter does not report performance parameters

When using a 1GE payload over the TXP-MR-2.5G card, the IfInErrors counter does not report oversized, undersized, or CRC errored frames. The counter reports frame coding only. This issue will not be resolved.

CSCsb47323—Unexpected RFI condition raised with OTUK-BDI for MXP-MR-10DME-C and MXP-MR-10DME-L cards

For MXP-MR-10DME-C and MXP-MR-10DME-L cards, an unexpected RFI condition might be raised along with an OTUK-BDI. When an LOS downstream occurs, the node receives OTUK-BDI. Because of the placement of dual OTN and SDH wrappers, the node can also receive an RFI. This issue will not be resolved.

CSCsb94736—MXP_MR_10DME card fails to detect the login message after fault condition

After a fault condition (trunk LOS or Y-cable switch) an MXP_MR_10DME card might fail to detect the login message and traffic might not start for some minutes (after multiple login trials). This situation can occur in an N-F configuration with the Cisco MDS switch and MXP_MR_10DME distance extension on, where test equipment traffic is set to 2G Fibre Channel (FC) full-bandwidth occupancy and started. The workaround is to stop traffic or keep bandwidth occupancy below 80% during the login phase. This issue will not be resolved.

CSCsc36494—Manual Y-cable switches with squelching turned off in the MXP-MR-10G card causes Fibre Channel link with Brocade switches to go down

Manual Y-cable switches with squelching turned off in the MXP-MR-10G card can cause a Fibre Channel link with Brocade switches to go down. SIGLOSS and GFP-CSF alarms are seen in CTC. Cisco recommends that squelching be on when interworking with Brocade switches. If for some reason, squelching must be off with Brocade switches, Cisco recommends using a FORCE command to perform Y-cable switches. This issue may not be resolved.

CSCsc60472—CTC is not able to discover TL1 OCHCC circuit provisioned over ITU-T line card

CTC is not able to discover a TL1 OCHCC circuit provisioned over an ITU-T line card (ITU-T OC48/STM16 and ITU-T OC192/STM64). This issue can occur when, using the TL1 client interface, you create the OCHNC layer that will be used by the OCHCC circuit, then create the OCHCC connections that involve the ITU-T line cards. The result is an OCHNC and two OCHCC partial circuits, instead of an OCHNC and a single OCHCC complete circuit. This issue will not be resolved.

CSCsq33614 —Hard reset of MXP-MR-10DME and MXP-2.5G-10E cards raises IMPROPRVML alarm

A hard reset on MXP-MR-10DME and MXP-2.5G-10E cards sometimes causes the improper removal alarm to be raised on some ports. No workaround is available for this issue. This issue will be resolved in a future release.

CSCee45443 —FICON bridge in the MXP-MR-2.5G card transitions to SERV MODE

The FICON bridge in the MXP-MR-2.5G card transitions to SERV MODE when the FICON bridge does not receive the expected number of idle frames between the data packets. The workaround is to not use the MXP-MR-2.5G card with the FICON bridge. This issue will not be resolved.

CSCef54670— SQUELCHED condition not raised when nonenhanced MXP card is in MS termination mode

The SQUELCHED condition is not raised when a nonenhanced MXP card is in MS termination mode. LOS and LOS-P alarms are reported on MXP-1 port 1 (client). The SQUELCHED condition is not reported on MXP-1 port 1 (client) because AIS is sent out of the client port instead. This behavior is intentional.

CSCeh94567—OTUK-LOF and OTUK-IA alarms reported on both MXP-2.5G-10G trunk ports

Setting a terminal loopback on an MXP-2.5G-10G trunk port causes OTUK-LOF and OTUK-IA alarms to be reported on both MXP-2.5G-10G trunk ports. This issue will not be resolved.

CSCsl70268—Severity is not cleared when the raised alarm is cleared

When an alarm raised on a port is cleared, the severity is not cleared. The workaround is to close and then reopen CTC Functional View. This issue will be resolved in a future release.

CSCso82618— UT module does not report the wavelength error when the error is caused by a laser drift

On TXP-MR-10E-UT2 cards, the UT module does not report the wavelength error when the error is caused by a laser drift. The alarm is reported only during the tuning process if the laser does not lock to the provisioned channel. No workaround is available for this issue. The issue will be resolved in a future release.

CSCso92518—TIM alarm is not cleared on TXP-MR-10E and MXP-MR-10DME cards

On TXP-MR-10E and MXP-MR-10DME cards, configuring a SONET section trace on the trunk port when G.709 is ON causes a stuck TIM alarm. This problem does not occur on a G.709 OFF trunk port. The workaround is to use OTUk/ODUk TTI. This issue will be resolved in a future release.

CSCsq16317—GE_XP card in L1 mode reports FEC Uncorrected Word (UNC-WORD) condition

The GE-XP card in L1 mode reports the FEC Uncorrected Word (UNC-WORD) condition when G.709 is enabled and FEC is disabled on both ends of the GE-XP trunk port. The workaround is to set the FEC to standard. This issue will be resolved in a future release.

Electrical I/O Cards

This section documents caveats for Electrical Cards in Release 8.6.

CSCeg80233—Long traffic hits occur on E1-42 when using cross-connect FIT cards

Long traffic hits can occur on E1-42 cards when using cross-connect FIT cards. These hits can occur when, on the FIT card, you toggle the 155-MHz clock going to the E1-42 cards to the OFF position. This issue cannot be resolved.

CSCeg81428—Long traffic hit (117 ms) occurs on E1-42 after XC side-switch

Rarely, a long traffic hit (117 ms) can occur on E1-42 cards after an XC side-switch. In multinode MS-SPR setups, switching the cross-connect cards repeatedly might cause traffic hits greater that 60 ms. To avoid this issue, side-switch the XC only when needed (and not repeatedly). This issue will not be resolved.

CSCeg19255—DS3I VC3 traffic takes a hit greater than 60 ms during cross-connect card soft reset

Rarely, DS3I VC3 traffic takes a hit greater than 60 ms during a cross-connect card soft reset. This issue will not be resolved.

CSCsu31027—J1 path trace does not work for E3 and DS3I from port 5 onward

The J1 path trace string is not received for ports greater than 5 on an E3 card under the following conditions:

1. Create a VC3 circuit between any two E3 ports of an E3 card for ports greater than 5.

2. Change the J1 path trace string. Set the transmitted and expected string. The J1 path trace is not received.

The workaround is to test the J1 path trace on the OCN cards before setting the string.

This issue will be resolved in a future release.

Hardware

This section documents caveats for Hardware in Release 8.6.

CSCei36415—Retrieving Gigabit Interface Converter (GBIC) inventory for FC_MR-4 returns nothing for CLEI code

When retrieving Gigabit Interface Converter (GBIC) inventory for the FC_MR-4, nothing is returned for the CLEI code. In a future release, enhanced inventory information will be available for ONS GBICs, including the CLEI code. This issue will be resolved in a future release.

CSCeb36749—In a Y-cable configuration, CARLOSS alarm is major and affects service even though traffic is fine

In a Y-cable configuration, if you remove the client standby RX fibre, a nonservice-affecting LOS is raised, as expected. However, if you then remove the trunk active RX fibre, a nonservice-affecting LOS-P is raised, but the previously non-service affecting LOS on the client port is now escalated to a service affecting alarm, in spite of no traffic having been affected. This issue will not be resolved.

CSCed18803—Nonenhanced muxponder unit does not pass jitter tolerance test from trunk port to client port

Rarely, the nonenhanced muxponder unit does not pass jitter tolerance tests from trunk port to client port as specified by ITU-T G.825 for 2- Mb/s masks at the 10-Hz- specific setpoint. To see this issue, configure the muxponder with G.709 Off, FEC Off and the Trunk signal provided by the external jitter test box, and then monitor the unit client port output for errors.

This issue will not be resolved. Note, however, that in normal network configurations, the muxponder is operated with G.709 and FEC turned on, and the jitter tolerance tests pass.

Linear Multiplex Section Protection

This section documents caveats for Linear Multiplex Section Protection in Release 8.6.

CSCsr91312— Traffic hit of more than 2 seconds on upgrade when UPSR is active on protect

A soft reset of the ADM-10G results in the linear multiplex section protection/SNCP switch causing a traffic hit of 2000 ms. This issue occurs under the following conditions:

1. Create a linear multiplex section protection/SNCP circuit on the ADM-10G single card/double card configuration.

2. Set the protect path of the linear multiplex section protection/SNCP circuit as the active path.

3. Soft reset the ADM-10G card on which the linear multiplex section protection/SNCP drop is configured.

4. If the working linear multiplex section protection/SNCP is error free, only a <50-ms traffic hit is observed when the card comes up.

5. If the working linear multiplex section protection/SNCP path has an error, a >2000-ms traffic hit is observed when the card comes up.

The workaround is to ensure that the linear multiplex section protection circuit is active on the working path before issuing a soft reset of the ADM-10G card.

CSCee53579— Traffic hits occur in unprotected to Linear Multiplex Section protection topology upgrade in unidirectional routing

Traffic hits can occur in an unprotected to linear multiplex section protection topology upgrade in unidirectional routing. You can create an unprotected circuit, then upgrade the circuit to a linear multiplex section protection circuit using the Unprotected to Linear Multiplex Section protection wizard. Select unidirectional routing in the wizard, and the circuit will be upgraded to a linear multiplex section protection circuit. However, during the conversion, traffic hits on the order of 300 ms should be expected. This issue will not be resolved.

Maintenance and Administration

This section documents caveats for Maintenance and Administration in Release 8.6.


Caution VxWorks is intended for qualified Cisco personnel only. Use of VxWorks by customers is not recommended, nor is it supported by the Cisco's Technical Assistance Center. Inappropriate use of VxWorks commands can have a negative and service-affecting impact on your network. Consult the troubleshooting guide for your release and platform for appropriate troubleshooting procedures. To exit without logging in, enter a Control-D (press the Control and D keys at the same time) at the Username prompt. To exit after logging in, type "logout" at the VxWorks shell prompt.


Note Cisco Transport Controller (CTC) does not support adding or creating more than five circuits in auto-ranged provisioning. This restriction is intentional.



Note In releases earlier than Cisco ONS Release 4.6, you could independently set proxy server gateway settings; however, with Cisco ONS Release 4.6.x and later, this is no longer the case. To retain the integrity of existing network configurations, settings made in a pre-4.6 release are not changed upon upgrading to Cisco ONS Release 7.x. Current settings are displayed in Cisco Transport Controller (whether they were inherited from an upgrade or they were set using the current GUI).


CSCse38590—Station reports "remote WTR" on a space even though the neighboring station is not advertising Wait to Restore (WTR) state

In the RPR topology, one station reports a "remote WTR" on a space, even though the neighboring station is not advertising Wait to Restore (WTR) state. This issue is observed after many XC pulls/switches, deleting and recreating circuits, and replacing cross-connects completely. This issue does not appear to have any real impact to traffic, but can potentially complicate troubleshooting. The workaround is to configure a forced-switch on both ends of the problem span, and then remove the forced-switch from both ends.

CSCsd44081—Series of crashes and reboots occur when policy-map includes approximately 200 class-map entries and policers

A series of crashes and reboots may occur when a policy-map includes approximately 200 class-map entries and policers. This error appears to occur when the card boots up, the field-programmable gate array (FPGA) process is attempting to download the new FPGA, the policy-map has at least 200 class-map entries, and traffic has been punted to the host. These conditions may trigger a provisioning-message timeout on the ML card that can lead to a crash. Because the system boots up in the same state, a continuous series of crashed and reboots may occur. The workaround is to remove the circuits and wait until the node boots up with the latest FPGA image before reconfiguring the circuits.

CSCse23518 —RPR SPAN-MISMATCH alarm not reported correctly

The RPR SPAN-MISMATCH alarm is not reported correctly in some situations. After creating and deleting an East-to-East RPR circuit through TL1 cross-connects and creating a West-to-West RPR circuit through the TL1 cross-connects script, both within less than 1 second of the other, the RPR-SPAN-MISMATCH alarm is seen only on one side of the circuit and not on the other side.
This problem does not occur when the operations are made manually. This alarm indicates mis-cabling or cross-connects created between two East spans or two West spans. The workaround is to ensure more than 1 second between the deletion of one circuit and creation of the another.

CSCse53133—RTRV-COND-VCn does not display path alarms on MS-SPR protect path

RTRV-COND-VCn does not display path alarms on an MS-SPR protect path. When the MS-SPR is switched on to protection and the protect paths have conditions on them, the TL1 retrieval command does not show those conditions on protection paths. No workaround is available for this issue. This issue will be resolved in a future release.

CSCsg10963—Connections remain in unlocked-disabled,failed after roll is canceled

Connections remain in unlocked-disabled,failed state after roll is canceled. This issue occurs after you perform the following tasks:

1. Create an STM16/STM64 two-fibre MS-SP ring among three Cisco ONS 15454 nodes.

2. Create five VC3 two-fibre MS-SP circuits from Cisco ONS 15454 Node 1 to Cisco ONS 15454 Node 2. All connections enter unlocked-enabled state.

3. Perform bulk roll to roll all connections from East port to West port. Roll is not complete. UNEQ-P alarms are raised for rollTo paths. Connection states change to unlocked-disabled,failed.

4. Cancel roll.

UNEQ-P alarms clear and connection states remain in unlocked-disabled,failed. No workaround is available for this issue. This issue will be resolved in a future release.

CSCsg16500—ROLL-PEND condition seen for VC low-order path circuits on CTC conditions pane

The ROLL-PEND condition is seen for LO circuits on the Cisco Transport Controller Conditions pane after you perform the following tasks:

1. Create a two-node STM-4 unprotected setup between two Cisco ONS 15454 nodes.

2. Create one LO circuit from Cisco ONS 15454 SDH Node 1, STM1 card to Cisco ONS 15454 SDH Node 2, STM4 card.

3. Give autobulkroll to circuit on the STM4 span from VC4-1 to VC4-2.

4. Force the valid signal using ED-BULKROLL command to "true." Bulkroll completes and no rolls are present on any of the nodes.

The ROLL-PEND condition is now visible on VC circuits in CTC and TL1. No workaround is available for this issue. This issue will be resolved in a future release.

CSCse91968—Automatic inservice to unlock transition on MS-SPR four-fibre protect does not function properly

The automaticinservice-to-unlocked transition on MS-SPR four-fibre Protect is not functioning properly. When an MS-SP four-fibre ring is used, the automaticinservice-to-unlocked transition is not correct when protect is active (ring switched). Sometimes the wrong protect is transitioning at the IO. If the TSC is notified incorrectly, it becomes out of sync with the IO, and becomes stuck in automaticinservice state, even when the protect switch is released. The PCA is also being incorrectly notified of an automaticinservice-to-unlocked transition. This issue will be resolved in a future release.

CSCeh92201—IDRI circuit created with wrong span selection

When you create a bidirectional MS-SPR-SNCP IDRI circuit using autorouting and select the PCA option for secondary spans, the circuit is created over working MS-SPR spans and does not use PCA spans. To enforce the use of the PCA option, provision the circuit using manual routing. This issue will not be resolved.

CSCef53317—Traffic hit occurs during clock reference switch

A traffic hit can occur during a clock reference switch. When the clock offset reaches approximately 17 ppm, Clock Reference 1 fails and MXP-1 switches to Clock Reference 2. During the clock switch, a traffic hit might occur for less than 1 second. The same behavior can occur when injecting a positive frequency offset. This issue will not be resolved.

CSCsg42366—Traffic outage occurs when FPGA upgrade is done with manual switch on Y-cable

A traffic outage of 120 sec occurs when an FPGA upgrade is done with a manual switch on the Y-cable and the client port is in out of service.

To prevent traffic outages, follow the procedure for an FPGA upgrade:

1. Configure the following:

Near-end (NE) node, 2 MXP-MR-10DME, Working and Protect, with the Working Active and the Protect Stdby for each protection group supported on the client ports

Far-end (FE) node, 2 MXP-MR-10DME, Working and Protect, with the Working Active and the Protect Stdby for each protection group supported on the client ports

NE Working card trunk port connected to FE Working card trunk port

NE Protect card trunk port connected to FE Protect card trunk port

2. Ensure traffic is running on the Working cards, for each protection group is supported by the MXP-MR-10DME cards.

3. Issue a Lockout of Protect to ensure traffic does not switch to Protect. Perform this on both NE and FE protection groups.

4. Disable client ports on the Protect cards and complete the manual FPGA upgrade. The upgrade should be hitless because traffic is accommodated on the Working facilities.

5. After the card has completed the software reset, move back the client ports to unlocked-enabled state. Ensure no unexpected alarm or condition is present on the Protect cards.

6. Release Lockout of Protection on both ends, on every protection group. This operation is not traffic affecting. Traffic is still carried on Working facilities.

7. Issue a Force to Protect on both NE and FE protection groups so that traffic switches from Working to Protect facilities. Do this on every protection group supported by these cards. The Force to Protect switching is affecting traffic less than 50 ms.

8. Disable client ports on the Working cards and complete the manual FPGA upgrade. The upgrade should be hitless because traffic is accommodated on the Protect facilities.

9. After the card has completed the software reset, move back the client ports to unlocked-enabled state. Ensure no unexpected alarm condition is present on the Working cards.

10. Release Force to Protect on both ends, on every protection group. If the protection group is revertive, this operation will revert traffic to the Working facilities. Less than 50-ms hits are expected. The operation keeps traffic on the Protect facilities if the protection group is nonrevertive and hitless.

This issue will not be resolved.

MS-SP Ring Functionality

This section documents caveats for Multiplex Section- Shared Protection (MS-SP) in Release 8.6.

CSCdv53427— Protection vulnerabilities in two-ring, two-fibre MS-SP ring configuration

In a two-ring, two-fibre MS-SP ring configuration (or in a two-ring MS-SP ring configuration with one two-fibre and one four-fibre ring) it is possible to provision a circuit that begins on one ring, crosses to a second ring, and returns to the original ring. Such a circuit can have protection vulnerabilities if one of the common nodes is isolated, or if a ring is segmented in such a way that two noncontiguous segments of the circuit on the same ring are both broken.

NCP

This section documents NCP caveats for Release 8.6.

CSCdu82934—Failure of VC low-order path circuit creation

When you auto route a VC11/VC12 circuit on an ONS 15454 node, a path is computed based on the availability of VC3/VC4n on the nodes involved. This selection process, when combined with a lack of VC11/VC12 matrix (or VC3/VC4n-VC11/VC12 connections) on an auto route selected node, can result in theVC11/VC12 circuit creation failing with the message "unable to create connection object at node." To correct this situation, manually route VC11/VC12 circuits in cases when auto routing fails. The error message will indicate which node is at issue.

CSCsu10564—DCN-EXT: OTS PPC problem with OSPF enabled on LAN

The provisionable patchcord (PPC) link does not show up in the CTC network view and it is not possible to route circuits. This issue occurs under the following conditions:

1. Connect two nodes with optical transport section (OTS) PPC. At least one of the two nodes does not have any other service channel, that is, optical service channel (OSC), data communication channel (DCC), or generic communications channel (GCC). Both nodes have OSPF enabled on a LAN with area ID 0.0.0.0.

2. Although the PPC link is correctly configured on both nodes it is not added to the OSPF link table, which prevents the link from showing in CTC.

The workaround for this issue is as follows:

1. Disable OSPF on the LAN on the node that does not have another service channel.

2. If OSPF cannot be disabled, make sure that at least one service channel (OSC, DCC, or GCC) is provisioned on both nodes involved in the PPC connection.

This issue will be resolved in a future release.

Optical I/O Cards

This section documents caveats for Optical I/O Cards in Release 8.6.

CSCsr76682—Bit errors observed on STM64 XFP after both XC cards reboots

Bit errors are observed on the STM64 XFP card after both the XC-10G cross-connect cards hard reboots.

Bit errors occur under the following conditions:

1. Traffic passes through the STM64 XFP card.

2. Both the XC (cross-connect) cards are hard reset at the same time (due to power cycling of the node), or you lock out one XC card and do a hard reset of the active XC card.

3. The XC card comes up and becomes active and the traffic is up again.

4. Dribbling bit errors are seen on some of the paths passing through the STM64 XFP card.

The workaround for this issue is to side-switch the cross-connect card. This issue will be resolved in a future release.

CSCsr13870— Traffic hit of around 18 ms on STM4_4 card when node is upgraded

Traffic hits of approximately 18 ms occur on STM4_4 card when the node is upgraded. The Auto-Reset condition is raised and cleared twice on the card. This issue occurs under the following conditions:

1. The STM4_4 card reboots twice.

2. The second time the card reboots, it comes up as a cold-reboot causing loss in traffic.

No workaround is available for this issue. This issue will be resolved in a future release.

CSCei26718—Different alarm behavior between one-way and two-way VC circuit creation on linear multiplex section protection

On the 15454-MRC-12 card, when a one-way VC circuit on path protection over 1+1 protection is created, the alarm behavior is not the same as in two-way circuit creation. In particular, for the one-way circuit creation, UNEQ-V and PLM-V alarms are reported, and the circuit state remains locked. This issue will not be resolved.

CSCin29274—Same static route on two interfaces fails

When configuring the same static route over two or more interfaces, use the following command:

ip route a-prefix a-networkmask a.b.c.d

where a.b.c.d is the address of the outgoing gateway;

or, similarly, use the command:

ip route vrf vrf-name

Do not try to configure this type of static route using only the interface instead of the address of the outgoing gateway. This issue will not be resolved.

CSCsv54817—VC4-32c circuits do not work with STM64 XFP cards

VC4-32c circuits raise path unequipped alarms if the circuit uses an STM64 XFP card as a source, destination, or trunk. This issue occurs under the following conditions:

1. Provision an VC4-32c circuit with one end of the circuit on an STM64 XFP card or using an STM64 XFP as the trunk card.

2. The path unequipped alarm is raised on the VC4-32c circuit.

No workaround is available for this issue. However, you could use a fixed-port STM64 card to have VC4-32c circuits, because those circuits work correctly on those cards.


Note CTC/TL-1 does not stop provisioning the VC4-32c circuit on STM64 XFP cards, even though the circuit eventually fails to carry traffic later.


This issue will be resolved in a future release.

CSCee17695—STM1-8 card fails to read MFG EEPROM and shows MEA in CTC

Rarely, an STM1-8 card might fail to read MFG EEPROM and will show MEA in Cisco Transport Controller. This issue can be reproduced by power cycling the node several times, by quickly removing and reinserting a fuse, or by removing the fuse for several minutes and then replacing it; however, the issue is not likely to be due to the power cycling. If a card enters this state, remove and reseat it, or cycle power again to recover STM1-8 operation. This issue will not be resolved.

CSCsu50003—Traffic loss when concatenated unidirectional circuit is provisioned through 1 + 1 protected clients

Traffic loss occurs when a concatenated unidirectional circuit is provisioned through 1 + 1 protected clients under the following conditions:

1. Set up the Cisco ONS 15454 NE with two ADM-10G cards as peer group (double card).

2. Create 1+1 protection group between client ports of ADM peer group.

3. Create a unidirectional concatenated circuit (VC4 onward) with the source as the working port of the 1 + 1 group and the destination (drop) as the client or trunk on the card where the protect port of 1 + 1 is configured. Traffic goes down if the working port (1 + 1 protection group) state is ACTIVE.

4. Create a unidirectional concatenated circuit with the source as the working port of the 1 + 1 group and destination (drop) on the card where the working port of 1 + 1 is configured. Traffic goes down if the protect port (1 + 1 protection group) state is ACTIVE.

The workaround for this issue is to manually switch to another facility in the protection group when the traffic is down.

TL1

This section documents caveats for TL1 in Release 8.6.


Note To be compatible with TL1 and DNS, all nodes must have valid names. Node names should contain alphanumeric characters or hyphens, but no special characters or spaces.


CSCsc41650 —Node reboots during DS3XM card pre-provisioning

Using a TL1 script to rapidly preprovision or delete various cards repeatedly in the same slot will reboot the TCC approximately 1 out of 10 times. Configuring a delay of about 10 seconds between preprovisioning/deletion cycles causes the node to not reboot. This issue will be resolved in a future release.

Resolved Caveats for Release 8.6

This section documents caveats resolved in Release 8.6.

Alarms

This section documents resolved caveats for Alarms in Release 8.6.

CSCsv30867—Alarms do not clear after XC side-switch or switch-duplex of matrix cards

Raised alarms do not clear after an XC side- switch or switch-duplex of matrix cards. This issue has been resolved.

CSCsl34189—PDI-P is not detected by ADM-10G card

If PDI-P is injected to the active path of the linear multiplex section protection circuit on an ADM-10G card, the linear multiplex section protection circuit does not switch to the protected path. The PDI-P alarm is not raised. For unprotected circuits, the alarm is not raised if PDI-P is injected. This issue has been resolved.

CSCsj96051—CE100 port transitions from Automatic In Service to unlocked when CARLOSS alarm is raised

Ports on CE100 and CE100T cards with a CARLOSS alarm will transition into unlocked state if the state is changed from locked, disabled to Automatic In Service and provisioned with zero soak-time. This issue has been resolved.

Common Control Cards

This section documents resolved caveats for Common Control Cards in Release 8.6.

CSCso58291—TCC2P card resets and goes into EQUIPMENT FAIL state

When the TCC2P card reboots during an active Direct Memory Access (DMA) transfer, the card fails to boot up, and goes into an EQUIPMENT FAIL state. This issue has been resolved.

CSCsr41128—TCC card reboots when many sockets are created

The traffic from a port scanner creates many sockets, causing the TCC card to reboot. This issue has been resolved.

CTC

This section documents resolved caveats for Common Control Cards in Release 8.6.

CSCsi29266— CTC displays BIC_UNKNOWN

The CTC inventory window displays BIC_UNKNOWN, when EIA BIC is not installed in either the A or B position on ONS 15454-SA or 15454-SA-HD chassis. This issue has been resolved.

CSCsl68680— CTC indicates AIS insert on terminal loopback as default setting

When terminal loopback is activated on the DS3 card and loopbacks are performed on the DS3 or DS3E cards, the column for AIS on Terminal Loopback is checked for each DS3 line. Checking this column indicates AIS, and will be sent in a direction away from the loopback. This issue has been resolved.

CSCsk59570—CTC does not display warning message regarding unauthorized access

When a user logs in to CTC, no warning message is displayed regarding unauthorized access. This issue has been resolved.

Data I/O Cards

This section documents resolved caveats for Data I/O Cards in Release 8.6.

CSCsl10070—Gigabit Ethernet interface with autonegotiation disabled is down after shut and no shut commands are issued

A Gigabit Ethernet interface with autonegotiation disabled remains down after shut and no shut commands are issued. This issue has been resolved.

CSCsm21404—Packet loss with soft reset of CE-MR-6/CE-MR-10 card

The traffic is affected for 1000 milliseconds when a CE-MR-6/CE-MR-10 card is soft reset after an SW-LCAS circuit is created between the CE-MR-6/CE-MR-10 card and the CE-1000-4 card. The traffic is affected for 30 milliseconds when the CE-MR-6/CE-MR-10 card is soft reset after an SW-LCAS circuit is created between the CE-1000 card and the CE-MR-6/CE-MR-10 card. This issue has been resolved.

CSCsq14370—ifspeed query results in incorrect value for circuit size

When queried, the ifspeed parameter returns a value of 1000 for the POS port regardless of the circuit size provisioned on CE-MR-6/CEMR10 cards. This issue has been resolved.

CSCsg92555— 20% CPU utilization without any configuration on ML100X-8 card

An ML100X-8 card shows 20% CPU utilization even without any configuration on the card. This issue has been resolved.

CSCsk04872— Multiple low-order VCATs do not transition to unlocked when created in TL1 or CTC

In Release 8.0, when multiple members (more than 16) are added to a low-order VCAT group using TL1 scripts or CTC with the service state set to unlocked, not all members report being in unlocked state. This issue has been resolved.

CSCsg35077—Cisco IOS crashes while processing malformed ISAKMP message

A device with a valid IPSec configuration that is running Cisco IOS software may crash during processing of an Internet Key Exchange (IKE) message. This issue has been resolved.

DWDM

This section documents resolved caveats for DWDM in Release 8.6.

CSCsl50180—ADM-10G card reboots after creating 1S-2D circuits

The ADM-10G card reboots after creating 1S-2D circuits when one of the destinations has an LOS. Rebooting occurs when the circuits switch to linear multiplex section protection while performing port-level provisioning on any of the ports. This issue has been resolved.

CSCsm73009—HW FAIL alarm is raised when optical module is not recognized

The HW FAIL alarm is raised when the optical module connected to a card is not recognized by the TCC2 card. This issue has been resolved.

CSCso92457—4G-FC switching on MXP-MR-10DME card takes longer time

4G-FC traffic switching on an MXP-MR-10DME card in a Y-cable configuration happens after 4 to 5 minutes instead of 20 seconds. This issue has been resolved.

CSCsq65534—CRC error on TX interface

Packet loss or CRC error occurs on the TX interface when traffic with Jumbo packet or high clock discrepancy is created between the far-end RX interface and the near-end TX interface. This issue has been resolved.

CSCsr41096—Traffic is affected on 4G-FC switching on MXP-MR-10DME

The data traffic is affected on the egress side of the MXP-MR-10DME card connected either to an MDS or Brocade switch. This problem occurs only when the MXP-MR-10DME card receives small packets (36 bytes, that is, packets with a 0-byte payload) from either the MDS or Brocade switch. No alarm is raised on CTC. This issue has been resolved.

CSCsr75681—Packet drop for high throughput on MXP-MR-10DME card

Packet drop occurs for high throughput on an MXP-MR-10DME card connected to an MDS-9513 switch with 4G-FC provisioned on port 1. This issue has been resolved.

CSCsm82513—Support of far-end laser control

Far-End Laser Control (FELC) is supported on copper SFP modules in the current release for GE_XP cards. This issue has been resolved.

CSCsq16653—Far-end port will be in squelched state on GE_XP card until the card is reset

In GE_XP cards, when an optical SFP is inserted instead of a copper SFP and the optical module has SYNCLOSS (not from FELC) before the port is put in locked state, the far-end port will be in squelched state until the card is reset. This issue has been resolved.

CSCsu26568—Traffic loss on 1G port of the GE_XP card

Loss of traffic occurs on the 1G port of the GE_XP card, when a copper PPM is swapped or replaced with a fibre PPM or vice versa. This issue has been resolved.

CSCsd80965—Traffic hit on TXP-MR-2.5G cards while upgrading the nodes from 5.0 or 6.0 to 7.xx versions

A traffic hit is observed on TXP_MR_2.5G cards while upgrading the nodes from Release 5.0 or 6.0 to Release 7.xx versions. The trunk laser shuts down after the upgrade. This issue has been resolved.

The GE_XP card in L1 mode reports the FEC Uncorrected Word (UNC-WORD) condition when G.709 is enabled and FEC is disabled on both ends of the GE_XP trunk port. The workaround is to set the FEC to standard. This issue has been resolved.

CSCsr91742—Maximum bandwidth of data communication channel (DCC) in subshelf is less than the bandwidth in the node controller

The implementation of DCCs in a multishelf configuration cannot handle congestion in the TX buffer of the subshelves. This issue has been resolved.

Linear Multiplex Section Protection

This section documents resolved caveats for linear multiplex section protection in Release 8.6.

CSCsv30593—AIS-V alarm does not clear in VC11 cross-connect circuits

In VC11 cross-connect circuits, an AIS-V alarm does not clear even though there are no defects. This issue has been resolved.

CSCsw86999 —AIS-V alarm does not clear for VC high-order path that does not have circuit created on VT-1

AIS-V alarm does not clear for an VC high-order path circuit that does not have a circuit created on VT-1. This issue has been resolved.

Maintenance and Administration

This section documents resolved caveats for Maintenance and Administration in Release 8.6.


Caution VxWorks is intended for qualified Cisco personnel only. Use of VxWorks by customers is not recommended, nor is it supported by the Cisco's Technical Assistance Center. Inappropriate use of VxWorks commands can have a negative and service-affecting impact on your network. Consult the troubleshooting guide for your release and platform for appropriate troubleshooting procedures. To exit without logging in, enter a Control-D (press the Control and D keys at the same time) at the Username prompt. To exit after logging in, type "logout" at the VxWorks shell prompt.


Note Cisco Transport Controller (CTC) does not support adding or creating more than five circuits in auto-ranged provisioning. This restriction is intentional.



Note In releases earlier than Cisco ONS Release 4.6, you could independently set proxy server gateway settings; however, with Cisco ONS Release 4.6.x and later, this is no longer the case. To retain the integrity of existing network configurations, settings made in a pre-4.6 release are not changed upon upgrading to Cisco ONS Release 7.x. Current settings are displayed in Cisco Transport Controller (whether they were inherited from an upgrade or they were set using the current GUI).


CSCsk42322—Pointer justification counter increments only for port 1 on MRC-12 card

The Pointer Justification counter increments only for port 1 on MRC-12 cards. This issue has been resolved.

CSCsr50786—Optical threshold defaults reset when software is upgraded

When a software upgrade from a release earlier than Release 8.0 to Release 9.0 is made, the optical threshold defaults of Release 9.0 are applied and all previously configured optical threshold defaults are lost. When a software upgrade from Release 8.0 and later to Release 9.0 is made, the configured optical threshold values are not overwritten. This problem occurs for ADM-10G, MXP-2.5G-10E, MXP-2.5G-10G, MXP-MR-10DME, MXP-MR-2.5G, MXPP-MR-2.5G, OTU2-XP, TXP-MR-10E, TXP-MR-10G, TXP-MR-2.5G, TXPP-MR-2.5G, 10GE-XP, and GE-XP cards. This issue has been resolved.

CSCsv13893—Admin state change from unlocked,enabled to locked,disabled fails

Changing the Admin state of an electrical port or optical port from unlocked,enabled to locked,disabled fails. This issue has been resolved.

CSCsk84133—Unable to archive audit log

The user cannot perform an audit log and the system displays the message "The archive is up to date". This issue has been resolved.

CSCsv14375— Shared secret key greater than 16 characters corrupts after an upgrade

The shared secret key greater than 16 characters corrupts after an upgrade from Release 7.20 to Release 8.5.2. This issue has been resolved.

NCP

This section documents resolved caveats for NCP found in Release 8.6.

CSCsx37297—FTP port issue for TCP Connect Scan

Line cards do not boot up, and software downloading and database synchronization between Active and Standby TSC cards fail under the following condition:

The FTP server task is blocked at the external FTP socket because of the execution of port scanners.

The workaround is to perform an FTP to the node. This issue has been resolved.

Optical I/O Cards

This section documents resolved caveats for Optical I/O Cards in Release 8.6.

CSCsr99947—Unable to retrieve VC high-order path PM values and thresholds on ports 2, 3, and 4

The VC high-order path PM values and thresholds on ports 2, 3, and 4 on an MRC-25G-4 card cannot be retrieved. This issue has been resolved.

CSCsm44367—False line PM values reported on facility loopback for STM4-1 card

False line PM values are reported on STM4-1 cards with facility loopback configured. This issue has been resolved.

TL1

This section documents resolved caveats for TL1 in Release 8.6.

CSCsw92329—TL1 does not initialize PM counts on all ports of MRC card

The INIT-REG-<Mod> command does not initialize the PM counts. When the command is used to initialize a specific PM count, all ports on the MRC-12 can be initialized except for the first port. When the command is used to initialize all PM counts, all PM counts are initialized. This issue has been resolved.

New Features and Functionality

No new software features are included in Release 8.6.

Related Documentation

This section lists release-specific and platform-specific documents.

Release-Specific Documents

Release Notes for the Cisco ONS 15454, Release 8.5.2

Release Notes for the Cisco ONS 15454 SDH, Release 8.5.2

Release Notes for the Cisco ONS 15454, Release 8.5.3

Release Notes for the Cisco ONS 15454 SDH, Release 8.5.3

Release Notes for the Cisco ONS 15310-MA, Release 8.5.3

Release Notes for the Cisco ONS 15454, Release 8.6

Release Notes for the Cisco ONS 15310-MA, Release 8.6

Release Notes for the Cisco ONS 15310-CL, Release 8.6

Platform-Specific Documents

Cisco ONS 15454 Release 8.6 is based on Cisco ONS 15454 Release 8.5.2 and Cisco ONS 15454 Release 8.5.3. Please refer to the Release 8.5.2 and 8.5.3 documents.

Cisco ONS 15454 SDH Procedure Guide
Provides installation, turn up, test, and maintenance procedures

Cisco ONS 15454 SDH Reference Manual
Provides technical reference information for SONET/SDH cards, nodes, and networks

Cisco ONS 15454 DWDM Installation and Operations Guide
Provides technical reference information for DWDM cards, nodes, and networks

Cisco ONS 15454 SDH Troubleshooting Guide
Provides a list of SDH alarms and troubleshooting procedures, general troubleshooting information, transient conditions, and error messages

Cisco ONS SDH TL1 Command Guide
Provides a comprehensive list of TL1 commands

Cisco ONS SDH TL1 Reference Guide
Provides general information, procedures, and errors for TL1

Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide
Provides software feature and operation information for Ethernet cards

Cisco ONS 15454 Software Upgrade Guide, Release 8.5.x

Obtaining Optical Networking Information

This section contains information that is specific to optical networking products. For information that pertains to all of Cisco, refer to the Obtaining Documentation and Submitting a Service Request section.

Where to Find Safety and Warning Information

For safety and warning information, refer to the Cisco Optical Transport Products Safety and Compliance Information document that accompanied the product. This publication describes the international agency compliance and safety information for the Cisco ONS 15454 system. It also includes translations of the safety warnings that appear in the ONS 15454 system documentation.

Cisco Optical Networking Product Documentation CD-ROM

Optical networking-related documentation, including Cisco ONS 15xxx product documentation, is available in a CD-ROM package that ships with your product. The Optical Networking Product Documentation CD-ROM is updated periodically and may be more current than printed documentation.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.