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

Radius Authentication success rate algorithm

Publication Date:  2014-10-24 Views:  52 Downloads:  0
Issue Description

【 ProblemSu mm ary 】 RADIUS MIB problem
【 ProblemDetails 】

We can use the following node to collect the OID, RADIUS authentication information:

Authentication requests

RadiusAuthClientAccessRequests (1.3.6.1.2.1.67.1.2.1.1.3.1.5)

Authentication successful requests

RadiusAuthClientAccessAccepts (1.3.6.1.2.1.67.1.2.1.1.3.1.7)

Authentication fail requests

RadiusAuthClientAccessRejects (1.3.6.1.2.1.67.1.2.1.1.3.1.8)

 

 

We can find that after the BRAS upgraded to V6r6 the authentication successful  rate is not like before (The authentication successful rate is around 50% before but now it is around 99% )

For example:

Bash -3.00 $ snmpwalk-v 2c X.X.X.XSJZX - R @.1.3.6.1.2.1.67.1.2.1.1.3.1
...

67.1.2.1.1.3.1.3.1 = 0

67.1.2.1.1.3.1.5.2 = Counter32: 1017518 Authentication requests

 

67.1.2.1.1.3.1.7.2 = Counter32: 1016053 Authentication successful times

 

67.1.2.1.1.3.1.8.2 = Counter32: 625829 Authentication failure times

 

 

The statistics on equipment are as follows:

<ME60> disradius server packet IP - address A.B.C.Dauthentication
Totalradius server authenticationpackets
:

AccessRequests      . 1019460       AccessRet RAN smissions        . 2073
AccessAccepts        . 391909         AccessRejects                         628154.
AccessChallenges :                   MalformedAccessResponses..
BadAuthenticators:                   PendingRequests                    ..
Timeouts                    . 2119             UnknownTypes                          ..
PacketsDropped      :
Last 30 minutesradius server authenticationpackets
:
AccessRequests      . 6538             AccessRet RAN smissions        . 9
AccessAccepts        . 2720             AccessRejects                        . 3818
AccessChallenges :    0                  MalformedAccessResponses..     0
BadAuthenticators:     0                   PendingRequests                    .. 0
Timeouts                    . 9                   UnknownTypes                       ..0
PacketsDropped      : 0

 

 

Please check whether they count both of the accept number and reject number into the accept number in the new version.

Handling Process

NA

Root Cause

The definition of the successful authentication times(RadiusAuthClientAccessAccepts " 1.3.6.1.2.1.67.1.2.1.1.3.1.7 ") have been modified in V6R6 version. It is including Access Accepts / Access Rejects / Access Challenges statistics.

And also the definition of the authentication request(RadiusAuthClientAccessRequests " 1.3.6.1.2.1.67.1.2.1.1.3.1.5 ) have been modified in V6R6. It is including Access Requests/Access Retransmissions statistics.

 

 

The definition of the successful authentication times(RadiusAuthClientAccessAccepts " 1.3.6.1.2.1.67.1.2.1.1.3.1.7 ") have been modified in V6R5 version. It is including Access Accepts statistics.

And also the definition of the authentication request(RadiusAuthClientAccessRequests " 1.3.6.1.2.1.67.1.2.1.1.3.1.5 ) have been modified in V6R5. It is including Access Requests  statistics.

Solution

Different versions  have difference algorithms,  so the issue is properly.

END