Gateway GPRS Support Node (GGSN) - 4.

0 AC-A09

10/01/10 11:37

OPERATION DIRECTIONS

2/1543-AXB 250 02 Uae X

Gi Interface Configuration
Copyright © Ericsson AB 2003, 2004 - All Rights Reserved Disclaimer The contents of this document are subject to revision without notice due to continued progress in methodology, design, and manufacturing. Ericsson shall have no liability for any errors or damage of any kind resulting from the use of this document.

Contents
1 1.1 1.2 1.3 2 2.1 2.2 2.3 3 4 4.1 4.2 4.3 4.4 5 5.1 5.2 6 6.1 6.2 7 7.1 7.2 7.3 7.4 7.5 7.6 7.7 8 9 Introduction Purpose Scope Applicability Prerequisites Planning User Equipment Flowchart L1, L2 and IP Layer Configuration Hardware Configuration IPsec, GRE and Packet Filters Configuration Internal Routing Configuration External Routing Configuration Access and Authentication Configuration APN Configuration Outband RADIUS Configuration Additional Configuration Deleting a Gi Interface partly or completely Modifying a Gi Interface partly or completely Example Hardware Configuration Example IPsec/GRE and Packet Filters Configuration Example Internal Routing Configuration Example External Routing Configuration Example APN Configuration Example Outband RADIUS Configuration Example DHCP Configuration Example Related Documents Reference List

http://digimqalex01.fwi.digicelgroup.local:80/alexserv?id=31493

Page 1 of 33

Gateway GPRS Support Node (GGSN) - 4.0 AC-A09

10/01/10 11:37

1 Introduction
1.1 Purpose
This document describes how to configure the Gi interface on the Gateway GPRS Support Node (GGSN) or the Combined GPRS Support Node (CGSN). It is mainly written for personnel performing first-time configuration of the GGSN. It covers GGSN 4.0 and CGSN G 3.0. CGSN G 3.0 consists of the SGSN and the GGSN software applications running in the same physical node. Throughout this document, when read from a CGSN point of view, SGSN/GGSN should be read as "the SGSN/GGSN part of the CGSN". If the CGSN differs from the SGSN/GGSN this will be stated.

1.2 Scope
This document covers the following issues: Prerequisites to be able to start the configuration Flowchart describing the order in which the interface should be configured Configuration procedures for Layer 1 (L1), Layer 2 (L2) and the Internet Protocol (IP) layer Configuration procedures for access and authorization Additional configuration procedures for deletion or modification of the Gi interface partly or completely Configuration examples The configuration of the Gi interface is transacted through Command Line Interface (CLI) commands or by using the Packet Exchange Manager (PXM). For operating instructions of the PXM and more information on the CLI commands used during the configuration, see the reference chapter. The Operation & Maintenance (O&M) environment, including PXM and CLI, is further described in Reference [60]. All descriptions in this document work under the assumption that the configuration is done as if no previous communication links to the Packet Data Network (PDN) exist. Only some recommendations regarding the configuration parameters are given in this document, since they can not be known in advance without a particular PDN at hand. For a description of the Gi interfaces refer to Reference [50].

1.3 Applicability
This document is intended to personnel performing first-time configuration of the GGSN. It is assumed that the installation of the GGSN has already been implemented by the site installation personnel.

2 Prerequisites
This chapter outlines the prerequisites, as they depend on the General Packet Radio Service (GPRS) backbone network and specific setup. Note: To be able to start the configuration on the basis of this document the GGSN must be completely installed by the site installation personnel.

No previous communication links may exist.

http://digimqalex01.fwi.digicelgroup.local:80/alexserv?id=31493

Page 2 of 33

Gateway GPRS Support Node (GGSN) - 4.0 AC-A09

10/01/10 11:37

2.1 Planning
The configuration requires planning, especially of the various communication protocol details. The planning phase should give information on the following topics: How to connect the PDN physically How to prepare the GPRS backbone network How to obtain the Internet Protocol (IP) addresses supposed to be used by the Mobile Stations (MS) Which mechanism to use when assigning an IP address to an MS All the low-level communication parameters used by the link to the PDN, depending on the chosen technology The usage of IP Routing or Access Point Name (APN) Routing The usage of packet filters and Internet Protocol Security (IPsec) or Generic Routing Encapsulation (GRE) The access configuration and APN parameters, as well as information on Remote Authentication Dial-In User Service (RADIUS) and Dynamic Host Configuration Protocol (DHCP) servers The GPRS backbone network configuration and related parameters The necessary GGSN specific planning parameters, which are listed in Reference [61] for a GGSN or Reference [62] for a CGSN Note: The details of the communication parameters configured on the various protocol levels depend on the PDN connected to the GGSN.

2.2 User
The person performing configuration and planning should have a solid knowledge and training in: The area of Transmission Control Protocol/Internet Protocol (TCP/IP) and the various Layer (L1) and Layer 2 (L2) technologies supported by the GGSN, for example Asynchronous Transfer Mode (ATM), routing protocols and router configuration. The function of the Global System for Mobile communication (GSM) and Wideband Code Division Multiple Access (WCDMA) Systems in general. For descriptions of the systems, see Reference [82] for the WCDMA System and Reference [52] for GSM. The function of the O&M system. Refer to Reference [60] for further information. Operation of the GGSN How to work in PXM How to work in UNIX

2.3 Equipment
To execute the configuration of the Gi interface the following equipment is needed: A GSN equipped with GGSN functions Any of these Work Station setups: A UNIX Work Station connected, through the O&M network, to the SGSN and GGSN A UNIX Work Station connected to a terminal server, which is directly plugged into the General Processing Board (GPB) serving as the active Node Controller Board (NCB)

3 Flowchart
On a general level, configuring the Gi interface is broken down into separate, partly independent, tasks:

http://digimqalex01.fwi.digicelgroup.local:80/alexserv?id=31493

Page 3 of 33

fwi. http://digimqalex01.digicelgroup.Gateway GPRS Support Node (GGSN) . see Figure 1.local:80/alexserv?id=31493 Page 4 of 33 . L2 and IP layer configuration Access and authentication configuration These steps are broken down into smaller processes described in the workflow.4.0 AC-A09 10/01/10 11:37 L1.

the hardware is configured. 4. Instructions Use the Ethernet PXM form or the CLI command connect_eth_ip to implement the following steps: 1. Also. This IP address maps to the ATM address of the peer. One or several Permanent Virtual Circuits (PVC) (made up of a Virtual Path Identifier [VPI] and a Virtual Circuit Identifier [VCI]) are then created on each ATM port and a TCP/IP stack address is configured and attached to each PVC. Note: Various other Ethernet parameters can also be configured. in order to clarify all the steps. GRE and routing. Specify the IP address and the subnet mask to configure the TCP/IP stack. Enable IP routing by setting the value of the attribute vanilla to true. the Gom interface must be configured in advance.2 ATM Plug-in Unit Configuration When setting up ATM for the Gi interface.fwi. each plug-in unit that is going to run ATM must be started.0 AC-A09 10/01/10 11:37 Figure 1 Gi Interface Configuration Workflow 4 L1. 3. either Ethernet or ATM can be used. the peer in the PDN has been associated with an IP address.Gateway GPRS Support Node (GGSN) . L2 and IP Layer Configuration This section describes how L1 and L2 are configured to create carrier for an IP layer.digicelgroup. Note: Auto negotiate is not supported and cannot be used by any equipment connected to the Ethernet link of the GSN.1. The hardware configuration must be executed on every Gi plug-in unit. 4. IPsec. The configuration is exemplified in Section 7.1.1 Hardware Configuration The configuration procedure depends on the hardware. followed by packet filtering. but it is recommended to use the default values for most parameters since they effect the internal performance of the hardware.local:80/alexserv?id=31493 Page 5 of 33 . Specify the link speed and the desired duplex mode for the Ethernet plug-in unit. The configuration can be implemented through using either CLI commands or PXM. Note: To be able to use the PXM form when configuring the Gi interface. First. All equipment connected to the Ethernet link of the GSN must be explicity configured to use the same speed and duplex settings as configured for the GSN. 4.4. initially.1 Ethernet Plug-in Unit Configuration Configure the external IP addresses on the Ethernet GiR plug-in units. http://digimqalex01. 2.

Specify the ATM address to the Network Service Access Point (NSAP) Destination. Note: The inbound and outbound packet filters are independent.2 IPsec. Instructions 1. The most likely case is to define a PVC for transmission and reception (Direction = RX/TX). Use the IP Setup tab in the ATM Management PXM form or the CLI command connect_atm_vc_ip. 2. should be chosen as end point for the IPsec tunnel instead of one of the GiR plug-in units. Permit and deny filters are directly defined.local:80/alexserv?id=31493 Page 6 of 33 . permitted or handled with Internet Protocol Security (IPsec) or Generic Routing Encapsulation (GRE) security policy. If authentication with or without encryption is required. 4. an IPsec connection is set up. GRE filter requires to have defined a Security Association (SA) or GRE tunnel in advance. Specify the IP address of the local and remote gateway 3. Specify the mode of the SA (tunnel or transport mode) http://digimqalex01. enable IP routing and state the selector. Then attach the TCP/IP stack to the PVC. GRE and Packet Filters Configuration Filtering on all logical external IP interfaces should be configured in order to permit inbound and outbound traffic. Specify the name and direction of the SA 2. hence both filters must be configured. Instructions Use the IPSec Management PXM form or the CLI command create_ipsec_sa to define an SA.0 AC-A09 10/01/10 11:37 The ATM PVCs can be configured for either IP or APN routed APNs.Gateway GPRS Support Node (GGSN) . while an IPsec.fwi. To achieve redundancy a virtual IP address. 3. hence one SA for outgoing and one for incoming traffic is necessary.digicelgroup. GRE is a lighter protocol and offers neither authentication nor encryption. the switch prefix number and the end system identifier. Specify the IP address. 4. This can only be done by first stopping the ATM driver. Normally also the Service Category is specified. destination IP address and a subnet mask of the TCP/IP interface. Note: It might be necessary to increase this value if all defined instances are already in use.4. the number of VPIs and VCIs. Use the Virtual Circuits tab in the ATM Management PXM form or the CLI command create_atm_vc to define a PVC. Define a PVC. Use the ATM Driver tab in the ATM Management PXM form or the CLI command start_atm to define the maximum number of IP instances. entering the new parameter values and then starting the driver again. The IPsec SAs are unidirectional. unless there is any reason to support only one direction. Complete the base ATM routing. IP packets can be either denied. Use the ATM Driver tab in the ATM Management PXM form or the CLI commands stop_atm and start_atm. implement the steps below: 1.1 IPsec Security Association To be able to run IPsec the SAs must be configured.2. not bound to a certain interface in the GGSN.

