Adding IP Address to Allow Discovery of a Device

[ljacobs16]

We have a list of IP Address that are not found in our FlexNet Manager Suite, but we received these IP Address from a Server Team to get them added in Flexera. What is the process to get these added? Is there a step by step guide to get additional Servers discovered by adding the IP Addresses?

[Natalie]

You will need to add these IP address ranges to the Sites and Subnets page, and then assign them to a beacon. 

[ljacobs16]

Hi Natalie, we did that but it seems we are still having trouble getting them to show up in our Discovery and Inventory. We know the IP addresses we have are live. Do you know if anyone has a step by step guide? Maybe we are not doing it correctly. Thanks!

[statler · Accepted solution]

Remember that computers must respond to a PING (ICMP) request to be discovered sucessfully.

Typically, the required steps would be:

1. Add the IP adresses as a new site to the "Discovery & Inventory > Network > Subnets" page. In case you want to target specific IP adresses, you can assign multiple "One IP network" with a /32 network mask to your site, like 172.31.0.15/32.
2. Make sure that all subnets are assigned to a Beacon. 
   Use the "Discovery & Inventory > Network > Unassigned Subnets" page for assigning
   multiple subnets to the same Beacon in a single step.
3. Under "Discovery & Inventory > Discovery > Discovery and Inventory Rules"
   locate the rule that is being used for discovering servers. Open the rule
   to find which targets are used for this rule.  
4. Again under "Discovery & Inventory > Discovery > Discovery and Inventory Rules",
   locate the target that you identified in the previous step and open it for editing.
   In the list "Define machines to target", make sure that the new/updated subnet is included. Save your target after updating it.
5. Make sure the updated rule information (with the updated target) is downloaded to the Beacon assigned to the IP subnet (see step #2). You can enforce immediate updating by using the "Update Rules" button in the "Rules" section in the Beacon UI.
6.  On the Beacon, you can trigger the immediate execution of the rule by selecting it in
   the "Rules" section and clickin on the the "Run" button.
7. Discovery results will be visible in the FNMS Web UI immediately (without Compliance Import). In case the servers are not being discovered immediately, check the LOG files on the Beacon (inventorybeacon.log, beaconEngine.log) for further information. You can also enforce additional logging by editing the \Program Files (x86)\Flexera Software\Inventory Beacon\etdp.trace file.
   
   Hope this helps :-).

[mfranz]

This is a very nice description.

Maybe an idea if the discovery still fails. Try ping, nslookup and/or telnet  to reach some sample machines in the  targeted range. There might still be a  routing issue or firewall blocking your access.