system integration-(v900r007c02 02)

8/13/2019 System Integration-(V900R007C02 02)

1/337

HUAWEI PDSN9660 Packet Data Serving Node

V900R007C02

System Integration

Issue 02

Date 2009-04-10

Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd.


2/337

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For anyassistance, please contact our local office or company headquarters.

Huawei Technologies Co., Ltd. Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Copyright Huawei Technologies Co., Ltd. 2009. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent of Huawei Technologies Co., Ltd. Trademarks and Permissions

and other Huawei trademarks are the property of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders. Notice

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but the statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd.
http://www.huawei.com/


3/337

Contents

About This Docum ent.....................................................................................................................1

1 Basis of System Integration......................................................................................................1-11.1 Starting the LMT.............................................................................................................................................1-2

1.2 Overview of CLI Views..................................................................................................................................1-61.3 Configuring Data by Using CLI Commands...................................................................................................1-9

2 Configuring t he Data for the PCF...........................................................................................2-12.1 Configura tion Preparation...............................................................................................................................2-3

2.2 Networkin g for Connecting to the PCF...........................................................................................................2-3

2.3 Co nfiguring the Physical Interface..................................................................................................................2-6

2.4 Configuring t he Eth-trunk Interface................................................................................................................2-7

2.5 Configuring t he R-P Interface.........................................................................................................................2-8

2.6 Configuring the Static Route to the PCF.........................................................................................................2-8

2.7 Setting the SPI Parameters..............................................................................................................................2-92.8 Configuring the A11 Timer...........................................................................................................................2-10

2.9 Commissioning the Data for the Interworking with the PCF........................................................................2-11

2.10 Configuration Example...............................................................................................................................2-12

2.10.1 Networking of the PDSN9660 and the PCF.......................................................................................2-12

2.10.2 Reliability Networking of the PDSN9660 and the PCF.....................................................................2-14

3 Configuring t he Data for the AAA Server............................................................................3-13.1 Configura tion Preparation...............................................................................................................................3-3

3.2 Planning t he Networking for Connecting to the AAA Server........................................................................3-3

3.3 Cr eating a VPN Instance.................................................................................................................................3-83.4 Configuri ng the Physical Interface..................................................................................................................3-9

3.5 Configuri ng the Eth-trunk Interface..............................................................................................................3-10

3.6 Configuring the Sub-interface.......................................................................................................................3-11

3.7 Configuring the Pi Interface..........................................................................................................................3-12

3.8 Configuring the GRE VPN...........................................................................................................................3-13

3.8 .1 Creating the Loopback Interface..........................................................................................................3-13

3.8.2 Creating the Tunnel Interface...............................................................................................................3-14

3.8.3 Configuring the Keepalive Function....................................................................................................3-16

3.9 Configuring the IPSec Policy........................................................................................................................3-17

3.9.1 Configuring the Protected Data Flows.................................................................................................3-19

HUAWEI PDSN9660 Packet Data Serving NodeSystem Integration Contents

Issue 02 (2009-04-10) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd.

i


4/337

3.9.2 Configuring the IPSec Proposal...........................................................................................................3-20

3.9.3 Configuring the IKE Security Proposal...............................................................................................3-22

3.9.4 Configuring the IKE Peer Attributes....................................................................................................3-23

3.9.5 Configuring the IKE Local ID.............................................................................................................3-24

3.9.6 Configuring the IKE DPD Function.....................................................................................................3-25

3.9.7 Conf iguring the Attributes of the IKE Keepalive Mechanism.............................................................3-25

3.9 .8 Configuring the IPSec Policy...............................................................................................................3-26

3.9.9 Applying an IPSec Policy to an Interface............................................................................................3-29

3.10 Configuring the Static Route to the AAA Server........................................................................................3-30

3.11 Configuring the Dynamic Route to the AAA Server..................................................................................3-32

3.12 Configuring the AAA Authentication/Accounting Server..........................................................................3-34

3.13 Commissioning the Data for the Interworking with the AAA Server.........................................................3-36


3.14.1 Inband Networking.............................................................................................................................3-373.14.2 Outband Networking..........................................................................................................................3-41

3.14.3 GRE VPN in Inband Networking.......................................................................................................3-47

3.1 4.4 GRE VPN in Outband Networking....................................................................................................3-52

3.14.5 IPS ec Policy Applied to the Pi Interface............................................................................................3-60

4 Configuring the Data for the OCS..........................................................................................4-14.1 Planning the Networking for Connecting to the OCS.....................................................................................4-3

4.2 Creating a VPN Instance.................................................................................................................................4-6

4.3 Configuring the Physical Interface..................................................................................................................4-7

4.4 Configuring the Eth-trunk Interface................................................................................................................4-8

4.5 Configuring the Sub-interface.........................................................................................................................4-9

4.6 Configuring the Gy Interface........................................................................................................................4-10

4.7 Configuring the Static Route to the OCS......................................................................................................4-11

4.8 Configuring the Dynamic Route to the OCS................................................................................................4-12

4.9 Configuring the OCS Information.................................................................................................................4-14

4.10 C ommissioning the Data for the Interworking with the OCS.....................................................................4-15

4.11 Configuratio n Example...............................................................................................................................4-16

5 Configuring the Data for the HA............................................................................................5-15.1 Configuration Preparation...............................................................................................................................5-3

5.2 Networking for Connecting to the HA............................................................................................................5-3



5.5 Configuring the Pi Interface............................................................................................................................5-7

5.6 Configuring the Static Route to the HA..........................................................................................................5-8

5.7 Commissioning the Data for the Interworking with the HA...........................................................................5-9

5.8 Configuration Example.................................................................................................................................5-10

6 Configuring the Data for the PDN......................................................................................... 6-16.1 Configuration Preparation...............................................................................................................................6-3

ContentsHUAWEI PDSN9660 Packet Data Serving Node

System Integration

ii Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd.

Issue 02 (2009-04-10)


5/337

6.2 Planning the Networking for Connecting to the PDN.....................................................................................6-3

6.3 Creating a VPN Instance.................................................................................................................................6-7



6.6 Configuring the Sub-interface.......................................................................................................................6-10

6.7 Configuring t he L2TP VPN..........................................................................................................................6-11

6.8 Configuri ng the GRE VPN...........................................................................................................................6-12

6.8.1 Creating the Loopback Interface..........................................................................................................6-13

6.8.2 Creating the Tunnel Interface...............................................................................................................6-14

6.8.3 Configu ring the Keepalive Function....................................................................................................6-15

6.9 Configuring t he IPSec Policy........................................................................................................................6-16

6.9.1 Configu ring the Protected Data Flows.................................................................................................6-18

6.9.2 Configu ring the IPSec Proposal...........................................................................................................6-19

6.9.3 Configu ring the IKE Security Proposal...............................................................................................6-216.9.4 Configu ring the IKE Peer Attributes....................................................................................................6-22

