if flags = 2 or 3, offline field = 1
if flags = 0 or 1, offline field = 0
When a robot comes online it takes the configured hub's name and does a nametoip call. For example, robot.cfg had the hub configured as /domain/hub/robot the robot will do a nametoip to resolve the Nimsoft name to the hub's ip address.
Robot will then attempt to contact that hub on it's IP address. If contact cannot be made it will then try the secondary hub's name and then its ip address.
If that does not work the robot will do a generic get hub call. The robot will attach to the nearest hub responding to the above sequence of calls. The robot should continue to look for it's Primary hub.
Does anyone have any experience with the UMP and firewalls and accessing robots? For example, in our environment we have a server that's in a special network segment that's behind a firewall. Our nimsoft server lives in another general network area. To get the two to communicate, we had to open up ports 48000 to 48030 between the two hosts with bi directional traffic. They communicate fine. With that configuration though, if I am at my computer I work from and I try to connect to that robots probes in the special segment, I can't reach it due to its firewall location and I get that and that's ok, but not desirable. One major thing I've noticed now though, is if I log into UMP and use the Maintenance Mode portlet to put that robot in maintenance mode, UMP can't connect to it. So UMP (presumably the UMP server) needs to have a firewall rule to allow bidirectional traffic between the robot and it too?
Download Nimsoft Robot
DOWNLOAD 🔥 https://urluso.com/2yGco8 🔥
Yes, any machine that you want to be allowed to communicate with robots needs to have the ports opened. If you are running Infrastructure Manager on a PC, you would need to have the ports open to the robots from the PC. If you are opening the ports on a stateful firewall, you should only have to open them in one direction (to the robot), as return traffic would be automatically allowed.
The one exception to this is when you are using hub-to-hub tunnels. Then you just need direct access to the "near" side of the tunnel, and the hub on the "far" side of the tunnel is the only thing that requires the ports open to the robot. If you do not want to setup a hub in the special network segment, you could just install the hub on the server you are trying to access and setup a tunnel. The hub does not consume much memory or CPU.
The whole architecture around Nimsoft is to be able to distribute things and minimize dependencies. Nearly every probe listens on a TCP port of its own so that you can talk to it directly without even going through the robot/agent/service/controller. This design has a variety of advantages and disadvantages.
We set a range of ports to be used by all robots. This range of ports is open for the hubs that the robots are attached to plus a dedicated machine that runs Infrastructure Manager so that configs could be done, but not the UMP's. this worked well for us. 152ee80cbc
computer chess game software free download
workzone endoskop kamera treiber download