Highlighted
Super Contributor.. Super Contributor..
Super Contributor..
349 views

Call Home Troubleshooting

I have quite a number of "client" devices in our environment that are delinquent in their scan schedules and would like to address.  Many of these are captured via call home.  I know that the call home is working as I see that the job is processing thousands of requests, however I'm trying to find a way to target the devices that have delinquent scans.  Is there a way, short of contacting the owners of the laptops, to get these devices to scan?  Any suggestions?

Thanks,

0 Likes
2 Replies
Highlighted
Outstanding Contributor.
Outstanding Contributor.

Re: Call Home Troubleshooting

What version and content pack of UD are you using?

What is the scheduled frequency of your Inventory Discovery by Scanner job? (7 days, 14 days, 30 days?)

Call home only works for parked inventory / UD Agent management jobs. When troubleshooting call home failure start by finding out if the client has a parked job in the Inventory by Scanner queue. If it doesn't, then you will have to run other jobs that will supply your trigger for the inventory job.

In my environment I run the IP MAC Harvesting by SNMP to gather IP Addresses of potential client devices from switch / router ARP caches. UDA Status Collector with property "isCreateUDA" equal "true" to create the Node and UDA CITs as needed. These jobs provide me with the necessary CITs for feeding the Inventory by Scanner trigger TQL. I will also sometimes run the Host Connection by Shell job with property "udaConnectionOrder" equal "first" if the UDA is being stubborn about being discovered. This job will return different data than a scan file so I use it sparingly to avoid data swapping issues.

0 Likes
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

Re: Call Home Troubleshooting

We are on version 10.22 CUP4 CP20.  The Inventory by Scanner schedule is set to 14 days.  My challenge is trying to "force" a scan on the devices with a delinquent scan date.  Or trying to track down whether the job is "parked" for specific hosts.  I guess I'm looking to determine whether a) the agent is installed b) agent is started c) the inventory by scanner job is completing successfully.  These can be fairly easily determined with static IP devices, but I'm not sure how to check these items when "call home" is the primary way the scan is initiated.  Thanks for your input.

Bob

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.