> Peer-to-Peer Detection Configuration
> This chapter describes how to configure the Peer-to-Peer (P2P) Detection feature.
> The following topics are covered in this chapter:

> • | Configuring System for P2P Detection Support

> • | Verifying the Configuration

> • | Gathering P2P Statistics

> • | P2P Reports

> Configuring System for P2P Detection Support
> This section lists the high-level steps to configuring the system with enhanced charging services for P2P Detection support in conjunction with ECS services.
> To configure the system for P2P Detection support with ECS:

> Step 1 | Set initial configuration parameters such as activating PACs/PSCs and modifying the local context as described in the Initial Configuration section.

> Step 2 | Enable the Enhanced Charging service with P2P and set basic ECS parameters such as service configuration, Ruledefs, charging actions, and EDRs as described in the P2P Detection Configuration section.

> Step 3 | Save the changes to system configuration as described in the Save the Configuration section.

> 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.
> Initial Configuration
> To perform initial system configuration for P2P detection support with ECS:

> Step 1 | Specify the role of the PACs/PSCs in the chassis as described in the Activating PACsPSCs section.

> Step 2 | Enable ACS as described in the Enabling Enhanced Charging section.

> Step 3 | Set local system management parameters as described in the Modifying the Local Context section.

> Activating PACs/PSCs
> Use the following configuration example to activate two PACs/PSCs, placing one in “active” mode and labeling the other as redundant:
> configure
> card <slot_number>
> redundancy card-mode [ -noconfirm ]
> exit
> card <slot_number>
> mode active pac/psc
> end
> Enabling Enhanced Charging
> Use the following configuration example to enable enhanced charging on the system:
> configure
> require active-charging
> end
> Modifying the Local Context
> Use the following configuration example to set the default subscriber and AAA group in the local context:
> configure
> context local
> interface <interface>
> ip address <address/mask>
> ip arp timeout <timeout>
> exit
> server ftpd
> exit
> server sshd
> subsystem sftp
> exit
> server telnetd
> exit
> subscriber default
> exit
> administrator <security_admin> encrypted password <password> ftp
> aaa group default
> exit
> gtpp group default
> exit
> ip route <route> SPIO1
> exit
> port ethernet <slot/port>
> no shutdown
> bind interface <interface> local
> exit
> snmp engine-id local <id_number>
> end
> P2P Detection Configuration
> To configure P2P Detection with ACS:

> Step 1 | Create the ACS service as described in the Creating the Active Charging Service section.

> Step 2 | Configure P2P detection rules as described in the Configuring P2P Detection Rules section.

> Step 3 | Configure the charging action as described in the Configuring the Charging Action section.

> Step 4 | Configure the rulebase as described in the Configuring the Rulebase section.

> Step 5 | Optional: Set EDR formats as described in the Setting EDR Formats section.

> Step 6 | Enable DSCP settings as described in the Enable DSCP Marking section.

> Step 7 | Optional: Configure P2P Dynamic Signature Updates functionality as described in the Configuring P2P Dynamic Signature Updates section.

