134 Rockwell Automation Publication 1756-UM535D-EN-P - November 2012
Chapter 6 Configure the Redundancy Modules
System Update Lock Attempts
The System Update Lock Attempts is where attempts to lock the system are
logged. This log displays the last four lock attempts and provides this information
specific to each attempt:
• Time and date
• Status (for example, Locked or Abort)
• Result (for example, System Locked or Invalid Response Received)
The status indicated in the System Update Lock Attempts log can be any one of
the states listed in this table.
If your status is indicated as Abort, one of these conditions can exist:
• An error occurred while communicating with the partner redundancy
module.
• A module in the secondary chassis does not have a partner in the primary
chassis.
• A module pair is incompatible.
• The SysFail test was unsuccessful in the primary redundancy module.
• A Major Recoverable Fault occurred in primary redundancy module.
• A Major NonRecoverable Fault occurred in primary redundancy module.
• A module was inserted into the chassis.
• A module was removed from the chassis.
• A failed module exists in the secondary chassis.
• A failed module exists in the primary chassis.
• An Abort System Update command received.
• Invalid response was received from a module.
• A module rejected the state change.
• A platform mismatch was detected.
Table 22 - System Update Lock Attempts Log Statuses
Status Interpretation
Not Attempted A system lock has not been attempted since the last
powerup.
In Progress A lock is in progress.
Locked The lock was successfully completed.
Abort The lock attempt failed. The reason for the failure is
indicated in a Result field.
To Next Page
Loading...
Need help?
General
