SJ-20110222160920-007-ZXUN xGW (V4.10.21) Extendable GateWay PDSN Data Configuration Guide

ZXUN xGWeXtendable GateWay

PDSN Data Configuration Guide

Version: V4.10.21

ZTE CORPORATIONNO. 55, Hi-tech Road South, ShenZhen, P.R.ChinaPostcode: 518057Tel: +86-755-26771900Fax: +86-755-26770801URL: http://ensupport.zte.com.cnE-mail: [email protected]

LEGAL INFORMATIONCopyright © 2011 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties. Any reproduction or

distribution of this document or any portion of this document, in any form by any means, without the prior written

consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by

contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE

CORPORATION or of their respective owners.

This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions

are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,

title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the

use of or reliance on the information contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications

covering the subject matter of this document. Except as expressly provided in any written license between ZTE

CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter

herein.

ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.

Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision History

Revision No. Revision Date Revision Reason

R1.0 2011-04-06 First Edition

Serial Number: SJ-20110222160920-007

Publishing Date: 2011-04-06(R1.0)

ContentsAbout This Manual ......................................................................................... I

Chapter 1 PDSN Introduction.................................................................... 1-11.1 Basic Function of the PDSN................................................................................ 1-1

1.2 Application of the PDSN ..................................................................................... 1-2

1.3 Overall Description of the Data Configuration ....................................................... 1-3

1.3.1 Basic Contents and Flow of Data Configuration.......................................... 1-3

1.3.2 Data Configuration Methods...................................................................... 1-7

1.3.3 Precautions for Data Configuration ............................................................ 1-8

1.3.4 Data Configuration References ................................................................. 1-8

1.4 ZXPDSS Network Planning................................................................................. 1-9

Chapter 2 Configuration of the Local Office Information ....................... 2-12.1 Loading License................................................................................................. 2-1

2.2 Basic Configuration ............................................................................................ 2-3

2.2.1 Configuring the Time Zone........................................................................ 2-3

2.2.2 Configuring the Time ................................................................................ 2-4

2.2.3 Configuring the VRF................................................................................. 2-5

2.2.4 Validating the Configuration ...................................................................... 2-7

2.2.5 Showing the Configuration Information ...................................................... 2-7

2.3 Board Configuration ........................................................................................... 2-9

2.3.1 Configuring the CPU Group Information..................................................... 2-9

2.3.2 Adding a CPU ........................................................................................ 2-10

2.3.3 Configuring the SLB ............................................................................... 2-12

2.3.4 Configuring the CU Daughter Card .......................................................... 2-14

2.4 IP Protocol Stack Configuration......................................................................... 2-17

2.4.1 Configuration Flow of IP Protocol Stack ................................................... 2-17

2.4.2 Querying the Real Interface Status .......................................................... 2-18

2.4.3 Configuring Basic Information of the Real Interface .................................. 2-19

2.4.4 Configuring the Default Route ................................................................. 2-21

2.4.5 Configuring a Non-default Route ............................................................. 2-21

2.4.6 Configuring the VRF Bound with the Sub-interface ................................... 2-22

2.5 Configuration of Interconnection Between the PDSN and the OCS ...................... 2-24

2.5.1 Configuration Flow of Interconnection Between PDSN and OCS ............... 2-24

2.5.2 Configuring the Adjacent Node................................................................ 2-25

I

2.5.3 Configuring the Local Node..................................................................... 2-27

2.5.4 Configuring the Diameter Link ................................................................. 2-28

2.5.5 Configuring the TCP Link........................................................................ 2-29

Chapter 3 Configuration of the Interfaces................................................ 3-13.1 Interface Introduction.......................................................................................... 3-1

3.2 Configuration of Interconnection Between the PDSN and the PCF......................... 3-1

3.2.1 Configuration Flow of Interconnection Between PDSN and PCF.................. 3-1

3.2.2 Configuring the Real IP Address of the RP Interface................................... 3-2

3.2.3 Configuring the Security Association of RP Interface .................................. 3-3

3.3 Configuration of the Interconnection Between the PDSN and the HA ..................... 3-5

3.3.1 Configuring the FA-HA Security Association............................................... 3-5

3.3.2 Configuring the FA-HA Security Association IP Segment ............................ 3-6

3.4 Configuration of Interconnection Between the PDSN and the AAA......................... 3-9

3.4.1 Configuration Flow of Interconnection Between PDSN and AAA.................. 3-9

3.4.2 Configuring the AAA Profile Name............................................................. 3-9

3.4.3 Configuring the RADIUS Server IP Address ............................................. 3-10

3.4.4 Configuring the IP Address of AAAC.........................................................3-11

3.4.5 Configuring the Shared Key .................................................................... 3-13

3.4.6 Configuring the NAS Attribute ................................................................. 3-14

3.5 Configuration of Interconnection Between the PDSN and the LNS....................... 3-15

3.5.1 Configuration Flow of Interconnection Between PDSN and LNS................ 3-15

3.5.2 Configuring the Homing Domain of the LAC ............................................. 3-15

3.5.3 Configuring the Default LAC Address ...................................................... 3-16

3.5.4 Configuring the Non-default LAC Address................................................ 3-18

Chapter 4 Configuration of the Services.................................................. 4-14.1 Configuration of the IP Pool ................................................................................ 4-1

4.1.1 Configuration Flow of the IP Pool .............................................................. 4-1

4.1.2 Creating an IP Pool .................................................................................. 4-2

4.1.3 Configuring the VRF of the IP Pool ............................................................ 4-3

4.1.4 Configuring the IP Segment of the IP Pool ................................................. 4-4

4.1.5 Setting Priority of the IP Pool..................................................................... 4-5

4.1.6 Setting External IP Pool Type.................................................................... 4-6

4.2 Configuration of the Domain................................................................................ 4-7

4.2.1 Configuration Flow of the Domain.............................................................. 4-7

4.2.2 Configuring the Domain Name .................................................................. 4-8

4.2.3 Configuring the IP Address of the Active DNS ............................................ 4-9

4.2.4 Configuring the IP Address of the Standby DNS....................................... 4-10

II

4.2.5 Configuring the IP Pool of a Domain .........................................................4-11

4.2.6 Configuring the AAA Profile for Authentication.......................................... 4-12

4.2.7 Configuring Realm Charging Mode.......................................................... 4-13

4.2.8 Configuring the AAA Profile for Domain Charging..................................... 4-14

4.3 Configuration of the Local Authentication Attributes ............................................ 4-15

4.3.1 Introduction to Types of Local Authentication............................................ 4-15

4.3.2 Configuring the Local Authentication Attributes of the SIP ......................... 4-16

4.3.3 Configuring the Local Authentication Attributes of the L2TP ...................... 4-17

4.4 Configuration of the MIP Service ....................................................................... 4-19

4.4.1 Configuration Flow of the MIP Service ..................................................... 4-19

4.4.2 Configuring the FA-HA Security Association............................................. 4-19

4.4.3 Configuring the COA Address ................................................................. 4-20

4.4.4 Configuring the MIP Parameter ............................................................... 4-21

4.5 Configuration of the Lawful Interception Service ................................................. 4-26

4.5.1 Configuration Flow of the Lawful Interception Service ............................... 4-26

4.5.2 Configuring the Basic Information of the PDSN Lawful Interception ........... 4-27

4.5.3 Configuring the Interception Types .......................................................... 4-29

4.5.4 Configuring the Remote Gateway Address of the Lawful Interception......... 4-30

4.5.5 Configuring the Remote End Types of the Lawful Interception ................... 4-31

4.5.6 Configuring the Gateway Address and the Port of the Interface X3 ............ 4-32

4.5.7 Configuring the Local Port of the Interface X3 .......................................... 4-33

4.5.8 Configuring the Local Media Plane IP Address of the Interface X3............. 4-34

4.5.9 Configuring the Link Detection Parameters of the Interface X3 .................. 4-35

4.6 Configuration of the Offline Charging ................................................................. 4-36

4.6.1 Configuration Flow of the Offline Charging ............................................... 4-36

4.6.2 Configuring Offline Charging Modes ........................................................ 4-36

4.6.3 Setting the Offline Charging Threshold .................................................... 4-37

4.6.4 Setting CDR Filtering.............................................................................. 4-38

4.6.5 Setting the Offline Charging Tariff ............................................................ 4-39

4.7 Configuration of the Online Charging ................................................................. 4-40

4.7.1 Configuration Flow of the Online Charging ............................................... 4-40

4.7.2 Setting the Online Charging Diameter Adjacent Office .............................. 4-42

4.7.3 Setting the Online Charging Quota Validation Time................................... 4-42

4.7.4 Setting the Online Charging Quota Holding Time...................................... 4-43

4.7.5 Setting the Online Charging Number Analysis Route Function................... 4-44

4.7.6 Setting Online Charging Credit Control Fault Handling Policies ................. 4-45

4.7.7 Setting Online Charging Defaulting Policies ............................................. 4-46

III

4.7.8 Setting Online Charging Redirect Address ............................................... 4-47

4.7.9 Enabling/Disabling Online Charging Keywords ......................................... 4-47

4.8 Configuration of the DPI.................................................................................... 4-48

4.8.1 Introduction to the DPI Function .............................................................. 4-48

4.8.2 Configuration Flow of DPI ....................................................................... 4-49

4.8.3 Configuring a DPI Rule ........................................................................... 4-51

4.8.4 Configuring FTP Server .......................................................................... 4-53

4.8.5 Deploying DPI Files................................................................................ 4-56

4.8.6 Enabling/Disabling xDPI Control.............................................................. 4-58

4.9 Configuration of the Policy ................................................................................ 4-58

4.9.1 Configuration Flow of Policy.................................................................... 4-58

4.9.2 Configuring the Local Charging Rules...................................................... 4-59

4.9.3 Configuring the Local Control Rule .......................................................... 4-62

4.9.4 Configuring the Local Charge Control Policy ............................................ 4-65

4.9.5 Configuring the Service Classification Map............................................... 4-68

4.10 Configuration of the PCC ................................................................................ 4-69

4.10.1 Configuration Flow of PCC.................................................................... 4-69

4.10.2 Enabling/Disabling PCC Function .......................................................... 4-70

4.10.3 Configuring PCC Default Service Name................................................. 4-71

4.10.4 Setting the PCC Access Type................................................................ 4-72

4.10.5 Configuring Rate Control Policy............................................................. 4-73

4.10.6 Configuring MBR Mapping .................................................................... 4-73

4.10.7 Configuring the PCC Parameter ............................................................ 4-74

4.11 Configuring SNMP Alarm Management ............................................................ 4-77

Figures............................................................................................................. I

Tables ............................................................................................................ III

Glossary ........................................................................................................IX

IV

About This ManualPurpose

This manual provides procedure and guidelines for configuration method of the ZXUNPDSN.

Intended Audience

This manual is intended for engineers and technicians who perform configuration activitiesthrough ZXUN PDSN command terminal.

Prerequisite Skill and Knowledge

To use this manual effectively, users should have a general understanding of wirelesstelecommunications technology. Familiarity with the following is helpful:

l The ZXUN PDSN system and its various components.l Local operating procedures.l Interfaces and protocols.

What Is in This Manual

This manual contains the following chapters:

Chapter Summary

Chapter 1, PDSN Introduction

Introduces the basic function and application of the PDSN, basic

contents of the data configuration, configuration methods, and

PDSS network planning.

Chapter 2, Configuration of the

Local Office Information

Introduces the configuration methods and commands about local

office information.


Interfaces

Introduces the configuration methods and commands about the

interfaces.


Services

Introduces the configuration methods and commands about

the services.

Glossary Lists the glossary in this manual.

FCC Compliance Statement

This device complies with part 15 of the FCC Rules. Operation is subject to the followingtwo conditions.

1. This device may not cause harmful interference.2. This device must accept any interference received, including interference that may

cause undesired operation.

I

Changes or modifications not expressly approved by the party responsible for compliancecould void the user's authority to operate the equipment.

Conventions

ZTE documents employ the following typographical conventions.

Typeface Meaning

Italics References to other Manuals and documents.

“Quotes” Links on screens.

Bold Menus, menu options, function names, input fields, radio button names, check boxes,

drop-down lists, dialog box names, window names.

CAPS Keys on the keyboard and buttons on screens and company name.

Note: Provides additional information about a certain topic.

Checkpoint: Indicates that a particular step needs to be checked before proceeding

further.

Tip: Indicates a suggestion or hint to make things easier or more productive for the

reader.

II

Chapter 1PDSN IntroductionTable of Contents

Basic Function of the PDSN .......................................................................................1-1Application of the PDSN.............................................................................................1-2Overall Description of the Data Configuration .............................................................1-3ZXPDSS Network Planning ........................................................................................1-9

1.1 Basic Function of the PDSNFunction DescriptionPacket Data Serving Node (PDSN) is the access gateway connecting the Radio Network(RN) and the Packet Data Network (PDN), and provides services of accessing the Internetor Intranet for cdma2000 mobile stations. Meanwhile, the PDSN cooperates with the AAAto authenticate and charge the users.

Hardware PlatformThe PDSN adopts ZXUN xGW of ZTE as the hardware platform, and uses an architectureof separating the service plane from the management & control plane.

Product Featuresl High reliability

The PDSN provides a design of 99.999% reliability, and has multiple redundancyoperation modes. This ensures the un-interruption of system services to the greatestextent. Besides, the PDSN provides multiple built-in security control policies to makesure that the system can run properly even under external attacks.

l Easy maintainability

The PDSN provides multiple methods to record and feed back the current runningstatus of the system, such as performance statistics, fail observer, and alarms. Whenthe system functions improperly, the PDSN can analyze and locate the faults easilyand quickly.

l High performance

PDSN provides a strong media plane stream processing capability, which cansatisfy the increasing requirements on the packet network traffic caused by the greatimprovement of mobile broadband network user access rate.

l Environmental protection

1-1

SJ-20110222160920-007|2011-04-06(R1.0) ZTE Proprietary and Confidential

ZXUN xGW PDSN Data Configuration Guide

Service running abides by the service usage habits of the customers, realizes that theequipment power consumption changes according to the system traffic, and performsdynamic power control on the basis of the loading according to the system runningload.

1.2 Application of the PDSNNetwork Position

Position of the PDSN in the mobile network is as shown in Figure 1-1.

Figure 1-1 Schematic Diagram of PDSN in the Mobile Network

Composition

Packet Data Switching System (PDSS) is composed of the following NEs.

l Packet Data Service Node (PDSN)

1-2


Chapter 1 PDSN Introduction

As the FA, the PDSN is the access gateway connecting the radio network and thepacket data network, and provides packet data access services of accessing theInternet and the Intranet for cdma2000 mobile stations.

l Home Agent(HA)

The HA provides not only the accessing of mobile IP services, but also the contentcharging functions.

l Authentication, Authorization and Accounting (AAA)

AAA is responsible for the authentication, authorization, and charging for packet dataservices.

l Access Network Authentication, Authorization and Accounting (AN-AAA)

The AN-AAA adopts the RADIUS server architecture; it undertakes theaccess-network level authentication function of the EV-DO network, andaccomplishes the identity validity verification of EV-DO user terminals, that is theAN-Level certification. Meanwhile, the AN-AAA accomplishes the account-openingmanagement function of EV-DO user terminals.

l Network Element Management System (EMS)

The EMSis composed of the operation & maintenance server and the operation &maintenance client, and it is in charge of the maintenance and management of thewhole PDSS.

Product Applications

In the PDSS, each logical NE can adopt the products developed by ZTE.

l The PDSN adopts ZXUN PDSN.l The HA adopts ZXUN HA.l The AAA and AN-AAA adopt ZXUN UniA.l The EMS adopts NetNumen.

1.3 Overall Description of the Data Configuration

1.3.1 Basic Contents and Flow of Data Configuration

Configuration Method

ZXUN PDSN uses the data product ZXUN xGW developed by ZTE as the hardwareplatform, and uses the command line online configuration method; therefore, the overalldata configuration method is similar to the configuration mode of the data communicationequipment. Perform the following steps to go to the PDSN data configuration mode.

1. On the MPU board debugging terminal, Telnet to the MPU board by the SecureCRTsoftware. When the prompt xGW> appears, the Telnet succeeds.

1-3



2. Enter the login username as en and password as zxr10 under the xGW>, the promptbecomes xGW#, indicating that you have logged in to the MPU board.

Note:

To create a new user name as zte, a password as zte, and the operation authority asthe maximum level (15), use the command as: xGW (config)#username zte passwordzte privilege 15

3. Type configure terminal under the xGW#, and the prompt becomes xGW(config)#,indicating that you have entered the configuration management mode.

4. Type xgw under the xGW(config)#, the prompt becomes xGW(config-xgw)#, indicatingthat you have entered the xGW data configuration directory.

5. Type pdsn under the xGW(config-xgw)#, the prompt becomes xGW(config-xgw-pdsn)#, indicating that you have entered the PDSN data configuration directory. Underthis mode, type the configuration command to configure the PDSN data.

Basic Operations of Command Line

Type configure terminal under xGW# to go to the configuration management mode, andthe prompt becomes xGW(config)#. Basic operation commands in this mode are as listedin Table 1-1.

Table 1-1 Command Operation Commands

Command Example Description

?

Lists the commands that can be carried out under current directory. If a ?is added after a command, the online help information of this command is

shown.

TabAutomatically supplements the incomplete command, and saves typing

operations.

Show Used to show the configured commands.

Exit Exits current directory and goes back to the upper-level directory.

no Deletes the configuration.

list Lists the configurations in the current directory.

1-4



Note:

To write the configuration commands into the configuration files, type the command writein xGW#; if you don't carry out the command write, you will lose all configuration data afterthe MPU board is restarted.

Configuration Flow Introduction

During the data configuration, configure the data according to certain flow, as shown inFigure 1-2.

1-5



Figure 1-2 PDSN Data Configuration Flow

1-6



Note:

The above-mentioned configuration sequence is the recommended sequence for initialsystem configuration; the hardware configuration and local data configuration must beperformed first, while there is no strict sequence for other configurations.

1.3.2 Data Configuration Methods

Introduction of the Operation & Maintenance SystemThe operation & maintenance system is composed of a PDSN foreground, an MPU boarddebugging terminal, a local alarm box, and an EMS network management server. Itsnetworking diagram is as shown in Figure 1-3.

Figure 1-3 Schematic Diagram of Operation & Maintenance System

In which,

l The MPU debugging terminal undertakes the initialization operations of the MPUboard (including the MPU board starting method setting, IP address setting, andversion file loading), and it can perform data configuration on PDSN in the commandline method.

l The alarm box is installed locally, presenting alarms in audible and visible forms.l As the upper-level network management, the EMS network management server

undertakes the functions such as daily configuration data maintenance, performance

1-7



statistics data collection and analysis, alarm parameter setting, and securitymanagement.

Data Configuration Methods

Currently two methods are available to configure the PDSN data.l During PDSN office commissioning debugging, Telnet to the MPU board by the MPU

board debugging terminal and execute online data configuration.

If the MPU board debugging terminal is used, set the link property of the HyperTerminal on the debugging terminal, and connect to the Console port of the MPUboard through a serial-port cable.

l During daily maintenance, maintain and configure the daily data through the dataconfiguration function provided by the EMS.

References

If the EMS network management server uses the NetNumen unified network managementsystem of ZTE, you may refer to NetNumen related documents for details.

1.3.3 Precautions for Data ConfigurationCorrect data configuration ensures proper running of the PDSN; meanwhile, dataconfiguration may also influence the service function of the system. Therefore, the dataconfiguration must be carried out strictly according to the configuration flow and thenetwork planning. At the same time, before the data configuration, pay attention to thefollowing:l Knowing the networking situation of the ZXPDSS system, and getting familiar with the

hardware configuration of the NEs.l Setting network planning and IP addresses according to the configuration rules of

dual-network dual-plane.l Knowing the requirements of the ZXPDSS system on the engineering design,

including the data specifications and network environment.l Knowing the data of other NEs or network which are interconnected to the PDSN,

including the IP addresses, port No., and security keys of the opposite NEs.

1.3.4 Data Configuration ReferencesData configuration involves product concept, networking scheme, principleimplementation, and hardware knowledge; refer to the following documents for moreinformation.

l ZXUN xGW eXtendable GateWay PDSN Product Descriptionl ZXUN xGW eXtendable GateWay PDSN Hardware Descriptionl ZXUN xGW eXtendable GateWay PDSN Software Installation Guidel ZXUN xGW eXtendable GateWay PDSN Interface Description

1-8



1.4 ZXPDSS Network PlanningNetwork Planning

This manual takes the ZXPDSS enabling the VRF function as an example to introduce thenetwork planning.

When the networking scheme enables the VRF function, according to different securitylevels, the system networking is classified into 5 areas, and the detailed networkingscheme is as shown in Figure 1-4.

Figure 1-4 Network Planning

According to different security levels, the system networking is classified into 5 areas, asshown in Table 1-2, using the firewall for connection.

Table 1-2 Networking Area Classification

Area Description

RP AreaIncluding the RP interfaces of PCF and PDSN; because the VRF function is enabled, RP-1

area and RP-2 area belong to different VRFs, IP addresses of them can be repeated.

1-9



Area Description

PI Area

Including the PI interface of PDSN, other devices between the PI interface and the

firewall, ZTE gateway/DBIO, and AAA.VRFs are classified into 7 types: VRF accessing

to the Internet (PI-VRF), VRF of data VPN (VPN-VRF), VRF of MIP (MIP-VRF), VRF of

VPDN (VPDN-VRF), VRF of lawful interception (LAW-VRF), VRF of AAA (AAA-VRF),

VRF of OMC (OMC-VRF). Details of VRFs are described in Table 1-3.

Network Management

Area

Including the MPU interface, EMS, AAA OMC server, and upper-level network

management EMS.

Accounting and

Charging AreaIncluding the accounting center and the charging center.

Internet Area -

Table 1-3 Description to VRFs

VRF Type Description

PI-VRFIncluding the PI interface of PDSN and the firewall; multiple PI-VRFs can be configured, and

each PI-VRF is independent to other VRFs; addresses can be repeated.

VPN-VRF

Including the PI interface of PDSN, domain AAA of VPN, and firewall accessing to the VPN

network (or other access equipment such as routers); multiple VPN-VRF can be configured,

each VPN-VRF is independent to other VRFs; addresses can be repeated.

VPDN-VRFIncluding the PI interface (LAC interface) of PDSN and the LNS; multiple VPDN-VRF can be

configured, and each VPDN-VRF is independent to other VRFs; addresses can be repeated.

MIP-VRFIncluding the PI interface (COA interface) of PDSN and the HA; multiple MIP-VRF can be

configured, and each MIP-VRF is independent to other VRFs; addresses can be repeated.

LAW-VRF Including the PI interface (X1/X2 interface) of PDSN and LIG.

AAA-VRF

Including the PI interface (AAAC interface) of PDSN, AAA, AN-AAA, AN, and ZTE

gateway/DBIO; generally one AAA-VRF is configured; AAA-VRF is independent to other

VRFs, and addresses can be repeated.

OMC-VRFIncluding the PI interface of PDSN, and AAA OMC, PDSN MPU, AAA OMC management

interface, PDSN alarm box, and AAA alarm box.

IP Address PlanningTable 1-4 shows an example of IP address planning enabling the VRF function.

Table 1-4 IP Address Planning

NE NE Node IP Address Service IP Address Home VLAN

aaasrv1 192.168.51.152/24 (active)AN_AAA

/AAAaaasrv2

192.168.51.153/24

(standby)

192.168.51.150/24 (service IP)

192.168.51.151/24 (database IP)

192.168.51.130/24 (charging server

IP)

AAA

1-10




RP-1 192.168.50.11/24 192.168.50.12/32 RP

RP-2 192.168.52.11/24 192.168.52.12/32 RP

RP-3 192.168.54.11/24 192.168.54.12/32 RP

PI

AAA

MIP

VPDN

PI-1 192.168.51.11/24 192.168.51.12/32

VPN

PI

AAA

MIP

VPDN

PI-2 192.168.53.11/24 192.168.53.12/32

VPN

PI

AAA

MIP

VPDN

PI-3 192.168.55.11/24 192.168.55.12/32

