Horizontal discovery is not getting trigger for some of the Azure VMIs.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-04-2023 06:55 AM
We have Azure Cloud Discovery in place to discover both Cloud Resources and Horizontal IP based discovery.
IP address information is missing for some of the Azure VMIs due to which Horizontal discovery don't get trigger for those devices. (Horizontal Discovery schedule for cloud don't require IP ranges to be defined as it automatically gets IPs from NIC "cmdb_ci_nic" table as per below KB).
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0828888
What we observed is if no public IP address is discovered for cloud account in "Azure - Public IP (LP)" pattern, NIC pattern "Azure - NIC (LP)" don't get trigger resulting no private IP address getting discover for any of the VMIs in that cloud account.
Some of the cloud accounts won't have public Ip address but that shouldn't have dependency to discover NIC. Please let me now if anyone encounter similar issue where IP address/NIC info is missing for VMIs resulting no horizontal discovery for those accounts?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2023 01:21 PM
Hi @Shantanu1 / @Niklas Peterson ,
Even I am having the same issue of discovering public IP.
I am not able to access the https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1288346
can any of you please summarize the fix/ trigger rule here.
Thank you,
Sri
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-12-2023 02:13 AM
Hi,
Update the Azure - NIC (LP) pattern and replace the trigger.
Remove Azure - Public IP (LP) and instead add Azure Datacenter discovery with Batch Size as All.
Also remove the Orchestrator Input cmdb_ci_cloud_public_ipaddress.
Don't forget to sync the Pattern to your MID Servers!
Regards,
Niklas
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2024 12:02 PM
Hi despite this setting which available out of the box in my instance I am on Vancouver and latest version of pattern none of my horizontal discovery is auto discovered.
All child schedule which run after azure cloud schedule are always cancelled due to discovery IP range is empty
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2024 10:10 AM
can you please populate the resolution here. for some folks it required hi access
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2024 11:40 AM
Hi,
Already did. Check my previous reply. It does not contain the full article but the parts that needs to be changed.
Regards,
Niklas