MgsSubnetMatch: Match to Subnet

IT Asset Management (Cloud)

This algorithm scans through all inventory beacons in the subnet containing the target inventory device and moves them to the front of the priority list, while retaining the relative order of existing priorities.

This is particularly useful if combining with other algorithms, such as

MgsPing;MgsSubnetMatch

This combination provides a resultant set of priorities based on the fastest responding servers within the current subnet, followed by the fastest responding servers outside the subnet.

MgsSubnetMatch (int limit, boolean discardForeign)

where:

• limit is an optional integer setting the maximum number of inventory beacons to which priorities will be assigned by this algorithm.
• discardForeign is an optional boolean represented by the case-insensitive strings true or false. The default is false.
  • If false or omitted, the algorithm assigns a lower priority to inventory beacons that are not matched by the algorithm than to all those that are matched.
  • If true, the algorithm sets the priorities of any unmatched inventory beacons to the string literal invalid. The launcher component and the upload component will not use such inventory beacons for transfers.

Example of MgsSubnetMatch algorithm results

For a target inventory device with:

• IP address: 172.16.34.53
• Subnet mask: 255.255.248.0
• Subnet: 172.16.34.0

In the following table, the bandwidth and IP address are for each inventory beacon under consideration.

Location	Bandwidth	IP address	Incoming priority	Resulting priority
Location A	LAN (100Mbps)	172.16.45.40	1	3
Location B	LAN (10Mbps)	169.15.13.12	2	4
Location C	WAN (56K modem)	172.16.34.40	4	2
Location D	WAN (ADSL)	172.16.34.60	3	1

In the above example:

• Location C and D are in the same subnet as the client, and therefore have higher priority than A and B.