6.9.5 Configu ring the IKE Local ID.............................................................................................................6-23

6.9.6 Configu ring the IKE DPD Function.....................................................................................................6-24

6.9.7 Conf iguring the Attributes of the IKE Keepalive Mechanism.............................................................6-24

6.9 .8 Configuring the IPSec Policy...............................................................................................................6-25

6.9.9 Applying an IPSec Policy to an Interface............................................................................................6-28

6.10 Configuring the Static Route to the PDN....................................................................................................6-29

6.11 Configuring the Dynamic Route to the PDN..............................................................................................6-31

6.12 Configuring the Downlink Route from the P Interface to the MS..............................................................6-336.13 Commissioning the Data for the Interworking with the PDN.....................................................................6-35


6.14.1 Eth-trunk Load-sharing Mode + Dynamic Routing...........................................................................6-36

6.14.2 Dynamic Routing + L2TP VPN Tunnel.............................................................................................6-40

6.14.3 IPSec Policy Applied to the Tunnel Interface....................................................................................6-44

7 Configuring Ser vice Data.........................................................................................................7-17.1 Configuring t he Domain Data.........................................................................................................................7-2

7.1.1 Applicat ion Scheme for the Domain......................................................................................................7-3

7.1.2 Configu ring PPP Negotiation Parameters..............................................................................................7-87.1.3 Configu ring the Basic Domain Information.........................................................................................7-10

7.1.4 Configu ring the Constructed Domain..................................................................................................7-13

7.1.5 Configu ring the Authentication Data and Accounting Data for the Domain.......................................7-14

7.1.6 Configu ring the Local Address Pool....................................................................................................7-15

7.1.7 Conf iguring the DNS Information.......................................................................................................7-17

7.1.8 Configu ring the Downlink Route to the MS........................................................................................7-19

7.1.9 Commis sioning the Domain Data........................................................................................................7-23

7.1.10 Config uration Example......................................................................................................................7-24

7.2 Configuri ng the Security...............................................................................................................................7-38

7.2.1 App lication Schemes for the Security Function...................................................................................7-39



iii


6/337

7.2.2 Configuring the Packet Filtering Policy...............................................................................................7-41

7.2.3 Configuring the Anti-DDoS Function..................................................................................................7-43

7.2.4 Configuring the Pi Redirection Function.............................................................................................7-43

7.2.5 Configuring the IPSec Policy...............................................................................................................7-44

7.2.6 Maintaining the Data for the Security Function...................................................................................7-58

7.2.7 Conf iguration Example........................................................................................................................7-59

7.3 Configuring t he Data for the FA...................................................................................................................7-68

7.3.1 Applicat ion Scheme for the FA............................................................................................................7-69

7.3.2 Configu ring the Foreign Agent Care-of Address.................................................................................7-70

7.3.3 Configu ring the FA..............................................................................................................................7-71

7.3.4 Conf iguring the SA Between the MN and the FA...............................................................................7-73

7.3.5 Configu ring the SA Between the FA and the HA................................................................................7-74

7.3.6 Commis sioning the Data for the FA Function.....................................................................................7-75

7.3.7 Configu ration Example........................................................................................................................7-757.4 Configuring t he Data for RADIUS Authentication and Accounting............................................................7-78

7.4.1 Planning the Application Scheme for RADIUS Authentication and Accounting................................7-79

7.4.2 Configu ring RADIUS Authentication..................................................................................................7-80

7.4.3 Configu ring RADIUS Accounting.......................................................................................................7-81

7.4.4 Configu ring the Charging Characteristic.............................................................................................7-82

7.4.5 Configu ring the Charging Parameters..................................................................................................7-83

7.4.6 Configu ring the Tariff Switch Function...............................................................................................7-84

7.4.7 Configu ring the UDR Cache Function.................................................................................................7-85

7.4.8 Mai ntaining the Data for RADIUS Authentication and Accounting...................................................7-867.4.9 Example of RADIUS Authentication and Accounting........................................................................7-86

7.5 Configuring t he Data for the Diameter Online Charging Function...............................................................7-89

7.5.1 Applicat ion Schemes for Online Charging..........................................................................................7-90

7.5.2 Configu ring the Gy Interface...............................................................................................................7-93

7.5.3 Configu ring the OCS Information........................................................................................................7-94

7.5.4 Configu ring the Primary and Secondary OCSs....................................................................................7-94

7.5.5 Configu ring the Quota Threshold........................................................................................................7-95

7.5.6 Configu ring the Mode for Sending a CCR Message............................................................................7-96

7.5.7 Configu ring the Conditions for Sending a CCR Message...................................................................7-97

7.5.8 Conf iguring the Tx Timer....................................................................................................................7-98

7.5.9 Configu ring the Service Processing Actions........................................................................................7-99

7.5.10 Mainta ining the Data for the Diameter Online Charging Function..................................................7-100

7.5.11 Config uration Example....................................................................................................................7-101

7.6 Configuring t he Data for the Content-based Charging Function................................................................7-108

7.6.1 Applicat ion Schemes for Content-based Charging............................................................................7-108

7.6.2 Configu ring the Content-based Charging Function...........................................................................7-110

7.6.3 Maintai ning the Data for the Content-based Charging Function.......................................................7-113

7.6.4 Conf iguration Example......................................................................................................................7-115

7.7 Configuring t he Data for the Service Resolution and Control Function.....................................................7-121

ContentsHUAWEI PDSN9660 Packet Data Serving Node

System Integration

iv Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd.

Issue 02 (2009-04-10)


7/337

7.7.1 Planning the Application Scheme for Service Control......................................................................7-121

7.7.2 Configuring the Service Control Function.........................................................................................7-123

7.7.3 Maintaining the Data for the Service Control Function.....................................................................7-126

7.7.4 Configuration Example......................................................................................................................7-127

A Glossary.....................................................................................................................................A-1

B Abbreviation..............................................................................................................................B-1



v


8/337


9/337

Figures

Figure 1-1 User login ...........................................................................................................................................1-3

Figure 1-2 O ffice Management dialog box ........................................................................................................1-4

Figure 1-3 Add dialog box...................................................................................................................................1-4

Figure 1-4 User login ...........................................................................................................................................1-5

Figure 1-5 CLI view structure on the PDSN9660 V900R007.............................................................................1-7

Figure 2-1 Networking for the interworking between the PDSN9660 and the PCF............................................2-4

Figure 2-2 Networking for the interworking between the PDSN9660 and the PCF..........................................2-12

Figure 2-3 Re liability networking for the interworking between the PDSN9660 and the PCF.........................2-15

Figure 3-1 Co nfiguration procedure.....................................................................................................................3-4

Figure 3-2 In band networking and outband networking......................................................................................3-7

Figure 3-3 Co nfiguration procedure for the IPSec policy..................................................................................3-18

