Log Messages
594
ProSAFE M7100 Managed Switches
RADIUS RADIUS: Could not allocate accounting
requestInfo
Resource issue with RADIUS Client service.
RADIUS RADIUS: Could not allocate requestInfo Resource issue with RADIUS Client service.
RADIUS RADIUS: osapiSocketRecvFrom returned
er
r
or
Error while attempting to read data from the
RADIUS server.
RADIUS RADIUS: Accounting-Response failed to
validat
e, id=xxx
The RADIUS Client received an invalid
message from the server.
RADIUS RADIUS: User (xxx) needs to respond for
challenge
An unexpected challenge was received for a
configur
ed user.
RADIUS RADIUS: Could not allocate a buffer for the
packe
t
Resource issue with RADIUS Client service.
RADIUS RADIUS: Access-Challenge failed to validate,
id=xx
x
The RADIUS Client received an invalid
message from the server.
RADIUS RADIUS: Failed to validate
Mes
sage-Authenticator, id=xxx
The RADIUS Client received an invalid
message from the server.
RADIUS RADIUS: Access-Accpet failed to validate, id=
xxx
The RADIUS Client received an invalid
message fr
om the server.
RADIUS RADIUS: Invalid packet length – xxx The RADIUS Client received an invalid
message fr
om the server.
RADIUS RADIUS: Response is missing
Mes
sage-Authenticator, id=xxx
The RADIUS Client received an invalid
message from the server.
RADIUS RADIUS: Server address does not match
configur
ed server
RADIUS Client received a server response
from an unconfigured server.
Table 16. TACACS+ Log Messages
Component Message Cause
TACACS+ TACACS+: authentication error, no server to
cont
act
TACACS+ request needed, but no servers are
configured.
TACACS+ TACACS+: connection failed to server x.x.x.x TACACS+ request sent to server x.x.x.x but
no response w
as received.
TACACS+ TACACS+: no key configured to encrypt
packe
t for server x.x.x.x
No key configured for the specified server.
TACACS+ TACACS+: received invalid packet type from
serv
er.
Received packet type that is not supported.
Table 15. RADIUS Log Messages (continued)
Component Message Cause
To Next Page
Loading...
