> Configuring Chassis for inPilot
> This chapter describes the configurations required to source data for the inPilot application.
> Important: These configurations are on the chassis.
> For more information on ECS configurations, see the Enhanced Charging Services Administration Guide.
> This chapter describes the following topics:

> • | Initial Configuration

> • | Configuration

> Initial Configuration
> If the configurations described in this section are not already available on the system, these must be configured.
> Initial configuration steps:

> Step 1 | Ensure that ECS license is installed on the system.

> Step 2 | Create the ECS administrative user account as described in the Creating the ECS Administrative User Account section.

> Step 3 | Enable Active Charging as described in the Enabling Active Charging section.

> Step 4 | Create Active Charging Service as described in the Creating the Active Charging Service section.

> Step 5 | Save your configuration as described in the Verifying and Saving Your Configuration chapter.

> Important: Commands used in the configuration examples in this section provide base functionality to the extent that the most common or likely commands and/or keyword options are presented. In many cases, other optional commands and/or keyword options are available. Refer to the Command Line Interface Reference for complete information regarding all commands.
> Installing the ECS License
> To enable and configure ECS functionality on the system you must obtain and install one of the following licenses:

> • | [600-00-7526] Enhanced Charging Bundle 1 1k Sessions license

> • | [600-00-7574] Enhanced Charging Bundle 2 1k Sessions license—to enable and configure Diameter and DCCA functionality with ECS

> For information on how to install licenses, see the Managing License Keys section of the Software Management Operations chapter in the Administration and Configuration Guide.
> Creating the ECS Administrative User Account
> At least one administrative user account that has ECS functionality privileges must be configured on the system. This is the account that is used to log on and execute ECS-related commands. For security purposes, it is recommended that these user accounts be created along with general system functionality administration.
> Use the following configuration example to create the ECS Administrative user account:
> configure
> context local
> administrator <user_name> password <password> ecs
> end
> Notes:

> • | Aside from having ECS capabilities, an ECS Administrator account also has the same capabilities and privileges as any other system-level administrator account.

> • | You can also create system ECS user account for a config-administrator, operator, or inspector. ECS accounts have all the same system-level privileges of normal system accounts except that they have full ECS command execution capability. For example, an ECS has rights to execute every command that a regular administrator can in addition to all of the ECS commands.

> • | Note that only Administrator and Config-administrator-level users can provision ECS functionality. Refer to the Configuring System Settings chapter of the System Administration and Configuration Guide for additional information on administrative user privileges.

> Enabling Active Charging
> Active Charging must be enabled before configuring charging services.
> Use the following configuration example to enable Active Charging:
> configure
> require active-charging optimized-mode
> context local
> interface <interface_name>
> ip address <ip_address> <ip_mask>
> exit
> server ftpd
> end
> Notes:

> • | ACS must be enabled in Optimized mode, wherein ACS functionality is managed by SessMgrs. The require active-charging optimized-mode command enables ACS in Optimized mode.

> • | The require active-charging optimized-mode command must be a part of the boot configuration. If configured after booting, the configuration must be saved and the system rebooted for the change to take effect.

> Creating the Active Charging Service
> Use the following configuration example to create an Active Charging Service:
> configure
> active-charging service <service_name> [ -noconfirm ]
> end
> Configuration
> The following is the sequence of configurations necessary to source data to the inPilot application:

> Step 1 | Activate P2P analyzer as described in the Activating P2P Analyzer section.

> Step 2 | Configure EDR flow format as described in the Configuring the EDR Flow Format section.

> Step 3 | Configure routing ruledefs and rulebase for deep-packet inspection as described in the Configuring Deep Packet Inspection section.

> Step 4 | Configure EDR module as described in the EDR Module Configuration section.

> Step 5 | Configure user as described in the Configuring EDR Download Permission section.

> Step 6 | Configure bulkstat schemas as described in the Configuring Bulkstat Schemas section.

> Step 7 | Load the bulkstats configuration file to the gateway as described in the Loading Bulkstats Configuration File section.

> Step 8 | Save your configuration as described in the Verifying and Saving Your Configuration chapter.

> Activating P2P Analyzer
> Use the following configuration example to activate P2P protocol detection:
> configure
> active-charging service <service_name>
> p2p-detection protocol all
> rulebase <rulebase_name>
> p2p dynamic-flow-detection
> end
> Notes:

> • | P2P protocol detection must be activated only within rulebases used by the APNs for which P2P detection is applicable. P2P detection must not be applied to the rulebases used for APNs where such reporting is either not useful or is not possible.