Figure 3-4 Co nfiguration of the IPSec proposal................................................................................................3-20

Figure 3-5 IK E proposal configuration map......................................................................................................3-22

Figure 3-6 IK E peer configuration procedure....................................................................................................3-23Figure 3-7 IPSec policy through manual configuration.....................................................................................3-26

Figure 3-8 IPSec policy through the IKE negotiation........................................................................................3-27

Figure 3-9 Networking for the interworking between the PDSN9660 and the AAA server.............................3-37

Figure 3-10 Networking for the interworking between the PDSN9660 and the AAA server...........................3-42

Figure 3-11 GRE VPN networking....................................................................................................................3-47

Figure 3-12 GRE VPN networking....................................................................................................................3-53

Figure 3-13 Networking of setting up a security tunnel between the PDSN9660 and the AAA server............3-60


Figure 4-2 Networking for the interworking between the PDSN9660 and the OCS.........................................4-16

Figure 5-1 Co nfiguration procedure for the interworking between the PDSN9660 and the HA.........................5-4

Figure 5-2 Networking for the interworking between the PDSN9660 and the HA...........................................5-10


Figure 6-2 Co nfiguration procedure for the IPSec policy..................................................................................6-17

Figure 6-3 Co nfiguration of the IPSec proposal................................................................................................6-19

Figure 6-4 IK E proposal configuration map......................................................................................................6-21

Figure 6-5 IKE peer configuration procedure....................................................................................................6-22

Figure 6-6 IPSec policy through manual configuration.....................................................................................6-25

Figure 6-7 IPSec policy through the IKE negotiation........................................................................................6-26

Figure 6-8 Networking for the interworking between the PDSN9660 and the PDN.........................................6-36

HUAWEI PDSN9660 Packet Data Serving NodeSystem Integration Figures


vii


10/337

Figure 6-9 L2TP VPN networking.....................................................................................................................6-41

Figure 6-10 Networking of setting up a security tunnel between the PDSN9660 and the enterprise gateway.............................................................................................................................................................................6-44

Figure 7-1 Configuring the domain......................................................................................................................7-4

Figure 7-2 Principles for DNS selection............................................................................................................7-18

Figure 7-3 Address assignment from the local address pool with a complete address segment........................7-20

Figure 7-4 Address assignment from the local address pool with an incomplete address segment...................7-21

Figure 7-5 Address assignment by the RADIUS server (address segment known in advance).........................7-22

Figure 7-6 Networking for an MS to access the IP network of an operator.......................................................7-25

Figure 7-7 Networking for an MS to access the network of an ISP...................................................................7-28

Figure 7-8 Networking for an MS to access an intranet.....................................................................................7-31

Figure 7-9 Address assignment from the local address pool with a complete address segment........................7-34

Figure 7-10 Address assignment from the local address pool with an incomplete address segment.................7-34

Figure 7-11 Address assignment by the RADIUS server (address segment known in advance).......................7-37Figure 7-12 Data transmission...........................................................................................................................7-42

Figure 7-13 Configuration procedure for the IPSec policy................................................................................7-45

Figure 7-14 Configuration of the IPSec proposal..............................................................................................7-47

Figure 7-15 IKE proposal configuration map....................................................................................................7-50

Figure 7-16 IKE peer configuration procedure..................................................................................................7-51

Figure 7-17 IPSec policy through manual configuration...................................................................................7-54

Figure 7-18 IPSec policy through the IKE negotiation......................................................................................7-54

Figure 7-19 Preventing attacks from an MS or a PDN user to devices on the core network.............................7-60

Figure 7-20 Packet redirection through the PDSN.............................................................................................7-64

Figure 7-21 Networking of setting up a security tunnel between the PDSN9660 and the AAA server............7-66

Figure 7-22 Configuring the FA function..........................................................................................................7-69

Figure 7-23 Networking for the MIP service.....................................................................................................7-76

Figure 7-24 Networking for a MS to access the enterprise network..................................................................7-87

Figure 7-25 Configuration procedure for online charging.................................................................................7-91

Figure 7-26 Networking of Diameter online charging.....................................................................................7-102

Figure 7-27 Networking of Diameter online charging.....................................................................................7-105

Figure 7-28 Configuration procedure for content-based charging...................................................................7-109

Figure 7-29 Networking for CBC....................................................................................................................7-115

Figure 7-30 Networking for CBC....................................................................................................................7-118

Figure 7-31 Configuring Procedure.................................................................................................................7-122

FiguresHUAWEI PDSN9660 Packet Data Serving Node

System Integration

viii Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd.

Issue 02 (2009-04-10)


11/337

Tables

Table 1-1 De scription of the CLI views...............................................................................................................1-7

Table 1-2 Co mmand syntax..................................................................................................................................1-9

Table 2-1 Co mmon networking schemes.............................................................................................................2-6

Table 2-2 Dis playing the data for the interworking between the PDSN and the PCF..................... ..................2-11

Table 2-3 Del eting the data for the interworking between the PDSN and the PCF...........................................2-12


Table 3-2 Co ncepts of the OSPF dynamic routing mode...................................................................................3-32

Table 3-3 Dis playing the data for the interworking between the PDSN and the AAA server...........................3-36

Table 3-4 Del eting the data for the interworking between the PDSN and the AAA server...............................3-36


Table 4-2 Co ncepts of the OSPF dynamic routing mode...................................................................................4-12

Table 4-3 Dis playing the data for the interworking between the PDSN9660 and the OCS...............................4-15

Table 4-4 Del eting the data for the interworking between the PDSN9660 and the OCS..................................4-15

Table 5-1 Co mmon networking scheme...............................................................................................................5-5Table 6-1 Co mmon networking schemes.............................................................................................................6-7

Table 6-2 Co ncepts of the OSPF dynamic route................................................................................................6-31

Table 7-1 Co mmon application schemes of the domain...................................................................................... 7-6

Table 7-2 Au thentication negotiation between the MS and the PDSN9660........................................................7-9

Table 7-3 Co mmon application schemes of the security function.....................................................................7-40

Table 7-4 Dis playing the configuration of the security function........................................................................7-58

Table 7-5 Del eting the configuration of the security function...........................................................................7-59

Table 7-6 Co mmon application scheme.............................................................................................................7-70

Table 7-7 Dis playing the RADIUS authentication and accounting configuration.............................................7-86

Table 7-8 Del eting the RADIUS authentication and accounting configuration.................................................7-86

Table 7-9 Co mmon application schemes of online charging.............................................................................7-92

Table 7-10 Displaying the Diameter online charging configuration................................................................7-101

Table 7-11 Deleting the Diameter online charging configuration....................................................................7-101

Table 7-12 Common application schemes of content-based charging.............................................................7-110

Table 7-13 Displaying the CBC configuration.................................................................................................7-113

Table 7-14 Deleting the CBC configuration.....................................................................................................7-114

