Release Notes for Cisco ONS 15454 SDHRelease 8.5.2

OL-16590-01

June 30, 2008

Release notes address closed (maintenance) issues, caveats, and new features for the Cisco ONS 15454 SDH multiplexer. 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.1 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.1 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.5.2, visit the following URL:

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.5.2 since the production of the Cisco ONS 15454 SDH System Software CD for Release 8.5.2

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.

Note The usage of 40WXC units are supported only in the networks running software Release 8.5.1 and later.

Alarms

This section documents Alarms caveats in Release 8.5.2.

CSCed28167

When a VC_LOW_PATH_TUNNEL only contains unidirectional circuits, an AU-LOP critical alarm is raised. This 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.

CSCef63240

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

CSCsl88037

Improper Removal alarm is raised on Slot-24 on activation even when the card is not present in Slot-24 before activation. Workaround is to connect Slots 23 and 24 to power modules.

CSCsq26495

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 fiber SFP at the far end. This 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 fiber 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.

There is no workaround for this issue. This issue will be resolved in a future release.

Common Control and Cross-Connect Cards

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

CSCec82148

Rarely, traffic hits can occur on TCC2/TCC2P card removal. 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.

Data I/O Cards

This section documents Data I/O cards caveats in Release 8.5.2.

CSCsm09512

A hard reset on a CE-MR-10 card causes a low order (LO) VC12-64v circuit or VC12-63v circuit to move into the VCG-DEG state. The workaround is to delete the circuit members after moving them to the locked,outOfGroup state and then adding them again to the circuit. This issue will be resolved in a future release.

CSCsm99133

Software upgrade on a Cisco ONS 15454 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 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

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

•Create a VC12-63v open ended HW-LCAS circuit between two network elements (NEs).

•On the CE-MR-10 card, place all members in the locked,outOfGroup state and delete the last 45 members.

•Place the remaining 18 members in unlocked state.

This results in an unbalanced VCG. There is loss of traffic and a PDI-P 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 members in the inGroup state on both ends of the circuit. This issue will be resolved in a future release.

CSCso54993

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. There is no workaround for this condition. This issue will be resolved in a future release.

CSCso55327

A reset of a TCC switch on CE-MR-10 and ML-MR-10 cards causes a traffic hit of upto 180ms on all circuits with software prior to release 9.0. There is no workaround for this issue. This issue will be resolved in a future release.

CSCso66424

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

CSCso94644

The LCAS VCG Member Rx side in Add State condition might persist after a hard reset of a CE-MR-10 card or a ML-MR-10 card carrying a HW-LCAS circuit with loopback on split fiber 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

An upgrade on Cisco ONS 15454 from release 8.50 to release 8.52 followed by a power cycle of the node causes a traffic hit on CE100T-8 cards. The workaround is to change the Admin state of the CE00T-8 card to the Maintenance state followed by a hard reset. This issue will be resolved in a future release.

CSCsq02815

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

Software upgrade on a Cisco ONS 15454 from Release 8.50 or 8.51 to Release 8.52 sometimes causes a traffic hit of 180 ms on CE-MR-10 cards with VCAT LCAS circuits. There is no workaround for this issue. This issue will be resolved in a future release.

CSCsq12616

A path payload defect indication (PDI-P) alarm is raised from the Far End NE causing the ethernet port to go down. This 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 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:

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

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

•Delete members on the near end NE.

•Delete members on the far end NE.

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

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

This issue will be resolved in a future release.

CSCsq16464

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. This 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 there is no congestion on the ring, the priority-multicast configuration can be removed. This issue will be resolved in a future release.

CSCsq20532

A traffic hit of about 25ms may occur in a Low Order LCAS circuit if members in the locked,outofGroup state are deleted in CE-MR-10, CE-MR-6 and ML-MR-10 cards. There is no workaround for this issue. This issue will be fixed in a future release.

CSCsq24903

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

•It is more probable if the data frame is large.

There is no workaround for this issue. This issue will not be resolved.

