Buy or Renew
Buy or Renew
Cisco Virtual Engineer generative AI bot now active in Wireless Discussion Forum. Learn more.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
1440
Views
0
Helpful
10
Replies

Wlc Radius authentication

studmuffin
Level 1
Level 1

‎09-27-2022 04:03 PM

I keep getting this error but i with different ID I have now idea what is cuasing it i had it working before then i moved my dc vm;s and did some work moved them back on and then it stopped working i cant figure out what is wrong 

Log System Time Trap
0Tue Sep 27 05:46:13 2022RADIUS server 192.168.40.58:1812 failed to respond to request (ID 175) for client e6:6c:be:80:34:a0 / user 'ThePlague'
1Tue Sep 27 05:42:37 2022RADIUS server 192.168.40.58:1812 failed to respond to request (ID 174) for client e6:6c:be:80:34:a0 / user 'ThePlague'
2Tue Sep 27 05:29:46 2022RADIUS server 192.168.40.55:1812 failed to respond to request (ID 165) for client e6:6c:be:80:34:a0 / user 'ThePlague'
3Tue Sep 27 05:16:40 2022RADIUS server 192.168.40.55:1813 failed to respond to request (ID 18) for client a0:88:69:01:56:62 / user 'a0-88-69-01-56-62'
4Tue Sep 27 05:16:26 2022RADIUS server 192.168.40.55:1813 failed to respond to request (ID 17) for client a0:88:69:01:56:62 / user 'a0-88-69-01-56-62'
5Tue Sep 27 05:12:19 2022RADIUS server 192.168.40.55:1812 failed to respond to request (ID 164) for client e6:6c:be:80:34:a0 / user 'ThePlague'
6Tue Sep 27 05:12:12 2022RADIUS server 192.168.40.55:1812 failed to respond to request (ID 163) for client e6:6c:be:80:34:a0 / user 'ThePlague'
7Tue Sep 27 05:06:32 2022RADIUS server 192.168.40.55:1812 failed to respond to request (ID 162) for client e6:6c:be:80:34:a0 / user 'ThePlague'
8Tue Sep 27 05:02:55 2022RADIUS server 192.168.40.55:1812 failed to respond to request (ID 65) for client a0:88:69:01:56:62 / user 'host/Studmuffin-Lab.Studmuffin.com'
9Tue Sep 27 05:02:38 2022RADIUS server 192.168.40.55:1812 failed to respond to request (ID 161) for client e6:6c:be:80:34:a0 / user 'ThePlague'
10Tue Sep 27 04:56:39 2022RADIUS server 192.168.40.55:1812 failed to respond to request (ID 160) for client e6:6c:be:80:34:a0 / user 'ThePlague'
11Tue Sep 27 04:56:23 2022RADIUS server 192.168.40.55:1812 failed to respond to request (ID 159) for client e6:6c:be:80:34:a0 / user 'ThePlague'
12Tue Sep 27 04:46:54 2022RADIUS server 192.168.40.55:1812 failed to respond to request (ID 139) for client 80:fd:7a:4a:21:94 / user 'Studmuffin.com\ThePlague'
13Tue Sep 27 04:46:25 2022RADIUS server 192.168.40.55:1812 failed to respond to request (ID 138) for client 80:fd:7a:4a:21:94 / user 'Studmuffin.com\ThePlague'
14Tue Sep 27 04:45:52 2022RADIUS server 192.168.40.55:1812 failed to respond to request (ID 137) for client 80:fd:7a:4a:21:94 / user 'Studmuffin.com\ThePlague'
15Tue Sep 27 04:45:11 2022RADIUS server 192.168.40.55:1812 failed to respond to request (ID 136) for client 80:fd:7a:4a:21:94 / user 'Studmuffin.com\ThePlague'
16Tue Sep 27 04:44:39 2022RADIUS server 192.168.40.55:1812 failed to respond to request (ID 135) for client 80:fd:7a:4a:21:94 / user 'Studmuffin.com\ThePlague'
17Tue Sep 27 04:44:19 2022RADIUS server 192.168.40.55:1812 failed to respond to request (ID 134) for client 80:fd:7a:4a:21:94 / user 'Studmuffin.com\ThePlague'
18Tue Sep 27 04:44:12 2022RADIUS server 192.168.40.55:1812 failed to respond to request (ID 158) for client e6:6c:be:80:34:a0 / user 'ThePlague'
19Tue Sep 27 04:42:00 2022RADIUS acct-server 192.168.40.55:1813 available
20Tue Sep 27 04:28:16 2022RADIUS server 192.168.40.55:1813 failed to respond to request (ID 3) for client a0:88:69:01:56:62 / user 'a0-88-69-01-56-62'
21Tue Sep 27 04:26:59 2022RADIUS server 192.168.40.55:1813 failed to respond to request (ID 2) for client a0:88:69:01:56:62 / user 'a0-88-69-01-56-62'
22Tue Sep 27 04:15:39 2022Noise Profile Updated to Pass for Base Radio MAC: 3c:08:f6:9a:b3:e0 and slotNo: 0
23Tue Sep 27 04:12:29 2022Noise Profile Failed for Base Radio MAC: 3c:08:f6:9a:b3:e0 and slotNo: 0
24Tue Sep 27 03:22:11 2022RADIUS ACCT Server 192.168.40.55:1813 deactivated in global list
25Tue Sep 27 03:22:11 2022RADIUS server 192.168.40.55:1813 failed to respond to request (ID 0) for client a0:88:69:01:56:62 / user 'a0-88-69-01-56-62'
26Tue Sep 27 03:17:54 2022RADIUS server 192.168.40.55:1813 failed to respond to request (ID 4) for client 46:26:69:af:1a:c4 / user '46-26-69-af-1a-c4'
27Tue Sep 27 03:17:20 2022RADIUS server 192.168.40.55:1812 failed to respond to request (ID 157) for client e6:6c:be:80:34:a0 / user 'ThePlague'
28Tue Sep 27 03:13:42 2022RADIUS server 192.168.40.55:1813 failed to respond to request (ID 3) for client 46:26:69:af:1a:c4 / user '46-26-69-af-1a-c4'
29Tue Sep 27 03:13:22 2022RADIUS server 192.168.40.55:1812 failed to respond to request (ID 156) for client e6:6c:be:80:34:a0 / user 'ThePlague'
30Tue Sep 27 03:10:31 2022RADIUS ACCT Server 192.168.40.55:1813 deactivated in global list
31Tue Sep 27 03:10:31 2022RADIUS acct-server 192.168.40.55:1813 unavailable
32Tue Sep 27 03:10:31 2022RADIUS server 192.168.40.55:1813 failed to respond to request (ID 2) for client 46:26:69:af:1a:c4 / user '46-26-69-af-1a-c4'
33Tue Sep 27 03:09:57 2022RADIUS server 192.168.40.55:1812 failed to respond to request (ID 155) for client e6:6c:be:80:34:a0 / user 'ThePlague'
34Tue Sep 27 03:08:13 2022RADIUS server 192.168.40.55:1813 failed to respond to request (ID 1) for client 46:26:69:af:1a:c4 / user '46-26-69-af-1a-c4'
35Tue Sep 27 03:07:39 2022RADIUS server 192.168.40.55:1812 failed to respond to request (ID 154) for client e6:6c:be:80:34:a0 / user 'ThePlague'
36Tue Sep 27 03:07:30 2022RADIUS server 192.168.40.55:1813 failed to respond to request (ID 0) for client 46:26:69:af:1a:c4 / user '46-26-69-af-1a-c4'
37Tue Sep 27 03:06:56 2022RADIUS server 192.168.40.55:1812 failed to respond to request (ID 153) for client e6:6c:be:80:34:a0 / user 'ThePlague'
38Tue Sep 27 03:05:21 2022RADIUS server 192.168.40.55:1812 failed to respond to request (ID 152) for client e6:6c:be:80:34:a0 / user 'ThePlague'
39Tue Sep 27 03:05:04 2022RADIUS server 192.168.40.55:1812 failed to respond to request (ID 151) for client e6:6c:be:80:34:a0 / user 'ThePlague'
40Tue Sep 27 03:04:47 2022RADIUS server 192.168.40.55:1812 failed to respond to request (ID 150) for client e6:6c:be:80:34:a0 / user 'ThePlague'
41Tue Sep 27 02:52:15 2022RADIUS server 192.168.40.55:1812 failed to respond to request (ID 55) for client a0:88:69:01:56:62 / user 'host/Studmuffin-Lab.Studmuffin.com'
42Tue Sep 27 02:51:53 2022RADIUS server 192.168.40.55:1812 failed to respond to request (ID 149) for client e6:6c:be:80:34:a0 / user 'ThePlague'
43Tue Sep 27 02:51:37 2022RADIUS server 192.168.40.55:1812 failed to respond to request (ID 148) for client e6:6c:be:80:34:a0 / user 'ThePlague'
44Tue Sep 27 02:49:09 2022RADIUS server 192.168.40.55:1812 failed to respond to request (ID 147) for client e6:6c:be:80:34:a0 / user 'Studmuffin.com\ThePlague'
45Tue Sep 27 02:47:43 2022RADIUS server 192.168.40.55:1812 failed to respond to request (ID 146) for client e6:6c:be:80:34:a0 / user 'Studmuffin.com\ThePlague'
46Tue Sep 27 02:47:26 2022RADIUS server 192.168.40.55:1812 failed to respond to request (ID 145) for client e6:6c:be:80:34:a0 / user 'Studmuffin.com\ThePlague'
47Tue Sep 27 02:45:01 2022RADIUS server 192.168.40.55:1812 failed to respond to request (ID 13) for client f8:1a:2b:33:58:4b / user 'ThePlague'
48Tue Sep 27 02:44:43 2022RADIUS server 192.168.40.55:1812 failed to respond to request (ID 12) for client f8:1a:2b:33:58:4b / user 'ThePlague'
49Tue Sep 27 02:23:56 2022RADIUS server 192.168.40.55:1812 failed to respond to request (ID 11) for client f8:1a:2b:33:58:4b / user 'ThePlague'
50Tue Sep 27 02:23:39 2022RADIUS server 192.168.40.55:1812 failed to respond to request (ID 10) for client f8:1a:2b:33:58:4b / user 'ThePlague'
51Tue Sep 27 02:22:25 2022RADIUS server 192.168.40.55:1812 failed to respond to request (ID 144) for client e6:6c:be:80:34:a0 / user 'ThePlague'
 
 
 
 
That is just some of the logs any ides?
0 Helpful
10 Replies 10

