[Contents] [Prev] [Next] [Index] [Report an Error]


RADIUS Accounting

RADIUS accounting is used to send accounting information to the RADIUS accounting server. Accounting information is sent to the server whenever a subscriber logs in or logs out and whenever a subscriber activates or deactivates a subscription.

Both the E-series router and the SAE software send accounting information to the RADIUS accounting server. The E-series router includes accounting information for all Broadband Remote Access Service (B-RAS) sessions. The SAE software sends the RADIUS attributes listed in Table A-1 to the RADIUS accounting server. These attributes are used for logging subscriber sessions with activated SAE services. Table A-2 contains a detailed description of the NAS-Port-Id attribute of the ERX for various interface types.

Table A-1 RADIUS accounting attributes 
RADIUS Accounting Attribute
Notes
User-Id
The values are:
  • login-name
  • accounting-id
  • auth-user-name
  • manager-id
Juniper Networks provides flexible RADIUS plug-ins; that is, you can freely define which attributes are used and which values are provided. See SDX-300 Administration Guide.
Terminate-Cause
User-Request, Lost-Carrier (PPP hangup), Idle-Timeout, Session-Timeout, Admin-Reset
Lost-Carrier is used when the transport interface goes down or when a DHCP lease expires.
User-Request is sent only when the session was terminated through an API call (deactivate session or user logout, but not a PPP logout). This includes scheduled deactivation.
Admin-Reset is sent when a service session is terminated because of updates of the directory data (for example, when a service definition has changed).
Framed-Ip-Address
User IP address
Event-Time
Number of seconds since Jan-1, 1970 00:00 UTC
The RADIUS server you are using may present this value differently.
Class
From service definition
Acct-Session-Id
There are two formats, one for subscriber sessions and one for service sessions.
  • Subscriber session:
<User-Id>:<timestamp>
  • Service session:
<service-name>:<User-Id>:<timestamp>
Multi-Session-Id
For PPP subscriber sessions, the session ID assigned by the E-series router.
NAS-Port-ID
SDX software takes the NAS-Port-ID attribute from the E-series router via COPS and prepends:
<virtualroutername>@<routername> _<NAS-Port-Id-from-ERX>
This attribute contains the full router name, space character, and the NAS-Port-Id attribute as received from the ERX for this interface. Example:
default@erx123 FastEthernet 3/0


Note: See Table A-2 for a detailed description of the NAS-Port-Id attribute for various interfaces types.

NAS-Identifier
Identification of SAE server
Acct-Input-Octets
  • Used in Interim and Stop requests, but for service sessions only.
  • Provided only for services with accounting policy rules.
Acct-Output-Octets
  • Used in Interim and Stop requests, but for service sessions only.
  • Provided only for services with accounting policy rules.
Acct-Input-Gigawords
  • Used in Interim and Stop requests, but for service sessions only.
  • Provided only for services with accounting policy rules.
Acct-Output-Gigawords
  • Used in Interim and Stop requests, but for service sessions only.
  • Provided only for services with accounting policy rules.
Acct-Input-Packets
  • Used in Interim and Stop requests, but for service sessions only.
  • Provided only for services with accounting policy rules.
Acct-Output-Packets
  • Used in Interim and Stop requests, but for service sessions only.
  • Provided only for services with accounting policy rules.
Acct-Session-Time
Used only in Stop requests; time specified in seconds.
Acct-Status-Type
1 [Start], 2 [Stop], 3 [Interim-Update], 7 [Accounting-On], or 8 [Accounting-Off]
The RADIUS server you are using may present these values differently.
Acct-Delay-Time
Number of seconds since first try to send data



Note: The SAE software sends a RADIUS Stop request for every service session that has been stopped. If the policies associated with the service define accounting rules, the SAE software retrieves volume data from the router and sends the data in the Stop request. Note that errors in communication with the router (e.g., broken connection) may prevent the SAE software from retrieving the volume data. If such an error happens, the SAE software will send a Stop record where the volume counters are set to zero. If an interim update for the same service session exists, which includes nonzero volume counters, we recommend that you use this interim update instead of the final accounting.

Table A-2 Description of NAS-Port-Id attribute for various interface types
Interface Type
Interface Format
Example
ATM 1483
erx atm <slot>/<port>.<subinterface>:<vpi>.<vci>        
host1 atm 0/1.20 22 10
FastEthernet
erx fastEthernet<slot>/<port>[.<subinterface>[ <vlan>[sub-vlan>]]]    
host1 fastEth 3/2.6.20
GigibitEthernet
erx gigabitEthernet<slot>/<port>[.<subinterface>[<vlan>[sub-vlan>]]]
host1 gigabitEth 3/2.6.20
Serial
erx serial <slot>/<port>[:<sonetPath>[/<sonetTributary(x/x/x)> [/<fractionalInterface>]]]
host1 path 2 ds1 1/7/4 channel-group 1 timeslots 1-5
LNS
ip:local  ip:peer  ip:local  tid:peer  tid:local  sid:peer  sid:call  serial number
GRE
erx gre<tunnel-name>
host1 tunnel gre:boston
DVMRP
erx dvmrp<tunnel-name>        
host1 tunnel dmvrp:chicago        

The SDX application provides RADIUS accounting that conforms to RFC 2866. SDX software Release 4.1.x supports three RADIUS packages: Merit AAA Server 4.22E, Steel-Belted Radius Service Provider Edition (SPE) Release 4.0 from Funk Software, and RAD-Series RADIUS Server version 6.0 from Interlink Networks. The format of the generated accounting log file differs in these RADIUS packages. The accounting log file formats are described in the appropriate chapters in this guide.


[Contents] [Prev] [Next] [Index] [Report an Error]