Release Notes for Cisco ONS 15454, Release 8.6.1
Available Languages
Table Of Contents
Release Notes for Cisco ONS 15454
Release 8.6.1CSCsl18519 —One CARLOSS and TPTFAIL alarm reported with dual failure on ports of CE-MR-10 card
CSCsm16960 —AUTO RESET alarm cleared before activation
CSCsm19928 —AS-MT condition not persistent against subtended shelf TCC software reset
CSCsm32308— Roll-pend(NA) and UNEQ-P(CR) alarms move to Conditions pane on soft reset of active TCC
CSCtd11068—CE-100T-8 card link is down with no alarms
CSCta72945—SWMTXMOD Alarm on MRC Cards
CSCsy69110—ADD Port Alarm not Raised
CSCtd60987—RFI-V alarm does not clear on ONS 15454 NEs in the CTM
CSCtf22211—Bridge and Roll valid signal is inconsistent
CSCdv53427— Protection vulnerabilities in two-ring, two-fiber MS-SP ring configuration
CSCsz39798—Constant TCC Reboot
CSCsy82228—CTC Network discovery is slow
CSCtb81645—CE-MR STS pool allocation is incorrect in CTC
CSCtc46543—CTC circuit creation wizard window hangs during OCHNC circuit creation
CTC Release 8.5.x unable to manually route STS1 from DS3 to DS3XM-12 card
CSCtg96470—BITS-OUT clock is not in sync with the incoming clock
CSCta95590—Provisioning strip sends wrong BPDU configuration for NNI ports
CSCtg92049—Incorrect pool allocation on CE100T-8 Card
CSCsq24903 —First data frame sent on POS circuit is lost on CE-MR-10 card
CSCte67178—Link does not recover between CE-1000 and Sycamore cards
CSCsq20532—Traffic hit of 25 ms occurs in a low-order LCAS circuit
CSCsy16814—Traffic drop is observed when port state is changed from OOS-DSBLD to IS
CSCtc44604—First 32 DCC Area IDs are restored after the upgrade
CSCtg93566—IDLE does not clear on few HW-LCAS members
CSCsx49926—Egress WRR scheduling does not work for frames > ~1500 on GE_XP card
CSCsf04299 —WTR time does not trigger switch back of protection
CSCsm82422—CARLOSS alarm not raised when power is turned off on MXP-MR-10DME 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
CSCsg10008—Y-cable protection switch time higher than 50 ms in GE_XP and 10GE_XP cards
CSCse97200 —Local and Express order-wire circuits do not work on ADM-10G card
CSCei87554—IfInErrors counter does not report performance parameters
CSCee45443 —FICON bridge in the MXP-MR-2.5G card transitions to SERV MODE
CSCtb33916 —After an upgrade, traffic is discarded on a newly created VLAN
CSCtc54159—Traffic drops if CVLAN coincides between the range and single entry on different SVLAN
CSCsq13945— DS3-12 card does not boot up in release 8.0 and later
Maintenance and Administration
CSCse23518—RPR SPAN-MISMATCH alarm not reported correctly
CSCse53133—RTRV-COND-STS does not display path alarms on BLSR protect path
CSCsg10963—Connections remain in OOS-AU,FLT after roll is canceled
CSCse91968—AINS-to-IS transition on BLSR four-fiber Protect does not function properly
CSCsm04659—CTC does not report TL1 circuits when the software is upgraded to Releases 8.5.1 and 8.6
CSCsm08019— MXP-MR-10DME card carries traffic even if trunk port is in OOS,DSBLD state
CSCsm43960— Intermediate switch to protect occurs when TIM alarm is generated on MXPP-MR-2.5G card
CSCsm61886 —Less accuracy of the Link Integrity timer on CE-MR-10 card
CSCsg42366—Traffic outage occurs when FPGA upgrade is done with manual switch on Y-cable
CSCta11737—Soft reset of CE card places IS-AINS port to IS when soak timer is set to zero
CSCta87573—40-MUX-C card does not report CHAN-RX power when COM-TX port is not in IS or MT state
CSCdu82934—Failure of VT circuit creation
CSCin29274—Same static route on two interfaces fails
CSCta42253—MRC card remains in OOF state
CSCsy42909—SNMP trap do not display port/slot number correctly for OCHTERM-INC alarm
CSCsc41650 —Node reboots during DS3XM card pre-provisioning
CSCtf50729—TCC crashes when debug commands are executed
Resolved Caveats for Release 8.6.1
CSCsu40460—External remote alarm relay is not set correctly
CSCsm32278 —Alarms at GFP level on MXP-MR-10DME cards do not trigger FLT state on port
CSCsk20948—VT alarms with invalid aid is raised on XM12 ports
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
CSCsq88986—Filler card prevents enabling MSTP multishelf
CSCsv01621—It is not possible to enter in the WXC card panel
CSCsl76583—Select Affected Circuits does not work for PLM-P
CSCtf77988—NMS support to display input voltage and ambience temperature
CSCsy86915—Extra STS is utilized in the first VT cross connect created on an STS
CSCtd46366—Cross-connect loopback on monitor circuit affects the traffic of the original circuit
CSCsm09512—Packet drop and VCG-DEG condition observed after hard reset of CE-MR-10 card
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
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 VT-1.5 LCAS circuits are in idle state
CSCsr67830—High traffic hit seen with larger HW-LCAS circuits with fiber pull
CSCsr06085—Error message on CPU switching packets greater than 1500 bytes in length
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
CSCsq20532—Traffic hit of 25 ms occurs in a low-order LCAS circuit
CSCsq52786—Link Integrity does not work for HW-LCAS circuits
CSCsq55568—High traffic hit while upgrading from pre 9.00 load on CE-MR-10, CE-MR-6 cards
CSCsq77755—UNEQ alarmed HW-LCAS member will go into In-Group when CTX or XC card is reset
CSCsr41260—RPR convergence time is more than expected (50 ms) in ML-100X
CSCsr78331—Cannot create a STS-1-2v or a STS1 circuit on the CE-100 card
CSCtc66943—Link does not come up when autonegotiation is enabled
CSCtf10958—Path PMs are displayed for CE-MR/ML-MR Cards
CSCse74833—GFP-CSF is not detected by CE-MR-10 and ML-MR-10 cards
CSCso73947—E port is down after MXP-MR-10DME card power up
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
CSCsq33614 —Hard reset of MXP-MR-10DME and MXP-2.5G-10E cards raises IMPROPRVML alarm
CSCsq46283— Packet loss on MXP-MR-10DME cards provisioned with 4G or 4G FICON
CSCsl70268 —Severity is not cleared when the raised alarm is cleared
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
CSCsq48070 —Standby TCC crashes during database restore
CSCsq58173—TCC reboots when configuring DS3XM12 or mixed 1:1 or 1:N PG
CSCsu20391—FE-AIS and RAI alarms are incorrectly reported
CSCsu39177—After deletion of VT circuit and creation of STS-1 circuit, there is traffic loss
CSCsu47448—For DS1 FEAC, loopcode in DS3 framing FAC is inserted on odd DS1 ports
CSCtb74439—DS3XM cards insert VT-AIS downstream
Maintenance and Administration
CSCsg16500—ROLL-PEND condition seen for VT circuits on CTC conditions pane
CSCsl76684—Delay in AIC-I card becoming active
CSCsm25619 —Traffic is not restored after card reset
CSCtd42075—Upgrade of DS3XM-6 card to DS3XM-12 card leaves first 6 ports of DS1's Unframed
CSCsu10564—DCN-EXT: OTS PPC problem with OSPF enabled on LAN
CSCsr76682—Bit errors observed on OC192XFP after both XC cards reboots
CSCsv54817—STS-96c circuits do not work with OC192XFP cards
CSCsl87931— ALS condition permanently lost when manual restart is performed
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
Release 8.6.1
OL-22856-01July 2010
Release notes address closed (maintenance) issues, caveats, and new features for the Cisco ONS 15454 SONET platform. 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 Procedure Guide; Release 8.5.x version of the Cisco ONS 15454 Reference Manual; Release 8.5.x version of the Cisco ONS 15454 Troubleshooting Guide; and Release 8.5.x version of the Cisco ONS 15454 SONET TL1 Command Guide. For the most current version of the Release Notes for Cisco ONS 15454 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 Release 8.6.1 does not include any new features.
Cisco ONS 15454 Release 8.6.1 is based on Cisco ONS 15454 Release 8.6. The Release Notes for Cisco ONS 15454 Release 8.6.1 contain closed (maintenance) issues and caveats found in Cisco ONS 15454 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 Release 8.6.1 since the production of the Cisco ONS 15454 System Software CD for Release 8.6.1.
Caveats
Review the notes listed below before deploying the 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.
CSCsl18519 —One CARLOSS and TPTFAIL alarm reported with dual failure on ports of CE-MR-10 card
When dual failure occurs on the ports of the CE-MR-10 card equipped with electrical small form-factor pluggables (SFPs), only one CARLOSS and TPTFAIL alarm is reported. No workaround is available for this issue.This issue will not be resolved.
CSCsm16960 —AUTO RESET alarm cleared before activation
When upgrading software on OC-12 4-port cards from Release 7.0.7 to Release 8.6.1, the AUTO RESET alarm is cleared before completing activation. No workaround is available for this issue. This issue will not be resolved.
CSCsm19928 —AS-MT condition not persistent against subtended shelf TCC software reset
An AS-MT alarm on the transponder (TXP) card in a subtended shelf of a multishelf configuration is cleared when a soft reset of the TCC is performed. The workaround is to change the port status to IS-AINS and OOS-MT. This issue will be resolved in a future release.
CSCsm32308— Roll-pend(NA) and UNEQ-P(CR) alarms move to Conditions pane on soft reset of active TCC
Roll-pend(NA) and UNEQ-P(CR) alarms move to the Conditions pane when a soft reset is performed on an active TCC during the manual mode of a circuit roll. No workaround is available for this issue. This issue will be resolved in a future release.
CSCtd11068—CE-100T-8 card link is down with no alarms
When selective auto-negotiation is enabled on the CE-100T-8 card, and if there is a mismatch in speed and duplex at the physical interface, the link is down but no alarm is raised. This issue will be resolved in a future release.
CSCta72945—SWMTXMOD Alarm on MRC Cards
Frequent and continuous side switching of the XC-VT cards result in SWMTXMOD alarm on the MRC cards. This issue will be resolved in a future release.
CSCsy69110—ADD Port Alarm not Raised
Add Port alarm is not raised on ports 27 and 23 of 40-WSS card when the 40-WSS card is inserted in slot 3 of an SDH shelf. 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.
CSCtf22211—Bridge and Roll valid signal is inconsistent
Bridge and Roll valid signal is inconsistent when there are VT circuits and cross-connects created between the nodes being rolled. The workaround is to create the circuits using DCC. This issue will be resolved in a future release.
BLSR Functionality
This section documents caveats for bidirectional line switched ring (BLSR) in Release 8.6.1.
CSCdv53427— Protection vulnerabilities in two-ring, two-fiber MS-SP ring configuration
In a two-ring, two-fiber BLSR configuration (or in a two-ring BLSR 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 both broken.
Common Control Cards
This section documents caveats for Common Control Cards in Release 8.6.1.
CSCsy91761—Constant TCC Reset
When a node with DS3XM-12 having multiple portless DS3s in the terminal loopback is upgraded, there is constant TCC reset after activation and the upgrade fails. This issue will be resolved in a future release.
CSCsz39798—Constant TCC Reboot
When the DS3XM12 or DS3XM6 port transitions from the AINS state to IS state, TCC reboots constantly. This issue will be resolved in a future release
CTC
This section documents caveats for CTC in Release 8.6.1.
CSCsy14945—CTC cannot manage either nodes of the same version of higher maintenance version, than its core version
CTC cannot manage either nodes of the same version of higher maintenance version, than its core version. Specifically the nodes are not accessible by CTC. The workaround is to upgrade the CTC core version or manually clean the CTC jar cache and then ensure no nodes of the specified version above are encountered. This issue will be resolved in a future release.
CSCsy82228—CTC Network discovery is slow
CTC Network discovery is very slow when it is disabled and NEs are added one at a time. This issue will be resolved in a future release.
CSCtb81645—CE-MR STS pool allocation is incorrect in CTC
Pool numbers are displayed incorrectly in the Cardview->Maintenance->STS/VT allocation tab when STS, STS_Vcat, or VT_Vcat circuits are created in different pools of CE-MR card. This issue will be resolved in a future release.
CSCtc46543—CTC circuit creation wizard window hangs during OCHNC circuit creation
The circuit creation window hangs when the creation process is canceled within the route pane. This problem occurs in a big network with a very high latency due to lack of high speed DCN. This issue will be resolved in a future release.
CTC Release 8.5.x unable to manually route STS1 from DS3 to DS3XM-12 card
CTC Release 8.5.x does not allow a manual routed circuit (STS1) from a DS3 to a DS3XM-12 card. The circuit creation chooses the automatic routing option by default. The workaround is to load Release 9.x CTC cache files and launch CTC with the latest CTC version. This will allow the STS1 circuit to be built manually from DS3 to DS3XM-12 card. This issue will be resolved in a future release.
CSCtg96470—BITS-OUT clock is not in sync with the incoming clock
The BITS-OUT clock is not in sync with the incoming clock on OSCM for E1 facility when the framing type is FAS+CAS+CRC or FAS+CRC. The workaround is to:
1.
Change the framing type to UNFRAMED.
2.
3.
This issue will be resolved in a future release.
CSCta95590—Provisioning strip sends wrong BPDU configuration for NNI ports
When a UNI port is changed to NNI port, the BPDU configuration parameter is not updated. The workaround is to:
1.
2.
3.
4.
This issue will be resolved in a future release.
CSCtg92049—Incorrect pool allocation on CE100T-8 Card
The pool allocation is incorrect when a VC3-CCAT circuit is created on the CE100T-8 card. The workaround is to create a VC3-VCAT circuit instead of VC3-CCAT circuit. This issue will be resolved in a future release.
Data I/O Cards
This section documents caveats for Data I/O Cards in Release 8.6.1.
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.
CSCsq24903 —First data frame sent on POS circuit is lost on CE-MR-10 card
On CE-MR-10 cards, the first data frame that is sent on a POS circuit is lost under the following conditions:
For a new provisioned POS circuit
If the data frame is large
No workaround is available for this issue. This issue will not be resolved.
CSCte67178—Link does not recover between CE-1000 and Sycamore cards
Link does not recover between the CE-1000 card and Sycamore 1 Gbps Ethernet card when the fibre is removed and restored again, with LI enabled. The workaround is to create a terminal loopback on the OC-192 port on the ONS 15454 node with the AIS flags disabled. If the Link Integrity Disable flag is selected, the circuit recovers correctly when the fiber is restored on the CE-1000 card.
CSCso94644—LCAS VCG Member Rx side in Add State condition persists after hard reset of CE-MR-10 card or ML-MR-10 card
The LCAS VCG Member Rx side in Add State condition might persist 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 fiber routing. The workaround is to place all the affected circuit members in the OOS,OOG state. After all the members have been placed in OOS,OOG state, place them back in IS state. This issue will not be resolved.
CSCsm78387—PDI-P alarm causes the Ethernet port to go down when members are deleted on open-ended HW-LCAS VCAT circuit
A path payload defect indication (PDI-P) alarm is raised and the Ethernet port goes down when members are deleted in a circuit under the following conditions:
•
•
•
These conditions result in an unbalanced virtual concatenation group (VCG). 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 OOG state on both ends. When members are being placed in IS, place them in IS state on both ends of the circuit. This issue will not be resolved.
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 OOS,OOG 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.
CSCsy16814—Traffic drop is observed when port state is changed from OOS-DSBLD to IS
Traffic drop is observed when the port state is changed from OOS-DSBLD to IS. The workaround is to perform IS->OOS-> IS transition until the problem is fixed. This issue will be resolved in a future release.
CSCtc44604—First 32 DCC Area IDs are restored after the upgrade
Only the first 32 data communications channel (DCC) area IDs are restored after an upgrade from an older software release to R9.0.1.
This issue will be resolved in a future release.
CSCtg93566—IDLE does not clear on few HW-LCAS members
IDLE does not clear on few HW-LCAS members when the path delay (propagation delay) is more than 400 ms and the active cross-connect is reset. The workaround is to change all the HW-LCAS members to OOS,OOG state before cross-connect reset and move HW-LCAS members back to IS state after cross-connect reset. Recover the affected members by transitioning the member state form IS > OOS,OOG > OOS,DSBLD and back to IS. 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.
CSCsg22669—Traffic hit greater than 50 ms but less than 60 ms on MXP-2.5G-10E in Y cable configuration with fiber cut
When a fiber 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.
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 OOS,DSBLD condition
When a port is placed in IS while the conditions necessary to squelch the port are present (for example, when the trunk port on a DWDM card is OOS,DSBLD and a client port is placed in IS), the client will momentarily enable, emitting light, before squelching due to the trunk OOS,DSBLD condition. The pulse is approximately 500 ms. 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 occurs downstream, the node receives OTUk-BDI. Because of the placement of dual OTN and SONET 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 Fiber 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 Fiber 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 Fiber 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.
CSCsg10008—Y-cable protection switch time higher than 50 ms in GE_XP and 10GE_XP cards
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.
CSCse97200 —Local and Express order-wire circuits do not work on ADM-10G card
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.
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.
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.
CSCsz94689—Incoming traffic received through any port on the affected card may flow to other Service Provider VLANs
Incoming traffic received through any port on the affected card may flow to other Service Provider VLANs (svlan) if the Customer VLAN (cvlan) ID on the incoming packet belongs to any VLAN range configured on the card. This issue may occur even if the packet is received via a Network to Network Interface (NNI) port. This issue will be resolved in a future release.
CSCtb33916 —After an upgrade, traffic is discarded on a newly created VLAN
The traffic does not flow in a newly created VLAN under the following conditions:
•
•
This issue will be resolved in a future release.
CSCtc54159—Traffic drops if CVLAN coincides between the range and single entry on different SVLAN
There is a drop in traffic when a VLAN range entry that is created on the UNI port coincides with an existing QinQ entry on the other ports. This issue will be resolved in a future release.
Electrical I/O Cards
This section documents caveats for Electrical I/O Cards in Release 8.6.1.
CSCsq13945— DS3-12 card does not boot up in release 8.0 and later
The DS3-12 card (part number 87-31-00001/800-06785-01) does not boot up in release 8.0 and later. The workaround is to use a later version of the card. This issue will not be resolved.
CSCsq98420—DS1 port state (under a DS3 port) moves to OOS,DSBLD state on deletion of first VT circuit
All DS1 ports (under a DS3 port) move to OOS,DSBLD state after the first VT circuit is deleted. This occurs under the following conditions:
1.
2.
3.
4.
5.
6.
7.
No workaround is available for this issue. However, this issue is resolved in Release 9.0.
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 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.
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 sent 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 crashes 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-STS does not display path alarms on BLSR protect path
RTRV-COND-STS does not display path alarms on a BLSR protect path. When the BLSR is switched onto 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 not be resolved.
CSCsg10963—Connections remain in OOS-AU,FLT after roll is canceled
Connections remain in OOS-AU,FLT state after roll is canceled. This issue occurs under the following conditions:
1.
2.
3.
4.
UNEQ-P alarms clear and connection states remain in OOS-AU,FLT. No workaround is available for this issue. This issue will not be resolved.
CSCse91968—AINS-to-IS transition on BLSR four-fiber Protect does not function properly
The AINS-to-IS transition on BLSR four-fiber Protect is not functioning properly. When a BLSR four-fiber ring is used, the AINS-to-IS transition is not correct when protect is active (ring switched). Sometimes the wrong protect is transitioning at the IO. If the TSC card is notified incorrectly, it becomes out of sync with the IO, and becomes stuck in AINS, even when the protect switch is released. The Cisco PCA is also being incorrectly notified of an AINS-to-IS transition. This issue will not be resolved.
CSCsm04659—CTC does not report TL1 circuits when the software is upgraded to Releases 8.5.1 and 8.6
Cisco Transport Controller does not report TL1 circuits when the software is upgraded to Releases 8.5.1 and 8.6. The workaround is to close and re-launch CTC. This issue will not be resolved.
CSCsm08019— MXP-MR-10DME card carries traffic even if trunk port is in OOS,DSBLD state
The MXP-MR-10DME card carries traffic even if the trunk port is in OOS,DSBLD state. No workaround is available for this issue. This issue will not be resolved.
CSCsm43960— Intermediate switch to protect occurs when TIM alarm is generated on MXPP-MR-2.5G card
An intermediate switch to protect occurs when a TIM alarm is generated on an MXPP-MR-2.5G card. No workaround is available for this issue. This issue will not be resolved.
CSCsm61886 —Less accuracy of the Link Integrity timer on CE-MR-10 card
The Link Integrity timer is less accurate on CE-MR-10 cards than on G1000-4 or CE1000-4 Ethernet cards. No workaround is available for this issue. This issue will be resolved in a future release.
CSCsg42366—Traffic outage occurs when FPGA upgrade is done with manual switch on Y-cable
A traffic outage of 120 seconds 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.
CSCta11737—Soft reset of CE card places IS-AINS port to IS when soak timer is set to zero
The CE Ethernet card with ports set in an IS-AINS state will incorrectly go to IS state when the SOAK timer is set to 00:00 and after the soft reset of the card. No workaround is available for this issue. This issue will be resolved in a future release.
CSCta87573—40-MUX-C card does not report CHAN-RX power when COM-TX port is not in IS or MT state
The 40-MUX-C optical card (with vendorID=1025) does not report the optical power value in the Provisioning->Optical Channel pane when the COM-TX port and the associated variable optical attenuator (VOA) are not ACTIVE. Due to this, the Raman Installation Wizard fails to tune the RAMAN span when the MUX or DEMUX option is selected, and a 40-MUX-C is used. The workaround is to move the COM-TX port of the 40MUX-C card to IS or MT state to display the CHAN-RX power. This issue will be resolved in a future release.
NCP
This section documents caveats for NCP in Release 8.6.1.
CSCdu82934—Failure of VT circuit creation
When you auto-route a VT circuit on an ONS 15454 node, a path is computed based on the availability of STSs on the nodes involved. This selection process, when combined with a lack of VT matrix (or STS-VT connections) on an auto-route selected node, can result in the failure of VT circuit creation and displays the following message,
Error Message Unable to create connection object at nodeTo correct this situation, manually route VT 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 VT/VC circuit creation on path protection
On the 15454-MRC-12 card, when a one-way VT/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 OOS. 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.
CSCta42253—MRC card remains in OOF state
MRC card remains in OOF state when OC-48 SFP is used in port 1. This issue will be resolved in a future release.
Path Protection
This section documents caveats for Path Protection in Release 8.6.1.
CSCee53579— Traffic hits occur in unprotected to path protection topology upgrade in unidirectional routing
Traffic hits can occur in an unprotected to path protection topology upgrade in unidirectional routing. You can create an unprotected circuit, then upgrade the circuit to a path protection circuit using the Unprotected to Path Protection wizard. Select unidirectional routing in the wizard, and the circuit will be upgraded to a path protection circuit. However, during the conversion, traffic hits of the order of 300 ms should be expected. This issue will not be resolved.
SNMP
This section documents caveats for SNMP in Release 8.6.1.
CSCsy42909—SNMP trap do not display port/slot number correctly for OCHTERM-INC alarm
The 15454 SNMP traps do not display the port and slot numbers correctly for the OCHTERM-INC alarm. The workaround is to check the port number in the TL1 AID part of the trap (example: LINE-1-2-RX). to determine port that has an alarm. This issue will be resolved in a future release.
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 not be resolved.
CSCtf50729—TCC crashes when debug commands are executed
The TCC crashes when debug commands are executed on a 15454 node where SNMP is configured. 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.
CSCsm32278 —Alarms at GFP level on MXP-MR-10DME cards do not trigger FLT state on port
Alarms at generic framing procedure (GFP) level on MXP-MR-10DME cards do not trigger an FLT state on the Virtual Facility (VFAC) port. This issue has been resolved.
CSCsk20948—VT alarms with invalid aid is raised on XM12 ports
When VT1.5 circuit is created on the ported ports of the DS3XM12 card, the VT alarms are reported with wrong AID's against the DS3XM12 card. This issue has been resolved.
CSCsq68460—LCAS-RX-FAIL and LCAS-RX-DNU alarms are not reported for AIS-V and LOP-V for MLMR and CEMR cards
LCAS-RX-FAIL and LCAS-RX-DNU alarms are not reported for AIS-V and LOP-V alarms but seen for other SONET alarms (such as UNEQ) under the following condition:
•
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.
CSCsq88986—Filler card prevents enabling MSTP multishelf
MSTP multishelf cannot be enabled 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.
CSCsl76583—Select Affected Circuits does not work for PLM-P
In the CTC, the "Select Affected Circuits" option does not show the affected circuits for PLM-P alarm. This issue has been resolved.
CSCtf77988—NMS support to display input voltage and ambience temperature
The CTC and CTM displays both the battery input voltage and ambient temperature. These values are also reported on the LCD panel.
Cross Connect Cards
This section documents resolved caveats for Cross Connect Cards in Release 8.6.1.
CSCsy86915—Extra STS is utilized in the first VT cross connect created on an STS
On the first VT cross connect created on an STS, an extra STS is utilized under the following conditions:
1.
2.
3.
This issue has been resolved.
CSCtd46366—Cross-connect loopback on monitor circuit affects the traffic of the original circuit
The cross-connect loopback on monitor circuit brings down the traffic of the original circuit under the following conditions:
1.
2.
3.
4.
This issue has been resolved.
Data I/O Cards
This section documents resolved caveats for Data I/O Cards in Release 8.6.1.
CSCsm09512—Packet drop and VCG-DEG condition observed after hard reset of CE-MR-10 card
The VT1.5-64v or VT1.5-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.
CSCso66424—LCAS VCG Member Rx side in Add State condition persists after hard reset of CE-MR-10 card
The LCAS VCG Member Rx side in Add State condition might persist after a hard reset of a CE-MR-10 card carrying a VT1.5 HW-LCAS circuit with a member count of greater than 40. 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.
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 VT-1.5 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 VT-1.5 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 fiber pull
A high traffic hit is seen on fiber pull for a HW-LCAS, split-fiber circuit on CE-MR-10, CE-MR-6, and ML-MR-10 cards under the following condition:
•
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.
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 carrying 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 release 9.0. This issue has been resolved.
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 OOS,OOG 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.
CSCsq24264—Traffic hit on CE100T-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.
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.
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.
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.
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.
CSCsr78331—Cannot create a STS-1-2v or a STS1 circuit on the CE-100 card
Cannot create a STS-1-2v or STS1 circuit when the following circuits are already provisioned: STS3c, STS-1-2v, STS-1-1v, VT-1-7v. This issue has been resolved.
CSCtc66943—Link does not come up when autonegotiation is enabled
The link fails to come up when the CE-1000-4 card and the HP ProCurve Switch are connected, and autonegotiation is enabled on both ends of the circuit. This issue has been resolved.
CSCtf10958—Path PMs are displayed for CE-MR/ML-MR Cards
The HTML PM file contains STS (or hop for SDH) rows related to CE-MR and ML-MR cards when a STS/VC circuit is present on the cards. This causes unwanted warning messages in the CTM PM logs. This issue has been resolved.
CSCse74833—GFP-CSF is not detected by CE-MR-10 and ML-MR-10 cards
GFP-CSF condition is not detected by CE-MR-10 and ML-MR-10 cards on a circuit with GFP encapsulation. This issue has been resolved.
DWDM
This section documents resolved caveats for DWDM in Release 8.6.1
CSCso73947—E port is down after MXP-MR-10DME card power up
The E port is down for 2 minutes after an MXP-MR-10DME card is powered up under the following conditions:
•
•
The system does not report an alarm. This issue has been resolved.
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.
This issue has been resolved.
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.
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.
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 put from IS state to OOS,MT state, and then back to IS state. This issue has been resolved.
CSCsl70268 —Severity is not cleared when the raised alarm is cleared
When an alarm raised on a port is cleared, the severity is not cleared. 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 I/O Cards in Release 8.6.1.
CSCsq48070 —Standby TCC crashes during database restore
The standby TCC crashes during a database restore in the following scenarios.
Scenario 1:
1.
2.
3.
Scenario 2:
1.
2.
3.
4.
Upon doing this operation, the standby TCC that should become active may reboot. This issue has been resolved.
CSCsq58173—TCC reboots when configuring DS3XM12 or mixed 1:1 or 1:N PG
TCC Reboot when configuring DS3XM12 or mixed 1:1 or 1:N PG. This issue occurs under the following conditions:
1.
2.
This issue has been resolved.
CSCsu20391—FE-AIS and RAI alarms are incorrectly reported
The far-end AIS (FE-AIS) and remote alarm indication (RAI) alarms are incorrectly reported and persist on the DS3 ports even though the FE-AIS is not present. This issue occurs under the following conditions:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Note
This issue has been resolved.
CSCsu39177—After deletion of VT circuit and creation of STS-1 circuit, there is traffic loss
After deleting a VT circuit and creating an STS-1 circuit, traffic loss occurs. A stuck AIS-V alarm causes the traffic loss.
This issue occurs under the following conditions:
1.
2.
3.
4.
This issue has been resolved.
CSCsu47448—For DS1 FEAC, loopcode in DS3 framing FAC is inserted on odd DS1 ports
In an XM12 portless operation in CTC, injecting far-end alarm and control (FEAC) codes on the odd port is reported on the even side of the portless circuit. This issue occurs under the following conditions:
1.
2.
This issue has been resolved.
CSCtb74439—DS3XM cards insert VT-AIS downstream
DS3XM card inserts an VT-AIS downstream when DS1 defects are detected on the VT circuits with IS,AINS state. 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 VT circuits on CTC conditions pane
The ROLL-PEND condition is seen for VT circuits on the CTC conditions pane.
1.
2.
3.
4.
This issue has been resolved.
CSCsl76684—Delay in AIC-I card becoming active
When activating or reverting an AIC-I card, there is a delay in becoming active. This issue has been resolved.
CSCsm14521—Inconsistency between LOCKOUT command status and switching status on Y-cable protected MXP-MR-10DME card
Inconsistency occurs between LOCKOUT command status and switching status on Y-cable protected MXP-MR-10DME cards. This issue has been resolved.
CSCsm25619 —Traffic is not restored after card reset
Traffic is not restored when the near-end and far-end nodes of a Y-cable protected MXP-MR-10DME card are unplugged and replugged. This issue has been resolved.
CSCtd42075—Upgrade of DS3XM-6 card to DS3XM-12 card leaves first 6 ports of DS1's Unframed
When DS3XM-6 card is upgraded to a DS3XM-12 card, the first 6 ports of the DS1's show framing type as unframed resulting in traffic loss. This issue has been resolved.
NCP
This section documents resolved caveats for NCP in 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 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 OC192XFP after both XC cards reboots
Bit errors are observed on the OC192XFP 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.
CSCsv54817—STS-96c circuits do not work with OC192XFP cards
STS-96c circuits raise path unequipped alarms if the circuit uses an OC192XFP card as a source, destination, or trunk. This issue occurs under the following conditions:
1.
2.
This issue has been resolved.
CSCsl87931— ALS condition permanently lost when manual restart is performed
When manual restart is performed on the OPT-BST-E card, an ALS alarm is cleared and a LASER-APR alarm is raised. The OPT-BST-E card shuts down because the line cannot be restored, and the LASER-APR alarm is cleared; however, the ALS alarm is not raised. 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 SONET 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.
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)