CSCsq42702

The HW-LCAS circuit with split-fiber routing on a CE-100T-8 card in the GFP framing mode goes down and the GFP-LFD alarm is raised if the fiber carrying the first member is unplugged due to which the circuit does 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 fiber 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 is seen in the following conditions:

•The fiber on the path that is carrying the first member is cut.

•The Tx and Rx fiber is unplugged from the span.

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

CSCsq52786

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. There is no workaround for this issue. This issue will be resolved in a future release.

DWDM

CSCsg10008

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

•RX fibers is 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 fiber on Trunk PPM port.

•User command, e.g., FORCE, is issued.

There is no workaround for this issue.

CSCsg22669

There is a traffic hit of greater than 50 ms but less than 60 ms on MXP-2.5G-10E in Y-cable configuration when a fiber cut occurs. This issue will be resolved in a future release.

CSCsf04299

When triggering the switch of optimized 1+1 protection and the failure is cleared, the WTR condition is raised, but once 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

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

CSCsm82422

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. There is no workaround for this issue. This issue will not be resolved.

CSCsq46283

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 to unlocked-to-locked,maintenance-to-unlocked.The workaround is to move the port to locked,disabled and then to unlocked state. This issue will be fixed in a future release.

CSCei19148

When a port is placed unlocked state while the conditions necessary to squelch the port are present, as in 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

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

CSCsb47323

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

CSCsb94736

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 can occur in an N-F configuration with MDS switch and MXP_MR_10DME distance extension on, where test equipment traffic is set to 2G Fiber channel (FC) full bandwidth occupancy and started. Stop traffic or keep bandwidth occupancy below 80% during the login phase to work around this issue. This issue will not be resolved.

CSCsc36494

Manual Y-cable switches with squelching turned off in the MXP-MR-10G card can cause a fiber channel link with Brocade switches to go down. SIGLOSS and GFP-CSF alarms are seen on the Cisco. Cisco recommends you provision squelching to be on when interworking with Brocade switches. If for some reason, squelching must be off with Brocade switches, Cisco recommends you use a FORCE command to perform Y-cable switches. It is not known when or if this issue will be resolved.

CSCsc60472

Cisco Transport Controller 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

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. There is no workaround for this issue. This issue will be resolved in a future release.

CSCee45443

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

CSCef54670

The SQUELCHED condition is not raised when a non-enhanced 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 is as designed.

CSCeh94567

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

When an alarm raised on the port is cleared, the severity is not cleared. The workaround is to close and re-open Cisco Transport Controller Functional View. This issue will be resolved in a future release.

CSCso73947

The E port is down for 2 minutes after MXP-MR-10DME card power up under the following conditions:

•The card is connected to Fibre Channel (FC) switches on both ends.

•The switches are connected to 4G FC ports.

No alarm is reported. There is no workaround for this issue. This issue will be resolved in a future release.

CSCso82618

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. There is no workaround for this issue. The issue will be resolved in a future release.

CSCso92518

In 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 is not applicable to a G.709 OFF trunk port. The workaround is to use OTUk/ODUk TTI. This issue will be resolved in a future release.

CSCsq16317

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.

CSCsq16653

In GE-XP cards, when an optical SFP is inserted instead of a copper SFP which has SYNCLOSS (not from FELC) before putting the port to locked state, the far end port will be in squelched state until the card is reset. The workaround is to do a soft reset of the GE-XP card. This issue can be avoided by placing the near end and far end ports to locked state before removing the cable from the copper SFP. This issue will be resolved in a future release.

Electrical I/O Cards

This section documents Electrical I/O Cards caveats in Release 8.5.2.

CSCeg80233

Long traffic hits can occur on E1-42 when using cross-connect FIT cards. This 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

Rarely, a long traffic hit (117 ms) can occur on E1-42 after an XC side switch. In multinode MSSPR 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

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

Hardware

This section documents Hardware caveats in Release 8.5.2.

CSCei36415

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. This will include the CLEI code. This issue will be resolved in a future release.

