No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Problem with selection of active RADIUS server on ME60

Publication Date:  2013-04-23 Views:  27 Downloads:  0
Issue Description
Problem was that priority of active radius server could not be changed by entering related weight.
Handling Process
First, the configuration of ME60 was checked. It was found:
radius-server group start-ip
 radius-server authentication 10.73.32.200 1645 weight 1
 radius-server authentication 10.73.32.201 1745 weight 0
 radius-server accounting 10.73.32.200 1646 weight 1
 radius-server accounting 10.73.32.201 1746 weight 0
 radius-server shared-key RADIUS-HBRAS1
 radius-server timeout 10
 radius-server accounting-stop-packet resend 50
 radius-server source interface LoopBack0
RADIUS server with ip 10.73.32.201 must be set with more high priority than 10.73.32.200 (see above part of config file).
Root Cause

When multiple authentication or accounting servers are configured in the RADIUS server group, you can configure the algorithm for selecting the RADIUS servers. The algorithm of selecting the RADIUS server is classified into loading-balancing and primary/secondary.

Loading-balancing: The ME60 allocates the load based on the weights of the servers.

Primary/Secondary: The first configured server functions as the primary server, and the others act as the secondary servers.
The algorithm for selecting the RADIUS server could be configured.

Solution

By default, the algorithm for selecting the RADIUS server is primary/secondary.
So, we need to configure load-balancing algorithm by below commands to solve the problem:
system-view
radius-server group group-name
radius-server algorithm loading-share

END