Concurrency Report Accuracy:
The Concurrency Report is only as accurate as your RADIUS log files permit it to be. If there are inconsistencies with logging START or STOP accounting records, or the Acct-Session-Id and/or the Acct-Multi-Ssn-Id attributes are not logged correctly in both START and STOP records, then the Concurrency report will not be accurate.Concurrency Calculation:
By default concurrency is calculated for ALL users found in the RADIUS log file(s) who started (and possibly ended) sessions during the selected reporting period. Due to this it is possible that you will see user-names in the concurrency report that you have purposely not loaded into the SITE/GROUP/USER selection hierarchy for usage report generation purposes. If you are reporting on a select Site or Group of Users and you want to produce a concurrency report which lists just these users, then you can do this by going into the Advanced Settings of RADREP and clearing the check-box option labelled For the Concurrency and Active User reports, process all users in the log file. It is important to note that if you clear this option, the concurrency figure shown will not be the true concurrency reached on the NAS/RAS server or RADIUS Client device because only the users you have selected in the SITE/GROUP/USER hierarchy will be processed instead of all users found in the log file(s).Concurrency Duration:
Concurrency Duration is calculated by taking the least recent STOP date and time and subtracting this from the most recent START date and time. If no users have STOP records available then the concurrency duration can only be given as an estimate and this is calculated by taking the most recent START date and time and subtracting the least recent START date and time.Chronological Log File Record Order:
If you process more than one RADIUS accounting log at a time then concurrency figures will not be correct unless the logs are processed by RADREP in the same order they were written, from a date and time perspective. RADREP orders the logs before processing them. Ordering of the logs is based on the date of the first accounting record in each log. During times of fail-over between a RADIUS primary and secondary server it is possible that accounting records could be written out of sequence. Ordering the logs before processing them will not fix this problem. Processing log file accounting records that are out of chronological order will produce incorrect concurrency reports.Larger than Expected Concurrency Rate or Duration:
If there are large numbers of users in the Active User Sessions report table that also show up in the Concurrency report table with blocks of start dates that are distant from one other then there is a good chance your log file(s) are being processed out of chronological order. If no STOP record exists for a user session during the selected reporting period they will not have a 'Stop Date & Time' or 'Session Duration' displayed. If there are users displayed in the 'Maximum Concurrency' table with no 'Stop Date & Time' try increasing the report end date so that these user's STOP records can be found and processed. If after processing the entire date range of your log file(s) these users still appear in both the 'Maximum Concurrency' table and the 'Active Users' report then this indicates that no STOP record exists for these users. This could mean that they are still logged in, that there has been some sort of RADIUS server downtime, or there is something wrong with your RADIUS accounting and logging setup.Concurrency for a Specific NAS Server :
Unless you filter your logs on a specific NAS-IP-Address, Concurrency reports are generated for all NAS Servers. If you have multiple NAS servers all writing to the same RADIUS accounting log file but want to report on just one of them, you will need to use the NAS-IP-Address filter to dynamically filter the logs during processing. To dynamically filter the logs in RADREP go to the Advanced Settings configuration section, enable the Filter on NAS-IP-Address option, and specify the specific NAS Server IP Address you want to generate reports for.