Yota PCRF - BME MIK LABORATÓRIUMzfaigl/QoS/doc/freePCRF... · Yota PCRF is a software product that allows managing access level to network resources and quality of services in different

© Yota 2013

Yota PCRF

Installation Guide

Product version: 3.6

Document version: 3.1

Status: development

© Yota 2013 2

Revision History

Date Version Author Revision

11.01.2013 1.0 Evgenia Martynyuk Document created.

28.03.2013 3.0 Evgenia Martynyuk Translated to English

12.09.2013 3.1 Evgenia Martynyuk

Minor corrections. PCRF and DDF clusters installation process, post-installation steps were updated.

Supported product version changed to 3.6

© Yota 2013 3

Table of Contents

About the Guide ........................................................................................................ 5

Formatting conventions .......................................................................................... 5

Introduction .............................................................................................................. 6

Terms and Definitions ............................................................................................ 6

Abbreviations ........................................................................................................ 6

Brief Yota PCRF Overview ........................................................................................... 7

System Purposes ....................................................................................................... 8

Geographical Distribution ........................................................................................... 8

Connectivity Description ............................................................................................. 9

PCRF Cluster ......................................................................................................... 9

DDF Cluster ......................................................................................................... 10

Installation Overview ............................................................................................... 11

Brief Installation Overview ......................................................................................... 12

System Requirements ............................................................................................... 12

Hardware Requirements ........................................................................................ 12

Software Requirements ......................................................................................... 12

PCRF Cluster Installation .......................................................................................... 13

Pre-installation Steps ................................................................................................ 14

PCRF Installation Files ........................................................................................... 14

PCRF Cluster Network Settings ............................................................................... 14

Supplementary Libraries Installation ....................................................................... 16

Time Format Setup ............................................................................................... 16

Swap Disabling ..................................................................................................... 16

PCRF Cluster Installation ........................................................................................... 17

Deploy Configuration File ....................................................................................... 17

Installation .......................................................................................................... 19

Core-files ............................................................................................................. 19

Third-party Software Installation ................................................................................ 20

PCRF as Standalone Node .......................................................................................... 20

DDF Cluster Installation ........................................................................................... 21

Pre-installation Steps ................................................................................................ 22

DDF Installation Files ............................................................................................ 22

DDF Cluster Network Settings ................................................................................ 22

Supplementary Libraries Installation ....................................................................... 23

Time Format Setup ............................................................................................... 23

© Yota 2013 4

Swap Disabling ..................................................................................................... 23

DDF Cluster Installation ............................................................................................. 24

Deploy Configuration File ....................................................................................... 24

Installation .......................................................................................................... 25

Core-files ............................................................................................................. 26

Post-installation Steps ............................................................................................. 27

Initial DDF O&M Console Configuration ........................................................................ 28

Initial PCRF O&M Console Configuration ....................................................................... 29

System Clusters Correct Operation Verification ............................................................. 30

Correct Process Start ............................................................................................ 30

Log Messages Check ............................................................................................. 31

System Status in O&M Console ............................................................................... 31

PCRF Cluster Implementation and Recovery ............................................................. 33

New PCRF Cluster Implementation .............................................................................. 34

System Cluster Recovery after Complete Failure ........................................................... 35

About the Guide

© Yota 2013 5

About the Guide

The following formatting convention is used the document:

Formatting conventions

Item Convention Example

Command-line commands and scripts

Monospace (Courier New font)

/opt/box_ddf/utils/ddf_full_stop.sh

Document titles Title caps, italic See "BIS.3_0_5_SP1 Release Notes"

Chapter titles Title caps, in quotation marks

See Chapter 2, "PCRF System Processes"

Command on menus and buttons

Bold, capitalization as in a user interface

Click Add button

System components Default, capitalization PCRF cluster

General emphasis Italic Reference to another chapter of the same document is made as a cross reference in the following format

Yota PCRF 3.6

Installation Guide

© Yota 2013 6

Introduction

The document describes Yota PCRF system installation process for LTE networks.

The document provides information on necessary pre-installation preparatory works and the installation steps.

The information contained in the document is intended for specialists, who are in change of Yota RCRF installation. It is preferable for an installation team to be familiar with:

Linux operating system installation (Red Hat Enterprise 5.2)

Linux packages installation and their configuration

Network equipment maintenance (Procera, Huawei PGW)

Base knowledge about LTE networks

Yota PCRF 3.6 Product Description

Terms and Definitions

Policy – a set of rules that define traffic management actions. Traffic management actions

