Sample Configuration of PGW using SNMP EMS

1. Install PGW RPM

Refer to EPC installation document.

2. Check service status

service epgw status
[epgw haf] Running
[epgw] Running
[edataplane] Running

HAF, epgw binary and Dataplane service should be running.

3. Check ports
netstat -nap | grep pgw
Sample Configuration:
Here pgw is running on the floating IP 192.168.9.88 and the physical machine IP is
192.168.9.34. SNMP connection is established on the port 705

tcp 0 0 192.168.9.88:4110 0.0.0.0:* LISTEN 13751/pgw

tcp 0 0 192.168.9.88:3868 0.0.0.0:* LISTEN 13751/pgw
tcp 0 0 192.168.9.88:3871 0.0.0.0:* LISTEN 13751/pgw
tcp 0 0 192.168.9.88:4521 0.0.0.0:* LISTEN 13751/pgw
tcp 0 0 192.168.9.88:4521 192.168.9.33:55299 ESTABLISHED
13751/pgw
tcp 0 0 192.168.9.34:38160 192.168.9.34:705 ESTABLISHED
13751/pgw
udp 0 0 127.0.0.1:15100 0.0.0.0:* 13751/pgw
udp 0 0 192.168.9.88:6666 0.0.0.0:* 13751/pgw
udp 0 0 192.168.9.88:6669 0.0.0.0:* 13751/pgw
udp 0 0 192.168.9.88:53 0.0.0.0:* 13751/pgw
udp 0 0 192.168.9.88:56 0.0.0.0:* 13751/pgw
udp 0 0 192.168.9.88:8505 0.0.0.0:* 13751/pgw
udp 0 0 192.168.9.88:2123 0.0.0.0:* 13751/pgw
udp 0 0 192.168.9.88:7124 0.0.0.0:* 13751/pgw
udp 0 0 192.168.9.88:7127 0.0.0.0:* 13751/pgw
raw 4106496 0 0.0.0.0:1 0.0.0.0:* 7 13751/pgw
raw 0 0 0.0.0.0:132 0.0.0.0:* 7 13751/pgw
raw 0 0 0.0.0.0:132 0.0.0.0:* 7 13751/pgw
raw 0 0 :::132 :::* 7 13751/pgw
unix 2 [] DGRAM 74312 13751/pgw

The following snapshots depicts a sample configuration of PGW required for a Initial
Attach.
2. Discover epgw
SNMP process should be running and pgw subAgent should be connected to SNMP
Agent on 705 port

IP Address: Floating Address of PGW(192.168.9.88)

User Name: authPgwMD5
Context Name: As given from pgw_discoveryfile(PGW)
Security Level: AuthNoPriv
Auth Protocol: MD5
Auth Password: authPgwMD5
Node should be successfully added. Now go to Configuration tab and configure the node.

NOTE : While configuring, action is Apply and Restart and in some, action
is Apply. Please make sure when the configurations is done initially, the
Apply and Restart action can be avoided and Apply action can be chosen for
each configuration. On configuring all the relevant parameters, PGW restart
can be given at the end.
3. MCC MNC Configuration

Click on Configuration ->Peer Discovery -> MCC MNC Config

Click “Add Row” and enter MCC and Number of MNC digits value.

A sample with MCC 311 and 3 digits in MNC is show below. You can add multiple
PLMNs.

Click Actions->Apply.
4. PDN Configuration

Click on Configuration ->APN-UE Settings ->PDN Settings

Click “Add Row” and enter the values.

Provide an unique PDN Index for each row.

Give any user-defined name as PDN Name(say pertsol_pdn).
Provide the Ethernet interface(say em1).
Give the VLAN ID. The PGW creates a VLAN for data. The range of VLAN is 1...4096.
If we give the VLAN ID as 4097 and above then there is no need to create VLAN otherwise
VLAN creation is required. So it is recommended to give this VLAN ID above 4096 i.e
4097 and above.
Give a routing table index(any user defined value in between 3-254)(say 121)
Provide same one free IP for TUN device which will be used for data from the external
PDN.
Enter the IP Address of the Gateway ( IP of external PDN).

Click Actions->Apply
5. NAS Configuration

Click on Configuration ->APN-UE Settings ->NAS Settings

Click “Add Row” and enter the values.

Provide an unique NAS Index for each row.

