Configuring Device Redundancy

The DAServer Manager provides the ability to assign redundant device for fail-over protection in the event of device failure. Two devices must be configured in the same DAServer having identical item syntax.

Primary and secondary devices will be setup in the REDUNDANT_DEVICE object in the SMC, along with a common item name (ping item) shared by each device to determine device status.

To setup up a REDUNDANT_DEVICE from the configuration branch:

1. Set-up a primary device and hierarchy in the DAServer Manager in the SMC.

2. Create at least one device item that can be shared between the primary and secondary devices to determine device status.

   

3. Set up an secondary device on the same DAServer. Once again, create an identical device item within the secondary device so that device status can be determined.

   

4. Select and right-click on the configuration node under the TCP/IP Network Device object.

5. Select Add REDUNDANT_DEVICE Object. An object called New_REDUNDANT_DEVICE_000 is created.

   

6. Rename the newly created object as appropriate. The New_REDUNDANT_DEVICE_000 configuration view is displayed in the Configuration branch of the hierarchy.

7. Enter or use the device browser to select the primary and secondary devices. Save the hierarchy node configuration by clicking on the save icon.

   

   Note: Unsolicited message configuration is not supported from the device redundant hierarchy.

   Important! A Ping item must be specified and be a valid tag in both the primary and secondary controllers to determine the connection status for $SYS$Status. The Ping item can be a static item in the device such as a firmware version or processor type. If the Ping item is invalid or does not exist in the controller, the failover operation may not work correctly as the value of $SYS$Status may continue to stay as FALSE in the standby device.