3.42.10. KeepaliveNoreplyTimeout Previous topic Parent topic Child topic Next topic

This is an optional integer that specifies the waiting time, in seconds, for a Status-Server request. If no reply is received within the time KeepaliveNoreplyTimeout defines, the Status-Server request is marked as lost.
If KeepaliveNoreplyTimeout is not defined, the waiting time value depends on the AuthBy you are using:
  • <AuthBy RADCSEC>: NoreplyTimeout value is used instead.
  • <AuthBy RADIUS>: RetryTimeout value is used instead.
It is recommended to have a smaller value for KeepaliveNoreplyTimeout and a larger value for NoreplyTimeout or RetryTimeout. The Status-Server responder is always the next hop host and a reply is received quickly. With a short KeepaliveNoreplyTimeout, a possible failure situation is discovered quickly and the request is rerouted to another server. The final destination of an Access-Request or an Accounting-Request message may be located many hops away and for this reason a long NoreplyTimeout may be needed.
Here is an example of using both KeepaliveNoreplyTimeout and NoreplyTimeout in <AuthBy RADSEC>:
<AuthBy RADSEC>
      NoreplyTimeout 10
      KeepaliveNoreplyTimeout 3
</AuthBy>
To use this example with <AuthBy RADIUS>, you must use RetryTimeout instead of NoreplyTimeout.