FUDforum
My FUDforum

Home »  » DeviceMaster RTS, Pro and Serial Hub » DeviceMaster RTS 32 Periodic Network Dropout (SocketServer firmware has started dropping off the network at random intervals)
DeviceMaster RTS 32 Periodic Network Dropout [message #1236] Mon, 28 September 2020 04:59 Go to next message
dscott is currently offline  dscott
Messages: 2
Registered: June 2017
Junior Member
I'm not sure whether this is a hardware fault or a firmware issue, but we are running SocketServer 10.06 on a DeviceMaster RTS 32-port and have recently started experiencing periodic dropouts of the network connection. Pinging the device results in a 25% loss over 300 messages.

The device has been working without issue for a number of years and the problem only started recently, but there have been no hardware/software changes to the system prior to the issue occurring.

We rules out an issue with the switch by swapping it to a different port but saw the same issue - every 10-20 seconds the network port can be seen to stop flashing for a second before starting again.

When it is communicating, the device seems to work fine.
Re: DeviceMaster RTS 32 Periodic Network Dropout [message #1240 is a reply to message #1236] Mon, 28 September 2020 08:18 Go to previous messageGo to next message
Kurt is currently offline  Kurt
Messages: 288
Registered: July 2016
Location: Minnesota
Power User
For issues like this, possible network problems need to be confirmed.

Can you run a Wireshark on your network and look for unusual activity?

Another thing to try is to isolate a DeviceMaster with this issue occurring most frequently and connect the network jack directly to your PC or laptop and see if the issue continues.

In the Driver Management Console, you can highlight the DeviceMaster, go to the Advanced Tab and check the network statistics for additional information as well.

Kurt


Kurt Rees
www.comtrol.com
http://forum.comtrol.com/

Comtrol Corporation
100 Fifth Ave NW
Minneapolis, MN. 55112
Direct +1 763.957.6000 | +1 Fax (763) 957-6001
connect. communicate. control
Re: DeviceMaster RTS 32 Periodic Network Dropout [message #1242 is a reply to message #1240] Mon, 28 September 2020 08:56 Go to previous messageGo to next message
dscott is currently offline  dscott
Messages: 2
Registered: June 2017
Junior Member
I don't have access to the system at the moment but should have the opportunity to get that checked later in the month. I'm assuming we would be looking for something either being broadcast or directly sent to that port?

What is the 'Driver Management Console' that you are referring to? We have Portvision DX installed, and can configure via the Web Interface, but haven't seen that software before is it used for managing 'virtual' serial ports on a PC? If so, that is not how the device is used in our application. It is being used to send data from each serial port to different I.P. addresses / devices (slaves) who then send responses back, with the responses being sent out on the relevant serial ports.
Re: DeviceMaster RTS 32 Periodic Network Dropout [message #1294 is a reply to message #1236] Mon, 25 January 2021 22:15 Go to previous messageGo to next message
imissmyrocket is currently offline  imissmyrocket
Messages: 15
Registered: January 2021
Location: Austin
Member
I came here for the exact same reason...I've tested the network thoroughly, and am experiencing issues. I've had a team of network engineers test the network. We are not dropping packets, we have no errors, very few packet retries. I'm now at the point where I'm starting to modify the driver so I can get a better idea of what is happening. Came looking for support, but I guess this is it? Might be time to start shopping instead.

It seems OK until IO load gets high, and then the devicemaster appears to be disconnecting on purpose...I think something is timing out (the driver is chock full of timeouts, and who knows what is going on in the embedded side). Changing timeouts in the config doesn't seem to help. If I raise IO prio of ethernet kernel module, nslink, way way up, it gets a little better, but causes worse problems when it does it's thing, nslink will block the entire OS if I let it it seems. The device master I confirmed is rebooting itself, at several different locations where network throughput is > 500 Mbps.

The journalctl has some good stuff for debugging in it, the driver has kernel messsages enabled. I get "kernel: nslink: TCP connection to serial hub terminated by 'send shutdown'" and then you see the DM reboot and bootloader pop up, then socket server, then a minute or two later it does it all over again, until ethernet traffic slows down. What is more concerning is sometimes I'll see "terminated by ?". Looks like a memory leak to me, you shouldn't realistically end up in that branch of the code.

Given this first page is about 50% problems like these, at least you can take solace in the fact that you are not alone? Or, maybe this is what you get for using 1970s technology? I mean these days I wish the hardware guys would throw a phy on it unless it is really long distance.

It would be great if the DeviceMaster when it auto-reboots itself would put a reason in a log somewhere. I think that would be a critical thing for debugging. I need a phone number to call, this is too one sided lol.


Re: DeviceMaster RTS 32 Periodic Network Dropout [message #1296 is a reply to message #1294] Wed, 27 January 2021 14:52 Go to previous messageGo to next message
Kurt is currently offline  Kurt
Messages: 288
Registered: July 2016
Location: Minnesota
Power User
Hi,

What version of driver, firmware and operating system are you using?
When did this start occurring or has this always been the case?
If you have more than one DeviceMaster in the network, is this happening to one or to all of them?
How often are these issues (hourly, daily, etc)?

You can call 1-330-425-3555 or 1-330-486-0001, Select Option 2

Kurt


Kurt Rees
www.comtrol.com
http://forum.comtrol.com/

Comtrol Corporation
100 Fifth Ave NW
Minneapolis, MN. 55112
Direct +1 763.957.6000 | +1 Fax (763) 957-6001
connect. communicate. control
Re: DeviceMaster RTS 32 Periodic Network Dropout [message #1298 is a reply to message #1296] Wed, 27 January 2021 18:20 Go to previous messageGo to next message
imissmyrocket is currently offline  imissmyrocket
Messages: 15
Registered: January 2021
Location: Austin
Member
I batched everything up and sent it off to you guys in an email, to a Mr. Carrizales. It has actual logs and timestamps and files downloaded from the devices. Hopefully you can help, I think things will go south real quickly if not. For the benefit of others. I've tried driver versions 7.26, 7.34. 8.0. We've only got one device master per network/site. We are basically direct connected with only a cisco switch in between us, on the same subnet/vlan. It's happening at multiple sites it seems, (different networks) but only where the IO load gets high...I recently updated firmware on the devices to the latest. Not sure how long it has been going on, we didn't realize it was happening until a few weeks ago. FW was updated a few months ago. Traffic on the network was lower then due to the application and effects of COVID19.
Re: DeviceMaster RTS 32 Periodic Network Dropout [message #1299 is a reply to message #1298] Wed, 27 January 2021 20:43 Go to previous messageGo to next message
Kurt is currently offline  Kurt
Messages: 288
Registered: July 2016
Location: Minnesota
Power User
I work closely with Ed. For the benefit of myself and others, when this occurs, can the unit be pinged? To recover, do you do a power off/ on or a reboot?
Also, in the network -> Security tab disable SNMP, there's also an area where you can isolate the IP Address connecting to the DeviceMaster to the server running the driver.
As a test, try those two things until Ed can get back to you after analyzing the data.

By high I/O I'm assuming high network vs high serial I/O.

Kurt


Kurt Rees
www.comtrol.com
http://forum.comtrol.com/

Comtrol Corporation
100 Fifth Ave NW
Minneapolis, MN. 55112
Direct +1 763.957.6000 | +1 Fax (763) 957-6001
connect. communicate. control
Re: DeviceMaster RTS 32 Periodic Network Dropout [message #1300 is a reply to message #1299] Thu, 28 January 2021 10:27 Go to previous messageGo to next message
imissmyrocket is currently offline  imissmyrocket
Messages: 15
Registered: January 2021
Location: Austin
Member
Hey Kurt, I mean high IO from the server perspective, could be ethernet/file/device/pipes/etc... Newer versions of linux allow you to set "IO priority", and when you look at those queues, they don't break it down by type of IO, it is all just files from that perspective anyhow. All the user threads are pretty low on this prio list, (B4) and i see the nslinkd at (B3). Kernel threads are usually a little higher.

The device master is restarting itself...so no it can't be pinged, not until after the boot process I imagine and ethernet comes up. We don't do anything to recover, it appears the DM is doing that on it's own, right? The on set techs told me they see it rebooting. The web interface times out too, it doesn't respond to pings, it is running the Bootloader I would think during this time-frame.

Is there not a branch in the embedded software that if something occurs it resets itself by rebooting? That is what appears to be happening. Is there a watchdog or something timing out? I can't seem to figure out what it is, but i have no idea what is running on the DM.

This message: 'kernel: nslink: TCP connection to serial hub 0 terminated by 'send shutdown'

Does that mean the DM sent the controlling server a message that he was going to restart for some reason? If so, what are the reasons he would do that? I know the DM may get neglected for a while because of more important stuff happening.

I will try what you've mentioned. I am also playing with priorities, both IO and thread scheduling trying to get nslink more time slices and more opputunity to do ethernet IO.
Re: DeviceMaster RTS 32 Periodic Network Dropout [message #1301 is a reply to message #1300] Thu, 28 January 2021 11:25 Go to previous messageGo to next message
Kurt is currently offline  Kurt
Messages: 288
Registered: July 2016
Location: Minnesota
Power User
The message is basically saying the driver lost the communication of the DeviceMaster over the network. I've discussed this with Ed and we will wait for your testing results.

Do you have any applications on the network that scan for vulnerabilities (Like Nessus, for instance). I've seen those programs cause some strange symptoms with network Devices including resets and communication losses.

Kurt


Kurt Rees
www.comtrol.com
http://forum.comtrol.com/

Comtrol Corporation
100 Fifth Ave NW
Minneapolis, MN. 55112
Direct +1 763.957.6000 | +1 Fax (763) 957-6001
connect. communicate. control
Re: DeviceMaster RTS 32 Periodic Network Dropout [message #1302 is a reply to message #1301] Thu, 28 January 2021 16:27 Go to previous messageGo to next message
imissmyrocket is currently offline  imissmyrocket
Messages: 15
Registered: January 2021
Location: Austin
Member
No. No applications on the local area network. I'm hooked to a cisco switch, which is the only thing between the server and the DM. I am on the same vlan/gateway as the device master. I could believe the wider area network on the other side of the gateway may have software like that, but our comm doesn't leave the local vlan. I regularly broadcast to devices on the vlan if i need to discover them, and even do dns inside the gateway sometimes. I can't just change things in production without written consent and approval...so I won't be able to change it now until next Monday most likely, as changes can mean possibly losing uptime and therefore $.

After changing settings for this, do I need to reload the driver to make it re-parse the /etc/nslink.conf? Is there a chance this might cause a need to reboot the machine? We've seen troubles reloading the driver when applications may or may not be using the serial ports. Theses problems often trick the OS into believing the driver is still loaded, even though it isn't.
Re: DeviceMaster RTS 32 Periodic Network Dropout [message #1303 is a reply to message #1302] Fri, 29 January 2021 07:44 Go to previous messageGo to next message
Kurt is currently offline  Kurt
Messages: 288
Registered: July 2016
Location: Minnesota
Power User
Changing the Network -> Security settings should affect the driver. No need to reload.
The settings basically help narrow down who and how the other network entities interact with the DeviceMaster on the network.

Kurt


Kurt Rees
www.comtrol.com
http://forum.comtrol.com/

Comtrol Corporation
100 Fifth Ave NW
Minneapolis, MN. 55112
Direct +1 763.957.6000 | +1 Fax (763) 957-6001
connect. communicate. control
Re: DeviceMaster RTS 32 Periodic Network Dropout [message #1304 is a reply to message #1303] Fri, 29 January 2021 09:39 Go to previous messageGo to next message
imissmyrocket is currently offline  imissmyrocket
Messages: 15
Registered: January 2021
Location: Austin
Member
There should not be anything else communicating with the DeviceMaster. I have to wait until next week to try the suggested changes, and those I have to roll out through the test site first for a day or two, then to production. Hopefully all will be allowed to start Monday Sad

I logged in today, (since I constantly have people calling and complaining) and it is really getting bad. It varies with load like I said, and the load is high today. I'll post a screenshot of what I'm seeing in the files below, but it certainly looks like it iks on a 90 second timer. When load is high I lose connection between around 90 and 91 seconds after it says connected. Like clockwork. Given this is a message from the driver, the 90 seconds must be coming from the driver, downstream, or closer to the metal somewhere.

I don't have any of the timers set to 90 seconds, so I'm wondering where this is coming from, if I knew that I might be able to determine root cause.I do not have any settings set to 90s. I see a 60 and 300 second timeout in the webgui, and a default 120s timeout on no the ports. Then there is a 15s keepalive, but that is it. Is there a timer on the FW end going for 90s, I didn't see one in the driver. Given it is relative to "Connected." message, it must be related to the DM software.

Also, can you point me to older versions of FW for the DeviceMaster FW? I was hoping to try an older FW. They don't seem to be online, it just points me to you all.
  • Attachment: nslink.png
    (Size: 674.88KB, Downloaded 79 times)
Re: DeviceMaster RTS 32 Periodic Network Dropout [message #1305 is a reply to message #1304] Fri, 29 January 2021 10:57 Go to previous messageGo to next message
Kurt is currently offline  Kurt
Messages: 288
Registered: July 2016
Location: Minnesota
Power User
I will ask our Linux developer what the nslink messages mean. I will get back to you when I hear back.
Just to confirm, you won't be able to make the Network -> Security changes until Monday?

We will try and see what is going on with this.

If the changes don't work, we will most likely need logging from the diagnostic port and Wireshark.

I would be able to provide an earlier version of firmware, but it may not have the IP Address lock down function, which could resolve the issue.
Here is a link for earlier version of binaries (folder 3), along with other material.

https://files.comtrol.com/contribs/devicemaster/driver-packa ges/current/devicemaster_1206_package_Rev_2.zip

Kurt





Kurt Rees
www.comtrol.com
http://forum.comtrol.com/

Comtrol Corporation
100 Fifth Ave NW
Minneapolis, MN. 55112
Direct +1 763.957.6000 | +1 Fax (763) 957-6001
connect. communicate. control
Re: DeviceMaster RTS 32 Periodic Network Dropout [message #1306 is a reply to message #1305] Fri, 29 January 2021 11:09 Go to previous messageGo to next message
Kurt is currently offline  Kurt
Messages: 288
Registered: July 2016
Location: Minnesota
Power User
I asked our developer about the messages.

It means that the nslinkd daemon shut down (or perhaps closed) the socket. but it never does that without messages in syslog showing what's wrong.

There weren't any syslog messages from nslinkd?

He also wants to know how the messages were obtained that you provided.

Kurt


Kurt Rees
www.comtrol.com
http://forum.comtrol.com/

Comtrol Corporation
100 Fifth Ave NW
Minneapolis, MN. 55112
Direct +1 763.957.6000 | +1 Fax (763) 957-6001
connect. communicate. control
Re: DeviceMaster RTS 32 Periodic Network Dropout [message #1307 is a reply to message #1306] Fri, 29 January 2021 12:30 Go to previous messageGo to next message
Kurt is currently offline  Kurt
Messages: 288
Registered: July 2016
Location: Minnesota
Power User
It would be really useful to capture both the syslog (which has messages from nslinkd) and kernel log (which has messages from the nslink kernel module). What you provided looks like only the kernel log

Would you be able to send those?

Kurt


Kurt Rees
www.comtrol.com
http://forum.comtrol.com/

Comtrol Corporation
100 Fifth Ave NW
Minneapolis, MN. 55112
Direct +1 763.957.6000 | +1 Fax (763) 957-6001
connect. communicate. control
Re: DeviceMaster RTS 32 Periodic Network Dropout [message #1308 is a reply to message #1303] Fri, 29 January 2021 15:03 Go to previous messageGo to next message
imissmyrocket is currently offline  imissmyrocket
Messages: 15
Registered: January 2021
Location: Austin
Member
There isn't anythiing in the log file except start up generally. It seems when it reboots it wipes the log? I will get it for you as soon as I can reconnect to that network. LIke I said, security is tight.

On Monday I can put the proposed changes on a test site, which isn't as busy. I have to prove that we aren't going to make things worse before I can proceed with releasing to production. That will take 1 day of operation that isn't any more degraded than it currently is. Unfortunately the test site doesn't have these same issues, so that is fairly useless.

On Tuesday night I should be able to put it in.
Re: DeviceMaster RTS 32 Periodic Network Dropout [message #1309 is a reply to message #1307] Fri, 29 January 2021 15:12 Go to previous messageGo to next message
imissmyrocket is currently offline  imissmyrocket
Messages: 15
Registered: January 2021
Location: Austin
Member
Not the same device I sent yesterday, I believe this one is running 11.24 or something? Anyhow, I have access to it, so I'd figure I'd grab it. It seems to be doing pretty much the same thing. and this one has some messages, the newer ones don't have anthing except the idle messages and the boot messaages.
Re: DeviceMaster RTS 32 Periodic Network Dropout [message #1310 is a reply to message #1307] Fri, 29 January 2021 15:13 Go to previous messageGo to next message
imissmyrocket is currently offline  imissmyrocket
Messages: 15
Registered: January 2021
Location: Austin
Member
Sorry..one more question. You mentioned doing wireshark. This is a windowless linux system, so I have tshark (the command line version). Do you have a capture filter you want me to catch?

Re: DeviceMaster RTS 32 Periodic Network Dropout [message #1311 is a reply to message #1310] Fri, 29 January 2021 15:56 Go to previous messageGo to next message
Kurt is currently offline  Kurt
Messages: 288
Registered: July 2016
Location: Minnesota
Power User
No, capture everything when we get to that point. When you do the packet tracing.

Kurt


Kurt Rees
www.comtrol.com
http://forum.comtrol.com/

Comtrol Corporation
100 Fifth Ave NW
Minneapolis, MN. 55112
Direct +1 763.957.6000 | +1 Fax (763) 957-6001
connect. communicate. control
Re: DeviceMaster RTS 32 Periodic Network Dropout [message #1313 is a reply to message #1311] Mon, 01 February 2021 14:01 Go to previous messageGo to next message
imissmyrocket is currently offline  imissmyrocket
Messages: 15
Registered: January 2021
Location: Austin
Member
log file for original DM attached. I'm also attempting another re-balance of priorities. It is for sure affected by how much time the kernel driver gets to run.

I just wish I knew why....that is really all I need to know to work around the problem. Seems like the device master should not have anything deadline oriented going on except the previously mentioned timeouts, and even then a kernel message is enough. Don't need it rebooting.

Re: DeviceMaster RTS 32 Periodic Network Dropout [message #1314 is a reply to message #1313] Mon, 01 February 2021 15:20 Go to previous messageGo to next message
Kurt is currently offline  Kurt
Messages: 288
Registered: July 2016
Location: Minnesota
Power User
Hi,

This is after making changes to the Network -> Security settings?

What firmware are you running?

The log doesn't look like there's any problems. The logs are volatile so reset after a reboot.

The developer would like to see the syslog and kernel log messages from the host running the nslink driver for the timeframe of the error.

There's another thing to try. I will send it in another follup-up.



Kurt Rees
www.comtrol.com
http://forum.comtrol.com/

Comtrol Corporation
100 Fifth Ave NW
Minneapolis, MN. 55112
Direct +1 763.957.6000 | +1 Fax (763) 957-6001
connect. communicate. control
Re: DeviceMaster RTS 32 Periodic Network Dropout [message #1315 is a reply to message #1313] Mon, 01 February 2021 15:23 Go to previous messageGo to next message
Kurt is currently offline  Kurt
Messages: 288
Registered: July 2016
Location: Minnesota
Power User
One more thing you can try is disabling diagnostic command handling on port 4607. If something is opening a TCP connection to port 4607 and writing garbage, it can disrupt normal operation. [If it's some host other than the nslink host doing that, then limiting the IP address should prevent that also.] There's no webui access to the diagnostic command disable flag, but you can see it via ssh/telnet:

$ telnet <dm_ip_address>

Connected to <dm_ip_address>.
Escape character is '^]'.

Password: <hit the enter key>

Pepperl+Fuchs Comtrol DeviceMaster UP ModelID: 5002697

SocketServer 11.50
Built: Mon Sep 28 16:12:24 CDT 2020
IP Addr: 10.0.0.104, Mask: 255.0.0.0, Gateway: 0.0.0.0
MAC Addr: 00:c0:4e:48:02:68

dm> show network

[NETWORK]
Ipv4Addr=10.0.0.104
Ipv4Mask=255.0.0.0
Ipv4Gate=0.0.0.0
SecureConfigEnable=0
SecureDataEnable=0
TelnetEnable=1
SecureMonitorEnable=0
SnmpEnable=1
NSLinkEnable=1
Ipv6mode=Disabled
Ipv6Addr=fdfe:dcba:9876:10::104
Ipv6PrefixLen=64
Ipv6Gateway=fdfe:dcba:9876:10::1
BootTimeout=4
TelnetTimeout=300
>>>> DiagCommandDisable=1
MinSslVersion=TLSv1.0
RestrictTcpSource=no
TcpSourceAddr1=
TcpSourceWidth1=0
TcpSourceAddr2=
TcpSourceWidth2=0

It defaults to 1 (commands disabled) on new units or when reset to factory defaults. But when units running 11.33 or older are upgraded, it remains 0 (commands enabled) to preserve backwards compatible behavior.

You can set/clear it manually via telnet/ssh with the "set" command (you need to do a "save" after changing things with the "set" command):



dm> show network DiagCommandDisable
0

dm> set network DiagCommandDisable 1

dm> show network DiagCommandDisable
1

dm> save

dm>



Kurt Rees
www.comtrol.com
http://forum.comtrol.com/

Comtrol Corporation
100 Fifth Ave NW
Minneapolis, MN. 55112
Direct +1 763.957.6000 | +1 Fax (763) 957-6001
connect. communicate. control
Re: DeviceMaster RTS 32 Periodic Network Dropout [message #1316 is a reply to message #1315] Mon, 01 February 2021 21:23 Go to previous messageGo to next message
imissmyrocket is currently offline  imissmyrocket
Messages: 15
Registered: January 2021
Location: Austin
Member
That is what I said. The log doesn't have anything good in it, since it is rebooting all the time. But why is it rebooting? The older one I can't tell what it is doing, it seeems the same, but it just stops comm for 60s or so, the newer one I had a tech sit out there and watch it, he says he sees it rebooting when this happens.
Re: DeviceMaster RTS 32 Periodic Network Dropout [message #1317 is a reply to message #1316] Tue, 02 February 2021 07:03 Go to previous messageGo to next message
Kurt is currently offline  Kurt
Messages: 288
Registered: July 2016
Location: Minnesota
Power User
Hi,

Perhaps the developer might be able to pick something out that would give a better clue on what is going on.
The developer would like to see the syslog and kernel log messages from the host running the nslink driver for the timeframe of the error.
The above logs could put in the missing pieces.

Kurt



Kurt Rees
www.comtrol.com
http://forum.comtrol.com/

Comtrol Corporation
100 Fifth Ave NW
Minneapolis, MN. 55112
Direct +1 763.957.6000 | +1 Fax (763) 957-6001
connect. communicate. control
Re: DeviceMaster RTS 32 Periodic Network Dropout [message #1318 is a reply to message #1317] Wed, 03 February 2021 22:45 Go to previous messageGo to next message
imissmyrocket is currently offline  imissmyrocket
Messages: 15
Registered: January 2021
Location: Austin
Member
I'll send you the logs via email. I can't post them here because of security concerns. I have sent you the relevant parts already above. What I am packing up is just a repeat of the same stuff.

I get the send_shutdown==1 and the thing reboots. it is just a repeat of what I sent above over and over. I don't know how many times or different ways I can ask this, I would appreciate an answer if you guys can give it. IS THERE A BRANCH of code in the DM firmware that causes the DM to restart itself? If so, what are the reasons it would do that?

If there isn't, we should just start packing up HW and sending it back, right? HW that is restarting when it isn't supposed to would be only something you could blame on power, and we are continually monitoring our conditioned power supply. There isn't anything wrong with it. SO either the DM is rebooting itself or it isn't, based on communication with the driver or serial ports. Seems pretty cut and dry, isn't it?

I finally got to try the new settings last night. Bedsides now rejecting technicians attempts to connect with a browser when it dies/restarts, (which I had to re-enable using telnet with the TcpSourceAddr1 and TcpSourceAddr2 flags with width1 and2 - thanks for that), it didn't really change anything. I could see the rejected attempts to connect, but if anything the problem was aggravated again today, because of high load. It was much worse than the day before, but the day before there was bad weather outside, which can lighten the IO load in this application.

It seems obvious the DM is getting starved for some type of servicing. I just want to know what it is it needs.
Re: DeviceMaster RTS 32 Periodic Network Dropout [message #1329 is a reply to message #1236] Mon, 01 March 2021 08:51 Go to previous messageGo to next message
imissmyrocket is currently offline  imissmyrocket
Messages: 15
Registered: January 2021
Location: Austin
Member
Hey Gents,

Some feedback for you. On the server side we are for sure having issues with kernel loading...the workqueue gets large for a bit, and some kernel drivers for sure get prioritized, knocking the nslink down the chain and delaying it's processing.

I found a working version combination for us, which is SocketServer 11.30 with kernel driver 8.00. Everything else I have seems to drop data or worse, reboot the DM and start up the bootloader. I never heard from engineering.
Re: DeviceMaster RTS 32 Periodic Network Dropout [message #1330 is a reply to message #1329] Tue, 09 March 2021 09:01 Go to previous message
Kurt is currently offline  Kurt
Messages: 288
Registered: July 2016
Location: Minnesota
Power User
Can you run a wireshark with this happening and send the log? Provide the IP Addresses of the hardware involved to make it quicker to track things down.

Kurt


Kurt Rees
www.comtrol.com
http://forum.comtrol.com/

Comtrol Corporation
100 Fifth Ave NW
Minneapolis, MN. 55112
Direct +1 763.957.6000 | +1 Fax (763) 957-6001
connect. communicate. control
Previous Topic: Certificate of Volatility P/N99456-5
Next Topic: Differences between DeviceMaster RTS devices
Goto Forum:
  


Current Time: Sun May 16 03:31:46 CDT 2021

Total time taken to generate the page: 0.00926 seconds