Cisco 2960 and WLC Accounting Interim-Update
I don't believe this is controlled by FreeRadius itself but I am kind of at a loss figuring out where it might be configured. I have Freeradius acting as an AAA server for a Cisco 2960 L2 switch as well as a Cisco Wireless LAN Controller. Working on setting up Accounting which for the most part works. However I am unable to determine what causes the Interim-Update Acct-Status-Type message to be sent. Checking the detail log (have that module turned on in accounting section) I have seen those messages present. In fact earlier in the day connected clients sent a few Interim-Update messages (one was 1 second apart, than 10 seconds apart, than 30 seconds apart). That happened early this morning. However ever since that I have not seen any Interim-Update accounting messages. I read through the 802.1x configuration guide for the 2960 and it just talks about the Interim-Update message being sent but doesn't list of a way to specify the interval (assuming that interval is specified on the switch side). Any help would be appreciated. Thanks
Matthew Ceroni wrote:
Working on setting up Accounting which for the most part works. However I am unable to determine what causes the Interim-Update Acct-Status-Type message to be sent. Checking the detail log (have that module turned on in accounting section) I have seen those messages present. In fact earlier in the day connected clients sent a few Interim-Update messages (one was 1 second apart, than 10 seconds apart, than 30 seconds apart). That happened early this morning. However ever since that I have not seen any Interim-Update accounting messages.
The NAS originates accounting packets. If it's not originating accounting packets, blame the NAS. This is a common theme with RADIUS. FreeRADIUS isn't perfect, but when things go wrong, blaming the NAS and/or the SQL server is a pretty good decision. Alan DeKok.
Alan: Ya, I figured it was the NAS. All the reading I did seemed to suggest that. I was able to force the 2960 to sent at regular intervals by setting the Acct-Interim-Interval option in the Accept-Request packet. But that didn't work for the WLC. On Mon, Apr 7, 2014 at 4:11 PM, Alan DeKok <aland@deployingradius.com>wrote:
Matthew Ceroni wrote:
Working on setting up Accounting which for the most part works. However I am unable to determine what causes the Interim-Update Acct-Status-Type message to be sent. Checking the detail log (have that module turned on in accounting section) I have seen those messages present. In fact earlier in the day connected clients sent a few Interim-Update messages (one was 1 second apart, than 10 seconds apart, than 30 seconds apart). That happened early this morning. However ever since that I have not seen any Interim-Update accounting messages.
The NAS originates accounting packets. If it's not originating accounting packets, blame the NAS.
This is a common theme with RADIUS. FreeRADIUS isn't perfect, but when things go wrong, blaming the NAS and/or the SQL server is a pretty good decision.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On Mon, Apr 07, 2014 at 04:19:10PM -0700, Matthew Ceroni wrote:
On Mon, Apr 7, 2014 at 4:11 PM, Alan DeKok <aland@deployingradius.com>wrote:
This is a common theme with RADIUS. FreeRADIUS isn't perfect, but when things go wrong, blaming the NAS and/or the SQL server is a pretty good decision.
I was able to force the 2960 to sent at regular intervals by setting the Acct-Interim-Interval option in the Accept-Request packet. But that didn't work for the WLC.
The WLC will send interim-update packets when something changes. So for example you'll see an acct-start without an IP when the session begins, then an interim-update with the IP address after DHCP has completed. You also get an update when the client roams to a different AP. If you want regular updates, look under WLANs -> your wlan -> Security -> AAA Servers -> Tick "Interim Update" -> Set Interim Interval or use config wlan radius_server acct interim-update ... at the command line. But on a busy system, you'll get a lot of (probably unnecessary) updates that you may not want putting load on your server. Cheers, Matthew -- Matthew Newton, Ph.D. <mcn4@le.ac.uk> Systems Specialist, Infrastructure Services, I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom For IT help contact helpdesk extn. 2253, <ithelp@le.ac.uk>
participants (3)
-
Alan DeKok -
Matthew Ceroni -
Matthew Newton