> 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.
> Creating the Active Charging Service
> Use the following configuration example to create the ACS service:
> configure
> active-charging service <acs_service_name> [ -noconfirm ]
> end
> Configuring P2P Detection Rules
> Use the following configuration example to set the P2P detection protocols in the ACS and the rule definitions for each P2P protocol. Note that the following example includes configuration to report voice and non-voice components for Skype, Yahoo, and MSN separately.
> configure
> active-charging service <acs_service_name>
> p2p-detection protocol all
> ruledef <charging_ruledef_actsync>
> p2p protocol = actsync
> exit
> ruledef <charging_ruledef_aimini>
> p2p protocol = aimini
> exit
> ruledef <charging_ruledef_applejuice>
> p2p protocol = applejuice
> exit
> ruledef <charging_ruledef_ares>
> p2p protocol = ares
> exit
> ruledef <charging_ruledef_battlefld>
> p2p protocol = battlefld
> exit
> ruledef <charging_ruledef_bittorrent>
> p2p protocol = bittorrent
> exit
> ruledef <charging_ruledef_ddlink>
> p2p protocol = ddlink
> exit
> ruledef <charging_ruledef_directconnect>
> p2p protocol = directconnect
> exit
> ruledef <charging_ruledef_edonkey>
> p2p protocol = edonkey
> exit
> ruledef <charging_ruledef_fasttrack>
> p2p protocol = fasttrack
> exit
> ruledef <charging_ruledef_feidian>
> p2p protocol = feidian
> exit
> ruledef <charging_ruledef_filetopia>
> p2p protocol = filetopia
> exit
> ruledef <charging_ruledef_freenet>
> p2p protocol = freenet
> exit
> ruledef <charging_ruledef_fring>
> p2p protocol = fring
> exit
> ruledef <charging_ruledef_gadugadu>
> p2p protocol = gadugadu
> exit
> ruledef <charging_ruledef_gnutella>
> p2p protocol = gnutella
> exit
> ruledef <charging_ruledef_gtalk>
> p2p protocol = gtalk
> exit
> ruledef <charging_ruledef_halflife2>
> p2p protocol = halflife2
> exit
> ruledef <charging_ruledef_hamachivpn>
> p2p protocol = hamachivpn
> exit
> ruledef <charging_ruledef_iax>
> p2p protocol = iax
> exit
> ruledef <charging_ruledef_imesh>
> p2p protocol = imesh
> exit
> ruledef <charging_ruledef_iptv>
> p2p protocol = iptv
> exit
> ruledef <charging_ruledef_irc>
> p2p protocol = irc
> exit
> ruledef <charging_ruledef_iskoot>
> p2p protocol = iskoot
> exit
> ruledef <charging_ruledef_jabber>
> p2p protocol = jabber
> exit
> ruledef <charging_ruledef_manolito>
> p2p protocol = manolito
> exit
> ruledef <charging_ruledef_msn>
> p2p protocol = msn
> exit
> ruledef <charging_ruledef_mute>
> p2p protocol = mute
> exit
> ruledef <charging_ruledef_nimbuzz>
> p2p protocol = nimbuzz
> exit
> ruledef <charging_ruledef_oovoo>
> p2p protocol = oovoo
> exit
> ruledef <charging_ruledef_openft>
> p2p protocol = openft
> exit
> ruledef <charging_ruledef_orb>
> p2p protocol = orb
> exit
> ruledef <charging_ruledef_oscar>
> p2p protocol = oscar
> exit
> ruledef <charging_ruledef_paltalk>
> p2p protocol = paltalk
> exit
> ruledef <charging_ruledef_pando>
> p2p protocol = pando
> exit
> ruledef <charging_ruledef_pandora>
> p2p protocol = pandora
> exit
> ruledef <charging_ruledef_popo>
> p2p protocol = popo
> exit
> ruledef <charging_ruledef_pplive>
> p2p protocol = pplive
> exit
> ruledef <charging_ruledef_ppstream>
> p2p protocol = ppstream
> exit
> ruledef <charging_ruledef_qq>
> p2p protocol = qq
> exit
> ruledef <charging_ruledef_qqgame>
> p2p protocol = qqgame
> exit
> ruledef <charging_ruledef_qqlive>
> p2p protocol = qqlive
> exit
> ruledef <charging_ruledef_quake>
> p2p protocol = quake
> exit
> ruledef <charging_ruledef_rdp>
> p2p protocol = rdp
> exit
> ruledef <charging_ruledef_secondlife>
> p2p protocol = secondlife
> exit
> ruledef <charging_ruledef_skinny>
> p2p protocol = skinny
> exit
> ruledef <charging_ruledef_skype>
> p2p protocol = skype
> exit
> ruledef <charging_ruledef_slingbox>
> p2p protocol = slingbox
> exit
> ruledef <charging_ruledef_sopcast>
> p2p protocol = sopcast
> exit
> ruledef <charging_ruledef_soulseek>
> p2p protocol = soulseek
> exit
> ruledef <charging_ruledef_steam>
> p2p protocol = steam
> exit
> ruledef <charging_ruledef_tvants>
> p2p protocol = tvants
> exit
> ruledef <charging_ruledef_tvuplayer>
> p2p protocol = tvuplayer
> exit
> ruledef <charging_ruledef_uusee>
> p2p protocol = uusee
> exit
> ruledef <charging_ruledef_vpnx>
> p2p protocol = vpnx
> exit
> ruledef <charging_ruledef_vtun>
> p2p protocol = vtun
> exit
> ruledef <charging_ruledef_warcft3>
> p2p protocol = warcft3
> exit
> ruledef <charging_ruledef_winmx>
> p2p protocol = winmx
> exit
> ruledef <charging_ruledef_winny>
> p2p protocol = winny
> exit
> ruledef <charging_ruledef_wofwarcraft>
> p2p protocol = wofwarcraft
> exit
> ruledef <charging_ruledef_xbox>
> p2p protocol = xbox
> exit
> ruledef <charging_ruledef_yahoo>
> p2p protocol = yahoo
> exit
> ruledef <charging_ruledef_zattoo>
> p2p protocol = zattoo
> exit
> # Configuration to report voice and non-voice components for GTalk, MSN, Oscar, Skype, and Yahoo separately:
> ruledef <charging_ruledef_gtalk_voice>
> p2p protocol = gtalk
> p2p traffic-type = voice
> exit
> ruledef <charging_ruledef_gtalk_non_voice>
> p2p protocol = gtalk
> p2p traffic-type != voice
> exit
> ruledef <charging_ruledef_msn_voice>
> p2p protocol = msn
> p2p traffic-type = voice
> exit
> ruledef <charging_ruledef_msn_non_voice>
> p2p protocol = msn
> p2p traffic-type != voice
> exit
> ruledef <charging_ruledef_oscar_voice>
> p2p protocol = oscar
> p2p traffic-type = voice
> exit
> ruledef <charging_ruledef_oscar_non_voice>
> p2p protocol = oscar
> p2p traffic-type != voice
> exit
> ruledef <charging_ruledef_skype_voice>
> p2p protocol = skype
> p2p traffic-type = voice
> exit
> ruledef <charging_ruledef_skype_non_voice>
> p2p protocol = skype
> p2p traffic-type != voice
> exit
> ruledef <charging_ruledef_yahoo_voice>
> p2p protocol = yahoo
> p2p traffic-type = voice
> exit
> ruledef <charging_ruledef_yahoo_non_voice>
> p2p protocol = yahoo
> p2p traffic-type != voice
> exit
> ruledef <charging_ruledef_non_voice>
> p2p traffic-type = voice
> exit
> ruledef <charging_ruledef_voice>
> p2p traffic-type != voice
> exit
> ruledef <routing_ruledef_dns-tcp>
> tcp either-port = 53
> rule-application routing
> exit
> ruledef <routing_ruledef_dns-udp>
> udp either-port = 53
> rule-application routing
> exit
> ruledef <routing_ruledef_ftp-control>
> tcp either-port = 21
> rule-application routing
> exit
> ruledef <routing_ruledef_ftp-data>
> tcp either-port = 20
> rule-application routing
> exit
> ruledef <routing_ruledef_http>
> tcp either-port = 80
> rule-application routing
> exit
> ruledef <routing_ruledef_https>
> tcp either-port = 443
> rule-application routing
> exit
> ruledef <routing_ruledef_imap>
> tcp either-port = 143
> rule-application routing
> exit
> ruledef <routing_ruledef_mms-wapcl-ct>
> wsp content type = application/vnd.wap.mms-message
> rule-application routing
> exit
> ruledef <routing_ruledef_mms_http_ct>
> http content type = application/vnd.wap.mms-message
> rule-application routing
> exit
> ruledef <routing_ruledef_mms_http_url>
> http url ends-with .mms
> rule-application routing
> exit
> ruledef <routing_ruledef_mms_wapcl-url>
> wsp url ends-with .mms
> rule-application routing
> exit
> ruledef <routing_ruledef_pop3>
> tcp either-port = 110
> rule-application routing
> exit
> ruledef <routing_ruledef_rtsp>
> tcp either-port = 554
> rule-application routing
> exit
> ruledef <routing_ruledef_rtsp-8556>
> tcp either-port = 8556
> rule-application routing
> exit
> ruledef <routing_ruledef_sdp>
> sip content type = application/sdp
> rule-application routing
> exit
> ruledef <routing_ruledef_sip>
> udp either-port = 5060
> rule-application routing
> exit
> ruledef <routing_ruledef_smtp>
> tcp either-port = 25
> rule-application routing
> exit
> ruledef <routing_ruledef_wap2.0>
> tcp either-port = 8080
> rule-application routing
> exit
> ruledef <routing_ruledef_wsp-connection-less>
> udp either-port = 9200
> rule-application routing
> exit
> ruledef <routing_ruledef_wsp-connection-oriented>
> udp either-port = 9201
> ip protocol = 51
> ip protocol = 50
> ip protocol = 47
> ip downlink = TRUE
> ip uplink = TRUE
> ip any-match = TRUE
> tcp any-match = TRUE
> udp dst-port = 5000
> rule-application routing
> end
> Notes:

