Discovery - IP Address Range vs IP Network

[poyntzj]

Is there a preference when configuring the discovery ranges to use IP Address Range vs IP Network ?

Also, for some locations there are two or three user VLANs that are continuous in their addressing

a.b.1.0/14

a.b.2.0/24

a.b.3.0/24

Is it best to

• create 3 IP networks ?
• create 3 IP Address ranges
• create a large IP Address range

I ask as I am finding a few oddities with some of our scans (including missing devices from a scan), but when I scan that address manually it works fine.

I just wonder if any of the above have implications and could be contributing

cheers

[poyntzj]

test

[poyntzj]

209.90.41.2

EXT\_WWGRM.ServiceNowMGT

I have gone through a similar process

We have management who think a "spreadsheet" is gospel - I know it is poor as it still has our old Domino servers (I retired the last one last year and the NTAM team removed it as per the Request / Change)

When we had our instance configured it was not the greatest with regards to discovery so I have worked on it over the last few months (I had a debate about deleting all existing records, or as I have done, mark old records as retired) and I am now confident it is pretty good.

On Thursday I got all the data from the Servicenow CMDB, our LANDesk cores for each region, all our devices from AD, the "spreadsheet" and did a compare.

Servicenow was pretty good bar a few servers, which we found a number are sitting on users VLAN's (they are pxe rep's so understandable) and a few that it had not found

On scanning It found 2 of the 3 - I need to investigate the missing one.

On looking at the weekend scan, I can see if found two of them, but called the VMH name and not the device name - I need to check that again next week.

My reason for asking is that I am sure I read something in one of the "Support" questions and someone mentioned it - be buggered if I can find that question again.

Cheers

[Ankush13]

Share it if you get your hands on that post again.

VMH can be due to a process that is running on one of the windows servers. Try discovering them individually and see what comes up.