Give any user defined NAS name(say pertsol_nas)
Allocation Schemes could be IP-Pool or DHCP. Currently we are using IP-Pool only.
Select a PDN from the list of configured PDNs.
Provide a Primary(196.1.105.47 for PERTSOL) and Secondary DNS(196.1.105.16 for
PERTSOL) address to resolve DNS query for Internet access.
Provide a UE Start and End IP Address range. More than one ranges can also be given. The
PGW shall allocate IPs for the UE from this pool.
Provide V4 DP-Ids. Pick a GTP-U Index(This will be the count of PGW dataplanes
configured)
Give user-defined Downlink and Uplink maximum allocated Rate(default is 1024)

Click Actions->Apply.
6. APN Configuration
Click on Configuration ->APN-UE Settings ->APN Settings
Click “Add Row” and enter the values.

Provide an unique APN Index for each row.

Enter the APN name along with OI & NI. i.e. APN_NAME.mncxxx.mccyyy.gprs
For eg. vzwinternet.mnc480.mcc311.gprs
Select NAS name which is configured in Step 5.
Enter DS ( DS or DSCP is a field in an IP packet that enables different levels of service to
be assigned to network traffic) values for all the QCI values(0 is the default value)

Policy Type can be Static or Dynamic. Static means the policy rules will be picked from
PCEF function of PGW. In case of dynamic policy type, PCRF will provide the policy rule
values to PGW.

The snapshot given below shows that policy type is chosen as Static policy. In this case,
please follow from step 7 to 12.

NOTE : Step 10 and 11 is only to be configured if metering method shown in the snapshot
given in Step 12 is set to NO_CHARGING.

Provide values for APN-AMBR-UPLINK (in Kbps) & APN-AMBR-DOWNLINK (in

Kbps), APN Restriction value(say 1), Subscription Flag whether required or not and Bearer
Modification Flag as per the operator strategy.

Click Actions->Apply.

In case of dynamic policy, where the policy rules are to be pushed from PCRF to PGW,
Steps 19 to 21 should be strictly followed. Please do not configure anything in Data Path
Filter Settings, Policy Rule Name, Policy Rule Set, Charging Characteristics (Steps 7,8,
9 and 12) in this case.

NOTE : The policy type should be picked as Dynamic when the policy rules are to be
provided by PCRF.
7. Data Path Filter Settings
Add Filters for both upload and download directions. The two figures below show the
configuration to be done ul and dl filters.
Click on Configuration ->Policy and Charging Setting ->Data Path Filter Setting
Click “Add Row” and enter the values.

Provide unique APN Filters Configuration Index for each row.

Create a User defined value. Make two separate filters for Downlink and Uplink(say dl
and ul)
In Filter Type provide value 32 for protocol, 1 for source IP, 2 for destination IP, 4 for
source port and 8 for destination port.
In our sample, the filters are not based on any criteria. So all fields are left blank.
Click Actions->Apply.

Fig: UL Filter
Fig: DL Filter
Note:- For UE initiated dedicated bearers create two different filters for one for dedicated
uplink(ded_ul) and dedicated downlink(ded_dl) and kept their protocol values as 1.
8. Policy Rule Name
Click on Configuration ->Policy and Charging Setting ->Policy Rule Name
Click “Add Row” and enter the values.

Provide unique APN PCC Index for each row.

Provide a user-defined Policy Rule Name(say pertsol_prn)
Give Precedence( say 1) (PCEF selects SDF based on Precedence value of PCC rules)
Pick UL Filter & DL Filter in case only a default bearer is present.

NOTE: When one or more dedicated bearer is present, the UL filter and DL Filter in
default policy should be left blank.

Metering method could be “Volume Based/Both” for charging of a particular user.

Enter the Uplink and Downlink MBR & GBR.
Enter the QCI value(say 5).
Select priority value(say 9). Provide ARP-Vulnerability & ARP-Preemptabilty(say as
True)
These must be the same as that configured in HSS.
Time can be left blank. Flow Status should be enabled, otherwise data will not flow.
Monitoring Key, Service ID and Rating Group can be left blank.

Service ID (service identifier) is used to identify a service or service component the SDF
relates SDF filter(s)

Monitoring key identifies a monitoring control instance that shall be used for usage
monitoring control of the SDFs.

Rating group define whether online and offline charging interfaces are used, what is to be
metered in offline, on what level the PCEF shall report the usage related to the rule, etc.

Click Actions->Apply.

Note:- For Network Initiated Dedicated Bearers

