Redundancy system

Add Redundant Chassis Pairs to the security policy model to secure class 3 traffic on the uplink port.
IMPORTANT: Multicast I/O traffic is not secured for redundant pairs.

Redundancy system requirements

Redundancy system works with 1756-EN4TR adapter firmware revision 4.001 or later. The adapters must be configured for redundancy and be in the IP Swapping Mode.
Both primary and secondary devices must:
  • Have chassis with the same number of slots
  • Each chassis must contain
    ControlLogix®
    1756-RM2
  • Have redundancy modules connected with each other
For more information, refer to the ControlLogix 5580 Redundant Controller User Manual, publication 1756-UM015H-EN.

Redundancy system configuration

During the redundancy system configuration, both primary and secondary controllers must have the same IP address. The IP address of the secondary controller changes automatically by adding 1 to the last octet. The redundancy configuration is independent from
FactoryTalk Policy Manager
.
For more information, refer to the ControlLogix 5580 Redundant Controller User Manual, publication 1756-UM015H-EN.
TIP:
FactoryTalk Policy Manager
 does not get information about devices in real time. If you validate redundant ports when two controllers configure redundancy and a connection error appears, verify that the redundant controllers are correctly connected, see
FactoryTalk® Diagnostics
 logs, and validate redundant ports again.

Policy security model configuration

Configure redundant systems in the security policy model by adding redundancy-capable devices to the security policy model. See Add redundancy-capable devices.
TIP: Validating the security policy model for redundancy to add all redundant systems to the model, displays the
Update security policy model to ensure redundancy
 dialog that enables you to adjust the policy model to ensure that Redundant Chassis Pairs are configured correctly. For more information, see Dialog: Update security policy model to ensure redundancy.
Throughout the
FactoryTalk Policy Manager
 interface, indicates Redundant Chassis Pairs in the security policy model. For more information, see FactoryTalk Policy Manager interface.
Consider the following for devices configured as Redundant Chassis Pairs:
  • You cannot configure a device as a Redundant Chassis Pair if the device is configured for Automatic Policy Deployment. See Automatic Policy Deployment.
  • You cannot copy devices configured as Redundant Chassis Pairs by using context menus. See Context menus.
  • Deleting devices configured as a Redundant Chassis Pair, deletes security configuration for both devices. See Delete a device.
  • Replacing devices configured as a Redundant Chassis Pair, replaces security configuration for both devices. See Replace a device.
  • Security policy model is deployed successfully if both devices in a Redundant Chassis Pair are correctly configured. See Deploy a policy model.
  • Inbound and outbound CIP bridging settings configured for Redundant Chassis Pairs allow all traffic only. See CIP Bridging.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal