ISE PSN rejecting RADIUS request

Hi,
We have a distributed ISE infrastructure version 1.3.
We begin noticing the following problem.
Randomly the PSN's started dropping radius requests.
Basically they didn't serviced any client.
It looked like this bug:
ISE PSN rejecting RADIUS request; deadlocks found @ catalina.out
CSCur43427
Symptom:
++ CU runs distributed deployment; 2PSN +MnT +PMN;
++ PSN "node status were up during the issue;
++ PSNs were rejecting RADIUS request; ICMP reachability to PSN were OK;
++ both wired and wireless are affected
++ removing accounting from both foreign/anchor did not fix the issue;
Conditions:
++ ISE 1.2.0.p10
++ happens every 2-3 weeks;
Workaround:
++ restart ISE services;
So we installed patch 2.
But now we got the same problem and there is no newer patch.
Did anyone encountered this also?
thanks,
laszlo

We've also encountered this with 1.3 and logged a TAC case but unfortunately they weren't able to determine the cause due to not enough detail. They suggested changing the log level for runtime-AAA and prrt-JNI to debug temporarily and when it happens again, before restarting the PSN, download the logs from it to supply to TAC.

Similar Messages

ISE v1.2 - Status-Server - 5405 RADIUS Request dropped

Just a note:
Some devices send regular RADIUS status messages;
The ISE drops these as
Event: 5405 RADIUS Request dropped
Failure Reason: 11031 RADIUS packet type is not a valid Request
Root cause: RADIUS packet type is not a valid Request.
Wireshark shows:-
Code: Status-Server (12)
Attribute Value Pairs:
AVP: l=6 t=Service-Type(6): Shell-User(6)
AVP: l=18 t=Message-Authenticator(80): df48bb4b50f0a772bd7c891ef6548c68
AVP: l=6 t=NAS-IP-Address(4): 10.1.1.1
I believe that ISE should accept and respond to these messages RFC5997 up2866.
A RADIUS server or proxy implementing this specification SHOULD respond to a Status-Server packet with an Access-Accept (authentication port) or Accounting-Response (accounting port). An Access-Challenge response is NOT RECOMMENDED. An Access-Reject response MAY be used.

Neno
Nothing to do with that,
The devices will use RADIUS to authenticate fine; databass, credentials, etc fine.
However they send keepalives to validate the RADIUS server is still there. ISE doesn't implement this and ISE logs get full of rejections. The end devices are unable to prioritise which ISE to used based on up/down. But still work.
This was just a note to everyone so they are aware of the issue,

ISE 1.3 not receiving Radius requests from WLC 5508 ver 8.0.110.0

Hello all. I just implemented ISE 1.3 at a customer site. added a WLC running 8.0.110.0 using its mgmt address with a RADIUS preshared key. On the WLC, I created to SSIDs, corp and guest.
For corp I configured WPA2 and AES and forwarded Radius requests to my 2 ISE node PSN interfaces
For the guest I configured MAC filter with advanced features AAA overide and Radius NAC - per Cisco's documents
The corp forwards Radius requests to ISE, the guest does not. I get nothing from the guest.
I configured the WLC step by step from the Cisco document. I have completed over 10 ISE implementations in the last year using ISE 1.2 and WLC 7.x and have never run into this issue before.
Any help will be much appreciated.

This issue has been resolved. The issue was that for the guest SSID MAC filtering was enabled as required, but they had the test PCs on a mac filter bypass list for that SSID in the WLC. This was automatically authenticating the PC, and therefore not forwarding the RADIUS to ISE.
Once we removed the PC from the MAC filter list in the WLC, the authentications were forwarded to ISE as desired.

ISE-5443 RADIUS request dropped due to reaching EAP sessions limit

Hi Guys,
I am getting the below error message from two PSNs (out of 4) & resulting 95% failed authentications on ISE
"5443 RADIUS request dropped due to reaching EAP sessions limit"
Could not find any documents/reference & trying to get on hold TAC in the mean time.
If anyone of you know what could it be, pls share your inputs
TIA
Rasika

Hi Scott,
Thanks for that..
here is bit more information about this evnts log in ISE system (1.2 Patch 4).
Event: 5405 RADIUS Request dropped
Failure Reason :5443 RADIUS request dropped due to reaching EAP sessions limit
Resolution : Wait a few seconds before invoking another RADIUS request with new EAP session. If system overload continues to occur, try restarting the ISE Server
Root cause: A RADIUS request was dropped due to reaching EAP sessions limit. This condition can be caused by too many parallel EAP authentication requests.
Worked with TAC & restarted the service of one PSN node & that brings that node to normal condition & removed the other PSN form the F5 pool until TAC analyze gathered support bundle from that.
It is not heavily loaded environment (3k wireless clients) at the moment & bit scary since we are expecting around 15k when students are back in early March. Authentication failure rate is around 100 in every 15-20s interval. Not sure what is the limitation of the ISE system itself to handle number of EAP sessions per second.
Rasika