should be chosen as end point for the GRE tunnel instead of one of the GiR plug-in units.2. For inbound filters it is recommended to configure rules which only allow inbound packets with a correct destination IP address to enter the GGSN. To achieve redundancy a virtual IP address.digicelgroup. The range of IP addresses. it is recommended is to configure rules which only allow outbound packets with a correct source IP address to leave the GGSN. not bound to a certain interface in the GGSN. thus.0 AC-A09 10/01/10 11:37 4.local:80/alexserv?id=31493 Page 7 of 33 . implement the steps below: 1. A general recommendation for both inbound and outbound filters is to configure the allowed traffic to pass the filter and configure everything else to be discarded. Create a set of packet filter policies.4.1.4. two SAs in each end-point are needed. a single GRE tunnel is used for both incoming and outgoing traffic (compared to the unidirectional IPsec SAs).Gateway GPRS Support Node (GGSN) .2. the routing configuration to the PDN and the filter must match the setup defined in the APN (implemented later). Instructions 1. Specify the IP address of the local and remote gateway 3.fwi. Specify the range of IP addresses allowed for inbound and outbound traffic among other parameters. For configuration of filters that are treating packets with IPsec or GRE functions. Instructions Use the IPSec Management PXM form or the CLI command create_gre_tunnel to create a GRE tunnel. Since GRE tunnels are unidirectional just one tunnel is necessary. Specify the name of the tunnel 2.2 GRE Tunnels GRE tunneling is similar to IPsec in tunnel mode without encryption or authentication. 4.3 Packet Filtering For outbound filters. Note: In the PXM form the value of the attribute name is already set to the name of the interface and it cannot be modified. so no special provisioning has to be made for this case. Specify the session key 4.2. State the protocol of the SA and the algorithm(s) resulting from the choice of protocol 4. see Section 4. See Section 5. Procedure Specific Prerequisites The following procedure specific prerequisite exists: http://digimqalex01.2. GRE is a bidirectional protocol.4 Filter Rules when Using IPsec or GRE To create a bidirectional IPsec connection. Use the PXM form Packet Filtering or the CLI command create_pf_policy to create a packet filter policy. Note: RADIUS requests will come from one of the IP addresses in the allowed IP address range.