Table 7-15 Common networking schemes.......................................................................................................7-123

Table 7-16 Displaying the service control configuration.................................................................................7-126

Table 7-17 Deleting the service control configuration.....................................................................................7-127

HUAWEI PDSN9660 Packet Data Serving NodeSystem Integration Tables


ix


12/337


13/337

About This Document

Purpose

This document describes the configuration methods and procedures of system integration for specific services of the PDSN9660.

Related Versions

The following table lists the product version related to this document.

Product Name Version

PDSN9660 V900R007C02

Intended Audience

This document is intended for:

l Installation commissioning engineer

l Data configuration engineer

Update History

Updates between document versions are cumulative. Therefore, the latest document versioncontains all updates made to previous issues.

Updates in Issue 02 (2009-04-10)

The second commercial release has the following updates:

The mistakes are corrected.

Updates in Issue 01 (2009-01-05)

Initial commercial release.

Organization

1 Basis of System Integration

Before system integration, you need to set up the configuration environment and learn how touse the local maintenance terminal (LMT) and the command line interface (CLI) commands.

2 Configuring the Data for the PCF

HUAWEI PDSN9660 Packet Data Serving NodeSystem Integration About This Document


1


14/337

The PDSN9660 interworks with the packet control function (PCF) through a physical interfaceand the R-P interface.

3 Configuring the Data for the AAA Server

The PDSN9660 supports Remote Authentication Dial In User Service (RADIUS) authenticationand accounting. It can assign an IP address to a mobile station (MS) through the authorization,authentication and accounting (AAA) server. Before setting parameters of authentication,accounting, or address assignment, ensure that the PDSN9660 interworks with the AAA server.

4 Configuring the Data for the OCS

The PDSN9660 provides the traffic plane function (TPF). With the TPF function, thePDSN9660 differentiates various content-based charging (CBC) services and collects thecharging information. The PDSN9660 performs the online charging for normal users and CBCusers by interworking with the online charging system (OCS) through the Gy interface.

5 Configuring the Data for the HA

This describes how to configure the data for the home agent (HA).

6 Configuring the Data for the PDN

The PDSN9660 is a gateway device that enables a mobile station (MS) to access an external packet data network (PDN). To carry out data service for an MS, the PDSN9660 needs tointerwork with network elements (NEs) on the PDN.

7 Configuring Service Data

This describe s how to configu re service data such as domain, security, Remote AuthenticationDial In User Service (RADIUS) authentication and accounting, content-based charging, andservice contr ol.

A Glossary

B Abbreviation

ConventionsSymbol Conventions

The symbols that may be found in this document are defined as follows.

Symbol Description

Indicates a hazard with a high level of risk, which if notavoided,will result in death or serious injury.

Indicates a hazard with a medium or low level of risk, whichif not avoided, could result in minor or moderate injury.

Indicates a potentially hazardous situation, which if notavoided,could result in equipment damage, data loss,

performance degradation, or unexpected results.

About This DocumentHUAWEI PDSN9660 Packet Data Serving Node

System Integration

2 Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd.

Issue 02 (2009-04-10)


15/337

Symbol Description

Indicates a tip that may help you solve a problem or savetime.

Provides additional information to emphasize or supplementimportant points of the main text.

General Conventions

The general conventions that may be found in this document are defined as follows.

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are inboldface . For example, log in as user root .

Italic Book titles are in italics .

Courier New Examples of information displayed on the screen are inCourier New.

Command Conventions

The command conventions that may be found in this document are defined as follows.


Boldface The keywords of a command line are in boldface .

Italic Command arguments are in italics .

[ ] Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... } Optional items are grouped in braces and separated byvertical bars. One item is selected.

[ x | y | ... ] Optional items are grouped in brackets and separated byvertical bars. One item is selected or no item is selected.

{ x | y | ... } * Optional items are grouped in braces and separated byvertical bars. A minimum of one item or a maximum of allitems can be selected.

[ x | y | ... ] * Optional items are grouped in brackets and separated byvertical bars. Several items or no item can be selected.

GUI Conventions

The GUI conventions that may be found in this document are defined as follows.

HUAWEI PDSN9660 Packet Data Serving NodeSystem Integration About This Document


3


16/337


Boldface Buttons, menus, parameters, tabs, window, and dialog titlesare in boldface . For example, click OK .

> Multi-level menus are in boldface and separated by the ">"signs. For example, choose File > Create > Folder .

Keyboard Operations

The keyboard operations that may be found in this document are defined as follows.

Format Description

Key Press the key. For example, press Enter and press Tab .

Key 1 +Key 2 Press the keys concurrently. For example, pressing Ctrl +Alt+A means the three keys should be pressed concurrently.

Key 1 , Key 2 Press the keys in turn. For example, pressing Alt , A meansthe two keys should be pressed in turn.

Mouse Operations

The mouse operations that may be found in this document are defined as follows.

Action Description

Click Select and release the primary mouse button without movingthe pointer.

Double-click Press the primary mouse button twice continuously andquickly without moving the pointer.

Drag Press and hold the primary mouse button and move the pointer to a certain position.

About This DocumentHUAWEI PDSN9660 Packet Data Serving Node

System Integration

4 Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd.

Issue 02 (2009-04-10)


17/337

1 Basis of System IntegrationAbout This Chapter

Before system integration, you need to set up the configuration environment and learn how touse the local maintenance terminal (LMT) and the command line interface (CLI) commands.

1.1 Starting the LMTThis describes how to start the local maintenance terminal (LMT) and set up the connection withthe PDSN966 0.

1.2 Overview of CLI ViewsThis describe s the command line interface (CLI) views. In addi tion to the graphical user interface(GUI), the local maintenance terminal (LMT) provides the CLI. The PDSN9660 providesabundant CL I commands for you to operate and maintain the system.

1.3 Configuri ng Data by Using CLI CommandsThe local ma intenance terminal (LMT) pr ovides a set of configuration commands. Users canconfigure and manage the PDSN9660 by entering these commands in the command line interface(CLI) to ensu re that the system runs normally.

HUAWEI PDSN9660 Packet Data Serving NodeSystem Integration 1 Basis of System Integration


1-1


18/337

1.1 Starting the LMT

This describes how to start the local maintenance terminal (LMT) and set up the connection withthe PDSN9660.

Prerequisitel The LMT software is installed. See Checking the Installation of the LMT Software.

l The LMT is connected to the PDSN9660.

Context

CAUTION

Logging in to the PDSN9660 through Telnet is prohibited.

WARNING

Do not modify the system time when the LMT programs are running. This helps to prevent

system errors. You can modify the system time only after all the LMT application programs arestopped.

Procedure

Step 1 Check whether the icon of LMT Service Manager exists in the notification area of thetaskbar.

Condition Operation

The icon of LMT Service Manager exists. It indicates that the LMT service manager isstarted. Go to Step 2 .

