Troubleshooting Radius; Radius Switch Side Troubleshooting - Avaya 8800 Troubleshooting Manual

7. Display the ingress packet trace:

Troubleshooting RADIUS

The following sections provide information for troubleshooting RADIUS issues.

RADIUS switch side troubleshooting

To troubleshoot RADIUS issues on the Ethernet Routing Switch 8800/8600, use the following
procedure.
1. Make sure the RADIUS server is reachable from the NAS (or 8800/8600 switch).
2. Make sure authentication and accounting are enabled globally in the address
3. Make sure the server entry exists for the user. The switch can have the same server
Troubleshooting
-------------------------------------------------------------------------
------- 11 1 (7) 33:33:00:00:00:05 00:04:38:6e:c2:01 N/A N/A0 141 (7)
33:33:00:00:00:05 00:04:38:6e:c2:01 N/AN/A0
dump rsp-trace ingress-display-pktport 3/17 pkt-id 11 (CLI)
OR
dump rsp-trace ingress-display-pkt 3/17 11 (ACLI)
Copy packet to Primary CPU. CPU Code=0x0 CPU Code Extension=0x0 Packet
PreclassificationInformation: PC Vector1: IPv6. PC Vector2: Control
packet. Layer2 Type: Ethernet with q-tag. MAC Type: Unicast(else). Layer3
Type: IPv6. Layer4 Type: ICMP. Ether Protocol Id Offset = 16 bytes from
the begin of packet. Ingress Packet Trace: Vlan Rec:0x11600140000a001f
Incoming Packet: 33330000 00050004 386ec201 8100e014 86dd6000 00000030
5901fe80 00000000 00000000 00000000 0003ff02 00000000
Highlighted above are the source and part of the destination IPv6 address in the
packet.
configuration:
radius enable radius server create <ipv4|ipv6> secret
<string> enable <true> acct-enable <true> (CLI)
radius
radius server host <WORD 0-46> key <WORD 0-32> used-by {cli|
igap|snmp|eapol} acct-enable acct-port <1-65536> enable port
<1-65536> priority <1-10> retry <0-6> source-ip <A.B.C.D>
timeout <1-60> (ACLI Global Configuration mode)
address under different user groups (for example, cli, igap, snmp, or eapol).
Troubleshooting RADIUS
July 2013 451