studmuffin
Level 1
Level 1

‎09-27-2022 06:07 PM

<Event><Timestamp data_type="4">09/27/2022 20:03:55.824</Timestamp><Computer-Name data_type="1">STUDMUFFIN-DC</Computer-Name><Event-Source data_type="1">IAS</Event-Source><User-Name data_type="1">46-26-69-af-1a-c4</User-Name><NAS-Port data_type="0">13</NAS-Port><NAS-IP-Address data_type="3">192.168.100.5</NAS-IP-Address><Framed-IP-Address data_type="3">192.168.30.50</Framed-IP-Address><Framed-IPv6-Prefix data_type="2">0040FE800000000000000000000000000000</Framed-IPv6-Prefix><NAS-Identifier data_type="1">StudmuffinWireless</NAS-Identifier><Vendor-Specific data_type="2">00003763010600000002</Vendor-Specific><Acct-Session-Id data_type="1">633253d7/46:26:69:af:1a:c4/8648</Acct-Session-Id><NAS-Port-Type data_type="0">19</NAS-Port-Type><Acct-Authentic data_type="0">3</Acct-Authentic><Tunnel-Type data_type="0">13</Tunnel-Type><Tunnel-Medium-Type data_type="0">6</Tunnel-Medium-Type><Tunnel-Pvt-Group-ID data_type="1">30</Tunnel-Pvt-Group-ID><Event-Timestamp data_type="4">09/27/2022 07:52:10</Event-Timestamp><Acct-Status-Type data_type="0">3</Acct-Status-Type><Acct-Input-Octets data_type="0">7259227</Acct-Input-Octets><Acct-Input-Gigawords data_type="0">0</Acct-Input-Gigawords><Acct-Output-Octets data_type="0">19371290</Acct-Output-Octets><Acct-Output-Gigawords data_type="0">0</Acct-Output-Gigawords><Acct-Input-Packets data_type="0">27967</Acct-Input-Packets><Acct-Output-Packets data_type="0">28876</Acct-Output-Packets><Acct-Session-Time data_type="0">22482</Acct-Session-Time><Acct-Delay-Time data_type="0">0</Acct-Delay-Time><Calling-Station-Id data_type="1">46-26-69-af-1a-c4</Calling-Station-Id><Called-Station-Id data_type="1">f4-7f-35-b6-a8-a0</Called-Station-Id><Client-IP-Address data_type="3">192.168.100.5</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">StudmuffinWireless</Client-Friendly-Name><Cisco-AV-Pair data_type="1">audit-session-id=c0a8640500000b90633253d7</Cisco-AV-Pair><Proxy-Policy-Name data_type="1">StudsUsers</Proxy-Policy-Name><Packet-Type data_type="0">4</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>

That is what i get in my wireless logs from accounting so i dont think it is connection or firewall issue if i am getting updates in accounting

0 Helpful

ammahend
VIP
VIP

‎09-27-2022 07:14 PM

can you run aaa test to your radius and share what you see on wlc as well as on radius

test aaa radius username <user name> password <password> wlan-id <wlan-id> ap-group <apgroup-name> server-index <server-index>

-hope this helps-
0 Helpful

studmuffin
Level 1
Level 1
In response to ammahend

‎09-27-2022 07:24 PM

what is the server-index and how do i find it

 

0 Helpful

studmuffin
Level 1
Level 1
In response to studmuffin

‎09-27-2022 07:30 PM

studmuffin_0-1664332214970.png

Does that look correct

 

0 Helpful

studmuffin
Level 1
Level 1
In response to studmuffin

‎09-27-2022 07:31 PM

studmuffin_1-1664332288326.png

that is the result

0 Helpful

ammahend
VIP
VIP
In response to studmuffin

‎09-30-2022 06:27 AM

can you share the full test command you ran ?

-hope this helps-
0 Helpful

ammahend
VIP
VIP
In response to studmuffin

‎09-30-2022 06:26 AM

ammahend_0-1664544436426.png

sorry for the late reply.

-hope this helps-
0 Helpful

