View the Lock for Update Logs

On the System Update tab of the RMCT, you can view logs for the following events:
  • System update lock attempts
  • Locked switchover attempts
Lock for Update Logs
Lock for Update Logs in RMCT
System Update Lock Attempts
Parameter
Description
Event No.
A unique, sequential number to identify the event.
Time Stamp
The date and time that the event was logged.
Event Class
All events related to system update lock attempts have the same event class: Lock for Update log
Basic Info
One of the following basic descriptions of the event:
  • System update lock is not attempted
  • Locking is in progress
  • System update lock is successfully completed
  • System update lock attempt failed
If a system update lock attempt failed, refer to the Extended Info parameters to identify the cause.
Extended Info 1
Extended Info 2
Additional information that is related to the basic description of the event. Use this information to troubleshoot failed lock attempts. Possible causes include the following:
  • Wrong chassis redundancy state
  • Wrong autoqualification option
  • Major fault in redundancy module
  • Modules in primary chassis and secondary chassis do not match
Extended information is not available for every event.
Locked Switchover Attempts
Parameter
Description
Event No.
A unique, sequential number to identify the event.
Time Stamp
The date and time that the event was logged.
Event Class
All events related to locked switchover attempts have the same event class: Locked Switchover log
Basic Info
One of the following basic descriptions of the event:
  • Locked switchover is not attempted
  • System is undergoing locked switchover process
  • Locked switchover is successfully completed
  • Locked switchover attempt failed
If a locked switchover attempt failed, refer to the Extended Info parameters to identify the cause.
Extended Info 1
Extended Info 2
Additional information that is related to the basic description of the event. Use this information to troubleshoot failed locked switchover attempts. Possible causes include the following:
  • Wrong chassis redundancy state
  • Major fault in redundancy module
  • Disconnected partner module
  • Synchronization connection timeout
Extended information is not available for every event.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal