Pulse secure article: 6358 – vtm – ip from the physical interface information
Even though the default Ip from the physical interface can be used to talk with the rear finish nodes, you are able to change this conduct by developing a Traffic IP (TIP) after which using custom static routing to map that TIP address towards the specified host. When utilizing an online appliance (Veterans administration), the network configuration ought to be transported out underneath the System > Networking tab.
Custom static routing can be achieved on Linux using the following command:
route add -host dev
Even though the default Ip from the physical interface can be used to talk with the rear finish nodes, you are able to change this conduct by developing a Traffic IP (TIP) after which using custom static routing to map that TIP address towards the specified host. When utilizing an online appliance (Veterans administration), the network configuration ought to be transported out underneath the System > Networking tab.
Custom static routing can be achieved on Linux using the following command:
route add -host dev
Which means this may seem like:
Traffic Manager IP – 192.168.98.50 (eth0)
Traffic IP – 192.168.98.52 on eth0:2
Backend Webserver IP – 192.168.98.51
Automatically, the 192.168.98.50 address can be used to talk with the net server, however if you simply give a custom static route the following, then your TIP can be used for communication with backend.
# route add -host 192.168.98.51 dev eth0:2
For those who have a small amount of Ideas to communicate to some pool of back-finish servers, this could permit you to by hand load balance across these back-finish servers with the addition of customer routes via their alias. Ex. node1 via TIP1, node2 via TIP2, etc…
NOTE: This solution might not be well suited for a lot of services and TIPS and wouldn’t safeguard against failover (unless of course there’s a cluster for redundancy) or maybe the machine is rebooted.
Resourse: https://kb.pulsesecure.internet/articles/Pulse_Secure_Article/