2-126
Cisco ONS 15454 Troubleshooting Guide, R8.5
November 2009
Chapter 2 Alarm Troubleshooting
2.7.165 HLDOVRSYNC
Clear the HI-TXPOWER Alarm
Step 1 In node view, double-click the card view for the TXP_MR_10E, TXP_MR_10G, TXP_MR_2.5G,
TXPP_MR_2.5G, MXP_2.5G_10G, or OC192-XFP card.
Step 2 Click the Provisioning > Optics Thresholds > Current Values tabs.
Step 3 Decrease (change toward the negative direction) the OPT-HIGH column value by 0.5 dBm.
Step 4 If the card transmit power setting cannot be lowered without disrupting the signal, complete the
“Physically Replace a Traffic Card” section on page 2-273.
Step 5 If the alarm does not clear, log into the Technical Support Website at http://www.cisco.com/techsupport
for more information or call Cisco TAC 1 800 553-2447.
2.7.165 HLDOVRSYNC
Default Severity: Not Alarmed (NA), Non-Service-Affecting (NSA)
SONET Logical Object: NE-SREF
The Holdover Synchronization Mode condition is caused by loss of the primary and second timing
references in the node. Timing reference loss occurs when line coding on the timing input is different
from the configuration on the node, and it often occurs during the selection of a new node reference
clock. The condition clears when primary or second timing is reestablished. After the 24-hour holdover
period expires, timing slips could begin to occur on an ONS 15454 relying on an internal clock.
Clear the HLDOVRSYNC Condition
Step 1 Clear additional alarms that relate to timing, such as:
• 2.7.141 FRNGSYNC, page 2-114
• 2.7.142 FSTSYNC, page 2-115
• 2.7.200 LOF (BITS), page 2-147
• 2.7.217 LOS (BITS), page 2-157
• 2.7.264 MANSWTOINT, page 2-179
• 2.7.265 MANSWTOPRI, page 2-179
• 2.7.266 MANSWTOSEC, page 2-179
• 2.7.267 MANSWTOTHIRD, page 2-179
• 2.7.403 SWTOPRI, page 2-239
• 2.7.404 SWTOSEC, page 2-239
• 2.7.405 SWTOTHIRD, page 2-239
• 2.7.406 SYNC-FREQ, page 2-240
• 2.7.408 SYNCPRI, page 2-241
• 2.7.409 SYNCSEC, page 2-242
• 2.7.410 SYNCTHIRD, page 2-242
To Next Page
Loading...
