- 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-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.
