How can we improve PI Connectors?

← PI Connectors

Connector-level Failover - OPC UA 2.x

Support connector-level failover in PI Connector for OPC UA 2.x (relay-enabled version). Similar to UniInt failover (interfaces), failover should be data source specific and always favor the data source in the better state.

104 votes

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Gabriel Verreault shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

8 comments

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Danifarris commented  ·   ·  Flag as inappropriate

    Hi OSIsoft,
    Echoing what others have shared already, I think we can all agree with these two points:

    1) Failover is a key pillar for the "critical infrastructure" very frequently present in all OSIsoft pitches; and
    2) OPC UA is probably the most common standard in industrial communication.

    Seeing that the OPC UA connector dropped the connector level failover feature in the new version (plus not having a clear roadmap for this) conveys a not so reassuring message to your customers who decided/take into consideration to engage a long strategic journey with you.

    I hope to see this implemented very soon, thanks!

  • jmoulds commented  ·   ·  Flag as inappropriate

    Hi OSIsoft, as others have pointed out, I'm baffled by the apparent backwards step in v2.x (i.e. no HA / failover support at the interface-level).

    However I notice that OPC UA has native support for something called "Client Failover" (see the 'OPC UA Online Reference' here: https://reference.opcfoundation.org/v104/Core/docs/Part4/6.6.1/ )

    I'm wondering if your intent is to support native OPC "Client Failover" under the new v2.x connector fork?

    For example:
    • You have two diverse PI OPC UA connectors (OPC UA 'clients') – both Active/Active – but one is operating in ‘backup’ mode
    • The OPC UA ‘server’ maintains information on it’s active client sessions
    • The ‘backup’ UA client monitors the client-session information on the UA server – and detects when the ‘active’ UA client has “failed”
    • The ‘backup’ UA client then instructs the UA server to redirect all future traffic to itself

    Is that on the cards for support in a future version of v2.x?

  • jproske commented  ·   ·  Flag as inappropriate

    From Case:00812539, I need a Failover at the Connector Level just the same as we have for the OPC-DA Interface.
    I learned that none of the "new" Connectors are able to have a redundancy on the Connector Level, so every Connector of a current Version is not useable for a Productive Environment in the chemical Production Environment.

  • Gabriel Verreault commented  ·   ·  Flag as inappropriate

    FYI - OPC UA 2.x connector does support OPC UA Server redundancy. It does not support client-side (connector) redundancy, which is what this 'Idea' is about.

  • Claudio Alejandro Martinez Carreño commented  ·   ·  Flag as inappropriate

    The main Idea is if the "Connector Model" will be replace the "Interface Model", this components must have at least, the same functionalities and improve performance on its purpose. So, a upgrade version of a connector should improve the last version and not minimize it.

PI Connectors: OPC UA

Categories

Feedback and Knowledge Base

(thinking…)
Posted ideas will have one of the following statuses.
Full definition of these statuses can be found on the Home Page.
No status
TELL US MORE
EVALUATING
PLANNED
IN DEVELOPMENT
COMPLETED
DECLINED