CSCeb36749

In a Y-Cable configuration, if you remove the client standby RX fiber, a nonservice-affecting LOS is raised, as expected. However, if you then remove the trunk active RX fiber, 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

Rarely, the non-enhanced Muxponder unit does not pass jitter tolerance test from trunk port to client port as per ITU-T G.825, 2 Mb/s mask, at the 10 Hz specific setpoint. The Muxponder should be configured with G.709 Off, FEC Off and Trunk signal provided by external Jitter test box, and the unit client port output monitored for errors, to see this issue. 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.

Maintenance and Administration

Caution VxWorks is intended for qualified Cisco personnel only. Use of VxWorks by customers is not recommended, nor is it supported by Cisco's Technical Assistance Center. Inappropriate use of VxWorks commands can have a negative and service-affecting impact on your network. Please consult the troubleshooting guide for your release and platform for appropriate troubleshooting procedures. To exit without logging in, enter a Control-D (hold down 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 Planner (CTC) does not support adding or creating more than 5 circuits in auto-ranged provisioning. This is as designed.

Note In releases prior to Cisco ONS Release 4.6 you could independently set proxy server gateway settings; however, with Cisco ONS Release 4.6.x and forward, 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 on an upgrade 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

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. This problem was seen after multiple XC-pulls, XC-side-switches, circuit-deletions and circuit-creations. 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

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. Since 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

The RPR SPAN-MISMATCH alarm is not reported correctly in some situations. After creating and deleting an East-to-East RPR circuit through TL-1 x-connects and creating a West-to-West RPR circuit through the TL-1 x-connects script, both within less than one 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 one second between the deletion of one circuit and creation of the another.

CSCse53133

RTRV-COND-VCn does not display path alarms on MSSPR protect path. When MSSPR 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. There is no workaround for this issue. This issue will be resolved in a future release.

CSCsg10963

Connections remain in unlocked-disabled,failed after roll is cancelled. This occurs under the following conditions:

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 Cisco Transport Controller and TL1. There is no workaround for this issue. This issue will be resolved in a future release.

CSCse91968

The automaticinservice-to-unlocked transition on MSSPR 4F Protect not functioning properly. When a MSSPR 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

When you create a bidirectional MS-SPRing-SNCP IDRI circuit using autorouting and select the PCA option for secondary spans, the circuit is created over working MS-SPRing 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

A traffic hit can occur during a clock reference switch. When the clock offset reaches around 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 one second. The same behavior can occur when injecting positive frequency offset. This issue will not be resolved.

CSCsm38428

VCn traffic loss occurs on the MXP-2.5G-10G card when the database is restored after upgrading the software from Release 7.0.4 to Release 8.5.1. There is no workaround for this issue. This issue will be resolved in a future release.

MS-SP Ring Functionality

CSCdv53427

