Highlighted
Established Member..
Established Member..
2227 views

Setting up Call Home For UDA

Jump to solution

It has been a while since this thread was discussed, but we're just moving from DDMi to UD.  Our UD environment only discovers end user devices, and we will have UD Agents on all of them.

However, we have many users who access via VPN and are trying to get these devices to use the call home feature since we obviously do not have the ip ranges for these.

We also have a limitation that prevents us from using SNMP data collection (not to mention we need to use UDA for software data collection).

We set up our UD environment as Data Center type and can see permanently connected *but DHCP-allocated IP addresses) are sending scan files to the Data Flow Probe.

However, the VPN test machines are not.  Can Call Home be used with the Data Center Type, and what are we missing in order to do this?

>John GOldstein provided this reply already in another thread:

"Your answer depends on the version of UCMDB that you are using. For 10.31 there is a property in globalSettings.xml called allowDataCenterCallhome that you must set to true."

It's hard, but it's not difficult
0 Likes
1 Solution

Accepted Solutions
Highlighted
Outstanding Contributor.
Outstanding Contributor.

Re: Setting up Call Home For UDA

Jump to solution

To get scans from VPN clients you first have to understand how the Inventory Discovery by Scanner and Call Home work together. Your client systems will need to at one time have been on a network that is included in the Probe Range. This will then queue the Inventory Discovery by Scanner job for that host and UD unique ID. The job for that host must then be in status pending probe or parked. When your VPN client does a call home it provides its UD unique ID and its current IP address. The pending or parked job is then started and provided with the IP address of the client. If the provided IP address is outside the scope of any of the probes then nothing happens. This includes clients that call home with private ip ranges assigned by their home router (i.e. 192.168.x.x).

Call home does not run the scan nor provide a way for a completed scan to get to the probe. Call home only provides an updated IP address to specific pending jobs; Inventory Discovery by Scanner, Update UD Agent, Install UD Agent, and Uninstall UD Agent.

View solution in original post

11 Replies
Highlighted
Honored Contributor.. Honored Contributor..
Honored Contributor..

Re: Setting up Call Home For UDA

Jump to solution

It is not allowed by default. Check the golbalsettings.xml file (via Adapter Management) and check the value for: "allowDataCenterCallhome"

Highlighted
Outstanding Contributor.
Outstanding Contributor.

Re: Setting up Call Home For UDA

Jump to solution

To get scans from VPN clients you first have to understand how the Inventory Discovery by Scanner and Call Home work together. Your client systems will need to at one time have been on a network that is included in the Probe Range. This will then queue the Inventory Discovery by Scanner job for that host and UD unique ID. The job for that host must then be in status pending probe or parked. When your VPN client does a call home it provides its UD unique ID and its current IP address. The pending or parked job is then started and provided with the IP address of the client. If the provided IP address is outside the scope of any of the probes then nothing happens. This includes clients that call home with private ip ranges assigned by their home router (i.e. 192.168.x.x).

Call home does not run the scan nor provide a way for a completed scan to get to the probe. Call home only provides an updated IP address to specific pending jobs; Inventory Discovery by Scanner, Update UD Agent, Install UD Agent, and Uninstall UD Agent.

View solution in original post

Highlighted
Established Member..
Established Member..

Re: Setting up Call Home For UDA

Jump to solution

What would happen if we included the popular 192.168.x.x range as a management zone?

It's hard, but it's not difficult
0 Likes
Highlighted
Outstanding Contributor.
Outstanding Contributor.

Re: Setting up Call Home For UDA

Jump to solution

@jayscismCHAOS!

No, seriously, the private IP ranges are meant to be self contained networks. The probes will not be able to connect to such IP addresses. If they could connect to that IP ranges it would mean that the probe is connected to its own private range and not the client systems home network.

0 Likes
Highlighted
Established Member..
Established Member..

Re: Setting up Call Home For UDA

Jump to solution

"Your client systems will need to at one time have been on a network that is included in the Probe Range."

Let's assume, because it is true, that our clients start life this way, as they are imaged at a central location, in a defined management zone, and the UD Agent is part of that image.  

This will then queue the Inventory Discovery by Scanner job for that host and UD unique ID. The job for that host must then be in status pending probe or parked.

Ok, this makes sense, so far, the probe doesn't recognize that this device is on VPN (and, indeed, it may not be yet).

When your VPN client does a call home it provides its UD unique ID and its current IP address.

In our case, our VPN client is the Cisco VPN client.  Are you saying it does a "call home" and will report the client's UD unique ID and IP address, or do you mean the UD Agent is doing this?