The icon of LMT Service Manager doesnot exist.

Choose Start > Programs > Huawei LocalMaintenance Terminal > LMT ServiceManager to start the LMT service manager onthe computer where the LMT is installed. Then,go to Step 2 .

Step 2 Choose Start > Programs > Huawei Local Maintenance Terminal > Local MaintenanceTerminal . The User Login dialog box is displayed. See Figure 1-1 .

1 Basis of System IntegrationHUAWEI PDSN9660 Packet Data Serving Node

System Integration

1-2 Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd.

Issue 02 (2009-04-10)


19/337

Start for the First Time? Operation

Yes Go to Step 3 .

No Select an office to which the LMT is connected in the Officedropdown list box. Go to Step 6 .

Figure 1-1 User login

NOTE

l Domain user: indicates that this user is managed by the M2000 domain.

l Local user: indicates that this user is managed by the local LMT.

NOTE

l You can also log in to the LMT by clicking Offline . Thus, you can use some of the functions of theLMT offline, such as help browsing, eliminating the need to log in to the PDSN9660.

l You can log out of the LMT by clicking Exit .

Step 3 Set the office information if you log in to the PDSN9660 for the first time. Click . The OfficeManagement dialog box is displayed. See Figure 1-2 .



1-3


20/337


21/337

NOTE

If the M2000 proxy server is located between the LMT and the PDSN9660, set the IP address of ProxyServer in the Add dialog box.

Step 5 Click Close in the Office Management dialog box. The office configuration is complete. TheUser Login dialog box is displayed. See Figure 1-4 .

Figure 1-4 User login

Step 6 Enter the user name and the password, and specify the user type. Then, click Login to access

the main interface of the LMT.

If the status is "Connected" and the IP address displayed in the bottom of the window, it indicatesthat the LMT is correctly connected to the PDSN9660. Thus, you can perform service and dataconfigurations for the PDSN9660 by using command line interface (CLI) commands on thiswindow.

NOTE

When logging in to the LMT for the first time, you must log in as an admin user. The password is determinedwhen the PDSN9660 software is installed.

NOTE

The user type can be EMS or Local .

l EMS user are managed by the M2000. The element management system (EMS) user account is usedfor management during routine maintenance. For the user that logs in to the M2000, the PDSN9660sends the information about user authentication to the M2000, and then the M2000 performs user authentication.

l Local users are managed by the LMT of the PDSN9660. The local user account is used for deploymentand upgrade. For the user that logs in to the LMT, the PDSN9660 performs user authentication by usingthe local user profile.

----End



1-5


22/337

1.2 Overview of CLI ViewsThis describes the command line interface (CLI) views. In addition to the graphical user interface(GUI), the local maintenance terminal (LMT) provides the CLI. The PDSN9660 providesabundant CLI commands for you to operate and maintain the system.

When the CLI is displayed, the initial user view is displayed. The CLI consists of command lineviews each with registered commands. The command line view must be displayed first for youto run a command that is registered in this view.

CLI Views on the PDSN9660 V900R007The CLI on the PDSN9660 V900R007 is composed of the following views:

l Charge view: The information related to charging is configured in this view.

l Domain view: The information related to domains is configured in this view.

l MIP view: The information related to mobile IP (MIP) is configured in this view.

l Interface view: The information related to interfaces such as physical interfaces, logicalinterfaces, and sub-interfaces is configured in this view.

l Access view: The access resources, including the Remote Authentication Dial In User Service (RADIUS) information, address pool, quality of service (QoS), and Layer 2Tunneli ng Protocol (L2TP) group, are configured in this view.

l Service view: The information related to service control is configured in this view.

l Operation and maintenance view: The information related to alarm management, performance measurement, and software management is configured in this view.

l Security view: The information related to the IP Security (IPSec) protocol and the InternetKey Exchange (IKE) protocol is configured in this type of view. Security views consist of the IPSec view, IPSec policy view, IKE peer view, and IKE proposal view.

CLI View Structure on the PDSN9660 V900R007Figure 1-5 shows the structure of CLI views on the PDSN9660 V900R007.


System Integration


Issue 02 (2009-04-10)


23/337

Figure 1-5 CLI view structure on the PDSN9660 V900R007

DCC template view

DCC global view

User view System view

Charge view

Domain view

MIP view

Interface view

Access view

RADIUS view

Address pool view

QoS view

L2TP group view

Service view

OM view

IPSec view

IPSec policy view

IKE peer view

IKE proposal view

User profileinstance view

Lawful interception view

Usage Guideline of the CLI Views on the PDSN9660 V900R007

Table 1-1 lists the CLI views.

Table 1-1 Description of the CLI views

View Prerequisite Command

User view You are logged in tothe LMT.

System view The user view isdisplayed.

system-view

[PDSN]



1-7


24/337


Charge view The system view isdisplayed.

system-view[PDSN]charge-view[PDSN-charge]

DCC template view The charge view isdisplayed.

system-view[PDSN]charge-view[PDSN-charge]dcc-template test[PDSN-dcc-test]

DCC global view The charge view isdisplayed.

system-view[PDSN]charge-view[PDSN-charge]dcc-global-view[PDSN-dcc-global]

Domain view The system view isdisplayed.

system-view[PDSN]domain testdomain[PDSN-domain-testdomain]

MIP view The system view isdisplayed.

system-view

[PDSN]mip enable[PDSN-mip-view]

Physical interfaceview

The system view isdisplayed.

system-view[PDSN]interface GigabitEthernet 0/0/0[PDSN-GigabitEthernet0/0/0]

Logical interfaceview


system-view[PDSN]interface rpif3/0/0[PDSN-rpif3/0/0]

Sub-interface view The Eth-trunk interface view or

physical interfaceview is displayed.

system-view[PDSN]interface Eth-Trunk 0[PDSN-Eth-Trunk0][PDSN]interface Eth-Trunk0.1[PDSN-Eth-Trunk0.1]

Eth-trunk interfaceview


system-view[PDSN]interface Eth-Trunk 0[PDSN-Eth-Trunk0]

Loopback interfaceview


system-view[PDSN]interface LoopBack 0[PDSN-LoopBack0]

Tunnel interfaceview


system-view[PDSN]interface Tunnel 1/0/0[PDSN-Tunnel1/0/0]

Access view The system view isdisplayed.

access-view[PDSN]access-view[PDSN-access]

RADIUS view The access view isdisplayed.

system-view[PDSN]access-view[PDSN-access]radius-server grouptestaaa[PDSN-access-radius-testaaa]

Address pool view The access view isdisplayed.

system-view[PDSN]access-view[PDSN-access]ip pool testpool[PDSN-access-ip-pool-testpool]

QoS view The access view isdisplayed.

system-view[PDSN]access-view[PDSN-access]qos-view

[PDSN-access-qos]


System Integration