(a) 2 PRNS are to be created
b) Default 1st PRN Precedence= 2, ARP= 9, QCI=7, PV=T, PC=T, UL, DL (No Filter)
c) Dedicated 2nd PRN Precedence=1, ARP=7, QCI=4, PV=F, PC=F, UL,DL 2 Filters

For UE Initiated Dedicated Bearers

(a) 2 PRNS are to be created
b) Default (As mentioned above)

NOTE :The below figure is just given for reference. Please enter the above values to
create multiple bearers against an IP-can session.
c) Dedicated (As mentioned above)
9. Policy Rule Set
Click on Configuration ->Policy and Charging Setting ->Policy Rule Set
Click “Add Row” and enter the values.

Provide unique Policy Rule Set for each row.

Give a user-defined Policy Rule Set Name(say pertsol_prs). Associate Policy Rules with
this Policy Rule Set. Here in example pertsol_prs in associated with pertsol_prn

Note:- For UE Initiated Bearers make 2 sets of PRS

1) Set 1- Default
2) Set 2- Dedicated

For Network Initiated Bearers create one set of PRS

1) Default PRN
2) Dedicated PRN

Click Actions->Apply.
10. Online Charging System

Click on Configuration ->Policy and Charging Setting ->Online Charging Setting

Click “Add Row” and enter the values.
Provide unique OCS Index for each row.
Enter any user-defined OCS Name(say ocs). Provide Primary OCS Server Address is the
aaa://fqdn format only. Secondary OCS Server Address can be left blank.

Click Actions->Apply.
11. Offline Charging System

Click on Configuration ->Policy and Charging Setting ->Offline Charging Setting

Click “Add Row” and enter the values.
Provide unique OFCS Index for each row.
Enter any user-defined OFCS Name(say cdf). Provide Primary OFCS Server Address is
the aaa://fqdn format only. Secondary OCS Server Address can be left blank.
Limit Interval(3600) and Limit Volume(10000) values will be taken as default.

Click Actions->Apply.
12. Charging Characteristics

Click on Configuration ->Policy and Charging Setting ->Charging Characteristics

Click “Add Row” and enter the values.
Provide unique CC Index for each row.
Enter the Charging Characteristics value as 1. This must be the same value as that
configured in IMSI APN config of HSS.
Select network type as EUTRAN
Pick an APN value. Provide a QCI.
Select Info Type as Default (this value is to be set as Specific for every other Charging
Characteristic apart from the first one)
Select the policy rule set

Select the metering method as Online, Offline, Both or No-Charging as per the operator
requirements.
If Online selected, pick online charging Info which is configured before.
If Offline selected, pick offline charging Info which is configured before.
If Both selected provide both.
If none of the above is to be chosen, pick No-charging.

Click Actions->Apply.

Note: - For UE Initiated Bearers, create a single Charging Characteristic Set with two sets
of PCCRules(PRN) value

For Network Initiated Bearers

Create a separate Charging Characteristic Set with same CC value and different
PCCRules(PRN) value for
1) Default
2) Dedicated
13. Traces and Alarms

To change the trace level goto Advanced->System Configuration->Trace

Settings
The Trace Levels of Trace Types Info, Error, protocol and IPC_dumps can be
changed individually.
Trace levels can be changed to No Trace, Brief, Detailed, Debug.

To

enable or disable the Data Path Trace

Navigate to Advanced->System Configuration-> DP Trace
14. Startup Option

Navigate to Home->Advanced->System Configuration->Startup Config

Factory Settings Mode, Persistence Mode and Checkpoint Mode are available
in drop-down menu. Select a mode and Apply.
CAUTION : The Factory-Settings configuration has to be specifically done, only when the
existing configuration is non-functional and the user wants to make the configuration
afresh. Factory Settings has to be applied when the user is absolutely sure of removing the
already made configuration.
15. Checkpoint Creation and Stats Reset

Navigate to Home->Monitoring->System->System Information

Version denotes the PGW version being used. System state denotes the current
state of the system. In Log File Path we can give the path where we want the
log to be formed. Default path is /opt/lte/epgw/log.
Checkpoint button will create the backup.
Reset Button will clear all the Performance Stats.
16. DNS Configuration

16.1 Self Configuration

