Changes made to any of the following OPC UA Server settings requires a restart (of either the Gateway or the OPC UA module) before the changes will take effect.
The table below represents settings on Ignition's OPC UA server. They'll only become available if the OPC UA Module is installed on the Gateway.
The port the UA server will bind to.
|Bind Addresses||The address the server will bind to. If you want to expose the OPC UA server to external sources, you need to use 0.0.0.0 or the IP address of the computer.|
A comma separated list of endpoint addresses that the UA server can be reached at. It is important that this is set to addresses that can be reached by any UA clients attempting to connect to the server.
When entering addresses into this property, they can be just an IP address or hostname:
Alternatively, angled brackets can be used. When applied to an address, the server attempts to find the hostname, or resolve the value to as many addresses or hostnames as it can find.
A comma separated list of acceptable security policies. Available policies are:
In addition, the following deprecated policies are available, but not recommended:
|Anonymous Access Allowed||Specifies if UA clients are allowed to connect to this server anonymously. While false, client connections are required to authenticate with the server.|
|User Source||Which user source contains the initial user for authenticated access. Credentials for the initial user can be found above.|
Attempts to use the 'opcua-module' user sources
|Expose Tag Providers|
When enabled, Ignition Tag Providers will be exposed through the UA server, allowing third-party UA clients to access tags in the provider.
|Max Session Count|
The maximum number of client connections to the UA server.
|Backup Bind Addresses|
The local addresses that the UA server will attempt to bind to while the backup server in a redundant pair .
|Backup Endpoint Addresses|
The endpoint addresses that the UA server can be reached at while the server is configured as the backup in a redundant pair . The notation on this property is similar to the Endpoint Addresses property above, in that angled brackets can be used with each hostname and IP address.
|Read-only When Inactive Node|
When enabled, this server switches to a read-only state while its Gateway is the inactive node in a redundant pair.
|Master Application URI|
Application URI that a redundant backup will advertise in its address space as belonging to the server on the redundant master. When enabling OPC UA redundancy, enter the master gateway's URI here. URIs will generally look like the following:
|Backup Application URI|
Application URI that a redundant master will advertise in its address space as belonging to the server on the redundant backup. When enabling OPC UA redundancy, enter the backup gateway's URI here.
Ignition's OPC UA server supports non-transparent redundancy. This allows third-party OPC UA clients to connect to the active node in a pair of redundant gateways. If the master gateway goes down, then the OPC UA client would be able to switch to the backup gateway, following the active node as the system changes.
The steps below demonstrate how to configure OPC UA redundancy.
From this point on, third-party OPC UA clients can connect to the active node's OPC UA server, and will fail over when the active node switches. While OPC UA redundancy is enabled, the Ignition OPC UA Server > Server > ServiceLevel tag can be used to denote which server is running as the master.
|Service Level Value||Description|
|255||The OPC Server is on the master gateway, and the master is the active node. Note that this value is also used in cases where redundancy is not enabled.|
|254||The OPC Server is on the backup gateway, and the backup is the active node.|
|1||The OPC Server is the inactive node. Meaning the other node is currently active.|
It is possible for both nodes to be active, where the master shows a value of 255 and the backup simultaneously shows a value of 254. This generally happens in cases where the two nodes are unable to communicate with each other. For example, when a network disconnect occurs between the two gateways, or if the gateway network connection between the two is pending approval.
You may occasionally run into issues with Ignition's OPC UA Server connection. In these situations, there are a few things you can check to diagnose your issue.
To troubleshoot your connection to Ignition's OPC UA Server, follow the steps below:
<hostname>,<localhost>. The IP address of the internal OPC UA Server, which can be found on the Status page of your Gateway, can also be appended.
localhost. If you want to expose the OPC UA Server to external clients, you can use a value like 0.0.0.0 or the IP address of the computer.
If you continue running into problems after following these troubleshooting steps, contact the Support department.