Acct-Session-Id Options In A Management Session; Unique Acct-Session-Id Operation - HP 3500yl Series Access Security Manual

RADIUS Authentication, Authorization, and Accounting
Accounting Services
Note
6-54
requests from the switch, a second or third server will not be
accessed. (For more on this topic, refer to "Changing RADIUS-Server
Access Order" on page 6-72.)
If access to a RADIUS server fails during a session, but after the client
■
has been authenticated, the switch continues to assume the server is
available to receive accounting data. Thus, if server access fails during
a session, it will not receive accounting data transmitted from the
switch.

Acct-Session-ID Options in a Management Session

The switch can be configured to support either of the following options for
the accounting service types used in a management session. (Refer to
"Accounting Service Types" on page 6-52.)
■ unique Acct-Session-ID for each accounting service type used in the
same management session (the default)
■ same Acct-Session-ID for all accounting service types used in the
same management session

Unique Acct-Session-ID Operation

In the Unique mode (the default), the various service types running in a
management session operate as parallel, independent processes. Thus, during
a specific management session, a given service type has the same Acct-
Session-ID for all accounting actions for that service type. However, the Acct-
Session-ID for each service type differs from the ID for the other types.
In Unique Acct-Session-ID operation, the Command service type is a special
case in which the Acct-Session-ID for each executed CLI command in the
session is different from the IDs for other service types used in the session
and also different for each CLI command executed during the session. That
is, the ID for each successive CLI command in the session is sequentially
incremented from the ID value assigned to the immediately preceding CLI
command in that session.