In a two-ring, two-fiber MS-SP Ring configuration (or a two-ring MS-SP Ring configuration with one two-fiber and one four-fiber 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 non-contiguous segments of the circuit on the same ring are each broken.

CSCeh92201

When you create a bidirectional MS-SP Ring path protection IDRI circuit using autorouting and select the PCA option for secondary spans, the circuit is created over working MS-SP Ring 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.

NCP

This section documents NCP caveats for Release 8.5.2.

CSCdu82934

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.

Optical I/O Cards

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

CSCei26718

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

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

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

Where a.b.c.d is the address of the outgoing gateway; or, similarly, use the command:

ip route vrfvrf-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.

CSCee17695

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 when the fuse is removed for several minutes and then replaced; 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.

Path Protection Functionality

This section documents Path Protection caveats in Release 8.5.2.

CSCee53579

Traffic hits can occur in an unprotected to path protection topology upgrade in unidirectional routing. If you create an unprotected circuit, then upgrade the unprotected circuit to a path protection circuit using Unprotected to path protection wizard, selecting unidirectional routing in the wizard, the circuit will be upgraded to a path protection circuit. However, during the conversion, traffic hits on the order of 300 ms should be expected. This issue will not be resolved.

TL1

This section documents TL1 caveats in Release 8.5.2.

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

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. Configure a delay of about 10 seconds between preprovisioning/deletion cycles and the node will not reboot. This issue will be resolved in a future release.

Resolved Caveats for Release 8.5.2

This section documents caveats resolved in Release 8.5.2.

Alarms

This section documents resolved Alarms caveats in Release 8.5.2.

CSCsj39442

The SYNCLOSS alarm on the standby Y-cable port is reported as Minor instead of Major. This issue has been resolved.

CSCsj88469

The protect port of the Y-cable protected MXP-MR-10DME cards report SYNCLOSS alarm as Minor instead of Major. This issue has been resolved.

CSCsj97288

The PROV-MISMATCH alarm is raised on TXP_MR_10E cards when a port with ONS-XC-10G-L2 Pluggable Port Module (PPM) is provisioned for ZR reach for 10GE. This issue has been resolved.

CSCsk15712

The trunk port of the Y-cable protected TXP-MR-2.5G card raises LOS-P alarm in Critical state. The workaround is to change the port status to locked,disabled. When the port status is changed to locked,disabled, the LOS-P alarm demotes to Minor from Critical state. This issue has been resolved.

CSCsl04155

Transient alarms occur under the following conditions:

•When upgrading the software from Cisco ONS Release 4.x, 5.x, 6.x, and 7.x to Cisco ONS Release 8.5, the PMI and FDI alarms are raised. These alarms disappear after all the nodes of the network are upgraded to Cisco ONS Release 8.5.

•When upgrading the software from Cisco ONS Release 8.0 to Cisco ONS Release 8.5, the PMI, FDI and APC-CORR-SKIP alarms are raised. These alarms disappear after all the nodes of the network are upgraded to Cisco ONS Release 8.5.

This issue has been resolved.

CSCsl57383

The OPWR_LFAIL and OPWR_HFAIL alarms do not properly correlate the downstream alarms when when MPO connected to the ADD port is removed from the ADD circuit passing through WXC card. This issue has been resolved.

CSCsm00488

SYNCLOSS alarm is raised for a long time on a Y-cable switch when switching back to working card after WTR alarm is cleared for MXP-MR-10DME cards. This issue has been resolved.

CSCsm12542

LOS-P alarm is reported in Critical severity on Y-cable protected MXP-MR-10DME card even when it is in standby mode. This issue has been resolved.

CSCsm27602

On a G1000 port, changing status from unlocked to locked to disabled to unlocked may cause loss in traffic. The workaround is to change the port state to locked-maintenance and then apply a facility loopback to restore traffic. Change the port state to unlocked to bring up the traffic. This issue has been resolved.

CSCsm38947

False LO-RXPOWER alarm is raised on client port of TXP-MR-2.5G card when the card is up and operational for a long time. This issue has been resolved.

Cross-Connect Cards

CSCso92212

A software upgrade to a 8.x release causes low order VC12/VC11 circuits to go into unlocked-disabled,failed state and the AIS-V alarm is raised even though traffic is fine on those circuits. This issue has been resolved.

CTC

This section documents resolved CTC caveats in Release 8.5.2.

CSCsk83405

Performing a retrieval of OSPF diagnostic information from the CTC network raises the OSPF Hello Fail alarm and the controller card is locked. This issue has been resolved.

CSCso08712

A VCAT member cannot be put in a locked,outOfGroup state in an open VCAT circuit. This issue has been resolved.

CSCsm85843

The Circuit tab in CTC displays the VCn circuit in the ROLL_PENDING state when a Bridge and Roll is performed under the following conditions:

1. Start a Bridge and Roll on a VCn circuit that is on the only circuit bearing port on a MRC card or a fixed rate card.

2. During a manual Bridge and Roll, perform the COMPLETE step but not the FINISH step.

3. Delete the fixed rate card or the port or PPM on the MRC card.

The Roll object still exists on the node even though the parent object is deleted and hence there is no pool for the rollFrom Path field in the Roll Object database. The Circuit tab in CTC will display the circuit in the ROLL_PENDING state and the Roll tab will not have an entry to finish the roll. The workaround is to complete all the steps of the ROLL process including the FINISH step. This issue has been resolved.

Data I/O Cards

CSCsm07215

Unconfiguring the port-channel using the CLI command no int port-i port-channel no causes the ML-MR-10 card to crash. This issue has been resolved.

CSCsm12390

When a member of a Link Capacity Adjustment Scheme (LCAS) Virtual Concatenation Group (VCG) member has signal fail (SF) or signal degrade (SD) conditions, no LCAS VCG alarms are raised on CE-MR cards. The LCAS VCG member continues to carry traffic. This issue has been resolved.

CSCsm80622

For POS ports on CE-MR-10 cards, in the GFP mode, it is not possible to provision FCS to NONE. For GFP POS ports, FCS is always set to 32-bits. This issue has been resolved.

CSCsm84897

Packet loss is seen on ML-MR-10 and CE-MR-10 cards at high data rates. This issue has been resolved.

CSCso22506

In Releases 8.5.0 and 8.5.1 it was possible to provision the FCS to NONE for POS ports using GFP framing on CE-MR-10 cards but the provisioned setting does not work as the card always appends a 4 byte GFP payload FCS. This issue has been resolved.

CSCso24872

If you have two VC3 CCAT/CCAT or CCAT/VCAT circuits between two CE-MR cards, deletion of either one of the circuits in CCAT/CCAT combination or deletion of the VCAT circuit in CCAT/VCAT combination causes a PLM alarm to be raised on the existing circuit. This issue has been resolved.

CSCso59494

If a CE-MR card is reset, traffic flows momentarily on LCAS members with SF or SD condition, after the card comes up. This issue has been resolved.

CSCso84751

After XC soft resets on CE-MR-10 cards, LCAS members may remain in a LCAS RX DNU alarm state. This issue has been resolved.

DWDM

This section documents resolved DWDM caveats in Release 8.5.2.

CSCsk50250

When the software is upgraded from Cisco ONS Release 7.0.1 to Cisco ONS Release 8.0, the West terminals are converted to A terminals and East terminals are converted to B terminals. When the B terminal is viewed after the upgrade, the APC screen (Maintenance > DWDM > APC) for the B terminals is blank. The workaround is to refresh/reload software on side B. This issue has been resolved.

CSCsl28270

Traffic outage occurs when Squelch is enabled on copper Small Form-Factor Pluggables (SFPs). This issue has been resolved.

CSCsl32370

When optical mesh network with Optical Transport Section (OTS) PPC is provisioned on the multi degree node, the alternative optical channel path is not calculated using the side constraints within the OCHNC circuit provisioning wizard. This issue has been resolved.

CSCsm50360

Single bit error events are generated by MXP_MR_10DME cards in the egress direction. The cards are configured in the 4G FC mode. This issue has been resolved.

CSCsm59936

Non-DWDM node type cannot be configured for a shelf where the OPT-AMP-C card is used. This issue has been resolved.

CSCsm64065

The Pause resolution algorithm on CE-MR card for 1000BaseX ports is not correct. Workaround is to disable the flow control on CE-MR card if the partner interface does not support symmetric flow control. This issue has been resolved.

CSCsm70709

Importing card parameters into CTC before configuring the pluggable port modules causes error. This issue has been resolved.

CSCsm76171

New circuits cannot be created on an OADM node with 2 or more AD-xC cards connected on the same side of the node. This issue has been resolved.

CSCsm82513

Far End Laser Control (FELC) is supported on copper SFP in the current release for GE_XP cards.

CSCso33395

When CTC imports a XML file from CTP, it displays a warning message if the versions are different. This issue has been resolved.

CSCso17376

Packet loss is seen in MXP_MR_10DME cards after upgrade and hard reset under the following conditions:

•The cards have an E-E configuration with MDS 9513 switches

•The MDS switches are connected to single mode 4G FC ports

•Distance extension is enabled on the cards

This issue has been resolved.

CSCso73537

Traffic hit is observed for more than 24 seconds for FICON2G during a software reboot or upgrade of the MXP-MR-2.5G card. This issue has been resolved.

Electrical I/O Cards

CSCsm64608

Equipment failure on E1-42 cards due to faulty DJA check. This issue has been resolved.

Hardware

This section documents resolved Hardware caveats in Release 8.5.2.

CSCsk48116

The traffic on CE-MR card is dropped when a loopback is applied on any member of the link capacity adjustment scheme (LCAS) circuit. Applying loopback potentially affects other members of the LCAS circuit as the differential delay threshold changes. This change in differential delay causes other members in the LCAS circuit to exceed the differential delay threshold raising the VCG-LOA alarm. The workaround is to assign locked,outofGroup state for any member of LCAS circuit before applying loopback. This issue has been resolved.

CSCsl26125

The 40-DMX unit can lower the channel TX power upon provisioning of a new optical circuit. This problem is created by the counter-propagating light reaching the VOA module on the COM-RX port in case of wrong cabling the DWDM source with the 40-DMX unit. This additional optical power results in the VOA to increase its attenuation and the power of the already provisioned circuits to be reduced. This issue has been resolved.

CSCsl92447

The traffic in a split fiber circuit is dropped when the trunk port is shut down either by pulling the trunk port fiber or setting the admin state as locked,disabled, and performing a soft reset on ML-MR card or hard reset on CE-MR-10 card. This issue has been resolved.

Maintenance and Administration

Caution VxWorks is intended for qualified Cisco personnel only. Use of VxWorks by customers is not recommended, nor is it supported by Cisco's Technical Assistance Center. Inappropriate use of VxWorks commands can have a negative and service-affecting impact on your network. Please consult the troubleshooting guide for your release and platform for appropriate troubleshooting procedures. To exit without logging in, enter a Control-D (hold down 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 Planner (CTC) does not support adding or creating more than 5 circuits in auto-ranged provisioning. This is as designed.

Note In releases prior to Cisco ONS Release 4.6 you could independently set proxy server gateway settings; however, with Cisco ONS Release 4.6.x and forward, 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 on an upgrade 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).

