The stored logs can be retrieved only by the Cisco support team to diagnose the root cause of the card failure.
Note
Run Time Log for IO Cards
Run time log traces events and critical information such as alarms raised and cleared, power variations and
so on, during the working of the card. The stored logs help identify the cause of failure.
For legacy cards (OPT-BST and OPT-PRE), the run time logs are automatically stored in RAM and are deleted
when the card is hard reset. To store the logs in the permanent memory, the user should take the snapshot of
logs as explained in the
Snapshot Logging in CTC, on page 39
section. For new cards (40-SMR1-C and
40-SMR2-C), the run time logs are automatically written to the flash memory and are not deleted even after
reset or hard reboot of the card.
The following table lists a few run time logs captured for a specific event:
Table 5: Run Time Logging—Events and Logs
Log
Event
• Input power of all the active stages (1 for the
BST, 2 for the PRE)
• Output power of all the active stages (1 for the
BST, 2 for the PRE)
When the change in Rx and Tx optical power in the
active stage is greater than the threshold value, the
unit stores the input and output power every second.
The difference between the two adjacent input power
readings or two adjacent output power readings is
greater than 1 db, and this event occurs more than 10
times in 30 seconds
• Module status
• Laser pump current—set point and value
• Laser pump power—set point and value
• DCU loss
• VOA loss
• Optical power values
Target power not reached (0.5 dB or more difference
from set point)
• Temperature of the case
• Temperature of the laser
Fiber Temperature Alarm
• Temperature of the case
• Temperature of the fiber
Laser Temperature Alarm
• Temperature of the case
• Temperature of the fiber
Case Temperature Alarm
Cisco NCS 2000 series Troubleshooting Guide, Release 11.0
38
General Troubleshooting
Run Time Log for IO Cards