ISE 1.2 rejects RADIUS messages from 5508 WLC

The setup in ref is:
WLC 5508 HA pair running 7.6 talking to ISE 1.2 patch 7 (was 6).
Wireless users are authenticated fine, so the 5508 is a valid NAD in ISE, but...
When I setup active RADIUS fallback, so that the WLC can poll the ISE servers I get the message:
"The RADIUS request from a non-wireless device was dropped because the installed license is for wireless devices only"
Why would ISE drop a RADIUS message from a WLC which is a wireless device? Surely this is a mistake?

Hi Nicholas,
This is a known defect.
CSCug34679 ISE drop keep alive coming from WLC.
Symptom:
ISE drops keep alive authentications coming from the WLC, with message 11054 Request from a non-wireless device due to installed wireless license.
Conditions:
When only a wireless license is install on the ISE and using active keep alive on the WLC.
Workaround:
Use passive keep alive on the WLC and not active.
Regards,
Jatin Katyal
*Do rate helpful posts*

ISE : Radius Request Drop

I've implementing cisco ise. But i got something weird. The communication cisco ise and switch has down about 1 hours, and when i check on monitoring, the report just said Radius Request Drop. The communication is good before this happening. Do you know what is happen?
Regards,
Gandhi

I think the problem has solved now.
But, what i want to know is what is happening, there is a bug on Cisco ISE?
Regards,
Gandhi

What happens if the certificate expire on a ISE PSN

What happens if a PSN certificate expire? Does all other nodes in the cluster looses the communication channel to that PSN node?
What is the procedure to install a new certificate on a PSN node with the expired certificate?
Does the PSN node still handle client RADIUS requests that does not depend on the PSN cerfificate?
Tanks!

You definitely want to renew the certs before they expire. Otherwise the effects can be very devastating to your ISE environment depending on what the certificates are used for :) Below are a couple of links that you can use to obtain more info on both of your questions:
ISE version 1.2:
http://www.cisco.com/c/en/us/support/docs/security/identity-services-engine/116977-technote-ise-cert-00.html
ISE Version 1.3:
http://www.cisco.com/c/en/us/td/docs/security/ise/1-3/admin_guide/b_ise_admin_guide_13/b_ise_admin_guide_sample_chapter_01000.html#concept_D7826198A3304303AD046DB981DA4FE6
Thank you for rating helpful posts!

Authentication Policy ISE with External RADIUS Server

Hi All,
I would like to authenticate client by using External RADIUS. Once I create authentication policy using the new compound condition (wireless dot1x + Radius Username Matches "domainB\") I would like to forward the user authentication who make an authen using domainB\username to the External RADIUS Server Sequence. But when I check on the authentication dashboard, it still authenticate using the default authentication rule.
Please suggest about this scenario.
Regards,
Sent from Cisco Technical Support Android App

Hi jrabinow,
Which details you would like to see ?
Here is some infos.
ISEs are deployed in 2 domains such as "acme.com" and "sub.acme.com"
Each domain does not make a trusted relationship so these 2 domains cannot communicate between them.
Each domain has owned Enterprise Root CA (Microsoft)
Client who need to access the network need to authenticate with EAP-TLS.
My environment
My ISE node joined into domain "acme.com"
User will be "[email protected]"
Once the user from "[email protected]" try to authenticate, I would like to forward the RADIUS request from ISEs (acme.com) to other ISEs (sub.acme.com)
After ISEs in "sub.acme.com" return RADIUS-ACCEPT then ISEs in "acme.com" will process an authorization policy.
Regards,
Pongsatorn

ISE acting as Radius Proxy Client?

Hi,
I have an issue where a remote company has there internal redius server and I have my ISE radius server.
When there users come to my site, they can authenticate with my wireless and my ISE server proxies the request to there home site to be authenticated and tells me if I should allow them access or not.
So standard radius proxy and it all works well when my ISE server begins the exchange.
However if my staff go to there site the reverse is not working, they are proxying the requests back OK, and I can see on the firewall and router the incomming radius packets destined to my ISE server. But there is no recourd on the ISE server of ever reciving them and it all times out.
Is tehre some thing I need to do to allow ISE to act as the client in a radius proxy set up?
Cheers.
Oh I am running version 1.2

Hi Aaron,
Check the Cisco ISE dashboard (Operations > Authentications) for any indication regarding the nature of RADIUS communication loss. (Look for instances of your specified RADIUS usernames and scan the system messages that are associated with any error message entries.)
Log into the Cisco ISE CLI5 and enter the following command to produce RADIUS attribute output that may aid in debugging connection issues:
test aaa group radius new-code
If this test command is successful, you should see the following attributes:
Connect      port
Connect NAD      IP address
Connect      Policy Service node IP address
Correct      server key
Recognized      username or password
Connectivity      between the NAD and Policy Service node
You can also use this command to help narrow the focus of the potential problem with RADIUS communication by deliberately specifying incorrect parameter values in the command line and then returning to the administrator dashboard (Operations > Authentications) to view the type and frequency of error message entries that result from the incorrect command line. For example, to test whether or not user credentials may be the source of the problem, enter a username and or password that you know is incorrect, and then go look for error message entries that are pertinent to that username in the Operations > Authentications page to see what Cisco ISE is reporting.)
Note This command does not validate whether or not the NAD is configured to use RADIUS, nor does it verify whether the NAD is configured to use the new AAA model.
The Cisco ISE network enforcement device (switch) is missing the radius-server vsa send accounting command.
Verify that the switch RADIUS configuration for this device is correct and features the appropriate command(s).
For more details please go through the following link:
http://www.cisco.com/c/en/us/td/docs/security/ise/1-2/troubleshooting_guide/ise_tsg.html#pgfId-192989