CSCsb88234

When a card is provisioned and a filler card is plugged in, a DBCHG with ENT-EQPT is sent, but when a filler card is plugged in without a prior provision there is no plug-in message. Similarly, there is no message upon removal of the filler card. The workaround for TL1 is to issue an inventory call and the filler card appears. For Cisco Transport Controller, the card is displayed and removed when the card is removed. This issue has been resolved.

CSCsg32263

When DBCHG messages are turned on by using the ALW-MSG-ALL command, there is no DBCHG message when creating and then deleting a proxy firewall tunnel. This issue has been resolved.

CSCsg43777

The number of rows added is inconsistent when a non-integer value is entered in the Add Rows field for the VLAN DB profile pane. This issue has been resolved.

CSCsg42366

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

To prevent traffic outage, follow the procedure for the 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 Manual FPGA upgrade. The upgrade should be hitless since traffic is accommodated on the Working facilities.

5. Once the card has completed SW reset, move back 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 Manual FPGA upgrade. The upgrade should be hitless since traffic is accommodated on the Protect facilities.

9. Once the card has completed SW reset, move back 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 Working facilities. Less than 50 ms hits are expected. The operation will keep traffic on Protect facilities if the protection group is non-revertive, hitless.

This issue has been resolved.

CSCdy57891

