Anyone know if it is possible to force or bind the agent to use a specific interface to talk to the polling engines?
what's the use case? What are you trying to accomplish?
Neverfail runs on these systems...tiertiary mode -> two systems are oddly "ghosted" and one is active. We are trying to figure out how to monitor the ghosted systems.
each system has 3 interfaces on same subnet and does interesting things with local host route table.... "management" interface is able to talk to monitoring servers, but is not the primary interface the OS has deemed to use.
One option is to set host based route for monitoring network, not sure what impact that would have on neverfail.
We are researching both paths.
so use case is, I would love to be able to go into agent config file or the like and put <interface used>managment</interface used> or something similiar to bind the agent app to utilizing a specific interface.
Similiar to how IIS can bind a site to an interface....thanks @aLTeReGo
Assuming the Orion poller and Neverfail servers are on different subnets, you could create a static route on the Neverfail server. E.G.
route add 10.1.1.10 MASK 255.255.255.255 192.168.0.1
In the example above
'10.1.1.10' is the Orion server
'255.255.255.255' says "only this one IP"
'192.168.0.1' is the gateway on the interface you want the traffic routed through.
This also assumes that each interface is in its own unique subnet. If you have two or more interfaces on the same subnet, then you will need to specify the interface index ID similar to the following, where '2' is the interface index ID for the interface the traffic should be routed out.
route add 10.1.1.10 MASK 255.255.255.255 192.168.0.1 IF 2
The interface index IDs will be listed at the top of the 'route print' command, as shown below.
C:\Users\Administrator>route print===========================================================================Interface List 2...00 50 56 98 74 96 ......vmxnet3 Ethernet Adapter 1...........................Software Loopback Interface 1===========================================================================
To make the change permanent, simply add the '-p' option. E.G.
route -p add 10.1.1.10 MASK 255.255.255.255 192.168.0.1 IF 2
Yep, that is the option on the OS side, thanks for the details.we are evaluating both paths and I understand the agent binding to an interface is not an option at this time. I suspected but needed to verify.
thanks much!
