MgsIPMatch: Match to IP Address

FlexNet Manager Suite 2021 R1 (On-Premises)

This algorithm prioritizes inventory beacons based on similarities in the IP address of the target inventory device and each inventory beacon. Address components are converted to binary numbers and compared, left to right. Priority is assigned according to the longest common (matching) bit in the binary number.

By comparing the IP address of the inventory device against each inventory beacon, any inventory beacons within a subnet will be given higher priority because the network address portion of the IP will be the same. If two inventory beacons are within the same subnet, then the value of the local host ID determines the priorities of the two inventory beacons.

MgsIPMatch (int limit)

where:

• limit is an optional integer setting the maximum number of inventory beacons to which priorities will be assigned by this algorithm.

Example of MgsIPMatch algorithm results

For a target inventory device with IP address 123.3.45.44.

Tip: This algorithm only supports the IPv4 address family.

Location	IP address of inventory beacon	AutoPriority	Incoming priority	Resulting priority	Normalized priority
A	123.3.45.56	true	blank	21	2
B	123.3.44.46	true	blank	42	3
C	123.5.45.56	true	blank	63	4
D	123.3.45.32	true	blank	14	1
E	123.3.45.42	false	5	5	5

In the above example:

• Location A matches the first three domain components, so there is little binary difference from the managed device’s IP address. The algorithm assigns a high priority (for example 20). It is then indexed by the order of location entries in the registry. Location A is first in the list, so the priority is recalculated as 20+1 (21).
• Location B matches on the first and second address components and has a greater binary difference than location A. It is given a medium high priority (for example, 40). This is indexed and the priority is recalculated as 40 + 2 (42).
• Location C matches the managed device on the first domain component and the third component, but not on the last address component. It has a high binary difference and is given a low priority (for example, 60). This is indexed and the priority is recalculated as 60 + 3 (63).
• Location D is similar to location A because it doesn’t match the last domain component of the managed device, but it does match on the first three domain components. It actually has a smaller binary difference, and is assigned a very high priority (for example, 10). It is then indexed by the order of location entries in the registry; it is fourth in the list, so the priority is recalculated as 10 + 4 (14).
• Location E has a fixed priority, so priority 5 is unchanged by the algorithm.
• The NetSelector normalizes the priorities of locations A to D to fit within the range specified by the server selection settings (described in Prioritizing Inventory Beacons). In this example, the range is 1-5.