System Update Tab Overview

The system update tab allows you to perform firmware updates in the secondary chassis while the primary chassis is controlling outputs.
WARNING:
While performing firmware updates with help of the "System Update" feature, the redundancy feature is disabled. i.e. the Secondary Chassis is unable to resume control on a primary failure.
To perform a Redundancy System Update, the Auto-Synchronization option in the
Configuration
 tab of the
FactoryTalk Linx
 Redundancy Module Configuration Tool must be set to
Never
 and the secondary chassis should be in a disqualified state.
This tab provides the following functionalities:
  • System Update Command buttons
    • Lock for Update
    • Cancel System Lock
    • Initiate Locked Switchover
  • System Update Lock Attempts History window
  • Locked Switchover Attempts History window
  • Refresh button
The
Lock For Update
,
Cancel System Update
 and
Initiate Locked Switchover
 buttons mentioned above are available only in
FactoryTalk Linx
 Redundancy Module Configuration Tool instance opened by referring to the primary Redundancy Module. These buttons are disabled in the
FactoryTalk Linx
 Redundancy Module Configuration Tool instance opened by referring to the secondary Redundancy Module. However, the
System Update Attempts
 history and
Locked Switchover Attempts
 history windows are updated in both primary and secondary
FactoryTalk Linx
 Redundancy Module Configuration Tool.
TIP:
Navigation to the following
FactoryTalk Linx
 Redundancy Module Configuration Tool tabs is NOT allowed while system update operations are in progress.
  • Configuration
  • Synchronization
  • Synchronization Status
System Update Command Buttons
Option
Descriptions
Lock For Update
Clicking this button initiates the locking process. This button will be enabled only when all the modules in the primary chassis have resolved their compatibilities. Before initiating the locking process, please make sure that
  1. Auto-Synchronization option in the
    Configuration
     tab of the
    FactoryTalk Linx
     Redundancy Module Configuration tool is set to Never
  2. The Secondary chassis is in Disqualified Secondary state
  3. All the modules in the secondary chassis (including the Secondary Redundancy Module) and the Primary Redundancy Module have been updated to Redundancy System Update compatible firmware revisions
After modules in the secondary chassis and the Primary Redundancy Module have had their firmware updated, and recompiled application programs have been downloaded to the updated secondary controllers, then click on this button to attempt locking.
Successful execution of this command initiates the locking process, which may not finish for several seconds. When the locking process is complete, the chassis status displayed at the bottom of the
FactoryTalk Linx
 Redundancy Module Configuration Tool will change from
Primary with Disqualified Secondary
 to
Primary Locked for Update
.
Cancel System Lock
The system Update process can be canceled by clicking on the
Cancel System Lock
 button. Successful execution of this command disqualifies the secondary. This button will be enabled when the locking process is in progress or the Redundant Chassis Pair has entered the steady state Locked condition.
Initiate Locked Switchover
Click on this button to initiate a locked switchover. This button is enabled only when the chassis redundancy state is primary with a locked secondary.
The difference between a Locked Switchover and a Normal Switchover is that the Locked Switchover can only be initiated by a user and not by a failure of the primary.
System Update Lock Attempts History
Displays the last four System update locking attempts. These attempts are labeled as follows:
  • N - the most recent attempt
  • N-1 - the second-most recent attempt
  • N-2 - the third-most recent attempt
  • N-3 - the fourth-most recent attempt
For each attempt, the lock initiation time, status, and result are mentioned. The Status and Result columns indicate the current status for the system update lock attempt and if the lock attempt is not successful, the reason for the same.
Lock Initiation Time is described in dd/mm/yyyy hr: min: sec: msec format.
Possible Status
Description
Not Attempted
System update lock is not attempted since the last power up
In Progress
Locking is in progress
Locked
System update lock was successfully completed
Cancel
System update lock attempt failed (Actual reason of the failure is indicated in a Result field)
Possible causes for
Cancel
 Status:
  • 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
  • The module pair is incompatible
  • SysFail test failed in the primary Redundancy Module
  • Major Recoverable fault in primary Redundancy Module
  • Major Non Recoverable fault in primary Redundancy Module
  • A module was inserted into the chassis
  • A module was removed from the chassis
  • A module failed in the secondary chassis
  • A failed module exists in the secondary Chassis
  • A failed module exists in the primary Chassis
  • Cancel System Update
     command received
  • Invalid response received from a module to
    Lock for Update
     command
  • A module rejected the state change (See Event Log for details)
  • A Module was Inserted in the Partner Chassis
  • Partner Module was Removed
  • Platform Configuration Identity Mismatch Detected
Locked Switchover Attempts History
Displays the last four Locked switchover attempts. These attempts are labeled as follows:
  • N - the most recent attempt
  • N-1 - the second-most recent attempt
  • N-2 - the third-most recent attempt
  • N-3 - the fourth most recent attempt
For each attempt, the locked initiation time, status, and result are mentioned. The Status and Result columns indicate the current status for the locked switchover attempt and if the locked switchover attempt is not successful, the reason for the same.
Locked switchover initiation time is described in dd/mm/yyyy hr: min: sec: msec format.
Possible Status
Description
Not Attempted
Locked switchover is not attempted since the last power up
In Progress
System is undergoing a Locked switchover process
Success
Locked switchover was successfully completed
Cancel
Locked switchover attempt failed
(Actual reason of the failure is indicated in a Result field)
Possible Causes for Cancel status
  • A module rejected the
    Locked Switchover Readiness
     command
  • Invalid response received from a module to the
    Locked Switchover Readiness
     command
  • A module rejected the
    Initiate Switchover to Locked secondary
     command (Refer to Note below)
  • Invalid response received from a module to
    Initiate Switchover to Locked secondary
     command (Refer to Note below)
    TIP:
    If this kind of failure occurs then the chassis enters into two disqualified states. i.e both the Primary and Secondary Redundancy Module's display
    DISQ
     on their front panel display. The control is lost in this case.
Refresh
Click on this button to refresh the recent system update locking attempts and locked switchover attempts list.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal