For one of our client we have an ignition 7.2.11 running with RSLinx and Kepserver6.
The RSLinx tags came from one ethernet card (controllogix 1756-ENB) and kepserver tags came from another exclusevly for that.
Despite this, we have errors like this one:
Do you have any clue or idea to attack this?
Thanks in advance. Greetings!
It looks like the root cause is that first error message with the
Unless you can capture this happening on Wireshark it’s not possible to assign blame to the Ignition UA client or the server it’s connected to. I’ve definitely seen servers return out of order sequence numbers before, and in the past there has been a bug in the client code that could cause it as well, though I don’t know if it actually affected a version this old.
I know this is an ignition forum and not wireshark forum, but.
I started capturing packets and is overwhelming the quantity. I tried to enable only OPCUA protocol but i didn’t understand what happened because the ip addresses disapear (I was filtering only the opcua lan and the remote kepware address).
Is there a “first steps” for wireshark and ignition (the old one that i’m using)?
In the capture options when you are selecting the interface to capture you can specify the IP address and port of the Kewpare server you are connected to. This should cut the traffic down considerably.
You should also probably set it up to use a ring buffer with multiple files on the Output tab so you can leave this running for long enough that the issue pops up again in the logs.
Once it’s happened again and you have a timestamp in the logs that you can correlate to a timestamp in the capture you can upload your captures here and we’ll take a look.
wireshark_capture.zip (1.8 MB) Kevin,
First of all, thanks for the help.
I think i’ve got it:
On wireshark, the timestamp says 17 because it’s UTC based, and ignition says 13 because it’s UTC-4 based (we’re from Chile).
Now, I attached the capture file.
Finally, i remembered that i have another ignition (same version 7.2.11) that it’s connected to the same kepserver (ask for only a few tags) through the same LAN and doesn’t have any error in the log.
The ignition that failed runs in a virtual machine (eSXi) but the one that doesn’t fail, runs in a “real” server.
Well, thanks again for the help. Greetings!
Sorry, but either there is something wrong with this capture or you’ve captured a different issue. The first 9 minutes of this capture, from packet 1 to packet 43225, don’t show a single response from the Kepware server. I don’t know if this is something else or the original error is a result of Kepware not responding for long enough.
I was doing it in the ignition server and the windows firewall was activated (we only open specific ports).
Do I need to do it in the kepserver machine (IP 126.96.36.199)?
Thanks and Greetings,