As touched upon in another thread, I've been plagued with XAP issues and could never keep XAP running long enough to even get a feel for XAP. After a bit of research, here is a summary of my issues and what I've found.
First off, xFx-Express Hub reports the following:
09-Aug-13 23:15:40.2 ERROR Hub message loop socket exception (MessageSize): A me
ssage sent on a datagram socket was larger than the internal message buffer or s
ome other network limit, or the buffer used to receive a datagram into was small
er than the datagram itself
09-Aug-13 23:16:23.4 INFO Selected Ethernet network interface 'Local Area Conne
ction' AMD PCNET Family PCI Ethernet Adapter - Packet Scheduler Miniport
Now, when this happens, you can see by the time stamps, the hub is recycling and stops listening for about 40 seconds. Now, using Wireshark, I found that fragmented UDP packet are getting sent out by the mcsXAP plugin, which is what is causing the hub to drop and recycle, and is what is knocking an unrelated network device off my network.
Now, the interesting part, it appears that certain devices that are getting updated is what is triggering the bad UDP packets. I turned off one particular event that runs a script, problem solved. The script in question is non other then the Jon00PerMon.vben, Jon00's performance monitor. My conclusion is device strings that contain heavy HTML, maybe referencing images, are what's causing the UDP fragments. What I can tell you with certainty is as long as the script doesn't run, everything is fine, the second I manually run the script, I get the message from the hub, pasted above, thus the fragmented UDP packet.
Now, as near as I can tell, there is no way to stop device updates from getting sent out via XAP, as near as I can tell, every single device update gets transmitted, am I wrong here? If I could stop mcsXAP from sending the problematic devices, all would be fine.
Thoughts???
First off, xFx-Express Hub reports the following:
09-Aug-13 23:15:40.2 ERROR Hub message loop socket exception (MessageSize): A me
ssage sent on a datagram socket was larger than the internal message buffer or s
ome other network limit, or the buffer used to receive a datagram into was small
er than the datagram itself
09-Aug-13 23:16:23.4 INFO Selected Ethernet network interface 'Local Area Conne
ction' AMD PCNET Family PCI Ethernet Adapter - Packet Scheduler Miniport
Now, when this happens, you can see by the time stamps, the hub is recycling and stops listening for about 40 seconds. Now, using Wireshark, I found that fragmented UDP packet are getting sent out by the mcsXAP plugin, which is what is causing the hub to drop and recycle, and is what is knocking an unrelated network device off my network.
Now, the interesting part, it appears that certain devices that are getting updated is what is triggering the bad UDP packets. I turned off one particular event that runs a script, problem solved. The script in question is non other then the Jon00PerMon.vben, Jon00's performance monitor. My conclusion is device strings that contain heavy HTML, maybe referencing images, are what's causing the UDP fragments. What I can tell you with certainty is as long as the script doesn't run, everything is fine, the second I manually run the script, I get the message from the hub, pasted above, thus the fragmented UDP packet.
Now, as near as I can tell, there is no way to stop device updates from getting sent out via XAP, as near as I can tell, every single device update gets transmitted, am I wrong here? If I could stop mcsXAP from sending the problematic devices, all would be fine.
Thoughts???
Comment