Sorry this should be "Accounting-Start" and "Accounting-Stop" From: freeradius-users-bounces+frank.wei=4rf.com@lists.freeradius.org [mailto:freeradius-users-bounces+frank.wei=4rf.com@lists.freeradius.org] On Behalf Of Frank Wei Sent: Thursday, 4 December 2014 11:35 a.m. To: FreeRadius users mailing list Subject: Accounting-Start and Accounting-Off Hi All, I have a few questions about the "Accounting-Start" and "Accounting-Off". 1. If a NAS configured to have a primary and a backup RADIUS server. To start with all the "Accounting-Start" records will be in the primary RADIUS server. Later on the primary server goes down (Primary server won't tell the NAS?). When sessions stop, the NAS sends the "Accounting-Stop" to the secondary. I understand the "Start-Stop" record with the same "user name" and "session-id" ideally should be recorded in the same server. If this situation happens what should both the NAS and RADIUS server do? 2. A NAS configured to have a primary and backup RADIUS server. To start with all the "Accounting-Start" records will be in the primary RADIUS server. Later on the administrator decided to change the primary server (as there are problems with the previous primary). sessions stop, the NAS sends the "Accounting-Stop" to the new primary. This ends up the "Accounting-Start" and "Accounting-Stop" with the same "user name" and "session Id" in two RADIUS servers. To summarize, how to avoid the "start-stop" pair ends up in different servers ? If it does, is it an issue for RADIUS application ? Cheers, 4RF Limited The information in this email communication (inclusive of attachments) is confidential to 4RF Limited and the intended recipient(s). If you are not the intended recipient(s), please note that any use, disclosure, distribution or copying of this information or any part thereof is strictly prohibited and that the author accepts no liability for the consequences of any action taken on the basis of the information provided. If you have received this email in error, please notify the sender immediately by return email and then delete all instances of this email from your system. 4RF Limited will not accept responsibility for any consequences associated with the use of this email (including, but not limited to, damages sustained as a result of any viruses and/or any action or lack of action taken in reliance on it). The information in this email communication (inclusive of attachments) is confidential to 4RF Limited and the intended recipient(s). If you are not the intended recipient(s), please note that any use, disclosure, distribution or copying of this information or any part thereof is strictly prohibited and that the author accepts no liability for the consequences of any action taken on the basis of the information provided. If you have received this email in error, please notify the sender immediately by return email and then delete all instances of this email from your system. 4RF Limited will not accept responsibility for any consequences associated with the use of this email (including, but not limited to, damages sustained as a result of any viruses and/or any action or lack of action taken in reliance on it).