Issue 02 (2009-04-10)


25/337


L2TP group view The access view isdisplayed.

system-view[PDSN]access-view[PDSN-access]l2tp group 1[PDSN-l2tp-group-1]

Lawful interceptionview


system-view[PDSN]li-view[PDSN-li]

Service view The system view isdisplayed.

system-view[PDSN]service-view[PDSN-service]

User profile view The service view isdisplayed.

[PDSN-service]user-profile testprofile[PDSN-service-profile-testprofile]

IP farm view The service view isdisplayed.

system-view[PDSN]service-view[PDSN-service][PDSN-service]ip-farm testfarm[PDSN-service-ip-farm-testfarm]

Operation andmaintenance view


system-view[PDSN]om-view[PDSN-om-view]

IPSec proposalview


system-view[PDSN]ipsec proposal testproposal[PDSN-ipsec-proposal-testproposal]

IPSec policy view The system view isdisplayed.

system-view[PDSN]ipsec policy testpolicy 100manual[PDSN-ipsec-policy-manual-

testpolicy-100]

IKE peer view The system view isdisplayed.

system-view[PDSN]ike peer testpeer[PDSN-ike-peer-testpeer]

IKE proposal view The system view isdisplayed.

system-view[PDSN]ike proposal 1[PDSN-ike-proposal-1]

1.3 Configuring Data by Using CLI CommandsThe local maintenance terminal (LMT) provides a set of configuration commands. Users canconfigure and manage the PDSN9660 by entering these commands in the command line interface(CLI) to ensure that the system runs normally.

CLI Command Overview

A CLI command may contain key words, arguments, and values. See Table 1-2 .

Table 1-2 Command syntax

Syntax Description

Boldface The keywords of a command line are in boldface .



1-9


26/337

Syntax Description

Italics Command arguments are in italics .

[ ] Items (keywords or arguments) in square brackets [ ] are optional.

{ x | y | ... } Alternative items are grouped in braces and separated by vertical bars. One is selected.

[ x | y | ... ] Optional alternative items are grouped in square brackets andseparated by vertical bars. One or none is selected.

{ x | y | ... } * Alternative items are grouped in braces and separated by vertical bars. A minimum of one or a maximum of all can be selected.

[ x | y | ... ] * Optional items are grouped in brackets and separated by vertical bars. Several items or no item can be selected.

Take the command radius-server accounting ip-address [ port port-number ] [ vpn-instance vpn-instance ] key key-string as an example.

Here, radius-server accounting is the command line keywords. port , vpn-instance , and keyare command keywords. ip-address , port-number , vpn-instance , and key-string are commandarguments.

Online Help of the Command LineThe CLI provides the following types of online help:

l Full help

Enter a question mark (?) in a command line view to display all the commands and their description in this view.

Enter a command and a question mark (?) separated by a space. If the question mark is inthe position of a keyword, all keywords and their description are displayed.

Enter a command and a question mark (?) separated by a space. If the question mark is inthe position of a parameter, the related parameter names and parameter description aredisplayed.

l Partial help

Enter a character string followed by a question mark (?) without any space to display allcommands that begin with this character string and their description.

Enter a character string followed by a question mark (?) without any space to display allkeywords that begin with this character string.

Example of Data Configuration by Using CLI CommandsThe procedure for setting the Remote Authentication Dial In User Service (RADIUS) accountingserver by using the CLI commands is as follows:

1. Enter the access view.system-view[PDSN]access-view

2. Configure the RADIUS accounting server.

Create the RADIUS server group group1.


System Integration


Issue 02 (2009-04-10)


27/337

[PDSN-access]radius-server group group1

Set the IP address of the accounting server to 10.1.1.1, port number to 1813, and key to12345.[PDSN-access-radius-group1]radius-server accounting ip 10.1.1.1 port 1813 key12345

3. Check the information about the accounting server.[PDSN-access]display radius-server accounting group1

NOTE

After all parameters are set, press Enter to run the command.



1-11


28/337


29/337

2 Configuring the Data for the PCFAbout This Chapter

The PDSN9660 interworks with the packet control function (PCF) through a physical interfaceand the R-P interface.

Prerequisitel The hardware of the PDSN9660 and the base station controller (BSC)/PCF is installed and

checked. The hardware is switched on and operates normally. For details, see Checking theInstallation.

l The local maintenance terminal (LMT) of the PDSN9660 is installed. For details, seeChecking the LMT System.

l The software of the PDSN9660 and the BSC/PCF is installed and checked. For details, seeChecking the Installation of the Host Software.

Context

Based on the 3rd Generation Partnership Project 2 (3GPP2) protocol, the PCF uses the GenericRouting Encapsulation (GRE) protocol to encapsulate uplink data packets from a mobile station(MS). The destination IP address of the encapsulated packets is the IP address of the R-P interfaceon the PDSN9660. The packets are forwarded to the PDSN9660 through the GRE tunnel betweenthe PCF and the PDSN9660. Then, the PDSN9660 GRE decapsulates the packets and forwardsthem to the packet data network (PDN).

The PDSN9660 GRE encapsulates downlink data packets to the MS from the PDN. Thedestination IP address of the encapsulated packets is the IP address of the R-P interface on thePCF. The packets are forwarded through the GRE tunnel to the PCF. Then, the PCF removesthe GRE headers and obtains the original packets. The original packets are then forwarded tothe MS.

The PDSN9660 sets up the physical path with the PCF through a physical interface. The logicalinterworking with the PCF is realized through the A10 connection. The interworking with thePCF at the network layer is realized through the routing protocol. The R-P logical interface iscreated through A11 messages. To ensure that the A11 messages are valid and reliable, you must

set the security parameter index (SPI) parameters. Then, you need to specify relevant parametersof A11 messages by configuring the A11 timer.

HUAWEI PDSN9660 Packet Data Serving NodeSystem Integration 2 Configuring the Data for the PCF


2-1


30/337

2.1 Configuration PreparationThis provides concepts related to the connection between the PDSN9660 and the packet controlfunction (PCF).

2.2 Networking for Connecting to the PCFThis describes the networking for connecting to the packet control function (PCF).

2.3 Configuring the Physical InterfaceThis describes how to configure a physical interface to establish the physical path between thePDSN9660 and the network entity.

2.4 Configuring the Eth-trunk InterfaceThis describes how to configure the Eth-trunk interface. To enhance networking reliability,configure the Eth-trunk interface to establish path between the PDSN9660 and the network entity, and enable the Address Resolution Protocol (ARP) probe function.

2.5 Configuring the R-P InterfaceThis describes how to create the logical communication path between the packet control function(PCF) and the PDSN9660.

2.6 Configuring the Static Route to the PCFThis describes how to configure the static route to realize the interworking between thePDSN9660 and the packet control function (PCF) at the network layer.

