Radius Accounting Authentication Association
Nicole Tan (Talk | contribs) |
Nicole Tan (Talk | contribs) (fixed link) |
||
| (3 intermediate revisions by one user not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
With version 2.7.31+, Toolpack has the Associated server field in the RADIUS Client configuration page: | With version 2.7.31+, Toolpack has the Associated server field in the RADIUS Client configuration page: | ||
| − | + | == General Usage == | |
| + | ===== Link accounting and authentication together logically ===== | ||
| − | == | + | 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. |
| − | + | ||
| − | + | So both servers have to be the 'current' at the same 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 | ||
| + | # In case of external failure Toolpack will switchover both stacks ACCT and AUTH to IPeradius | ||
| + | # In some specific cases of external failures Toolpack will switchover only one stack, so we will have AUTH to IPerbill and ACCT to IPeradius: | ||
| + | :* 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. | ||
| + | |||
| + | == Configuration == | ||
| + | *[[Web_Portal_Tutorial_Guide_v2.7#RADIUS_Authorization_and_Authentication|Web Portal v2.7: RADIUS Authorization and Authentication]] | ||
Latest revision as of 15:49, 5 February 2014
With version 2.7.31+, Toolpack has the Associated server field in the RADIUS Client configuration page:
Contents |
General Usage
Link accounting and authentication together logically
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.
So both servers have to be the 'current' at the same 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
- In case of external failure Toolpack will switchover both stacks ACCT and AUTH to IPeradius
- In some specific cases of external failures Toolpack will switchover only one stack, so we will have AUTH to IPerbill and ACCT to IPeradius:
- 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.
