cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
5041
Views
0
Helpful
13
Replies

15022 Could not find selected Access Service - Cisco ISE 2.4

drivera_
Level 1
Level 1

Hi everybody.   Right now I'm having an issue when connecting an endpoint.   This endpoint can't have a successful authorization access because it generates the error "15022 Could not find selected Access Service".  I'm looking for the root cause of this error online, but I haven't found anything yet.   I will apprecciate any help someone can give me.   I attached the error generated.

 

Thank you in advance.

1 Accepted Solution

Accepted Solutions

drivera_
Level 1
Level 1

Hi everybody,  we found the solution!

 

The issue was with the Active Directory sync, because the AD clock was not syc with the PSNs clocks.   Thank you so much for your help. 

 

 

View solution in original post

13 Replies 13

pan
Cisco Employee
Cisco Employee

You may have to check allowed protocol. Try using default allowed protocol.

Hi,

 

You mean by activating de Default Network Access option?  I attached two files, but right now we have configured two custom options on Allowed Protocols.  I'm confused.  

 

 

Can you show the step data? 

 

How are the clients authenticating? User/pass, cert etc?

 

Is it all the same devices, or just one?

We have the next envirnoment:  3 PSN, 2 PAN, and 2 MnMT.    We only have configured dot1x and MAB for now, and we're testing only Wired network devices.  We're using EAP-TLS and PEAP with dot1X and Internal Endpoints for mab.   I have attached images of all the configuratinos we have set.   There are several users with the same problem, and even when every endpoint has his certificate, it failed dot1x and starts MAB, sometimes failing too. 

 

I will apprecciate any help you guys can give me. 

just curious what config you have on switch side.

 

have you follow the best cisco ISE config on switch side

please do not forget to rate.

pan
Cisco Employee
Cisco Employee

Please use "Default network access" shown in first attachment. Also what method you are using for authentication?

We have the next envirnoment:  3 PSN, 2 PAN, and 2 MnMT.    We only have configured dot1x and MAB for now, and we're testing only Wired network devices.  We're using EAP-TLS and PEAP with dot1X and Internal Endpoints for mab.   I have attached images of all the configuratinos we have set.   There are several users with the same problem, and even when every endpoint has his certificate, it failed dot1x and starts MAB, sometimes failing too. 

 

I will apprecciate any help you guys can give me. 

Would suggest you to check the configuration at Policy > Policy Sets > Authentication. Here check every policy set for the section "Allowed Protocols / Server Sequence". See if any policy set has an empty one. If yes, choose one and save the config.


@Surendra wrote:

Would suggest you to check the configuration at Policy > Policy Sets > Authentication. Here check every policy set for the section "Allowed Protocols / Server Sequence". See if any policy set has an empty one. If yes, choose one and save the config.


Hi surendra.  I checked that and everything is OK with that.  All policy sets have the field "Allowed Protocols / Server Sequence" with a service list.  

Nidhi
Cisco Employee
Cisco Employee

Please raise a TAC case to troubleshoot this further. 

seem to me your authorization rules are not define properly.

you need to be more specific narrow it down for exmaple if

network access-EapTunnel = Peap MSCAP than permit

 

please do not forget to rate.

drivera_
Level 1
Level 1

Hi everybody,  we found the solution!

 

The issue was with the Active Directory sync, because the AD clock was not syc with the PSNs clocks.   Thank you so much for your help. 

 

 

gold.pigeon
Level 1
Level 1

When upgrading from Cisco ISE v2.2 to Cisco ISE v2.4 either an oridinary upgrade or an re-image to v2.4 followed by a restore from backup, I ran into the issue that some policy sets were missing the settings for Allowed Protocols.

 

When re-selecting the right allowed protocol, it works again.

CCIE Security #53075 | Aruba ACCX #703