On the bottom half of the screen is section called Capture.This is accomplished either via a port-mirroring switch, or by setting up port-mirroring on the existing system switch (which is only possible if an existing port is open and the folks managing the network will allow it). The computer will need to see the exact data being sent to the the gateway. In the first example above, if a DMX Gateway is not receiving sACN lighting level information, it will do us no good to plug the computer into a random network port or directly into a network switch port. Expanding on that notion, Wireshark only captures network information that is being accessed by the computer hosting the software. With each of these examples, it becomes critical to determine where to place the computer that will run Wireshark. Probable Cause: Ring Network Topology (Closed Loop) and Spanning Tree is disabled -OR- duplicate IP addresses are causing an IP conflict.ETC devices continuously reboot while they are plugged into a network.
Paradigm Architectural Control Processors (PACPs) not seeing one another.Probable Cause: End of Line termination may not be accepted or set correctly.Serial (Network UDP) communication is not present between ETC and third-party controllers.Probable Cause: Multicast is being blocked.DMX Gateway is not receiving sACN lighting levels from the network.This will vary based on the type of connectivity problems that are occurring.īelow are examples of common networking problems Wireshark may be useful: ETC Technical Support Specialists will help direct the discussion about where the best place to take the capture is.Īs Wireshark is generally used to troubleshoot communication between two networked devices, it is important to discuss where the suspected problem is in the network.
0 kommentar(er)
