Accounting services

RADIUS accounting collects data about user activity and system events and sends it to a RADIUS server when specified events occur on the switch, such as a logoff or a reboot.

Accounting service types

The switch supports four types of accounting services:

Network accounting: Provides records containing the information listed below on clients directly connected to the switch and operating under Port-Based Access Control (802.1X):

Acct-Session-Id
Acct-Status-Type
Acct-Terminate-Cause
Acct-Authentic
Acct-Delay-Time
Acct-Input-Packets

Acct-Output-Packets
Acct-Input-Octets
Nas-Port
Acct-Output-Octets
Acct-Session-Time
User-Name

Service-Type
NAS-IP-Address
NAS-Identifier
Calling-Station-Id
HP-acct-terminate-cause
MS-RAS-Vendor

Exec accounting: Provides records holding the information listed below about login sessions (console, Telnet, and SSH) on the switch:

Acct-Session-Id
Acct-Status-Type
Acct-Terminate-Cause
Acct-Authentic

Acct-Delay-Time
Acct-Session-Time
User-Name
Service-Type

NAS-IP-Address
NAS-Identifier
Calling-Station-Id
MS-RAS-Vendor

System accounting: Provides records containing the information listed below when system events occur on the switch, including system reset, system boot, and enabling or disabling of system accounting.

Acct-Session-Id
Acct-Status-Type
Acct-Terminate-Cause
Acct-Authentic

Acct-Delay-Time
Username
Service-Type
NAS-IP-Address

NAS-Identifier
Calling-Station-Id
Acct-Session-Time
MS-RAS-Vendor

Commands accounting: Provides records containing information on CLI command execution during user sessions.

Acct-Session-Id
Acct-Status-Type
Service-Type
Acct-Authentic

User-Name
NAS-IP-Address
NAS-Identifier
NAS-Port-Type

Calling-Station-Id
HP-Command-String
Acct-Delay-Time

The switch forwards the accounting information it collects to the designated RADIUS server, where the information is formatted, stored, and managed by the server. For more information on this aspect of RADIUS accounting, see the documentation provided with your RADIUS server.

Operating rules for RADIUS accounting

You can configure up to four types of accounting to run simultaneously: exec, system, network, and command.
RADIUS servers used for accounting are also used for authentication.
The switch must be configured to access at least one RADIUS server.
RADIUS servers are accessed in the order in which their IP addresses were configured in the switch. Use show radius to view the order. As long as the first server is accessible and responding to authentication requests from the switch, a second or third server will not be accessed. For more on this topic, see Changing RADIUS-server access order.
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.

Configuring RADIUS accounting


	NOTE: This procedure assumes: RADIUS authentication is configured on the switch for one or more access methods One or more RADIUS servers is configured to support the switch

Steps for configuring RADIUS accounting

Configure the switch for accessing a RADIUS server.

You can configure up to three RADIUS servers (one primary, two backup). The switch operates on the assumption that a server can operate in both accounting and authentication mode. See the documentation for your RADIUS server application for additional information.
- Use the same radius-server host command that you would use to configure RADIUS authentication. See Configuring a switch to access a RADIUS server.
- Provide the following:
  - A RADIUS server IP address.
  - Optional — UDP destination port for authentication requests. Otherwise the switch assigns the default UDP port (1812; recommended).
  - Optional — if you are also configuring the switch for RADIUS authentication, and need a unique encryption key for use during authentication sessions with the RADIUS server you are designating, configure a server-specific key. This key overrides the global encryption key you can also configure on the switch, and must match the encryption key used on the specified RADIUS server. For more information, see the key <key-string> parameter in Configuring a switch to access a RADIUS server. Default: null
Configure accounting types and the controls for sending reports to the RADIUS server.
- Accounting types:
  - exec
  - network
  - system
  - commands
- Trigger for sending accounting reports to a RADIUS server: At session start and stop or only at session stop.
(Optional) Configure session blocking and interim updating options
- Updating: Periodically update the accounting data for sessions-in-progress.
- Suppress accounting: Block the accounting session for any unknown user with no username trying to access to the switch.

Configuring a switch to access a RADIUS server

Before you configure the actual accounting parameters, configure the switch to use a RADIUS server. This process is outlined in Configuring the switch to access a RADIUS server. Repeat this now only if one of the following applies:

The switch is not yet configured to use a RADIUS server
Your server data has changed
You need to specify a non-default UDP destination port for accounting requests


	NOTE: Switch operation expects a RADIUS server to accommodate both authentication and accounting.

Syntax:

[no] radius-server host <ip-address>

Adds a server to the RADIUS configuration or (with no) deletes a server from the configuration.

[acct-port <port-number>]

Optional. Changes the UDP destination port for accounting requests to the specified RADIUS server. If you do not use this option, the switch automatically assigns the default accounting port number. (Default: 1813)

[key <key-string>]

