Cisco SCMS Subscriber Manager LEGs User Guide, Release 3.8.x

Installing the RADIUS Listener Login Event Generator

Introduction

This chapter describes the procedures for installing the software on the Cisco Service Control Subscriber Manager. It also describes uninstalling the software.

The RADIUS listener Login Event Generator (LEG) is part of the Cisco Service Control Subscriber Manager installation package. The installation package also includes configuration files and the Command-Line Utility (CLU) of the LEG.

•Installing the RADIUS Listener LEG Software

•Uninstalling the RADIUS Listener LEG

Installing the RADIUS Listener LEG Software

Step 1 Edit the RADUIS listener LEG configuration file.

To run the RADIUS listener LEG at SM startup, set the start parameter to yes. See Configuring the General Settings.

Step 2 Load the configuration file using the p3sm CLU.

Run the p3sm CLU from the sm-inst-dir/sm/server/bin folder (sm-inst-dir refers to the SM installation directory):

>p3sm --load-config

Step 3 Configure the NAS devices that are sending RADIUS accounting messages to the RADIUS listener LEG.

The Network Access System (NAS) devices may be RADIUS servers acting as RADIUS clients that proxy or forward RADIUS accounting messages to the RADIUS listener.

These RADIUS clients must be configured according to the RADIUS listener configuration, as performed in Step 1 above. There are many different RADIUS client devices, each of which is configured in a different manner. See Configuring the NAS Devices for instructions on configuring the RADIUS clients on NAS devices.

Uninstalling the RADIUS Listener LEG

Step 1 Edit the Cisco Service Control Subscriber Manager configuration file and set the RADIUS listener start parameter to no.

For further information, see Configuring the General Settings.

Note Setting the start parameter to no does not remove the RADIUS listener LEG from the Cisco Service Control Subscriber Manager installation. You can reinstall the software again by setting the start parameter to yes.

Step 2 Run the p3sm CLU.

>p3sm --load-config