2.7 Setting the SPI ParametersThis describes how to set the security parameter index (SPI). The SPI is an extended option inan A11 mess age. It provides security parameters, such as the authentication mode and key, for reliable trans mission of the A11 message.

2.8 Configuri ng the A11 Timer This describe s how to configure the A11 timer and the Point-to-Point Protocol (PPP) timer.

2.9 Commiss ioning the Data for the Interworking with the PCFThis provides the commands for commissioning the configuration data for the interworking withthe packet co ntrol function (PCF).

2.10 Configu ration ExampleThis provides an example of the configuration for the interworking between the PDSN9660 andthe packet co ntrol function (PCF).

2 Configuring the Data for the PCFHUAWEI PDSN9660 Packet Data Serving Node

System Integration


Issue 02 (2009-04-10)


31/337

2.1 Configuration PreparationThis provides concepts related to the connection between the PDSN9660 and the packet controlfunction (PCF).

Related Concepts

Related Concept Reference

Concepts related to interfaces

Physical interface l Overview of NEs and Interfaces

l Physical Interfaces

l Relation Between Logical Interfaces and

Physical Interfacesl Interface Naming Rules

Eth-trunk interface l Logical Interfaces

l Interface Naming Rules

R-P interface Overview of the Configuration for theInterworking Between NEs

Logical interface l Logical Interfaces

l Relation Between Logical Interfaces andPhysical Interfaces

l Interface Naming Rules

Concepts related to networking modes

Networking of the single physical interfacemode

Networking of Single Physical Interface andStatic Routing Mode

Networking of Eth-trunk active/standbymode and static routing mode

Networking of Eth-trunk Active/StandbyMode and Static Routing Mode

Networking of Eth-trunk load-sharing modeand dynamic routing mode

Networking of Eth-trunk Load-sharing Modeand Dynamic Routing Mode

2.2 Networking for Connecting to the PCFThis describes the networking for connecting to the packet control function (PCF).

Configuration RoadmapFor the interworking between the PDSN9660 and the base station controller (BSC)/PCF, youmust establish the physical path and the logical link, and configure the routing protocol for theinterworking at the network layer. See Figure 2-1 .



2-3


32/337

Figure 2-1 Networking for the interworking between the PDSN9660 and the PCF

Configure data for interworking with the PCF.

Configure the R-P interface.

Configure thephysical interface.

Configure theEth-trunk interface.

Configure the staticroute to the PCF.

End

Set the SPI parameters.

(Optional)Configure the A11 timer.

Choose a networkingmode.

Simple networking Reliability networking

By clicking the following operations, you can check the corresponding configuration tasks.

l 2.3 Configuring the Physical Interface

l 2.4 Configuring the Eth-trunk Interface

l 2.5 Configuring the R-P Interface

l 2.6 Configuring the Static Route to the PCF

l 2.7 Setting the SPI Parameters

l 2.8 Configuring the A11 Timer

Configuration Task Description1. Select a networking scheme.


System Integration


Issue 02 (2009-04-10)


33/337

Networking Scheme

Networking Requirement

Characteristic

Simplenetworking

2.3Configuringthe PhysicalInterface

It is easy to configure the physical path by using asingle physical interface. This method is suitable for simple networks.

One configured physical interface can be shared by twolinks.

Reliabilitynetworking

2.4Configuringthe Eth-trunk

Interface

Eth-trunk active/standby mode: It can enhancereliability. When a member link is faulty, the traffic isautomatically switched to an available link.

Eth-trunk load-sharing mode: It can improve bandwidth usage and enhance reliability. The bandwidth of the Eth-trunk interface is the total bandwidth of all physical interfaces. If a physicalinterface is Down, other member interfaces are stillavailable for data transmission.

2. Establish the logical path. For details, see 2.5 Configuring the R-P Interface .

3. Configure the route to the BSC/PCF for the interworking at the network layer with the BSC/PCF.

Routing Protocol

Characteristic

Static routing

mode

The static routing mode is applicable for a small stable network with

simple topology.

4. Set the parameters related to the security parameter index (SPI), such as the IP address of the signaling plane on the PCF, IP address of the R-P interface on the PDSN9660, SPIvalue, authentication algorithm, authentication mode, key, and anti-replay mode. For details, see 2.7 Setting the SPI Parameters .

5. (Optional) Set the parameters related to the A11 timer and the PPP timer. For details, see2.8 Configuring the A11 Timer .

Common Networking SchemesDifferent networking schemes can meet different requirements. The common networkingschemes for the interworking with the BSC/PCF are described as follows:



2-5


34/337

Table 2-1 Common networking schemes

Networking Scheme

Networking Requirement ConfigurationExample

Eth-trunk active/standbymode andstatic routingmode

l The Eth-trunk active/standby mode can improve reliability.When a member link is faulty, the traffic is automaticallyswitched to an available link.

l This scheme simplifies the configurations when thePDSN9660 interworks with multiple BSCs/PCFs.

l This scheme features easy management. If the IP addressesor the planning of the BSCs/PCFs are changed, noconfiguration change is required on the PDSN9660.

For details,see 2.10ConfigurationExample .

2.3 Configuring the Physical InterfaceThis describes how to configure a physical interface to establish the physical path between thePDSN9660 and the network entity.

PrerequisiteThe network environment between the PDSN9660 and the network entity is established.

ContextSingle physical interface is a simple method to set up a physical path.

Configuration Principlel The configuration steps are not transposable. You must follow the order strictly.l To bind an interface to a Virtual private network (VPN), you must associate the interface

with the specific VPN instance in the interface view and then set the IP address for theinterface.

Data Planning

No. Data

1 Name of the physical interface that is connected to the networking entities2 (Optional) VPNs to which the interfaces are bound

3 IP addresses and subnet masks of the physical interfaces

Procedure

Step 1 Run interface to enter the interface view.

Step 2 Optional: Run ip binding vpn-instance to bind the interface to the specific VPN instance.

Step 3 Run ip address to set the IP address of the physical interface.

----End


System Integration


Issue 02 (2009-04-10)


35/337

2.4 Configuring the Eth-trunk InterfaceThis describes how to configure the Eth-trunk interface. To enhance networking reliability,configure the Eth-trunk interface to establish path between the PDSN9660 and the network entity, and enable the Address Resolution Protocol (ARP) probe function.

PrerequisiteThe network environment between the PDSN9660 and the network entity is established.

Context

An Eth-trunk interface can work in either active/standby mode or load-sharing mode.

l Active/standby mode: It can enhance reliability. When a member link is Down, the trafficis automatically switched to another available link.

l Load-sharing mode: It can improve bandwidth usage and enhance reliability. The bandwidth of the Eth-trunk interface is the total bandwidth of all physical interfaces. If a physical interface is Down, other member interfaces are still available for data transmission.

