I am working on a large project where we are running close to the maximum monitored item count in the PLC for our OPC license. Another consequence of working on the project is that many engineers have created copies of the project on their own localhost and one or two individuals have failed to or do not understand the need to disable OPC connections on their own local project. Thus, we are unable to monitor all of our devices when one of them connects to the network as each item is monitored by two identical projects. The PLC gives us two unique numbers associated with the Ignition session/subscription, as well as the project name. As the project names are duplicate, I am wondering if there is any information about the ID or name properties of Ignition's OPC subscriptions that might allow us to trace down where this project is being hosted. Any information is appreciated, even if these properties are indeed known to be random assignments!
The session name that Ignition uses when it creates a session is "ignition[$systemName]_${connectionName}_${System.currentTimeMillis()}"
where $systemName is the Ignition Gatway system name. Unfortunately if people are just restoring copies they may be the same...
Might be the same issue using the application URI to identify the client connections...
You might try to connect that server using UaExpert and then open a Diagnostics view and see if there's any information in all the session diagnostics info that lets you identify a client.
UaExpert gives me an aditional GUID from the client but I'm unsure if this is decipherable- and still looking into methods of tracking this down on the network
If you've got fancy managed switches in place that let you capture traffic on a network port then you could get a packet cap of all the traffic going to the PLC and then look for the inbound comms to the OPC UA TCP port.