- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-30-2024 06:08 AM
Good morning all,
We are currently experiencing an issue where Discovery is creating an empty/unknown AIX server that should not be picked up.
I run discovery on 10.5.250.201, and successfully pick up the UNIX Cluster, IBM Frame, and two AIX servers.
'newleaf_pboota' is the correct AIX server thats correctly populated while 'newleaf' is the incorrect AIX server and has no data.
Unable to determine how this incorrect server is being identified.
Requesting assistance on ability to stop discovery of this incorrect/empty AIX server CI. Thank you!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2025 01:06 AM - edited 01-06-2025 01:07 AM
Hi @Jeffrey Beaudry ,
We have had instances in the past where it picked the Old DNS names.
Check with the network team to see if the DNS names are mapped appropriately for the IP address.
If my answer helped in any way, please mark it as ✅Correct & 👍Helpful
Regards,
Mahathi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2025 01:06 AM - edited 01-06-2025 01:07 AM
Hi @Jeffrey Beaudry ,
We have had instances in the past where it picked the Old DNS names.
Check with the network team to see if the DNS names are mapped appropriately for the IP address.
If my answer helped in any way, please mark it as ✅Correct & 👍Helpful
Regards,
Mahathi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-17-2025 07:54 AM
Thank you Mahathi. Looking into the DNS names was able to lead me to a resolution with our Networking and CMDB team.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-20-2025 11:21 AM
Glad it helped @Jeffrey Beaudry 🙂