Lucent Technologies Stinger, Administration Manual

Page: 342 / 374

A-20 Stinger® Administration Guide
Using Debug Commands
RADIUS debugging
Displaying RADIUS authentication and accounting statistics
The radstats debug command displays a compilation of RADIUS authentication and
accounting statistics.
To enable radstats debugging, enter radstats at the command prompt as shown:
admin> radstats
RADIUS authen stats:
In the following sample 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]
Of connections attempts, 602 were authenticated successfully, and 18 were not:
timout[A,O]=[0,6], unexp=0, bad=18, authOK=602
In the next sample 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 indicates no . 1 indicates yes .
IpAddress 1.1.1.1, curServerFlag 1
RADIUS accounting stats:
The next message indicates that the Stinger unit sent 1557 accounting packets and
received 1555 responses (
ACKs from the accounting server). Therefore, the unexp
value is 2 . This value does not necessarily indicate a problem, but might be the result
of the Stinger unit timing out a particular session before receiving an ACK from the
RADIUS server. A momentarily heavy traffic load might cause this condition. The
value of
bad is the number of packets that were formatted incorrectly by either the
Stinger unit or the RADIUS server.
0 sent=1557, rcv=1555, timout=0, unexp=2, bad=0
In the next message, note that 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:
You can use the next two messages to look for traffic congestion problems or badly
formatted accounting packets. Under typical conditions, you might see a few packets
whose acknowledgments fail.
nasPort Statistics about the call. The first two digits indicate the type of
call:
1 indicates a digital call, 2 indicates an analog call. The
next two digits indicate the line on which the call was
received. The last two digits indicate the channel on which the
call was received.
authM Method of authentication.
evTime Event time. This is a timestamp.
Field Indicates