Arshad Safrulla
VIP Alumni
VIP Alumni

‎09-28-2022 02:23 PM - edited ‎09-28-2022 02:24 PM

Looks like your radius servers are not reachable from WLC. Please check whether the Radius source interface of WLC can reach the Radius server, if there is any firewall/ routers in the path please make sure that you have required routing/policies are created to allow the traffic. From Radius server side check it's availability and reachability to its gateway and to the NAD. If avaialble and reachability is fine, please check whether the required services are running as expected.

If the issue persists, please share more info on WLC model, code etc. and Radius server model, code etc.

___________________________________________
TAC recommended codes for AireOS WLC's
Best Practices for AireOS WLC's
TAC recommended codes for 9800 WLC's
Best Practices for 9800 WLC's
Cisco Wireless compatibility matrix
___________________________________________
Arshad Safrulla
0 Helpful

studmuffin
Level 1
Level 1
In response to Arshad Safrulla

‎09-28-2022 02:35 PM

there is no firewall rules in between the radius server and the wlc the wlc can ping the radius server and accounting works The radius server is running a vmware esxi vm and the hardware is connected via trunk ports to much switch the router is a cisco 2901 router doing router on a stick and there are no access lists on the interfaces there is one ip route out to the internet and no nat there is a firewall but that would have nothing to do with it i have tried it with both windows firewall on and off and no change i am not sure what services are required but i checked to make sure nps was running and i even gave it a restart 

0 Helpful

bsmagulov1
Level 1
Level 1

‎12-05-2022 03:23 AM

Here you can find some advice on the topic:

https://youtu.be/lZl_jv1keg8

0 Helpful
Customers Also Viewed These Support Documents
Review Cisco Networking products for a $25 gift card