VPN

X1/X2 lawful

interception

port

- - LAW

SLB - 192.168.50.10/32 RP

1X IP POOL10.50.0.1-

10.50.255.254/16- -

PDSN

DO IP POOL10.60.0.1-

10.60.255.254/16- -

LIG - - 192.168.51.21 LAW

SSG550_1 FE1(inside) 192.168.51.253

SSG550_2 FE1(inside) 192.168.51.252

192.168.51.254

192.168.53.253

192.168.55.253

PI

PDSN MPU - 172.19.1.1/24 - OMC

OMCAAA OMC - 172.23.1.129/24 -

AAA

1-11




AAA OMC

management

interface

- 172.23.1.1/24 - OMC

DBIO - 192.168.51.134/24 - AAA

PDSN alarm

box- 172.19.1.254/24 - OMC

AAA alarm

box- 172. 23.1.254/24 - OMC

1-12


Chapter 2Configuration of the LocalOffice InformationTable of Contents

Loading License .........................................................................................................2-1Basic Configuration ....................................................................................................2-3Board Configuration ...................................................................................................2-9IP Protocol Stack Configuration................................................................................2-17Configuration of Interconnection Between the PDSN and the OCS...........................2-24

2.1 Loading LicensePrerequisites

l The debugging computer has the License files.l The debugging computer is correctly connected to the MPU board.l The FTP server has been set on the debugging computer.

Context

You can perform operations in the PDSN directory only after the License files are loaded.Therefore, before configuring PDSN, you need load License first.

Caution!

The License file cannot be loaded if the equipment ID set in the file is inconsistent with therack equipment ID. You can check the rack equipment ID using the debugging function_lic_dbg_show_devid() under the shell of the LICMNG process, as shown below:

[LICMNG_MPUF_85XX_RELEASE]#_lic_dbg_show_devid()

Steps

1. Log in to the 23 port of the MPU board, and upload the License file to the sysdisk0/directory.

a. Use the telnet method to telnet the MPU board. The corresponding port is 23.

2-1



Note:

The active and standby of MPU boards have different addresses. The active MPUboard address is 168.0.31.1, the port is 23. The standby MPU board address is168.0.31.9, and the port is 23.

b. Type the username and password (for example, the username is zte, the passwordis also zte) and log in to the board.

c. Open the sysdisk0/ directory.The directory is installed in cd /sysdisk0.

d. Upload the License file in the sysdisk0/ directory by entering

ftpget–––u <usrname> -p <password> [FTP Server IP] <license file name> <licensefile name>.

For example, if the FTP server username and password are both zte, the FTPserver address is 168.0.12.15, and the License file is named t8000.lcs, you shouldtype:

/sysdisk0#ftpget–––u zte -p zte 168.0.12.15 t8000.lcs t8000.lcs

2. Log in to the 10000 port of the MPU board to set the License ID.

a. Use the telnet method to telnet the MPU board. The corresponding port is 10000.

b. Type the username and password (for example, the username is zte, the passwordis also zte) and log in to the board.

c. Search the LICMNG process ID using the show command, as shown below:

[admin]#show

d. Type the sh [LICMNG process ID] command to open the LICMNG process, asshown below:

[admin]#sh [LICMNG process ID]

For example, if the LICMNG process ID is 6, type the following:

[admin]#sh 6

The following information appears.

Now switch to LICMNG_MPUF_85XX_RELEASE shell ...

[LICMNG_MPUF_85XX_RELEASE]#

e. Type the setDevId(ID) command to run the License ID, as shown below:

[LICMNG_MPUF_85XX_RELEASE]#setDevId(ID)

For example, if the License ID is 12345678, type the following:

[LICMNG_MPUF_85XX_RELEASE]#setDevId12345678

2-2


Chapter 2 Configuration of the Local Office Information

Note:

The License ID is related to the License file. When obtaining the License file, acorresponding ID is provided, which depends on the on-site conditions.

3. Activate the License file.

a. Log in to the MPU configuration port (or serial port).

b. Type the disable command to enter the xGW subscriber mode, as shown below:

xGW#disable

c. Carry out the license install File name command to activate the License file, asshown below:

xGW>license install File name

For example, if the License file is named t8000.lcs, type the following:

xGW>license install t8000.lcs

Note:

In the xGW> mode, directly type the license install File name command to activatethe License file. In the xGW# mode, type the disable command to enter the xGW>mode.

– End of Steps –

Follow-Up Action

To disable the License function in the Debug version, do the following:

Log in to the 10000 port of the MPU board, and run g_dwStopLicenseCheck=1 in the shellof the INTERPRET process.

2.2 Basic Configuration

2.2.1 Configuring the Time Zone

Prerequisites

l According to the onsite planning, the time zone information is ready.l You have logged in to the configuration window.

2-3



Context

This topic describes how to set the time zone of the system to ensure the time consistency.

Steps

l Configure the time zone.

Command: clock timezone

The command syntax for configuring the time zone is: clock timezone <word> <hoursoffset from UTC> <minutes offset from UTC>, as described in Table 2-1.

Table 2-1 Description of Commands for Configuring the Time Zone

Value Description

word Sets the name of the time zone.

hours offset form UTC New time zone to be set

minutes offset from UTC Sets the offset time on the basis of UTC.


Example

To set the time zone with time zone name as UTC+8 and offset time as 8, use the followingcommand:

xGW(config)#clock timezone UTC+8 8

Follow-Up Action

To query the time zone, use the following command:

xGW(config)#show clock

2.2.2 Configuring the Time

Prerequisites

You have logged in to the configuration window.

Context

This topic describes how to configure the time to make the PDSN foreground timeconsistent with the local time.

Steps

l Configure the time.

Command: clock set

2-4



The command syntax for configuring the time is: clock set <hh:mm:ss><MM-DD-YYYY>, as described in Table 2-2.

Table 2-2 Description of Commands for Configuring the Time

Value Description

hh:mm:ss

Sets the exact time.

l hh: hour

l mm: minute

l ss: second

MM-DD-YYYY

Sets the year, the month, and the date.

l MM: month

l DD: date

l YYYY: year


Example

To set the time as 11:30:40, 20th, May, 2010, use the following command:

xGW(config)#clock set 11:30:40 03-20-2011

Follow-Up Action

To query the time, use the following command:

xGW(config)#show clock

2.2.3 Configuring the VRF

Prerequisites

l The network planning is complete.l You have logged in to the configuration window.

Context

Main function of VRF is to differentiate different route spaces; if the VRF function is notsupported, there is only one set of global route table on a PDSN; if the VRF function issupported, routes for different VRF spaces can be separated, therefore the IP addressesconfigured on different interfaces can be repeated.

Virtual Route Forwarding Table (VRF) means that in the PDSN system, multiple routetables can be accomplished, and IP messages from different VPNs can find their ownroute tables without interferences. A VRF can apply to one ore multiple physical interfacesand sub-interfaces simultaneously, that is, one VRF can correspond to multiple physicalinterfaces and sub-interfaces.

2-5



Using the VRF method, PDSN does not need to establish connection to the VPN networkusing the message encapsulation by tunnels higher than level 2, while it can establishconnection to the VPN network using the virtual route method directly.

PDSN establishes individual VPN route forwarding tables for users in each VPN type.Users in different VPN types use their own route forwarding tables, therefore, PDSN canestablish connection to the router of the VPN network directly, and forward user datainformation between user terminals and VPN network.

After a user accesses the PDSN, according to the attribute of the VPN where the userbelongs, PDSN finds the route for the user data message from the route forwarding tablespecified by the VPN, and forwards the user message from the specified sub-interface,and mark the VLAN ID of the user message in the Ethernet header of the message. PDSNreceives the user data message with VLAN ID specified, determines the VPN attribute ofthe user according to the VLAN, and forwards the message to the user.

Steps1. Create a VRF.

Command: ip vrf

The command syntax for configuring the VRF is: ip vrf <WORD> vpnid <vpnid>, asdescribed in Table 2-3.

Table 2-3 Description of Commands for Creating the VRF

Parameter Value Description

- WORD VRF name

vpnid vpnid ID of the VPN

2. Set the range of rd.

Command: rd

The command syntax for configuring the rd is: rd rd:rd, as described in Table 2-4.

Table 2-4 Description of Commands for Setting the rd Range

Value Description

rd:rd

Route distinguisher, used to differentiate the

routes of different VPNs. rd range <1-65535>:

<0-4294967295>.


ExampleTo create the VRF with name as PI, and VPN ID as 1, use the following command:

xGW(config)#ip vrf PI vpnid 1

To set the rd range of VRF as 1:1, use the following command:

2-6



xGW(config-vrf)#rd 1:1

Follow-Up Action

To query all VRFs, use the following command:

xGW(config)#show ip vrf

2.2.4 Validating the Configuration

Prerequisites

l You have logged in to the configuration window.l The configuration is complete.

Context

After the configuration commands are complete, carry out the command write under thedirectory xGW to save the configuration data. Otherwise, you will lose all configuration dataafter the MPU board is restarted.

Steps

l Save the configuration.

Command: write


Example

To save the configuration data, use the following command:

xGW#write

2.2.5 Showing the Configuration Information

Context

Show the configuration information through the command show or list.

Steps

l Type the command list in the configuration directory to be queried to show theconfiguration information.

l Type the command list in the configuration directory to be queried to show theconfiguration information.

The common show commands are listed in Table 2-5.

2-7



Table 2-5 show Command

Command Meaning

xGW(config)#show ip interface Queries the IP port.

xGW(config-xgw-pdsn)#show pdsn group Queries the CPU group.

xGW(config-xgw-pdsn)#show pdsn

service-ip-addressQueries the PDSN service address.

xGW(config-xgw-slb)#show slb group Queries the SLB group information.

xGW(config-xgw-cu)#show cu ageing-time Queries the CU ageing time.

xGW(config-xgw-cu)#show cu group Queries the CU group information.


sip-local-authentication-user

Queries the information of SIP local

authentication users.

xGW(config-xgw-pdsn)#show pdsn l2tp

local-authentication-user

Queries the information of L2TP local

authentication users.


service-ip-addressQueries the PDSN service IP address.

xGW(config-xgw-pdsn)#show pdsn mip secure

fa-ha-segment

Queries the security association between an

FA and a segment of HA.

xGW(config-xgw-pdsn)#show pdsn mip secure

fa-ha

Queries the security association between an

FA and an HA.

xGW(config-xgw-pdsn)#show pdsn aaa-profile Queries all names of the AAA Profile.

xGW(config-xgw-pdsn)#show pdsn aaa-profile

<profile-name>

Queries the information of an AAA Profile,

<profile-name> is the name of the AAA Profile

to be queried.

xGW(config-xgw-pdsn)#show pdsn ippool Queries all IP pools.

xGW(config-xgw-pdsn)#show pdsn ippool

<pool-name>

Queries an IP pool, <pool-name> is the name

of the IP pool to be queried.

xGW(config-xgw-pdsn)#show pdsn realm Queries all Realms.

xGW(config-xgw-pdsn)#show pdsn rp secure Queries the RP security association.

xGW(config-xgw-pdsn)#show pdsn licQueries the basic information of the lawful

interception configuration local end.


Example

Take querying the AAA Profile configuration information as an example.

l The command list is used as shown below:

xGW(config-xgw-pdsn-aaa)#list

2-8



l The command show is used as shown below:

xGW(config-xgw-pdsn)#show pdsn aaa-profile aaa // aaa is the name of the RADIUSProfile to be queried.

2.3 Board Configuration

2.3.1 Configuring the CPU Group Information

Prerequisites


Context

This topic describes how to create a CPU group and set the backup relationship of theCPU group.

Steps

1. Create and enter a CPU group or directly enter the CPU group.

Command: group

The command syntax for creating and entering the a CPU group or directly enteringthe CPU group is: group <number>, as described in Table 2-6.

Table 2-6 Description of Commands for Creating or Entering a CPU Group

Value Description

number Group No. of the CPU group

2. Set the backup mode of the CPU group.

Command: backupmode

The command syntax for configuring the backup mode of the CPU group is: backupmode {none | 1+1 | N+1}, as described in Table 2-7.

Table 2-7 Description of Commands for Setting Backup Mode of CPU Group

Value Description

none no backup

1+1 1+1 backup

N+1 N+1 backup


2-9



Example

1. To create and enter or directly enter the CPU group whose group No. is 1, use thefollowing command:

xGW(config-xgw-pdsn)#group 1

2. To configure the backup mode of the CPU group as 1+1 backup, use the followingcommand:

xGW(config-xgw-pdsn-group)#backupmode 1+1

Follow-Up Action

To query the CPU group, use the following command:

l xGW(config-xgw-pdsn-group)#listl xGW(config-xgw-pdsn)#show pdsn group

To delete a CPU group, use the following command:

xGW(config-xgw-pdsn)#no group <number>

Note:

Delete all CPUs configured in a group before deleting the group.

2.3.2 Adding a CPU

Prerequisites

l You have logged in to the configuration window.l The CPU group is configured, as described in 2.3.1 Configuring the CPU Group

Information.

Context

This topic describes how to add a CPU on the board into the created CPU group.

Steps

l Add a CPU into the CPU group.

Command: cpu

The command syntax for adding a CPU is: cpu <location>, as described in Table 2-8.

2-10



Table 2-8 Description of Commands for Adding a CPU

Parameter Description

Location

Location of the CPU, the format is: shelf<0-79>/slot<0-

22>/cpu<0-5>.

l Shelf: shelf, generally the shelf ID is configured as 0.

l Slot: slot

l cpu: CPU ID, generally starting from 0 and orderly

numbered inside the board.

Note:

Use the CPU that is powered on successfully and runs properly earlier as the activeCPU, while use the latter one as the standby one.

Configured active/standby CPUs must have the same shelf ID, different slot No., andthe same CPU ID.


Example

1. To create and enter or directly enter the CPU group whose group No. is 10, use thefollowing command:

xGW(config-xgw-pdsn)#group 10

2. To configure the backup mode of the CPU group as 1+1 backup, use the followingcommand:

xGW(config-xgw-pdsn-group)#backupmode 1+1

3. To add the CPU 0 of the GSU boards at slots 14 and 15 into the CPU group whosegroup No. is 10, use the following command:

xGW(config-xgw-pdsn-group)#cpu 0/14/0

xGW(config-xgw-pdsn-group)#cpu 0/15/0

Follow-Up Action

To delete a CPU, use the following command:

xGW(config-xgw-pdsn-group)#no cpu <location>

2-11



2.3.3 Configuring the SLB

Prerequisites


Context

As the master control unit of the PDSN load sharing, Server Load Balancing (SLB)allocates the usage of the GSU resources, so as to make sure the balance of the loadof each GSU.

Steps

1. Enter the SLB configuration area.

Command: slb

2. Create and enter the SLB group.

Command: group

The command syntax for creating and entering the SLB group is: group <number>, asdescribed in Table 2-9.

Table 2-9 Description of Commands for Creating and Entering an SLB Group

Value Description

numberNo. of the SLB group, configuration range: numeric string

from 1 to 250.

3. Configure the backup mode of the CPU of the SLB group.

Command: backupmode

The command syntax for configuring the backup mode of the CPU of the SLB groupis: backupmode {none | 1+1}, as described in Table 2-10.

Table 2-10 Description of Commands for Configuring Backup Mode of CPU ofSLB Group

Value Description

none No backup

1+1 1+1 backup

4. Add a CPU into an SLB group.

Command: cpu

The command syntax for adding a CPU in an SLB group is: cpu <location>, asdescribed in Table 2-11.

2-12



Table 2-11 Description of Commands for Adding a CPU in an SLB Group

Value Description

location


22>/cpu<0-5>.

l Shelf: shelf

l Slot: slot

l cpu: CPU ID

Note:



5. Configure the SLB address.

Command: virtual-rp-ip-addrdss

The command syntax for configuring the SLB address is: virtual-rp-ip-addrdss<A.B.C.D> [vrf <vrf-name>], as described in Table 2-12.

Table 2-12 Description of Commands for Configuring the SLB Address


- A.B.C.D SLB address

vrf vrf-nameVRF name, configuration range: 1-32 bit

string.


Example

1. To enter the SLB configuration area, use the following command:

xGW(config-xgw)#slb

2. To create and enter the SLB groupwith the groupNo. as 1, use the following command:

xGW(config-xgw-slb)#group 1

3. To set the CPU as 1+1 backup, use the following command:

xGW(config-xgw-slb-group)#backupmode 1+1

4. Add the CPU with shelf 0/slot 13/CPU 0 and the CPU with shelf 0/slot 15/CPU 0 intothe SLB group, use the following command:

xGW(config-xgw-slb-group)#cpu 0/13/0

2-13



xGW(config-xgw-slb-group)#cpu 0/15/0

5. To configure the SLB address as 192.168.50.10 and the VRF as RP, use the followingcommand:

xGW(config-xgw-pdsn)#virtual-rp-ip-address 192.168.50.10 vrf RP

Follow-Up Action

To query the SLB group information, use the following command:

l xGW(config-xgw-slb-group)#listl xGW(config-xgw-slb)#show slb group

To delete the CPU group information, use the following command:

l xGW(config-xgw-slb-group)#no cpu <location>l xGW(config-xgw-slb-group)#clear-cpu-all

To delete an SLB group, use the following command:

xGW(config-xgw-slb)#no group <number>

Note:


To delete the SLB address, use the following command:

xGW(config-xgw-pdsn)#no virtual-rp-ip-address <A.B.C.D> [vrf <vrf-name>]

2.3.4 Configuring the CU Daughter Card

Prerequisites

l You have logged in to the configuration window.l Make sure that there is a CPU as XSFC in the daughter card No. on the GSU board.

Context

This topic describes how to configure the CPU of the Charging Unit (CU) daughter card,and configure the alarm threshold.

Only the CPU as XSFC in the daughter card No. on the GSU board can be configured asthe CU, and generally it is the CPU 2 on the GSU; therefore, the location of the CPU thatis to be configured as CU is shelf 0/slot XX/CPU 2.

There is a hard disk on the CU daughter card, which is used to save the CDRs.

2-14



CU does not require to configure the backup mode of the CPU group, and all CPUs areactive by default. Where there are multiple CU groups, system will automatically choosethe CU group with a smaller group No. as the preferred CU group for saving CDRs.

Steps1. Enter the CU configuration area.

Command: cu

2. Create and enter the CU group.

Command: group

The command syntax for creating and entering the CU is: group <number> asdescribed in Table 2-13.

Table 2-13 Description of Commands for Creating and Entering an CU Group

Value Description

numberNo. of the CU group, Configuration range: numeric string

from 1 to 250.

3. Carry out the following command to add a CPU into a CU group in CU group mode.

Command: cpu

The command syntax for adding a CPU into a CU group is: cpu <location>, asdescribed in Table 2-14.

Table 2-14 Description of Commands for Adding a CPU into a CU Group

Value Description

location


22>/cpu<0-5>.

l Shelf: shelf

l Slot: slot

l cpu: CPU ID

Note:



4. Set the context capacity alarm threshold.

Command: system-resource-alarm

2-15