fwi. Set the router identity on each GiR plug-in unit. Note that the Gi and Gn interfaces should be configured on separate plug-in units. Use the Router ID tab in the Routing PXM form or the CLI command set_router_id.4. 4.Gateway GPRS Support Node (GGSN) . Therefore.0 since this area is to be used on the external interface. Note: The internal OSPF area may not be set to 0. Note: The inbound filter rule Perform IPSec/GRE does not have to be configured for every SA or GRE tunnel since the IPSec/GRE processing will automaticly find the correct SA/GRE tunnel when decapsulating. 4. Use the OSPFv2 Area Customization tab in the Routing PXM form or the CLI command custom_ospf_area. Configure virtual links on the GiR plug-in units. The virtual link must be configured cross wise on both GiR plug-in units. Enable the internal OSPF routing on the Internal Gi subnetwork (IGi) by specifying the OSPF area and the attributes retransmission. hello and router intervals. Use the CLI command set_ospf_igi. To create a new policy with the rule Perform IPsec/GRE transformation. it is enough to configure one filter rule per protocol number (it means IPSec AH. Note: The name of the created IPsec or GRE tunnel must be used later to identify the point-topoint connection when the APN is defined. Note: The internal OSPF routing on the IGi subnetwork can not be enabled from PXM. 2. Instructions 1. Use the Packet Filtering PXM form or the CLI command create_pf_policy to bind the SA or GRE tunnel to the IP stack.0 AC-A09 10/01/10 11:37 A filter treating packet with IPsec or GRE functions requires to have defined SAs or a GRE tunnel in advance. 3.digicelgroup. OSPF virtual links must be configured between two GiR plugin units. The router IDs may not collide with other IDs of routers within an autonomous system. specify the IP destination and the name of the SA or GRE tunnel to be associated with the policy.0.local:80/alexserv?id=31493 Page 8 of 33 .4 External Routing Configuration http://digimqalex01. Instructions 1. since the Gn interface requires configuration of both the internal routing and the Operation & Maintenance Virtual IP (O&M VIP) address. To achieve full redundancy at link failure.3 Internal Routing Configuration Open Shortest Path First (OSPF) is the recommended routing protocol for routing internally within the GGSN. IPSec ESP and GRE).0.

source and filter operands.1 Static Routes Static routes are used when the setup is not changing. http://digimqalex01. Instructions To configure the OSPF use the OSPFv2 tab in the Routing PXM form or the CLI command set_ospf_if to implement the steps below: 1. 4. 2. Use the Static Routes tab in the Routing PXM form. Within this Autonomous System the GGSN advertises that it knows a route to the hosts from the APN address range. Use the Export tab in the Routing PXM form. Alternatively use the CLI command set_rip.local:80/alexserv?id=31493 Page 9 of 33 . hence it is used within an autonomous system.4.2 OSPF .3 RIP . in order to create an area border to the IGi subnetwork.4.digicelgroup. To configure RIP use the RIP II tab in the Routing PXM form. 3.Routing Within an Autonomous System The usage of RIP as routing protocol should be avoided since it is just suitable for smaller networks and it has some significant technical drawbacks.0. Specify the OSPF area ID and the router priority. If OSPF is used internally and externally.0. In other words.Routing Within an Autonomous System Usage of OSPF means that the GGSN and the PDN form one Autonomous System. To export the routing information to the GiA plug-in units configure the required destination. Note: The backbone OSPF area should always be set to 0. Specify the type and IP address of the interface. Instructions 1. Alternatively use the CLI command set_static_route. If OSPF is being used internally but not externally the routing information must be exported to the OSPF database. Alternatively use the CLI command set_route_export. 2.4.0 AC-A09 10/01/10 11:37 There are several options on how to configure the GiR plug-in units externally.4. Set the attributes retransmission. 4. hello and router dead interval as well as the cost of the interface. To configure a static route specify the destination IP address. netmask and the gateway IP address. Either static routes or a routing protocol like OSPF. 4.0.Gateway GPRS Support Node (GGSN) . Instructions 1. Routing Information Protocol (RIP) or Border Gateway Protocol (BGP) can be used.fwi. the information on the GiR plug-in units must be propagated to the GiA plug-in units. exportation rules do not have to be configured. RIP is an Interior Gateway Protocol (IGP). Routing protocols provides more flexibility.

fwi. 5 Access and Authentication Configuration The access is set up in the Access Point Name (APN). Due to this. The access and authentication configuration is implemented in the following order: 1.Gateway GPRS Support Node (GGSN) . Alternatively use the CLI command set_route_export. the remote AS number and the type of session (EBGP). which exchanges network reachability information with other EBGP systems. This is done in the APN PXM form or by using the CLI command create_apn. which is called RADIUS External Protocol IP Address in the APN PXM form. it may not offer an IP address that is equal to any of the addresses used for sending messages or making requests. Alternatively use the CLI command set_route_export. The APN setup also includes authentication of user. Use the BGP-4 tab in the Routing PXM form or the CLI command set_bgp_peer. EBGP is an inter-Autonomous System routing protocol. To export the routing information to the GiA plug-in units configure the required destination. is one out of the range of the allowed RADIUS addresses. a Dynamic Host Configuration Protocol (DHCP) server or by an inband or outband RADIUS server. 2. The APN configuration requires an IP address to be used by the GGSN when making requests. EBGP is of concern to the Gi interface.4. 3. the RADIUS APN must be configured first. Instructions 1. This IP address. The MS IP address can either be statically provided or provided by the GGSN. Use the Export tab in the Routing PXM form. http://digimqalex01. 4. To export the routing information to the GiA plug-in units configure the required destination. To configure BGP specify the IP address of the BGP peer.4 BGP . 2. the peers can learn about the MSs and know where to direct traffic. Configure the APN and the connection to the RADIUS or DHCP server if either of these are going to be used. it must be configured to have an IP address lease time that is at least 60 seconds. When outband RADIUS is used for authentication. This is done in the RADIUS APN PXM form or by using the CLI command create_rapn. Note: If a DHCP server is used for IP address allocation.4. the route exportation rules should ensure that the range of IP addresses used later when configuring the APN. When configuring the BGP routing of the interface.Routing Between Autonomous Systems The BGP configuration distinguishes between Internal BGP (IBGP) and External BGP (EBGP).digicelgroup. To configure the Autonomous System number on a router plug-in unit use the AS tab in the Routing PXM form or the CLI command set_router_as. for example RADIUS requests to the PDN. Use the Export tab in the Routing PXM form. source and filter operands. is exported to the peer system. For an EBGP session the number of the remote Autonomous System (AS) must be configured prior to enabling BGP. Note: If a DHCP or RADIUS server is used for IP address allocation.local:80/alexserv?id=31493 Page 10 of 33 .0 AC-A09 10/01/10 11:37 2. source and filter operands.

1. This is the netmask for the network corresponding to the first and last supported IP Segments. 7. The APN is configured to contain an IP address range.0 AC-A09 10/01/10 11:37 5. Configure the value of the time-out and retry attributes for messages to the primary RADIUS http://digimqalex01. Specify the IP address to be used by the GGSN when making Internet Control Message Protocol (ICMP) and IP Control Protocol (IPCP) messages.digicelgroup. 3. the GGSN IP Address.fwi.1 step 28 is optional. 6. The configuration performed in 5. Note: For APNs containing an IP address range with more than 30 KB IP addresses it is recommended that the IP address range is configured as several ranges. Instructions The operands used in the instructions below are specified in either the APN PXM form or by using the CLI command create_apn. 4. Note: To continue without the use of inband RADIUS continue at 5. Specify the RADIUS External Protocol IP Address. Specify the name of the APN by entering a domain name. follow the instructions according to Section 5. Enter IP address mask. Specify performed authentication. 2. The RADIUS APN must be configured before the APN configuration if outband RADIUS is going to be used. To use an inband RADIUS server to authenticate the MS. L2 and IP layer configuration must be completed. inband RADIUS or no authentication. Enter or choose the APNs to use for User Name Based Selection.1 step 5.local:80/alexserv?id=31493 Page 11 of 33 . Specify the start of supported IP addresses to be covered by the PDN. The same could also be done for APNs with smaller IP address ranges. which covers the IP addresses as controlled by the PDN. 8. 11.4. Procedure Specific Prerequisites The following procedure specific prerequisites exist: The L1.1 step 7 is mandatory while 5. 5. 9. Note: To continue without User Name Based Selection go directly to 5. to achieve a better internal redundancy in GGSN.1 step 16. Enter a default APN for User Name Based Selection. 10. The GGSN needs to know the IP address of the RADIUS server in the PDN to access the RADIUS server.2.Gateway GPRS Support Node (GGSN) . specify the Primary RADIUS Server Address. This is done to improve the internal loadsharing and redundancy in GGSN. Specify whether User Name Based Selection is going to be used.1 step 8 to 5.1 step 1 to 5.1 APN Configuration Note: If outband RADIUS is going to be used.

no limit on the number of PDP contexts will exist. 19. If LLF is chosen.digicelgroup. 29. Enter Static. Note: To continue without the use of DHCP continue at 5. Specify whether to use a single.1 step 10 to 5. Enter values for rating vectors and use the checkbox to enable or disable RTC Active. If DHCP is used together with inband RADIUS authentication the External Protocol IP Address equals the RADIUS External Protocol IP Address. 22. Real. and also specify the External Protocol IP Address. Indicate in which RADIUS message type to include any of the attributes Full IMSI. 13. Note: The Packet Inspection and Service Classification feature is license dependent. and SGSN IP Address.Gateway GPRS Support Node (GGSN) . GGSN. Select one of the following options: No. however. 25. Specify a shared encryption key for the primary RADIUS server. Filter Associations and Perform Imsi Analysis if the optional feature Packet Inspection and Service Classification is enabled. For both RADIUS Access-Request and RADIUS Accounting-Request. http://digimqalex01. URI Filters. To be able to enter secondary DNS server IP address. limits the number of simultaneous RADIUS dialogs to 256. Enter IP or Link Layer Forwarding (LLF). If the parameter is not defined. If ingress filter is applied on all packets sent from the MS.4. 17. or RADIUS. MCC +MNC. This option. first choose primary DNS server IP address. specify it according to 5. select what tunnel or ATM PVC to connect the APN to. Note: The RTC feature is license dependent.local:80/alexserv?id=31493 Page 12 of 33 . Specify from where the MS is going to get its IP address. 27. 14. This is necessary. 15. enter a valid value in the box MSISDN for the appropriate RADIUS message. if the primary RADIUS server identifies a RADIUS dialog by only the identifier and not by both identifier and source port. This shared secret is compared to a password allowing the GGSN to access the primary RADIUS server.1 step 19. enable ingress filter. Enter secondary DNS server IP address.fwi. 12.1 step 13. Enter primary Domain Name System (DNS) server IP address. WAP Signaling Filters. Selection Mode.0 AC-A09 10/01/10 11:37 server. Note: The routing method must be the same as the one chosen during link configuration. 20. constant Source Port for communication with the primary RADIUS server. Enter the DHCP server IP address. Indicate if RADIUS is going to be used for accounting and if it is going to be used for authentication. Specify one or several ways. If a second RADIUS server is going to be used. Specify the routing method. Dummy. If Dummy is selected. 28. Specify the maximum number of allowed Packet Data Protocol (PDP) contexts for this APN. 26. Charging Id. 24. DHCP. 18. The filter will drop packets where IP spoofing is detected. GGSN GTP IP Address. The shared secret is used for both accounting and authentication. Specify how the MS is allowed to connect to an APN. 21. 23. Specify name and metric of the tunnel or ATM PVC. Enter IP Filters. specify which type of Mobile Station Integrated Services Digital Network Number (MSISDN) shall be included in the message. Specify the default service class to be used. 16.

2 step 4 and 5.2 step 31 are optional. Note: To continue without User Name Based Selection continue at 5. If a second RADIUS server is going to be used.2 step 8 to 5. Specify the routing method. MCC +MNC. Select one of the following options: No. 11. Specify the name of the RADIUS APN by entering a domain name. Dummy.2 step 1 to 5.2 Outband RADIUS Configuration Implement the configuration below if outband RADIUS is going to be used. Instructions The operands used in the instructions below are specified in either the RADIUS APN PXM form or by using the CLI command create_rapn. 14. Specify the IP address to be used by the GGSN when making ICMP and IPCP messages. 13. 2. The APN is configured to contain an IP address range. When the configuration of the RADIUS APN is implemented continue with the APN configuration. 5.0 AC-A09 10/01/10 11:37 5. 17. Specify the start of supported IP addresses to be covered by the PDN. This is the netmask for the network corresponding to the first and last supported IP Segments.2 step 14 are mandatory while 5. Specify the Primary Server Address of the RADIUS Server to be used to authenticate the MS.Gateway GPRS Support Node (GGSN) . The GGSN needs to know the IP address of the RADIUS server in the PDN to access the RADIUS server. 1. The operands used in the instructions below are specified in either the APN PXM form or by using the CLI command create_apn. Enter or choose the APNs to use for User Name Based Selection 12. This shared secret is used for both accounting and authentication.2 step 7 and 5. Enter IP address mask. select what tunnel or ATM PVC to connect the APN to. specify which type of Mobile Station Integrated Services Digital Network Number (MSISDN) shall be included in the message. Specify the RADIUS External Protocol IP Address. 18.2 step 12. which covers the IP addresses as controlled by the PDN.local:80/alexserv?id=31493 Page 13 of 33 . 10. 7. Real. If LLF is chosen. Specify a shared encryption key for the primary RADIUS server.digicelgroup. Also specify whether to use a single source port.2 step 5 to 5. For both RADIUS Access-Request and RADIUS Accounting-Request. If Dummy is selected. Specify the name of the APN. enter a valid value in the box MSISDN for the appropriate RADIUS message. The configurations performed in 5. 6. 3. Procedure Specific Prerequisites The following procedure specific prerequisite exists: The L1. Configure the value of the time-out and retry attributes for RADIUS access. the GGSN IP Address.2 step 15 to 5. http://digimqalex01.4. Enter IP or LLF. Specify name and metric of the tunnel or ATM PVC.fwi.2 step 3 to 5. Specify whether User Name Based Selection is going to be used. Specify RADIUS APN name by entering a domain name. Indicate in which RADIUS message types to include any of the attributes Full IMSI. 15. 16.2 step 4. 4. L2 and IP layer configuration must be completed. 8. configure its parameters according to 5. 9. Enter a default APN for User Name Based Selection. Specify Outband RADIUS authentication as the performed authentication.

Indicate if RADIUS is going to be used for accounting and if it is going to be used for authentication. 28. DHCP or RADIUS. If LLF is chosen. Enter Static. Note: The Packet Inspection and Service Classification feature is license dependent.4.fwi. 21. 26. If the parameter is not defined. 22. WAP Signaling Filters. 6 Additional Configuration This section describes how to delete and modify either the complete Gi interface or selected parts of it.local:80/alexserv?id=31493 Page 14 of 33 . a few APNs. for example. and SGSN IP Address.1 Deleting a Gi Interface partly or completely Deleting a Gi interface is equivalent to removing a PDN from a GGSN and therefore from the GPRS backbone network. 19. URI Filters. Note: The RTC feature is license dependent. Charging Id. 30. 27.Gateway GPRS Support Node (GGSN) .digicelgroup. To be able to enter secondary DNS server IP address. Specify the routing method. Removing an PDN from a GGSN involves the reverse execution of the key steps described in the procedure of creating a Gi interface. just one RADIUS. Enter IP Filters. The filter will drop packets where IP spoofing is detected. The following steps are for deleting the Gi interface: http://digimqalex01. Specify the External Protocol IP Address. GGSN GTP IP Address. Specify one or several ways. Specify from where the MS is going to get its IP address. Note: The routing method must be the same as the one chosen during link setup. Enter secondary DNS server IP address. Specify name and metric of the tunnel or ATM PVC. enable ingress filter. one packet filter or the like. select what tunnel or ATM PVC to connect the APN to. no limit on the number of PDP contexts will exist. Specify the maximum number of allowed Packet Data Protocol (PDP) contexts for this APN. 24. Specify how the MS is allowed to connect to an APN. 31. If ingress filter is applied on all packets sent from the MS. 29.2 step 22. 6. 32. The Gi interface configuration can also be partly deleted by removing. Enter the DHCP server IP address. Filter Associations and Perform Imsi Analysis if the optional feature Packet Inspection and Service Classification is enabled. Enter values for rating vectors and use the checkbox to enable or disable RTC Active. Enter IP or LLF.0 AC-A09 10/01/10 11:37 Selection Mode. GGSN. first choose primary DNS server IP address. Enter primary DNS server IP address. Specify the default service class to be used. 23. 25. 20. Note: To continue without the use of DHCP continue at 5.

Required Order of Configuration If an APN is using outband RADIUS the deletion must be implemented in the following order: 1. or removal.0 AC-A09 10/01/10 11:37 APN configuration RADIUS configuration Routing configuration IPsec. To delete an APN. RADIUS APN http://digimqalex01. The same applies for a DHCP server. if the APN is deleted. All PDP contexts active in an APN will be removed. If the RADIUS server has provided the subscribers with dynamic IP addresses. Change of a RADIUS server (primary or secondary). 6. they will be automatically released when the APN is deleted. Change of RADIUS External Protocol IP Address and External Protocol IP Address. Change of origin of IP Address. APN 2.4. use the APN PXM form or the CLI command list_apns.fwi. Available Operations The following operations exist to display and remove APNs and RADIUS APNs: To display all the RADIUS APNs that can be deleted. To delete a RADIUS APN. This includes change of IP address. GRE and filtering configuration TCP/IP stack attachment IP layer configuration Link layers configuration Note: Since the rate of PDP context deactivations is limited.1. use the RADIUS APN PXM form or the CLI command delete_rapn. an APN may be out of operation for a long time. before the APN is deleted. Change of routing method (from normal IP to APN or vice versa). if any of the following types of modifications are made to the APN: Change of MS APN IP address range (first IP address or netmask). Procedure Specific Prerequisites The following procedure specific prerequisite exists: The APN entry should be removed from the DNS in the GPRS backbone network. The set of configured LLF links is changed. To display all the APNs that can be deleted. If the APN uses a RADIUS server. GGSN IP address is changed.local:80/alexserv?id=31493 Page 15 of 33 . All subscriber connections to the APN are automatically removed. use the RADIUS APN PXM form or the CLI command list_rapns. All PDP contexts active in an APN will be removed. use the APN PXM form or the CLI command delete_apn.1 Deleting APN and RADIUS Configuration Removing an APN configuration basically means to reverse the definition of the APN in the GGSN. the connection between APN and the RADIUS server is lost when the APN is deleted.Gateway GPRS Support Node (GGSN) . operations on APNs with many active PDP contexts should be handled with due care. the SGSN will send Create PDP Context requests to the GGSN. replacement. addition.digicelgroup. Otherwise. Otherwise.

Procedure Specific Prerequisites The following procedure specific prerequisite exists: RADIUS and APN connections to the selected router plug-in unit must be deleted. To delete the static routes use the Static Routes tab in the Routing PXM form or the CLI commands delete_static_route.fwi. When changing router configurations. the routing configuration is not deleted automatically.digicelgroup. To delete the OSPF protocol internally use the OSPFv2 tab in the Routing PXM form or the CLI command delete_ospf_igi.1. The packet filter policies on an interface must be deleted before the interface itself.0 AC-A09 10/01/10 11:37 6.1. For example the routing protocols have to pick up the routing changes. Available Operations To remove packet filter policies or IPsec or GRE connections the following operations exist: To delete the filter policy or set of policies for a router plug-in unit.3 Deleting IPsec.2 Reverse Routing Configuration When a plug-in unit is detached from its IP stack. http://digimqalex01. SA or GRE tunnel. use the Packet Filtering PXM form or the CLI command delete_pf_policy.4. Note: The internal routing should only be removed if the whole Gi interface is to be deleted. Note: The necessary operations must be implemented on every plug-in unit to be configured. To delete policies for exporting routes use the Routing PXM form and the Exports tab or the CLI commands delete_route_export.local:80/alexserv?id=31493 Page 16 of 33 . use the IPSec Management PXM form or the CLI command delete_ipsec_sa. Both SAs of the bidirectional IPsec connection must be deleted. hence the routing protocols must be removed prior to the physical link. To delete an SA. Available Operations In order to disable the existing routing configuration on a router plug-in unit the following operations exist: To delete the OSPF protocol on an external GiR plug-in unit use the OSPFv2 tab in the Routing PXM form or the CLI command delete_ospf_if. 6. GRE and Packet Filtering Configuration If packet filter policies or IPsec or GRE connections are defined on a Gi plug-in unit they must be removed for security reasons. To delete the BGP routing protocol use the BGP-4 tab in the Routing PXM form or the CLI commands delete_bgp_peer.Gateway GPRS Support Node (GGSN) . To delete the RIP routing protocol use the RIP II tab in the Routing PXM form or the CLI commands delete_rip. The SAs are deleted one by one. it should be taken into account that such changes might take some time to propagate.

Required Order of Configuration To delete IPsec SAs or a GRE tunnel with a corresponding set of packet filter policies. follow the instructions bellow. Available Operations To remove the Ethernet configuration the following operation exist: To disconnect the selected Ethernet driver from the TCP/IP stack the Ethernet PXM form or the CLI command disconnect_eth_ip can be used. Note: The operation must be implemented on every plug-in unit to be configured.4 Deleting Physical Links The deletion process differs depending on whether the plug-in unit is running Ethernet or ATM. follow the instructions bellow. Deleting an ATM Configuration To disconnect an ATM PVC or to deinitialize the ATM plug-in unit from the TCP/IP stack. Procedure Specific Prerequisites The following procedure specific prerequisite exists: On the router plug-in unit where Ethernet is going to be disconnected.Gateway GPRS Support Node (GGSN) . Note: The necessary operations must be implemented on every plug-in unit to be configured. Deleting an Ethernet Configuration To disconnect an Ethernet plug-in unit from the TCP/IP stack.digicelgroup.4. the deletion must be implemented in the following order: 1. the routing and packet filtering configuration must previously be removed.1.fwi.local:80/alexserv?id=31493 Page 17 of 33 . Delete the IPsec SAs or GRE tunnel 6. use the IPSec Management PXM form or the CLI command delete_gre_tunnel. the routing and packet filtering configuration must previously be removed.0 AC-A09 10/01/10 11:37 To delete a GRE tunnel. Available Operations To remove the ATM configuration the following operations exist: http://digimqalex01. Procedure Specific Prerequisites The following procedure specific prerequisite exists: On the router plug-in unit where ATM will be disconnected. Delete the set of packet filters 2. The GRE tunnels are deleted one by one.

partly or completely.1. All PDP contexts active in an APN will be removed. Required Order of Configuration To remove an ATM PVC and stop an ATM plug-in unit the operations must be implemented in the following order: 1. Detach the TCP/IP stack from the ATM PVC 2. performed by implementing 6. To deinitialized an ATM plug-in unit use the ATM Driver tab in the ATM Management PXM form or the CLI command stop_atm. To do this the execution of the key steps described in the procedure of creating a Gi interface are either overwritten or changed. 6. Otherwise.digicelgroup.1. 6. It is possible to delete just one or all of them. Note: The deinitialization of the ATM plug-in unit. use the IP Setup tab in the ATM Management PXM form or the CLI command disconnect_atm_vc_ip.4 step 2 need to be repeated.local:80/alexserv?id=31493 Page 18 of 33 . are disconnected and deleted. should just be executed if all the ATM PVCs. an APN may be out of operation for a long time. The following steps are for modifying the Gi interface: APN configuration RADIUS configuration Routing configuration IPsec. if the APN is deleted. operations on APNs with many active PDP contexts should be handled with due care. Note: The ATM driver for a plug-in unit may be deinitialized if there are no active PVCs for this specific plug-in unit. Stop the ATM driver Note: For every ATM PVC that is going to be deleted.Gateway GPRS Support Node (GGSN) .4 step 3.4 step 1 and 6. To delete the detached ATM PVC use the Virtual Circuits tab in the ATM Management PXM form or the CLI command delete_atm_vc.4.2 Modifying a Gi Interface partly or completely The configuration of the Gi interface can also be modified. GRE and filtering configuration Note: Since the rate of PDP context deactivations is limited.0 AC-A09 10/01/10 11:37 To detach the TCP/IP stack from an ATM PVC.1. Note: The necessary operations must be executed on every plug-in unit to be configured. All PDP contexts active in an APN will be removed. Delete the ATM PVC 3. once connected to the plug-in unit.fwi. if any of the following types of modifications are made to the APN: http://digimqalex01.

GGSN IP address is changed. To display the data for a specific APN by specifying the name of the APN. Available Operations There are no specific CLI commands to change any of the router attributes.fwi. use the APN PXM form or the CLI command set_apn.2. To modify an APN. addition. Change of RADIUS External Protocol IP Address and External Protocol IP Address. use the RADIUS APN PXM form or the CLI command set_rapn.2 Modifying Routing Configuration When changing router configurations. Note: Only attributes which are entered will be changed. 6.local:80/alexserv?id=31493 Page 19 of 33 . An optional number of operands of an existing APN or RADIUS APN can be changed. 6. it should be taken into account that such changes might take some time to propagate. use the APN PXM form or the CLI command get_apn to display the values of the operands.1 Modifying APN and RADIUS Configuration To view the current data it is possible to display the values of the attributes of a specific APN or RADIUS APN. For example. This includes change of IP address. Change of a RADIUS server (primary or secondary). When a CLI command is run again the old configuration is overwritten by the new. The set of configured LLF links is changed.2. Note: If the modifications of the APN and RADIUS APN influence on other parts of the system.3 Modifying Packet Filtering and IPsec/GRE Configuration http://digimqalex01. Attributes which are not entered will keep its previous value. replacement. To modify a RADIUS APN.0 AC-A09 10/01/10 11:37 Change of MS APN IP address range (first IP address or netmask). or removal. The Routing PXM form and the respective tabs can also be utilized to edit the attributes. use the RADIUS APN PXM form or the CLI command get_rapn. Note: If the modifications of the router configuration influence on other parts of the system.Gateway GPRS Support Node (GGSN) . make sure to change the configuration of these parts too. the routing protocols have to pick up the routing changes. make sure to change the configuration of these parts too. Change of routing method (from normal IP to APN or vice versa). Available Operations The following operations exist to display and modify APNs and RADIUS APNs: To display the data for a specific RADIUS APN by specifying the name of the RADIUS APN. The router configuration is instead modified by following the instructions outlined in Section 4.3.digicelgroup.2.4. Change of origin of IP Address. 6.4 and Section 4.

Modifying an ATM Configuration The ATM driver should not be modified. The CLI command is the same as the one used when creating the filter. Since the configuration can be performed in more than one way several examples explain the different http://digimqalex01.digicelgroup. Note: All the attributes must be specified just as when creating the GRE tunnel. Note: All the attributes must be specified just as when creating the SA.Gateway GPRS Support Node (GGSN) .4. The GRE tunnels are deleted one by one. Required Order of Configuration If modifying a filter that is treating packets with IPsec or GRE functions.1. Define the SA or GRE tunnel 2. IPsec SAs or GRE tunnels influence on other parts of the network. new ATM PVCs are created according to Section 4.1. To modify an SA. or set of policies.2.4 Modifying Physical Links The modification process differs depending on whether the plug-in unit is running Ethernet or ATM. the command also changes the filter data for the interface with the name. implement the configuration in the following order: 1. Modifying an Ethernet Configuration The Ethernet plug-in unit attachment to the TCP/IP stack should not be modified in order to have the rest of the system running. use the IPSec Management PXM form or the CLI command set_gre_tunnel. To modify a GRE tunnel. that is to say. use the IPSec Management PXM form or the CLI command set_ipsec_sa.4. Available Operations To modify packet filter policies.local:80/alexserv?id=31493 Page 20 of 33 . IPsec or GRE connections the following operations exist: To change the filter policy. make sure to change the configuration of these parts too.0 AC-A09 10/01/10 11:37 Note: If the modifications of the filter policies. SA or GRE tunnel. 7 Example In this section the configuration procedure is described on the basis of an example set up. traffic direction and equipment specified. use the Packet Filtering PXM form or the CLI command delete_pf_policy. ATM PVCs can be modified by deleting the old configuration according to Section 6.2. for a router plug-in unit.fwi. Attach the SA or GRE tunnel to the IP stack using a packet filter 6. Both SAs of the bidirectional IPsec connection must be modified. The SAs are modified one by one.

Since IPsec and GRE packets are routed as normal IP packets. 7. Caution! Every operator should carefully examine what parameters to configure and what values to give them. The configuration can also be performed by using PXM. Note: When using Ethernet the value of the attribute vanilla should always be set to true.1. The operator must also take into consideration how the hardware is compounded. however not described.0 -speed 100 -duplex 1} The O&M port is configured to function as an Ethernet plug-in unit. either for IP routed APNs or for APN routed APNs.4 -mask 255.0 AC-A09 10/01/10 11:37 configuration situations.2 ATM Example Initially the ATM driver is setup.255. Each GiR plug-in unit can have several PVCs. Example 1 Ethernet Configuration of the GiR External IP Address connect_eth_ip -eq {2 11 2 1} -unit 0 {-name ETH_2_11_0 -vanilla true -ip 172.local:80/alexserv?id=31493 Page 21 of 33 .28. The parameter values in the examples are not in any way recommended values. When using LLF tunnels for the Ethernet case.1 Hardware Configuration Example Either an Ethernet plug-in unit or an ATM plug-in unit can be used as hardware. Example 3 Setting Up a PVC When Using Normal IP Routing create_atm_vc -eq {2 11 2 1} -unit 1 -vpi 1 -vci 100 http://digimqalex01.fwi.1. then the PVCs are created and given an external IP address. This is.130. 7.Gateway GPRS Support Node (GGSN) . The examples covers configuration by using CLI commands.digicelgroup. The examples below cover both cases. Example 2 Starting Up the ATM Driver start_atm -eq {2 11 2 1} -unit 1 -sdh true -range "1:11" -esi "00:00:02:00:02:11" -perm false -switch "10:20:30:40:50:60:70:80:90:a0:b0:c0:d0" -mip 50 -rx 900 -tx 16 This procedure is performed once for each GiR plug-in unit that is using ATM. The configuration must be repeated on each GiR plug-in unit that is running Ethernet. 7.1 Ethernet Example One external IP address per GiR plug-in unit is set. IPsec or GRE are used as external tunnels.255.4. normal IP routing will always be used.

28. see Section 7. Example 4 Setting Up a PVC When Using APN Routing create_atm_vc -eq {2 11 2 1} -unit 1 -vpi 1 -vci 101 -dir 3 -addr "10:20:30:40:50:60:70:80:90:a0:b0:c0:d0: 00:00:02:00:02:11:01" -cat VBR -pcr 155000 -scr 100000 -mbs 20 connect_atm_vc_ip -eq {2 11 2 1} -unit 1 -vpi 1 -vci 101 -name ATM_2_11_1_1_101 -vanilla false -sel 1 -ip 172. the value of the attribute vanilla is set to false. The commands must be repeated for each PVC used for normal IP routing.140.28.28. To achieve redundancy the SAs are automatically created on both GiR plug-in units.1 -mask 255.28.24.10 The configuration above depicts a PVC with an IP interface used for normal IP routing. One SA for the outgoing and one for the incoming IPsec tunnel should be configured.1 IPsec Security Association Example Example 5 Creating Security Associations create_ipsec_sa {-name AhTunnelIn1 -dir 1 -mode 2 -proto 51 -spi 551 -aualg 3 -aukey 0x1111111111111111111111111111111111111111 -lip 172. IPsec or GRE.150.28.132.5.24.2 IPsec/GRE and Packet Filters Configuration Example The examples below depicts how to set both inbound and outbound filter rules in different situations.254 } IPsec tunnels are always configured in pairs. The commands must be repeated for each PVC used for APN routing. The filter rules differ depending on whether using ATM PVCs. In Example 3 and Example 4 the values of the attributes cat.255. The addresses of the SAs on both sides of the tunnel must match to each other and to http://digimqalex01.4.digicelgroup. The ATM PVC and LLF tunnel bindings are established later in the configuration course of events. when creating the APNs. Also.250.1 -lip 172.255.Gateway GPRS Support Node (GGSN) . the sum of SCR should be less than the sum of PCR 7. 7.2. The sum of Peak Cell Rate (PCR) over the PVCs should be less or equal to 155 000.250.2.fwi.28. the value of the attribute vanilla is set to true. The same applies for the sum of Sustainable Cell Rate (SCR) over the PVCs. If IPsec or GRE is going to be used the SAs or GRE tunnel must be created first.2 -mask 255.140.0 -dip 172.150.132.255. scr and mbs are optional and when using them they must be configured in agreement with the number of PVCs used.0 AC-A09 10/01/10 11:37 -dir 3 -addr "10:20:30:40:50:60:70:80:90:a0:b0:c0:d0:00: 00:02:00:02:11:00" -cat VBR -pcr 155000 -scr 100000 -mbs 20 connect_atm_vc_ip -eq {2 11 2 1} -unit 1 -vpi 1 -vci 100 -name ATM_2_11_1_1_100 -vanilla true -sel 0 -ip 172.local:80/alexserv?id=31493 Page 22 of 33 .255.1 } create_ipsec_sa {-name AhTunnelOut1 -dir 2 -mode 2 -proto 51 -spi 501 -aualg 3 -aukey 0x1111111111111111111111111111111111111111 -rip 172.2 The configuration above depicts a PVC with an IP interface used for APN routing. pcr.254 -rip 172.252 -dip 172.

0 {-proto 0.254 -rip 172.2.0. lip (the endpoint of the tunnel) must be chosen according to Section 7.254 127.3 Choosing Gi IPsec/GRE VIP Address Example To achieve redundancy a virtual IP address.0. when creating the APNs.0. Note: To get a functioning redundancy.255 -gip set_static_route -eq {2 12 -mask 255.0.fwi. lip (the endpoint of the tunnel) must be chosen according to Section 7. when creating the APNs.250.255.0.0.28.0 AC-A09 10/01/10 11:37 fulfil the redundancy the local termination IP address.24.0 3 -src -rule 2}}} 3 -src -rule 2}}} 10 2 1} -dst 0.250.255.24.0.24.4 Filter Rules when Using ATM PVCs Example When using ATM PVCs inbound and outbound filters should be set.2. Example 7 Local Termination IP Address set_static_route -eq {2 10 -mask 255. The GRE tunnels will be connected to LLF tunnels. 7.2. Example 8 Inbound Filter for a PVC Directed to IP Routed APNs create_pf_policy -eq { 2 11 2 1 } -name ATM_2_11_1_1_100 -dir 1 {-rule 2 -proto 0 -sip 0.0.255. routing protocols like OSPF need to be used on the external GiR plug-in units.254 127.2.0 -mask Static routes for the virtual IP address are set to a loopback interface on the GiR plug-in units.local:80/alexserv?id=31493 Page 23 of 33 . 7.2 GRE Tunnel Example Example 6 Creating a GRE Tunnel create_gre_tunnel { -name ISPtunnel1 -gskp true -gskey 801 -lip 172. not bound to a certain interface in the GGSN.0.digicelgroup.2.3. see Section 7. The GRE and LLF tunnel bindings are established later in the configuration course of events. To achieve redundancy the GRE tunnels are automatically created on both GiR plug-in units.255 -gip set_route_export -eq {2 {-proto 5 -filter {-ip set_route_export -eq {2 {-proto 5 -filter {-ip 2 1 } {-dip 172. The IPsec tunnels will be connected to LLF tunnels. For more information on the configuration of the attribute lip.Gateway GPRS Support Node (GGSN) .250.0 -smask 0.1} GRE tunnels are bidirectional which means that one GRE tunnel is used for both incoming and outgoing traffic. To fulfil the redundancy the local termination IP address.2. To accomplish this perform the configuration in Example 7.5.0.0.0. see Section 7. 7.1} 2 1 } {-dip 172.255. see Reference [50].0 -dip http://digimqalex01.0.5.0.2.4.0. The IPsec and LLF tunnel bindings are established later in the configuration course of events.0.1} {-proto 0.0 -mask 12 2 1} -dst 0. should be chosen as end point for the IPsec/GRE tunnel instead of one of the GiR plug-in units. These static routes are then exported so that external routers receive routing information about the virtual IP address.3.132.

0 -dmask 0.Gateway GPRS Support Node (GGSN) .0. Note: The SAs must be configured prior to the filter settings.0 -smask 0.0.0 -dip 0.0 -ipnext 0 -ipnextq 3 -ipopt false -log false } Example 9 Outbound Filter for a PVC Directed to IP Routed APNs create_pf_policy -eq { 2 11 2 1 } -name ATM_2_11_1_1_100 -dir 2 {-rule 2 -proto 0 -sip 0.0 -smask 0.0 -ipnext 0 -ipnextq 3 -ipopt false -log false } Example 11 Outbound Filter for a PVC Directed to APN Routed APNs create_pf_policy -eq { 2 11 2 1 } -name ATM_2_11_1_1_101 -dir 2 {-rule 2 -proto 0 -sip 0.fwi. the other rule allow all incoming packets to enter the GGSN.0 -smask 0.0.0.0. This must be done by repeating the commands.0.0.0.0.0. 7.0.0 -dmask 0.0.0. Example 10 Inbound Filter for a PVC Directed to APN Routed APNs create_pf_policy -eq { 2 11 2 1 } -name ATM_2_11_1_1_101 -dir 1 {-rule 2 -proto 0 -sip 0.0. Note: The inbound filter rule Perform IPSec/GRE does not have to be configured for every SA or GRE tunnel since the IPSec/GRE processing will automaticly find the correct SA/GRE tunnel when decapsulating.0.0.0.0 -dip 0.5 Filter Rules when Using IPsec Example When using IPsec there are three filters to configure.0 AC-A09 10/01/10 11:37 0.0.0.0.0.0 -dip 0.0.0.0.0 -smask 0.0 -smask 0.0 -dmask 0.0.0 -dmask 0.0.0. Since the SAs are automatically configured on both GiR plug-in units the filters should also be configured on both plug-in units.0.digicelgroup.0.0.0 -dip 0.0 -ipnext 51 -ipnextq 1 -ipopt false -sa AhTunnelIn1 -log false } {-rule 2 -proto 0 -sip 0.0 -dmask 0.0.0.0.0.0.0 -dip 0.0.0 -ipnext 0 -ipnextq 3 -ipopt false -log false } These filters allow all incoming and outgoing traffic.0.0. One rule catch incoming IPsec packets and sends them for IPsec processing. it is enough to configure one filter rule per protocol number (it means IPSec AH. IPSec ESP and GRE).0 -dmask 0.2.4.0. Example 12 Inbound Filter Settings create_pf_policy -eq {2 11 2 1} -name ETH_2_11_0 -dir 1 {-rule 3 -proto 0 -sip 0.0.0.0. Therefore.0.0 -ipnext 0 -ipnextq 3 -ipopt false -log false } These filters allow all incoming and outgoing traffic.local:80/alexserv?id=31493 Page 24 of 33 . http://digimqalex01.0.0 -ipnext 0 -ipnextq 3 -ipopt false -log false } This filter uses two rules.

Example 15 Inbound Filter Settings create_pf_policy -eq {2 11 2 1} -name ETH_2_11_0 -dir 1 {-rule 3 -proto 0 -sip 0.0.0. Example 13 Outbound Filter Settings create_pf_policy -eq {2 11 2 1} -name ETH_2_11_0 -dir 2 {-rule 2 -proto 0 -sip 0.0.0. Note: Rule 3 is configured once for all the GRE tunnels.0 -dip 0.0.0 -ipnext 47 -ipnextq 1 -ipopt false -sa ISPtunnel1 -log false } {-rule 2 -proto 0 -sip 0.0.0. Consequently the examples below correspond to those in Section 7.0.0 -smask 0.0.local:80/alexserv?id=31493 Page 25 of 33 .0 -dmask 0.digicelgroup.0 } -name AhTunnelIn1 -dir 1 {-rule 2 -proto 0 -sip 0.0 -dip 0.0.fwi. smask.0.0 -dip 0.0 -smask 0.0. The GGSN itself directs the trafic in this case. 50 for IPsec ESP and 51 for IPsec AH).0.Gateway GPRS Support Node (GGSN) .6 Filter Rules when Using GRE Example The only attribute that distinguishes the filter settings for GRE from the ones for IPsec is ipnext.0.4. Example 14 Inbound Interface Filter create_pf_policy -eq { 0.0.0. http://digimqalex01. Note: The tunnel interface filter is configured to only filter inbound packets. the other rule allows all incoming packets to enter the GGSN.0.0.0.0.0. Note: The GRE tunnel must be configured prior to the filter settings.0.0 -dmask 0. dip and dmask should be configured with the IP address 0.0 -smask 0. smask.0. which indicates the protocol number (47 for GRE.0 AC-A09 10/01/10 11:37 Note: Rule 3 is configured once for each type of tunnel (IPsec AH or IPsec ESP).0.0 -dip 0. Since the GRE tunnels are automatically configured on both GiR plug-in units the filters should also be configured on both plug-in units.0 -dmask 0. hence the equipment identifier is configured to {0 0 0 0}.0 -smask 0.0. The values of the attributes sip. One rule catch incoming GRE packets and sends them for GRE processing. In this example all traffic is allowed.0.0.5.0 -ipnext 0 -ipnextq 3 -ipopt false -log false} The incoming traffic is filtered after IPsec treatment.0 -dmask 0. The values of the attributes sip. This must be done by repeating the commands.2. The GSN itself will then automatically direct trafic to any of the tunnels of that type.2.0.0.0.0. 7.0.0 -ipnext 0 -ipnextq 3 -ipopt false -log false } This example contains one filter rule that allows all outgoing traffic.0.0 -ipnext 0 -ipnextq 3 -ipopt false -log false } This filter uses two rules.0.0.0.0.

hence the equipment identifier is configured to {0 0 0 0}.0.0.0 -smask 0. All traffic is allowed in this situation.digicelgroup.0.0 -dip 0.0.0 -ipnext 0 -ipnextq 3 -ipopt false -log false } This example contains one filter rule that allows all outgoing traffic.0.0.0 since this area is to be used on the external interface.0.0 -dmask 0.0. Example 20 Configuring Virtual Links Between two GiR Plug-in Units Page 26 of 33 http://digimqalex01.3 Internal Routing Configuration Example Example 18 Enable Internal OSPF Routing set_ospf_igi {-area 0. Example 17 Inbound Interface Filter create_pf_policy -eq { 0 0 0 0 } -name AhTunnelIn1 -dir 1 {-rule 2 -proto 0 -sip 0.0.0.0. For example. The GSN itself will then automatically direct trafic to any of the tunnels of that type.0 AC-A09 10/01/10 11:37 dip and dmask should be configured with the IP address 0.0. Note: The OSPF area may not be set to 0.130.0.0. The GGSN itself directs the traffic in this case.0. OSPF is the routing protocol that is used internally.0. between the GiR and GiA plugin units.28.0.0 -dmask 0.0.local:80/alexserv?id=31493 .0. the IP addresses on two of the normal IP routed interfaces can be used as GiR identities.0. Note: The tunnel interface filter is configured to only filter inbound packets.0.0 -ipnext 0 -ipnextq 3 -ipopt false -log false } This filter processes the packets in the tunnel instead of filtering the tunnel just as in Example 15. Example 19 Setting Router Identity on a GiR Plug-in Unit set_router_id -eq {2 11 2 1} -ip 172.4 Note: The router IDs may not collide with any of the other router IDs within an autonomous system.Gateway GPRS Support Node (GGSN) .0.4 -retr 5 -hello 10 -rtrd 40} This example illustrates how to enable routing on the IGi subnetwork.0 -dip 0. Example 16 Outbound Filter Settings create_pf_policy -eq {2 11 2 1} -name ETH_2_11_0 -dir 2 {-rule 2 -proto 0 -sip 0.4. 7.0.fwi.0 -smask 0.

0.0 -custom "virtuallink neighborid 172.10} Example 22 Exportation of Static Route Information to the OSPF Database set_route_export -eq {2 11 2 1} -dst {-proto 3 -src {-proto 5 -filter {-ip 0. in order to create an area boarder to the IGi subnetwork.3 RIP Example http://digimqalex01.fwi. Example 23 Enable External OSPF Routing on an Ethernet Plug-in Unit set_ospf_if -eq {2 11 2 1} {-ip 172.20.0.0.4 transitarea 0.4 -type 1 -area 0.4.1 Static Routes Example Example 21 Setting Static Routes on a GiR Plug-in Unit set_static_route -eq {2 11 2 1} {-dip 172.0 -custom "virtuallink neighborid 172. 7. In this example the opposite GiR plug-in unit is situated in mag <2>. slot <13> and has the router ID 172.0.28.4.0 -gip 172.0.40. varies a little depending on whether using Ethernet or ATM plug-in units. in other words.130.0.0.130.28.0 -rule 2}}} The configuration is implemented the same way independent on if the plug-in unit is running Ethernet or ATM.local:80/alexserv?id=31493 Page 27 of 33 .255.0.4.0.4.0 AC-A09 10/01/10 11:37 custom_ospf_area -eq {2 11 2 1} -area 0.Gateway GPRS Support Node (GGSN) . which describes the interface type. The example below shows the Ethernet situation but the disagreement in the ATM case is minor. The virtual link must be configured cross wise on both GiR plug-in units.0.0. 7.28.0.0 -mask 255." custom_ospf_area -eq {2 13 2 1} -area 0. 7.0 -prio 1 -retr 5 -hello 10 -rtrd 40 -cost 1} The only attribute that distinguishes the Ethernet and ATM cases are type.28. OSPF virtual links must be configured between the two GiR plug-in units.131.0." To achieve full redundancy at link failure. the information on the GiR plug-in units should be propagated to the internal OSPF domain. Note: The OSPF area on the external GiR plug-in units should always be set to 0.255.0.0.4.0 -mask 0.130.28.4 External Routing Configuration Example The GiR plug-in units can be configured to use either static routes or to use a routing protocol like OSPF.131. 7.digicelgroup.2 OSPF Routing Externally Example The configuration of OSPF routing externally.4 transitarea 0. RIP or BGP.4.0. If not using OSPF externally the routing information must be exported to the OSPF database.4.0. An Ethernet plug-in unit is configured to use a broadcast interface while an ATM plugin unit is using a point-to-point interface.

4 -src {-proto 1 -filter {-ip 0.24. the routing method is set to IP.0 -mask 0. that http://digimqalex01.130.0 -rule 2}}} 7. 7. Since EBGP exchange information with other autonomous systems the autonomous system number must be known. metric.0.5 APN Configuration Example This section describes a variety of examples on how to set up an APN.5.24.1.28.255.254 -nm 255.Gateway GPRS Support Node (GGSN) .se -ubs no -fip 172.255.0.fwi.28.0 AC-A09 10/01/10 11:37 Example 24 Enabling RIP on a GiR Plug-in Unit set_rip -eq {2 11 2 1} -ip 172.130.0. Example 25 Exportation of RIP Information to the OSPF Database set_route_export -eq {2 11 2 1} -dst {-proto 3 -ip 172.254 -type 1 -as 2} The type indicates that EBGP is used. 7.0 -oad GGSN -ssgsn -ssubs -suser -rm IP Above. The llf attribute also contains a number.4 For a point-to-point link (for example ATM) the remote IP address of the interface should be used as the RIP interface address. These will now be connected to the LLF tunnel. Hence the configuration of the IP address differ depending on whether configuring an ATM or an Ethernet plug-in unit.0.5.0 -rule 2}}} Also when exporting the RIP information the destination IP address should be chosen according to whether configuring an ATM or an Ethernet plug-in unit.0 -gip 172.digicelgroup. 7.0. Otherwise (for example Ethernet) the local IP address of an interface should be used. Example 26 Setting Autonomous System Number on a GiR Plug-in Unit set_router_as -eq {2 11 2 1} -as 1 Example 27 Enabling EBGP on a GiR Plug-in Unit set_bgp_peer -eq {2 11 2 1} {-ip 172. The example above illustrates the Ethernet case.0. The MS is assigned an IP address provided by the GGSN.ericsson.4.2 APN Routed APN Example When APN is used as routing method the attribute llf must be configured. IPsec tunnels or GRE tunnels previously created.0.0.0 -mask 0.130. Example 28 Exportation of BGP Information to the OSPF Database set_route_export -eq {2 11 2 1} -dst {-proto 3 -as 2 -src {-proto 4 -filter {-ip 0.1 IP Routed APN Example Example 29 IP Routed APN create_apn apn04a.28.1. The parameter contains the name (or names) of the external ATM PVCs.4 BGP Example Only EBGP is relevant on the Gi interface.4.local:80/alexserv?id=31493 Page 28 of 33 .

24. Note: The external tunnels that are connected to the LLF tunnels must be created prior to the APN configuration.0 -oad GGSN -ssgsn -ssubs -suser -rm LLF -llf ATM_2_11_1_1_101.digicelgroup.ericsson.20 ATM_2_13_1_1_101. One IPsec tunnel is used for outbound traffic (AhTunnelOut1) and the other one is for inbound traffic (AhTunnelIn1).4. The PVC named ATM_2_11_1_1_101 has a higher priority then the one named ATM_2_13_1_1_101.0 -oad GGSN -ssgsn -ssubs -suser -rm LLF -llf AhTunnelIn1.254 -nm 255. Inband RADIUS Used create_apn apn04d.24. was created in Example 4. If load sharing is desired two PVCs with the same metric should be configured. the LLF tunnel is linked to a GRE tunnel. inband RADIUS is used for IP address allocation and authentication. hence traffic will be sent through the first prior to the second.4.fwi.20 In this example the LLF tunnel is connected to one ATM PVC.24.0 -gip 172. the MS is assigned an IP address provided by the GGSN.255.ericsson.se -ubs no -fip 172.3.253 -pip 172. Since GRE is a bidirectional protocol just one tunnel is necessary.se -ubs no -fip 172.se -ubs no -fip 172.255. As above. Also in this case the MS is assigned an IP address provided by the GGSN. The LLF tunnel is connected to the previously created IPsec SAs. The MS is assigned an IP address provided by the GGSN. named ATM_2_11_1_1_101.2.254 -nm 255.se -ubs no -fip 172.255.3.4.24.255.254 -nm 255.24.local:80/alexserv?id=31493 Page 29 of 33 .255.0 -gip 172.0 -gip 172.255. Hence.255.2. Example 32 APN Routed APN Connected to an IPsec Tunnel create_apn apn04b.1 The purpose of this example is to describe two important matters.0 -ru inband -repi 172.3. in contrast to IPsec.28.254 -nm 255. Example 31 APN Routed APN Connected to Two ATM PVCs create_apn apn04c. The metric must be higher on outgoing traffic then on incoming.5 AhTunnelOut1. Example 30 APN Routed APN Connected to One ATM PVC create_apn apn04c.10 Since SAs and GRE tunnels are automatically setup on both GiR plug-in units the LLF tunnel are automatically setup to both GiR plug-in units.0 AC-A09 10/01/10 11:37 indicates the priority of the link. in this case it has nothing to do with priority.3. This particular ATM PVC. Second.4. First.0 -gip 172.0 -oad GGSN -ssgsn -ssubs -suser -rm LLF -llf ATM_2_11_1_1_101.255. http://digimqalex01.24. Example 33 APN Routed APN Connected to a GRE Tunnel. the MS is assigned an IP address provided by the RADIUS.131.24.ericsson.Gateway GPRS Support Node (GGSN) .2 -pqt 2000 -pqr 6 -pek gprs5 -oad RADIUS -ssgsn -ssubs -suser -rm LLF -llf ISPtunnel1.24.10 This case describes how to configure the APN routed APN when the LLF tunnel is connected to two redundant ATM PVCs.24.ericsson.

254 -nm 255. Hence. GRE. it may as well be connected to either an IPsec tunnel or an ATM PVC or normal IP routing can be used.com -fip "170.255. has been created to handle communication between the GGSN and the RADIUS server.0 170.0 -ru outband -rapn rapn04 -oad RADIUS -ssgsn -ssubs -suser -rm LLF -llf ISPtunnel2.1.ericsson.se -ubs no -fip 172.1 Example 37 Creation of another APN Using the Same Outband RADIUS APN create_apn apn04f.24.7.24. Example 38 Creation of an APN Using a DHCP Server for IP Address Allocation create_apn apn04e.2 -pqt 2000 -pqr 6 -pek gprs5 -rm LLF -llf Radiustunnel1.7 DHCP Configuration Example The MS can also be assigned an IP address provided by a DHCP server. This is done to improve the internal loadsharing and redundancy in GGSN.1 In both examples above outband RADIUS is used for IP address allocation and authentication.28.24. This is no requirement though.255.7.0 -gip 172. Example 35 Creation of a RADIUS APN create_rapn rapn04 -repi 172.24.fwi.24. with the IP Address Range Configured as Several Ranges create_apn ericsson1.0.0 AC-A09 10/01/10 11:37 Example 34 APN Routed APN.local:80/alexserv?id=31493 Page 30 of 33 .254 -nm 255.131.Gateway GPRS Support Node (GGSN) .0 -ru outband -rapn rapn04 -oad RADIUS -ssgsn -ssubs -suser -rm LLF -llf ISPtunnel3.255.253 -oad DHCP -ssgsn -ssubs -suser -rm LLF -llf ISPtunnel31.255.17.1 An APN called rapn04. The same could also be done for APNs with smaller IP address ranges.254 -nm 255. The APNs using the RADIUS APN can be linked to any kind of tunnels.se -ubs no -fip 172.0 -dsaddr 172.ericsson. 7.255.254" -nm "255. to achieve a better internal redundancy in GGSN.ericsson.0 -gip 172.17.5. 7.255.0" -gip "170. In this case the RADIUS APN is linked to a GRE tunnel.4.1.6.0 -gip 172.1 http://digimqalex01.6.255.17.digicelgroup.255. a RADIUS APN must be configured prior to the APN configuration. the MS is assigned an IP address provided by a RADIUS server in another network.0.24.1 -pip 172.24.253 -epi 172.34. according to the example above. Example 36 Creation of an Outband APN Routed RADIUS APN create_apn apn04e.0 255.0" -oad GGSN -rm IP For APNs containing an IP address range with more than 30 KB IP addresses it is recommended that the IP address range is configured as several ranges.255.255.7.se -ubs no -fip 172.5.6 Outband RADIUS Configuration Example When using outband RADIUS.24. IPsec or ATM PVCs or normal IP routing can be used.7.

local:80/alexserv?id=31493 Page 31 of 33 .4.0 AC-A09 10/01/10 11:37 When communicating with the DHCP server the GGSN uses the External Protocol IP Address in the APN.Gateway GPRS Support Node (GGSN) . it cannot handle authentication. In the example above the DHCP server performs the IP address allocation. See Reference [51]. however.digicelgroup.fwi. http://digimqalex01. 8 Related Documents Gn/Gp and Gom Interface Configuration. It is possible to combine DHCP IP address allocation and inband or outband RADIUS authentication.

MANUAL PAGE. [38] Detaching an Ethernet Interface from the TCP/IP Stack. OPERATION DIRECTIONS. [18] Creating a RADIUS APN. OPERATION DIRECTIONS. MANUAL PAGE. 4/190 80-CXC 132 0509. MANUAL PAGE. OPERATION DIRECTIONS. [42] disconnect_eth_ip. [29] delete_rip. 15/190 80-CXC 132 660. [8] create_apn. [35] Deleting a Security Association or GRE Tunnel.0 AC-A09 10/01/10 11:37 9 Reference List [1] Activating and Deactivating RIP. 203/154 31-CXC 132 0863. [39] Detaching an IP Interface from an ATM VC. MANUAL PAGE. [24] delete_ipsec_sa. 14/154 31-CRA 250 39. 150/154 31-CXC 132 0863. MANUAL PAGE. 205/154 31-CXC 132 0863. [4] BGP-4 (Border Gateway Protocol) OPERATION DIRECTIONS. [32] Deleting All Policies of an Interface or of an SA. 10/190 80-CXC 132 660. 16/190 80-CRA 250 39. 201/154 31-CXC 132 0863. http://digimqalex01. [13] create_rapn. 205/190 80-CXC 132 879. 2/154 31-CXC 132 0866. 1/190 80-CXC 132 1157. OPERATION DIRECTIONS. 204/190 80-CXC 132 879.digicelgroup. [26] delete_ospf_igi.4. MANUAL PAGE.local:80/alexserv?id=31493 Page 32 of 33 . 2/154 31-CXC 132 0868. 8/154 31-CXC 132 0861. [21] delete_atm_vc. [15] Creating a New Policy. 17/154 31-CRA 250 39. 4/154 31-CXC 132 0866. 202/190 80-CXC 132 879. OPERATION DIRECTIONS. [9] create_atm_vc.fwi. OPERATION DIRECTIONS. OPERATION DIRECTIONS. 10/190 80-CRA 250 39. MANUAL PAGE. OPERATION DIRECTIONS. [12] create_pf_policy. OPERATION DIRECTIONS. MANUAL PAGE. MANUAL PAGE. 1/154 31-CXC 132 0868. MANUAL PAGE. MANUAL PAGE. 4/190 80-CXC 132 660. OPERATION DIRECTIONS. MANUAL PAGE. 6/190 80-CXC 132 0509. [11] create_ipsec_sa. [41] disconnect_atm_vc_ip. [17] Creating a New Virtual Circuit. MANUAL PAGE. OPERATION DIRECTIONS. [31] delete_static_route. [5] Changing the Settings of a Security Association or GRE Tunnel. OPERATION DIRECTIONS. [40] Disabling OSPF for an Interface. 3/154 31-CXC 132 0866. 15/154 31-CRA 250 39. 203/190 80-CXC 132 879. [2] Attaching an Ethernet Equipment to the TCP/IP Stack. OPERATION DIRECTIONS. OPERATION DIRECTIONS. 1/190 80-CXC 132 0509. [27] delete_pf_policy. [33] Deleting an APN. [28] delete_rapn. MANUAL PAGE. OPERATION DIRECTIONS. MANUAL PAGE. 2/190 80-CXC 132 1157. MANUAL PAGE. MANUAL PAGE. [20] delete_apn.Gateway GPRS Support Node (GGSN) . [19] De-initializing the ATM Driver. 151/190 80-CXC 132 879. 15/190 80-CRA 250 39. MANUAL PAGE. 152/190 80-CXC 132 879. 4/154 31-CXC 132 0861. MANUAL PAGE. [25] delete_ospf_if. [14] Creating an APN. [22] delete_bgp_peer. OPERATION DIRECTIONS. 22/190 80-CXC 132 660. [23] delete_gre_tunnel. 202/154 31-CXC 132 0863. 12/190 80-CRA 250 39. 6/190 80-CXC 132 660. [6] connect_atm_vc_ip. MANUAL PAGE. 3/190 80-CXC 132 0509. [7] connect_eth_ip. [3] Attaching an IP Interface to an ATM VC. 3/154 31-CXC 132 0868. 151/154 31CXC 132 0863. OPERATION DIRECTIONS. [34] Deleting a RADIUS APN. [10] create_gre_tunnel. 11/154 31-CRA 250 39. MANUAL PAGE. 9/154 31-CXC 132 0861. MANUAL PAGE. OPERATION DIRECTIONS. [30] delete_route_export. [37] Deleting a Virtual Circuit. 204/154 31-CXC 132 0863. [16] Creating a New Security Association or GRE Tunnel. 18/190 80-CXC 132 660. OPERATION DIRECTIONS. [36] Deleting a Selected Policy.

[66] set_bgp_peer. MANUAL PAGE. 2/154 31-CXC 132 0861. DESCRIPTION. [75] set_router_id. 6/154 31-CXC 132 0866. 16/154 31-CRA 250 39. OPERATION DIRECTIONS. MANUAL PAGE. [77] Specifying the Autonomous System. PARAMETER DESCRIPTION. 1/154 31-CXC 132 0866.CXC 132 879. [54] list_apns. [68] set_ipsec_sa. MANUAL PAGE. [47] Exports (Route Exportation Policies) OPERATION DIRECTIONS. [55] list_rapns. 9/190 80-CXC 132 660. 21/190 80-CXC 132 660. 200/154 31-CXC 132 0863. 10/154 31-CXC 132 0861. [60] Operation and Maintenance Description. 6/154 31-CXC 132 0861. [48] get_apn. OPERATION DIRECTIONS. [59] Modifying the Settings of an Existing Policy. [57] Modifying the Attributes of a RADIUS APN. OPERATION DIRECTIONS. 2/1551-AXB 250 04. [72] set_rip. [45] Editing the OSPF Settings for an Active Interface. [67] set_gre_tunnel. [76] set_static_route. MANUAL PAGE. OPERATION DIRECTIONS. [63] Reusing the OSPF Settings of a "Down" Interface. 17/190 80-CXC 132 660. MANUAL PAGE. [61] Parameter Description GGSN 4. MANUAL PAGE. 3/190 80-CXC 132 660. OPERATION DIRECTIONS. [78] Specifying the Router ID. 12/154 31-CRA 250 39. [49] get_rapn. http://digimqalex01. OPERATION DIRECTIONS. OPERATION DIRECTIONS. 19/190 80-CRA 250 39. [62] Parameter Description CGSN G 3.CXC 132 879. OPERATION DIRECTIONS. MANUAL PAGE. 13/190 80-CXC 132 660.digicelgroup. [70] set_ospf_igi. [73] set_route_export. DESCRIPTION.0. MANUAL PAGE. 12/154 31-CXC 132 0861. 2/1551-AXB 250 02. 2/190 80-CXC 132 0509. 5/154 31-CXC 132 0861. OPERATION DIRECTIONS. [82] WCDMA GSN System Description. [58] Modifying the Order of the Existing Policies.4. 3/154 31-CXC 132 0861. [65] set_apn. OPERATION DIRECTIONS. 17/190 80-CRA 250 39. 13/154 31-CRA 250 39. [79] start_atm.0 AC-A09 10/01/10 11:37 [43] Displaying the Attributes of an APN. 14/190 80-CRA 250 39. [81] stop_atm. [52] GSM GSN System Description. 5/190 80-CXC 132 660. MANUAL PAGE. MANUAL PAGE. PARAMETER DESCRIPTION. 11/190 80-CRA 250 39. [50] Gi Interface Description. [53] Initializing the ATM Driver. DESCRIPTION. MANUAL PAGE. [71] set_rapn. 1/1551-AXB 250 03. [46] Enabling OSPF for an Interface. MANUAL PAGE. DESCRIPTION. 18/190 80-CRA 250 39. 18/154 31-CRA 250 39. 208/190 80 . [64] Selecting a Security Association. 3/1543-AXB 250 03. [56] Modifying the Attributes of an APN. MANUAL PAGE. 5/154 31-CXC 132 0866. OPERATION DIRECTIONS. MANUAL PAGE. 2/190 84-AXB 250 07. 207/190 80 . OPERATION DIRECTIONS. MANUAL PAGE.0. MANUAL PAGE. MANUAL PAGE.fwi. 14/190 80-CXC 132 660.local:80/alexserv?id=31493 Page 33 of 33 .Gateway GPRS Support Node (GGSN) . 13/190 80-CRA 250 39. [44] Displaying the Attributes of a RADIUS APN. 2/190 80-CXC 132 660. 1551-AXB 250 04. OPERATION DIRECTIONS. 7/154 31-CXC 132 0861. [80] Static Route. 5/190 80-CXC 132 0509. MANUAL PAGE. OPERATION DIRECTIONS. [51] Gn/Gp and Gom Interface Configuration. OPERATION DIRECTIONS. 1/190 84-AXB 250 02. [74] set_router_as. [69] set_ospf_if.

Sign up to vote on this title
UsefulNot useful