Radius Accounting Authentication Association - Revision history

Nicole Tan: fixed link

2014-02-05T20:49:51Z

fixed link

Nicole Tan: Removed the screen, changed format and description

2014-02-05T20:47:02Z

Removed the screen, changed format and description

Nicole Tan: moved Radius Acct Auth Association to Radius Accounting Authentication Association: Use complete name to be more formal

2014-02-05T20:23:07Z

moved Radius Acct Auth Association to Radius Accounting Authentication Association: Use complete name to be more formal

Nicole Tan: NT: Completed the page

2014-02-04T21:37:54Z

NT: Completed the page

Nicole Tan at 21:06, 4 February 2014

2014-02-04T21:06:06Z

Nicole Tan: Created the initial page with the information of "RADIUS Accounting and Authorization Association"

2014-02-04T21:05:09Z

Created the initial page with the information of "RADIUS Accounting and Authorization Association"

New page

'''''Applies to version(s): v2.7'''''
{{DISPLAYTITLE:Toolpack:RADIUS Accounting and Authorization Association}}

With version 2.7.31+, Toolpack has the Associated server field in the RADIUS Client configuration page:
[[File:Radius_client_configuration_Association.jpg]]

== Multiple Radius Servers ==
Toolpack Radius AUTH/ACCT can be provisioned with several Radius servers (not only two).
Each Radius client processing AUTH and ACCT are flexibly configurable by:

=====Use polling (Status-Server)=====

=====Requests timeout and number of retries=====

This list of Radius servers can be configured here: [[Toolpack:Adding_RADIUS_server_B|Configuring Radius]]

== Current(Primary) Radius AUTH/ACCT server ==
If polling is enabled, the selected "Current" server will be the first that responds to the polling requests.
All other servers in the list will be flagged as "online" or "offline" depending whether it responses to the polling.

If polling is disabled, the server is selected in a round robin order, the first being tested successfully is the "Current".
All other servers in the list will be flagged as "online" or "offline" depending whether it responses to requests within the timeout and retries.

== Radius AUTH/ACCT switch-over ==
Let's take this scenario to explain the Radius AUTH/ACCT switchover feature:

We have servers '''A''' and '''B''', both 'online', and server '''A''' is 'Current'.

Request W　is sent to server '''A'''.

Request X，R,Z are in the queue sent to server '''A'''.

Server '''A''' doesn't respond to Request W. In consequence, server '''A''' is qualified as 'offline' and server B is elected as 'Current'.

Request W is then sent to server '''B'''.

All new requests M,Y,Q will be sent to server '''B'''.

The Request X which is in queue to '''A''', will be sent to '''A'''. If A is still qualified as 'offline'. It will be then sent to '''B'''.

If server '''A''' is back qualified as "online". It will process the request X.

The requests R,Z in queue will be processed same as X.

← Older revision		Revision as of 20:49, 5 February 2014
Line 28:		Line 28:

	== Configuration ==		== Configuration ==
−	*[[Web_Portal_Tutorial_Guide_v2.7#~~CDR~~\|Web Portal v2.7: RADIUS ~~configuration~~]]	+	*[[Web_Portal_Tutorial_Guide_v2.7#RADIUS_Authorization_and_Authentication\|Web Portal v2.7: RADIUS Authorization and Authentication]]

@@ Line 1: / Line 1: @@
 With version 2.7.31+, Toolpack has the Associated server field in the RADIUS Client configuration page:
-===== Association Field in Radius Configuration =====
+== General Usage ==
-[[File:Radius_client_configuration_Association.jpg]]
+===== Link accounting and authentication together logically =====
-−
-===== General Usage =====
-'''Link accounting and authorization together'''.
 This allows to specify that whenever one of the two associated server is the Current one, then the other one should also be set as the current one.
@@ Line 14: / Line 9: @@
 So both servers have to be the 'current' at the same time.
-'''The association can ensure that Toolpack sends RADIUS requests to a single physical RADIUS server at a time'''.
+===== Sends Acct/Auth requests to the same physical RADIUS server =====
 The association resolves a problem when you would have two physical RADIUS servers, each server hosts an accounting and authorization server, and you have a limitation on the Radius server to run the primary accounting and authentication on the same server (identical IP).
-===== A specific scenario =====
 There are 2 Radius AUTH servers provisioned (IPerbill & IPeradius) and 2 Radius ACCT servers provisioned (the same IPerbill & IPeradius)
 So there are 3 different possibilities for switchover:
-.- Toolpack will work with IPerbill as master for ACCT and AUTH
+# Toolpack will work with IPerbill as master for ACCT and AUTH
-.- In case of external failure Toolpack will switchover both stacks ACCT and AUTH to IPeradius
+In this case, associating the accounting and authentication to the same IP will prevent occurrence of scenario 3.
-.- In some specific cases of external failures Toolpack will switchover only one stack, so we will have AUTH to IPerbill and ACCT to IPeradius:
+== Configuration ==
+*[[Web_Portal_Tutorial_Guide_v2.7#CDR|Web Portal v2.7: RADIUS configuration]]
-- either: AUTH to IPerbill and ACCT to IPeradius
-−
-- or: ACCT to IPerbill and AUTH to IPeradius
-−
-In this case, associating the accounting and authentication to the same IP will prevent occurrence of scenario 3.

@@ Line 3: / Line 3: @@
 With version 2.7.31+, Toolpack has the Associated server field in the RADIUS Client configuration page:
 [[File:Radius_client_configuration_Association.jpg]]
@@ Line 8: / Line 9: @@
 Toolpack Radius AUTH/ACCT can be provisioned with several Radius servers (not only two).
 Each Radius client processing AUTH and ACCT are flexibly configurable by: