Maintain a Secure High Availability System
To maintain a high availability system in compliance with IEC-62443-4-2 requirements,
know how to update firmware, recover high availability, and back up and restore all
components of the system in accordance with documented procedures.
Firmware Update Considerations
The Redundancy System Update (RSU) feature automatically migrates a deployed security
policy to a new firmware revision when you follow the procedures in Online Firmware Updates. To make sure that all
security settings are in place after a firmware update, repeat verification of the
Security Requirements for IEC 62443-4-2.
Recover High Availability After a Fault
If an event occurs that causes the high availability system to lose redundancy, you
must be prepared to recover the high availability of your system if manual
intervention is necessary:
- Protect access to the system for users who are responsible for recovery as described in Prevent Lockout of Essential Users.
- Know how to reset a redundancy module.
- Understand the methods to identify and clear faults or other events that can cause a loss of redundancy as described in Troubleshoot Redundancy.
- Know how to replace a redundant module as described in Module Replacement.
- Know how to perform a factory reset on redundant modules. For more information, see the user manual for the module.
IMPORTANT:
Replacing a
CIP Security™
-enabled 1756-EN4TR module requires additional steps to make the module
visible in FactoryTalk® Linx
software. See Replace a CIP Security-enabled 1756-EN4TR Module.Back up and Restore a High Availability System
Know how to back up and restore all components of your secure high availability
system. A full backup includes the components in the following table.
Component | Guidelines |
|---|---|
FactoryTalk® Directory | Enable disaster recovery for assets in the FactoryTalk® Directory .For more information, see the FactoryTalk AssetCentre Getting
Results Guide, publication FTAC-GR002. |
Security policy model | Create backup files to preserve and restore the security policy models for your system if there is a failure. For more information, see the FactoryTalk Policy Manager
Getting Results Guide, publication FTALK-GR001. |
Controller project | Create a backup of the controller project in the primary chassis and store the file in a secure location. The controller project for the primary controller automatically transfers to the secondary controller during the synchronization process. |
Redundancy module | Manually record all configuration settings for 1756-RM3 modules and store the settings in a secure location. |
Communication module | The configurations are automatically backed up to the SD cards when they are plugged into the modules. To save the configurations to both SD cards, you must keep the SD cards inserted in the modules in both chassis. Create copies of the SD cards and store them in a secure location. Also record where each SD card is installed, including the chassis name (Chassis A or Chassis B) and the slot number. For more information about communication module SD cards, see
the ControlLogix EtherNet/IP Network Devices, publication 1756-UM004. |
Cables and other hardware | Reserve duplicate cables and other hardware that is used in the system so that essential functions of the system can be restored if needed. Along with the hardware, keep the following:
|
Provide Feedback