The command syntax for setting the context capacity alarm thresholdis :system-resource-alarm <alarm-code> {(<level> <threshold> <restore-threshold> | default}, asdescribed inTable 2-15.

Table 2-15 Description of Commands for Setting the Context Capacity AlarmThreshold

Value Description

alarm-codeAlarm code, configuration range: numeric string from 0 to

4294967295.

level

Alarm level, configuration range: numeric string from 1 to

4, it refers to alarm level from 1 to 4. Smaller value refers

to higher alarm level.

thresholdAlarm threshold, configuration range: string from 60% to

95%, it refers to alarm once this threshold is exceeded.

restore-threshold

Alarm restoring threshold, configuration range: string from

55% to 95%, it refers to restoring alarm once this threshold

is exceeded.

defaultDefault alarm value; System default alarm parameter is

used.

5. Configure the CU ageing time.

Command: ageing-time

The command syntax for configuring the CU ageing time is: ageing-time {<3-30> |default}, as described in Table 2-16.

Table 2-16 Description of Commands for Configuring the CU Ageing Time

Value Description

3-30Value of the CU ageing time, ranging 3~30. When the hard disk space on the CU is

insufficient, CDRs earlier the ageing time will be deleted firstly.

default The default ageing time is 7 days.


Example

1. To enter the CU configuration area, use the following command:

xGW(config-xgw)#cu

2. To create and enter the CU group with the group No. as 1, use the following command:

xGW(config-xgw-cu)#group 1

3. Add the CPU with shelf 0/slot 13/CPU 2 into the CU group 1, use the followingcommand:

2-16



xGW(config-xgw-cu-group)#cpu 0/13/2

4. To create the CU group 2 in a similar way, and add the CPU with shelf 0/slot 15/CPU2 into this group, use the following command:

xGW(config-xgw-cu)#group 2

xGW(config-xgw-cu-group)#cpu 0/15/2

5. To set the value whose alarm code is 1 as default, use the following command:

xGW(config-xgw-cu)#system-resource-alarm 1 default

6. To configure the CU ageing time in the default way, use the following command:

xGW(config-xgw-cu)#ageing-time default

Follow-Up Action

To query the CU ageing time, use the following command:

xGW(config-xgw-cu)#show cu ageing-time

To query the CU group information, use the following command:

xGW(config-xgw-cu)#show cu group

To delete the CPU of the CU group, use the following command:

xGW(config-xgw-cu-group)#no cpu <location>

To delete a CU group, use the following command:

xGW(config-xgw-cu)#no group <number>

Note:


2.4 IP Protocol Stack Configuration

2.4.1 Configuration Flow of IP Protocol StackThe flow for configuring the IP protocol stack is as shown in Figure 2-1.

2-17



Figure 2-1 Configuration Flow of IP Protocol Stack

2.4.2 Querying the Real Interface Status

Prerequisites

l The PFU board is started properly.l You have logged in to the configuration window.

ContextThe real interface is the physical interface, which is used for communications amongbottom layer links of PDSN.

Steps

l Query the status of the real interface.

Command: show ip interface


ExampleTo query the status of the real interface, use the following command:

xGW(config)#show ip interface

2-18



The following is an example of the output result for querying the status of the real interface.

gei-0/10/0/1 AdminStatus is up, PhyStatus is down,

line protocol is down

IP MTU is 1500 bytes

gei-0/10/0/2 AdminStatus is up, PhyStatus is up,

line protocol is up

Internet address is 192.136.1.1/16

Broadcast address is 255.255.255.255

Secondary address is 194.136.1.1/16




gei-0/10/0/3

AdminStatus is up, PhyStatus is down,





IP MTU is 1500 bytes gei-0/10/0/5

AdminStatus is up, PhyStatus is down,

line protocol is down IP MTU is 1500 bytes


line protocol is down IP MTU is 1500 bytes

gei-0/10/0/7 AdminStatus is up, PhyStatus is up,

line protocol is up IP MTU is 1500 bytes

2.4.3 Configuring Basic Information of the Real Interface

Prerequisites

l The PFU board is started properly.l You have logged in to the configuration window.

Context

This topic describes how to set the real interface in the PFU board.

Steps

1. Enter the interface status.

Command: interface

The command syntax for entering the interface status is: interface gei-0/10/0/7 or interface xgei-0/10/0/7, as described in Table 2-17.

2-19



Table 2-17 Description of Commands for Entering the Interface Status

Value Description

gei-0/10/0/7 or xgei-0/10/0/7

Name of the real interface, it is the Interface Name in the

result of querying the real interface, as described in 2.4.2

Querying the Real Interface Status. This parameter should

be set as required.

Note:

To enter the interface status, use gei when the interface is 1000M or 100M, and usexgei when the interface is 10G port.

2. Add the interface IP address.

Command: ip add

The command syntax for adding the interface IP address is: ip address <IP-address><mask>, as described in Table 2-18.

Table 2-18 Description of Commands for Adding the Interface IP Address

Value Description

IP-Address IP address of the real interface.

Mask Mask address of the real interface.

3. Set the MAC address offset.

Command: interface mac-address offset

The command syntax for setting the MAC address offset is: interface mac-addressoffset <number>, as described in Table 2-19.

Table 2-19 Description of Commands for Setting MAC Address Offset

Value Description

number Number of bytes for offsetting the MAC address.

Note:

The PFU has multiple optical ports or electrical ports, and their MAC addresses maybe the same; therefore, offset their MAC addresses for N bytes during configurationto ensure no-repeat.


2-20



Example

1. To enter the interface gei-0/10/0/7, use the following command:

xGW(config)#interface gei-0/10/0/7

2. To add the RP interface IP address, with IP address as 192.168.50.11 and mask as255.255.0.0, use the following command:

xGW(config-if)#ip address 192.168.50.11 255.255.0.0

To add the PI interface IP address, with IP address as 192.168.51.11 and mask as255.255.0.0, use the following command:

xGW(config-if)#ip address 192.168.51.11 255.255.0.0

3. To set the MAC address to offset for 2 bytes, use the following command:

xGW(config-if)#interface mac-address offset 2

2.4.4 Configuring the Default Route

PrerequisitesYou have logged in to the configuration window.

ContextThis topic describes how to set the default route of the PDSN.

Steps

l Set the default route of the PDSN.

Command: ip route 0.0.0.0 0.0.0.0 gateway IP address


ExampleTo set the default route of the PDSN, use the following command:

xGW(config)#ip route 0.0.0.0 0.0.0.0 194.136.0.254

Follow-Up ActionTo query the route of the PDSN, use the following command:

xGW(config)#show ip protocol routing

2.4.5 Configuring a Non-default Route


2-21



ContextThis topic describes how to set the non-default route of the PDSN.

Steps1. Set the non-default route of the PDSN.

Command: ip route

The command syntax for setting the non-default route of the PDSN is: ip route<IP-address> <mask> <next hop>, as described in Table 2-20.

Table 2-20 Description of Commands for Setting Non-default Route of PDSN

Value Description

IP-Address Destination IP address of the non-default route.

Mask Mask address of the non-default route.

Next HopGateway IP address of the non-default route, which must be in the same

network segment with the IP address of the interface using this route.


ExampleTo set the route with the destination IP address as 192.136.2.5, the subnet mask as255.255.0.0, and the gateway address as 194.136.0.254, use the following command:

xGW(config)#ip route 192.136.2.5 255.255.0.0 192.136.0.254

2.4.6 Configuring the VRF Bound with the Sub-interface

Prerequisites

l The PFU board is started properly.l The VRF is configured, as described in 2.2.3 Configuring the VRF.l You have logged in to the configuration window.

ContextThis topic describes how to bind the VRF to the sub-interface, so as to realize the VPNfunction.

Steps1. Enter the VLAN configuration directory.

Command: vlan

2. Enter the sub-interface status.

Command: interface

2-22



The command syntax for entering the sub-interface status is: interfacegei-0/10/0/7.<1–4094> or interface xgei-0/10/0/7.<1–4094> as described in Table2-21.

Table 2-21 Description of Commands for Entering the Sub-interface Status

Value Description

<1–4094> Range of the sub-interface No.

3. Bind the sub-interface with the VLAN.

Command: encapsulation-dot1q

The command syntax for binding the sub-interface with the VLAN is: encapsulation-dot1q <1–4094>, as described in Table 2-22.

Table 2-22 Description of Commands for Binding the Sub-interface with the VLAN

Value Description

<1–4094> Range of VLAN ID.

4. Exit VLAN configuration.

Command: exit

5. Enter the sub-interface status.

Command: interface

6. Bind the sub-interface with the VRF.

Command: ip vrf forwarding

The command syntax for binding the sub-interface with the VRF is: ip vrf forwarding<WORD>, as described in Table 2-23.

Table 2-23 Description of Commands for Binding the Sub-interface with the VRF

Value Description

WORD VRF name.

7. Configure the IP address of the sub-interface.

Command: ip address

The command syntax for configuring the IP address of the sub-interface is: ip address<A.B.C.D> <A.B.C.D>, as described in Table 2-24.

Table 2-24 Description of Commands for Configuring the IP Address of theSub-interface

Value Description

A.B.C.D IP address of the sub-interface.

2-23



Value Description

A.B.C.D Mask of the sub-interface IP address.


Example

1. To enter the VLAN configuration directory, use the following command:

xGW(config)#vlan

2. To enter the sub-interface status, use the following command:

xGW(vlan-config)#interface gei-0/10/0/7.1

3. To bind the sub-interface with the VLAN, use the following command:

xGW(subvlan-if-config)#encapsulation-dot1q 10 // 10 is the VLAN ID.

4. To exit the VLAN configuration, use the following command:

a. xGW(subvlan-if-config)#exit

b. xGW(vlan-config)#exit

5. To enter the sub-interface status, use the following command:

xGW(config)#interface gei-0/10/0/7.1

6. To bind the sub-interface with the VRF, use the following command:

xGW(config-subif)#ip vrf forwarding PI // PI is the VRF name.

7. To configure the IP address of the sub-interface, use the following command:

xGW(config-subif)#ip address 192.168.51.11 255.255.0.0

Follow-Up Action

Query the brief information of the interface.

xGW(config)#show ip interface

2.5 Configuration of Interconnection Between thePDSN and the OCS

2.5.1 Configuration Flow of Interconnection Between PDSN andOCS

Refer to the flow as shown in Figure 2-2 to configure the interconnection between thePDSN and the OCS.

2-24



Figure 2-2 Configuration Flow of Interconnection Between PDSN and OCS

2.5.2 Configuring the Adjacent Node

PrerequisitesYou have entered the PDSN configuration mode, and the command prompt becomes:xGW(config-xgw-pdsn)#.

ContextConfigure the Diameter adjacent office node parameters.

Steps

l Configure the adjacent office node parameters.

Command: diameter adjacent-node

The command syntax for configuring the adjacent office node parametersis: diameter adjacent-node <node-name> type {bmsc | none | proxy |ocs(interface-mode {ro_extension_10(0) | ro_extension_11(1) | ro_3gpp_32299_6b0(2)| ro_3gpp_32299_900(3) | ro_extension_12(4) | ro_extension_14(5)| ro_extension_13(8) | ro_extension_41(9)}) | pcrf (interface-mode {gx_3gpp_29212_910(7)|gx_extension_20(6)})} (host <host-name>) (realm<realm-name>) (capability <0–128>) [tx-timer <6–12>], as described in Table 2-25.

2-25



Table 2-25 Description of Commands for Configuring Adjacent Office NodeParameters


node-name Adjacent office node name, 1–63 characters.

type

Adjacent office type:

l none: the specific type of the node is not specified.

l proxy: the adjacent office supports the Diameter Proxy function.

l ocs: the adjacent office supports the OCS function.

l pcrf: the adjacent office supports the PCRF function.

l bmsc: the adjacent office supports the BMSC function.

interface-mode

The type of the interfaces activated for the adjacent office. Currently,

two types of interfaces are available, Gx and Ro.

Wherein, Gx interfaces can be further divided into:

l ro_extension_10(0): the extended Ro interfaces based on the

3GPP v1.0 version.


3GPP v1.1 version.

l ro_3gpp_32299_6b0(2): the Ro interfaces defined in 3GPP

TS32.299 v6.b.0.

l ro_3gpp_32299_900(3): the Ro interfaces defined in 3GPP

TS32.299 v9.0.0.


3GPP v1.2 version.


3GPP v1.4 version.


3GPP v1.3 version.

Go interfaces can be further divided into:

l gx_3gpp_29212_910(7): Ro interfaces defined in 3GPP TS29.212

v9.1.0.

l gx_extension_20(6): the extended Ro interfaces based on the

3GPP v2.0 version.

host-name Host name, 1–63 characters.

realm-name domain name, 1–63 characters.

capability

The capacity negotiation template used when the Diameter connection

to the adjacent office is created. Before configuring the information, you

need configure the Diameter capacity negotiation template first, valued

as a string of 0-128 digits.

tx-timer Timeout timer, ranging (unit: second) 6–12.


2-26



Example

To configure the adjacent office node name as ocs1, the adjacent office type as ocs, usingthe Ro interfaces defined in 3GPP TS32.299 v6.b.0, with the host name ocs1, domainname ocs1, and the negotiation template 0, use the following command:

xGW(config-xgw-pdsn)#diameter adjacent-node ocs1 interface-modero_3gpp_32299_6b0(2) host ocs1 realm ocs1 capability 0

2.5.3 Configuring the Local Node

Prerequisites

You have entered the PDSN configuration mode, and the command prompt becomes:xGW(config-xgw-pdsn)#.

Context

Configure the Diameter local node parameters.

Steps

l Configure local node parameters.

Command: diameter local-node

The command syntax for configuring local node parameters is: diameter local-node<node-name> (host <host-name>) (realm <realm-name>) (carrier <carrier-name>)(interface-mode <1–8>), as described in Table 2-26.

Table 2-26 Description of Commands for Configuring Local Node Parameters


node-name Local node name, 1–63 characters

carrier-name Operator name, 1–127 characters

host-name Host name, 1–63 characters

realm-name

The Diameter domain name of the adjacent office, the

Host ID of the node when receiving and sending a

Diameter message, composed of 1-63 characters.

interface-mode Interface mode, ranging 1–8


Example

To configure the local node name as pdsn1, the operator name as pdsncarrier, the hostname as hostpdsn.com, the domain name as unicomgd.com, and the interface mode as1, use the command below:

2-27



xGW(config-xgw-pdsn)#diameter local-node pdsn1 carrier pdsncarrier hosthostpdsn.com realm unicomgd.com interface-mode 1

2.5.4 Configuring the Diameter Link

Prerequisites

l You have entered the PDSN configuration mode, and the command prompt becomes:xGW(config-xgw-pdsn)#.

l The CPU is added in the CPU group.l The local office node is configured.l The adjacent office node is configured.l The TCP link is configured.

Context

Configure the Diameter link.

Steps

l Configure the Diameter link.

Command: diameter link

The command syntax for configuring the Diameter link is: diameter link <link-name><local-node-name> <adjacent-node-name> {none {[ro/gy] ,[gx], [gmb]}} (tcp-name<tcp-name>) [tc <0,4–100>] [dwr <1–20>] [avp-check], as described in Table 2-27.

Table 2-27 Description of Commands for Configuring Diameter Link


link-name Diameter link name, 1–63 characters.

local-node-name Local office node name, 1–63 characters.

adjacent-node-name Adjacent office node name, 1–63 characters.

gmb|gx|none|ro/gy

Application type, with options below:

l none: no Diameter application type is specified.

l gmb: gmb interface.

l gx: corresponds to the Gx interface application, used when the

peer-end is PCRF and the Gx interface is available.

l ro/gy: corresponds to the Ro interface (alternatively named

as Gy interface), used when the peer-end is OCS and the Ro

interface is available.

tcp-name TCP link name, 1–63 characters.

tcTc timer, which sets the interval for message re-transfer during

Diameter negotiation. Optional parameter, a string of 5-100 digits.

2-28




dwr Maximum no responded dwr sending times, 1-20 characters.

avp-check Sets whether to check the Diameter capability AVP of the peer end.


ExampleTo configure the Diameter link name as ocs1, the local node name as pdsn1, the adjacentoffice name as ocs1, the application type as ro/gy, the TCP link name as ocs1, the Tc timervalue as 10 seconds, and configure to check the Diameter capability of the peer end, usethe following command:

xGW(config-xgw-pdsn)#diameter link ocs1 pdsn1 ocs1 ro/gy tcp-name ocs1 tc 10avp-check

2.5.5 Configuring the TCP Link

Prerequisites

l You have entered the PDSN configuration mode, and the command prompt becomes:xGW(config-xgw-pdsn)#.

l The CPU is added in the CPU group.

ContextConfigure the Diameter TCP link.

Steps

l Configure the TCP link.

Command: diameter tcp-link

The command syntax for configuring the TCP link is: diameter tcp-link <name> <LocalIP> <1–65536> <destination ip> <1–65536> <cpu-location> [mtu <800-1460>] [vrf<vrf-name>], as described in Table 2-28.

Table 2-28 Description of Commands for Configuring the TCP Link


name TCP link name, 1–63 characters

local ip Local PDSN IP address

1–65536 Local port No., integer type: 1–65535

destination ip Opposite OCS IP address

1–65536 Opposite port No., integer type: 1–65535

2-29




cpu-location

CPU ID of the PDSN, the format is: groupno/intragroupno

groupno: Group ID of the CPU group

intragroupno: CPU ID inside the group

mtu MSS value, integer type: 800–1460

vrf-name VRF name


Example

To configure the TCP link name as ocs1, local address as 192.168.50.11 (loopbackaddress), local port No. as 8888, opposite address as 192.168.59.19, and opposite portNo. as 8889 for CPU 1 of CPU group 4, use the command below:

xGW(config-xgw-pdsn)#diameter tcp-link ocs1 192.168.50.11 8888 192.168.59.198889 4/1

2-30


Chapter 3Configuration of theInterfacesTable of Contents

Interface Introduction..................................................................................................3-1Configuration of Interconnection Between the PDSN and the PCF .............................3-1Configuration of the Interconnection Between the PDSN and the HA .........................3-5Configuration of Interconnection Between the PDSN and the AAA .............................3-9Configuration of Interconnection Between the PDSN and the LNS ...........................3-15

3.1 Interface IntroductionDescriptionInterfaces are classified into physical interface and service interface.

l Physical interface is used to accomplish communication among bottom layer links.l Service interface is used to accomplish communication among NEs.

Interface Types of the PDSNExternal interfaces of the PDSN includes RP interface and PI interface.

l RP interface

The RP interface is the interface between the PDSN and the PCF.

l PI interface

The PI interface is the interface among PDSN and devices such as AAA, HA, andLNS.

3.2 Configuration of Interconnection Between thePDSN and the PCF

3.2.1 Configuration Flow of Interconnection Between PDSN andPCF

Refer to the flow as shown in Figure 3-1 to configure the interconnection between thePDSN and the PCF.

3-1



Figure 3-1 Configuration Flow of Interconnection Between PDSN and PCF

3.2.2 Configuring the Real IP Address of the RP Interface

Prerequisites

l The network planning is complete.l You have logged in to the configuration window.l The CPU is added in the CPU group.

Context

When completes configuring the CPU group in the PDSN and adding the CPU into theCPU group, configure the RP service addresses for specific CPUs, and use these CPUsto process the data communication from the RP interface.

Steps

l Configure the Real IP service address of the RP interface.

Command: rp real-ip

The command syntax for configuring the Real IP service address of the RP interfaceis: rp real-ip <A.B.C.D> [vrf <vrf-name>] <cpu-location>, as described in Table 3-1.

Table 3-1 Description of Commands for Configuring the Real IP Service Addressof the RP Interface


- A.B.C.D Service address of the RP interface.


string.

3-2


Chapter 3 Configuration of the Interfaces


- cpu-location

CPU No. of the PDSN, with the format as:

groupno<1-250>/intragroupno<1-5>.

l groupno: No. of the CPU group, the

range is 1-250.

l intragroupno: CPU ID inside the

group, the range is 1-5.


ExampleTo set the RP service address of CPU 1 of CPU group 1 as 192.168.50.12, use the followingcommand:

xGW(config-xgw-pdsn)#rp real-ip 192.168.50.12 1/1

Set the RP service address of CPU 1 of CPU group 1 as 192.168.52.12, and add thisaddress to the VRF whose name is RP, use the following command:

xGW(config-xgw-pdsn)#rp real-ip 192.168.52.12 vrf RP 1/1

Follow-Up ActionTo query the RP service address, use the following command:

xGW(config-xgw-pdsn)#show pdsn service-ip-address

To delete the RP service address, use the following command:

xGW(config-xgw-pdsn)#no rp real-ip <A.B.C.D> [vrf <vrf-name>]

3.2.3 Configuring the Security Association of RP Interface


ContextConfiguring the security association is to configure the security association parametersused to show legal identity when PDSN communicates to other NEs.

Security association parameters between PDSN and PCF includes the security parameterindex and the shared key, and these parameters must be consistent with those configuredat PCF side.

Steps

l Add the PCF-PDSN security association.

Command: rp secure

3-3



The command syntax for adding the RP interface security association is: rpsecure <A.B.C.D> [vrf <vrf-name>] {(spi <256-4294967295>) | ((regist-spi<256-4294967295>) (update-spi <256-4294967295>))} {(string <key-string>) | (hex<key-string>)}, as described in Table 3-2.

Table 3-2 Description of Commands for Adding RP Security Association


- A.B.C.DIP address of the RP security association, that is the IP address

of the PCF.

vrf vrf-nameVRF name; vrf <vrf-name> is optional, and the value of vrfid is 0

when nothing is typed, configuration range: 1-32 bit string.

spi256-

4294967295

Security parameter index of the RP session security association

(including the registration security association and the session

update security association), configuration range: numeric string

from 256 to 4294967295.

regist-spi256-

4294967295

Security parameter index of the registration security association,

configuration range: numeric string from 256 to 4294967295.

update-spi256-

4294967295

Security parameter index of the session update security

association, configuration range: numeric string from 256 to

4294967295.

string

hexkey-string

Shared key

l string: Character string, configuration range: 1-64 bit string.

l hex: Hex, configuration range: 1-128 bit string.


Example

To add the RP security association, with PCF IP address as 192.136.30.15, security keyas 123456789ZBCDEF, and security parameter index as 256, use the following command:

xGW(config-xgw-pdsn)#rp secure 192.136.30.15 spi 256 string 123456789ABCDEF

Follow-Up Action

To query the RP security association information, use the following command:

xGW(config-xgw-pdsn)#show pdsn rp secure

To delete the RP security association information, use the following command:

xGW(config-xgw-pdsn)#no rp secure <A.B.C.D> [vrf <vrf-name>]

3-4



3.3 Configuration of the Interconnection Between thePDSN and the HA

3.3.1 Configuring the FA-HA Security Association

Prerequisites


Context

Configuring the security association is to configure the security association parametersused to show legal identity when PDSN communicates to other NEs.

Security association parameters between PDSN and HA includes the security parameterindex and the shared key, and these parameters must be consistent with those configuredat HA side.

Steps

l Configure the FA-HA security association.

Command: mip secure fa-ha

The command syntax for configuring the FA-HA security association is: mip secure fa-ha <A.B.C.D> {(string <key-string>) | (hex <key-string>)} [vrf <vrf-name>] (spi<256-4294967295>) [authstyle {rfc2002 | rfc2002bis | rfc3344}] [gre-tunnel {enable |disable}] [carry-nai-imsi {none | nai | imsi | both}] [carry-so {enable | disable}] [carry-pcfip-esn {enable | disable}] [rrq-ha-ip-zero {enable | disable}], as described in Table3-3.

Table 3-3 Description of Commands for Configuring FA-HA Security Association


- A.B.C.DIP address of the FA-HA security association, that is the

IP address of the HA.

string key-string

hex key-string

Shared key

l string: Character string, configuration range: 1-64 bit

string.

l hex: Hex, configuration range: 1-128 bit string.

spi256-

4294967295

Security parameter index, configuration range: numeric

string from 256 to 4294967295

vrf vrf-name

VRF name; vrf<vrf-name> is optional, and the value of

vrfid is 0 when nothing is typed, configuration range:1-32

bit string.

3-5




rfc2002

rfc2002bisauthstyle

rfc3344

Authentication algorithm type; if authstyle is not typed,use the default value rfc2002.

enablegre-tunnel

disable

Whether to support the GRE tunnel; if gre-tunnel is nottyped, use the default value disable.

none

nai

imsicarry-nai-imsi

both

Whether NAI or IMSI is carried in the registration

cancellation message or in the registration cancellation

response; if carry-nai-imsi is not typed, use the defaultvalue none.

enable

carry-sodisable

Whether so is carried in the registration cancellation

message; use the default value enable if this parameter

is not typed.

enable Carry pcf ip and esncarry-pcfip-esn

disable Not carry pcf ip and esn

enable Ha address of rrq is zerorrq-ha-ip-zero

disable Ha address of rrq is not zero


ExampleTo add the FA-HA IP address, with IP address of HA as 192.168.51.22, security key as zte,VRF name asMIP, security parameter index as 256, authentication algorithm as RFC2002,use the following command:

xGW(config-xgw-pdsn)#mip secure fa-ha 192.168.51.22 string zte spi 256 vrf MIP authstyle rfc2002

Follow-Up ActionTo query the FA-HA security association information, use the following command:

xGW(config-xgw-pdsn)#show pdsn mip secure fa-ha

To delete the FA-HA security association information, use the following command:

xGW(config-xgw-pdsn)#no mip secure fa-ha <A.B.C.D> [vrf <vrf-name>]

3.3.2 Configuring the FA-HA Security Association IP Segment

Prerequisites

l The network planning is complete.

3-6



l You have logged in to the configuration window.

Context

For security association between FA and HA, besides configuring a single IP address,system supports to configure multiple IP segments. Its advantage lies that when the HAis expanded, PDSN can use the addresses in the configured HA IP segments, while doesnot need to add security association with HA.

If there are multiple HAs in ZXPDSS, and the service addresses of the HA are successive,use the batch adding method to add the FA-HA security association.

Steps

l Add the FA-HA security association in batch.

Command: mip secure fa-ha-segment

The command syntax for adding the FA-HA security association in batch is: mip secure fa-ha-segment <startip> <endip> {(string <key-string>) | (hex <key-string>)} (spi<256-4294967295>) [vrf <vrf-name>] [authstyle {rfc2002 | rfc2002bis | rfc3344}] [gre-tunnel {enable | disable}] [carry-nai-imsi {none | nai | imsi | both}] [carry-so {enable| disable}] [carry-pcfip-esn {enable | disable}] [rrq-ha-ip-zero {enable | disable}], asdescribed in Table 3-4.

Table 3-4 Description of Commands for Adding FA-HA Security Association inBatch


- startipHA start IP address of the FA-HA security

association.

- endipHA end IP address of the FA-HA security

association.

- A.B.C.DIP address of the FA-HA security association,

that is the IP address of the HA.

string key-string

hex key-string

Shared key

l string: Character string, configuration

range: 1-64 bit string.

l hex: Hex, configuration range: 1-128 bit

string.

spi 256-4294967295Security parameter index, configuration range:

numeric string from 256 to 4294967295.

vrf vrf-name

VRF name; vrf<vrf-name> is optional, and

the value of vrfid is 0 when nothing is typed,

configuration range: 1-32 bit string.

3-7




rfc2002

rfc2002bisauthstyle

rfc3344

Authentication algorithm type; if authstyle isnot typed, use the default value rfc2002.

enable

gre-tunneldisable

Whether to support the GRE tunnel; if

gre-tunnel is not typed, use the default valuedisable.

none

nai

imsicarry-nai-imsi

both

Whether NAI or IMSI is carried in the

registration cancellation message or in

the registration cancellation response; if

carry-nai-imsi is not typed, use the defaultvalue none.

enable

carry-sodisable

Whether so is carried in the registration

cancellation message; use the default value

enable if this parameter is not typed.

enable Carry pcf ip and esncarry-pcfip-esn

disable Not carry pcf ip and esn

enable Ha address of rrq is zerorrq-ha-ip-zero

disable Ha address of rrq is not zero


Example

To add the FA-HA security association in batch, with HA start IP address as 192.168.53.22,end IP address as 192.168.53.25, security key as zte, VRF name as MIP, securityparameter index as 256, authentication algorithm as RFC2002, use the followingcommand:

xGW(config-xgw-pdsn)#mip secure fa-ha-segment 192.168.53.22 192.168.53.25 string ztespi 256 vrf MIP authstyle rfc2002

Follow-Up Action

To query the information of a segment of FA-HA security association, use the followingcommand:

xGW(config-xgw-pdsn)#show pdsn mip secure fa-ha-segment

To delete the information of a segment of the FA-HA security association, use the followingcommand:

xGW(config-xgw-pdsn)#no mip secure fa-ha-segment <startip> [vrf <vrf-name>]

3-8



3.4 Configuration of Interconnection Between thePDSN and the AAA

3.4.1 Configuration Flow of Interconnection Between PDSN andAAA

Refer to the flow as shown in Figure 3-2 to configure the interconnection between thePDSN and the AAA.

Figure 3-2 Configuration Flow of Interconnection Between PDSN and AAA

3.4.2 Configuring the AAA Profile Name

Prerequisites


3-9



Context

AAA-Profile includes the attributes used for authentication and charging, including RADIUSserver address, authentication port number, and charging port number.

The authentication attribute and the charging attribute can be configured in the sameprofile, and can also be configured separately.

Steps

l Create and enter the AAA Profile configuration mode.

Command: aaa-profile

The command syntax for creating and entering the AAA-Profile configuration mode is:aaa-profile <profile-name>, as described in Table 3-5.

Table 3-5 Description of Commands for Creating and Entering AAA ProfileConfiguration Mode

Value Description

name Name of the AAA Profile, configuration range: 1-64 bit string.


Example

To create and enter the AAA Profile configuration mode whose name is aaa, use thefollowing command:

xGW(config-xgw-pdsn)#aaa-profile aaa

Follow-Up Action

To check the AAA Profile configuration information, use the following command:


To delete the AAA Profile configuration information, use the following command:

xGW(config-xgw-pdsn)#no aaa-profile <profile-name>

3.4.3 Configuring the RADIUS Server IP Address

Prerequisites

You have created and entered an AAA Profile, as described in 3.4.2 Configuring the AAAProfile Name.

Context

This topic describes how to configure the RADIUS server for the created AAA Profile.

3-10



Steps

l Configure the RADIUS server.

Command: radius-server

The command syntax for configuring the RADIUS server is: radius-server <A.B.C.D>[vrf <vrf-name>] [(auth-port <1-65535>)] [(acct-port <1-65535>)], as described inTable 3-6.

Table 3-6 Description of Commands for Configuring the RADIUS Server


- A.B.C.D Address of the RADIUS server.

vrf vrf-nameVRF name, configuration range:1-32 bit

string.

auth-port 1-65535 Authentication port, 1812 by default.

acct-port 1-65535 Charging port, 1813 by default.


Example

1. To create and enter the AAA Profile configuration mode whose name is aaa, use thefollowing command:


2. To add the RADIUS server,IP address 192.168.51.152, VRF name as AAA, asauthentication port as 1812, charging port as 1813, use the following command:

xGW(config-xgw-pdsn-aaa)#radius-server 192.168.51.152 vrf AAA auth-port 1812acct-port 1813

Follow-Up Action

To check the AAA Profile configuration information, use the following command:


To delete the RADIUS server configuration, use the following command:

xGW(config-xgw-pdsn-aaa)#no radius-server <A.B.C.D> [vrf <vrf-name>]

3.4.4 Configuring the IP Address of AAAC

Prerequisites


3-11



ContextThis topic describes how to configure the AAAC address of PDSN for AAA Profile; asthe client of the AAA server, PDSN communicates to the AAA server through the AAACaddress.

Steps

l Add the AAAC address.

Command: client-address

The command syntax for configuring the AAAC address is: client-address <A.B.C.D>[<cpu-location> | global], as described in Table 3-7.

Table 3-7 Description of Commands for Configuring the AAAC Address

Value Description

A.B.C.D AAAC address.

cpu-location

Input the CPU group and group number as per the format of

groupno/intragroupno.

l Groupno: CPU group number with maximum 250 and

minimum 1.

l Intragroupno: CPU within-group number with maximum 5

and minimum 1.

global

If the AAAC address is configured as global, this AAAC

address is used when the domain users using this AAA Profile

access.


Example



2. To add AAAC address 192.168.51.12 for CPU 1 of CPU group 2, use the followingcommand:

xGW(config-xgw-pdsn-aaa)#client-address 192.168.51.12 2/1

Follow-Up ActionTo check the AAA Profile configuration information, use the following command:


To check the AAAC address configuration information in AAA attributes, use the followingcommand:

xGW(config-xgw-pdsn-aaa)#list client

3-12



To delete the AAA Profile configuration information, use the following command:

xGW(config-xgw-pdsn-aaa)#no client-address [<cpu-location> | global]

3.4.5 Configuring the Shared Key

Prerequisites


Context

The shared key is the parameter for authentication between the PDSN and the AAA.

Steps

l Configure the shared key in aaa attributes.

Command: shared-key

The command syntax for configuring the shared key is: shared-key <key>, asdescribed in Table 3-8.

Table 3-8 Description of Commands for Configuring the Shared Key

Value Description

key Shared key, 1–64 characters.


Example



2. To configure the shared key in aaa attributes, use the following command:

xGW(config-xgw-pdsn-aaa)#shared-key pdsn

Follow-Up Action

To check the aaa-profile configuration information, use the following command:


To delete the aaa-profile configuration information, use the following command:

xGW(config-xgw-pdsn-aaa)#no shared-key

3-13



3.4.6 Configuring the NAS Attribute

PrerequisitesYou have created and entered an AAA Profile, as described in 3.4.2 Configuring the AAAProfile Name.

ContextThis topic describes how to configure the IP address and ID of the NAS (Network AccessServer) corresponded to the AAA Profile; the AAA server directs the data services tocorresponding NAS through the IP address and ID of the NAS.

Steps

l Configure the NAS attribute.

Command: nas-identify

The command syntax for configuring the NAS attribute is: nas-identify [<cpu-location>|global] {[nas-id <nas-id-string>] [nas-ip <A.B.C.D>]}, as described in Table 3-9.

Table 3-9 Description of Commands for Configuring the NAS Attribute


- cpu-location

Input the CPU group and group number as per the format

of groupno/intragroupno.

l Groupno: CPU group number with maximum 250

and minimum 1.

l Intragroupno: CPU within-group number with

maximum 5 and minimum 1.- global

If the NAS address is configured as global, domain users

using this AAA Profile for authentication will access the

NAS corresponded to this IP address.nas-id nas-id-string

Identifier of network access server, Configuration range:

1-64 bit string.

nas-ip A.B.C.D NAS IP address.


Example



2. To configure the NAS IP address and NAS ID in aaa attributes, use the followingcommand:

xGW(config-xgw-pdsn-aaa)#nas-identify 2/1 nas-id 2 nas-ip 192.168.52.202

Follow-Up ActionTo check the AAA Profile configuration information, use the following command:


3-14



To check the NAS configuration information, use the following command:

xGW(config-xgw-pdsn-aaa)#list nas

To delete the NAS configuration information, use the following command:

xGW(config-xgw-pdsn-aaa)#no nas-identify {global | <cpu-location>}{nas-id | nas-ip | both}

3.5 Configuration of Interconnection Between thePDSN and the LNS

3.5.1 Configuration Flow of Interconnection Between PDSN andLNS

Refer to the flow as shown in Figure 3-3 to configure the interconnection between thePDSN and the LNS.

Figure 3-3 Configuration Flow of Interconnection Between PDSN and LNS

3.5.2 Configuring the Homing Domain of the LAC

Prerequisites


Context

In PDSN, set user types by setting domains. For example, specify a domain for the VPNusers and specify corresponding LNS server for this domain. When VPN users in thisdomain access, they all access the LNS server corresponded to this domain.

3-15



Steps

l Create and enter the Realm mode (the Realm is not created before), or directly enterthe Realm mode (the Realm is already created).

Command: realm

The command syntax for configuring the Realm is: realm [<realm-name>], asdescribed in Table 3-10.

Table 3-10 Description of Commands for Configuring the Realm

Value Description

realm-name

Name of the Realm. If the parameter realm-name is not carried,

it enters the default domain (domain ID is 0, and the default

domain is created automatically by the system. This default

domain cannot be deleted, while it can be modified by the

command under the domain mode after entering this domain;

the default domain cannot be copied), configuration range:

1-63 bit string


ExampleTo create the Realm whose name is lnsrealm, use the following command:

xGW(config-xgw-pdsn)#realm lnsrealm

Follow-Up ActionTo query the information of all configured domains, use the following command:

xGW(config-xgw-pdsn)#show pdsn realm

To query the basic configuration information in this domain, use the following command:

xGW(config-xgw-pdsn-realm)#list basic-info

To clear the Realm, use the following command:

xGW(config-xgw-pdsn)#clear-realm <realm-name>

3.5.3 Configuring the Default LAC Address

PrerequisitesYou have entered the Realm, as described in 3.5.2 Configuring the Homing Domain of theLAC.

ContextDefault LAC address can only be configured in the default domain.

3-16



When ZXPDSS provides VPN access function, as the client of the LNS (LAC), PDSNcommunicates to the LNS server through the LAC address.

Steps

l Configure the default LAC address of the L2TP.

Command: l2tp lac-ip-address-default

The command syntax for configuring the default LAC address of the L2TP is: l2tp lac-ip-address-default <A.B.C.D> <cpu-location> [vrf <vrf-name>], as described in Table3-11.

Table 3-11 Description of Commands for Configuring the Default LAC


- A.B.C.D Address of the LAC

- cpu-location

Input the CPU group and group

number as per the format of


l Groupno: CPU group number with

maximum 250 and minimum 1.

l Intragroupno: CPU within-group

number with maximum 5 and

minimum 1.


string.


Example

1. To enter the default domain, use the following command:

xGW(config-xgw-pdsn)#realm

2. To configure the default LAC address of the L2TP, use the following command:

xGW(config-xgw-pdsn-realm)#l2tp lac-ip-address-default 192.168.55.12 2/1

Follow-Up Action

To query the configuration information of the L2TP, use the following command:

xGW(config-xgw-pdsn-realm)#list l2tp-lac-ip

3-17



3.5.4 Configuring the Non-default LAC Address

Prerequisites

You have entered the Realm, as described in 3.5.2 Configuring the Homing Domain of theLAC.

Context

Non-default LAC address can only be configured in the non-default domain.

When ZXPDSS provides VPN access function, as the client of the LNS (LAC), PDSNcommunicates to the LNS server through the LAC address.

Steps

l Configure the non-default LAC address of the L2TP.

Command: l2tp lac-ip-address

The command syntax for configuring the non-default LAC address of the L2TP is: l2tplac-ip-address <A.B.C.D> <A.B.C.D> [vrf <vrf-name>] <A.B.C.D> <cpu-location>, asdescribed in Table 3-12.

Table 3-12 Description of Commands for Configuring the Non-default LAC Address


- A.B.C.D LNS address

- A.B.C.D Mask of the LNS address

vrf vrf-name VRF name, configuration range: 1-32 bit string.

- A.B.C.D Address of the LAC

- cpu-location

Input the CPU group and group number as per the

format of groupno/intragroupno.

l Groupno: CPU group number with maximum 250

and minimum 1.

l Intragroupno: CPU within-group number with



Example

To enter the non-default domain, use the following command:

xGW(config-xgw-pdsn)#realm lnsrealm

To configure the non-default LAC address of the L2TP, LNS address as 192.168.54.21,Mask as 255.255.0.0, LAC address as 192.168.53.12, CPU location as 2/1, use thefollowing command:

3-18



xGW(config-xgw-pdsn-realm)#l2tp lac-ip-address 192.168.54.21 255.255.0.0192.168.53.12 2/1

Follow-Up Action

To query the configuration information of the L2TP, use the following command:

xGW(config-xgw-pdsn-realm)#list l2tp-lac-ip

3-19



This page intentionally left blank.

3-20


Chapter 4Configuration of the ServicesTable of Contents

Configuration of the IP Pool........................................................................................4-1Configuration of the Domain .......................................................................................4-7Configuration of the Local Authentication Attributes..................................................4-15Configuration of the MIP Service ..............................................................................4-19Configuration of the Lawful Interception Service .......................................................4-26Configuration of the Offline Charging........................................................................4-36Configuration of the Online Charging........................................................................4-40Configuration of the DPI ...........................................................................................4-48Configuration of the Policy........................................................................................4-58Configuration of the PCC..........................................................................................4-69Configuring SNMP Alarm Management ....................................................................4-77

4.1 Configuration of the IP Pool

4.1.1 Configuration Flow of the IP PoolRefer to the flow as shown in Figure 4-1 to configure the IP pool.

4-1



Figure 4-1 Configuration Flow of IP Pool

4.1.2 Creating an IP Pool

Prerequisites


Context

There are following three types of IP pools:

l local: locally assigns or AAA returns IP pool namel assigned: AAA returns IP addressl aaa: AAA returns IP pool name

Steps

l Create and enter the IP pool mode.

Command: ipv4 ip-pool

4-2


Chapter 4 Configuration of the Services

The command syntax for creating and entering an IP pool is: ipv4 ip-pool {local |assigned | aaa} <pool-name>, as described in Table 4-1.

Table 4-1 Description of Commands for Configuring the IP Pool

Value Description

local IP pool type, locally assigns or AAA returns IP pool name.

assigned IP pool type, AAA returns IP address.

aaa IP pool type, AAA returns IP pool name.

pool-name IP pool name


Example

To create and enter the configuration mode whose name is zteippool, use the followingcommand:

xGW(config-xgw-pdsn)#ipv4 ip-pool local zteippool

Follow-Up Action

To query the IP pool, use the following command:

xGW(config-xgw-pdsn-ipv4)#list

To query the attributes of the local IP pool, use the following command:

xGW(config-xgw-pdsn)#show pdsn ip-pool <pool-name>

To delete the IP pool, use the following command:

xGW(config-xgw-pdsn)#no ipv4 [ip-pool <pool-name>]

4.1.3 Configuring the VRF of the IP Pool

Prerequisites

l The VRF is configured, as described in 2.2.3 Configuring the VRF.l You have created and entered an IP pool, as described in 4.1.2 Creating an IP Pool.

Context

This topic describes how to add the created IP pool into the VRF.

Steps

l Add the created IP pool into the VRF.

Command: vrf

4-3



The command syntax for configuring the VRF of the IP pool is: vrf <vrfname>, asdescribed in Table 4-2.

Table 4-2 Description of Commands for Configuring the VRF of the IP Pool

Value Description

vfrname Name of the created VRF


Example

1. To enter the IP pool, use the following command:


2. To configure the VRF of the IP pool as PI, use the following command:

xGW(config-xgw-pdsn-ipv4)#vrf PI

Follow-Up ActionTo query the IP pool, use the following command:


4.1.4 Configuring the IP Segment of the IP Pool

PrerequisitesYou have created and entered an IP pool, as described in 4.1.2 Creating an IP Pool.

ContextThis topic describes how to add IP segments in the created IP pool.

Steps

l Configure the the IP segment of the IP pool.

Command: segment

The command syntax for configuring the IP segments of the IP pool is: segment<ipstart> <ipend> [mask <mask>] [dhcpgateway <dhcpgateway>] cpulocation<cpulocation> (need-dync-route {disable | enable}), as described in Table 4-3.

Table 4-3 Description of Commands for Configuring the IP Segments


- ipstart Start IP address

ipend End IP address

mask mask Mask of the IP segment

4-4




dhcpgateway dhcpgateway DHCP gateway

cpulocation cpulocation








minimum 0.

disable disable dynamic routeneed-dync-route

enable enable dynamic route


Example



2. To add the IP segment with start IP address as 10.50.0.1, end IP address as10.50.255.254, mask as 255.255.0.0, CPU location as 3/1, and enable dynamicroute, use the following command:

xGW(config-xgw-pdsn-ipv4)#segment 10.50.0.1 10.50.255.254 mask 255.255.0.0 cpulocation 3/1 need-dync-route enable

Follow-Up ActionTo delete the IP segment, use the following command:

xGW(config-xgw-pdsn-ipv4)#no segment <ipstart> <ipend> [mask <mask>] [dhcpgateway <dhcpgateway>] cpulocation <cpulocation>

4.1.5 Setting Priority of the IP Pool

PrerequisitesYou have created and entered an IP pool, as described in 4.1.2 Creating an IP Pool.

ContextThis topic describes how to configure the priority for the created IP pool.

Steps

l Set the priority of the IP pool.

4-5



Command: priority

The command syntax for setting the priority for the IP pool is: priority <0-255>, asdescribed in Table 4-4.

Table 4-4 Description of Commands for Configuring the Priority of the IP Pool

Value Description

0-255Priority of the IP pool, the smaller the value is, the higher

the priority is.


Example



2. To configure the priority of the IP pool, use the following command:

xGW(config-xgw-pdsn-ipv4)#priority 10

Follow-Up Action





4.1.6 Setting External IP Pool Type

Prerequisites

You have created and entered an IP pool, as described in 4.1.2 Creating an IP Pool.

Context

Set the types of the external IP pool. This configuration is designed for the performancestatistics, and users can perform the configuration as required.

Steps

l Set the types of the external IP pool.

Command: report-type

The command syntax for configuring the types of the external IP pool is: report-type{internet | private-wap | private-mail | other }, as described in Table 4-5.

4-6



Table 4-5 Description of Commands for Configuring the Types of the IP Pool

Value Description

internetPublic network users type, indicating that IP addresses of this IP pool are

assigned to the data service users accessing the Internet.

private-wapWAP user type, indicating that IP addresses of this IP pool are assigned to

WAP users.

private-mailMAIL user type, indicating that IP addresses of this IP pool are assigned to

MAIL users.

otherOther user types, indicating that IP addresses of this IP pool are assigned to

users except the Internet users, WAP users, and the MAIL users.


Example



2. To set the type of the external IP pool as internet, use the following command:

xGW(config-xgw-pdsn-ipv4)#report-type internet

Follow-Up Action





4.2 Configuration of the Domain

4.2.1 Configuration Flow of the DomainRefer to the flow as shown in Figure 4-2 to configure the domain.

4-7



Figure 4-2 Configuration Flow of the Domain

4.2.2 Configuring the Domain Name


ContextFor the networking of a PDSN with multiple AAA servers, to enable each AAA server toprocess the authentication and charging information of users evenly, PDSN supports toclassify users according to the domain name. In this way, PDSN can dispatch different

4-8



users to specified AAA servers for authentication and charging according to the domainname of the users, so as to realize load sharing of multiple AAA servers.

Steps

l Create and enter the Realm mode (the Realm is not created before), or directly enterthe Realm mode (the Realm is already created).

Command: realm

The command syntax for configuring the Realm is: realm [<realm-name>], asdescribed in Table 4-6.

Table 4-6 Description of Commands for Configuring the Realm

Value Description

realm-name

Name of the Realm. If the parameter realm-name is not carried, it

enters the default domain (domain ID is 0, and the default domain

is created automatically by the system. This default domain cannot

be deleted, while it can be modified by the command under the

domain mode after entering this domain; the default domain cannot

be copied.), configuration range: 1-63 bit string.


Example

To create the Realm whose name is zte, use the following command:

xGW(config-xgw-pdsn)#realm zte

Follow-Up Action

To query the information of all configured domains, use the following command:

xGW(config-xgw-pdsn)#show pdsn realm



To clear the Realm, use the following command:


4.2.3 Configuring the IP Address of the Active DNS

Prerequisites

You have entered the Realm, as described in 4.2.2 Configuring the Domain Name.

4-9



Context

When a domain adopts the method of assigning IP addresses by a DNS server,corresponding IP address of the active DNS server must be configured.

Steps

l Configure the active DNS IP address.

Command: primary-dns

The command syntax for configuring the IP address of the active DNS is: primary-dns<A.B.C.D>, as described in Table 4-7.

Table 4-7 Description of Commands for Configuring the Active DNS Address

Value Description

A.B.C.D IP address of the active DNS


Example

1. To enter the created domain zte, use the following command:


2. To set the active DNS address as 1.1.1.1, use the following command:

xGW(config-xgw-pdsn-realm)#primary-dns 1.1.1.1

Follow-Up Action



To clear the basic information of all configured domains, use the following command:

xGW(config-xgw-pdsn-realm)#show pdsn realm

To clear the configuration information of a domain, use the following command:


4.2.4 Configuring the IP Address of the Standby DNS

Prerequisites


Context

This topic describes how to configure the standby DNS for the created domain.

4-10



Steps

l Configure the standby DNS IP address.

Command: secondary-dns

The command syntax for configuring the IP address of the standby DNS is: secondary-dns <A.B.C.D>, as described in Table 4-8.

Table 4-8 Description of Commands for Configuring the Standby DNS Address

Value Description

A.B.C.D IP address of the standby DNS


Example



2. To set the standby DNS address as 2.2.2.2, use the following command:

xGW(config-xgw-pdsn-realm)#secondary-dns 2.2.2.2

Follow-Up ActionTo query the basic configuration information in this domain, use the following command:


To check the basic information of all configured domains, use the following command:




4.2.5 Configuring the IP Pool of a Domain

Prerequisites

l You have entered the Realm, as described in 4.2.2 Configuring the Domain Name.l The IP pool exists.

ContextThis topic describes how to configure the IP pool for the created domain, and all users inthis domain will get IP addresses from this IP pool.

Steps

l Configure the IP pool of a domain.

4-11



Command: ippool

The command syntax for configuring the IP pool of a domain is: ippool <pool-name>,as described in Table 4-9.

Table 4-9 Description of Commands for Configuring the IP Pool of a Domain

Value Description

pool-nameIP pool name; obtain corresponding IP pool from the IP

pool list according to this name.


Example



2. To set the IP pool name of the domain as zteippool, use the following command:

xGW(config-xgw-pdsn-realm)#ippool zteippool

Follow-Up ActionTo query the basic configuration information in this domain, use the following command:


To clear the basic information of all configured domains, use the following command:




4.2.6 Configuring the AAA Profile for Authentication

Prerequisites

l You have entered the Realm, as described in 4.2.2 Configuring the Domain Name.l The Profile is configured.

ContextSet an authentication AAA Profile corresponded to a domain; when users in this domainoriginate data service requests, the authentication function is provided by correspondingAAA Profile.

Steps

l Set the AAA Profile used for authentication.

Command: auth aaa-profile

4-12



The command syntax for configuring the AAA Profile used for authentication is: authaaa-profile <profile-name>, as described in Table 4-10.

Table 4-10 Description of Commands for Configuring the AAA Profile Used forAuthentication

Value Description

profile-name Name of the authentication AAA Profile


Example



2. To configure the name of the authentication AAA Profile as aaaauth, use the followingcommand:

xGW(config-xgw-pdsn-realm)#auth aaa-profile aaaauth

Follow-Up ActionTo clear the authentication AAA Profile, use the following command:

xGW(config-xgw-pdsn)#no auth aaa-profile

4.2.7 Configuring Realm Charging Mode

PrerequisitesYou have entered the Realm, as described in 4.2.2 Configuring the Domain Name.

ContextThere are following two charging methods in the Realm:

l Offline normal chargingl Online + Offline charging

PDSN support content charge function, there are following three content charge functionmethods:

l Offline content chargel Online content chargel Offline and online content charge

Steps1. Configure realm charging mode.

Command: charge mode

4-13



The command syntax for configuring realm charging mode is: charge mode {disable |offline | offline-and-online}, as described in Table 4-11.

Table 4-11 Description of Commands for Configuring Realm Charging Mode

Value Description

disable Not support charge

offline Offline normal charging

offline-and-online Online + Offline charging

2. Configure content charge attribute.

Command: charge attribute

The command syntax for configuring content charge attribute is: charge attribute{disable | ({offline | online | offline-and-online} <1-4096>)}, as described in Table 4-12.

Table 4-12 Description of Commands for Configuring Content Charge Attribute

Value Description

disable Disable content charge

offline Enable offline content charge

online Enable online content charge

offline-and-online Enable offline and online content charge

1-4096Content charge template ID. If disable content charge,

the ID is 0.


Example



2. To configure realm charging mode as offline and online, use the following command:

xGW(config-xgw-pdsn-realm)#charge mode offline-and-online

3. To configure content charge attribute as offline and online, and content chargetemplate ID as 20, use the following command:

xGW(config-xgw-pdsn-realm)#charge attribute offline-and-online 20

4.2.8 Configuring the AAA Profile for Domain Charging

Prerequisites

l You have entered the Realm, as described in 4.2.2 Configuring the Domain Name.l The Profile is configured.

4-14



Context

ZXPDSS provides the function to differentiate different charging methods according to thedomains, therefore, different domains can differentiate the charging methods by specifyingAAA Profiles.

Steps

l Configure the AAA Profile used for charging.

Command: charge aaa-profile

The command syntax for configuring the AAA Profile used for charging is: charge aaa-profile <profile-name>, as described in Table 4-13.

Table 4-13 Description of Commands for Configuring the AAA Profile Used forCharging

Value Description

profile-name Name of the charging AAA Profile


Example



2. To configure the name of the charging AAA Profile as aaachar, use the followingcommand:

xGW(config-xgw-pdsn-realm)#charge aaa-profile aaachar

4.3 Configuration of the Local Authentication Attributes

4.3.1 Introduction to Types of Local Authentication

Description

The PDSN local authentication function means that when the AAA is down or faulty, PDSNcan authenticate users according to the locally saved user names, passwords, and otheruser attributes, so as to enable users to access smoothly.

Types of Local Authentication

Currently, the system supports to perform local authentication on SIP users and L2TPusers.

l Local authentication on SIP users

4-15



The PDSN can authenticate Simple IP users according to the locally saved Simple IPuser names, passwords, and other user attributes, so as to enable users to accesssmoothly.

l Local authentication on L2TP users

The PDSN can authenticate L2TP users according to the locally saved L2TP usernames, passwords, and other user attributes, so as to enable users to accesssmoothly.

4.3.2 Configuring the Local Authentication Attributes of the SIP

Prerequisites

l You have logged in to the configuration window.l You have created an IP pool, as described in 4.1.2 Creating an IP Pool.l The VRF is created, as described in 2.2.3 Configuring the VRF.

Context

This topic describes how to configure the local authentication attributes of the SIP.

Steps

l Configure the local authentication attributes of the SIP.

Command: sip-local-authentication-user

The command syntax for configuring the SIP local authentication attributes is: sip-local-authentication-user <username> {[password <password>] [vrf <vrf-name>] [ippool <ip-pool-name>] [primary <A.B.C.D>] [secondary <A.B.C.D>] [{checkpwd |no-checkpwd}]}, as described in Table 4-14.

Table 4-14 Description of Commands for Configuring the Local AuthenticationAttributes of the SIP


- usernameName of the user accessed, configuration range: 1-63

bit string.

password passwordPassword of the user accessed, configuration range:

1-16 bit string.


ippool ip-pool-name IP pool name, configuration range: 1-20 bit string.

primary A.B.C.D Active DNS address

secondary A.B.C.D Standby DNS

- checkpwd Verifies the user password.

4-16




- no-checkpwd Does not verify the user password.


Example

To set the SIP user name as 163, password as 163, not verifying the user password, IPpool name as zteippool, active DNS as 3.3.3.1, standby DNS as 3.3.3.2, and VRF as PI,use the following command:

xGW(config-xgw-pdsn)#sip-local-authentication-user 163 password 163 ippool zteippoolprimary 3.3.3.1 secondary 3.3.3.2 vrf PI no-checkpwd

Follow-Up Action

To clear the configuration of the IP pool of a user, use the following command:

xGW(config-xgw-pdsn)#clear-sip-local-auth-ippool <username>

To clear the configuration of the user name and the password of a user, use the followingcommand:

xGW(config-xgw-pdsn)#clear-sip-local-auth-password <username>

To delete a simple local authentication user, use the following command:

xGW(config-xgw-pdsn)#no sip-local-authentication-user <username>

To delete the configuration of active or standby DNS, use the following command:

xGW(config-xgw-pdsn)#clear-sip-local-auth-dns <username> {primary | secondary | both}

To query the configured local authentication, use the following command:

xGW(config-xgw-pdsn)#show pdsn sip-local-authentication-user

4.3.3 Configuring the Local Authentication Attributes of the L2TP

Prerequisites

l You have logged in to the configuration window.l The VRF is created, as described in 2.2.3 Configuring the VRF.

Context

This topic describes how to configure the local authentication attributes of the L2TP.

Steps

l Configure the local authentication attributes of the L2TP.

Command: l2tp local-authentication-user

4-17



The command syntax for configuring the L2TP local authentication attributes is: l2tplocal-authentication-user <user-name> {[userpwd <user-password>] [vrf <vrf-name>][tunnelip <A.B.C.D>] [tunnelpwd <tunnel-password>] [{checkpwd | no-checkpwd}]},as described in Table 4-15.

Table 4-15 Description of Commands for Configuring the Local AuthenticationAttributes of the L2TP


- user-nameName of the user accessed, configuration range: 1-63

bit string.

userpwd user-passwordPassword of the user accessed, configuration range:

1-16 bit string.


tunnelip A.B.C.D IP address of the tunnel terminal, that is the LNS

tunnelpwd tunnel-password Password of the tunnel

- checkpwd Verifies the user password.

- no-checkpwd Does not verify the user password.


Example

To set the L2TP user name as l2tpusr, password as l2tp, verifying the user password, IPaddress of the tunnel terminal as 4.4.4.1, password of the tunnel as tunnela, and VRF asVPDN, use the following command:

xGW(config-xgw-pdsn)#l2tp local-authentication-user l2tpusr userpwd l2tp vrf VPDN tunnelip 4.4.4.1 tunnelpwd tunnela checkpwd

Follow-Up Action

To clear the user password of the L2TP local authentication user, including the tunnelpassword and the user password, use the following command:

xGW(config-xgw-pdsn)#l2tp clear-local-auth-password <user-name> {userpwd | tunnelpwd| both}

To clear the L2TP local authentication user, use the following command:

xGW(config-xgw-pdsn)#no l2tp local-authentication-user <user-name>

To query the L2TP local authentication user, use the following command:

xGW(config-xgw-pdsn)#show pdsn l2tp local-authentication-user

4-18



4.4 Configuration of the MIP Service

4.4.1 Configuration Flow of the MIP ServiceMIP is a solution providing the mobile data communication function on the global Internet;when users access the cdma2000 network using the MIP method, they can move freelywithin the network range while keep the same IP addresses; MS can keep servicecontinuity when crossing the PDSN, and does not need to terminate the previous service.When users require roaming, the operators can provide the MIP access method for them.

Refer to the flow as shown in Figure 4-3 to configure the MIP service.

Figure 4-3 Configuration Flow of MIP Service

4.4.2 Configuring the FA-HA Security Association

Prerequisites


Context

To ensure the security communication between the PDSN and the HA, configure thesecurity association between the PDSN and the HA, that is, configure the FA-HA securityassociation.

4-19



Steps

l Add the FA-HA security association.l To add a single FA-HA security association, refer to 3.3.1 Configuring the FA-HA

Security Association.l To add the FA-HA security association in batch, refer to 3.3.2 Configuring the

FA-HA Security Association IP Segment.


4.4.3 Configuring the COA Address

Prerequisites

l You have logged in to the configuration window.l The CPU group configuration is complete.

ContextConfiguring the COA address is to configure the FA address of the MIP. The COA addressis used for the communication with the HA; when the PDSN supports the MIP function,this address should be configured.

Steps

l Configure the COA address.

Command: mip coa-ip-address

The command syntax for configuring the COA address is: mip coa-ip-address<A.B.C.D> <cpu-location> [(vrf <vrf-name>)], as described in Table 4-16.

Table 4-16 Description of Commands for Configuring the COA Address


- A.B.C.DCOA address, that is the service IP

address of the PI interface of the PDSN.


string.

- cpu-location








minimum 1.


4-20



ExampleTo configure the COA address as 192.168.54.12, the VRF name as MIP, and the CPUlocation as 3/1, use the following command:

xGW(config-xgw-pdsn)#mip coa-ip-address 192.168.54.12 3/1 vrf MIP

To configure a COA address not carrying the VRF attribute, use the following command:

xGW(config-xgw-pdsn)#mip coa-ip-address 192.168.54.12 3/1

Follow-Up ActionTo query the COA address of the MIP, use the following command:

xGW(config-xgw-pdsn)#show pdsn service-ip-address

To delete a COA address, use the following command:

xGW(config-xgw-pdsn)#no mip coa-ip-address <A.B.C.D> [(vrf <vrf-name>)]

4.4.4 Configuring the MIP Parameter

Prerequisites

l You have logged in to the configuration window.l The FA-HA Security Association is configuredas described in 3.3.1 Configuring the

FA-HA Security Association and 3.3.2 Configuring the FA-HA Security Association IPSegment.

ContextConfigure the MIP parameter, including timeout of HA authentication reply, timeoutof AAA authentication reply, interval of sending proxy broadcast or times of sendingproxy broadcast, support registration revocation, length of FAC, support PMIP type,maximal times of send Reg_Req for PMIP and refresh time before expired for PMIP,enable or disable PMIP use reverse tunnel, MN-HA authentication algorithm type, agentadvertisement gbit, enable or disable carrying null attribute in mip rrq.

Steps1. Configure timeout of HA authentication reply.

Command: mip authentication-timeout-ha

The command syntax for configuring timeout of HA authentication reply is: mip authentication-timeout-ha <1-15>, as described in Table 4-17.

Table 4-17 Description of Commands for Configuring Timeout of HA AuthenticationReply

Value Description

1-15Timeout of HA authentication reply value configuration

range: 1–15s.

4-21



2. Configure timeout of AAA authentication reply.

Command: mip authentication-timeout-aaa

The command syntax for Configuring timeout of AAA authentication reply is: mip authentication-timeout-aaa <1-20>, as described in Table 4-18.

Table 4-18 Description of Commands for Configuring Timeout of AAAAuthentication Reply

Value Description

1-20Timeout of AAA Authentication Reply value, configuration

range: 1–20s.

3. Configure interval of sending proxy broadcast or times of sending proxy broadcast.

Command: mip advertisement

The command syntax for Cconfiguring interval of sending proxy broadcast or timesof sending proxy broadcast is: mip advertisement [(interval <1-3>)] [(max-retransmit<0-2>)], as described in Table 4-19.

Table 4-19 Description of Commands for Configuring Interval of Sending ProxyBroadcast or Times of Sending Proxy Broadcast


timeout 1-3Interval of advertisement valueconfigu-

ration range: 1–3s.

max-retransmit 0-2

Key name of Times of

advertisement configuration range:

1–3 times.

4. Configure support registration revocation.

Command: mip registration-revocation

The command syntax for configuring support registration revocation is: mip registration-revocation {disable| no-stc-disable | no-stc-enable}, as described in Table 4-20.

Table 4-20 Description of Commands for Configuring Support RegistrationRevocation

Value Description

disable Not support registration revocation

no-stc-disable Not support when no stc returned

no-stc-enable Support when no stc returned

5. Configure length of FAC.

Command: mip fac-length

4-22



The command syntax for is configuring length of FAC: mip fac-length <4-238>, asdescribed in Table 4-21.

Table 4-21 Description of Commands for Configuring Length of FAC

Value Description

4-238 Length of FAC, configuration range: 4–238Bytes

6. Configure support PMIP type.

Command: mip pmip-support

The command syntax for Configuring support PMIP type is: mip pmip-support {disable| (pmip {zte | telm})}, as described in Table 4-22.

Table 4-22 Description of Commands for Configuring Support PMIP Type


- disable Not Support PMIP

ztepmip

telm

Key name of support PMIP type, support

ZTE PMIP and telecom PMIP.

7. Configure maximal times of send Reg_Req for PMIP and refresh time before expiredfor PMIP.

Command: mip pmip

The command syntax for configuring maximal times of send Reg_Req for PMIP andrefresh time before expired for PMIP is: mip pmip [(retransmit <0-2>)] [(timeout<1-99>)], as described in Table 4-23.

Table 4-23 Description of Commands for Configuring Maximal Times of SendReg_Req for PMIP and Refresh Time Before Expired for PMIP


retransmit 0-2Maximal times of send Reg_Req for PMIP

value, configuration range: 0–2 times.

timeout 1-99Refresh time before expired for PMIP

valueconfiguration range: 1–99s.

8. Configure PMIP use reverse tunnel.

Command: mip pmip-use-reverse-tunnel

The command syntax for configuring PMIP use reverse tunnel is: mip pmip-use-reverse-tunnel {enable | disable}, as described in Table 4-24.

Table 4-24 Description of Commands for Configuring PMIP Use Reverse Tunnel

Value Description

enable Enable PMIP use reverse tunnel

4-23



Value Description

disable Disable PMIP use reverse tunnel

9. Configure MN-HA authentication algorithm type.

Command: mip mn-ha-auth-algorithm

The command syntax for configuring MN-HA authentication algorithm type is: mipmn-ha-auth-algorithm{rfc2002 | rfc2002bis | rfc3344}, as described in Table 4-25.

Table 4-25 Description of Commands for Configuring MN-HA AuthenticationAlgorithm Type

Value Description

rfc2002 rfc2002 type

rfc2002bis rfc2002bis type

rfc3344 rfc3344 type

10. Configure agent advertisement gbit.

Command: mip agent-advertisement-gbit

The command syntax for is configuring agent advertisement gbit: mip agent-advertisement-gbit <0-1>, as described in Table 4-26.

Table 4-26 Description of Commands for Configuring Agent Advertisement Gbit

Value Description

0-1 Agent advertisement G bit, configuration range: 0 or 1

11. Configrue carrying null attribute in mip rrq when no location information in a11 rrq.

Command: mip location-null

The command syntax for is configruing carrying null attribute in mip rrq: mip location-null {enable | disable}, as described in Table 4-27.

Table 4-27 Description of Commands for Configruing Carrying Null Attribute inMip Rrq

Value Description

enable Disable carrying null attribute in mip rrq

disable Enable carrying null attribute in mip rrq

12. Configure maximal time of MIP establishing.

Command: mip max-sessiontime

The command syntax for is configuring maximal time of MIP establishing: mip max-sessiontime <3-100>, as described in Table 4-28.

4-24



Table 4-28 Description of Commands for Configuring Maximal Time of MIPEstablishing

Value Description

3-100Maximal time of MIP establishing, the range is 3-100

seconds

13. Configure maximal times and interval of register revocation.

Command: mip register-revocation

The command syntax for is configuring maximal times and interval of registerrevocationmip register-revocation [retransmit <2-9>] [timeout <2-5>], as describedin Table 4-29.

Table 4-29 Configure Maximal Times and Interval of Register Revocation


retransmit 2-9Maximal retransmit of register revocation

value, the range is 2-9

timeout 2-5Maximal timeout of register revocation

value, the range is 2-5 seconds

14. Configure revocation extention I bit flag value.

Command: mip revocation-extension-i-bit

The command syntax for is configuring revocation extention I bit flag value: mip revocation-extension-i-bit <0-1>, as described in Table 4-30.

Table 4-30 Configuring Revocation Extention I bit Flag Value.

Value Description

0-1 Revocation extension I bit flag value


Example

1. Timeout of HA authentication reply value as 10s, use the following command:

xGW(config-xgw-pdsn-realm)#mip authentication-timeout-ha 10

2. Timeout of AAA authentication reply value as 10s, use the following command:

xGW(config-xgw-pdsn-realm)#mip authentication-timeout-aaa 10

3. Times of advertisement value as 2, tnterval of advertisement value as 2, use thefollowing command:

xGW(config-xgw-pdsn-realm)#mip advertisement interval 2 max-retransmit 2

4. Support when no stc returned, use the following command:

4-25



xGW(config-xgw-pdsn-realm)#mip registration-revocation no-stc-enable

5. Length of FAC 200 bytes, use the following command:

xGW(config-xgw-pdsn-realm)#mip fac-length 200

6. Support ZTE PMIP, use the following command:

xGW(config-xgw-pdsn-realm)#mip pmip-support pmip zte

7. Maximal Times of Send Reg_Req for PMIP value as 2, refresh time before expired forPMIP value 60s, use the following command:

xGW(config-xgw-pdsn-realm)#mip pmip retransmit 2 timeout 60

8. Enable PMIP use reverse tunnel, use the following command:

xGW(config-xgw-pdsn-realm)#mip pmip-use-reverse-tunnel enable

9. Configure MN-HA authentication algorithm type as rfc2002, use the followingcommand:

xGW(config-xgw-pdsn-realm)#mip mn-ha-auth-algorithm rfc2002

10. Agent advertisement G bit as 1, use the following command:

xGW(config-xgw-pdsn-realm)#mip agent-advertisement-gbit 1

11. Disable carrying null attribute in mip rrq, use the following command:

xGW(config-xgw-pdsn-realm)#mip location-null enable

12. Configure maximal time of MIP establishing as 10 seconds, use the followingcommand:

xGW(config-xgw-pdsn-realm)#mip max-sessiontime 10

13. Configure maximal times as 5, and interval of register revocation as 3 seconds, usethe following command:

xGW(config-xgw-pdsn-realm)#mip register-revocation retransmit 5 timeout 3

14. Revocation extension I bit flag value as 1, use the following command:

xGW(config-xgw-pdsn-realm)#mip revocation-extension-i-bit 1

Follow-Up ActionRecover current configuration for MIP configuration to be default values, use the followingcommand:

xGW(config-xgw-pdsn)#mip default

4.5 Configuration of the Lawful Interception Service

4.5.1 Configuration Flow of the Lawful Interception ServiceRefer to the flow as shown in Figure 4-4 to configure the lawful interception service.

4-26



Figure 4-4 Configuration Flow of the Lawful Interception Service

4.5.2 Configuring the Basic Information of the PDSN LawfulInterception

Prerequisites


4-27



Context

When providing the lawful interception service, as the client of the LIC, the PDSNcommunicates to the LIC through the LIG.

l The X1 interface is called the control disposal interface, and this interface is used forthe interaction of lawful interception command messages between the PDSN and theLIC.

l The X2 interface is used for LIG to report the communication events of the monitoredobjects to the LIC.

Steps

l Configure the local end information of the lawful interception.

Command: lic local

The command syntax for configuring the local end information of the lawful interceptionis: lic local {[ne-id <1-1000>] [ipaddr <A.B.C.D>] [port <15000-15999>] [password<password-string>] [cpu <cpu-location>]}, as described in Table 4-31.

Table 4-31 Description of Commands for Configuring the Local End Information ofthe Lawful Interception


ne-id 1-1000 NE ID of the PDSN

ipaddr A.B.C.D

Service address of the lawful

interception, that is the address

for communication between the PDSN

and the LIG.

port 15000-15999 X1/X2 lawful interception port No.

password password-string Password for logging in to the LIG

cpu cpu-location

CPU location, with the format as

groupno/intragroupno. groupno is the

No. of the CPU group (ranging 1~250),

while intragroupno is the ID of the CPU

inside the group (ranging 1~5).


Example

To configure the CPU 1 of the CPU group 3 with the service address of the lawfulinterception as 192.168.51.21, the password for logging in to the LIG as 123456, theX1/X2 interception port No. as 15003, use the following command:

xGW(config-xgw-pdsn)#lic local ne-id 3 ipaddr 192.168.51.21 port 15003 password123456 cpu 3/1

4-28



Follow-Up ActionTo delete the basic information configuration of the lawful interception, use the followingcommand:

xGW(config-xgw-pdsn)#lic clear local

4.5.3 Configuring the Interception Types


ContextConfigure the types and sub-types of the lawful interception.

The lawful interception includes four standard types: China, ETSI, CALEA, and VERINT.

l China

The "China" is the lawful interception standard specified by China.

If the lawful interception interface adopts the "China" standard, the interfaces X1 andX2 use TCP for communication, while the interface X3 uses UDP for communication.

l ETSI

European Telecommunications Standards Institute (ETSI) is an independentnon-profit organization in Europe, whose main job is to make standards fortelecommunications.

If the lawful interception interface adopts the "ETSI" standard, the interface X1uses TELNET for communication, while the interfaces X2 and X3 use FTP forcommunication.

l CALEA

Communications Assistance for Law Enforcement Act (CALEA) is a communicationmanagement act in United States, and many telecommunications vendors make ajoint interception standard according to it.

If the lawful interception interface adopts the "CALEA" standard, the interface X1uses TELNET for communication, while the interfaces X2 and X3 use TCP forcommunication.

l VERINT

VERINT is a private interception standard of third-party middleware vendors.

l If the lawful interception interface adopts the "VERINT" standard, the interfaces X1,X2, and X3 all use TCP for communication.

Steps

l Configure the types and sub-types of the lawful interception.

4-29



Command: lic intercept-type

The command syntax for configuring the types and sub-types of the lawful interceptionis: lic intercept-type {[{china | etsi | calea | verint}] [subtype <0-3>]}, as described inTable 4-32.

Table 4-32 Description of Commands for Configuring Types and Sub-types ofthe Lawful Interception


- china

- etsi

- calea

- verint

Types of the interception: China, ETSI,

CALEA, and VERINT.

subtype 0-3Sub-type of the lawful interception,

ranging 0-3.


ExampleTo configure the types as verint and sub-types as 3 of the lawful interception, use thefollowing command:

xGW(config-xgw-pdsn)#lic intercept-type verint subtype 3

4.5.4 Configuring the Remote Gateway Address of the LawfulInterception


ContextThe LIG is the interface between the PDSN and the LIC; it realizes the adaption of variouslawful interception standards, completes the interaction between the LIC and the PDSN,and accomplishes the lawful interception function cooperating with the PDSN.

Here we introduce the IP addresses of the LIG corresponded to the interfaces X1 and X2.

Steps

l Configure the remote gateway address of the lawful interception.

Command: lic x1-x2-gateway

The command syntax for configuring the remote gateway address of the lawfulinterception is: lic x1-x2-gateway <A.B.C.D>, as described in Table 4-33.

4-30



Table 4-33 Description of Commands for Configuring the Remote Gateway Addressof the Lawful Interception

Value Description

A.B.C.D IP address of the remote gateway


ExampleTo configure the remote gateway address of the lawful interception, use the followingcommand:

xGW(config-xgw-pdsn)#lic x1-x2-gateway 192.168.81.39

Follow-Up ActionTo delete the remote gateway address of the lawful interception, use the followingcommand:

xGW(config-xgw-pdsn)#no lic x1-x2-gateway

4.5.5 Configuring the Remote End Types of the Lawful Interception


ContextThe X3 interface accomplishes the function that the LIG outputs the communicationcontents (voice or packet data services) and the correlation ID of the monitored objectsto the LIC in real time.

Steps

l Configure the remote end types of the lawful interception.

Command: lic x3 dest-type

The command syntax for configuring the remote end types of the lawful interceptionis: lic x3 dest-type {controller | gateway}, as described in Table 4-34.

Table 4-34 Description of Commands for Configuring the Remote End Types ofthe Lawful Interception

Value Description

controller The X3 communicates to the LIC without using the gateway.

gateway The X3 communicates to the LIC through the gateway.


4-31



Example

To configure the remote end type of the lawful interception, use the following command:

xGW(config-xgw-pdsn)#lic x3 dest-type gateway

4.5.6 Configuring the Gateway Address and the Port of the InterfaceX3

Prerequisites


Context

This topic describes how to configure the gateway address and the port of the interfaceX3.

Steps

l Configure the gateway address and the port of the interface X3.

Command: lic x3 gateway

The command syntax for configuring the gateway address and the port of the interfaceX3 is: lic x3 gateway {[sig-ip <A.B.C.D>] [sig-port <0-65535>] [media-ip <A.B.C.D>][media-port <0-65535>]}, as described in Table 4-35.

Table 4-35 Description of Commands for Configuring the Gateway Address and thePort of the Interface X3


sig-ip A.B.C.D Signaling plane address of the X3 gateway

sig-por 0-65535 Signaling plane port of the X3 gateway

media-ip A.B.C.D Media plane address of the X3 gateway

media-port 0-65535 Media plane port of the X3 gateway


Example

To configure the X3 gateway address and the port of the lawful interception, use thefollowing command:

xGW(config-xgw-pdsn)#lic x3 gateway sig-ip 194.136.36.131 sig-port 2222 media-ip194.136.36.131 media-port 2222

4-32



Follow-Up Action

To query the basic information of the local end of the lawful interception configured, usethe following command:

xGW(config-xgw-pdsn)#show pdsn lic

4.5.7 Configuring the Local Port of the Interface X3

Prerequisites


Context

Configure the local port of the interface X3.

Steps

l Configure the local port of the interface X3.

Command: lic x3 local port

The command syntax for configuring the local port of the interface X3 is: lic x3 localport {[sig-port <15000-15999>] [media-port <15000-15999>]}, as described in Table4-36.

Table 4-36 Description of Commands for Configuring the Local Port of the InterfaceX3


sig-port 15000-15999 Local signaling plane port of the X3

media-port 15000-15999 Local media plane port of the X3


Example

To configure the local media plane and signaling plane ports of the lawful interception X3,use the following command:

xGW(config-xgw-pdsn)#lic x3 local port sig-port 15002 media-port 15001

Follow-Up Action



4-33



4.5.8 Configuring the Local Media Plane IP Address of the InterfaceX3

Prerequisites


Context

Configure the local media plane IP address of the interface X3.

Steps

l Configure the local media plane IP address of the interface X3.

Command: lic x3 local media-ip

The command syntax for configuring the local media plane IP address of the interfaceX3 is: lic x3 local media-ip <cpu-location> <A.B.C.D>, as described in Table 4-37.

Table 4-37 Description of Commands for Configuring the Local Media Plane IPAddress of the Interface X3

Value Description

cpu-location

CPU location, with the format as groupno/intragroupno.

groupno is the No. of the CPU group (ranging 1~250), while

intragroupno is the ID of the CPU inside the group (ranging

1~5).

A.B.C.D Local media plane IP address of the interface X3


Example

To configure the local media plane IP address of the lawful interception X3, use thefollowing command:

xGW(config-xgw-pdsn)#lic x3 local media-ip 3/1 192.168.51.33

Follow-Up Action



To delete the basic information of the local media plane IP address of the interface X3, usethe following command:

xGW(config-xgw-pdsn)#no media-ip <cpu-location>

4-34



4.5.9 Configuring the Link Detection Parameters of the Interface X3

Prerequisites


Context

When setting to support the detection, this function can be used to check the status ofthe interface X3 between the PDSN and the LIG. If no response from the LIG is receivedwhen the retry times of the link detection exceed the preset value, PDSN determines thatthe interface X3 link with the LIG is broken.

Steps

l Configure the link detection parameters of the interface X3.

Command: lic x3 link-detection

The command syntax for configuring the link detection parameters of the interface X3is: lic x3 link-detection {[{enable | disable}] [retries <3-10>] [interval <10-3600>]}, asdescribed in Table 4-38.

Table 4-38 Description of Commands for Configuring the Link Detection Parametersof the Interface X3


- enable Supports the interface X3 link detection.

- disableDoes not support the interface X3 link

detection.

retries 3-10Number of times of retrying the interface X3

link detection

interval 10-3600Interval for retrying the interface X3 link

detection


Example

To configure the link detection parameters of the interface X3, use the following command:

xGW(config-xgw-pdsn)#lic x3 link-detection enable retries 3 interval 10

Follow-Up Action



4-35



To delete the X3 configuration information of the lawful interception, use the followingcommand:

xGW(config-xgw-pdsn)#lic clear x3-intercept

4.6 Configuration of the Offline Charging

4.6.1 Configuration Flow of the Offline ChargingWhen the system supports offline charging, offline charging related information should beconfigured, and the configuratin flow is as shown in Figure 4-5.

Figure 4-5 Configuration Flow of the Offline Charging

4.6.2 Configuring Offline Charging Modes

Prerequisites

l The offline charging mode is adopted in the Realm configuration, as described in 4.2.7Configuring Realm Charging Mode.

l You have entered the Realm, as described in 4.2.2 Configuring the Domain Name.

4-36



ContextThere are three modes for the offline charging:

l Charging by timel Charging by flowl Charging by time + flow

Steps

l Set the offline charging mode.

Command: charge offline mode

The command syntax for setting the offline charging mode is: charge offline mode {time| flow | time-flow}, as described in Table 4-39.

Table 4-39 Description of Commands for Setting the Offline Charging Modes

Value Description

time Charging by time

flow Charging by flow

time-flow Charging by time + flow


ExampleTo set the offline charging mode as time + flow, use the following command:

xGW(config-xgw-pdsn-realm)#charge offline mode time-flow

4.6.3 Setting the Offline Charging Threshold

Prerequisites



ContextSet the offline charging flow threshold and time threshold.

Steps1. Set the offline charging flow threshold.

Command: charge offline flow-threshold

The command syntax for setting the offline charging flow threshold is: charge offlineflow-threshold <100-4000000> as described in Table 4-40.

4-37



Table 4-40 Description of Commands for Setting Offline Charging Flow Threshold

Value Description

100-4000000 Offline charging flow threshold range is 100-4000000 KByte.

2. Set the offline charging time threshold.

Command: charge offline time-threshold

The command syntax for setting the offline charging time threshold is: charge offlinetime-threshold <6-1440>, as described in Table 4-41.

Table 4-41 Description of Commands for Setting Offline Charging Time Threshold

Value Description

6-1440 Offline charging time threshold range is 6-1440 minutes


Example

1. To set the offline charging flow threshold as 1000Kbyte, use the following command:

xGW(config-xgw-pdsn-realm)#charge offline flow-threshold 1000

2. To set the offline charging time threshold as 60 minutes, use the following command:

xGW(config-xgw-pdsn-realm)#charge offline time-threshold 60

4.6.4 Setting CDR Filtering

Prerequisites



Context

Different CDRs can be filtered during the offline charging.

Steps

l Set the CDR filtering.

Command: charge offline cdr-filt

The command syntax for setting the CDR filtering is: charge offline cdr-filt {all |plmn-change | prepaid | qos-change | rat-change | sgsnip-change | timezone-change}{disable | enable}, as described in Table 4-42.

4-38



Table 4-42 Description of Commands for Setting the CDR Filtering

Value Description

all Exports all CDRs

plmn-change Exports PLMN changed CDRs

prepaid Prepaid users exporting CDRs

qos-change Exports QoS changed CDRs

rat-change Exports RAT changed CDRs

sgsnip-change Exports SGSN changed CDRs

timezone-change Exports time zone changed CDRs

disable Enable the CDR filtering

enable Disable the CDR filtering


ExampleTo filter all CDRs, use the following command:

xGW(config-xgw-pdsn-realm)#charge offline cdr-filt all enable

4.6.5 Setting the Offline Charging Tariff

Prerequisites



ContextThe charging standards may be different at different time during the offline charging,therefore, the offline charging tariff should be set.

Steps

l Set the offline charging tariff.

Command: charge offline tariff

The command syntax for setting the offline charging tarrif is: charge offline tariff begin<hh:mm> end <hh:mm> rate <0-100>, as described in Table 4-43.

Table 4-43 Description of Commands for Setting the Offline Charging Tariff


begin hh:mm Begin time

4-39




end hh:mm End time

rate 0-100 Charging rate, ranging 0–100(%)


Example

To set the offline charging tariff begin time as 1:00:00, end time as 2:00:00, and thecharging rate as 50%, use the following command:

xGW(config-xgw-pdsn-realm)#charge offline tariff begin 1:00:00 end 2:00:00 rate 50

4.7 Configuration of the Online Charging

4.7.1 Configuration Flow of the Online ChargingWhen the system supports the online charging, online charging related information shouldbe configured, and the configuration flow is as shown in Figure 4-6.

4-40



Figure 4-6 Configuration Flow of Online Charging

4-41



4.7.2 Setting the Online Charging Diameter Adjacent Office

Prerequisites

l The online charging mode is adopted in the Realm configuration, as described in 4.2.7Configuring Realm Charging Mode.


Context

Online charging uses the content charging mode, and the online charging Diameteradjacent office should be set.

Steps

l Set the online charging diameter adjacent office.

Command: charge online ocs-host

The command syntax for setting the online charging Diameter adjacent office is: charge online ocs-host <adjacent-node-name>, as described in Table 4-44.

Table 4-44 Description of Commands for Setting the Online Charging DiameterAdjacent Office

Value Description

adjacent-node-name Name of the online charging Diameter adjacent office


Example

To set the name of the online charging Diameter adjacent office as dmtsrv001.zte.com.cn,use the following command:

xGW(config-xgw-pdsn-realm)#charge online ocs-host dmtsrv001.zte.com.cn

Follow-Up Action

To view the online charging information, use the following command:

xGW(config-xgw-pdsn-realm)#charge list

4.7.3 Setting the Online Charging Quota Validation Time

Prerequisites



4-42



Context

Set to consume certain amount of money in a certain time; if it is not run out within thistime, the quota will be unavailable once the time expires.

Steps

l Set the online charging quota validation time.

Command charge online quota-valid-time

To command syntax for setting the online charging quota validation time is: chargeonline quota-valid-time <0-65535>, as described in Table 4-45.

Table 4-45 Description of Commands for Setting Online Charging Quota ValidationTime

Value Description

0-65535Online charging quota validation time range is 0~65535

(minutes)


Example

To set the online charging quota validation time as 10000 minutes, use the followingcommand:

xGW(config-xgw-pdsn-realm)#charge online quota-valid-time 10000

4.7.4 Setting the Online Charging Quota Holding Time

Prerequisites



Context

Set that a certain amount of money is available during a certain time, and it is unavailableonce the time expires.

Steps

l Set the online charging quota holding time.

Command: charge online quota-holding-time

The command syntax for setting the online charging quota holding time is: chargeonline quota-holding-time <0-65535>, as described in Table 4-46.

4-43



Table 4-46 Description of Commands for Setting Online Charging Quota HoldingTime

Value Description

0-65535Online charging quota holding time range is 0~65535

(minutes)


ExampleTo set the online charging quota holding time as 10000 minutes, use the followingcommand:

xGW(config-xgw-pdsn-realm)#charge online quota-holding-time 10000

4.7.5 Setting the Online Charging Number Analysis Route Function

Prerequisites



ContextWhether to enable the online charging number analysis route function during the onlinecharging.

Steps

l Enable/disable the online charging number analysis route function.

Command: charge online analysis-route

The command syntax for enabling/disabling the online charging number analysis routefunction is: charge online analysis-route {disable | digit-number | msisdn-last-digit |imsi-last-digit}, as described in Table 4-47.

Table 4-47 Description of Commands for Enabling/Disabling Online ChargingNumber Analysis Route Function

Value Description

disableDisable the online-charged number analysis and routing

function.

digit-numberEnable the number-based online-charged number

analysis and routing function.

msisdn-last-digitEnable the online-charged number analysis and routing

function based on the final number of MSISDN.

4-44



Value Description

imsi-last-digitEnable the online-charged number analysis and routing

function based on the final number of IMSI.


Example

To disable the online charging number analysis route function, use the following command:

xGW(config-xgw-pdsn-realm)#charge online analysis-route disable

4.7.6 Setting Online Charging Credit Control Fault Handling Policies

Prerequisites



Context

During online charging, the online charging credit control fault-handling policies should beset.

Steps

l Set the online charging credit control fault handling policies.

Command: charge online max-free-use-time

The command syntax for setting the online charging credit control fault handlingpolicies is: charge online max-free-use-time {2g | 3g | both} {local | roaming | visiting |all}<0–1440>, as described in Table 4-48.

Table 4-48 Description of Commands for Setting Online Charging Credit ControlFault Handling Policies

Value Description

2g 2G user

3g 3G user

both 2G and 3G user

local Local user

roaming Roaming user

visiting Visiting user

all All user(local, roaming, visiting)

4-45



Value Description

0–1440 Max free use time, ranged within 0–1440(minutes)


Example

To set the online charging credit control policy as 2G and 3G user, and user as local user,and max-free-use-time as 100 minutes, use the following command:

xGW(config-xgw-pdsn-realm)#charge online max-free-use-time both local 100

4.7.7 Setting Online Charging Defaulting Policies

Prerequisites



Context

When the online charging is defaulting, handle it as per the configured policies.

Steps

l Set the online charging defaulting policies.

Command: charge online out-balance-policy

The command syntax for setting the online charging defaulting policies is: charge online out-balance-policy {terminate | free-service | deactivate}, as described in Table 4-49.

Table 4-49 Description of Commands for Setting Online Charging DefaultingPolicies

Value Description

terminate It is terminated immediately when defaulting

free-service It is free service when defaulting

deactivate It is used to release the users when defaulting


Example

To set the online charging defaulting policy as terminate, use the following command:

xGW(config-xgw-pdsn-realm)#charge online out-balance-policy terminate

4-46



4.7.8 Setting Online Charging Redirect Address

Prerequisites



Context

When the online charging amount is insufficient, it will link to the redirect addressautomatically. Generally the redirect address is the recharging address of the operators,which is convenient for users recharging.

Steps

l Set the online charging redirect address.

Command: charge online default-redirect-server

The command syntax for setting the online charging redirect address is: charge onlinedefault-redirect-server <url>, as described in Table 4-50.

Table 4-50 Description of Commands for Setting Online Charging Redirect Address

Value Description

url Online charging redirect address


Example

To set the online charging redirect address as www.getmoney.com, use the followingcommand:

xGW(config-xgw-pdsn-realm)#charge online default-redirect-server www.getmoney.com

4.7.9 Enabling/Disabling Online Charging Keywords

Prerequisites



Context

Whether to enable the online charging keywords during the online charging.

4-47



Steps

l Enabling/disabling online charging keywords.

Command: charge online charge-key

The command syntax for enabling/disabling the online charging keywords is: chargeonline charge-key {rg-only | rg-and-si}, as described in Table 4-51.

Table 4-51 Description of Commands for Enabling/Disabling the Online ChargingKeywords

Value Description

rg-only Rating group only

rg-and-si Rating group and service identifie


ExampleTo enable the online charging keywords as rating group and service identifie, use thefollowing command:

xGW(config-xgw-pdsn-realm)#charge online charge-key rg-and-si

4.8 Configuration of the DPI

4.8.1 Introduction to the DPI Function

DescriptionZXUN PDSN supports the DPI function, and provides identification of L3-L4, L7, andP2P protocols and applications through protocol analysis, characteristics analysis. Itcan identify multiple services such as HTTP, WAP1.x/2.0, FTP, RTSP, SIP, BT, eDonkey,and Thunder. In addition, ZXUN PDSN supports the online update of the characteristicslibrary, without affecting the data services of online subscribers.

ZXUN PDSN supports locally configuring a subscriber, service, location, time, and accessmode. Thus the delicacy service control and charge management is implemented.

DPI Hardware ArchitectureThe ZXUN PDSN hardware is based on the ZXUN xGW hardware platform. The DPIfunction is implemented on the GSU board. All XLR chips on the GSU board carries aTCAM and an LSI chip to implement the DPI function.

l TCAM

TCAM is used to quickly match the level-1 rule.

l LSI

4-48



The LSI string search chip, used to search the string in the level-2 rule.

Note:

For details about the PDSN hardware, refer to ZXUN xGW eXtendable GateWay PDSNHardware Decription.

Implementation Mode

The DPI function is implemented in the following ways:

l The level-1 DPI rule is configured and the messages are classified based on themessage quintuple to obtain the message rulebaseid, which is provided for othermodules.

l Further the level-2 rule is configured under the level-1 rule to further analyze themessages, such as the URL matching analysis.

Message Analysis

The DPI subsystem can analyze the messages through the ZXUN PDSN system by:

l Identifying the matching messages based on the locally configured filter rule.l Further identifying messages based on the deep identification policy corresponding

to the filter rule. The deep identification policy includes application-layer trafficidentification, event identification, and service-logic-based time identification.

To implement the deep identification mode, you need configure the correspondingdeep identification policy for the rule. Thus, you can obtain the corresponding deepidentification policy based on the filter rule identified through DPI.

4.8.2 Configuration Flow of DPI

DPI Rule Library Loading

The DPI filter rule is independently loaded. The DPI filter rule configuration provides anindependent configuration tool, through which the rule files are generated and then loadedto the front end.

When generating the loading files, the configuration tool generates different loading filesfor different types of NEs. If the NEs are of the same type, the file is generated as follows:

l For level-1 rule, level-1 rule loading file is independently generated and loaded to theTCAM chip.

l For level-2 rule, a string loading file is generated from the string-based rules such asa level-2 rule, customized rule, DNS rule, and user-defined rule, and is loaded to theLSI chip.

4-49



The DPI rule file is downloaded to MPU through FTP, and then loaded to GSU by MPU.The DPI loading process is as shown in Figure 4-7.

Figure 4-7 DPI Loading Process

1. MPU requests to download the DPI rule file from the FTP server.2. MPU downloads the DPI rule file from the FTP server.3. The DPI rule file is saved on MPU and decompressed.4. MPU notifies GSU to update the DPI rule library.5. GSU requests to download the DPI rule library from MPU.6. GSU downloads the DPI rule library from MPU.7. The DPI rule library is loaded to GSU.

DPI Configuration Flow

Refer to the flow as shown inFigure 4-8 to configure the DPI.

4-50



Figure 4-8 Configuration Flow of DPI

4.8.3 Configuring a DPI Rule

Prerequisites

l You have obtained DPI TOOL. This tool is generally saved in the directory \version\dpi\DPITool of the version file.

l You have been acknowledged with the level-1 and level-2 filtering rules of differentservices and the corresponding charge rates.

ContextThis topic introduces how to use DPI TOOL to configure the level-1 and level-2 filteringrules of different charged services and generate the rule files for protocol analysis of DPI.

Note:

DPI TOOL is the tool used to configure the DPI function. It is a background offlineconfiguration tool and is nested in EXCEL provided by WINDOWS.

The version of DPI TOOL must be exactly consistent with that of the front-end GSU.Otherwise, errors occur.

4-51



Steps

1. Open the DPItool.xls tool.

2. Configure the level-1 filtering rule. The entered parameters include content-basedtemplate ID and the message quintuple (including the source IP, destination IP, clientport, server port, and protocol type). Currently, available protocols include TCP,UDP, and ICMP. In the following example, the content-based charge template is 100,the message quintuple to be filtered includes the source IP address 10.20.30.40,the destination IP address 12.34.56.78, the client port 50/70, the server port 50/70,RuleBaseID is 3. The parameters are as shown in Figure 4-9.

Figure 4-9 Level-1 Filtering Rule

Note:

For one charge template ID, you must set two default rules, one is the default wildcastrule (IP address are compatible 0 and 0.0.0.0), the other is abnormal signaling rule(both the destination IP address and the destination IP mask are 255). See the firstand second columns of the table. Error messages occur if they are not configured.

3. Configure the level-2 filtering rule, set the load on the seven layers of the messages.The entered parameter is the URL included in messages. For example, to implementdifferent charge rates for different websites, enter the parameters as shown in Figure4-10.

Figure 4-10 Level-2 Filtering Rule

4-52



Note:l If the service is the multimedia message service, you may not enter the URL

of the level-2 rule.l If the service is the P2P or CUSTOM service, you may not enter the URL of the

level-2 rule.

4. After configuring the rule, click DPI > RuleBaseID to form the DPI file, as shown inFigure 4-11.The screen may flashes for a few seconds or minutes. After that, the BINfile to be loaded is formed in the directory of DPI TOOL.

Figure 4-11 Generated DPI File


4.8.4 Configuring FTP Server

Prerequisites

l The BIN file of DPI rules has been generated as described in 4.8.3 Configuring a DPIRule.

l The FTP server tool FileZilla Server has been installed on local, and the installationfiles are saved in the \tool\FTP_server directory.

Context

The previous topic introduces how to generate the DPI rule files using DPI TOOL. The DPIfiles should be saved on the FTP server. You can obtain and activate the files using propercommands on ZXUN PDSN. This topic introduces how to configure the FTP server.

Steps

1. Copy the BIN file of the DPI rule to the root directory of the disk C of the FTP server.

2. Open the FileZilla Server tool, select Edit > User to open the user setting dialog box,as shown in Figure 4-12.

4-53



Figure 4-12 Users

3. Click ADD to open the Add user account dialog box, as shown in Figure 4-13. Typempuf.

Figure 4-13 Add User Account

4. Click OK to go back to the Users dialog box, as shown in Figure 4-14.

4-54



Figure 4-14 Users

5. Select the Password option and type mpuf, as shown in Figure 4-15.

Figure 4-15 Password

6. Click OK to open a message box as shown in Figure 4-16.

4-55



Figure 4-16 Message Box

7. Click OK. The local disk C is set as the shared folder, as shown in Figure 4-17.

Figure 4-17 Shared Folders

8. Click OK to complete the setting of the FTP server.


Follow-Up Action

Load and activate the DPI file on ZXUN PDSN.

4.8.5 Deploying DPI Files

Prerequisites

l You have configured the FTP server.l The FTP server and the address of the interface board of ZXUN xGW has been

connected.

4-56



Context

While deploying the DPI files on PDSN , you need first load the DPI files from the specifiedhard disk and activate the files.

Steps

1. Obtain the DPI files.

Command: dpi-file get.

The syntax of the command used to upload the DPI files is dpi-file get ftp <url>| harddisk <file-path>, as described in Table 4-52.

Table 4-52 Description of Commands for Loading DPI Files


ftp url

The location of the DPI files on the FTP server and the

user name and password used to log in to the FTP.

The format of the typed command is: /username:pass-

word@server address/directory/file name.

harddisk file-path

Download the specified DPI files from the specified

local hard disk.

The format of the typed command is: /directory/file

name.

2. Activate the DPI files.

Command: dpi-file activate.

The syntax of the command used to activate the DPI files is dpi-file activate <filename>,as described in Table 4-53.

Table 4-53 Description of Commands for Activating DPI Files

Value Description

filename The name of a DPI file, with 1-79 characters.


Example

To obtain the DPI file named DPI20101128.bin from teh FTP server whose IP address is192.168.110.253, if the user name and password used to log in to the FTP server are bothmpuf, use the following command:

xGW(config-xgw-pdsn)#dpi-file get ftp //mpuf:[email protected]/DPI20101128.bin

To activate the loaded DPI file named DPI20101128.bin, use the following command:

xGW(config-xgw-pdsn)#dpi-file activate DPI20101128.bin

4-57



4.8.6 Enabling/Disabling xDPI Control

Prerequisites


Context

Enable or disable xDPI (Extended Deep Packet Inspection) control function.

Steps

l Enable or disable xDPI control.

Command: xdpi-control

The command syntax for enabling or disabling xDPI control: xdpi-control {enable |disable}, as described in Table 4-54.

Table 4-54 Description of Commands for Enabling/Disabling xDPI Control

Value Description

enable Enable xDPI control

disable Disable xDPI control


Example

Enable xDPI control, use the following command:

xGW(config-xgw-pdsn-realm)#xdpi-control enable

4.9 Configuration of the Policy

4.9.1 Configuration Flow of Policy

Description

Configure the charging policies in the Realm according to the following methods:

l Configure the charging policy profile and the control policy profile, which are used todescribe the user charging methods.

l Configure the charging control policy mapping, and associate the charging policyprofile with the control policy profile.

Policy Configuration Flow

Refer to the flow as shown inFigure 4-18 to configure the policy.

4-58



Figure 4-18 Configuration Flow of Policy

4.9.2 Configuring the Local Charging Rules


ContextThe configuration cannot be effective until it is referenced by charging control policyconfiguration. Setting contents include whether to set as free service.

l If it is free service, it is necessary to set whether the charging mode is based on L3layer or L3 and L7 layer traffic flow, duration statistic mode needs to be set with threeoptions: normal, time-slot and service.

l If time-slot or service is selected, timeslot value should also be set.l If set as charging by event type, event type shall also be set.l If set as charging by flow, it shall include online charging or offline charging, or both

charging mode supported.

Steps

l Configure the local charging rules.

Command: charge-rule

4-59



The command syntax for configuring the local charging rules:charge-rule <rule-name>{ free | not-free {flux-type {l3 | l3–and-l7}} [time-type {normal | time-slot | service}(<1–4294967295>)] [event-type {hit | download | upload}]} (uplink <1–4294967295><1–4294967295>) (downlink <1–4294967295> <1–4294967295>) [flow-charge{offline | online | both}], as described in Table 4-55.

Table 4-55 Description of Commands for Configuring the Local Charging Rules


- rule-nameCharging rule name, required parameter, configuration

range is 1-32 bit string.

- free

Free service, no charging.

Free and not-free are two options. If set as free, it indicates

the service is free. It will not interact with OCS to make

quota application and change during online charging,

which will also be reflected on ticket during offline charging.

- not-free

Non-free service, need to be charged.

Not-free and free are two options. If set as not-free, it

indicates the service is online non-free service. And

flux-type must be set.

l3

flux-typel3–and-l7

Flow charging mode.

l l3: Layer 3 flow will be charged.

l l3–and-l7: Indicate that it will be charged according to

the flow of Layer 3 and Layer 7 reported. At this time,

flow will be identified through DPI.

normal

time-slot

time-type

service

Optional setting, used to set the duration type in duration

charging mode. Duration type includes normal duration

statistics, time slot duration statistics, and service duration

statistics.

l normal: Normal time, accumulate front and end

messages to achieve interval.

l time-slot: Count by time slot duration.If message

interval is less than configured time slot, message

interval shall be accumulated; if message interval

is greater than the time slot, only time slot duration

needs to be accumulated.

l service: Service duration statistics: valid for RTSP

service, it only counts playing time of media stream,

with player playing and pause actions differentiated;

during playing, message intervals of media stream

will be accumulated, and counting mode is equivalent

to time slot statistics; during pause action, message

intervals whose media stream message interval is

larger than time slot will not be accumulated.

4-60




- 1–4294967295

Time slot length.

When time-type value is time-slot and server, the value will

be valid, and the default value is 5 seconds. Configuration

range: numeric string from 1 to 4294967295

hit

download

event-type

upload

Event charging mode, it is divided into counting by hit, by

download and by upload.

l hit: Valid for http protocol. Hit once, message sending

shall serve as the start of event, and receiving server

response as the end of event according to application

method of http protocol.

l download: Download event, valid for ftp protocol

service. Application for file download will serve as the

start of event, and completion of downloading a file

as the end of event.

l upload: Upload event, valid for ftp protocol service.

Application for file upload will serve as the start of

event, and completion of uploading a file as the end

of event.

uplink 1-4294967295

Uplink service ID and rate group configuration.

The first <1-4294967295> is Service ID, and the

second <1-4294967295> is Rating Group, simultaneous

configuration is required. Both configuration values are

allowed to be different.

downlink 1-4294967295

Downlink service ID and rate group configuration.

The first <1-4294967295> is Service ID, and the

second <1-4294967295> is Rating Group, simultaneous

configuration is required. Both configuration values are

allowed to be different.

offline

online

flow-charge

both

Flow charging mode, a charging mode for current service

in previous user charging mode, it can be online charging,

offline charging or online and offline charging.

l offline: Offline charging

l online: Online charging

l both: Online and offline charging


Example

To set charging rule name as zterule (for free service), use the following command:

xGW(config-xgw-pdsn)#charge-rule zterule free

4-61



Follow-Up ActionTo query charging rule according to specified charging rule name, use the followingcommand:

xGW(config-xgw-pdsn)#show pdsn charge-rule [<rule-name>]

To delete charging rule according to specified charging rule name, use the followingcommand:

xGW(config-xgw-pdsn)#no charge-rule <rule-name>

4.9.3 Configuring the Local Control Rule


ContextConfigures the PCC control rule.

Steps1. Set the PCC control rule name.

Command: control-rule

The command syntax for Setting the PCC control rule name: control-rule <rule-name>,as described in Table 4-56.

Table 4-56 Description of Commands for Setting the PCC Control Rule Name

Value Description

rule-namePCC control rule name, configuration range: 1-32 bit

string

2. Configure the threshold control to the service flow. When it is open, the correspondingservice is allowed to pass, otherwise, the message is discarded.

Command: access-control

The command syntax for configuring the threshold control to the service flow: access-control {enable | disable}, as described in Table 4-57.

Table 4-57 Description of Commands for Configuring the Threshold Control tothe Service Flow

Value Description

enable Allows the service flow to pass.

disable Prohibits the service flow to pass.

4-62



3. Configure control rule for the forwarding of packets which trigger new service.

Command: ocs-new-packet

The command syntax for configuring control rule for the forwarding of packets whichtrigger new service:ocs-new-packet {pass | discard | storefirst | storelast}, as describedin Table 4-58.

Table 4-58 Description of Commands for Configuring Control Rule for theForwarding of Packets Which Trigger New Service

Value Description

pass Allows the packets to pass directly.

discard Discard the packets of OCS service.

storefirst Buffer the earliest packets of OCS service.

storelast Buffer the latest packets of OCS service.

4. Configure the redirect control rule.

Command: redirect

The command syntax for configuring the redirect control rule: redirect {enable <url> |disable [acct {enable | disable}])}, as described in Table 4-59.