> • | If in a ruledef the rule-application is not specified, by default the system configures the ruledef as a charging ruledef.

> Configuring the Charging Action
> Use the following configuration example to configure the charging actions:
> configure
> active-charging service <acs_service_name>
> charging-action <charging_action_name1>
> flow limit-for-bandwidth direction downlink peak-data-rate 4000 peak-burst-size 1024 violate-action discard committed-data-rate 3200 committed-burst-size 512 exceed-action discard
> exit
> charging-action <charging_action_name2>
> content-id 1
> exit
> charging-action <charging_action_name3>
> flow action terminate-flow
> end
> Configuring the Rulebase
> Use the following configuration example to configure the rulebases for P2P. This configuration also enables the P2P analyzer to detect the P2P applications configured for the Active Charging Service. Note that the following example includes configuration to report voice and non-voice components for GTalk, MSN, Oscar, Skype, and Yahoo separately.
> configure
> active-charging service <acs_service_name>
> rulebase <rulebase_name>
> action priority <priority> ruledef <charging_ruledef_actsync> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_aimini> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_applejuice> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_ares> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_battlefld> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_bittorrent> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_ddlink> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_directconnect> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_edonkey> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_fasttrack> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_feidian> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_filetopia> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_freenet> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_fring> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_gadugadu> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_gnutella> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_gtalk> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_halflife2> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_hamachivpn> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_iax> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_imesh> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_iptv> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_irc> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_iskoot> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_jabber> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_manolito> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_msn> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_mute> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_nimbuzz> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_oovoo> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_openft> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_orb> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_oscar> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_paltalk> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_pando> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_pandora> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_popo> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_pplive> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_ppstream> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_qq> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_qqgame> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_qqlive> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_quake> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_rdp> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_secondlife> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_skinny> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_skype> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_slingbox> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_sopcast> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_soulseek> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_steam> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_tvants> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_tvuplayer> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_uusee> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_vpnx> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_vtun> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_warcft3> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_winmx> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_winny> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_wofwarcraft> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_xbox> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_yahoo> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_zattoo> charging-action <charging_action_name>
> # Configuration to report voice and non-voice components for Oscar, GTalk, MSN, Skype, and Yahoo separately:
> action priority <priority> ruledef <charging_ruledef_gtalk_voice> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_gtalk_non_voice> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_msn_non_voice> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_voice> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_oscar_voice> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_oscar_non_voice> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_skype_voice> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_skype_non_voice> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_yahoo_voice> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_yahoo_non_voice> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_msn_voice> charging-action <charging_action_name>
> action priority <priority> ruledef <charging_ruledef_non_voice> charging-action <charging_action_name>
> route priority <priority> ruledef <routing_ruledef_http> analyzer http
> route priority <priority> ruledef <routing_ruledef_wap2.0> analyzer http
> route priority <priority> ruledef <routing_ruledef_https> analyzer secure-http
> route priority <priority> ruledef <routing_ruledef_imap> analyzer imap
> route priority <priority> ruledef <routing_ruledef_pop3> analyzer pop3
> route priority <priority> ruledef <routing_ruledef_smtp> analyzer smtp
> route priority <priority> ruledef <routing_ruledef_dns-udp> analyzer dns
> route priority <priority> ruledef <routing_ruledef_dns-tcp> analyzer dns
> route priority <priority> ruledef <routing_ruledef_ftp-control> analyzer ftp-control
> route priority <priority> ruledef <routing_ruledef_ftp-data> analyzer ftp-data
> route priority <priority> ruledef <routing_ruledef_rtsp> analyzer rtsp
> route priority <priority> ruledef <routing_ruledef_rtsp-8556> analyzer rtsp
> route priority <priority> ruledef <routing_ruledef_sip> analyzer sip
> route priority <priority> ruledef <routing_ruledef_wsp-connection-less> analyzer wsp-connection-less
> route priority <priority> ruledef <routing_ruledef_wsp-connection-oriented> analyzer wsp-connection-oriented
> route priority <priority> ruledef <routing_ruledef_sdp> analyzer sdp
> route priority <priority> ruledef <routing_ruledef_mms-wapcl-ct> analyzer mms
> route priority <priority> ruledef <routing_ruledef_mms_wapcl-url> analyzer mms
> route priority <priority> ruledef <routing_ruledef_mms_http_ct> analyzer mms
> route priority <priority> ruledef <routing_ruledef_mms_http_url> analyzer mms
> rtp dynamic-flow-detection
> p2p dynamic-flow-detection
> end
> Notes:

> • | For information about the list of protocols that support prepaid and postpaid charging, refer to the Peer-to-Peer Overview chapter of this guide.

> Setting EDR Formats
> ECS generates postpaid charging data files which can be retrieved from the system periodically and used as input to a billing mediation system for post-processing. Event Detail Records (EDRs) are generated according to action statements in rule commands.
> Up to 32 different EDR schema types may be specified, each composed of up to 32 fields or analyzer parameter names. The records are written at the time of each rule event in a comma-separated (CSV) format. This configuration aids in capturing the detected P2P protocol data in the EDR.
> Use the following example to set the EDR configuration:
> configure
> active-charging service <ecs_service>
> edr-format <edr_flow_format>
> rule-variable traffic type priority <priority>
> rule-variable voip-duration priority <priority>
> attribute sn-start-time format seconds priority <priority>
> attribute sn-end-time format seconds priority <priority>
> attribute radius-calling-station-id priority <priority>
> rule-variable ip server-ip-address priority <priority>
> attribute sn-server-port priority <priority>
> attribute sn-app-protocol priority <priority>
> attribute sn-parent-protocol priority <priority>
> rule-variable ip protocol priority <priority>
> rule-variable p2p protocol priority <priority>
> attribute sn-volume-amt ip bytes uplink priority <priority>
> attribute sn-volume-amt ip bytes downlink priority <priority>
> attribute sn-volume-amt ip pkts uplink priority <priority>
> attribute sn-volume-amt ip pkts downlink priority <priority>
> rule-variable bearer 3gpp charging-id priority <priority>
> rule-variable bearer 3gpp imei priority <priority>
> rule-variable bearer 3gpp rat-type priority <priority>
> rule-variable bearer 3gpp user-location-information 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 Guide.