Navigate to Home->Advanced->DNS Configuration->Self Configuration
Give the IPv4 address and port.
PGW Self Address is the default Self IPv4 Address and 53 is the default Self
Port.
16.2 Peer Configuration
Navigate to Home->Advanced->DNS Configuration->Peer Configuration
Give the Peer IPv4 Address and Peer Port.
17. Subscriber Trace

Ensure SUBSCRIBER_TRACE flag in epgw_limitsfile to be TRUE

i.e., this flag is enabled while creating the pgw_licensefile.

Navigate to
Home->Advanced->Subscriber Trace->System Configuration
Default IPv4 Address and Eth Interface and port base is given.
Trace Collection Entity address has to be given in IPv4 Address 1 field.
Optionally TCE Address 2 can also be given.
Also, the default port (10085) in TCE Port field has to be given. The same port
should also be given in neIp.conf file while running the “tce” executable.
18. Lawful Interception

LI_ENABLED=TRUE &
PERTSOL_LIS_ENABLED=TRUE in epgw_limitsfile (this is to be set as TRUE while
creating pgw_licensefile)

NOTE : The configuration given in Section 18.2 should only be configured if

PERTSOL_LIS_ENABLED=FALSE and LI_ENABLED=TRUE in epgw_limitsfile i,e,
STUB_LIS is enabled when licensefile is generated.

18.1 LI Self Config

Navigate to Home->Advanced->Lawful Interception->LI Self Config

The default Self Port in this case 4110.
Provide the values and Actions-> Apply
18.2 LI Peer Config

Navigate to Home->Advanced->Lawful Interception->LI Peer Config

Provide the values and Actions-> Apply
19. Diameter Interface Setting

Navigate to Home->Configuration->PGW System Settings->Diameter

Interface Setting.

Provide Primary Host Name as PGW.

Provide Realm Name epc.mnc480.mcc311.3gppnetwork.org.
Transport Protocol should be the protocol which PCRF supports i.e., TCP in
the present scenario.

The interface name will be automatically fetched from PGW configuration

file. In the snapshot given below, the interface name is eth0.

NOTE : The mcc and mnc depends on the PLMN of the home network. The
PLMN in this case is 311480.

Click Actions->Apply.
20. Diameter Routing

Navigate to Home->Configuration->Peer Discovery->Diameter Routing.

Click “Add Row” and enter the values.

Provide an unique Diameter Routing Index for each row.

Provide the Diameter URI as

aaa://pcrf.epc.mnc480.mcc311.3gppnetwork.org:3868;transport=tcp;pr
otocol=diameter
The Diameter URI is dependent on the configuration defined in Step 19.
The protocol between PGW and PCRF is diameter.
The transport protocol is TCP.
Give Realm Name as epc.mnc480.mcc311.3gppnetwork.org.

NOTE : The mcc and mnc depends on the PLMN of the home network. The
PLMN in this case is 311480.

Click Actions->Apply.
NOTE : Please make sure the same PLMN as given in Step 19 is being given
here as well. The PLMN is 311480.
21. Static DNS Config

Navigate to Home->Configuration->Peer Discovery->Static DNS Config.

Click “Add Row” and enter the values.

Provide an unique DNS Config Index for each row.

Provide Host Name as pcrf.epc.mnc480.mcc311.3gppnetwork.org.

Also provide the floating IP address of PCRF in IP address field.

NOTE : The mcc and mnc depends on the PLMN of the home networks. The
PLMN in this case is 311480.

Click Actions->Apply.
Section 2 Performance

Viewing PGW Performance or Statistics:

This section contains the mechanism to check the current statistics for resource, procedure,
traffic, system and debug.
Click on Performance.
Click on On-Demand Statistics. It displays a tree of MME Statistics, SGW Statistics,
PGW Statistics and PCRF Statistics.
Click PGW Statistics from tree view.
Click text view PGW. It will display Monitoring which has Traffic Model Statistics and
Debug Statistics.
To view Traffic Model Statistics click on it. It will display the Stats Report.
To view Debug Statistics click on it. It will display Subscriber Interface Stats, GTPv2
Interface Stats, OCR Interface Stats, CDF Interface Stats etc. Click anyone of them to see
the Transmitted, Received and Dropped Statistics.
For example, click Debug Statistics ->Diameter Interface Stats to view the Diameter
Interface Statistics values.
Section 3 Alarms

The snapshot shows are various Alarms being raised at PGW.

Click the Event Details to view all the alarm details.
Refer to Alarm Code and Alarm Description fields.
From Alarm Description Alarm Code can be taken out.