- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-13-2024 09:26 AM
Linux server is getting classified as IP Router via discovery as SNMP is enabled on Linux server, I tried decreasing priority of Linux classification than SNMP. Also tried creating identifier for Linux server with priority as 99 and snmp router it is having as 100. Still it is getting classified as IP router. Please suggest any workaround or fix this issue.
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-15-2024 09:20 AM
Hello,
Remove the IP affinity to the protocol, SNMP. I've just delt with this exact issue. Removing existing affinity to snmp worked upon next Discovery. SSH is credential is valid on the box, will be tried first over SNMP, assuming the priority order for protocols is SSH before SNMP (which is the default order I think .. )
In my case, the Linux box had 2 protocols and Discovery had a preexisting affinity to snmp.... Hence disco was not trying SSH...
Hope this helps?
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2024 10:26 AM
hi @akmalbabu ,
SNMP classification happens via OID. Are you seeing any OID values in the shazam input?
Please check Standard Network Router ci classifier and see if there is any OID Match from this SNMP OID Classifications in the related tab.
Regards,
Srinija
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-15-2024 03:07 AM
Hi, consider to remove corresponding affinity record from Credential Affinity table (dscy_credentials_affinity).

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-15-2024 09:20 AM
Hello,
Remove the IP affinity to the protocol, SNMP. I've just delt with this exact issue. Removing existing affinity to snmp worked upon next Discovery. SSH is credential is valid on the box, will be tried first over SNMP, assuming the priority order for protocols is SSH before SNMP (which is the default order I think .. )
In my case, the Linux box had 2 protocols and Discovery had a preexisting affinity to snmp.... Hence disco was not trying SSH...
Hope this helps?
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2024 05:08 AM
Thanks Dave, we need to remove related server IP address in IP Affinity SNMP service.