Critical VLAN/"fail open" support when ISE PSN is unavailable

This thread regards ISE operation (and options) where a policy node becomes unavailable - so, in the case of either a single standalone ISE appliance (no HA), or more often a PSN becoming unavailable due to a WAN failure to a remote branch. The intended design for the deployment in question would involve using downloadable ACLs (dACLs) to provide differentiated access, specifically:
- A default ACL would be configured on 802.1x switchports would allow "limited" access (possibly Internet-only, but TBD).
- Successful 802.1x authentication would require 1) validation of a corporate certificate on the endpoint, and 2) successful AD login. This would provision a dACL providing full access.
ISE provides the option to configure Inaccessible Authentication Bypass to support RADIUS unavailability when 802.1x is configured on switch ports, but I'm needing to confirm how this works when using dACLs instead of VLANs for differentiated access. Specifically, if IAB is configured so that 802.1x ports (maybe all of them if all ports at the branch need to be functional) get placed into a "critical VLAN", will this override the default ACL on the port, which would no longer be applicable to the new VLAN anyway?
Simply put - we need to configure the deployment so that all endpoints fail open and have full access in the event of ISE/RADIUS becoming unavailable. (There'll be no local RADIUS and/or AD server in the event of WAN failure.) This will need to work although the 802.1x authentication/authorization will be using dACLs to determine access.
Thank you

I have a similar set up i.e. Pre-auth ACL applied on each port which is overwritten by a 'permit ip any any' DACL from the ISE server if a device successfully authenticates.
My understanding is that if the ISE PSN nodes become unavailable then if a Critical Vlan has been configured then devices will be placed into that vlan, however, the pre-auth ACL will still apply. Hence, if the pre-auth ACL only allows limited network connectivity, then in the event of all the ISE PSN nodes being unreachable then the device will only get the connectivity you allow via the pre-auth ACL.
This is obviously quite undesirable and so when I raised this with TAC they suggested that I add an EEM script to each switch so that if the ISE PSN nodes become unavailable then the EEM script will kick in and add a "1 permit ip any any' at the top of the pre-auth ACL.

HT1311 i tried to do a backup from my old iphone as i have a new one that was signed into another itunes account. it said i cant do it because the iphone rejected the request. how do i get around this? i have signed out of the old acct and into mine on th

i tried to do a backup from my old iphone as i have a new one that was signed into another itunes account. it said i cant do it because the iphone rejected the request. how do i get around this? i have signed out of the old acct and into mine on the phone

What is the precise wording of the error message that occurs on the old iPhone when attempting to do a backup?
Are you attempting to backup via iTunes on the computer or iCloud?

ERM Role con't be deleted Automatically after rejecting the request in CUP

Hi Experts,
I am involving the GRC implimentation project and ERM component is succefully configured with post-installation activites and also configure the workflow(1-stage) in CUP for role approval.
After initiating request, the request was sent to appropriate approver for approval process and approved/ Rejected by the approver.For first case(Request approved) everything is looks fine.
but whenever the request is rejected (second case) by the approver, the role is still present in ERM and ABAP backend as well as.
please suggest me, if the role is deleted in ABAP/ERM system after rejecting the request by Role Approver in CUP. or still present the role in systems.
Regards,
Arjuna.

Hi Jes,
We so have a feature called Password Self Service which is used by users to reset their password using CUP. Also if the password is locked by multiple failed attempt, CUP even activate this user.
However in your case administrator will be locking the user or deactivating the password, so CUP will not allow users to unlock their users as it has been locked by administrator.
So CUP can only unlock those users which were locked due to failed attempts etc.
Regards,
Shweta

Rejecting a request in Custom Workflow

Hi
I have a custom workflow at operational level for two level of approvals. Workflow is working fine and assigning the request to the correct role but when a user of that role is trying to Reject the request he is getting the error on the console. I can see the below error in logs:
*[soa_server1] [ERROR] [] [oracle.soa.services.workflow.task] [tid: [ACTIVE].ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: level1approver] [ecid: 5d5629f8c05bbdb0:-69d83486:13ccea452b7:-8000-00000000000147ea,1:30185] [APP: soa-infra] <.> Bulk update is not allowed for this Task.[[*
This task expects the user to view task details before acting on it.
Make sure that the task is approved/rejected from task details page. Also ensure that TaskService API which takes task Object as input is used instead of the API which takes taskID as input.
ORABPEL-30094
Bulk update is not allowed for this Task.
This task expects the user to view task details before acting on it.
Make sure that the task is approved/rejected from task details page. Also ensure that TaskService API which takes task Object as input is used instead of the API which takes taskID as input.
As per my understanding the error is trying to say that open the request details page and then reject but the other part of the issue is when i am trying to open the Request details page( by clicking on the approval pending task), OIM is opening a blank pop-up which does not show anything.
Just for the information, We have two Human task in our workflow.
Thanks in Advance
Edited by: iam37 on Feb 16, 2013 4:22 PM

Hi Durga
The second part is not my concern, what i am assuming is it can be the browser issue or some host issue.
But the issue is it is throwing the exception for rejecting the request at first level if we are not checking the task details. But at second level we are able to reject the request without even checking the details.
In my workflow, I have two Human tasks for two different level of approval. My thought is that using two Human task is creating this inconsistent behavior.
Please suggest.
Thanks

Problem in ACS5.1 : "EAP session timed out", "RADIUS Request dropped "

Hi .
Part of my access points do not want to authenticate wi-fi users (through Radius server and Microsoft AD) .
The scheme is: wi-fi PC-access point -ACS server 5.1 (Radius)-Microsoft AD
After I configured some AP, next logs we can see :
EAP session timed out (many)
RADIUS Request dropped (many)
Could not establish connection with ACS Active Directory agent
User's Groups retrieval from Active Directory failed
The user is not found in the internal users identity store.
Another part of devices (AP) works well.
Anyone can help me to solve this problem please?

Hi Nicolas.
In logs usually we see some steps of beginning relations between devices. But here we see only one log line:
What can it mean?
The other messages seem to indicate that there is a problem with your AD. Did you test the bind ? Can you retrieve the AD groups list from ACS ?
Yes, we tested relations between AD and ACS, AD groups list retrieve fine from AD. In addition half of devices in network works fine: wi-fi devices authenticates excellent .
Do you use AD with the ACS for another part of your network that would be working fine ?
Yes, there is single AD and ACS.

Client Install Fails: Log: ClientIdManagerStartup - Server rejected registration request: 3

Trying to install the client onto Windows Server 2008 R2 Servers using ConfigMgr 2012R2. no PKI is being used. We do not see this issue on any workstations, only servers.
It returns the following:
Got registration response from MP. Client approval status: -1
[RegTask] - Server rejected registration request: 3 ClientIDManagerStartup
Actions taken based on other Articles:
1.Delete the c:\windows\smscfg.ini file
2) Run CCMDELCERT on the client
3) Restart the SMS agent Host service.
Result: FAILED, it comes back with the same errors.
MP_RegistrationManager.log shows:
MP Reg: Client in-band certificate is not valid due to failures in certificate chain validation, Raising status event. Failure HR = 0x800b010a, In-band Cert SubjectName = Servername - SERVER
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of MpEvent_CertInvalidChain
ClientID = "GUID:D32A0A76-E832-49B6-A431-084DB435FD83";
DateTime = "20140520175614.768000+000";
MachineName = "Servername.tes.name.com";
ProcessID = 3444;
SiteCode = "XYZ";
SubjectName = "Servername - SERVER";
ThreadID = 17368;
Win32ErrorCode = 2148204810;
MP Reg: Registration request body is invalid.
Any other ideas out there???
David Baur

Do the following to check the SMS self-signed certificates
Start MMC.exe
Add/Remove Snapin -> Select Certificates -> Select local computer
Locate the SMS folder
Find the SMS Signing certificate and SMS Encryption Cerrtificate - check if they have expired. If they have expired - delete them.
Retry client installation

ISE PSN rejecting RADIUS request

Similar Messages

Maybe you are looking for