UCMDB and UD Practitioners Forum (Previously CMS)
cancel

Using Range IPs by ICMP in UCMDB

SOLVED
Go to solution
Highlighted
Peter Miebach
Super Collector

Using Range IPs by ICMP in UCMDB

I'm trying to discovery my environment using the Range IPs by ICMP under the advanced mode but only the device discovered is the one that is running the DDM probe.

What could be wrong?

In the probe setup I have specified the range of IP addresses the probe should use. (see screen shots)

 

 

P.S. This thread has been moved from Application Perf Mgmt (BAC / BSM) Support and News Forum to CMS and Discovery Support and News Forum. - Hp Forum Moderator

15 REPLIES
Rutger
Frequent Visitor

Re: Using Range IPs by ICMP in UCMDB

Are you using uCMDB 8 or 9? Just curious.

 

As to your question: is it possible the active network components, like routers/firewalls are configured to disallow ICMP traffic? That could cause you to find only the local host(s).

 

-Rutger

Peter Miebach
Super Collector

Re: Using Range IPs by ICMP in UCMDB

I'm using BSM 9 and I have the DDM advanced license applied.

 

Well from the bsm probe machine I can ping other computers on the network so I believe ICMP isn't being blocked.

Rutger
Frequent Visitor

Re: Using Range IPs by ICMP in UCMDB

You could try entering your range into the Range parameter of the pattern (Discovery - Run Discovery - Range IPs by ICMP - Properties tab) and re-running the pattern. Are any other parameter check boxes marked?

 

Peter Miebach
Super Collector

Re: Using Range IPs by ICMP in UCMDB

I tried your suggestion but still only 1 device is found.

No other parameters are selected - see attached screen shot.

Peter Miebach
Super Collector

Re: Using Range IPs by ICMP in UCMDB

looking in the DDM logs I see(from probeMgr-adaptersDebug.log):

 

2011-01-18 15:11:17,555> [DEBUG] [JobExecuterWorker-0:Range IPs by ICMP] - Starting script icmp_utils.py
<2011-01-18 15:11:17,555> [DEBUG] [JobExecuterWorker-0:Range IPs by ICMP] - Finished script icmp_utils.py
<2011-01-18 15:11:17,555> [DEBUG] [JobExecuterWorker-0:Range IPs by ICMP] - Starting script IP_by_range.py
<2011-01-18 15:11:17,570> [INFO ] [JobExecuterWorker-0:Range IPs by ICMP] - Start working on total probe ranges: 1
<2011-01-18 15:11:17,570> [DEBUG] [JobExecuterWorker-0:Range IPs by ICMP] - =====>Start working on range Range: [192.168.88.0 - 192.168.88.255]
<2011-01-18 15:11:23,510> [DEBUG] [JobExecuterWorker-0:Range IPs by ICMP] - -->Result Collected IPs in range: array(['192.168.88.1', '192.168.88.4', '192.168.88.6', '192.168.88.8', '192.168.88.9', '192.168.88.10', '192.168.88.11', '192.168.88.12', '192.168.88.16', '192.168.88.30', '192.168.88.32', '192.168.88.33', '192.168.88.48', '192.168.88.49', '192.168.88.53', '192.168.88.54', '192.168.88.61', '192.168.88.63', '192.168.88.97', '192.168.88.99'], java.lang.String)
<2011-01-18 15:11:29,451> [DEBUG] [JobExecuterWorker-0:Range IPs by ICMP] - -->Result Collected IPs in range: array(['192.168.88.102', '192.168.88.103', '192.168.88.107', '192.168.88.113', '192.168.88.117', '192.168.88.118', '192.168.88.120', '192.168.88.121', '192.168.88.124', '192.168.88.125', '192.168.88.148', '192.168.88.149', '192.168.88.158', '192.168.88.164', '192.168.88.165', '192.168.88.168', '192.168.88.170', '192.168.88.174', '192.168.88.175', '192.168.88.179'], java.lang.String)
<2011-01-18 15:11:34,172> [DEBUG] [JobExecuterWorker-0:Range IPs by ICMP] - -->Result Collected IPs in range: array(['192.168.88.254', '192.168.88.254', '192.168.88.252:192.168.88.255', '192.168.88.32:192.168.88.255', '192.168.88.253:192.168.88.255', '192.168.88.33:192.168.88.255', '192.168.88.30:192.168.88.255', '192.168.88.250:192.168.88.255', '192.168.88.252:192.168.88.255', '192.168.88.253:192.168.88.255', '192.168.88.250:192.168.88.255', '192.168.88.32:192.168.88.255', '192.168.88.33:192.168.88.255', '192.168.88.30:192.168.88.255'], java.lang.String)
<2011-01-18 15:11:34,172> [DEBUG] [JobExecuterWorker-0:Range IPs by ICMP] - =====>Done working on range Range: [192.168.88.0 - 192.168.88.255]
<2011-01-18 15:11:34,172> [INFO ] [JobExecuterWorker-0:Range IPs by ICMP] - Finished working on all Probes Ranges..
<2011-01-18 15:11:34,187> [DEBUG] [JobExecuterWorker-0:Range IPs by ICMP] - Finished script IP_by_range.py
<2011-01-18 15:11:34,187> [DEBUG] [JobExecuterWorker-0:Range IPs by ICMP] - Framework Range IPs by ICMP8c0cfa91dab026f5ac697ff66dd61fca: closing all resources
<2011-01-18 15:11:34,187> [DEBUG] [JobExecuterWorker-0:Range IPs by ICMP] - Unregistering connections (total 0) on framework Range IPs by ICMP8c0cfa91dab026f5ac697ff66dd61fca with thread Thread[JobExecuterWorker-0:Range IPs by ICMP,5,main]

