Solved

EXOS - show radius - round trip time

  • 7 August 2019
  • 2 replies
  • 109 views

Userlevel 6
New EXOS V30.2 shows this information:

code:
 RADIUS server       : 1 Status is Active
host name :
IP address : 10.0.1.52
Server IP Port: 1812
Client address: 10.1.0.4 (VR-Default)
Retries : 2 *
Timeout : 3 *
Realm : Netlogin
shared secret : [removed]
Access Requests : 1 Access Accepts : 1
Access Rejects : 0 Access Challenges : 9
Access Retransmits: 0 Client timeouts : 0
Bad authenticators: 0 Unknown types : 0
Round Trip Time : 3




How is this Round Trip Time measured ? Seconds (i guess) ?

Is this a average value of last radius session ? How many last session ?
Or is this the value of really last radius session ?

If anyone have some reliable information (no guessing) it will be very welcome!

Regards
icon

Best answer by Drew C. 12 August 2019, 18:52

@M.Nees, I heard back from engineering on this question.
From code inspection it appears this a count of “system ticks” each of which is 1/100th of a second. As such, the 3 would indicate 30 milliseconds (+/- 10 milliseconds due to the tick granularity) from when EXOS sends the request to the RADIUS server to when EXOS gets a response from the RADIUS server.
It is the value of the last successful exchange and does not average the value over multiple authentications.

The origin of the value is from RFC2618 (RADIUS authentication MIB):
code:
radiusAuthClientRoundTripTime  OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time interval (in hundredths of a second) between
the most recent Access-Reply/Access-Challenge and the
Access-Request that matched it from this RADIUS
authentication server."
::= { radiusAuthServerEntry 4 }
View original

2 replies

Userlevel 7
Round Trip Time has been available in the "show radius" command for a very long time. I checked an EXOS 11.2 command reference guide and it was listed.

Regarding the RTT units and what this value actually means, I've emailed two of the developers and will have to get back to you.
Userlevel 7
@M.Nees, I heard back from engineering on this question.
From code inspection it appears this a count of “system ticks” each of which is 1/100th of a second. As such, the 3 would indicate 30 milliseconds (+/- 10 milliseconds due to the tick granularity) from when EXOS sends the request to the RADIUS server to when EXOS gets a response from the RADIUS server.
It is the value of the last successful exchange and does not average the value over multiple authentications.

The origin of the value is from RFC2618 (RADIUS authentication MIB):
code:
radiusAuthClientRoundTripTime  OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time interval (in hundredths of a second) between
the most recent Access-Reply/Access-Challenge and the
Access-Request that matched it from this RADIUS
authentication server."
::= { radiusAuthServerEntry 4 }

Reply