01-10-2023 01:59 PM
Good day to you all,
we have a very strange situation, currently using two ise nodes (ver 3.0 patch nr 6), one set as primary the other one as secondary. We migrated a lot of NADs to snmp v3 and also updated the NADs configuration inside ISE with the appropriate snmp username and password, but still we are getting the SNMP request failure as request timed out but only from the other ISE node wich is set as secondary, not a single one from the primary server. Couldnt find any similar problem here in the community, hopefully someone could give a hint where to start.
Thanks.
01-10-2023 03:55 PM
Hello,
is the "Secondary" ISE node reporting SNMP timeout? Are you using SNMP to probe the NAD devices for endpoint data?
Have you checked things like ACLs on the NAD to ensure that you're allowing both ISE nodes' IP addresses to perform SNMP probing?
Not enough technical details here to go on
01-12-2023 01:46 PM
Hello,
sorry for late reply, no acl could prevent communication with both ise nodes. yes for endpoint data
01-11-2023 07:01 AM
What is your use-case for even needing SNMP at all?
01-12-2023 01:47 PM
yes for endpoint data, but what is for me unclear that only the second node sends those alarms, and the second node is configured as backup/secondary not primary.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide