HP-UX AAA Server A.08.02 Administrator's Guide

Table 85 Predefined Event Names (continued)
DescriptionEvent Name
Received accounting message has a Status-Type of Accounting-Off.ACCT_OFF
Received accounting message has a Status-Type of Accounting-On.ACCT_ON
Received accounting message has a Status-Type of Start.ACCT_START
Received accounting message has a Status-Type of Stop.ACCT_STOP
The incoming Accounting-Request is a message to start a session
through an established tunnel.
ACCT_TUNNEL_LINK_START
The incoming Accounting-Request is a message to end a session
through an established tunnel.
ACCT_TUNNEL_LINK_STOP
The incoming Accounting-Request indicates that a requested tunnel
could not be established.
ACCT_TUNNEL_REJECT
The incoming Accounting-Request is a message to establish a
tunnel.
ACCT_TUNNEL_START
The incoming Accounting-Request is a message to eliminate a
tunnel.
ACCT_TUNNEL_STOP
Acknowledgment of the previous action.ACK
The incoming Accounting-Request that the user has been denied
access to an established tunnel.
ACT_TUNNEL_LINK_REJECT
The incoming request is an Access-Request.AUTHEN
Received Access-Request has a Status-Type of Authenticate-Only.AUTH_ONLY
The incoming Access-Request is a continuation of an in-progress
EAP conversation. In general, you can allow the server to handle
CONTINUE
these events without any modification. This event is not pre-defined,
it must be defined in the FSM file.
The request is a CLIENT request.CLIENT_REQ
The request must be dropped without any further processing. This
event is not pre-defined, it must be defined in the FSM file with a
DROP
value that matches the value of DROP for the
Interlink-Reply-Status attribute defined in the
dictionary file.
The incoming Access-Request is a duplicate. Generally, you should
allow the server to handle these events without modification.
DUP
The previous action generated an error. Generally, you can allow
the server to handle these events without modification.
ERROR
The incoming Accounting-Request is an accounting-interim-update.
Generally, you can allow the server to handle these events without
LASCP
modification. This event is not pre-defined, it must be defined in
the FSM file.
Negative acknowledgment of the previous action.NAK
This event is returned by the REALM Action when a user's realm
cannot be found in the authfile.
NO_SUCH_REALM
This event is returned by the reply-egress policy. This event handles
post reply egress actions when OTP authentication is configured.
NOTE: The default policy file uses SQLAccess.
POST_REPLY_EGRESS
Event Names 293