Considerations When Connecting OPC Collector to Redundancy Master with Primary and Secondary IGS Servers

Consider the following information when you connect an OPC Collector to a Kepware Redundancy Master with both primary and secondary servers using IGS (Industrial Gateway Server).

Note: These considerations assume that both IGS servers share the same channel, device, and tags.
  • If, after creating a tag in Historian, you modify the tag ?s existing source address, Historian will consider this an invalid tag until the OPC Collector is restarted.

    For example, suppose there is a tag in IGS Server called ?r;Tag1 with source address K0001 and the source address of Tag1 is modified from K0001 to R9998. Historian considers this an invalid tag. No data update occurs and no Bad Quality marker is set in Historian. The OPC Collector must be restarted to ensure that data is collected for this tag in Historian.

  • Restart sequence is important, and needs to be done in order from the source.

    When you need to restart after encountering an issue, restart the Redundancy Master Service before restarting the OPC Collector.

  • If IGS OPC tags are added in Historian Server, then these tags cannot be deleted in IGS Server.

    If you attempt to delete them in IGS Server, the error ?Rejecting attempt to delete reference object ? is displayed at the IGS Server end.

    To avoid this error, first delete the tags in Historian which were associated with IGS Server and then delete the device in IGS Server.

  • Failure to browse IGS Server Tags may require OPC Collector restart.
    Note: If the OPC Collector status shows as Running, but you are unable to browse IGS Server tags, restarting your OPC Collector may solve this issue.