Quick Ranges Discovery - ITOM

[Sumeet Verma]

Hi All,

I'm running a quick discovery in an on demand discovery schedule.

I put 10 ips as a quick discovery and only 1 got discovered. I don't see other 9 ips, no error message for them.

where I'm suppose to see those ips if they're not reachable or something?

they're not been excluded.

[Ashutosh Munot1]

HI,

You have to check if the ports are open for this. Shazzam will only discover the CI's which will have ports open.

I think you have run a Scheduled discover not a QUICK Discover. Because quick discovery will take single IP and Mid Server.

You might have manually run scheduled discovery right?

Thanks,
Ashutosh Munot

[ACripps]

@Ashutosh Munot1 Hi Ashutosh, Is it a requirement to have a MID server present when running a Quick discovery or can you just leave it blank  ? Thanks 

[tim_broberg]

Based on the ecc_queue count, it looks like it did fully discover just one device. It didn't try to discover a bunch of others. ((1 shazzam probe + 14 probes for the device that got discovered) x 2 for input and output)

That suggests either

• you did quick discovery of only one IP rather than Discover Now of the whole schedule
• the other ports were not open.

To check the ports, go to the ecc_queue and look at the shazzam input record. You should see details on what ports were found open for which IPs.

[Sumeet Verma]

thanks Ashutosh and Tim for your views...

FYI - I'm using the Kingston Version of SNOW.

what I did was:

- for some clients reason I'm bound to use an On Demand discovery run for testing few IPs whether they get discover or not. So they have created an On demand Discovery run in the discovery schedules and I just put few IPs in the quick range, update the on demand discovery run and do Discover now.

since there becomes more quick ranges under Discovery IP Ranges, I disable all others and keep Active or True only the current quick range that I'm gonna scan. please see below screen. so in this situation discovery should happen for all 9 ips that I put under quick range.

- I saw the ECC input queue and there's a lot to find which ips got dropped from discovery for port issue or whatever reason. would you be able to advise from attached ECC input file, which line should of interest to check the dropped ips or undiscovered\unprocessed ips?

actually, I was a BMC Discovery guy and there we used to see clearly with columns like which ip was success and which were dropped, access issues etc, but here I'm finding it little difficult.

I was expecting it into a separate results column rather searching under  mix data of ECC queue and logs with mixed data.

Steps of Discovery I performed like:

1.

2.

3.

4.