11-05-2008 07:33 AM - edited 03-04-2019 12:12 AM
We see numerous entries in the log about RADIUS_DEAD, RADIUS_ALIVE. Anyone seen this?
cisco WS-C6506-E (R7000) processor (revision 1.1) with 458752K/65536K bytes of memory.
Processor board ID SAL1215M20E
R7000 CPU at 300Mhz, Implementation 0x27, Rev 3.3, 256KB L2, 1024KB L3 Cache
Last reset from power-on
10 Virtual Ethernet interfaces
48 FastEthernet interfaces
57 Gigabit Ethernet interfaces
1915K bytes of non-volatile configuration memory.
65536K bytes of Flash internal SIMM (Sector size 512K).
Configuration register is 0x2102
System image file is "bootdisk:s3223-advipservicesk9_wan-mz.122-33.SXH2a.bin"
We have verified that the RADIUS serviuces on TACACS is active .
s0llbrt-core2#
Nov 5 10:20:26: %RADIUS-4-RADIUS_DEAD: RADIUS server 10.129.12.196:1645,1646 is not responding.
Nov 5 10:20:26: %RADIUS-4-RADIUS_ALIVE: RADIUS server 10.129.12.196:1645,1646 has returned.
s0llbrt-core2#
Nov 5 10:21:08: %RADIUS-4-RADIUS_DEAD: RADIUS server 10.129.12.128:1645,1646 is not responding.
Nov 5 10:21:08: %RADIUS-4-RADIUS_ALIVE: RADIUS server 10.129.12.128:1645,1646 has returned.
Nov 5 10:21:30: %RADIUS-4-RADIUS_DEAD: RADIUS server 10.129.12.196:1645,1646 is not responding.
Nov 5 10:21:30: %RADIUS-4-RADIUS_ALIVE: RADIUS server 10.129.12.196:1645,1646 has returned.
Nov 5 10:21:42: %RADIUS-4-RADIUS_DEAD: RADIUS server 10.129.12.128:1645,1646 is not responding.
Nov 5 10:21:42: %RADIUS-4-RADIUS_ALIVE: RADIUS server 10.129.12.128:1645,1646 has returned.
Nov 5 10:22:03: %RADIUS-4-RADIUS_DEAD: RADIUS server 10.129.12.196:1645,1646 is not responding.
Nov 5 10:22:03: %RADIUS-4-RADIUS_ALIVE: RADIUS server 10.129.12.196:1645,1646 has returned.
Nov 5 10:22:06: %RADIUS-4-RADIUS_DEAD: RADIUS server 10.129.12.128:1645,1646 is not responding.
Nov 5 10:22:06: %RADIUS-4-RADIUS_ALIVE: RADIUS server 10.129.12.128:1645,1646 has returned.
Nov 5 10:22:28: %RADIUS-4-RADIUS_DEAD: RADIUS server 10.129.12.196:1645,1646 is not responding.
Nov 5 10:22:28: %RADIUS-4-RADIUS_ALIVE: RADIUS server 10.129.12.196:1645,1646 has returned.
Nov 5 10:23:13: %RADIUS-4-RADIUS_DEAD: RADIUS server 10.129.12.128:1645,1646 is not responding.
Nov 5 10:23:13: %RADIUS-4-RADIUS_ALIVE: RADIUS server 10.129.12.128:1645,1646 has returned.
Nov 5 10:23:34: %RADIUS-4-RADIUS_DEAD: RADIUS server 10.129.12.196:1645,1646 is not responding.
Nov 5 10:23:34: %RADIUS-4-RADIUS_ALIVE: RADIUS server 10.129.12.196:1645,1646 has returned.
Nov 5 10:24:02: %RADIUS-4-RADIUS_DEAD: RADIUS server 10.129.12.128:1645,1646 is not responding.
Nov 5 10:24:02: %RADIUS-4-RADIUS_ALIVE: RADIUS server 10.129.12.128:1645,1646 has returned.
Nov 5 10:24:23: %RADIUS-4-RADIUS_DEAD: RADIUS server 10.129.12.196:1645,1646 is not responding.
Nov 5 10:24:23: %RADIUS-4-RADIUS_ALIVE: RADIUS server 10.129.12.196:1645,1646 has returned.
Nov 5 10:25:00: %RADIUS-4-RADIUS_DEAD: RADIUS server 10.129.12.128:1645,1646 is not responding.
Nov 5 10:25:00: %RADIUS-4-RADIUS_ALIVE: RADIUS server 10.129.12.128:1645,1646 has returned.
Nov 5 10:25:21: %RADIUS-4-RADIUS_DEAD: RADIUS server 10.129.12.196:1645,1646 is not responding.
Nov 5 10:25:21: %RADIUS-4-RADIUS_ALIVE: RADIUS server 10.129.12.196:1645,1646 has returned.
Nov 5 10:25:26: %RADIUS-4-RADIUS_DEAD: RADIUS server 10.129.12.128:1645,1646 is not responding.
Nov 5 10:25:26: %RADIUS-4-RADIUS_ALIVE: RADIUS server 10.129.12.128:1645,1646 has returned.
Nov 5 10:25:47: %RADIUS-4-RADIUS_DEAD: RADIUS server 10.129.12.128:1645,1646 is not responding.
Nov 5 10:25:47: %RADIUS-4-RADIUS_ALIVE: RADIUS server 10.129.12.128:1645,1646 has returned.
Nov 5 10:25:47: %RADIUS-4-RADIUS_DEAD: RADIUS server 10.129.12.196:1645,1646 is not responding.
Nov 5 10:25:47: %RADIUS-4-RADIUS_ALIVE: RADIUS server 10.129.12.196:1645,1646 has returned.
11-05-2008 07:40 AM
Can you ping 10.129.12.196? Is the radius server configured for this device? Are you using the right ports (we use 1812 and 1813 on Steel-Belted Radius) Do you have these commands in your config:
radius-server host x.x.x.x auth-port #### acct-port ####
radius-server key somekey
ip radius source-interface f 0/0 (or what ever interface might be applicable?)
11-05-2008 08:05 AM
s0llbrt-core1#ping 10.129.12.128
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.129.12.128, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/8 ms
s0llbrt-core1#ping 10.129.12.196
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.129.12.196, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/5/8 ms
ip radius source-interface Loopback0
radius-server attribute 8 include-in-access-req
radius-server host 10.129.12.128 auth-port 1645 acct-port 1646
radius-server host 10.129.12.196 auth-port 1645 acct-port 1646
radius-server source-ports 1645-1646
radius-server key 7 key
radius-server vsa send accounting
radius-server vsa send authentication
11-05-2008 08:45 AM
I received the same errors sometime back in some of my access points , hope this helps in your case too
If you have enabled the command " radius-server deadtime " then this an informational message , When you enable this setting, it causes the Cisco IOS software to mark dead any Radius servers that fail to respond to authentication requests, that avoid the wait for the request to time out before the attempt to the next configured server. A Radius server marked as dead is skipped by additional requests for the duration of minutes unless all servers are marked dead.
11-05-2008 10:04 AM
No, that command is not in my Config. I have listed all RADIUS_SERVER statements above in a previous post. Thanks anyway.
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