include: access level change (gating / admission control), QoS change (bandwidth, priority), etc.

DWR\DWA – Diameter messages that are used for nodes availability determination. Cluster

nodes periodically send DWR to each other and get DWA in response.

Abbreviations

Abbreviation Meaning

AAA Authentication Authorization Accounting

BSS Business Support System

DDF Data Distribution Function

Eth Ethernet

FQDN Fully Qualified Domain Name

O&M Operations and Maintenance

SPR Subscriber Profile Repository

@ Yota 2013 7

1

Brief Yota PCRF Overview

System Purposes

Geographical Distribution

Connectivity Description

Yota PCRF 3.6

Installation Guide

© Yota 2013 8

System Purposes

Yota PCRF is a software product that allows managing access level to network resources and

quality of services in different networks (LTE, 3G) in real time by applying specific policies,

based on the available information, such as subscriber services, services and network resources usage habits.

Geographical Distribution

Yota PCRF supports installation in multiple regions. The component that provides geographical

distribution is DDF (Data Distribution Function).

The scheme of geographically-distributed configuration is shown in the figure below:

Figure 1. Geographical distribution

BSS

DDF

HTTP

SPR

PCRF

PCRF

DB

City A

PCRF

DB

HTTP,

Diameter (I0,I1)

HTTP,

Diameter (I0,I1)

HTTP,

Diameter (I0,I1)

SPR

PCRF

PCRF

DB

City B

SPR

PCRF

PCRF

DB

City C

PCEFPCEF PCEFPCEF PCEFPCEF

Information

For more information about Yota PCRF, please refer to the "Yota PCRF 3.6 Product Description".


© Yota 2013 9


PCRF Cluster

In standard configuration PCRF cluster has 2 nodes. Each node is a separate server with required software. But installation as a standalone PCRF node is also possible.

Connectivity scheme for LTE network

The typical connectivity scheme for LTE network, where PCRF cluster interacts with other

network components, such as DPI (Procera, Cisco SCE), P-GW (Huawei UGW9811), is presented in the figure below:

Figure 2. Connectivity scheme (LTE)

Cluster

eth1

P-GW

(UGW9811)

PCRF 1

eth2 eth2

eth0

HTTP

Gx

PCRF 2

(DB Sync)

Gx

DPI

(Procera)

DPI

(Cisco SCE)

eth1

eth0

DDF

Cluster

Cluster nodes are connected to each other via eth2 network interface for database synchronization if PCRF is installed in cluster mode (not as single node).

Eth1 is used for interaction with DPI, P-GW via Diameter Gx protocol.

Eth0 is used for getting different management command from DDF cluster in HTTP format (delete\add subscriber profile, service, etc.)

Yota PCRF 3.6

Installation Guide

© Yota 2013 10

DDF Cluster

DDF cluster differs from PCне RF cluster only in the absence of eth1 network interface.

Cluster nodes are also connected to each other via eth2 network interface to synchronize data between them.

Eth0 is used for getting different management command from BSS in HTTP format (delete\add

subscriber profile, service, etc.) and sending them to PCRF clusters; work with O&M console is

also performed via Eth0.

@ Yota 2013 11

2

Installation Overview

Brief Installation Overview

System Requirements

Yota PCRF 3.6

Installation Guide

© Yota 2013 12

This chapter describes brief installation overview and software and hardware requirements.

Brief Installation Overview

Yota PCRF requires installation of the two main components, which are described in the table below:

System Requirements

Hardware Requirements

Minimum cluster node hardware requirements are listed below:

Blade-architecture

Component Requirements

PCRF