Table 4-59 Description of Commands for Configuring the Redirect Control Rule


- enable Enables the redirect.

- urlWhen enabled, specify the redirect url

information.

- disable Disables the redirect.

enable Enable accounting for redirectionacct

disable Disable accounting for redirection

5. Configure the service uplink/downlink maximum bandwidth limit.

Command: qos limit

The command syntax for configuring the service uplink/downlink maximum bandwidthlimit: qos limit {uplink | downlink | both} {enable (mbr <8–25600>) | disable}, asdescribed in Table 4-60.

Table 4-60 Description of Commands for Configuring the Service Uplink/DownlinkMaximum Bandwidth Limit


- uplink Uplink

- downlink Downlink

4-63




- both Including uplink and downlink

- enable Enables bandwidth control

mbr 8–25600 Bandwidth control range: 8-256000kpbs

- disable Disables bandwidth control

6. Configure the DSCP identifier of the uplink/downlink messages.

Command: qos dscp

The command syntax for configuring the DSCP identifier of the uplink/downlinkmessages: qos dscp {uplink | downlink | both} {enable <1–63>| disable}, as describedin Table 4-61.

Table 4-61 Description of Commands for Configuring the DSCP Identifier of theUplink/Downlink Messages

Value Description

uplink Uplink

downlink Downlink

