net_connect use profile name in OC inventory

[Anupama Purayannur]

Hi All, 
Is it possible to use of "Hostname" configured in net_connect to display in OC inventory (instead of depending on DNS resolution)? The Hostname and IP address configured properly in net_connect profile.
- hostname=servername.fqdn.com
- ip=10.1.1.100

It is not feasible to add host entry for all devices outside the environment which will not be registered in DNS.

Regards

Anu

[Stephen Danseglio]

Hi Anu,

Check discovery_agent (at loglevel 5) on the monitoring hub. Does it show:

[PerIpDiscovery-1, discovery_agent] Did not detect hostname for ##.#.###.##. getCanonicalHostName() returned input IP address.

To workaround the problem of the monitored target host not resolving, try adding a complete host entry in (/etc/hosts) for <example_hostname> on the hub where the discovery_agent is deployed, e.g., IP address, FQDN and shortname-> ###.###.#.## myhost.example.com myhost

Then rediscover the host using the OC setup wizard to see if it produces the desired result/preferred hostname in the OC Inventory Name column.

Best Regards,
Steve

------------------------------
Steve Danseglio
Senior Principal Support Engineer (Technical Support Engineer 5)
Broadcom Software-IMS Division
UIM Certified Expert
KCSv6 Practices Certified
Certified Customer Success Manager (CCSM) Level 1
------------------------------

[Anupama Purayannur]

Hi Steve, 

It is not feasible to add host entry for all devices outside the environment which will not be registered in DNS. 

Any other options?

Thanks

Anu

[Samer Al Yasiri]

Hi Anu,

A new feature was released in net_connect probe v. 4.01 to enable granular monitoring based on  net_connect profile
KB Enable granular monitoring based on profile in net_connect probe

[Anupama Purayannur]

Thanks @Samer Al Yasiri. Can you please provide more details on what these settings are? It is not clear from the documentation. 

Is it this one
net_connect AC Configuration

Regards

Anu

[Samer Al Yasiri]

That is correct Anu, with the net_connect probe v. 4.01, you can use user-defined hostname instead of Ip address. 

For example, hostname1 will appear in OC inventory and the source of the QOS and alarms based on the below configuration:

In OC inventory, the entry will appear based on the hostname we defined in the net_connect profile.

Thanks,
Samer

[Anupama Purayannur]

Hi @Samer Al Yasiri

We could achieve this by setting the sendqostoprofilename to yes in profiles. Is there a way to sendqostoprofilename to yes in all existing profiles other than updating one by one? I cannot think of a way to do this. But thought of checking anyway. 

Thanks

Anu

-------------------------------------------

[Samer Al Yasiri]

Hi Anu,

Unfortunately, you have to update each profile manually.

Thanks,
Samer

-------------------------------------------

[Garin Walsh]

This isn't specifically correct.

Look into the controller probe callback "probe_config_set" - you can use this with pu to make changes. It's usually pretty straight forward to use something like excel to generate the list of commands if this is a one-off effort.

@Luke Christiansen (hope that's the right Luke) has a tool that will also generate these commands with a lot more flexibility.

And finally, if you need full control over it, look for a Lua script posted to this forum (search for nimbus.request) - there are lots of examples of automating such changes.

-------------------------------------------