Highlighted
Trusted Contributor.. Trusted Contributor..
Trusted Contributor..
242 views

Many CallHomeEvents and bad performance of discovery

Jump to solution

Dear community,

I was reading this discussion : 

https://community.microfocus.com/t5/CMS-Discovery-CMDB-User/UCMDB-Support-Tip-callhome-inventory-by-scanner-job-scheduling/td-p/1649718

And i want your advices.

I'm using callhome jobs and Discovery jobs trought MZ. 

Discovery job are scheduled and cal home job are scheduled too.

I think it's the cause of the bad discovery performance.

Can you give me some tips ?

Thanks.

Labels (1)
0 Likes
1 Solution

Accepted Solutions
Highlighted
Outstanding Contributor.
Outstanding Contributor.

Re: Many CallHomeEvents and bad performance of discovery

Jump to solution

Call home processing is a very processor intensive job. There are many writes and deletes involved with this job. I would optimize your use of Call Home so that it is only used for the most dynamic hosts in your inventory collection.

Do you have your IP Ranges configured by Datacenter and Client ranges?
If you have Client ranges defined then, stop Datacenter (IP Lease Time = Permanent or long) Call Home:
globalSettings.xml

<!--Switch for if allowing data center IP to call home-->
<property name="allowDataCenterCallhome">false</property>

How frequent is your Inventory Discovery by Scanner interval?
If your discovery is every 14 days then, set call home interval to 336 hours.
If your discovery is every 7 days then, set call home interval to 168 hours.
globalSettings.xml

<!--Time interval in hours that is allowed between two call home requests from the same host -->
<property name="allowCallhomeInterval">168</property>

Do you run the IP MAC harvesting job (SNMP or ARP cache)?
These jobs also create Call Home event so set the interval to match your Inventory Discovery schedule.
For instance, Inventory Discovery begins on Monday and interval is every 7 days. Then schedule IP MAC for once a week on Wednesday or Thursday. The reason is that Agent Call home will be close to Monday start time and will update IP Address. The IP MAC job should then be several days later to update IP address of still parked inventory jobs before the job invocation time is reset.

If you do not use any UD Agent based jobs then, turn off Call Home.
UD Agent based jobs are:

  • Install UD Agent
  • Uninstall UD Agent
  • Update UD Agent
  • Inventory Discovery by Scanner

globalSettings.xml

<!--Switch for if allowing to call home-->
<property name="allowCallhome">false</property>

Call Home processing is only used for unparking the scheduled UD Agent jobs. If you do not use any of these jobs then you have no need to process call home requests. You can then stop all the processing overhead on the UCMDB server by turning off call home.

View solution in original post

Tags (2)
3 Replies
Highlighted
Outstanding Contributor.
Outstanding Contributor.

Re: Many CallHomeEvents and bad performance of discovery

Jump to solution

Call home processing is a very processor intensive job. There are many writes and deletes involved with this job. I would optimize your use of Call Home so that it is only used for the most dynamic hosts in your inventory collection.

Do you have your IP Ranges configured by Datacenter and Client ranges?
If you have Client ranges defined then, stop Datacenter (IP Lease Time = Permanent or long) Call Home:
globalSettings.xml

<!--Switch for if allowing data center IP to call home-->
<property name="allowDataCenterCallhome">false</property>

How frequent is your Inventory Discovery by Scanner interval?
If your discovery is every 14 days then, set call home interval to 336 hours.
If your discovery is every 7 days then, set call home interval to 168 hours.
globalSettings.xml

<!--Time interval in hours that is allowed between two call home requests from the same host -->
<property name="allowCallhomeInterval">168</property>

Do you run the IP MAC harvesting job (SNMP or ARP cache)?
These jobs also create Call Home event so set the interval to match your Inventory Discovery schedule.
For instance, Inventory Discovery begins on Monday and interval is every 7 days. Then schedule IP MAC for once a week on Wednesday or Thursday. The reason is that Agent Call home will be close to Monday start time and will update IP Address. The IP MAC job should then be several days later to update IP address of still parked inventory jobs before the job invocation time is reset.

If you do not use any UD Agent based jobs then, turn off Call Home.
UD Agent based jobs are:

  • Install UD Agent
  • Uninstall UD Agent
  • Update UD Agent
  • Inventory Discovery by Scanner

globalSettings.xml

<!--Switch for if allowing to call home-->
<property name="allowCallhome">false</property>

Call Home processing is only used for unparking the scheduled UD Agent jobs. If you do not use any of these jobs then you have no need to process call home requests. You can then stop all the processing overhead on the UCMDB server by turning off call home.

View solution in original post

Tags (2)
Highlighted
Trusted Contributor.. Trusted Contributor..
Trusted Contributor..

Re: Many CallHomeEvents and bad performance of discovery

Jump to solution

Thanks you so much !

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Many CallHomeEvents and bad performance of discovery

Jump to solution

Hello Florian,

I presume that the main scope of your inquiry is the general performance degradation induced by the heavy CallHome tasks.

This was noticed in the past also. To add to the information provided by @John Goldstein, some of the performance degradation happens on the History updates on the CallHome history tables.

A good option is to disable the entire CallHome CIT History tracking so whatever updates we have on these CIs we won't have any history statements behind them so the DB and overall data-in will perform much better. This is done with a special qualifier on the CIT level.

When the CIT_NOT_TRACKED_FOR_HISTORY qualifier is assigned to an object CIT, no CI events (add, update, delete) will be stored to history for all instances of the selected CIT as well as all incoming and outgoing links related.

More details on the documentation page at https://docs.microfocus.com/itom/Universal_CMDB:2020.02/SAHstryDisable

 

 

 

Kind regards,
Bogdan Mureșan
EMEA CMS Technical Success
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.