both Including uplink and downlink

enable Enables the DSCP identifier.

1–63 DSCP identifier value, range: 1-63

disable Disables the DSCP identifier.

7. Configure the usage monitoring function.

Command: usage-monitor

he command syntax for configuring the usage monitoring function: usage-monitor{(enable (key <key–string>)) | disable}, as described in Table 4-62.

Table 4-62 Description of Commands for Configuring the Usage MonitoringFunction


- enable

Enables the usage monitoring function, and

configure the usage monitoring key when it

is enabled.

key key–stringUsage monitoring key, character string

ranging 1~32

- disable Disables the usage monitoring.


4-64



Example

1. To set the control policy name as ztecont, use the following command:

xGW(config-xgw-pdsn)#control-rule ztecont

2. To allow the corresponding service flow to pass, use the following command:

xGW(config-xgw-pdsn-ctrl_rule)#access-control enable

3. To allow the first packet to pass directly, use the following command:

xGW(config-xgw-pdsn-ctrl_rule)#ocs-new-packet pass

4. To enable the redirect and set the redirect website as www.zte.com, use the followingcommand:

xGW(config-xgw-pdsn-ctrl_rule)#redirect www.zte.com

5. To configure the service uplink/downlink maximum bandwidth limit as 500kpbs, usethe following command:

