Types of Tracking Plug-Ins

You can configure the tracking plug-ins described in Table 8.

By default, the fileAcct plug-in instance tracks all subscriber and service sessions and writes all available attributes to a file. You can use this plug-in instance or create new one.

Note

The NAS-Port attribute is available only for JunosE routers that terminate L2TP tunnels (starting in JunosE Release 11.0).

Table 8: Tracking Plug-Ins

Plug-In	Description
Basic RADIUS accounting	Sends accounting information to an external RADIUS accounting server or a group of redundant servers. Java class name—net.juniper.smgt.sae.plugin.RadiusTrackingPluginEventListener
Custom RADIUS accounting	Provides customized functions that can also be found in the flexible RADIUS accounting plug-ins. Custom plug-ins are internal plug-ins that are designed to deliver better system performance than the flexible RADIUS plug-ins. You can extend this plug-in by using the RADIUS client library. Java class name—net.juniper.smgt.sae.plugin.CustomRadiusAccouting
Flat file accounting	Writes tracking information to a file in comma-separated format. Java class name—net.juniper.smgt.sae.plugin.FileTrackingPluginEventListener
Flexible RADIUS accounting	Performs the same functions as the basic RADIUS accounting plug-in, but also lets you customize RADIUS accounting packets that the SAE sends to RADIUS servers. You can specify which fields are included in RADIUS accounting packets and what information is contained in the fields. Java class name—net.juniper.smgt.sae.plugin.FlexibleRadiusTrackingPluginEventListener
PCMM record-keeping server plug-in	Sends accounting information to an external PCMM record-keeping server (RKS). See Configuring PCMM Record-Keeping Server Plug-Ins (SRC CLI). Java class name—net.juniper.smgt.sae.plugin.RksEventListener
QoS profile tracking	Ensures that as a subscriber activates and deactivates services, the correct QoS profile is attached to the subscriber interface. See Dynamically Managing QoS Profiles. Java class name—net.juniper.smgt.sae.plugin.qtp.QosProfileTrackingPluginEventListener

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. The SRC software provides RADIUS accounting that conforms to RFC 2866—RADIUS Accounting (June 2000).

Both the JunosE router and the service activation engine (SAE) send accounting information to the RADIUS accounting server. The JunosE router includes accounting information for all Broadband Remote Access Service (B-RAS) sessions. The SAE sends the RADIUS attributes listed in Table 9 to the RADIUS accounting server. These attributes are used for logging SRC subscriber sessions and service sessions. Table 10 contains a detailed description of the NAS-Port-Id attribute of the JunosE router for various interface types.

Table 9: RADIUS Accounting Attributes

RADIUS Accounting Attribute	Notes
User-Id	This attribute value can be login-name, accounting-id, auth-user-name, or manager-id.
Terminate-Cause	Based on the SRC scenario, map this attribute to one of the following values: User-Request—If the subscriber or user session has logged out Lost-Carrier—If the interface (Dynamic Host Configuration Protocol or Point-to-Point Protocol) has logged out Lost-Service—If the service deactivation of a fragment in aggregate services failed (the fragment could not be started during failover or while handling a change notification) Idle-Timeout—If the service session is inactive or has timed out Session-Timeout—If the user session has timed out or the subscription has expired Admin-Reset—Map the Terminate-Cause attribute to this value for any of the following scenarios: If an interface update request is reported in the Common Open Policy Service (COPS) In the case of the Diameter server, if the user session is to be discarded In the case of infrastructure services, if an orphan shared session is removed If a change of interface address led to the termination of a session in the SRC software NAS-Error—If the session data cannot be stored. This could occur if the session store file could not be written with session contents (disk full or session store corrupted). NAS-Request—If you are unable to recover user or service sessions during synchronization Port-Unneeded—If the infrastructure service session is terminated Service-Unavailable—When a user tries to access a service for which there are no subscriptions available in the user profile
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	Identifier of user and service sessions The Acct-Session-Id is included in all accounting and authorization events for the same session and can be used to correlate the events.
Multi-Session-Id	For PPP subscriber sessions, the session ID assigned by the JunosE router
NAS-Port-Id	SRC software takes the NAS-Port-Id attribute from the JunosE router through COPS and prepends: <virtual-router-name>@<router-name> <NAS-Port-Id-from-router> This attribute contains the full router name, space character, and the NAS-Port-Id attribute as received from the JunosE router for this interface. For example: default@eseries1 FastEthernet 3/0 See Table 10 for a detailed description of the NAS-Port-Id attribute for various interface types.
NAS-Identifier	Identifier 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.
Ipv6-Acct-Input-Octets	Used in IPv6 Interim and Stop requests, but for service sessions only. Provided only for services with accounting policy rules.
Ipv6-Acct-Output-Octets	Used in IPv6 Interim and Stop requests, but for service sessions only. Provided only for services with accounting policy rules.
Ipv6-Acct-Input-Gigawords	Used in IPv6 Interim and Stop requests, but for service sessions only. Provided only for services with accounting policy rules.
Ipv6-Acct-Output-Gigawords	Used in IPv6 Interim and Stop requests, but for service sessions only. Provided only for services with accounting policy rules.
Ipv6-Acct-Input-Packets	Used in IPv6 Interim and Stop requests, but for service sessions only. Provided only for services with accounting policy rules.
Ipv6-Acct-Output-Packets	Used in IPv6 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	Values are: 1 [Start], 2 [Stop], 3 [Interim-Update], 7 [Accounting-On], or 8 [Accounting-Off] The RADIUS server you are using may present this value differently.
Acct-Delay-Time	Number of seconds since first try to send data

Note

The SAE 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 retrieves volume data from the router and sends the data in the Stop request. Note that errors in communication with the router (for example, broken connection) may prevent the SAE from retrieving the volume data. If such an error happens, the SAE 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 10: Description of NAS-Port-Id Attribute for Various Interface Types

Interface Type	Interface Format	Example
ATM 1483	router atm <slot>/<port>.<subinterface> :<vpi>.<vci>	host1 atm 0/1.20 22 10
FastEthernet	router fastEthernet <slot>/<port>[.<subinterface> [<vlan>[<sub-vlan>]]]	host1 fastEth 3/2.6.20
GigabitEthernet	router gigabitEthernet <slot>/<port>[.<subinterface> [<vlan>[<sub-vlan>]]]	host1 gigabitEth 3/2.6.20
Serial	router 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	router gre:<tunnel-name>	host1 tunnel gre:boston
DVMRP	router dvmrp:<tunnel-name>	host1 tunnel dvmrp:chicago