> Enable DSCP Marking
> Use the following configuration example to enable DSCP marking in the configuration:
> configure
> context ggsn
> interface <interface>
> ip address <address/mask>
> ip arp timeout <timeout>
> exit
> subscriber default
> ip context-name <context_name>
> exit
> apn <apn_name>
> selection-mode sent-by-ms
> accounting-mode none
> ip access-group <access_group_name> in
> ip access-group <access_group_name> out
> ip source-violation ignore
> ip qos-dscp conversational pt streaming pt interactive 1 pt interactive 2 pt interactive 3 pt background pt
> ip qos-dscp interactive 1 allocation-retention-priority 1 pt interactive 1 allocation-retention-priority 2 pt interactive 1 allocation-retention-priority 3 pt
> ip qos-dscp interactive 2 allocation-retention-priority 1 pt interactive 2 allocation-retention-priority 2 pt interactive 2 allocation-retention-priority 3 pt
> ip qos-dscp interactive 3 allocation-retention-priority 1 pt interactive 3 allocation-retention-priority 2 pt interactive 3 allocation-retention-priority 3 pt
> ip context-name <context_name>
> ip address pool name <pool_name>
> active-charging rulebase <rulebase_name>
> exit
> aaa group default
> exit
> gtpp group default
> exit
> ggsn-service GGSN
> retransmission-timeout <retransmission_timeout>
> max-retransmission <max_retransmission>
> plmn unlisted-sgsn home
> bind address <ip_address>
> exit
> context <context_name>
> ip access-list <access_list_name>
> redirect css service <acs_service> ip any any
> exit
> ip pool <pool_name> <ip_address/mask> static
> interface <interface>
> ip address <ip_address/mask>
> ip arp timeout <timeout>
> exit
> subscriber default
> exit
> radius group default
> exit
> gtpp group default
> exit
> ip route <ip_address/mask> <interface>
> exit
> port ethernet <interface>
> no shutdown
> bind interface <interface> ggsn
> exit
> port ethernet <interface>
> no shutdown
> bind interface <interface> <context_name>
> end
> Notes:

