DETAILED STEPS
Complete the Clear the OTUK-SD Condition, on page 345 procedure.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/c/en/us/support/index.html
for more information or call Cisco TAC (1 800 553-2447).
ODUK-SF-PM
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
Logical Object: TRUNK
The ODUK Signal Fail (SF) PM condition (ODUK-SD-PM) applies to TXP_MR_10G, TXP_MR_2.5G,
TXPP_MR_2.5G, MXP_2.5G_10G, ADM-10G, and OTU2_XP cards when ITU-T G.709 encapsulation is
enabled. ODUK-SF-PM indicates that incoming signal quality is poor and the incoming line BER has passed
the fail threshold. The BER problem is indicated in the path monitoring area of the optical data unit frame
overhead.
Clear the ODUK-SF-PM Condition
SUMMARY STEPS
1. Complete the Clear the SF (DS1, DS3) Condition procedure located in the Alarm Troubleshooting chapter
of the Troubleshooting guide.
DETAILED STEPS
Complete the Clear the SF (DS1, DS3) Condition procedure located in the Alarm Troubleshooting chapter of the
Troubleshooting guide.
If the condition does not clear, log into the Technical Support Website at http://www.cisco.com/c/en/us/support/index.html
for more information or call Cisco TAC (1 800 553-2447).
ODUK-TIM-PM
Default Severity: Major (MJ), Service-Affecting (SA)
Logical Object: TRUNK
The ODUK-TIM- PM condition applies to the path monitoring area of the OTN overhead for TXP_MR_10G,
TXP_MR_2.5G, TXPP_MR_2.5G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, MXP_2.5G_10G,
AR_MXP, AR_XP, AR_XPE, ADM-10G, and OTU2_XP cards. The condition occurs when there is a trace
identifier mismatch in the data stream. ODUK-TIM-PM causes an ODUK-BDI-PM , on page 317, downstream.
Cisco NCS 2000 series Troubleshooting Guide, Release 11.0
320
Alarm Troubleshooting
ODUK-SF-PM
To Next Page
Loading...
Need help?
General
