Summary
This article describes the issue that some machines in the range of the subnets setting may be classified in "Unmanaged Devices" when they have multiple IP addresses and how to avoid the issue.
Symptoms
Some machines are listed in "Unmanaged Devices" even if the inventory source of these machines is "FlexNet Manager Suite" or IP addresses are in the range of subnets.
Cause
FlexNet Manager Suite (FNMS) discovers machines deployed in the range of subnets by IP addresses and associate an IP address with a machine when responded. The discovered devices are listed in "All Discovered Devices". But, the discovery process doesn't recognize if each machine has multiple NICs or IP addresses and only one IP address is stored for a machine during the discovery process. That if the machines has multiple IP addresses is not recognized until inventory data is collected. When FNMS creates "Unmanaged Devices" list, it examines if the stored IP address is in the range of subnets.
So, if a machine has multiple IP addresses, it is listed in "Unmanaged Devices" in the following scenario. Suppose if a machines has 2 IP addresses as "aaa.aaa.aaa.aaa" and "bbb.bbb.bbb.bbb" and that the former one isn't in the range of subnets and the latter one is. If the machine is discovered by "aaa.aaa.aaa.aaa", FNMS stores the IP address and link it to the machine. When "Unmanaged Devices" list is created, FNMS examines if "aaa.aaa.aaa.aaa." is in the range of subnets and list the machine because "aaa.aaa.aaa.aaa" is not in the range. From this behaviour, it is possible that the machine is listed in "Unmanaged Devices" list even when "bbb.bbb.bbb.bbb" is in the list and the machine has agent installed.
Steps To Reproduce
1) The client machine has multiple IP addresses.
2) Confirm at least one IP address is not in the range of subnet settings.
3) Confirm the machine is discovered by the IP address that is not in the range by checking "IP address" column in "All Discovered Devices" page.
4) The machine is listed in "Unmanaged Devices" list.
Resolution
Please include the IP address in the subnet settings.
