I currently have (open)SER configured to write accounting records to a radius server. However there is a possibility that the Radius server may become unavailable. What is the recommended way to deal with this scenario? Is there a way to cache accounting records? Or is it best to write records to both flatfile and the radius server? Something like this: modparam("acc", "db_flag", 1) modparam("acc", "db_missed_flag", 3) modparam("acc", "radius_config", "/etc/radiusclient-ng/radiusclient.conf") modparam("acc", "radius_flag", 1) modparam("acc", "radius_missed_flag", 3)
Any suggestions would be appreciated.
Regards
Cameron
Hi Cameron,
as far as I know, the radius client library does not provide any support for RADIUS server failover. OpenSER cannot do anything about this as the radius configuration is not available to it (it is directly loaded by the radius client library).
most probably you should try to come up with an HA configuration for your Radius server. Using a secondary logging backend is got, but see how this affects the load on your server.
regards, bogdan
kjcsb wrote:
I currently have (open)SER configured to write accounting records to a radius server. However there is a possibility that the Radius server may become unavailable. What is the recommended way to deal with this scenario? Is there a way to cache accounting records? Or is it best to write records to both flatfile and the radius server? Something like this: modparam("acc", "db_flag", 1) modparam("acc", "db_missed_flag", 3) modparam("acc", "radius_config", "/etc/radiusclient-ng/radiusclient.conf") modparam("acc", "radius_flag", 1) modparam("acc", "radius_missed_flag", 3)
Any suggestions would be appreciated.
Regards
Cameron
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
-
Bogdan-Andrei Iancu -
kjcsb