> Configuring the EDR Flow Format
> Use the following configuration example to configure the EDR format generated for flows:
> configure
> active-charging service <service_name>
> edr-format <edr_format_name> [ -noconfirm ]
> attribute <attribute> { [ format { MM/DD/YY-HH:MM:SS | MM/DD/YYYY-HH:MM:SS | YYYY/MM/DD-HH:MM:SS | YYYYMMDDHHMMSS | seconds } ] [ localtime ] | [ { ip | tcp } { bytes | pkts } { downlink | uplink } ] priority <priority> }
> rule-variable <protocol> <rule> priority <priority>
> event-label <event-label> priority <priority>
> end
> Notes:

> • | For information on EDR format configuration and rule variables, refer to the EDR Format Configuration Mode Commands chapter of the Command Line Interface Reference.

> The following is a sample EDR configuration.
> configure
> active-charging service ecs_svc1
> edr-format edr_flow_format
> attribute sn-start-time format seconds priority 10
> attribute sn-end-time format seconds priority 20
> attribute radius-calling-station-id priority 30
> rule-variable ip server-ip-address priority 60
> attribute sn-server-port priority 70
> attribute sn-app-protocol priority 80
> attribute sn-parent-protocol priority 81
> rule-variable ip protocol priority 82
> rule-variable p2p protocol priority 90
> attribute sn-volume-amt ip bytes uplink priority 100
> attribute sn-volume-amt ip bytes downlink priority 110
> attribute sn-volume-amt ip pkts uplink priority 120
> attribute sn-volume-amt ip pkts downlink priority 130
> rule-variable bearer 3gpp charging-id priority 140
> rule-variable bearer 3gpp imei priority 141
> rule-variable bearer 3gpp rat-type priority 142
> rule-variable bearer 3gpp user-location-information priority 143
> rule-variable traffic type priority 160
> rule-variable voip-duration priority 170
> end
> The following is a sample HTTP EDR configuration.
> configure
> active-charging service ecs_svc1
> edr-format edr_http_format
> attribute sn-start-time format seconds priority 10
> attribute sn-end-time format seconds priority 20
> attribute radius-calling-station-id priority 30
> rule-variable ip server-ip-address priority 50
> rule-variable http host priority 70
> rule-variable http content type priority 80
> attribute transaction-downlink-bytes priority 90
> attribute transaction-uplink-bytes priority 100
> attribute transaction-downlink-packets priority 110
> attribute transaction-uplink-packets priority 120
> rule-variable bearer 3gpp charging-id priority 130
> end
> Verifying your Configuration
> To verify your configuration, in the Exec Mode, enter the following command:
> show active-charging edr-format name <edr_format_name>
> Configuring Deep Packet Inspection
> Configuring Routing Rule Definition
> Use the following configuration example to create and configure a routing ruledef:
> configure
> active-charging service <service_name>
> ruledef <ruledef_name>
> <protocol> <expression> <operator> <condition>
> rule-application routing
> end
> Notes:

> • | The rule-application routing command specifies the ruledef type. If not specified, by default, the system configures the ruledef as a charging ruledef.

> • | For information on all the protocol types, expressions, operators, and conditions supported, refer to the Ruledef Configuration Mode Commands chapter of the Command Line Interface Reference.

> • | Up to 10 rule matches can be configured in one ruledef.

> Verifying your Configuration
> To verify your configuration, in the Exec Mode, enter the following command:
> show active-charging ruledef routing
> Configuring Rulebase
> Use the following configuration example to route traffic to the appropriate analyzer within each rulebase where the reporting is applicable.
> configure
> active-charging service <service_name>
> rulebase <rulebase_name> [ -noconfirm ]
> route priority <priority> ruledef <ruledef_name> analyzer <analyzer> [ description ]
> rtp dynamic-flow-detection
> flow end-condition timeout normal-end-signaling session-end edr <edr_format_name>
> end
> The following is a sample rulebase configuration.
> configure
> active-charging service ecs_svc1
> rulebase p2p-rb
> flow end-condition timeout normal-end-signaling session-end edr edr_flow_format
> action priority 4 ruledef rtsp_setup charging-action standard
> action priority 5 ruledef rtsp_play charging-action standard
> action priority 6 ruledef rtsp_teardown charging-action standard
> action priority 7 ruledef rtsp_anymatch charging-action standard
> action priority 10 ruledef sip_anymatch charging-action handshake
> action priority 11 ruledef rtp-anymatch charging-action handshake
> action priority 12 ruledef udp-anymatch charging-action handshake
> action priority 13 ruledef tcp-anymatch charging-action handshake
> action priority 100 ruledef ip-anymatch charging-action handshake
> route priority 60 ruledef sip-src analyzer sip
> route priority 65 ruledef sip-dst analyzer sip
> route priority 70 ruledef rtsp-src analyzer rtsp
> route priority 75 ruledef rtsp-dst analyzer rtsp
> route priority 250 ruledef sdp_route analyzer sdp
> rtp dynamic-flow-detection
> edr transaction-complete http edr-format edr_http_format
> edr voip-call-end edr-format edr_flow_format
> p2p dynamic-flow-detection
> end
> Verifying your Configuration
> To verify your configuration, in the Exec Mode, enter the following command:
> show active-charging rulebase name <rulebase_name>
> Configuring Charging Action
> Use the following configuration example to configure a charging action:
> configure
> active-charging service <service_name>
> charging-action <charging_action_name> [ -noconfirm ]
> content-id <content_id>
> retransmissions-counted
> billing-action [ edr <edr_format> [ wait-until-flow-ends ] | egcdr | exclude-from-udrs | radius ] +
> flow idle-timeout <idle_timeout>
> end
> Verifying your Configuration
> To verify your configuration, in the Exec Mode, enter the following command:
> show active-charging charging-action name <charging_action_name>
> EDR Module Configuration
> Use the following configuration example to configure the EDR module:
> configure
> context <context_name>
> edr-module active-charging-service
> file name <file_name> rotation volume <file_size_bytes> rotation time <file_complete_seconds> storage-limit <storage_limit_bytes> headers reset-indicator edr-format-name trap-on-file-delete compression gzip file-sequence-number rulebase-seq-num
> cdr [ push-interval <interval> | remove-file-after-transfer | transfer-mode { pull | push primary { encrypted-url <enc_url> | url <url> } [ secondary { encrypted-secondary-url <enc_sec_url> | url <sec_url> } ] } + | use-harddisk ]
> end
> Notes:

