Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Server & Application Monitor (SAM) > SAM Documentation > SAM 6.7 Administrator Guide > What is High Availability in SAM > Which IP address is used as the source for HA in SAM

Which IP address is used as the source for HA in SAM

Updated February 7, 2018

This Orion Platform topic applies to the highlighted products:

DPAIMEOCETSIPAMLMNCMNPMNTASAMSRMUDTVMANVNQMWPM

Outbound communication from the HA pool, such as WMI or SNMP polling requests, may be sent by the primary or secondary server's IP address or the VIP address. All inbound communication goes through the VIP address.

The active pool member has a minimum of two IP addresses available: the IP address of the server and the VIP address for the pool.

Because there are multiple IP addresses bound to a single NIC, Windows chooses which IP address is used as the originating IP address. The IP address with the most high order bits that match the destination of the next hop is used as the source IP address for all outbound polling activity.

You can determine the source IP address by doing the following:

  1. Convert the IP addresses to binary.
  2. From left to right, compare how many bits in the IP addresses match the default gateway's IP address.

The IP address with the most consecutive, matching bits is used for the HA pool's source IP address.

Choose an IP address close to the default gateway's IP address so outbound communication comes from the VIP address. You can also modify the converted bits to be the IP address with the longest match and convert it back to an IP address.

All local (same subnet as the Orion server) traffic will source from the "first" address or native.

Examples of matching the binary bits

The following is an example where the VIP is used as the outbound IP address.

  IP address IP address converted to binary # of matching bits
Default Gateway (first hop) 10.199.15.1 00001010-11000111-00001111-00000001  
VIP 10.199.15.20 00001010-11000111-00001111-00010100 27
Primary pool member 10.199.15.61 00001010-11000111-00001111-00111101 26
Secondary pool member 10.199.15.62 00001010-11000111-00001111-00111110 26

The longest match in the example above is the VIP. It has 27 consecutive matching high order bits to the default gateway.

The following is an example where pool members' IP addresses are used as the outbound IP address.

  IP address IP address converted to binary # of matching bits
Default Gateway (first hop) 10.199.15.1 00001010-11000111-00001111-00000001  

VIP

10.199.15.82 00001010-11000111-00001111-01010010 25
Primary pool member 10.199.15.61 00001010-11000111-00001111-00111101 26
Secondary pool member 10.199.15.62 00001010-11000111-00001111-00111110 26

In this example, the longest match is the pool members' IP addresses. When a failover occurs, the IP address of the active Orion server is used as the source IP for all polling requests. The VIP address is only used for inbound traffic, such as syslog, SNMP traps, NetFlow, and accessing the Orion Web Console.

 
Last modified

Tags

Classifications

Public