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


Configuring Tracking Plug-Ins

This section shows how to configure the tracking plug-ins described in Table 16.

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: When you use the NAS-Port attribute in tracking plug-ins, the SAE calculates the NAS-Port value based on the NAS-Port-Id value that it receives from the JUNOSe router. You can change the NAS-Port format in the JUNOSe software. However, because the SAE has no indication of which format is configured on the JUNOSe router, the calculation of the NAS-Port attribute is correct only if the router uses the default configuration.





Table 16: 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 in SRC-PE Solutions Guide, Chapter 6, Configuring the SAE for a PCMM Environment with SDX Configuration Editor.

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 SRC-PE Solutions Guide, Chapter 1, Managing Tiered and Premium Services with QoS on JUNOSe Routers.

Java class name—net.juniper.smgt.sae.plugin.qtp.QosProfileTrackingPluginEventListener

The overall steps to configure a tracking plug-in are:

  1. Create and configure a plug-in instance in the plug-in pool. The following sections show how to create and configure an instance for each type of tracking plug-in.
  2. Configure an event publisher to publish events to the plug-in instance.

See Configuring Event Publishers.

Configuring Flat File Accounting Plug-Ins

Flat file accounting plug-ins write information to a file in a comma-separated format. The SRC software has a default flat file accounting plug-in instance called fileAcct. The fileAcct instance logs all possible attributes for 24-hour periods in the file var/acct/log. You can modify the fileAcct instance, use it as is, or create a new instance.

Another item that you can configure for flat files is the names of the headers that appear in the file. See Configuring Headers for Flat File Accounting Plug-Ins.

To create flat-file accounting plug-in instances:

  1. In the Plug-In Pool area of the Plug-Ins pane, create a flat file accounting instance as described in Creating Plug-In Instances.

The instance appears in the Plug-In Pool area.

  1. Fill in the fields for the plug-in instance as described below.

Filename

Template

Interval [hour]

Fields

Configuring Headers for Flat File Accounting Plug-Ins

When the SAE writes data to a flat file, it writes into the first line the headers that identify the attributes in the file. For example, in the following accounting file, the first line lists headers for all attribute fields in the file, and the following lines list the actual data in each field:

Accounting Status,NAS ID,SSP Host,Router Name,Interface Name,Interface
Alias,Interface Description,NAS port ID,User IP Address,User ID,User Accounting
ID,User Authentication ID,INTF Radius Class,INTF,SessionId, Service Name,Radius
Class,Timestamp,SessionId, Terminate Cause,Session Time,Input Octets,Output
Octets,Input Packets,Output Packets,NAS IP,User Mac address,Service Session
Name,Service Session Tag,User Session Type,User Session Radius Class,User
Session ID

start,SSP.uelmo,uelmo,default@erx7_ssp57,FastEthernet1/1.1,,IP1/1.1,default@erx7
_ssp57 FastEthernet1/1:65535, 10.10.10.20,pebbles@virneo.net,,,,erx fastEthernet
1/1:0001048619,Video-Gold,Video-Gold,Fri Jan 30 14:23:29 EDT 2004,
VideoGold:null:1064946209182, 0,0,0,0,0,0, 10.10.7.17,,,,PPP,,
pebbles:1064946144841

You can assign your own names to the headers that appear in the file. To do so, you define the header names in a template and then set up file accounting plug-in instances to use the template. The default template, FileAccounting.std, defines header names for all possible attributes. You can use the default template or create your own templates.

To set up a file accounting template:

  1. In the File-Acct Template tab, create a File Accounting Attributes instance as described in Creating Plug-In Instances.

The new instance appears.

  1. Define header names in the attribute table in the format property=value, where property is the attribute name and value is the header name that you want to assign to the attribute. Configure the attribute table as follows:

Configuring Basic RADIUS Accounting Plug-Ins

You can use basic RADIUS accounting plug-ins to send accounting information to an external RADIUS accounting server or to a group of redundant servers. To communicate with nonredundant servers, you need to create multiple instances of the plug-in.

To set up basic RADIUS accounting plug-ins:

  1. In the Plug-In Pool area of the Plug-Ins pane, create a basic RADIUS accounting plug-in instance as described in Creating Plug-In Instances.

The instance appears in the Plug-In Pool area.

  1. Fill in the fields for the plug-in instance as described in Using RADIUS Plug-In Fields.
  2. In the Peer Group area, create at least one RADIUS peer to use as the default peer. See Creating RADIUS Peers.

Configuring Flexible RADIUS Accounting Plug-Ins

Flexible RADIUS accounting plug-ins provide the same features as basic RADIUS accounting plug-ins. In addition, they allow you to customize RADIUS accounting packets that the SAE sends to RADIUS servers. You can specify which fields are included in the RADIUS accounting packets and what information is contained in the fields.

You can also extend custom RADIUS plug-ins to perform the same functions as the flexible RADIUS plug-ins. These custom plug-ins are also internal plug-ins, but are designed to deliver better system performance. See Configuring Custom RADIUS Accounting-Plug-Ins.

To set up flexible RADIUS accounting plug-ins:

  1. In the Plug-In Pool area of the Plug-Ins pane, create a flexible RADIUS accounting plug-in instance as described in Creating Plug-In Instances.

The instance appears in the Plug-In Pool area.

  1. Fill in the fields for the plug-in instance as described in Using RADIUS Plug-In Fields.
  2. In the Peer Group area, create at least one peer to use as the default peer. See Creating RADIUS Peers.
  3. (Optional) Assign a RADIUS packet template to the instance, or create a packet definition for the instance. See Defining RADIUS Packets for Flexible RADIUS Plug-Ins with SDX Configuration Editor.

Configuring Custom RADIUS Accounting-Plug-Ins

The custom RADIUS accounting plug-ins provide the same functions as the flexible RADIUS accounting plug-ins, but are designed to deliver better system performance. To use a custom plug-in, you must provide a Java class that implements the SPI defined in the RADIUS client library. Use this SPI to specify which fields and field values to include in RADIUS accounting packets. The RADIUS client library is part of the SAE core API.

See the documentation for the RADIUS client library in the SRC software distribution in the folder SDK/doc/sae/net/juniper/smgt/sae/radiuslib or in the SAE Core API documentation on the Juniper Networks Web site at

http://www.juniper.net/techpubs/software/management/sdx/api-index.html

For a sample implementation, see the following directory in the SRC software distribution: SDK/plugin/java/src/net/juniper/smgt/sample/radiuslib/RadiusPacketHandlerImpl.java.

To set up custom RADIUS accounting plug-ins:

  1. In the Plug-In Pool area of the Plug-Ins pane, create a custom RADIUS accounting plug-in instance as described in Creating Plug-In Instances.

The instance appears in the Plug-In Pool area.

  1. Fill in the plug-in instance fields as described in Using RADIUS Plug-In Fields.
  2. In the Peer Group area, create at least one peer to use as the default peer. See Creating RADIUS Peers.

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