
Diagnostic Parameters and Commands
Using diagnostics-related DO commands
MAX Administration Guide
B-47
[0000]: 02 01 48 60 08 02 1A 7B 05 04 03 80 90 A2 18 04
[0010]: E9 82 83 88 70 05 C1 34 39 39 30
pridisplay 0
PRI message display terminated
Quit
Description: Exits diagnostic mode.
Usage: Enter
quit
at the command prompt.
RadStats
Description: Displays a compilation of RADIUS Authentication and Accounting statistics.
Usage: Enter
radstats
at the command prompt.
Example:
> radstats
RADIUS authen stats:
In the following message,
A
denotes authentication and
O
denotes other. There were 612
authentication requests sent and 612 authentication responses received.
0 sent[A,O]=[612,15], rcv[A,O]=[612,8]
602 were authenticated successfully, and 18 were not:
timout[A,O]=[0,6], unexp=0, bad=18, authOK=602
In the next message, the IP address of the RADIUS server is 1.1.1.1, and the
curServerFlag
indicates whether or not this RADIUS server is the current authentication server. (You can
have several configured RADIUS servers, but only one is current at any one time.)
0
(zero)
indicates no. A
1
indicates yes.
IpAddress 1.1.1.1, curServerFlag 1
RADIUS accounting stats:
The next message indicates that the MAX sent 1557 Accounting packets and received 1555
responses (
ACKs
from the Accounting server). Therefore, the
unexp
value is
2
. This does not
necessarily indicate a problem, but might be the result of the MAX timing out a particular
session before receiving an
ACK
from the RADIUS server. Momentary traffic load might cause
this condition. The value of
bad
is the number of packets that were formatted incorrectly by
either the MAX or the RADIUS server.
0 sent=1557, rcv=1555, timout=0, unexp=2, bad=0
In the next message, the Accounting server is different from the Authentication server. The
Accounting and Authentication servers do not need to be running on the same host, although
they can be.
IpAddress 2.2.2.2, curServerFlag 1
Local Rad Acct Stats:
The next two messages can be used to look for traffic congestion problems or badly formatted
Accounting packets. Under typical conditions, you might see a few packets whose
acknowledgments fail.