xGW(config-xgw-pdsn-ctrl_rule)#qos limit both enable mbr 500

6. To enable the DSCP identifier value of the uplink/downlink messages as 63, use thefollowing command:

xGW(config-xgw-pdsn-ctrl_rule)#qos dscp both enable 63

7. To disable the usage monitoring, use the following command:

xGW(config-xgw-pdsn-ctrl_rule)#usage-monitor disable

Follow-Up ActionTo delete the PCC control rule, use the following command:

xGW(config-xgw-pdsn)#no control-rule <rule-name>

To query the PCC control rule, use the following command:

xGW(config-xgw-pdsn-ctrl_rule)#list

To query the PCC control rule of the PDSN, use the following command:

xGW(config-xgw-pdsn-ctrl_rule)#show pdsn control-rule [<rule-name>]

4.9.4 Configuring the Local Charge Control Policy

Prerequisites

l You have entered the Realm, as described in 4.2.2 Configuring the Domain Name.l The charging policy is set, referring to 4.9.2 Configuring the Local Charging Rules.l The control policy is set, referring to 4.9.3 Configuring the Local Control Rule.

ContextConfigure the local charge control policy.

4-65



Steps1. Sets the default charge control policy map for the realm.

Command: charge-control default

The command syntax for setting the default charge control policy map for therealm: charge-control default <policy-name> <1-4294967295> <charge-rule-name><control-rule-name>, as described in Table 4-63.