An LOP-P alarm can be inadvertently cleared by an LOS that is raised and cleared. On older STM-N cards, when an LOP condition and an LOS condition are both present on the input, an LOS will be raised. However, upon clearing the LOS with the LOP still present, the LOP alarm is not raised. An AIS-P condition will be visible. This issue has been resolved.

CSCsj42162

Packets are corrupted with CRC errors and traffic is lost when the source Ethernet signal is dropped and applied again on a chain of MXP-MR-10DME cards. This issue has been resolved.

CSCsj82440

When the ANS parameter is launched with default patchcords to regulate the ports, the 40MUX COM-TX port status is not shown correctly in the WDM-ANS->Port Status panel. Resetting the timing communication and control (TCC) card displays the 40MUX COM-TX port status correctly. This issue has been resolved.

CSCsj85066

When creating or adding members to a new Low Order (LO) circuit on an VCn and VC12 index that has not previously carried LO traffic (since the TCC card was last rebooted), some of the VC12 members' state is not displayed correctly. This issue has been resolved.

CSCsk95390

The database will get corrupted when a few among multiple VC circuits are rolled into same slot or VC-4. The rest of the VC circuits cannot be rolled into single slot/VC-4. This issue has been resolved.

CSCsl04148

When retrieving power values on Cisco Transport Controller and TL1, the LINE-TX and LINE-RX power values related to OSC-CSM card are not retrieved. This issue has been resolved.

