Clear The Otuk-Tim Condition - Cisco NCS 2000 series Troubleshooting Manual

Alarm Troubleshooting
ITU-T G.709 encapsulation refers to a digital data wrapper that is transparent across networking standards
such as SONET and protocols (such as Ethernet or IP).
When the trace mode is set to manual at the section and path level and the OTUk-TTI string is 64 bytes, the
OTUK-TIM alarm is triggered. This error condition occurs when the OTUk-TTI string is configured along
with ODUk-TTI string and the OTUk-TTI string is 64 Bytes. If the OTUk-TTI string is 63 bytes or if you
configure all the 64 bytes of the OTUk-TTI string without configuring the ODUk TTI string, the alarm is not
triggered.
For the above error condition, you can restrict the length of the provisioned OTUk-TIM messages to 32 bytes,
or disable manual insertion of TTI in the ODUk layer if you want to configure all the 64 bytes.

Clear the OTUK-TIM Condition

SUMMARY STEPS
1. Complete the
DETAILED STEPS
Complete the Clear the TIM Alarm, on page 415
If the condition does not clear, log into the Technical Support Website at
for more information or call Cisco TAC (1 800 553-2447).
OUT-OF-BUNDLE
Default Severity:
• On GE physical ports: Minor (MN), Non-Service-Affecting (NSA)
• On Channel Group port: Major (MJ), Service-Affecting (SA)
Logical Objects: ETH, CHGRP
The Out Of Bundle (OUT-OF-BUNDLE) condition occurs on GE_XP and 10GE_XP cards when the physical
port is placed outside the channel group bundle. It can also be raised on a channel group when all the members
of the bundle are placed outside the channel group bundle.
Clear the OUT-OF-BUNDLE Condition
SUMMARY STEPS
1. Make sure that the ports' expected speed and duplex settings are same as that of the channel group.
2. LACP mode configured between the peer ports must be valid. For example, you cannot have a
passive-passive combination.
Clear the TIM Alarm, on page 415
procedure.
Cisco NCS 2000 series Troubleshooting Guide, Release 11.0
Clear the OTUK-TIM Condition
procedure.
http://www.cisco.com/c/en/us/support/index.html
347