Table 4-63 Description of Commands for Setting the Default Charge Control policyMap for the Realm

Value Description

policy-name The name of the policy, a string of 1-32 characters.

1-4294967295Service rule or classification service rule group ID, a string of

1-4294967295 digits.

charge-rule-nameThe name of the local charge rule. Before configuring it, first

configure the local charge rule, which is a string of 1-32 characters.

control-rule-nameThe name of the local control rule. Before configuring it, first

configure the local control rule, which is a string of 1-32 characters.

2. Set the predefined user policy charge control policy for realm.

Command: charge-control predefined

The command syntax for setting the predefined user policy charge controlpolicy for realm: charge-control predefined <policy-name> <1-4294967295><charge-rule-name> <control-rule-name> (precedence <1–255>), as described inTable 4-64.

Table 4-64 Description of Commands for Setting the Predefined User Policy ChargeControl Policy for realm

Value Description

policy-name Policy name, a string of 1-32 characters.

1-4294967295The name of the user policy group, or classification service rule

group ID, a string of 1-4294967295 digits.

charge-rule-name

The name of the local charge rule. Before configuring it,

first configure the local charge rule, which is a string of 1-32

characters.

control-rule-name

The name of the local control rule. Before configuring it,

first configure the local control rule, which is a string of 1-32

characters.

1–255Priority, a string with 1-255 digits. The less the digit is, the higher

the priority is.

3. Configure the local charge control policy for realm.

4-66



Command: charge-control local

The command syntax for configuring the local charge control policy for realm:charge-control local <policy-name> <user-policy-name> <1-4294967295><charge-rule-name> <control-rule-name>, as described in Table 4-65.

Table 4-65 Description of Commands for Configuring the Local Charge ControlPolicy for Realm

Value Description

policy-name The policy name, a string of 1-32 characters.

user-policy-name The user policy group name, a string of 1-32 characters.

1-4294967295Service rule or classification service rule group ID, a string of

1-4294967295 digits.

charge-rule-name

The name of the local charge rule. Before configuring it,

first configure the local charge rule, which is a string of 1-32

characters.

control-rule-name

The name of the local control rule. Before configuring it,

first configure the local control rule, which is a string of 1-32

characters.


Example

1. To set the default charge control policy for realm, in which, the policy name is ztepolicy,the service rule group ID is 202, the local charge rule name is ztechargerule, and thelocal control rule name is ztecontrolrule, use the following command:

xGW(config-xgw-pdsn-realm)#charge-control default ztepolicy 202 ztechargeruleztecontrolrule

2. To configure the predefined user policy charge control policy for realm, in which, thepolicy name is ztepolicy, the user policy ID is 101, the service rule ID is 202, the localcharge rule name is ztechargerule, the local control rule name is ztecontrolrule, andthe priority is 255, use the following command:

xGW(config-xgw-pdsn-realm)#charge-control predefined user-policy ztepolicy 101 202ztechargerule ztecontrolrule precedence 255

3. To set the local charge control policy for realm, in which, the policy name is ztepolicy,the user policy group name is zteuserpolicy, the service rule ID is 202, the local chargerule name is ztechargerule, and the local control rule name is ztecontrolrule, use thefollowing command:

xGW(config-xgw-pdsn-realm)#charge-control local ztepolicy zteuserpolicy 202ztechargerule ztecontrolrule

4-67



Follow-Up Action

To delete the local charge control policy for realm, use the following command:

xGW(config-xgw-pdsn-realm)#no charge-control local <policy-name>

To delete the predefined user policy charge control policy for realm, use the followingcommand:

xGW(config-xgw-pdsn-realm)#no charge-control predefined user-policy <policy-name>

To delete the default charge control policy for realm, use the following command:

xGW(config-xgw-pdsn-realm)#no charge-control default <policy-name>

To check the realm charging control policy mapping, use the following command:

xGW(config-xgw-pdsn-realm)#show pdsn charge-control [<realm–name>]

4.9.5 Configuring the Service Classification Map

Prerequisites


Context

Sets the service classification map, which is applicable if basic service classification isunder policy control.

Steps

l Configure the service classification map.

Command: service-class-map

The command syntax for configuring the service classification map: service-class-map<1-4294967295> <1-4294967295>, as described in Table 4-66.

Table 4-66 Description of Commands for Configuring the Service Classification Map

Value Description

1-4294967295 The rule ID, a string of 1-4294967295 digits.

1-4294967295 The application ID, a string of 1-4294967295 digits.


Example

To set the service classification map, with the rule ID map 1 and the application ID map 3,use the following command:

xGW(config-xgw-pdsn-realm)#service-class-map 1 3

4-68



Follow-Up Action

To query the service classification map, use the following command:

xGW(config-xgw-pdsn-realm)#list service-class-map

4.10 Configuration of the PCC

4.10.1 Configuration Flow of PCC

Description

To increase the use and additional value of the mobile bandwidth, PDSN supports the PCC(Policy and Charging Control) function to control the subscriber or service policies. The HAgateway has the integrated PCEF (Policy and Charging Enforcement Function) functionalentity and has the service identification and policy control function.

PCC Configuration Flow

Refer to the flow as shown in Figure 4-19 to configure the PCC.

4-69



Figure 4-19 Configuration Flow of PCC

4.10.2 Enabling/Disabling PCC Function

Prerequisites


Context

Enable or Disable PCC Function, and enable or disable default support PCC.

Steps

l Enable or disable PCC function.

Command: pcc control

4-70



The command syntax for enabling/disabling PCC function is: pcc control {enable |disable}, as described in Table 4-67.

Table 4-67 Description of Commands for Enabling/Disabling PCC Function

Value Description

enable Enable PCC function

disable Disable PCC function

l Enable or disable default support PCC.

Command: pcc default-support-pcc

The command syntax for enabling/disabling default support PCC is: pcc default-support-pcc {enable | disable}, as described in Table 4-68.

Table 4-68 Description of Commands for Enabling/Disabling Default Support PCC

Value Description

enable Enable default support PCC

disable Disable default support PCC


ExampleEnable PCC function, use the following command:

xGW(config-xgw-pdsn-realm)#pcc control enable

Enable default support PCC, use the following command:

xGW(config-xgw-pdsn-realm)#pcc default-support-pcc enable

4.10.3 Configuring PCC Default Service Name


ContextConfigure PCC default service name.

Steps

l Configure PCC default service name.

Command: pcc default-service-name

The command syntax for configuring PCC default service name is: pcc default-service-name <service-name>, as described in Table 4-69.

4-71



Table 4-69 Description of Commands for Configuring PCC Default Service Name

Value Description

service-name Default service name, configuration range: 1-63 bit string.


ExampleTo configure PCC default service name as pdsnpcc, use the following command:

xGW(config-xgw-pdsn-realm)#pcc default-service-name pdsnpcc

Follow-Up ActionTo delete PCC default service name, use the following command:

xGW(config-xgw-pdsn-realm)#no pcc default-service-name <service-name>

4.10.4 Setting the PCC Access Type


ContextSet the PCC access type.

Steps

l Set the PCC access type.

Command: pcc access-type

The command syntax for setting the PCC access type: pcc access-type {local | gx}, asdescribed in Table 4-70.

Table 4-70 Description of Commands for Setting the PCC Access Type

Value Description

localIndicates that the local policy is enabled and used to serve

users.

gxIndicates that the Gx interface is enabled, which controls users’

PCC policies by interacting with PCRF.


ExampleTo set the PCC access type as local, use the following command:

4-72



xGW(config-xgw-pdsn-realm)#pcc access-type local

4.10.5 Configuring Rate Control Policy

Prerequisites


Context

Configure rate control by AAA or PCRF authorization parameters.

Steps

l Configure rate control policy

Command: pcc pcrf rate-control-policy

The command syntax for configuring rate control policy is: pcc pcrf rate-control-policy{aaa-auth | pcrf-auth}, as described in Table 4-71.

Table 4-71 Description of Commands for Configuring Rate Control Policy

Value Description

aaa-auth Rate control by aaa authorization parameters.

pcrf-auth Rate control by pcrf authorization parameters.


Example

Rate control by aaa authorization parameters, use the following command:

xGW(config-xgw-pdsn-realm)#pcc pcrf rate-control-policy aaa-auth

4.10.6 Configuring MBR Mapping

Prerequisites


Context

Enable or disable MBR mapping to AMBR

Steps

l Enable or disable MBR mapping to AMBR

Command: pcc pcrf mbr-mapping-ambr

4-73



The command syntax for enabling/disabling MBR mapping to AMBR is: pcc pcrf mbr-mapping-ambr{enable | disable}, as described in Table 4-72.

Table 4-72 Description of Commands for Enabling/Disabling MBR Mapping toAMBR

Value Description

enable Enable MBR mapping to AMBR

disable Disable MBR mapping to AMBR


ExampleEnable MBR mapping to AMBR, use the following command:

xGW(config-xgw-pdsn-realm)#pcc mbr-mapping-ambrenable

4.10.7 Configuring the PCC Parameter


ContextSet the PCC Parameter.

Steps1. Set PCRF failure processing policies.

Command: pcc pcrf ccfh

The command syntax for setting PCRF failure processing policies: pcc pcrf ccfh{continue | terminate}, as described in Table 4-73.

Table 4-73 Description of Commands for Setting PCRF Failure Processing Policies

Value Description

continueThe services of users keep going when abnormal messages

are received from PCRF.

terminateUsers are kicked off when abnormal messages are received

from PCRF.

2. Configure dynamic pcc rule continue or not for pcrf exception.

Command: pcc pcrf except-rule-select

The command syntax for configuring dynamic pcc rule continue or not for pcrfexception: pcc pcrf except-rule-select {local | dynamic}, as described in Table 4-74.

4-74



Table 4-74 Description of Commands for Configuring Dynamic PCC Rule Continueor Not for Pcrf Exception

Value Description

local Use local rule

dynamic Use dynamic rule

3. Configure pcc charging rule selection.

Command: pcc dynm-charge-rule

The command syntax for configuring pcc charging rule selection: pcc dynm-charge-rule {local | dynamic}, as described in Table 4-75.

Table 4-75 Description of Commands for Configuring PCC Charging Rule Selection

Value Description

local Local charging rule prior

dynamic Dynamic charging rule prior

4. Configure pcc redirected service charging policy.

Command: pcc control-service-charge

The command syntax for configuring pcc redirected service charging policy: pcc control-service-charge {free | special | normal}, as described in Table 4-76.

Table 4-76 Description of Commands for Configuring PCC Redirected ServiceCharging Policy

Value Description

free No charging

special Charging to special service

normal Normal service charging

5. Set whether to enable pcc dynamic rule request.

Command: pcc dynm-rule-request

The command syntax for setting whether to enable pcc dynamic rule request: pccdynm-rule-request {enable | disable}, as described in Table 4-77.

Table 4-77 Description of Commands for Setting Whether to Enable PCC DynamicRule Request

Value Description

enable enable pcc dynamic rule request

disable disable pcc dynamic rule request

6. Set whether to enable pcc service classification matching.

4-75



Command: pcc service-classification

The command syntax for setting whether to enable pcc service classification matching:pcc service-classification {enable | disable}, as described in Table 4-78.

Table 4-78 Description of Commands for Setting Whether to Enable PCC ServiceClassification Matching

Value Description

enable enable pcc service classification matching

disable disable pcc service classification matching

7. Set default service app id.

Command: pcc default-service-app-id

The command syntax for setting default service app id: pcc default-service-app-id<0-4294967295>, as described in Table 4-79.

Table 4-79 Description of Commands for Setting Default Service App ID

Value Description

0-4294967295 Service application identifier

8. Set digit number analysis access type

Command: pcc digit-number-analysis-access

The command syntax for setting digit number analysis access type: pcc digit-number-analysis-access {disable | imsi}, as described in Table 4-80.

Table 4-80 Description of Commands for Setting Digit Number Analysis AccessType

Value Description

disable Disable digit number analysis access type

imsi Access type obtained by imsi analysis

9. Set whether to enable the blacklist and whitelist control function.

Command: pcc black-white-list

The command syntax for setting whether to enable the blacklist and whitelist controlfunction: pcc black-white-list {enable | disable}, as described in Table 4-81.

Table 4-81 Description of Commands for Setting Whether to Enable the Blacklistand Whitelist Control Function

Value Description

enableIndicates that the blacklist and whitelist control

function is enabled.

4-76



Value Description

disableIndicates that the blacklist and whitelist control

function is disabled.


Example

1. If you want users’ services keep going when abnormal messages are received fromthe PCRF, use the following command:

xGW(config-xgw-pdsn-realm)#pcc pcrf ccfh continue

2. Configure dynamic pcc rule continue as local rule, use the following command:

xGW(config-xgw-pdsn-realm)#pcc pcrf except-rule-select local

3. Configure pcc charging rule selection as local, use the following command:

xGW(config-xgw-pdsn-realm)#pcc dynm-charge-rule local

4. Configure pcc redirected service charging policy as free, use the following command:

xGW(config-xgw-pdsn-realm)#pcc control-service-charge free

5. Enable pcc dynamic rule request, use the following command:

xGW(config-xgw-pdsn-realm)#pcc dynm-rule-request enable

6. enable pcc service classification matching, use the following command:

xGW(config-xgw-pdsn-realm)#pcc service-classification enable

7. Set default service app id as 10, use the following command:

xGW(config-xgw-pdsn-realm)#pcc default-service-app-id 10

8. Access type obtained by imsi analysis, use the following command:

xGW(config-xgw-pdsn-realm)#pcc digit-number-analysis-access imsi

9. To enable the blacklist and whitelist control function, use the following command:

xGW(config-xgw-pdsn-realm)#black-white-list enable

Follow-Up Action

To query the PCC parameter, use the following command:

xGW(config-xgw-pdsn-realm)#list pcc

4.11 Configuring SNMP Alarm ManagementPrerequisites


4-77



ContextThe alarm agent residents on all CPUs. It collects the alarm messages of variousapplications, and synchronizes the collected alarm messages to the active alarmserver.The alarm agent is used to collect and construct alarm message records andtransfer the records to the alarm server. The alarms on it keep consistent with the alarmson the alarm server.SNMP implements alarm setting, query, and screen through the alarmserver.

Steps1. Access to the system host through the SNMP protocol using the configured ACL.

The syntax of the command is snmp-server access-list ipv4 <name>. The involvedparameters are as shown in Table 4-82.

Table 4-82 Command for Configuring Access List Name

Value Description

name The name of the access list.

2. Set the SNMP message community string.

The syntax of the command is snmp-server community community_name view<community_name_view> {ro | rw}. The involved parameters are as described inTable 4-83.

Table 4-83 Command for Setting SNMP Message Community String


view community_name_view

Specifies the view name for the

configured community string, a string of

1-32 characterfixed as AllView

- roIndicates performing only-read access

on MIB.

- rwIndicates performing read/write access

on MIB.

3. Set the name of the SNMP context.

The syntax of the command is snmp-server context <snmp_context_name>. Theinvolved parameters are as shown in Table 4-84.

Table 4-84 Command for Setting the SNMP Context

Value Description

snmp_context_name The name of the SNMP context.

4. Set the switches and types of the notifications to be sent by the agent.

4-78



The syntax of the command is snmp-server {enable | disable} inform { bgp | ospf |rmon | snmp | stalarm | vpn}. The involved parameters are as shown in Table 4-85.

Table 4-85 Command for Seting the Switches and Types of notifications to beSent by an Agent.


- enableEnable the switch of the agent to send

notifications.

- disableDisable the switch of the agent to send

notifications.

bgp

ospf

rmon

snmp

stalarm

inform

vpn

Specifies the notification types, including

the types of notifications BGP, OSPF,

RMON, SNMP, STALARM, and VPN. If you

do not select the types of the notifications

to be sent by the agent, all notifications of

informs are sent.

- server-working Enable SNMP server start to work

- trap Enable SNMP traps

5. Set the switches and types of the traps to be sent by the agent.

The syntax of the command is snmp-server {enable | disable} inform { bgp | ospf |rmon | snmp | stalarm | vpn}. The involved parameters are as shown in Table 4-86.

Table 4-86 Command for Seting the Switches and Types of Traps to be Sent byan Agent


- enableEnable the switch of the agent to send

traps.

- disableDisable the switch of the agent to send

traps.

bgp

ospf

rmon

snmp

stalarm

trap

vpn

Specifies the types of the traps to be

sent by the agent, including the types of