CSCsl22077

The rxTotalPkts and txTotalPkts does not increment when jumbo frames (packets of more than 1522 bytes) with MTU setting of 9700 is sent through the circuit. This issue has been resolved.

CSCsl39888

Upgrading or downgrading the software from Cisco ONS Release 7.0.5 to Cisco ONS Release 7.0.7 or vice-versa causes errors on some of the ports or Y-cable protected MXP-MR-10DME card is loaded with all copper SFPs. This issue has been resolved.

CSCsl85419

Cisco Transport Controller and TL1 does not report standing alarms on MS-ISC-100T card when MS-ISC-100T cards are interconnecting multiple shelves in a multishelf node as part of a SMTP ring. This issue has been resolved.

CSCsm02122

Traffic is affected when the software is upgraded to Cisco ONS Release 8.5.1 on MXP-MR-10DME card with eight copper SFPs. This issue has been resolved.

CSCsm02773

LOS alarm on the OPT-BST card LINE-RX port is not correlated in DirLess node when a Mesh-X (4/8) node is connected to DirLess node. This issue has been resolved.

•when defects such as LOS, LOF, AIS-L are raised that cause multiple low order path protection paths to switch

This issue has been resolved.

CSCsl52122

Revertive path protection circuit may not switch to protected path during activation when the path protection selector does not detect the working path as Active even if that path has errors. This issue has been resolved.

SNCP

This section documents resolved SNCP caveats in Release 8.5.2.

CSCsl52122

During activation, the revertive SNCP circuit may not switch to the protect path even though the working path contains errors. This issue has been resolved.

SNMP

This section documents resolved SNMP caveats in Release 8.5.2.

CSCso22135

The Node may reboot when the snmpwalk command is executed on entPhysicalDescr, cerentEnvMonVoltage. This issue has been resolved.

to switch to the protect path even though the working path contains errors. This issue has been resolved.

CSCso60529

On ONS 15454 MSTP in multi-shelf configuration, snmpwalk on entPhysicalChildIndex goes into a loop. This issue has been resolved.

TL1

This section documents resolved TL1 caveats in Release 8.5.2.

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.

CSCsm34460

The ENT-EQPT::SLOT-14&SLOT-16:81::DS3:PROTID=SLOT-15,PRTYPE=1-N,CMDMDE=FRCD; TL1 command returns wrong response. This issue has been resolved.

New Features and Functionality

This section documents new software features for Release 8.5.2.

New Supported Rate for ONS-XC-10G-L2

A new rate is available for ONS-XC-10G-L2= XFP. It is possible to configure a 10GE-BASE ZR client rate when a ONS-XC-10G-L2= is inserted on Cisco 15454-10E-L1-C. It is mandatory to use the 10-2194-02 version of ONS-XC-10G-L2=.

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:

Subscribe to the What's New in Cisco Product Documentationas 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.

All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0805R)