There really needs to be a better way than setting up so many net_connect probes and profiles.
Where I work we have a multi-tennant environment. We have HUB servers in each tenant environment.
We would have to setup the net_connect probe on every tenants hub server, and then configure a net_connect profile for every target ROBOT in every tenant hub. THat sucks.
Seems that when you are logged into the primary hub and have infrastructure manager open, you can hit "F5" to refresh the Domain tree of origins and robots. If a Robot is down or not responding it turns red fairly instantly.
Why not have a Primary HUB based probe that alarms to the NAS if any Robot is in a RED state?
That is what I really want. It would dynamically include all new robots setup in the future that way.
And it would just need to poll every 3 minutes or so and return one alarm for each Robot in a RED state.
Anyone know how to do that?
-Ben.