notifications BGP, OSPF, RMON, SNMP,

STALARM, and VPN.If you do not select

the types of the traps to be sent by the

agent, all types of traps are sent.

6. Set the local engine ID of SNMP.

4-79



The syntax of the command is snmp-server <engine-id> <snmp_engid_name>. Theinvolved parameters are as shown in Table 4-87.

Table 4-87 Command of Setting Local Engine ID of SNMP

Value Description

engine-idSets the local engine ID of SNMP, tha range is 1-24 hex

characters.

Note:

If the local engine ID of SNMP as default, this step doesn’t execution.

7. Map SNMP subscribers to the SNMP view, that is, configure a new SNMP group.

The syntax of the command is snmp-server group <groupname> <version> {auth| noauth | priv} [context {match-prefix | match-exact}] read <readview> write<writeview> notify <notifyview>. The involved parameters are as described in Table4-88.

Table 4-88 Command of Mapping SNMP Subscribers to SNMP View


group groupnameThe name of the SNMP group, composed of

1-32 characters.

- version Specifies the version used for the group.

- authSets message authentication, but no

encryption is needed.

- noauthSets no message authentication nor

encryption.

- priv Sets message authentication and encryption.

match-prefixSpecifies the group context. The context

matching mode is prefix matching.context

match-exact The context matching mode is exact match.

read readviewSpecifies the read view, composed of 1-32

characters.

write writeviewSpecifies the write view, composed of 1-32

characters.

notify notifyviewSpecifies the notification view, composed of

1-32 characters.

8. Sets the destination for receiving the SNMP notifications.

4-80



The syntax of the command is snmp-server host <ip-address> [vrf <vrf-name>] {trap| inform} ver version [auth | noauth | priv] <community-name> [udp-port <udp-port>]<trap-type>. The involved parameters are as described in Table 4-89.

Table 4-89 Command of Setting the Destination for Receiving SNMP Notifications


- ip-address Specifies the IP address of the SNMP host.

vrf vrf-nameThe name of the VRF, composed of 1-32

characters.

- trap Specifies sending traps to the host.

- inform Specifies sending notifications to the host.

ver versionSNMP versions, including version numbers

1, 2c, and 3.

- auth Sets to authenticate the sent messages.

- noauth Sets not to authenticate the sent messages.

- priv Sets to encrypt the sent messages.

- community-nameThe community string name or the SNMPv3

user name, composed of 1-32 characters.

udp-port udp-portSpecifies the UDP port through which traps

are sent, a character with 0–65535 digits.

- trap-type

Specifies the trap or notification types,

including the types BGP, OSPF, RMON,

SNMP, STALARM, and VPN.

9. Set the maximal length of an SNMP message.

The syntax of the command is snmp-server packetsize <snmp-packet-max-size>. Theinvolved parameters are as decribed in Table 4-90.

Table 4-90 Command of Setting the Maximal Length of an SNMP Message


packetsize snmp-packet-max-size

The size of an SNMP packet, with the unit

byte and valued within 484–1400, default

value is 8192

10. Configure the source IP address of all traps.

The syntax of the command is snmp-server trap-source <IP Address>. The involvedparameters are as described in Table 4-91.

4-81



Table 4-91 Command for Configuring Source IP Address of All Traps


trap-source IP Address Configure the source IP address of all traps.

11. Configure an SNMPv3 subscriber.

The syntax of the command is snmp-server <username> <groupname> version auth{md5 | sha} <auth-password> priv dess56 priv-password. The involved parametersare as decribed in Table 4-92.

Table 4-92 Command for Configuring an SNMPv3 Subscriber

Value Description

usernameThe name of an SNMP subscriber, composed of 1-32

characters.

groupnameThe name of the group related to an SNMP subscriber,

composed of 1-32 characters.

version Specifies the version number used for the subscriber.

auth Specifies that the subscriber has authentication permission.

md5 Use HMAC-MD5-96 as the authentication mode.

sha Use HMAC-MD5-96 as the authentication mode.

auth-passwordAuthentication password (or authentication key), composed

of 1–32 characters.

priv Specifies that the subscriber has encryption permission.

dess56 Specifies CBC-DES as the encryption mode.

priv-password Encryption password, composed of 1-32 characters.

12. Sets the SNMP view.

The syntax of the command is snmp-server view <view-name> subtree-id {included |exculded}. The involved parameters are as shown in Table 4-93.

Table 4-93 Command for Setting the SNMP View

Value Description

view-name The name of the view, composed of 1-32 characters.

subtree-idThe specified MIB subtree ID or node name, composed of

1-79 characters.

included The MIB subtree is included.

exculded The MIB subtree is excluded.

4-82



Note:

Sets the SNMP view as default:

snmp-server view AllView 1.3.6.1 included

snmp-server view DefaultView 1.3.6.1.2.1.1 included

Please the SNMP view as default, if modified the configuration, this function may benot used.


Example

1. To set the access list name as snmp_access_list, use the following command:

xGW(config)#snmp-server access-list ipv4 snmp_access_list

2. To set the SNMP message community string name as community_zte_view and theaccess mode as read-only, use the following command:

xGW(config)#snmp-server community community_name view AllView ro

3. To set the SNMP context name as snmp_context_zte, use the following command:

xGW(config)#snmp-server context snmp_context_zte

4. To enable the agent switch for sending notifications, and set the notification type asSNMP, use the following command:

xGW(config)#snmp-server enable inform snmp

Enable SNMP server start to work, use the following command:

xGW(config)#snmp-server enable server-working

Enable SNMP traps, use the following command:

xGW(config)#snmp-server enable trap

5. To enable the agent switch for sending traps, and set the trap type as SNMP, use thefollowing command:

xGW(config)#p-server enable trap snmp

6. To set the local engine ID of SNMP as engid_12, use the following command:

xGW(config)#snmp-server engid_12

7. To set the SNMP group name as group1, using the v3 version, with messageauthentication and encryption, the read view name as view1, the write view name aswrite1, the notification view name as notify1, use the following command:

xGW(config)#snmp-server group group1 v3 priv read view1writewrite1 notify notify1

4-83



8. To set the destination address for receiving the SNMP notifications as 192.168.1.1,specifying to send traps to the host, the SNMP version number as 1, the SNMPv3subscriber name as community-zte, using the SNMP trap type, use the followingcommand:

xGW(config)#snmp-server host 192.168.1.1 trap ver 2c community-zte snmp

9. To set the maximal length of an SNMP message to 1000 bytes, use the followingcommand:

xGW(config)#snmp-server packetsize 1000

10. To configure the source IP address of all traps as 192.168.2.3, use the followingcommand:

xGW(config)#snmp-server trap-source 192.168.2.3

11. To set the SNMP subscriber name as user1, the subscriber-related group name asgroup1, using the v3 version, set the subscriber having authentication permission,using the HMAC-MD5-96 authentication mode, with the authentication password12345678, and set the subscriber to have encryption permission using the CBC-DESencryption mode, with the encryption password 87654321, use the followingcommand:

xGW(config)#snmp-server user1 group1 v3 auth md5 12345678 priv des56 87654321

12. To set the SNMP view as default, use the following command:

xGW(config)#snmp-server view AllView 1.3.6.1 included

xGW(config)#snmp-server view DefaultView 1.3.6.1.2.1.1 included

4-84


FiguresFigure 1-1 Schematic Diagram of PDSN in the Mobile Network ................................ 1-2

Figure 1-2 PDSN Data Configuration Flow................................................................ 1-6

Figure 1-3 Schematic Diagram of Operation & Maintenance System ....................... 1-7

Figure 1-4 Network Planning..................................................................................... 1-9

Figure 2-1 Configuration Flow of IP Protocol Stack ................................................. 2-18

Figure 2-2 Configuration Flow of Interconnection Between PDSN and OCS ........... 2-25

Figure 3-1 Configuration Flow of Interconnection Between PDSN and PCF .............. 3-2

Figure 3-2 Configuration Flow of Interconnection Between PDSN and AAA .............. 3-9

Figure 3-3 Configuration Flow of Interconnection Between PDSN and LNS ............ 3-15

Figure 4-1 Configuration Flow of IP Pool................................................................... 4-2

Figure 4-2 Configuration Flow of the Domain ............................................................ 4-8

Figure 4-3 Configuration Flow of MIP Service ......................................................... 4-19

Figure 4-4 Configuration Flow of the Lawful Interception Service ............................ 4-27

Figure 4-5 Configuration Flow of the Offline Charging ............................................. 4-36

Figure 4-6 Configuration Flow of Online Charging................................................... 4-41

Figure 4-7 DPI Loading Process ............................................................................. 4-50

Figure 4-8 Configuration Flow of DPI ...................................................................... 4-51

Figure 4-9 Level-1 Filtering Rule ............................................................................. 4-52

Figure 4-10 Level-2 Filtering Rule ........................................................................... 4-52

Figure 4-11 Generated DPI File .............................................................................. 4-53

Figure 4-12 Users ................................................................................................... 4-54

Figure 4-13 Add User Account ................................................................................ 4-54

Figure 4-14 Users ................................................................................................... 4-55

Figure 4-15 Password............................................................................................. 4-55

Figure 4-16 Message Box....................................................................................... 4-56

Figure 4-17 Shared Folders .................................................................................... 4-56

Figure 4-18 Configuration Flow of Policy................................................................. 4-59

Figure 4-19 Configuration Flow of PCC................................................................... 4-70

I

Figures

This page intentionally left blank.

TablesTable 1-1 Command Operation Commands .............................................................. 1-4

Table 1-2 Networking Area Classification .................................................................. 1-9

Table 1-3 Description to VRFs ................................................................................ 1-10

Table 1-4 IP Address Planning................................................................................ 1-10

Table 2-1 Description of Commands for Configuring the Time Zone .......................... 2-4

Table 2-2 Description of Commands for Configuring the Time................................... 2-5

Table 2-3 Description of Commands for Creating the VRF ........................................ 2-6

Table 2-4 Description of Commands for Setting the rd Range ................................... 2-6

Table 2-5 show Command ........................................................................................ 2-8

Table 2-6 Description of Commands for Creating or Entering a CPU Group .............. 2-9

Table 2-7 Description of Commands for Setting Backup Mode of CPU Group ........... 2-9

Table 2-8 Description of Commands for Adding a CPU ........................................... 2-11

Table 2-9 Description of Commands for Creating and Entering an SLBGroup..................................................................................................... 2-12

Table 2-10 Description of Commands for Configuring Backup Mode of CPU of SLBGroup..................................................................................................... 2-12

Table 2-11 Description of Commands for Adding a CPU in an SLB Group............... 2-13

Table 2-12 Description of Commands for Configuring the SLB Address .................. 2-13

Table 2-13 Description of Commands for Creating and Entering an CUGroup..................................................................................................... 2-15

Table 2-14 Description of Commands for Adding a CPU into a CU Group............... 2-15

Table 2-15 Description of Commands for Setting the Context Capacity AlarmThreshold............................................................................................... 2-16

Table 2-16 Description of Commands for Configuring the CU Ageing Time ............. 2-16

Table 2-17 Description of Commands for Entering the Interface Status ................... 2-20

Table 2-18 Description of Commands for Adding the Interface IP Address .............. 2-20

Table 2-19 Description of Commands for Setting MAC Address Offset.................... 2-20

Table 2-20 Description of Commands for Setting Non-default Route ofPDSN..................................................................................................... 2-22

Table 2-21 Description of Commands for Entering the Sub-interface Status............ 2-23

Table 2-22 Description of Commands for Binding the Sub-interface with theVLAN ..................................................................................................... 2-23

III


Table 2-23 Description of Commands for Binding the Sub-interface with theVRF ....................................................................................................... 2-23

Table 2-24 Description of Commands for Configuring the IP Address of theSub-interface ......................................................................................... 2-23

Table 2-25 Description of Commands for Configuring Adjacent Office NodeParameters ............................................................................................ 2-26

Table 2-26 Description of Commands for Configuring Local NodeParameters ............................................................................................ 2-27

Table 2-27 Description of Commands for Configuring Diameter Link ....................... 2-28

Table 2-28 Description of Commands for Configuring the TCP Link ........................ 2-29

Table 3-1 Description of Commands for Configuring the Real IP Service Addressof the RP Interface ................................................................................... 3-2

Table 3-2 Description of Commands for Adding RP Security Association .................. 3-4

Table 3-3 Description of Commands for Configuring FA-HA SecurityAssociation .............................................................................................. 3-5

Table 3-4 Description of Commands for Adding FA-HA Security Association inBatch ....................................................................................................... 3-7

Table 3-5 Description of Commands for Creating and Entering AAA ProfileConfiguration Mode................................................................................ 3-10

Table 3-6 Description of Commands for Configuring the RADIUS Server ................ 3-11

Table 3-7 Description of Commands for Configuring the AAAC Address ................. 3-12

Table 3-8 Description of Commands for Configuring the Shared Key ...................... 3-13

Table 3-9 Description of Commands for Configuring the NAS Attribute ................... 3-14

Table 3-10 Description of Commands for Configuring the Realm............................. 3-16

Table 3-11 Description of Commands for Configuring the Default LAC .................... 3-17

Table 3-12 Description of Commands for Configuring the Non-default LACAddress ................................................................................................. 3-18

Table 4-1 Description of Commands for Configuring the IP Pool ............................... 4-3

Table 4-2 Description of Commands for Configuring the VRF of the IP Pool.............. 4-4

Table 4-3 Description of Commands for Configuring the IP Segments....................... 4-4

Table 4-4 Description of Commands for Configuring the Priority of the IP Pool ........... 4-6

Table 4-5 Description of Commands for Configuring the Types of the IP Pool ........... 4-7

Table 4-6 Description of Commands for Configuring the Realm ................................ 4-9

Table 4-7 Description of Commands for Configuring the Active DNS Address ........... 4-10

Table 4-8 Description of Commands for Configuring the Standby DNSAddress ................................................................................................. 4-11

Table 4-9 Description of Commands for Configuring the IP Pool of a Domain ........... 4-12

IV

Tables

Table 4-10 Description of Commands for Configuring the AAA Profile Used forAuthentication ........................................................................................ 4-13

Table 4-11 Description of Commands for Configuring Realm Charging Mode ........... 4-14

Table 4-12 Description of Commands for Configuring Content ChargeAttribute ................................................................................................. 4-14

Table 4-13 Description of Commands for Configuring the AAA Profile Used forCharging ................................................................................................ 4-15

Table 4-14 Description of Commands for Configuring the Local AuthenticationAttributes of the SIP ............................................................................... 4-16

Table 4-15 Description of Commands for Configuring the Local AuthenticationAttributes of the L2TP ............................................................................ 4-18

Table 4-16 Description of Commands for Configuring the COA Address ................. 4-20

Table 4-17 Description of Commands for Configuring Timeout of HA AuthenticationReply ..................................................................................................... 4-21

Table 4-18 Description of Commands for Configuring Timeout of AAAAuthentication Reply .............................................................................. 4-22

Table 4-19 Description of Commands for Configuring Interval of Sending ProxyBroadcast or Times of Sending Proxy Broadcast.................................... 4-22

Table 4-20 Description of Commands for Configuring Support RegistrationRevocation............................................................................................. 4-22

Table 4-21 Description of Commands for Configuring Length of FAC ...................... 4-23

Table 4-22 Description of Commands for Configuring Support PMIP Type .............. 4-23

Table 4-23 Description of Commands for Configuring Maximal Times of SendReg_Req for PMIP and Refresh Time Before Expired for PMIP ............. 4-23

Table 4-24 Description of Commands for Configuring PMIP Use ReverseTunnel.................................................................................................... 4-23

Table 4-25 Description of Commands for Configuring MN-HA AuthenticationAlgorithm Type....................................................................................... 4-24

Table 4-26 Description of Commands for Configuring Agent AdvertisementGbit........................................................................................................ 4-24

Table 4-27 Description of Commands for Configruing Carrying Null Attribute in MipRrq......................................................................................................... 4-24

Table 4-28 Description of Commands for Configuring Maximal Time of MIPEstablishing ........................................................................................... 4-25

Table 4-29 Configure Maximal Times and Interval of Register Revocation .............. 4-25

Table 4-30 Configuring Revocation Extention I bit Flag Value.................................. 4-25

Table 4-31 Description of Commands for Configuring the Local End Information ofthe Lawful Interception ........................................................................... 4-28

V


Table 4-32 Description of Commands for Configuring Types and Sub-types of theLawful Interception................................................................................. 4-30

Table 4-33 Description of Commands for Configuring the Remote GatewayAddress of the Lawful Interception ......................................................... 4-31

Table 4-34 Description of Commands for Configuring the Remote End Types ofthe Lawful Interception ........................................................................... 4-31

Table 4-35 Description of Commands for Configuring the Gateway Address andthe Port of the Interface X3 .................................................................... 4-32

Table 4-36 Description of Commands for Configuring the Local Port of the InterfaceX3.......................................................................................................... 4-33

Table 4-37 Description of Commands for Configuring the Local Media Plane IPAddress of the Interface X3.................................................................... 4-34

Table 4-38 Description of Commands for Configuring the Link DetectionParameters of the Interface X3............................................................... 4-35

Table 4-39 Description of Commands for Setting the Offline ChargingModes.................................................................................................... 4-37

Table 4-40 Description of Commands for Setting Offline Charging FlowThreshold............................................................................................... 4-38

Table 4-41 Description of Commands for Setting Offline Charging TimeThreshold............................................................................................... 4-38

Table 4-42 Description of Commands for Setting the CDR Filtering......................... 4-39

Table 4-43 Description of Commands for Setting the Offline Charging Tariff ............ 4-39

Table 4-44 Description of Commands for Setting the Online Charging DiameterAdjacent Office....................................................................................... 4-42

Table 4-45 Description of Commands for Setting Online Charging Quota ValidationTime....................................................................................................... 4-43

Table 4-46 Description of Commands for Setting Online Charging Quota HoldingTime....................................................................................................... 4-44

Table 4-47 Description of Commands for Enabling/Disabling Online ChargingNumber Analysis Route Function ........................................................... 4-44

Table 4-48 Description of Commands for Setting Online Charging Credit ControlFault Handling Policies........................................................................... 4-45

Table 4-49 Description of Commands for Setting Online Charging DefaultingPolicies .................................................................................................. 4-46

Table 4-50 Description of Commands for Setting Online Charging RedirectAddress ................................................................................................. 4-47

Table 4-51 Description of Commands for Enabling/Disabling the Online ChargingKeywords............................................................................................... 4-48

Table 4-52 Description of Commands for Loading DPI Files.................................... 4-57

VI

Tables

Table 4-53 Description of Commands for Activating DPI Files ................................. 4-57

Table 4-54 Description of Commands for Enabling/Disabling xDPI Control.............. 4-58

Table 4-55 Description of Commands for Configuring the Local ChargingRules ..................................................................................................... 4-60

Table 4-56 Description of Commands for Setting the PCC Control RuleName..................................................................................................... 4-62

Table 4-57 Description of Commands for Configuring the Threshold Control to theService Flow .......................................................................................... 4-62

Table 4-58 Description of Commands for Configuring Control Rule for theForwarding of Packets Which Trigger New Service ................................ 4-63

Table 4-59 Description of Commands for Configuring the Redirect ControlRule ....................................................................................................... 4-63

Table 4-60 Description of Commands for Configuring the Service Uplink/DownlinkMaximum Bandwidth Limit ..................................................................... 4-63

Table 4-61 Description of Commands for Configuring the DSCP Identifier of theUplink/Downlink Messages .................................................................... 4-64

Table 4-62 Description of Commands for Configuring the Usage MonitoringFunction................................................................................................. 4-64

Table 4-63 Description of Commands for Setting the Default Charge Control policyMap for the Realm ................................................................................. 4-66

Table 4-64 Description of Commands for Setting the Predefined User PolicyCharge Control Policy for realm ............................................................. 4-66

Table 4-65 Description of Commands for Configuring the Local Charge ControlPolicy for Realm..................................................................................... 4-67

Table 4-66 Description of Commands for Configuring the Service ClassificationMap ....................................................................................................... 4-68

Table 4-67 Description of Commands for Enabling/Disabling PCC Function............ 4-71

Table 4-68 Description of Commands for Enabling/Disabling Default SupportPCC....................................................................................................... 4-71

Table 4-69 Description of Commands for Configuring PCC Default ServiceName..................................................................................................... 4-72

Table 4-70 Description of Commands for Setting the PCC Access Type ................. 4-72

Table 4-71 Description of Commands for Configuring Rate Control Policy............... 4-73

Table 4-72 Description of Commands for Enabling/Disabling MBR Mapping toAMBR .................................................................................................... 4-74

Table 4-73 Description of Commands for Setting PCRF Failure ProcessingPolicies .................................................................................................. 4-74

Table 4-74 Description of Commands for Configuring Dynamic PCC Rule Continueor Not for Pcrf Exception ........................................................................ 4-75

VII


Table 4-75 Description of Commands for Configuring PCC Charging RuleSelection................................................................................................ 4-75

Table 4-76 Description of Commands for Configuring PCC Redirected ServiceCharging Policy...................................................................................... 4-75

Table 4-77 Description of Commands for Setting Whether to Enable PCC DynamicRule Request ......................................................................................... 4-75

Table 4-78 Description of Commands for Setting Whether to Enable PCC ServiceClassification Matching .......................................................................... 4-76

Table 4-79 Description of Commands for Setting Default Service App ID ................ 4-76

Table 4-80 Description of Commands for Setting Digit Number Analysis AccessType....................................................................................................... 4-76

Table 4-81 Description of Commands for Setting Whether to Enable the Blacklistand Whitelist Control Function................................................................ 4-76

Table 4-82 Command for Configuring Access List Name......................................... 4-78

Table 4-83 Command for Setting SNMP Message Community String...................... 4-78

Table 4-84 Command for Setting the SNMP Context............................................... 4-78

Table 4-85 Command for Seting the Switches and Types of notifications to be Sentby an Agent............................................................................................ 4-79

Table 4-86 Command for Seting the Switches and Types of Traps to be Sent by anAgent ..................................................................................................... 4-79

Table 4-87 Command of Setting Local Engine ID of SNMP ..................................... 4-80

Table 4-88 Command of Mapping SNMP Subscribers to SNMP View ..................... 4-80

Table 4-89 Command of Setting the Destination for Receiving SNMPNotifications ........................................................................................... 4-81

Table 4-90 Command of Setting the Maximal Length of an SNMP Message ........... 4-81

Table 4-91 Command for Configuring Source IP Address of All Traps..................... 4-82

Table 4-92 Command for Configuring an SNMPv3 Subscriber ................................ 4-82

Table 4-93 Command for Setting the SNMP View ................................................... 4-82

VIII

GlossaryAAA- Authentication, Authorization and Accounting

AN- Access Network

CU- Charging Unit

DNS- Domain Name Server

DPI- Deep Packet Inspection

EMS- Network Element Management System

FA- Foreign Agent

GSU- General Service Unit

HA- Home Agent

IP- Internet Protocol

L2TP- Layer2 Tunnel Protocol

LAC- L2TP Access Concentrator

LIC- Lawful Interception Center

LIG- Lawful Interception Gateway

MBR- Master Boot Record

MPU- Management Process Unit

NAS- Network Access Service

IX


PCC- Policy and Charging Control

PCEF- Policy and Charging Enforcement Function

PCF- Packet Control Function

PCF is a board which is responsible for the data selection between multiplereverse traffic channels and data distribution from a forward traffic channel tomultiple cells/sectors during soft handoff.

PDSN- Packet Data Service Node

PDSS- Packet Data Switching System

PFU- Packet Forwarding Unit

PLMN- Public Land Mobile Network

QoS- Quality of Service

RADIUS- Remote Authentication Dial In User Service

RAT- Radio Access Technology

RP- RAN and PDSN

RTSP- Real-Time Streaming Protocol

SGSN- Service GPRS Supporting Node

SLB- Service Load Balancing

VRF- Virtual Route Forwarding Table

XSFC- X86 Service Funtion Card

xDPI- Extended Deep Packet Inspection

X

Documents

SJ-20110222160920-007-ZXUN xGW (V4.10.21) Extendable GateWay PDSN Data Configuration Guide