Highlighted
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor
181 views

UCMDB Tip: Difference between DDMI and UD Call Home requests

In DDMI the agent sends a Call Home request only when DDMI server has not got the up-to-date inventory collected from this device and the time it uses is the scanning interval. If it is longer than a scanning interval +20% (or a maximum of 8 hours), then the agent will send a Call Home request and the Call Home request initiates an inventory scanning.

 

In UD the Call Home request is sent by the agent all the time according to the configured frequency (by default 3 days). When the Call Home event arrives, it tries to wake-up the scanning workflow, but if the scanning workflow has already finished, then the Call Home event will do nothing.

“HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.”

Click the KUDOS star on the left to say 'Thanks'
Labels (1)
Tags (1)
0 Likes
5 Replies
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: UCMDB Tip: Difference between DDMI and UD Call Home requests

Hi,

 

Just one doubt.  In fact call home facility is used for mobile devices like laptop or user on VPN. If all devices are in DC  , then in that case too, is it required to configure call home.

 

Since we are going for dependancy discovery from modules  and agentbased discovery,  if I configure coll home request , it will lock the node without our knowledge .So my questionis  both agentless jobs and agentbased call home would work properly??? Or I can skip call home featue since scanning will be done weekly or fortnightly.

 

Please suggest.

 

 

with regards,

Nick

0 Likes
Highlighted
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

Re: UCMDB Tip: Difference between DDMI and UD Call Home requests

Hi Nick,

 

CallHome can be benefitial in DataCenter environments as well if ICMP ping is disabled by Firewall and discovery of ip addresses via ping sweep is not possible.

 

As regards to node locks, CallHome by itself is not locking any nodes, only the jobs that have workflows do the node locking, such as Inventory Discovery by Scanner and UD Agent Management jobs. 

 

Regards,

Irina

“HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.”

Click the KUDOS star on the left to say 'Thanks'
0 Likes
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: UCMDB Tip: Difference between DDMI and UD Call Home requests

Hi,

 

Thanks for the reply.

 

But at the current customer , there are no firewalls in DC  but ony DMZ firewalls are available.  I feel  to use call home option to  scan the  unscanned devices by UD.

 

 

But there are few doubts about call home.

 

1. can I use 5/6 probe ips  in agentinstall. sh script  while istalling agent since customer have total 7 probes.

 

I tried by increasig arguments in script i.e. --url3, --url4, --url5, --url6 but script doesnot work. But sameis woring with 3 arguments only or without any arguments.

 

2. Agent based discovery wil run nly on weekend and o weekdays I am planing to run modulebased discvery for advanced and dependancy relationship. If due t call home , if probe gets request from any unscanned node , it will start the scanning at that time or how i can control that scanning if want to postpone the same

 

 

. Pleas explain detailed steps how call home  and UD will work.

 

 

Please suggest.

 

with regards,

Nick

 

 

 

0 Likes
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: UCMDB Tip: Difference between DDMI and UD Call Home requests

Hi,

 

Please reply.

 

With regards,

Nick

0 Likes
Highlighted
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

Re: UCMDB Tip: Difference between DDMI and UD Call Home requests

Hi Nick,

 

Sorry for the delay in coming back to you.

 

Only --url0, --url1 and  --url2 parameters are supported. Unlike DDMI, in UD the agent can report the Call Home to any of the UD probes and it will be accepted and approriate Call Home CI will be created and send to UCMDB server, and then it will be dispatched to the correct probe that has got its IP address in its range.

 

When the Call Home event CI is received by the Call Home processing job, this job tries to find the Inventory by Scanner job running on the probe and wake it up, so the scanning will only be started if the probe has not managed to connect to the device yet, and in other cases it will simply restart the scanning process from the step at which the scanning workflow is at (usually the download scan step). If the scanning has already finished and the workflow is no longer active, Call home will do nothing.

 

Regards,

Irina

“HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.”

Click the KUDOS star on the left to say 'Thanks'
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.