ServiceNow Discovery not populating public IPv4 addresses.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2024 03:33 AM
Posting here as I was not able to find any help on the internet.
When I run discovery against a Linux Server using its public IP (IPv4) this IP is not populated in the CMDB. I get Only the Private IP address of the CI along with some public IPv6 address (which is not supposed to be there, because the Server does not have IPv6 address associated with it).
Is this expected behavior (I highly doubt it)? If so what might be a possible workaround for me to populate the public IPv4 address so it can be associated with the CI - doesn't make sense to do it manually as I am literally using this public IP to perform the discovery.
Any help is greatly appreciated!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-24-2024 04:09 AM
Hi @BozhidarNizamov,
No, this is not the expected behavior. To resolve this, you can try the following steps:
1. Check Discovery Probe Configuration: Ensure that your discovery probes and sensors are correctly configured to capture the public IPv4 address.
2. Update IP Address Table: Verify and update the IP address table in your ServiceNow CMDB to include public IP addresses.
3. Scripted Workaround: Use a custom script within ServiceNow to manually associate the public IPv4 address with the CI post-discovery.
4. Review Firewall and Network Configuration: Ensure that there are no network restrictions or firewall rules that might be affecting the discovery process.
5. Consult ServiceNow Documentation: Review the ServiceNow documentation or reach out to ServiceNow support for guidance specific to your instance.
These steps should help ensure the public IPv4 address is correctly populated in the CMDB.
Thank you, please make helpful if you accept the solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2024 02:11 AM
I would suggest to debug the linux server pattern. You can look for step 5. the pattern query the DNS and store that value in the respective table. While debugging you will see what the output you are getting.
Thank you, please make helpful if you accept the solution.