Server HP BL460с G7 (2xCPU 6 Core, RAM 12Gb, 2xHDD 300Gb, 3 network cables (1 Gb/sec)

DDF

Server HP BL460с G7 (2xCPU 6 Core, RAM 12Gb, 2xHDD 300Gb, 2 network cables (1 Gb/sec)

Standalone-architecture

Component Requirements

PCRF

Server HP DL360 (2xCPU 4 Core, RAM 12 (3x4Gb), 2xHDD 146G, 3 network cables (1 Gb/sec)

DDF

Server HP DL360 (2xCPU 4 Core, RAM 12 (3x4Gb), 2xHDD 146G, 2 network cables (1 Gb/sec)

The following connections are needed to provide system clusters correct operation:

1. Connection between PCRF nodes and Huawei UGW or Procera, Cisco SCE (port 3868)

via Gx interface (network interface eth1, 100 Mb/sec).

2. Connection between DDF cluster nodes (network interface eth2, 1 Gb/sec).

3. Connection between PCRF cluster nodes (network interface eth2, 1 Gb/sec) if cluster

mode is used (not standalone node mode).

Software Requirements

Each server, where installation of Yota PCRF system will be performed to, should have Red Hat

Enterprise Linux 5.2.

Component Name Description

PCRF Component that dynamically manages access to network resources and QoS

DDF Component that is used for system geographical distribution

Information

DDF component installation is not required if Yota PCRF will be used only in one region (i.e.

as standalone PCRF cluster (node).

@ Yota 2013 13

3

PCRF Cluster Installation

Pre-installation Steps


Third-party Software Installation

Yota PCRF 3.6

Installation Guide

© Yota 2013 14

This chapter describes PCRF cluster installation process.


Make sure that server, where PCRF component will be installed to, meets the system requirements described in section "System Requirements".

PCRF Installation Files

PCRF installation files are stored on network drive in the following directory:

/mnt/JumpStart/Pcrf/Smoke/latest/

This directory contains Yota PCRF distribution packages of the latest version.

It is enough to mount the directory /mnt/JumpStart/Pcrf/Smoke/latest preserving the

directory hierarchy by adding the appropriate records to /etc/fstab.

Or before the system installation it will be needed to copy distribution packages to

/mnt/JumpStart/Pcrf/Smoke/latest directory of the server manually.

PCRF Cluster Network Settings

It is necessary to make network configuration that allow nodes of one cluster to communicate

with each other via network interface eth2 (as defined in "Connectivity scheme for LTE network"

section):

1. Configure network interface eth2 on both cluster nodes

In operating system Red Hat this operation can be performed through the package system-

config-network, which is launched by the following command:

system-config-network

In appeared dialog window Select A Device choose eth2 (eth2) line, using the Tab/Alt+Tab

for switching between the elements, and press Enter.

In Devernet Configuration window set the following parameters:

Field Value

Name eth2

Device eth2

Use DHCP Uncheck Use DHCP check box by pressing space bar

Static IP IP address of network interface that is used for interaction between nodes of one cluster

Netmask 255.255.255.0

Default gateway IP Leave blank

Save settings by pressing ok.


© Yota 2013 15

Settings example:

2. Set HOSTNAME parameter in /etc/sysconfig/network file on every node in the following

format:

HOSTNAME=<pcrf1_domain_name> on the primary node

HOSTNAME=<pcrf2_domain_name> on the secondary node

Example for St. Petersburg (primary node):

HOSTNAME=spb-pcrf1.scartel.dc

Example for St. Petersburg (secondary node):

HOSTNAME=spb-pcrf2.scartel.dc

Example for Moscow (primary node):

HOSTNAME=msk-pcrf1.scartel.dc

3. Reboot both cluster nodes by command:

reboot

4. Check if network settings that were made earlier are saved by executing command on both

nodes:

hostname

The fully qualified domain name of a node will be displayed.

5. Check if required network directories are mounted (/mnt/JumpStart) by command:

cat /etc/mtab

If the directories are not mounted execute the command:

mount –a

Information

system-config-network utility is suggestive to use, not literal.

Yota PCRF 3.6

Installation Guide

© Yota 2013 16

Supplementary Libraries Installation

Before launching Yota PCRF deploy script it is required to install supplementary libraries by command:

/mnt/JumpStart/Pcrf/Smoke/latest/pre_setup/setup_rpms.sh

Time Format Setup

Time must be set in UTC format on every cluster node. Otherwise PCRF installation won’t be successful. To set time in UTC format execute the command:

/mnt/JumpStart/Pcrf/Smoke/latest/pre_setup/set_timezone_to_utc.sh

Time format will become UTC.

Swap Disabling

1. In the file /etc/fstab comment the line , which is similar to this one:

LABEL=SW-cciss/c0d0p2 swap swap defaults 0 0

2. Execute command:

swapoff -a

Important!

If library deploy script didn’t run immediately try to launch it directly from directory

/mnt/JumpStart/Pcrf/Smoke/latest/pre_setup by command:

./setup_rpms.sh

Important

The script only sets time format and not the time itself!


© Yota 2013 17


Deploy Configuration File

There is two ways to save the deploy configuration file.

Fist:

/mnt/JumpStart/Pcrf/<release_version>/config/<pcrf_server_domain_name>

Where:

<release_verion> – release version of the PCRF system.

<pcrf_server_domain_name> – FDNQ of the server, where installation will be performed.

Example:

/mnt/JumpStart/Pcrf/3.6/config/spb-pcrf1.scartel.dc

Second:

/mnt/JumpStart/deploy/config/<realm>/<server_name_before_realm>

Where:

<realm> – server realm.

<server_name_before_realm> – a part of FDNQ of the server, where PCRF installation will

be performed, before realm part.

Example:

mnt/JumpStart/deploy/config/scartel.dc/spb-pcrf1

Parameters that are used in deploy configuration file are described in the table below:

Parameter Name Description (Default value)

SETUP_PCRF_SERVER Install components of PCRF server (Y)

Cluster mode parameters

CLUSTER_MODE Install in cluster mode (Y)

CLUSTER_NODE1 FQDN of the node, where PCRF installation will be

Important

The entire installation process should be made by the user with administrator’s rights (root user).

Important

Every PCRF node should have its own configuration file, which can be stored on this node, or

on a network drive. The configuration files of the same cluster nodes are identical. To create

configuration file for the secondary node save primary file deploy configuration file with

different name.

Deploy configuration files storage on a shared network drive is more preferable because

secondary node configuration file can be made as a reference to the primary node

configuration file (simlink). In this case, any changes that were made in the first configuration file will be reflected immediately in the other.

Yota PCRF 3.6

Installation Guide

© Yota 2013 18

performed first (primary node)

CLUSTER_NODE2 FQDN of the node, where PCRF installation will be performed second (secondary node)

CLUSTER_ID PCRF cluster ID. Must be unique within entire Yota PCRF system

PEER_ID1 Primary node ID. Must be unique within entire Yota PCRF system

PEER_ID2 Secondary node ID. Must be unique within entire Yota PCRF system

DB Information

TT_ADMIN_PASSWORD DB administrator password (for DB structure modification)

TT_USER_PASSWORD DB user password (for DB data modification)

DATABASE_TYPE Database type: TimesTen or PostgreSQL. (TT by default).

Parameters for interaction with DDF cluster

DDF_CLUSTER_ID DDF cluster ID

DDF_HOST1 FQDN of the primary DDF node, which interaction via HTTP and Diameter interfaces will be performed with.

DDF_HOST2 FQDN of the secondary DDF node, which interaction via HTTP and Diameter interfaces will be performed with

Replication Information (only if TT is used)

COMPRESS_REPLICATION Turn on/off replication traffic compression. Turned on by default. Set to T to turn off the compression

CROSSLINK_IP1 Used in case of particular crosslink interface


Other Parameters

DIAMETER_REALM Value that will be transmitted in every command in AVP Origin-Realm

PCRF_DB_SIZE PCRF database size in Mb (Megabytes) of used RAM

NO_BACKUP Install backup component on PCRF node:(Y – to install, N – not to install)

NTP_HOST

IP address of a server, which nodes time will be synchronize with. IP address is set as 10.X.150.138, where X is the regional part of external cluster node IP address (see the second numeral of external IP address)

CLEAN_RRD Clean RRD charts info (Y/N)

Example of PCRF deploy configuration file is presented below:

SETUP_PCRF_SERVER=Y

export FORCE_DB_CREATE=Y

#DB authentication information

TT_ADMIN_PASSWORD=password

TT_USER_PASSWORD=password

#Cluster mode parameters

CLUSTER_MODE=Y

CLUSTER_NODE1=spb-pcrf1.scartel.dc


CLUSTER_ID=2

PEER_ID1=21

PEER_ID2=22


© Yota 2013 19

DDF_CLUSTER_ID=0

DDF_HOST1=spb-ddf1.scartel.dc

DDF_HOST2=spb-ddf2.scartel.dc

#Other parameters

PCRF_DB_SIZE=2000

NO_BACKUP=N

NTP_HOST=10.2.150.138

DIAMETER_REALM=scartel.dc

CLEAN_RRD=Y

Installation

It is required to perform installation steps on the primary node first and only then on the secondary node:

1. Launch deploy script on the node:

/mnt/JumpStart/Pcrf/Smoke/latest/!deploy.sh

If parameter FORCE_DEPLOY=N or absent in the deploy configuration file, the following

installation confirmation message will be displayed on the screen:

Enter 'start' to continue or Ctrl+C to abort.

Enter start to continue or Ctrl+C to stop the installation process.

The installer will perform further actions automatically.

2. Check node network settings.

In the /etc/hosts file the following lines should be present:

127.0.0.1 localhost.localdomain localhost

192.168.0.1 cl.<pcrf1_server_domain_name>

192.168.0.2 cl.<pcrf2_server_domain_name>

If a particular crosslink interface is used and CROSSLINK_IP1 and CROSSLINK_IP2

parameters are set in the deploy configuration file then /etc/hosts file should contain the

following lines:


192.168.0.1 cl.<crosslink_ip1_value>


Core-files

In order to be able to identify and solve different system operating issues the following action should be performed during the installation:

The directory /cores is created, where operating system core-files will be stored.

Path to the /cores directory is set in required files.

Required core-files configuration is performed (size, etc...).

Yota PCRF 3.6

Installation Guide

© Yota 2013 20

Third-party Software Installation

All necessary third-party software components (DBMS, etc.), along with their dependencies, are

automatically installed by deploy scripts. At the same time all necessary changes are made in

operating system: directories creation, ownership and access to directories and files change, cron-tasks creation, environment variables setup, and database schema creation.

PCRF as Standalone Node

It is possible to install PCRF component as standalone node. In this case it is not needed to set

replication and secondary node information, and PostgreSQL can be used as the database

management system.

Standalone node deploy configuration file example:

SETUP_PCRF_SERVER=Y

export FORCE_DB_CREATE=Y

#DB Information



DATABASE_TYPE=PQ

#Cluster Mode Parameters

CLUSTER_MODE=N


#CLUSTER_NODE2=spb-pcrf2.scartel.dc

CLUSTER_ID=2

PEER_ID1=21

#PEER_ID2=22

DDF_CLUSTER_ID=none #0

DDF_HOST1=none #spb-ddf1.scartel.dc

DDF_HOST2=none #spb-ddf2.scartel.dc

#Other parameters

PCRF_DB_SIZE=2000

NO_BACKUP=N

NTP_HOST=10.2.150.138


CLEAN_RRD=Y

Important

PostgreSQL can’t be used for cluster mode installation.

@ Yota 2013 21

4

DDF Cluster Installation



Yota PCRF 3.6

Installation Guide

© Yota 2013 22


Make sure that server, where DDF component will be installed to, meets the system requirements described in section "System Requirements".

DDF Installation Files

See "PCRF Installation Files" section in chapter "PCRF Cluster Installation".

DDF Cluster Network Settings

It is necessary to make network configuration that allow nodes of one cluster to communicate

with each other via network interface eth2 (as defined in "Connectivity scheme for LTE network" section):

1. Configure network interface eth2 on both cluster nodes.

In operating system Red Hat this operation can be performed through a package system-

config-network, which is launched by the following command:

system-config-network

In appeared dialog window Select A Device choose eth2 (eth2) line, using the Tab/Alt+Tab

for switching between the elements, and press Enter.

In Devernet Configuration window set the following parameters:

Field Value

Name eth2

Device eth2

Use DHCP Uncheck Use DHCP check box by pressing the Space Bar

Static IP IP address of network interface that is used for interaction between nodes of one cluster

Netmask 255.255.255.0

Default gateway IP Leave blank

Save settings by pressing ok.

2. Set HOSTNAME parameter in /etc/sysconfig/network file on every node in the following

format:

HOSTNAME=<ddf1_domain_name> on the primary node

HOSTNAME=<ddf2_domain_name> on the secondary node

3. Reboot both cluster nodes by command:

reboot

4. Check if network settings that were made earlier are saved by executing command on both

nodes:

hostname

The fully qualified domain name of the node will be displayed, i.e. spb-ddf2.scartel.dс.

5. Check if required network directories are mounted (/mnt/JumpStart) by command:

cat /etc/mtab

Information

system-config-network utility is suggestive, not literal.


© Yota 2013 23

If the directories are not mounted execute the command:

mount –a

Supplementary Libraries Installation

Supplementary Libraries installation process on DDF is the same as described in section "Supplementary Libraries Installation", Chapter "PCRF Cluster Installation".

Time Format Setup

Time setup process on DDF is the same as described in section "Time Format Setup", Chapter "PCRF Cluster Installation".

Swap Disabling

Swap disabling process on DDF is the same as described in section "Swap Disabling", Chapter "PCRF Cluster Installation".

Yota PCRF 3.6

Installation Guide

© Yota 2013 24


Deploy Configuration File

Deploy configuration file must be saves as:

/mnt/JumpStart/Pcrf/<release_version>/config/<ddf_server_domain_name>

Where:

<release_verion> – release version of PCRF system.

<ddf_server_domain_name> – FDNQ of the server, where installation will be performed.

Example:

/mnt/JumpStart/Pcrf/3.6/config/spb-ddf1.scartel.dc

Parameters that are used in deploy configuration file are described in the table below:

Parameter Name Description (Default value)

SETUP_PCRF_DDF_SERVER Install components of DDF server (Y)

Cluster mode parameters

CLUSTER_MODE Install in cluster mode (Y)

CLUSTER_NODE1 FQDN of the node, where DDF installation will be performed first (primary node)

CLUSTER_NODE2 FQDN of the node, where DDF installation will be performed second (secondary node)

CLUSTER_ID DDF cluster ID. Must be unique within entire Yota PCRF system

PEER_ID1 Primary node ID. Must be unique within entire Yota PCRF system

PEER_ID2 Secondary node ID. Must be unique within entire Yota PCRF system

DB Information

Important

The entire installation process should be made by the user with administrator’s rights (root user).

Important

Every DDF node should have its own configuration file, which can be stored on this node, or

on a network drive. The configuration files of the same cluster nodes are identical. To create

configuration file for the secondary node save primary file deploy configuration file with

different name.

Deploy configuration files storage on a shared network drive is more preferable because

secondary node configuration file can be made as a reference to the primary node

configuration file (simlink). In this case, any changes that were made in the first configuration file will be reflected immediately in the other.


© Yota 2013 25

TT_ADMIN_PASSWORD DB administrator password (for DB structure modification)

TT_USER_PASSWORD DB user password (for DB data modification)

Replication Information

COMPRESS_REPLICATION Turn on/off replication traffic compression. Turned on by default. Set to T to turn off the compression



Other Parameters

DIAMETER_REALM Value that will be transmitted in every command in AVP Origin-Realm

DDF_DB_SIZE DDF database size in Mb (Megabytes) of used RAM

NO_BACKUP Perform old database backup before PCRF reinstallation. Y – not to back up the database, N – to back up.

NTP_HOST

IP address of a server, which nodes time will be synchronize with. IP address is set as 10.X.150.138, where X is the regional part of external cluster node IP address (see the second numeral of external IP address)

FORCE_DEPLOY Confirm DDF installation (Y/N)

Example of DDF deploy configuration file is presented below:

SETUP_PCRF_DDF_SERVER=Y

#TimesTen authentication information



#Cluster mode parameters

CLUSTER_MODE=Y

CLUSTER_NODE1=spb-ddf1.scartel.dc

CLUSTER_NODE2=spb-ddf2.scartel.dc

CLUSTER_ID=1

PEER_ID1=11

PEER_ID2=12

#Other parameter


DDF_DB_SIZE=2000

NO_BACKUP=N

NTP_HOST=10.2.150.138

FORCE_DEPLOY=Y

Installation

It is required to perform installation steps on the primary node first and only then on the secondary node:

1. Launch deploy script on the node:

/mnt/JumpStart/Pcrf/Smoke/latest/!deploy.sh

If parameter FORCE_DEPLOY=N or absent in the deploy configuration file, the following

installation confirmation message will be displayed on the screen:

Enter 'start' to continue or Ctrl+C to abort.

Yota PCRF 3.6

Installation Guide

© Yota 2013 26

Enter start to continue or Ctrl+C to stop the installation process.

The installer will perform further actions automatically.

2. Check node network settings.

In the /etc/hosts file the following lines should be present:


192.168.0.1 cl.<ddf1_server_domain_name>

192.168.0.2 cl.<ddf2_server_domain_name>

If a particular crosslink interface is used and CROSSLINK_IP1 and CROSSLINK_IP2

parameters are set in the deploy configuration file then /etc/hosts file should contain the

following lines:




Core-files

Core-files configuration process on DDF is the same as described in section "Core-files",

Chapter "PCRF Cluster Installation".

@ Yota 2013 27

5

Post-installation Steps

Initial DDF O&M Console Configuration

Initial PCRF O&M Console Configuration

System Clusters Correct Operation

Verification

Yota PCRF 3.6

Installation Guide

© Yota 2013 28

This chapter describes O&M Console initial configuration and system correct operation

verification steps.

Initial DDF O&M Console Configuration

O&M console is a Web interface of Yota PCRF system, which was developed for nodes state,

database and Diameter interfaces monitoring, and allows performing different types of operations and system configuration in real time.

DDF O&M is installed automatically by deploy script and available at:

http://<ddf_host>:[80]

After DDF cluster installation it is required to specify information about all system clusters and

nodes by the following steps:

1. Open DDF O&M console in a browser tab and choose the primary DDF node in the Server

List.

2. Choose Configuration -> Network Topology -> Clusters in the Operations block. Only

DDF cluster information will be displayed.

3. Click Add button in appeared Clusters table and set required parameters for all PCRF

clusters and standalone nodes:

Parameter Description

Cluster ID ID of the a cluster

Role Cluster role. Values: 1 – PCRF; 2 – SPR, 3 – PCRF with SPR, 4 – DDF; 6 – DDF with SPR, 8 – PCEF; 16 – AF; 32 – Slave PCEF

Name User-friendly cluster name

Description Cluster description

Note! Make sure that ID of each cluster of the Yota PCRF system in unique within the whole

system configuration.

Each standalone node must have cluster ID.

4. Go to Configuration -> Network Topology -> Peers. Click Add button in appeared Peers

table and set required parameters for all PCRF nodes:


Peer ID ID of a PCRF node

Cluster ID ID of the PCRF cluster which the node belongs to

Host Internal domain name of new node

Realm Realm of new cluster

Address External FQDN or external IP address of new node

Port Port which is used by node for interaction via Diameter interface (3868)

Dialect Vendor-specific Diameter protocol dialect

Auto Connect

0 – new node will wait for income connection from a server with which the node is going to interact via Diameter protocol

1 – new node will initiate connection with a server with which the node is going to interact via Diameter protocol

Mandatory Monitoring parameter. 1 – system monitoring alarms if no connection with the node; 0 – system monitoring ignores connection miss

Priority New node priority over other PCRF nodes in the system


© Yota 2013 29

Example (PCRF cluster information):

Parameter Value:

Peer ID 41

Cluster ID 4

Host vsk-pcrf1.scartel.dc

Realm scartel.dc

Address vsk-pcrf1.scartel.dc

Port 3868

Dialect 0

Auto Connect 1

Mandatory 1

Priority 0

Note! Secondary node priority must be set lower than primary node priority for each PCRF

cluster. For example, Priority=1 for secondary and Priority=0 for the primary node. 0 is the

highest priority.

5. Go to Configuration -> Network Topology ->HTTP Peers. Click Add button in appeared

HTTP Peers table and set required parameters for all PCRF nodes:


Peer ID ID of a PCRF node

HTTP address IP address of the PCRF node for receiving HTTP requests from DDF in HTTP format

HTTP port Port for receiving HTTP requests from DDF(80)

This table is used by DDF to send management HTTP requests to PCRF nodes.


PCRF O&M is installed automatically by the deploy script and available at:

http://<pcrf_host>:[80]

After PCRF cluster installation it is required to specify information about all clusters and nodes this cluster interacts with via Diameter protocol by the following steps:

1. Open PCRF O&M console in a browser tab.

2. Choose Configuration -> Network Topology -> Clusters in the Operations block. Click

Add button to add information about all PCEF clusters this cluster interact with:


Cluster ID ID of the a cluster

Role Cluster role. 8 – PCEF; 32 – Slave PCEF

Name User-friendly cluster name

Description Cluster description

3. Choose Configuration -> Network Topology -> Peers.

Check if Peer IDs of this cluster nodes are the same as were set in DDF O&M Console Peers

table.

Click Add button to add information about all cluster nodes this cluster interact with via

Diameter interface (PCEF clusters and DDF cluster):

Yota PCRF 3.6

Installation Guide

© Yota 2013 30

Example for Huawei:

Parameter Value

Peer ID 52

Cluster ID 5

Host test.ugw02.g4lab.ru

Realm g4lab.ru

Address test.ugw02.g4lab.ru

Port 3868

Priority 0

Mandatory Enabled

Enabled Enabled

Dialect Default

Auto Connect Disabled

4. Go to Configuration -> Server Settings and set default_region parameter value for this

PCRF cluster.

For example, default_region=Vasyuki.

System Clusters Correct Operation

Verification

After installation make sure that each cluster of the system operates correctly. For this purpose

the following verifications should be performed:

1. Check if all required processes are started after PCRF software setup.

2. Check if log files contain any error.

3. Check the system status in O&M console.

Correct Process Start

PCRF cluster

The following processes must operate after the system installation on PCRF server:

pcrf_core

pcrf_console

pcrf_check

drug

timesten or postgres

rx_watchdog

stat_writer

pcrf_notify

log_writer

Process operation check is performed by command:

ps ax | grep <process_name>

where <process_name> process name.

System Clusters Correct Operation Verification

© Yota 2013 31

pcrf_core

The following information will be displayed:

19375 Ss 0:00 /opt/pcrf_core/bin/pcrf_core -l debug --worker-count=3 --event-

worker-count=3 -d --sql-password=qwer

19376 S< 0:01 /opt/pcrf_core/bin/pcrf_core worker 0



19381 S 0:00 /opt/pcrf_core/bin/pcrf_core [E0] - event worker 0



19386 SN 0:00 /opt/pcrf_core/bin/pcrf_core [GS] - get subscriber

19389 S 0:00 /opt/pcrf_core/bin/pcrf_core [CT] - check state machine timers

19390 S 0:00 /opt/pcrf_core/bin/pcrf_core [SC] - send profile changes to DDF

19393 S 0:00 /opt/pcrf_core/bin/pcrf_core [PS] - send profile subscription renew

19396 S 0:00 /opt/pcrf_core/bin/pcrf_core [KS] - kill sessions

19397 S 0:00 /opt/pcrf_core/bin/pcrf_core [RX] - Rx events

19399 S 0:00 /opt/pcrf_core/bin/pcrf_core [SY] - Sync db peers info to shm

19401 S 2:17 /opt/pcrf_core/bin/pcrf_core [UP] - update process

The number of "worker" type sub-processes may differ.

DDF cluster

The following processes must operate after the system installation on DDF server:

ddf

drug

timesten

ddf_propagator

ddf_console

rx_watchdog

stat_writer

log_writer

Process operation check is performed by command:

ps ax | grep <process_name>

where <process_name> process name.

Log Messages Check

After the installation launch Log Viewer by command in the command line:

lv

and verify if the shared memory contains any error log messages.

Also check system log files, which are stored in the following directories:

/var/log/pcrf/

/var/log/roox/

System Status in O&M Console

The system status can be checked via node status indicators and sensors tree that are available

in O&M Console:

Yota PCRF 3.6

Installation Guide

© Yota 2013 32

1. Go to DDF O&M console:

http://<ddf_host>

2. Choose the first node in the Server List. This node console will be opened in a new browser

tab. In this node console make sure that all status indicators are orange and all sensors are

green:

Figure 3. Node status indicators and sensors tree

Node status indicators show the status of the node based on the sensors state of the sensors

tree.

3. Choose other nodes in the Server List of DDF O&M Console and check status indicators and

sensors.

© Yota 2013 33

6

PCRF Cluster Implementation

and Recovery

New PCRF Cluster Implementation

System Cluster Recovery after Complete

Failure

Yota PCRF 3.6

Installation Guide

© Yota 2013 34

This chapter describes new cluster implementation steps for geographically distributed

configuration and the system recovery actions after complete failure.

New PCRF Cluster Implementation

Cluster implementation steps are described below:

1. Install PCRF software on both nodes (see chapter «PCRF Cluster Installation»).

2. Provision to primary node information about all dictionaries used in the system (services

dictionary info, accumulators dictionary info, threshold schemes dictionary info, attributes

dictionary info). The information can be taken from DDF database.

Dictionaries information provisioning is performed via SPR Configuration Interface. (See

"Yota PCRF 3.6 SPR Configuration Interface" document for more details).

HTTP request example to add service information to the service dictionary:

http://pcrf.host.example.com/spr/conf/addServiceInfo?id=www&name=WWW_Default_ser

vice&description=Basic_service_with_default_QoS_parameters

3. Set new PCRF cluster information in DDF O&M Console. Console is available at:

http://<ddf_host>

Required cluster information setup steps are described in section "Initial DDF O&M Console

Configuration".

4. Add information about subscriber profiles (IMSI) to DDF database that will be activated in

this new region.

When a subscriber attaches to the Network in new region his profile will be requested from

DDF.

Important!

Make sure that new cluster ID (Cluster ID) and new cluster node IDs (Peer IDs) that

are set in DDF O&M Console are identical to Cluster ID and Peer IDs that are set in new PCRF O&M Console.

http://pcrf.host.example.com/spr/conf/addServiceInfo?id=www&name=WWW_Default_service&description=Basic_service_with_default_QoS_parameters

http://pcrf.host.example.com/spr/conf/addServiceInfo?id=www&name=WWW_Default_service&description=Basic_service_with_default_QoS_parameters

© Yota 2013 35

System Cluster Recovery after Complete

Failure

For PCRF cluster restoration after the complete failure a backup copy of PCRF database is used,

which allows to restore information about all subscribers and system settings of the given

region.

Information

Backup and recovery procedures are described in the "Yota PCRF 3.6 Backup and Recovery" document.

Documents

Yota PCRF - BME MIK LABORATÓRIUMzfaigl/QoS/doc/freePCRF... · Yota PCRF is a software product that allows managing access level to network resources and quality of services in different