- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2024 08:25 AM
sorry didnt get you. what was 'switched on' ? I was referring to not use 'public' SNMP credential.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-14-2024 03:52 AM
sorry i meant it was switched off and using custom snmp v3 credentials
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-13-2024 02:13 PM
Hi,
1)please check if snmp port is open on port 161 on Shazzam probe input payload.
2) check MID server Ip ranges are correctly assigned
3)check if snmp credentials are applied to all mid Servers or specific mid server
Regards,
srinija
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-14-2024 04:13 AM
because no credentials are being captured in the XML payload no SNMP Probes are being sent out to classify anything
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-15-2024 05:30 AM
Hi.
This is now resolved !
For some reason a VAST number of switches were not getting SNMP credentials they needed.
Instead it was defaulting to UNIX Probes !
Building an SNMP only Behavior and applying it to the schedule resolved this issue.
