Interlogix NS3550-8T-2S User Manual - Manual (Page 221)

221
RADIUS Accounting Servers
The statistics map closely to those specified in RFC4670 - RADIUS Accounting Client MIB.
Use the server select box to switch between the backend servers to show details for.
Object Description
RADIUS accounting server packet counter. There are five receive and four transmit
counters.
Direction Name RFC4670 Name Description
Rx Responses radiusAccClientExt
Responses The number of RADIUS
packets (valid or invalid)
received from the server.
Rx Malformed
Responses radiusAccClientExt
MalformedRespons
es The number of malformed
RADIUS packets received
from the server. Malformed
packets include packets with
an invalid length. Bad
authenticators or or unknown
types are not included as
malformed access responses.
Rx Bad
Authenticators radiusAcctClientExt
BadAuthenticators The number of RADIUS
packets containing invalid
authenticators received from
the server.
Rx Unknown Types radiusAccClientExt
UnknownTypes The number of RADIUS
packets of unknown types that
were received from the server
on the accounting port.
Rx Packets Dropped radiusAccClientExt
PacketsDropped The number of RADIUS
packets that were received
from the server on the
accounting port and dropped
for some other reason.
Tx Requests radiusAccClientExt
Requests The number of RADIUS
packets sent to the server.
This does not include
retransmissions.
Tx Retransmissions radiusAccClientExt
Retransmissions The number of RADIUS
packets retransmitted to the
RADIUS accounting server.
Tx Pending
Requests radiusAccClientExt
PendingRequests The number of RADIUS
packets destined for the server
that have not yet timed out or
received a response. This
variable is incremented when
a Request is sent and
decremented due to receipt of
a Response, timeout, or
retransmission.
 Packet Counters
Tx Timeouts radiusAccClientExt
Timeouts The number of accounting
timeouts to the server. After a
timeout, the client may retry to
the same server, send to a
different server, or give up. A
retry to the same server is
counted as a retransmit as
well as a timeout. A send to a
different server is counted as a
Request as well as a timeout.
This section contains information about the state of the server and the latest round-trip
time.  Other Info
Name RFC4670 Name Description