> • | <acs_service> is the name of the ACS service; no CSS service needs to be configured.

> Configuring P2P Dynamic Signature Updates
> This section describes how to enable and configure the P2P Dynamic Signature Updates feature.
> Enabling/Disabling P2P Dynamic Signature Updates
> To enable the P2P Dynamic Signature Updates feature, use the following configuration example:
> configure
> active-charging service <acs_service_name>
> default p2p-dynamic-rules file
> end
> Notes:

> • | On enabling the P2P Dynamic Signature Updates feature, if a P2P signature file is available at the default location, the system loads it. Default location for the signature file is “/usr/lib/p2p-rules.xml”.

> Loading/Enabling Signatures
> To enable the P2P Dynamic Signature Updates feature, and load a specific signature file (from other than the default location) to the memory, use the following configuration example:
> configure
> active-charging service <acs_service_name>
> p2p-dynamic-rules { file <location> | protocol [ all | bittorrent | directconnect | edonkey | gnutella | skype | yahoo + ] }
> end
> Notes:

> • | <location> must be one of the following:

> [file:]{/flash | /pcmcia1 | /hd-raid}[/<directory>]/<filename>

> • | The protocol keyword and options can be used to selectively enable signatures for specific protocol(s).

> • | This release supports dynamic signature updates only for the following protocols: BitTorrent, DirectConnect, eDonkey, Gnutella, Skype, and Yahoo.

> Unloading/Disabling Signatures
> To disable the P2P Dynamic Signature Updates feature, and delete any signatures in the memory, use the following configuration example:
> configure
> active-charging service <acs_service_name>
> no p2p-dynamic-rules { file | protocol [ all | bittorrent | directconnect | edonkey | gnutella | skype | yahoo + ] }
> end
> Notes:

> • | The no p2p-dynamic-rules file command disables the P2P Dynamic Signature Updates feature, also any/specified signature(s) already loaded in the memory is unloaded. If there are any active sessions using the file, it changes the file status to inactive. And, when the sessions are cleared, the file is removed from the memory.

> • | The no p2p-dynamic-rules protocol [ all | bittorrent | directconnect | edonkey | gnutella | skype | yahoo + ] command disables the execution of signatures loaded in the memory for a specific protocol or all protocols.

> Saving the Configuration
> Refer to the Verifying and Saving Your Configuration chapter of this guide to save changes made to the system configuration for P2P Detection.
> Verifying the Configuration
> This section explains how to review the configurations after saving them in a .cfg file as described in Verifying and Saving Your Configuration chapter and also to retrieve errors and warnings within an active configuration for a service.
> Viewing System Configuration
> The following configuration example displays the active configuration for a service:
> configure
> context <context_name>
> end
> show configuration [ card <card_num> | context <name> [ radius group [ all | name <group> ] ] | port <slot/port> | srp ] [ showsecrets ] [ url <url> ] [ verbose ] [ | { grep <grep_options> | more } ]
> Viewing Service Configuration Errors
> The following configuration example displays the errors in configuration for a service:
> configure
> context <context_name>
> end
> show configuration errors section active-charging [ verbose ] [ | { grep <grep_options> | more } ]
> Gathering P2P Statistics
> In the following table, the first column lists what statistics to gather, the second column lists an action to perform, and the third column describes what information is displayed or what information to look for in the resulting output.
> Gathering Statistics

