topic I ended up opening a TAC case in Network Access Control

ISE Alarm : Critical : Profiler SNMP Request Failure : Server

Clark Willms — Mon, 11 Mar 2019 04:05:14 GMT

Ok, so this alarm is coming in repeatedly and is now on my projects list. I get email alerts from the server that list thr NAD IP as the endpoint device and the Endpoint IP address is correct. I've checked the settings and the endpoint is not listed as a NAD in ISE (ver 1.2).

Profiler SNMP Request Failure

Details :

Profiler SNMP Request Failure : Server=xxx-xxx-xxx; NAD Address=10.253.124.194; Endpoint IP Address=10.253.124.194

Description :

SNMP request times out, or SNMP community/user auth data is incorrect.

Suggested Actions :

Please ensure if SNMP is running on the NAD and verify that SNMP configuration on ISE matches on NAD

*** This message is generated by Cisco Identity Services Engine (ISE) ***

Has anyone seen this come in before?

PS - Why is the IOS for ISE so cut down? Looks like something you would get from an Apple product.

Thanks,

Clark

ISE Alarm : Critical : Profiler SNMP Request Failure : Server

blenka — Sun, 17 Nov 2013 16:13:08 GMT

Alarm Name :- Profiler SNMP Request Failure

Alarm Description :- Either the SNMP request timed out or the SNMP community or user authentication data is incorrect.

Alarm Resolution :- Ensure that SNMP is running on the NAD and verify that SNMP configuration on Cisco ISE matches with NAD.

ISE Alarm : Critical : Profiler SNMP Request Failure : Server

sahseth — Mon, 18 Nov 2013 20:40:50 GMT

Hello,

Please follow below CiscoLink:

http://www.cisco.com/en/US/docs/security/ise/1.2/user_guide/ise_mnt.html

Profiler SNMP Request Failure

Either the SNMP request timed out or the SNMP community or user authentication data is incorrect.

Ensure that SNMP is running on the NAD and verify that SNMP configuration on Cisco ISE matches with NAD.

Also ensure what snmp version device is using.

Thanks,

I have this issue also. The

Cristopher Bohde — Fri, 04 Apr 2014 12:44:40 GMT

I have this issue also. The previous replies do not answer the question, simply restate the confusing alert message and generic alert description from Cisco.

I'm getting this message 20+ times a day, and have verified that the NAD IP that is being reported in the alarm are NOT NADs. They are end clients.

I am having the same issue as

David A — Tue, 08 Apr 2014 18:57:18 GMT

I am having the same issue as well, and there is definitely a duplicating of the NAD and / or Client IP into the respective fields.

In addition, I see Clients bring labeled with the SNMP trap under the "Endpoint" as the source, however when I click on the interface inside the Authentication Monitor it returns with a blank report that only says "SNMP information is not configured for this device in ISE." inside the status field.

Any suggestions?

Please assist,

David

I have this issue too. I

Justin bollinger — Tue, 29 Apr 2014 18:20:00 GMT

I have this issue too. I believe that ISE is actually trying to do an SNMP Query against the IP address of the client instead of the IP address of the NAD.

I ended up opening a TAC case

Cristopher Bohde — Tue, 29 Apr 2014 18:24:08 GMT

I ended up opening a TAC case on this. Apparently there's some bug when both SNMP and NMAP profiling are turned on. The TAC engineer had me disable NMAP since we weren't really using it for profiling (as DHCP, RADIUS, SNMP, etc provide much more information and are a higher priority in ISE profiling). Disabling NMAP profiling worked, and the SNMP alerts stopped.

I have this behavior too with

luisq — Tue, 23 Jun 2015 01:30:51 GMT

I have this behavior too with an ISE 1.4! It is amazing such an old bug still appears on the latest version of the product. But this is not the only case:

NAM PAC renewal Anyconnect 4.1.28
HA Replication ISE 1.4

Same problem here on 2.1

lmediavilla — Wed, 06 Jul 2016 07:29:02 GMT

Same problem here on 2.1

Re: Same problem here on 2.4 patch 1

TIM JUDGE — Tue, 19 Jun 2018 02:54:17 GMT

We have the same problem. We've checked ACLs, firewalls, config of the NAD, retyped SNMP variables and so on. but still it comes.....

Re: Same problem here on 2.4 patch 1

pnowikow — Fri, 20 Dec 2019 15:09:46 GMT

Are there any updates on this post? I'm about to upgrade to 2.6 next month and hopefully it goes away. I made sure on all my routers and switches that SNMP is running and my access list allows read only access to ISE servers.

Re: Same problem here on 2.4 patch 1

Damien Miller — Fri, 20 Dec 2019 16:44:47 GMT

Which version of SNMP are you using? There are quite a few SNMP caveats and TAC would still be the best bet for determining which specific one you are hitting.

Re: Same problem here on 2.4 patch 1

pnowikow — Mon, 23 Dec 2019 15:09:42 GMT

We use V1 & V2. I'll get a TAC case open if this upgrade to 2.6 scheduled for next month doesn't fix it.

Thanks,

Pete

Re: Same problem here on 2.4 patch 1

Jason Kunst — Mon, 23 Dec 2019 15:43:35 GMT

@pnowikow wrote:

We use V1 & V2. I'll get a TAC case open if this upgrade to 2.6 scheduled for next month doesn't fix it.

Thanks,

Pete

I'd recommend opening a tac case before hand to make sure its a bug fixed in 2.6, that's a bigger move then getting a hotfix or patch.

Re: ISE Alarm : Critical : Profiler SNMP Request Failure : Server

sinady — Tue, 22 Jun 2021 11:21:32 GMT

Hi all,

I'm currently facing the same issue.

Note: we use ISE 2.7

Could please help to share how to fix this issue.

Thank in advance.

Re: ISE Alarm : Critical : Profiler SNMP Request Failure : Server

CiscoBoy — Thu, 24 Nov 2022 22:38:47 GMT

Hi, I am also on ISE 2.7, did you find the resolution for this? Thanks

Re: ISE Alarm : Critical : Profiler SNMP Request Failure : Server

katerina.dardoufa — Thu, 21 Dec 2023 07:43:10 GMT

Hi all!

I also have the same behavior for only one catalyst9300 in our environment. SNMP settings are correct both on ISE and the device and the device is also correctly monitored by a bunch of other monitoring tools! I am running ISE 3.2!!!!

Re: ISE Alarm : Critical : Profiler SNMP Request Failure : Server

jaydoer1 — Thu, 01 Feb 2024 16:00:12 GMT

Hello all,

I have the same behaviour in our ISE 3.2

Profiler SNMP Request Failure : Server= xxxxxxxxxx ; NAD Address=10.24.1.3; Error Message=Request timed out.

We have deployed distributed PSN's globally,

the SNMP profiler scan tries to run from the PSN's to other region NAD's - for example the UK PSN profiles the Melbourne NAD's which is not needed as there is a Melbourne PSN deployed.

Is this is because of the NMAP scan?

Thanks

Re: ISE Alarm : Critical : Profiler SNMP Request Failure : Server

Charlie Moreton — Thu, 01 Feb 2024 20:17:42 GMT

Resurrecting a 2-year old + thread that has an accepted solution limits the number of people that will take a look at it. The best thing to do is to start a new thread.

Re: ISE Alarm : Critical : Profiler SNMP Request Failure : Server

jaydoer1 — Mon, 05 Feb 2024 14:30:06 GMT

Thanks Charlie, Yes its an old thread

Just fyki - I worked with the TAC and got to know this below for the ISE - Azure Intune MDZ alerts -

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwh51297

Thanks