Optional. Specifies an encryption key for use during accounting or authentication sessions with the specified server. This key must match the encryption key used on the RADIUS server. Use this command only if the specified server requires a different encryption key than configured for the global encryption key.

NOTE: If you save the config file using Xmodem or TFTP, the key information is not saved in the file. This causes RADIUS authentication to fail when the config file is loaded back onto the switch.

Example:

Suppose you want the switch to use the RADIUS server described below for both authentication and accounting purposes.

IP address: 10.33.18.151
A non-default UDP port number of 1750 for accounting.

For this example, assume that all other RADIUS authentication parameters for accessing this server are acceptable at their default settings, and RADIUS is already configured as an authentication method for one or more types of access to the switch (Telnet, Console, etc.).

Because the radius-server command includes an acct-port keyword with a non-default UDP port number of 1750, the switch assigns this value as the UDP accounting port.

Configuring for a RADIUS server with a non-default accounting UDP port number

HP Switch(config)# radius-server host 10.33.18.151 
 acct-port 1750 key source0151
HP Switch(config)# write mem

HP Switch(config)# show radius

 Status and Counters - General RADIUS Information

  Deadtime(min) : 0
  Timeout(secs) : 5
  Retransmit Attempts : 3
  Global Encryption Key :
  Dynamic Authorization UDP Port : 3799

                  Auth Acct DM/ Time
  Server IP Addr  Port Port CoA Window Encryption Key
  --------------- ---- ---- --- ------ -------------------
  10.33.18.151    1812 1750 No  10     source0151

The radius-server command as shown in Configuring for a RADIUS server with a non-default accounting UDP port number above, configures the switch to use a RADIUS server at IP address 10.33.18.151, with a non-default UDP accounting port of 1750, and a server-specific key of "source0151".

Configure accounting types and controls for sending reports to the RADIUS server

Accounting service types to track

Configure one or more accounting service types to track:

Exec: Use exec if you want to collect accounting information on login sessions on the switch via the console, Telnet, or SSH. See Accounting services.

System: Use system if you want to collect accounting data when:

A system boot or reload occurs
System accounting is turned on or off


	NOTE: There is no time span associated with using the `system` option. It simply causes the switch to transmit whatever accounting data it currently has when one of the above events occurs.

Network: Use network if you want to collect accounting information on 802.1X port-based-access to the network by users connected to the physical ports on the switch. See Accounting services.
Commands: When commands accounting is enabled, an accounting notice record is sent after the execution of each command.

Accounting controls

These options are enabled separately, and define how the switch will send accounting data to a RADIUS server:

Start-Stop: Applies to the exec, network, and system accounting service types:
- Send a "start record accounting" notice at the beginning of the accounting session and a "stop record notice" at the end of the session. Both notices include the latest data the switch has collected for the requested accounting type.
- Do not wait for an acknowledgement.
Stop-Only: Applies to the network, exec, system, and command service types, as described below:
- Send a stop record accounting notice at the end of the accounting session. The notice includes the latest data the switch has collected for the requested accounting type (network, exec, or system service types). For the commandsservice type, sends the "Stop" accounting notice after execution of each CLI command.
- Do not wait for an acknowledgment.
  
  The system option always delivers stop-only operation because the switch sends the accumulated data only when there is a reboot, reload, or accounting on/off event.

Syntax:

[no] aaa accounting <exec|network|system|commands> <start-stop|stop-only> radius

Configures RADIUS accounting service type and how data will be sent to the RADIUS server.

<exec|network|system|command>

Specifies an accounting service type to configure. See Accounting service types.

start-stop: Applies to exec, network, and system accounting service types.

stop-only: Applies to all accounting service types.

Example:

For example, to configure RADIUS accounting on the switch with start-stop for exec functions and stop-only for system functions:

Example of configuring accounting types

Configuring session blocking and interim updating options (optional)

These optional parameters give you additional control over accounting data.

Updates: In addition to using a Start-Stop or Stop-Only trigger, you can optionally configure the switch to send periodic accounting record updates to a RADIUS server.
Suppress: The switch can suppress accounting for an unknown user having no user name.

Syntax:

[no] aaa accounting update periodic <1-525600>

Sets the accounting update period for all accounting sessions on the switch.

The no form disables the update function and resets the value to zero.

Default: zero; disabled

Syntax:

[no] aaa accounting suppress null-username

Disables accounting for unknown users having no username.

Default: suppression disabled

To continue the example in Example of configuring accounting types, suppose you want the switch to:

Send updates every 10 minutes on in-progress accounting sessions.
Block accounting for unknown users (no username).

Example of optional accounting update period and accounting suppression on unknown user

prev	up	next
MAC-based VLANs	home	Viewing RADIUS statistics


	NOTE: If you save the config file using Xmodem or TFTP, the key information is not saved in the file. This causes RADIUS authentication to fail when the config file is loaded back onto the switch.