15 RADIUS Manager Utilities

This chapter provides reference information for Oracle Communications Billing and Revenue Management (BRM) RADIUS Manager utilities.

pin_ipass_loader

Use the pin_ipass_loader utility to load the iPass call detail records (CDRs) into the BRM database.

For more information, see "Using the pin_ipass_loader Utility for Batch Accounting" and "Setting Up iPass Roaming".

Important:

To connect to the BRM database, the pin_ipass_loader utility needs a configuration file in the directory from which you run the utility. See "Creating Configuration Files for BRM Utilities" in BRM System Administrator's Guide.

Location

BRM_home/bin

Syntax

pin_ipass_loader -f input_file -s session_length_rate                  [-c cost_rate] -u qualified | unqualified
                 -p problem_file [-m] monthly_charge_rate -t [-h][-v]

Parameters

-f input_file

Specifies the name of the CDR file. The default is stdin. See "iPass Call Detail Record File Definition".

-s session_length_rate

Specifies the rate based on session length. The default is ip/dialup/async/hourly.

-c cost_rate

Rate based on session cost rating.

-u qualified | unqualified

Includes or excludes the domain in user name searches. The default is unqualified.

-p problem_file

Specifies the name of problem file. The default is pin_ipass_loader.problem.yyyymmddhhmm. The file is placed by default in BRM_home/.

-m monthly_charge_rate

(Optional) Rate based on monthly iPass charges.

-t

Specifies test mode, which parses the file and runs consistency checks without modifying the database.

-v

Displays information about successful or failed processing as the utility runs.

-h

Displays the syntax and parameters for this utility.

Results

If the utility doesn't notify you that it was successful, look in the default.pinlog file to find any errors. This file is either in the directory from which the utility was started or in a directory specified in the utility configuration file.

pin_radiusd_sig

Use the pin_radiusd_sig utility to initiate dynamic reconfiguration of the RADIUS server, extract information about the RADIUS server, and stop the RADIUS server.

For more information, see "Reconfiguring Your RADIUS Server without Stopping Operation".

Important:

To connect to the Oracle Communications Billing and Revenue Management (BRM) database, the pin_radiusd_sig utility needs a configuration file in the directory from which you run the utility. See "Creating Configuration Files for BRM Utilities" in BRM System Administrator's Guide.

Location

BRM_home/bin

Syntax

pin_radiusd_sig HUP|USR1|INT host_name port secret

Parameters

HUP

Initiates dynamic reconfiguration. This parameter causes the server to reload the pin_radiusd config file containing the changes that you want to deploy.

USR1

Logs status information about the RADIUS server to the radius.pinlog log file, /var/portal/7.5/radius/radius.pinlog.

INT

Shuts down the RADIUS server.

host_name

Specifies the name of the RADIUS server host computer.

port

Specifies the port number that the server listens to for requests.

secret

Specifies the secret shared between the client NAS (network access server) and RADIUS Manager.

Results

If the utility doesn't notify you that it was successful, look in the default.pinlog file to find any errors. This file is either in the directory from which the utility was started or in a directory specified in the utility configuration file.

pin_term_acct

Use the pin_term_acct utility to simulate receiving Accounting-On or Accounting-Off requests from a terminal server by manually calling the PCM_OP_IP_DIALUP_ACCOUNTING_ON and PCM_OP_IP_DIALUP_ACCOUNTING_OFF opcodes from RADIUS Manager. You can also use pin_term_acct to monitor all opened sessions based on TERMSERV_ID.

For more information, see "About the Account Request Utility".

Note:

To connect to the Oracle Communications Billing and Revenue Management (BRM) database, the pin_term_acct utility needs a configuration file in the directory from which you run the utility. See "Creating Configuration Files for BRM Utilities" in BRM System Administrator's Guide.

Location

BRM_home/bin

The configuration file for this utility is located in BRM_home/apps/pinapps/pin_term_acct/pin.conf.

Syntax

pin_term_acct -m list|on|off -n termserv_id -v verbose -d days 
              -t hh:mm:ss -c charge mode [-h] help

Parameters

-m list|on|off

Sets the mode of operation.

  • list mode (default) displays a list of all open sessions.

  • on sends an Accounting-On request.

  • off sends an Accounting-Off request.

You use these parameters to simulate end-of-cycle usage. See "Listing All Open Sessions" for the output format.

-n termserv_id

Specifies the terminal server ID. This parameter is optional in list mode. If not specified in list mode, the default is all terminal servers.

-v

Displays information about successful or failed processing as the utility runs.

-d days

Specifies the date that an Accounting-On/Accounting-Off event occurs. The default is today's date.

-t hh:mm:ss

Specifies the time that an Accounting-On/Accounting-Off event occurs. The default is the current time. Hours are in 24-hour format.

-c NC|C

Specifies the charge mode.

  • NC (the default) does not charge sessions that were closed in off mode.

  • C charges sessions that were closed in off mode.

This parameter has no effect in list and on modes.

-h

Displays the syntax and parameters for this utility.

Results

If the utility doesn't notify you that it was successful, look in the default.pinlog file to find any errors. This file is either in the directory from which the utility was started or in a directory specified in the utility configuration file.

rad_tester

Use the rad_tester utility to send RADIUS packets to the RADIUS server to replicate a terminal server.

For more information, see "Testing a RADIUS Configuration".

Important:

To connect to the Oracle Communications Billing and Revenue Management (BRM) database, the rad_tester utility needs a configuration file in the directory from which you run the utility. See "Creating Configuration Files for BRM Utilities" in BRM System Administrator's Guide.

Location

BRM_home/bin

Syntax

rad_tester -h host_name -p port_number -a port_number -s secret 
           -f input_file [-r] input_file [-O] sss-d dictionary_file_name 
           [-D] [-v]

Parameters

Note:

These parameters are case sensitive.
-h host_name

Host name of the RADIUS server. The default is the local host name.

-p port_number

Authorization port.

-a port_number

Accounting port.

-s secret

Shared RADIUS secret. The default is testing123.

-f input_file

Input file name. The default is stdin.

-r input_file

Number of times to re-send a request when the request times-out. The default is 3.

-O sss

Timeout value in seconds to wait for an ACK to a send request. The default is 10.

-d dictionary_file_name

Specifies the dictionary file. See "Selecting the Data Dictionary".

-D

Debug mode.

-v

Displays information about successful or failed processing as the utility runs.

Supported Attributes and Request Types

All attributes included in the data dictionary are supported.

Results

If the utility doesn't notify you that it was successful, look in the default.pinlog file to find any errors. This file is either in the directory from which the utility was started or in a directory specified in the utility configuration file.