> • | The <context_name> must be the context specified for accounting.

> • | The cdr use-harddisk command is only available on the ASR 5000 platform.

> • | The cdr use-harddisk command specifies storing files on the hard disk. The reporting server will download these files through the SPIO interface on the SMC and will delete the files after successful retrieval.

> • | The edr-format-name keyword must be configured to distinguish between different EDRs.

> • | The files will be compressed to save storage and transmission bandwidth.

> Verifying your Configuration
> To verify your configuration, in the Exec Mode, enter the following command:
> show active-charging edr-udr-file statistics
> Pushing EDR/UDR Files Manually
> To manually push EDR/UDR files to the configured L-ESS, in the Exec mode, enter the following command:
> cdr-push { all | local-filename <file_name> }
> Notes:

> • | Before you can use this command, in the EDR/UDR Configuration Mode, the CDR transfer mode and file locations must be set to push.

> • | <file_name> must be absolute path of the local file to push.

> Configuring EDR Download Permission
> Use the following configuration example to configure EDR download permission:
> configure
> context local
> administrator <administrator_id> password <password> ftp nocli
> end
> Notes:

> • | The user must be configured in the local context with administrative privileges to download and delete EDRs from the hard disk. The ftp nocli options restrict access to FTP only.

> Configuring Bulkstat Schemas
> Ensure that the following checks are made prior to configuring bulkstat schemas.

> • | FTP must be enabled on the inPilot server.

> To enable the FTP daemon, use the following command:
> /usr/sbin/svcadm/ enable ftp
> To disable the FTP daemon, use the following command:
> /usr/sbin/svcadm/ disable ftp

> • | Bulkstat files FTPed from gateways must have the following file naming convention:

> bulkstat%date%%time%.txt
> Where, date format = yyyymmdd and Time format = hhmmss
> Example: bulkstat20100206150002.txt

> • | Bulkstats files must be FTPed at the following location from the gateway:

> $STARBI_HOME/server/data/$gwname/bs
> Where $STARBI_HOME = inPilot installation directory
> $gwname = Gateway name
> Use the following configuration example to configure bulkstat schemas:
> configure
> bulkstats collection
> bulkstats mode
> sample-interval <minutes>
> transfer-interval <minutes>
> file <file_number>
> header format <format_string>
> remotefile format <format_string>
> receiver <ip_address> primary mechanism ftp login <user_name> password <password>
> <module> schema <schema_name> format <format_string>
> end
> Notes:

> • | <ip_address> specifies the IP address of the inPilot server.

> • | The default file transfer mechanism is ftp.

> • | For more information on commands for bulkstats configuration on the chassis, refer to the Bulk Statistics Configuration Mode Commands chapter in the Command Line Interface Reference Guide.

> • | For more information on variable descriptions for bulkstats schema configuration, refer to the Statistics and Counters Reference Guide or WEM Online Help.

> For viewing the sample bulkstats configuration file, refer to Sample Bulkstats Schema Configuration appendix.
> Loading Bulkstats Configuration File
> To load the bulkstats configuration file to the gateway, use the following command:
> configure [File URL]
> Where, File URL is the path of bulkstats configuration file.

Cisco Systems Inc.
Tel: 408-526-4000
Fax: 408-527-0883