The working mode of active and standby Eth-trunk interfaces that each operate in load-sharing mode can further enhance reliability and ensure connectivity of the physical path.You can configure the cost value for running Open Shortest Path First (OSPF) on aninterface to specify whether the interface is active or standby. The interface with a larger cost value serves as the standby interface.

Configuration Principlel The configuration steps are not transposable. You must follow the order strictly.

l To bind an interface to a VPN, you must associate the interface with the specific VPNinstance in the interface view and then set the IP address for the interface.

Data Planning

Data planning for configuring the Eth-trunk interface

No. Data

1 Physical interfaces that are bound to an Eth-trunk logical interface2 Operating modes of the Eth-trunk logical interfaces

3 (Optional) VPNs to which the interfaces are bound

4 IP addresses of the Eth-trunk logical interfaces

Procedure

Step 1 Run interface eth-trunk to create an Eth-trunk interface.

Step 2 Run workmode to set the operating mode of the Eth-trunk trunk to active/standby or load-sharing.



2-7


36/337

Step 3 Optional: Run ip binding vpn-instance to bind the interface to the specific VPN instance.

Step 4 Run ip address to set the IP address of the Eth-trunk interface.

Step 5 Run quit to return to the system view.

Step 6 Run interface to enter the physical interface view.

Step 7 Run eth-trunk to bind the physical interface to the specific Eth-trunk interface.

----End

2.5 Configuring the R-P InterfaceThis describes how to create the logical communication path between the packet control function(PCF) and the PDSN9660.

Prerequisitel The network environment between the PDSN9660 and the PCF is established.

l The physical interface is configured and commissioned. For details, see 2.3 Configuringthe Physical Interface .

Data Planning

No. Data

1 Name of the R-P interface that is used to interwork with the PCF

2 IP address of the interface

Procedure

Step 1 Run interface to enter the interface view and create the R-P interface.NOTE

l The created interface must be the planned R-P interface. The interface name consists of the interfacetype rpif and the interface number. The interface number is in the format of SPU group number /virtual interface card number /virtual port number .

l The R-P inte rface is created on the SPU and can be configured only when the SPU runs normally andno user exists on the SPU. You cannot configure the R-P interface if the SPU is not started or wh en itis starting.

Step 2 Run ip address to set the IP address of the R-P interface.NOTE

When you set the IP address of theR-P interface, the subnet mask must be set to 255.255.255.255.

----End

2.6 Configuring the Static Route to the PCF

This describes how to configure the static route to realize the interworking between thePDSN9660 and the packet control function (PCF) at the network layer.


System Integration


Issue 02 (2009-04-10)


37/337

Prerequisitel The network environment between the PDSN9660 and the PCF is established.

l The physical interface is configured. For details, see 2.3 Configuring the Physical

Interface .l The R-P interface is configured. For details, see 2.5 Configuring the R-P Interface .

Configuration Principle

You can configure only the static route between the PDSN9660 and the PCF.

Data Planning

No. Data

1 IP address and subnet mask of the R-P interface (signaling plane on the PCF)2 IP address of the next hop router or firewall to the PCF

Procedure

Run ip route-static to configure a static route.

NOTE

The destination address of the static route is an IP address of the network segment to which the R-P interface(signaling plane of the PCF) belongs. The next hop address is the IP address of the router or the firewallto which the PDSN9660 connects.

CAUTION

On the next hop router or firewall, you must configure the static route to the PDSN9660. Thedestination address of the static route is the IP address of the R-P interface on the PDSN9660,and the next hop address is the IP address of the physical interface on the PDSN9660 used for interworking with the PCF, or the next hop address can be the IP address of the Eth-trunk interface when reliability networking is adopted.

----End

2.7 Setting the SPI ParametersThis describes how to set the security parameter index (SPI). The SPI is an extended option inan A11 message. It provides security parameters, such as the authentication mode and key, for reliable transmission of the A11 message.

Prerequisite

The R-P interface is configured. For details, see 2.5 Configuring the R-P Interface .



2-9


38/337

CAUTION

On the packet control function (PCF), you must set the same SPI value, authentication mode,

and key as those on the PDSN9660. Otherwise, the A10 connection between the PDSN9660 andthe PCF cannot be established.

Data Planning

No. Data

1 IP address of the R-P interface on the PCF, and that of the R-P interface onthe PDSN9660

2 SPI value, authentication algorithm, authentication mode, and key betweenthe PDSN9660 and the PCF

3 Anti-replay mode between the PDSN9660 and the PCF

Procedure

Step 1 Run access-view to enter the access view.

Step 2 Run pcf to set the SPI parameters, such as the IP address of the signaling plane on the PCF, IPaddress of the R-P interface on the PDSN9660, SPI value, authentication algorithm,authentication mode, key, and anti-replay mode.

NOTE

Anti-replay is to prevent any user from repeatedly sending a data packet. The receiver rejects an old or aduplicate packet.

----End

2.8 Configuring the A11 TimerThis describes how to configure the A11 timer and the Point-to-Point Protocol (PPP) timer.

Context

An A10 connection between the PDSN9660 and the packet control function (PCF) is set up,refreshed or released through A11 messages.

l When a mobile station (MS) initiates a packet data session, the base station controller (BSC)coordinates the air channel. After the radio access network (RAN) is set up, the PCF sendsan A11 registration request to the PDSN9660 for establishing an A10 connection.

l If the PDSN9660 accepts the A11 registration request, the PDSN9660 returns an A11registration reply containing the accept indication to inform the PCF that the A10connection is established.

l The establishment of the A10 connection indicates that the data path for the user is set up.

Then, the PPP negotiation between the MS and the PDSN9660 can be started through this path.


System Integration


Issue 02 (2009-04-10)


39/337

The user data over the path is encapsulated by using the Generic Routing Encapsulation (GRE) protocol. For details about GRE, see RFC1701.

Data Planning

No. Data

1 Number of retransmission times of registration update messages

2 Timeout interval of the dormant timer

3 Timeout interval of the registration update timer

4 Interval for the registration lifetime timer of the A10 connection

Procedure

Step 1 Run access-view to enter the access view.

Step 2 Run a11timer to configure the A11 timer, that is, set the number of retransmission times of registration update messages, timeout interval of the dormant timer, timeout interval of theregistration update timer, and interval for the registration lifetime timer of the A10 connection.

----End

2.9 Commissioning the Data for the Interworking with thePCF

This provides the commands for commissioning the configuration data for the interworking withthe packet control function (PCF).

Context

When the preceding configuration is complete, you can run the following commands to check the running status or configuration result.

Table 2-2 Displaying the data for the interworking between the PDSN and the PCF

Command Functiondisplay current-configuration Displays the current configuration of the

interface.

display ip interface Displays the running status of the interface.

display ip routing-table Displays the abstract information about therouting table and information about the routewith a specified destination IP address.

display pcf Displays the security parameter index (SPI) parameters and PCF-related information.

system integration-(v900r007c02 02)

Documents