 Feedback
|
Table Of Contents
Release Notes for Cisco ONS 15454 SDH
Release 8.6.1CSCef63240— LP TIM alarm displays its severity as NR instead of MJ in CTC
CSCsl88037— Improper removal alarm is not consistent on slot 24
CSCtd60987—RFI-V alarm does not clear on ONS 15454 NEs in the CTM
Common Control and Cross-Connect Cards
CSCec82148— Traffic hits occur on TCC2/TCC2P card removal
CSCso54993 —SF-V condition is not detected on VC12-nv circuits
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
CSCtg86988 —GFP-CSF alarm is cleared after hard reset of CE-MR-10 card
CSCsx49926—Egress WRR scheduling does not work for frames > ~1500 on GE_XP card
CSCsg10008—Y-cable protection switch time higher than 50 ms in GE_XP and 10GE_XP cards
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
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
CSCsc60472—CTC is not able to discover TL1 OCHCC circuit provisioned over ITU-T line card
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
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
CSCsz38549—40-WXC Channels do not restart correctly after card replacement
Linear Multiplex Section Protection
Maintenance and Administration
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
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
CSCdv53427— Protection vulnerabilities in two-ring, two-fibre MS-SP ring configuration
CSCdu82934—Failure of VC low-order path circuit creation
CSCin29274—Same static route on two interfaces fails
CSCee17695—STM1-8 card fails to read MFG EEPROM and shows MEA in CTC
CSCsc41650 —Node reboots during DS3XM card pre-provisioning
Resolved Caveats for Release 8.6.1
CSCsu40460—External remote alarm relay is not set correctly
CSCsq60390—Memory leak issue in alarm agent code
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
CSCsm09809—De-selecting the "LI Timer disable" gives an error message
CSCtd71846—VC12 circuits cannot be created through CTC
CSCtb72815—DNU does not clear on CE-MR and ML-MR 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
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
CSCsq16464 —Traffic on nodes duplicates on ML-series cards
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
CSCsu06528—GE_XP and 10GE_XP Trail Trace receive incorrect message
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
CSCsq46283—Packet loss on MXP-MR-10DME cards provisioned with 4G or 4G FICON
CSCsq33614 —Hard reset of MXP-MR-10DME and MXP-2.5G-10E cards raises IMPROPRVML alarm
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
CSCsu31027—J1 path trace does not work for E3 and DS3I from port 5 onward
Linear Multiplex Section Protection
CSCsr91312— Traffic hit of more than 2 seconds on upgrade when UPSR is active on protect
Maintenance and Administration
CSCsg16500—ROLL-PEND condition seen for VC low-order path circuits on CTC conditions pane
CSCsu10564—DCN-EXT: OTS PPC problem with OSPF enabled on LAN
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
CSCsv54817—VC4-32c circuits do not work with STM64 XFP cards
New Features and Functionality
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.1
OL-22857-01July 2010
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.1, 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.1
Cisco ONS 15454 SDH Release 8.6.1 does not include any new features. Cisco ONS 15454 SDH Release 8.6.1 is based on Cisco ONS 15454 SDH Release 8.6. The Release Notes for Cisco ONS 15454 SDH Release 8.6.1 contain closed (maintenance) issues and caveats found in Cisco ONS 15454 SDH Release 8.6. For detailed information on bugs fixed refer to the respective sections in this document.
Contents
Resolved Caveats for Release 8.6.1
New Features and Functionality
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.1 since the production of the Cisco ONS 15454 SDH System Software CD for Release 8.6.1.
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.1.
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.
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. This issue will not be resolved.
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.
•
•
•
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.
CSCtd60987—RFI-V alarm does not clear on ONS 15454 NEs in the CTM
In Software Release 8.6.1, the RFI-V alarm does not clear on ONS 15454 NEs in the Cisco Transport Manager (CTM). The workaround is to modify the severity of the RFI-V of the logical objects VT-MON and VT-TERM in the alarm profile to the same value as a customized severity. After changing the MON and TERM severity to the same value the RFI-V alarm is cleared in the CTM/CTC. This issue will not be resolved.
Common Control and Cross-Connect Cards
This section documents caveats for Common Control and Cross-Connect Cards in Release 8.6.1.
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.
Data I/O Cards
This section documents caveats for Data I/O Cards in Release 8.6.1.
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:
•
•
•
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 not be resolved.
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.
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 not be resolved.
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.
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 not be resolved.
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:
•
•
No workaround is available for this issue. This issue will not be resolved.
CSCtg86988 —GFP-CSF alarm is cleared after hard reset of CE-MR-10 card
Traffic is hit when the GFP-CSF alarm is cleared after the hard reset of CE-MR-10, CE-MR-6, or ML-MR-10 cards. This issue will be resolved in a future release.
DWDM
This section documents caveats for DWDM in Release 8.6.1.
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 not be resolved.
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:
•
•
•
•
No workaround is available for this issue. This issue will not be resolved.
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 not be resolved.
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 not be resolved.
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 not be resolved.
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.
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.
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.
Electrical I/O Cards
This section documents caveats for Electrical Cards in Release 8.6.1.
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.
Hardware
This section documents caveats for Hardware in Release 8.6.1.
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. This issue will not be resolved.
CSCsz38549—40-WXC Channels do not restart correctly after card replacement
Channel(s) added through the WSS mux unit reports a "VOA fail" alarm on the CHAN-RX port of the 40-WXC card. The 40-WX-C card does not start-up due to low power received from the WSS unit. The workaround is to increase the power coming from WSS unit through "VOA power Calib" field. Change the power value from 0 to +3. Then change the OCH-NC/CC circuit status to the OOS state and again revert to the IS state to restart the variable optical attenuator (VOA).
This issue will be resolved in a future release.
Linear Multiplex Section Protection
This section documents caveats for Linear Multiplex Section Protection in Release 8.6.1.
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.1.
Caution
Note
Note
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. This issue will not be resolved.
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.
2.
3.
4.
UNEQ-P alarms clear and connection states remain in unlocked-disabled,failed. No workaround is available for this issue. This issue will not be resolved.
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 not be resolved.
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.
–
–
–
–
2.
3.
4.
5.
6.
7.
8.
9.
10.
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.1.
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.1.
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.
Optical I/O Cards
This section documents caveats for Optical I/O Cards in Release 8.6.1.
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.
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.
TL1
This section documents caveats for TL1 in Release 8.6.1
Note
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.1
This section documents caveats resolved in Release 8.6.1.
Alarms
This section documents resolved caveats for Alarms in Release 8.6.1.
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.
2.
3.
This issue has been resolved.
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.
2.
The workaround for this condition is as follows:
1.
2.
Before deleting the protection, make sure that you have switched the traffic that uses this entire 1+1 setup.
Condition 2:
1.
2.
The two workarounds for this condition are as follows:
1.
2.
This issue has been resolved.
CTC
This section documents resolved caveats for CTC in Release 8.6.1.
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.
This issue has been resolved.
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:
•
This issue has been resolved.
CSCsq73116—PPC does not work on secure mode node
PPC does not work on a secure mode node under the following condition:
•
This issue has been resolved.
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.
2.
This issue has been resolved.
CSCsq88986—Filler card prevents enabling MSTP multishelf
Cannot enable MSTP multishelf under the following condition:
•
The workaround is to perform the following steps in the specified order.
1.
2.
3.
This issue has been resolved.
CSCsm09809—De-selecting the "LI Timer disable" gives an error message
When you de-select the "LI Timer disable" check box and click Apply, an error message pops-up. This issue has been resolved.
CSCtd71846—VC12 circuits cannot be created through CTC
On CE-100 cards, VC12 circuits cannot be created through CTC, even if the bandwidth is available, and the following error message is displayed:
"EID-2055 No endpoints are available for this selection. Please make another selection".
This issue has been resolved.
Data I/O Cards
This section documents resolved caveats for Data I/O Cards in Release 8.6.1.
CSCtb72815—DNU does not clear on CE-MR and ML-MR cards
For CE-MR-10 and ML-MR-10 cards, when the network round-trip latency is more than 80 ms, DoNotUse (DNU) does not clear after SONET defects are cleared on the HW-LCAS members. This issue has been resolved.
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.
2.
3.
4.
5.
Note
This issue has been resolved.
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.
2.
This issue has been resolved.
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.
2.
3.
4.
This issue has been resolved.
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:
•
This issue has been resolved.
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. This issue has been resolved.
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:
•
This issue has been resolved.
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:
•
This issue has been resolved.
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. This issue has been resolved.
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. This issue has been resolved.
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. This issue has been resolved.
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. This issue has been resolved.
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. This issue has been resolved.
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. This issue has been 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:
•
•
This issue has been resolved.
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. This issue has been resolved.
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.
2.
3.
This issue has been resolved.
DWDM
This section documents resolved caveats for DWDM in Release 8.6.1.
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.
2.
3.
4.
This issue has been resolved.
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. This issue has been resolved.
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.
2.
This issue has been resolved.
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.
2.
This issue has been resolved.
CSCsr60270—Upgrade issues in GE_XP/10GE_XP cards
The following issues are noticed:
•
If a copper SFP has a link flap (cable disconnect or autoneg restart) the link will come up but traffic will not flow.
•
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
•
When there is a sequence of add and delete selective operations followed by a reset, new selective operations might not work after reset.
•
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.
This issue has been resolved.
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:
–
–
Copper PPMs with CRC issues that were already installed before the software upgrade will again drop packets.
This issue has been resolved.
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.
2.
3.
4.
5.
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:
•
•
This issue occurs under the following conditions:
1.
2.
This issue has been resolved.
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:
•
This issue has been resolved.
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.
This issue has been 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. This issue has been 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. This issue has been resolved.
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. This issue has been resolved.
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. This issue has been resolved.
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. This issue has been resolved.
Electrical I/O Cards
This section documents resolved caveats for Electrical Cards in Release 8.6.1.
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.
2.
This issue has been resolved.
Linear Multiplex Section Protection
This section documents resolved caveats for Linear Multiplex Section Protection in Release 8.6.1.
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.
2.
3.
4.
5.
This issue has been resolved.
Maintenance and Administration
This section documents resolved caveats for Maintenance and Administration in Release 8.6.1.
Caution
Note
Note
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.
2.
3.
4.
This issue has been resolved.
NCP
This section documents NCP resolved caveats for Release 8.6.1.
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.
2.
This issue has been resolved.
Optical I/O Cards
This section documents resolved caveats for Optical I/O Cards in Release 8.6.1.
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.
2.
3.
4.
This issue has been resolved.
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.
2.
This issue has been 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.
2.
Note
This issue has been 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.
2.
3.
4.
This issue has been resolved.
New Features and Functionality
No new software features are included in Release 8.6.1.
Related Documentation
This section lists release-specific and platform-specific documents.
Release-Specific Documents
•
•
•
•
•
•
Platform-Specific Documents
Cisco ONS 15454 Release 8.6.1 is based on Cisco ONS 15454 Release 8.6.
•
Provides installation, turn up, test, and maintenance procedures•
Provides technical reference information for SONET/SDH cards, nodes, and networks•
Provides technical reference information for DWDM cards, nodes, and networks•
Provides a list of SDH alarms and troubleshooting procedures, general troubleshooting information, transient conditions, and error messages•
Provides a comprehensive list of TL1 commands•
Provides general information, procedures, and errors for TL1•
Provides software feature and operation information for Ethernet cards•
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.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned 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. (1005R)
© 2010 Cisco Systems, Inc. All rights reserved.