Rutger
Frequent Visitor

Re: Using Range IPs by ICMP in UCMDB

Hi,

 

Have you checked if you can ping the hosts in the target range directly from the probe machine?

 

Could you check the probe's logs, e.g. wrapperprobe.log, patterndebug.log and probe-error.log for interesting messages.

 

Could you try running a sweep on your IP range using a ping sweeper like Angry IP http://www.angryip.org ?

 

Rutger

 

 

Rutger
Frequent Visitor

Re: Using Range IPs by ICMP in UCMDB

Sorry did not see you last post.

 

Peter Miebach
Super Collector

Re: Using Range IPs by ICMP in UCMDB

I was reading on the old thread:

http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1295383949890+28353475&threadId=1346782

 

I'm trying to add a network ci but I can't find the network ci type in the list.

Maybe the name changed from ucmdb 8 to ucmdb 9?

Rutger
Frequent Visitor

Re: Using Range IPs by ICMP in UCMDB

Could you check the taskresults log to see if the Range pattern output was sent to the server?

Peter Miebach
Super Collector

Re: Using Range IPs by ICMP in UCMDB

I re-ran the discovery and the following appears in the probeGW-takResults.log:

<2011-01-18 16:36:56,828> 102008302 [INFO ] (TaskResultsSenderThread.java:326) - Successfuly sent task result to server. task ID: progress_Task, Job ID: 'progress_Task', Updates: 1, Deletes: 0

 

a little further up I see:

<2011-01-17 12:18:47,097> 118571 [INFO ] (TaskResultsSenderThread.java:326) - Successfuly sent task result to server. task ID: Range IPs by ICMP, Job ID: 'Range IPs by ICMP', Updates: 1, Deletes: 0

Rutger
Frequent Visitor

Re: Using Range IPs by ICMP in UCMDB

Interesting. It's almost as if DDM does not allow entering discovered CIs into the OPS database.

I'm afraid I have to stop here, because my knowledge is limited (at the moment) to uCMDB standalone.

Perhaps you could log an issue with Support.

Oh and do post this on the Live Net (www.www2.hp.com) on the Configuration Management/DDM board.

There's some really good skills hanging around those parts.

 

Mike Makar
Super Collector

Re: Using Range IPs by ICMP in UCMDB

You need to add network CI's, whatever range you're trying to discovery first needs to have that subnet added as a network CI.  Then discovery can begin.  As discovery runs, there are other jobs that will discover and populate other network CI's which is the idea of spiral discovery.

Rutger
Frequent Visitor

Re: Using Range IPs by ICMP in UCMDB

Ah. But isn't that what he did in the first place when he added the probe range?

Peter Miebach
Super Collector
Solution

Re: Using Range IPs by ICMP in UCMDB

I played around a bit more and discovered some things.

 

Adding the probe creates a few CIs in the CMDB. If I look at the Network Topology view I can see the following CIs for the probe instance (see screenshot):

IPsubnet

Windows

IPAddress

 

If I run the adv. discovery for only "Range IPs by ICMP" the results only show that one instance is found (the probe).

 

I created a view for only IP addresses and it showed me all of the IPs that were detected in the scan. (see screen shot)

 

Just noticed the "Statistics Results" section in the discovery was hidden below the "Discovery Status".

It shows that 81 CIs were created.

Michael-Polyako
Acclaimed Contributor

Re: Using Range IPs by ICMP in UCMDB

Just a sec! If you are running the Range IP by ICMP,

you should see only one CI in the list, it's the probe itself, because he's the one on which the job is being done!!

 

I think you have no problem at all if after it finishes it's giving you all the IP's scope you gave him.

 

Michael

//Add this to "OnDomLoad" event