- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-26-2024 03:05 PM
Hello!
I'm working on an SNMP discovery of a Nutanix-hosted devices (Load Balancers) which, in turn, discovered a Linux Server. The Linux Server was initially discovered with a normal looking name like xyz123. Then, three months later, it was discovered again, but this time the name changed to "xyz123 (the double quote appeared at the beginning). Two months after this discovery, it changed back to xyz123 and, of course, now it's back again. I'm receiving complaints that ServiceNow isn't interpreting this device's name correctly during discovery, but that doesn't seem correct.
When I looked at recent discovery entries for this device, I noticed that ServiceNow appears to use SNMP to discovery it as I see OIDs being gathered. My sense is that something is changing somewhere, but ServiceNow isn't the problem.
I'm hoping someone might have experience with this type of issue and be able to shed some light on it for me.
Any help is appreciated.
Steve.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-30-2024 06:10 AM
Hi @SteveEdM okay.. i agree thats strange..
using alias should serve the purpose of not using other credentials OR you can use the schedule with a behavior created which will only launch SSH probes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-27-2024 05:56 AM
1. did u check the discovery logs for this linux server and what does it fetch via SNMP?
2. Is there any name change happening at the server level by the team?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-27-2024 07:01 AM
I checked the discovery logs and have attached the XML (as a text file) to this response. On line 93 is the first mention of the device name: "xyz123, in the CI Data section of the file. My sense is that the name is being discovered this way and that ServiceNow is only returning what is provided to it.
To my knowledge, I do not think they are changing the name, but I will reach out to them now to find out.
The only other thing I can think of is the name is somehow not being parsed properly and retaining the double quote occasionally.
Any help you can provide is appreciated.
Steve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-28-2024 06:30 AM
yes only the 'name' field has double quotes.. hostname, DNS and all looks fine.. see what u get as a response from the technical team and you can ask them to double check on the OS level also for the name given to this box
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-30-2024 05:57 AM
Hello Pratik,
Update: After some research, I think my colleague and I have found the issue. The device in question appears to be discovered by two separate schedules...one schedule uses Linux credentials and the other users SNMP credentials. The SNMP credential appears to be the one adding the double quote before the server name though we're not quite sure why. We are looking into creating separate schedule and adding a credential alias for Linux only credentials for this device and, perhaps, others that may have this issue.
Let me know your thoughts/opinions.
Steve.
