33-35z The switch cannot communicate with the RADIUS server (you can determine by pinging theRADIUS server from the switch) — Take measures to make the switch communicate with theRADIUS server normally.Symptom 2: RADIUS packets cannot be sent to the RADIUS server.Possible reasons and solutions:z The communication links (physical/link layer) between the switch and the RADIUS server isdisconnected/blocked — Take measures to make the links connected/unblocked.z None or incorrect RADIUS server IP address is set on the switch — Be sure to set a correctRADIUS server IP address.z One or all AAA UDP port settings are incorrect — Be sure to set the same UDP port numbers asthose on the RADIUS server.Symptom 3: The user passes the authentication and gets authorized, but the accounting informationcannot be transmitted to the RADIUS server.Possible reasons and solutions:z The accounting port number is not properly set — Be sure to set a correct port number for RADIUSaccounting.z The switch requests that both the authentication/authorization server and the accounting serveruse the same device (with the same IP address), but in fact they are not resident on the samedevice — Be sure to configure the RADIUS servers on the switch according to the actual situation.Troubleshooting HWTACACS ConfigurationSee the previous section if you encounter an HWTACACS fault.
