Lucent Technologies Stinger, Administration Manual, Page: 343 / 374

Using Debug Commands
Interface debugging
Stinger® Administration Guide A-21
The following message indicates whether any RADIUS requests have been
dropped by the Stinger unit. With this particular message, no requests were
dropped and 1557 were sent successfully.
nSent[OK,fail]=[1557,0], nRcv=1557, nDrop[QFull,Other]=[0,0]
The following message indicates whether any session timeouts resulted from a
failure to receive RADIUS responses. The message also indicates responses that
are received by the Stinger unit but do not match any expected responses. The
Stinger unit keeps a list of sent requests, and expects a response for each request.
In the following message, one response was received from the RADIUS server
that did not match any of the requests that the Stinger had sent out. This
situation might be caused by a corrupted response packet, or by the Stinger unit
timing out the session before the response was received.
nRsp[TimOut,NoMatch]=[0,1], nBackoff[new,norsp]=[0,0]
The following messages display a summarized list of RADIUS server statistics.
Local Rad Serv Stats:
unkClient=0
index 0 #Sent = 0, #SendFail=0 badAuthRcv = 0, badPktRcv = 0
Interface debugging
The following sections describe the commands that you can use to debug Stinger
interfaces.
Displaying network interface mappings
The netif debug command displays the Stinger network interface mappings. This
command has the following syntax:
netif -m | -q | -v |?
The following example displays valid interface mappings:
admin> netif -v
map 0x1042C0E0: type 0 (call-id), id 0x1042B5A0
This example displays interface mappings that contain
type 0
:
admin> netif -m 0
SHELF SLOT SysID SlotID
1 1 52 2
1 6 90 58
1 6 89 57
1 6 86 56
1 6 78 51
1 6 72 50
Syntax element Description
-m
Displays mappings for the specified map type.
-q
Displays the queue for a map.
-v
Displays valid mapping tables.
?
Displays the command summary.