The pending or parked job is then started and provided with the IP address of the client. If the provided IP address is outside the scope of any of the probes then nothing happens. This includes clients that call home with private ip ranges assigned by their home router (i.e. 192.168.x.x)."

I believe that our Cisco VPN assigns the clients internal IP addresses on our 10. space, so they should call home with that address.  If that's the case, then...

Call home does not run the scan nor provide a way for a completed scan to get to the probe. Call home only provides an updated IP address to specific pending jobs; Inventory Discovery by Scanner, Update UD Agent, Install UD Agent, and Uninstall UD Agent.

We would need to have the IP space for our VPN set up as a management zone, correct? Once Call Home provides an IP in that range, Inventory Discover by Scanner gets it and boom, scan file is provided to Data Flow Probe?

Do I have that right, or am I missing something?

If I have it right, the thing we are missing is a correctly configured management zone for our VPN based clients. 

It's hard, but it's not difficult
0 Likes
Highlighted
New Member..
New Member..

Re: Setting up Call Home For UDA

Jump to solution

Thanks. Should I change the value for the following settings to 'true' as well?

    <!-- Whether to resolve IP address from primary dns name during connection in Inventory Discovery by Scanner job-->
    <property name="pingHostName">false</property>

0 Likes
Highlighted
Honored Contributor.. Honored Contributor..
Honored Contributor..

Re: Setting up Call Home For UDA

Jump to solution

We would need to have the IP space for our VPN set up as a management zone, correct? Once Call Home provides an IP in that range, Inventory Discover by Scanner gets it and boom, scan file is provided to Data Flow Probe?

This is correct. Once you assign the VPN ranges (typically 10.x.x.x.) to a probe, the callhome will trigger waiting jobs for the devices that "called home." You might run into an issue with MAC Addresses for short IPs (as the Cisco VPN will use the same MAC for all connections), but there's a fix for that...

0 Likes
Highlighted
Outstanding Contributor.
Outstanding Contributor.

Re: Setting up Call Home For UDA

Jump to solution

@jayscism wrote:

When your VPN client does a call home it provides its UD unique ID and its current IP address.

In our case, our VPN client is the Cisco VPN client.  Are you saying it does a "call home" and will report the client's UD unique ID and IP address, or do you mean the UD Agent is doing this?

The Cisco VPN client doesn't do the call home, the HPE Universal Discovery Agent will do the call home. You can see this activity on the client side in log C:\Windows\SysWOW64\config\systemprofile\AppData\Roaming\Hewlett-Packard\Universal Discovery\Data\discagnt.log (Windows 7 64bit). Or, on the call home probe configured in the Agent as URL0, URL1, URL2 and seen in log file WrapperProbeGw.log (search for string CallhomeServlet). The IP address that is sent by Agent will depend on the network configuration of the client system. Sometimes the VPN assigned IP address is sent but sometimes I also see the IP address of the users home network. I have not figured out what controls this behavior. If you do get sent the VPN IP address 10.x.x.x then you will need to have one of your probes configured to have that IP address in the probes scope.

Now that the probe has received the UD unique ID and updated IP address it creates a CallHomeEvent CI. You must run the job Call Home Processing to process these CIs and trigger the parked Inventory Discovery by scanner job to try and contact the client at the VPN ip address. If it is able to connect to that IP address it will then run through the jobs 13 step workflow; Remove Local Scan Log File,Scanner Connect,Lock Scanner Node,UD Unique ID check,Check Scan File Existence,Upgrade Scanner,Run Scanner,Check Scanner Finished,Download Scan File,Remove Scan Data,Unlock Scanner Node,Wait XML Enricher Process,Parse Enriched Scan File. 

If the client stays connected to the same IP address from Scanner Connect through Download Scan File then you will get a scan file that will be parsed by the probe server. If not then it will try the whole workflow again next time a call home event is triggered.

0 Likes
Highlighted
Outstanding Contributor.
Outstanding Contributor.

Re: Setting up Call Home For UDA

Jump to solution

@jayscismHow did it go? Where you able to do discovery of your client devices?

If any of the responses helped you solve your question please mark the posted solved so other people can find the information.

0 Likes
Highlighted
Established Member..
Established Member..

Re: Setting up Call Home For UDA

Jump to solution

A couple of key learnings here for us and John's post marked as the solution was instrumental to unlocking these for us:

  1. The UD Agent must be properly configured for calling home.
  2. Create a management zone for your VPN-connected clients
  3. Sit back and watch the magic happen

 

It's hard, but it's not difficult
0 Likes
Highlighted
Frequent Contributor.. Frequent Contributor..
Frequent Contributor..

Re: Setting up Call Home For UDA

Jump to solution

What is the fix for cisco VPN connected users that you reference in your reply?

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.