> Statistics Wanted | Action to Perform | Information to Look For
> Analyzer statistics | At the Exec Mode prompt, enter the following command: show active-charging analyzer statistics name p2p verbose | The output of this command displays the analyzer statistics if a P2P analyzer is used. Since the analyzer statistics are not bound to any service, the traffic information per gateway can be obtained.
> Ruledef statistics | At the Exec Mode prompt, enter the following command: show active-charging ruledef statistics name <name> | The output of this command displays the Ruledef statistics including the packet count, byte count and hits.
> P2P flow statistics | At the Exec Mode prompt, enter the following command: show active-charging flows type p2p traffic-type voice show active-charging flows type p2p traffic-type non-voice | The output of this command displays the number of P2P voice and non-voice flows.
> Charging Action information | At the Exec Mode prompt, enter the following command: show active-charging charging-action statistics | The output of this command displays the charging action information and corresponding statistics configured in the active charging service.
> Transmit and Receive data | At the Exec Mode prompt, enter the following command: show active-charging sessions tx-data <operator> <bytes> show active-charging sessions rx-data <operator> <bytes> | The output of the command displays the information for sessions that have received or transmitted data which matches the criteria.
> Sessions using specific protocol | At the Exec Mode prompt, enter the following command: show active-charging sessions type P2P application <protocol> | The output of this command displays information for the sessions using the specified protocol.
> Total and current P2P and P2P voice flows | At the Exec Mode prompt, enter the following command: show active-charging subsystem all | The output of this command displays total and current P2P flow and P2P voice flow statistics, and total number of subscribers.
> Dynamic signature files information | At the Exec Mode prompt, enter the following command: show active-charging p2p-dynamic-rules verbose | The output of this command displays P2P dynamic signature file information.
> Voice Statistics | At the Exec Mode prompt, enter the following command: show active-charging analyzer statistics name p2p application [ gtalk | msn | oscar | skype | yahoo ] | The output of this command displays the voice and non-voice analyzer statistics for voice supported protocols (MSN, Yahoo, GTalk, Skype, Oscar).

> ‌
> The P2P analyzer tracks all P2P protocols for both uplink and downlink packets and bytes statistics. For additional statistics, refer to the Gathering P2P Statistics section in the P2P Service Configuration chapter of the Peer-to-Peer Detection Administration Guide.
> Supported Bulk Statistics
> For information on P2P bulk statistics and bulk statistics configuration and collection, refer to the Bulk Statistics Configuration Mode Commands chapter of the Command Line Interface Reference, and the Statistics and Counters Reference.
> P2P Reports
> The P2P reports provide details of the bandwidth consumption of P2P traffic over time. These reports are used to analyze network performance, identify the customer trends, network usage patterns, and network categorization.
> Important: In StarOS 9.0 and earlier releases, the P2P reporting functionality was available in the Web Element Manager software. For more information, refer to the WEM Online Help documentation.
> Important: In StarOS 10.0 and later releases, the P2P reporting functionality is supported in inPilot. For more information, refer to the inPilot Online Help documentation.
> The following bandwidth usage reports are supported:

> • | Cumulative analyzer count - representing the total bandwidth consumed by the P2P traffic in bits/sec. Daily, monthly or yearly reports are supported.

> • | Total bandwidth consumed P2P traffic against other protocols like HTTP, RTSP, etc. Daily or monthly reports are supported.

> • | Per protocol type - total bandwidth consumed by the individual P2P protocol traffic in packets/sec or bytes/sec plotted against time range or date range. Daily reports are supported. The graph uses separate colors to differentiate among the multiple protocol types.

> • | The number of active users per application for specified date/time range. Daily reports are supported.

> • | Analysis of the percentage of total bandwidth consumed by P2P traffic from the total subscriber traffic. Weekly reports are supported.

> Important: For additional information about viewing reports, refer to the Web Element Manager Online Help System.

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