Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Example: Configuring MobileNext Broadband Gateway with Provider Edge Functionality

    This example describes how to configure the MobileNext Broadband Gateway integrated with provider edge functionality.

    Requirements

    This example uses the following hardware and software components:

    • Junos OS Release 11.2W
    • Juniper Networks MobileNext Broadband Gateway

    Before you configure the broadband gateway, make sure you have the following information:

    • IP addresses for configuring GPRS tunneling protocol (GTP), RADIUS, and charging signaling functions.
    • MPLS provider-edge configuration details for MX 3D Universal Edge Routers, including BGP peer configuration, IP addresses, AS number, import/export route target, and IGP configuration.

    Overview

    This example describes how to configure the broadband gateway integrated with provider edge functionality. VPN routing and forwarding (VRF) is used to support the following configuration:

    • Internal BGP is used to exchange VPN routing information between the provider edge routers.
    • RSVP is used in the MPLS backbone to establish the label-switched paths (LSPs) between the provider edge routers.

      Note: All routing instances are VRF routing instances in the MPLS VPN.

    • 3GPP interfaces (Gn and S5) for control are in the same VRF called VRF11-Control.
    • 3GPP interfaces (Gn and S5) for data are in the same VRF called VRF11-Data.
    • 3GPP interfaces (Gp and S8) for control are in the same VRF called VRF12-Control.
    • 3GPP interfaces (Gp and S8) for data are in the same VRF called VRF12-Data.
    • Gi interfaces (Gi, SGi) to the external networks are in the same VRF named VRF3.
    • RADIUS server and charging are in the VRF called VRF2.

    Table 1: Components of the Broadband Gateway

    Property

    Settings

    Description

    Loopback address

    lo0 unit 100 address 192.168.100.1/32

    lo0 unit 111 address 192.168.111.1/32

    lo0 unit 112 address 192.168.112.1/32

    lo0 unit 121 address 192.168.121.1/32

    lo0 unit 122 address 192.168.122.1/32

    lo0 unit 200 address 192.168.200.1/32

    Interfaces used for 3GPP signaling and IP routing functions

    Routing protocol

    bgp

    Indicates device is using BGP as routing protocol

    MPLS protocol and LSP definition

    mpls

    Indicates device is using the MPLS protocol

    RSVP

    rsvp

    Indicates device is using RSVP

    Gi/SGi routing instance

    VRF3

    mif.0

    Mobile interface unit 0 (mif unit 0) is associated with Gi/SGi routing instance by placing the interface in VRF3

    Gn/S5 control connectivity

    VRF11-Control

    lo0.111

    VRF for Gn/S5 interfaces for control

    Gn/S5 data connectivity

    VRF11-Data

    lo0.112

    VRF for Gn/S5 interfaces for data

    Gp/S8 control connectivity

    VRF12-Control

    lo0.121

    VRF for Gp/S8 interfaces for control

    Gp/S8 data connectivity

    VRF12-Data

    lo0.122

    VRF for Gp/S8 interfaces for data

    RADIUS/charging connectivity

    VRF2

    lo0.200

    VRF for charging and RADIUS servers

    Configuration

    Configuring the Chassis

    CLI Quick Configuration

    To quickly configure this example, copy the following commands and paste them into the router terminal window:

    [edit]load merge /etc/config/mobility-defaults.confset chassis fpc 1 pic 0 apply-groups mobilityset chassis fpc 1 pic 1 apply-groups mobilityset chassis fpc 3 pic 0 apply-groups mobilityset chassis fpc 3 pic 1 apply-groups mobilityset chassis fpc 0 forwarding-packages mobility ggsn-pgw set chassis fpc 5 forwarding-packages mobility ggsn-pgw set interfaces lo0 unit 100 family inet address 192.168.100.1/32set interfaces lo0 unit 111 family inet address 192.168.111.1/32set interfaces lo0 unit 112 family inet address 192.168.112.1/32set interfaces lo0 unit 121 family inet address 192.168.121.1/32set interfaces lo0 unit 122 family inet address 192.168.122.1/32set interfaces lo0 unit 200 family inet address 192.168.200.1/32set chassis fpc 5 pic 2 tunnel-services bandwidth 10gset interfaces vt-5/2/0 unit 0 family inet

    Step-by-Step Procedure

    To configure the chassis:

    1. Load and merge the default configuration file for the mobility group.
      [edit]user@pe1# load merge /etc/config/mobility-defaults.conf
    2. Configure the mobility group on the session DPCs.
      [edit]user@pe1# set chassis fpc 1 pic 0 apply-groups mobilityuser@pe1# set chassis fpc 1 pic 1 apply-groups mobilityuser@pe1# set chassis fpc 3 pic 0 apply-groups mobilityuser@pe1# set chassis fpc 3 pic 1 apply-groups mobility

      Note: You must include every services PIC configured with the jservices-mobile package at the [edit unified-edge gateways ggsn-pgw gateway-name system anchor-spics] hierarchy level on the broadband gateway. If you do not include the services PIC as an anchor interface, then the services PIC will not be used by the broadband gateway.

    3. Configure the interface MPC at the FPC level.
      [edit]user@pe1# set chassis fpc 0 forwarding-packages mobility ggsn-pgwuser@pe1# set chassis fpc 5 forwarding-packages mobility ggsn-pgw

      Note: You must include every Packet Forwarding Engine configured with the ggsn-pgw forwarding package at the [edit unified-edge gateways ggsn-pgw gateway-name system anchor-pfes] hierarchy level on the broadband gateway. If you do not specify the Packet Forwarding Engine as an anchor interface, then the Packet Forwarding Engine will not be used by the broadband gateway.

    4. Configure loopback interfaces for signaling functions.
      [edit]user@pe1# set interfaces lo0 unit 100 family inet address 192.168.100.1/32user@pe1# set interfaces lo0 unit 111 family inet address 192.168.111.1/32user@pe1# set interfaces lo0 unit 112 family inet address 192.168.112.1/32user@pe1# set interfaces lo0 unit 121 family inet address 192.168.121.1/32user@pe1# set interfaces lo0 unit 122 family inet address 192.168.122.1/32user@pe1# set interfaces lo0 unit 200 family inet address 192.168.200.1/32
    5. Configure the tunnel interfaces.
      [edit]user@pe1# set chassis fpc 5 pic 2 tunnel-services bandwidth 10guser@pe1# set interfaces vt-5/2/0 unit 0 family inet

    Configuring the MPLS/BGP VPN

    CLI Quick Configuration

    To quickly configure this example, copy the following commands and paste them into the router terminal window:

    [edit]set protocols mpls label-switched-path LSP1 to 192.168.100.5set protocols mpls label-switched-path LSP1 no-cspfset protocols mpls interface xe-1/0/1set protocols rsvp interface xe-1/0/1set protocols bgp local-as 14203set protocols bgp group PE1-PE2 type internal set protocols bgp group PE1-PE2 local-address 192.168.100.1set protocols bgp group PE1-PE2 family inet-vpn unicastset protocols bgp group PE1-PE2 neighbor 192.168.100.5

    Step-by-Step Procedure

    To enable MPLS and RSVP:

    1. In the MPLS configuration, specify the LSP used for dynamic MPLS and disable constrained-path LSP computation.
      [edit]user@pe1# set protocols mpls label-switched-path LSP1 to 192.168.100.5user@pe1# set protocols mpls label-switched-path LSP1 no-cspf
    2. Include the interface in the MPLS and RSVP protocol configuration.
      [edit]user@pe1# set protocols rsvp interface xe-1/0/1user@pe1# set protocols mpls interface xe-1/0/1
    3. Configure the local AS for BGP updates.
      [edit]user@pe1# set protocols bgp local-as 14203
    4. Configure the BGP group for Layer 3 VPNs.
      [edit]user@pe1# set protocols bgp group PE1-PE2 type internaluser@pe1# set protocols bgp group PE1-PE2 local-address 192.168.100.1user@pe1# set protocols bgp group PE1-PE2 family inet-vpn unicastuser@pe1# set protocols bgp group PE1-PE2 neighbor 192.168.100.5

    Enabling the Routing Instances for the VPN

    CLI Quick Configuration

    To quickly configure this example, copy the following commands and paste them into the router terminal window:

    [edit]set routing-instances VRF11-Control instance-type vrfset routing-instances VRF11-Control interface lo0.111set routing-instances VRF11-Control route-distinguisher 192.168.100.1:111set routing-instances VRF11-Control vrf-target target:1:111set routing-instances VRF11-Control vrf-table-labelset routing-instances VRF11-Data instance-type vrfset routing-instances VRF11-Data interface lo0.112set routing-instances VRF11-Data route-distinguisher 192.168.100.1:112set routing-instances VRF11-Data vrf-target target:1:112set routing-instances VRF11-Data vrf-table-labelset routing-instances VRF12-Control instance-type vrfset routing-instances VRF12-Control interface lo0.121set routing-instances VRF12-Control route-distinguisher 192.168.100.1:121set routing-instances VRF12-Control vrf-target target:1:121set routing-instances VRF12-Control vrf-table-labelset routing-instances VRF12-Data instance-type vrfset routing-instances VRF12-Data interface lo0.122set routing-instances VRF12-Data route-distinguisher 192.168.100.1:122set routing-instances VRF12-Data vrf-target target:1:122set routing-instances VRF12-Data vrf-table-labelset routing-instances VRF2 instance-type vrfset routing-instances VRF2 interface lo0.200set routing-instances VRF2 route-distinguisher 192.168.100.1:200set routing-instances VRF2 vrf-target target:1:200set routing-instances VRF2 interface vt-5/2/0.0

    Step-by-Step Procedure

    To configure the routing instance for the VRF used in the Layer 3 VPN:

    Best Practice: For GTP traffic, use the vrf-table-label option when configuring the routing instances. For RADIUS or charging traffic, use the tunnel interface when configuring the routing instance.

    1. Configure the VRF routing instances for GTP traffic.
      [edit]user@pe1# set routing-instances VRF11-Control instance-type vrfuser@pe1# set routing-instances VRF11-Control interface lo0.111user@pe1# set routing-instances VRF11-Control route-distinguisher 192.168.100.1:111user@pe1# set routing-instances VRF11-Control vrf-target target:1:111user@pe1# set routing-instances VRF11-Control vrf-table-labeluser@pe1# set routing-instances VRF11-Data instance-type vrfuser@pe1# set routing-instances VRF11-Data interface lo0.112user@pe1# set routing-instances VRF11-Data route-distinguisher 192.168.100.1:112user@pe1# set routing-instances VRF11-Data vrf-target target:1:112user@pe1# set routing-instances VRF11-Data vrf-table-labeluser@pe1# set routing-instances VRF12-Control instance-type vrfuser@pe1# set routing-instances VRF12-Control interface lo0.121user@pe1# set routing-instances VRF12-Control route-distinguisher 192.168.100.1:121user@pe1# set routing-instances VRF12-Control vrf-target target:1:121user@pe1# set routing-instances VRF12-Control vrf-table-labeluser@pe1# set routing-instances VRF12-Data instance-type vrfuser@pe1# set routing-instances VRF12-Data interface lo0.122user@pe1# set routing-instances VRF12-Data route-distinguisher 192.168.100.1:122user@pe1# set routing-instances VRF12-Data vrf-target target:1:122user@pe1# set routing-instances VRF12-Data vrf-table-label
    2. Configure the VRF routing instance for RADIUS or charging traffic.
      [edit]user@pe1# set routing-instances VRF2 instance-type vrfuser@pe1# set routing-instances VRF2 interface lo0.200user@pe1# set routing-instances VRF2 route-distinguisher 192.168.100.1:200user@pe1# set routing-instances VRF2 vrf-target target:1:200user@pe1# set routing-instances VRF2 interface vt-5/2/0.0

    Configuring GTP Interfaces

    CLI Quick Configuration

    To quickly configure this example, copy the following commands and paste them into the router terminal window:

    [edit]set unified-edge gateways ggsn-pgw MBG1 gtp gn control interface lo0.111set unified-edge gateways ggsn-pgw MBG1 gtp gn data interface lo0.112set unified-edge gateways ggsn-pgw MBG1 gtp gp control interface lo0.121set unified-edge gateways ggsn-pgw MBG1 gtp gp data interface lo0.122set unified-edge gateways ggsn-pgw MBG1 gtp s5 control interface lo0.111set unified-edge gateways ggsn-pgw MBG1 gtp s5 data interface lo0.112set unified-edge gateways ggsn-pgw MBG1 gtp s8 control interface lo0.121set unified-edge gateways ggsn-pgw MBG1 gtp s8 data interface lo0.122

    Step-by-Step Procedure

    To configure GTP interfaces:

    1. Configure the GTP interfaces for the broadband gateway called MBG1.
      [edit]user@pe1# edit unified-edge gateways ggsn-pgw MBG1 gtp
    2. Specify the appropriate loopback interface associated with the VRF routing instance for the Gn, Gp, S5, and S8 interfaces.
      [edit unified-edge gateways ggsn-pgw MBG1 gtp]user@pe1# set gn control interface lo0.111user@pe1# set gn data interface lo0.112user@pe1# set gp control interface lo0.121user@pe1# set gp data interface lo0.122user@pe1# set s5 control interface lo0.111user@pe1# set s5 data interface lo0.112user@pe1# set s8 control interface lo0.121user@pe1# set s8 data interface lo0.122

    Configuring the Source Interface for RADIUS and Charging Servers

    CLI Quick Configuration

    To quickly configure this example, copy the following commands and paste them into the router terminal window:

    [edit]set access radius servers radius_server source-interface lo0.200set unified-edge gateways ggsn-pgw MBG1 charging gtpp peer CGF source-interface lo0.200

    Step-by-Step Procedure

    To associate source interfaces with the RADIUS or charging servers:

    1. Specify the source interface for the RADIUS server.
      [edit]user@pe1# set access radius servers radius_server source-interface lo0.200
    2. Specify the source interface for the charging server.
      [edit]user@pe1# set unified-edge gateways ggsn-pgw MBG1 charging gtpp peer CGF source-interface lo0.200

    Enabling the APN Configuration

    CLI Quick Configuration

    To quickly configure this example, copy the following commands and paste them into the router terminal window:

    [edit]set interfaces mif unit 0 family inet set unified-edge gateways ggsn-pgw MBG1 apn-services apns wireless.juniper.net apn-data-type ipv4set unified-edge gateways ggsn-pgw MBG1 apn-services apns wireless.juniper.net mobile-interface mif.0set unified-edge gateways ggsn-pgw MBG1 apn-services apns wireless.juniper.net address-assignment localset unified-edge gateways ggsn-pgw MBG1 apn-services apns wireless.juniper.net aaa-profile aaa_profileset routing-instances VRF3 interface mif unit 0 family inet

    Step-by-Step Procedure

    To enable the APN configuration:

    1. Create the mobile interface for mobile subscribers.
      [edit]user@pe1# set interfaces mif unit 0 family inet
    2. Configure the APN services for mobile subscribers on the broadband gateway called MBG1.
      [edit]user@pe1# edit unified-edge gateways ggsn-pgw MBG1 apn-services
    3. Configure the wireless.juniper.net APN used for the mif.0 interface. This APN uses aaa_profile as the AAA profile.
      [edit unified-edge gateways ggsn-pgw MBG1 apn-services]user@pe1# set apns wireless.juniper.net apn-data-type ipv4user@pe1# set apns wireless.juniper.net mobile-interface mif.0user@pe1# set apns wireless.juniper.net address-assignment local user@pe1# set apns wireless.juniper.net aaa-profile aaa_profile
    4. Specify the VRF routing instance for routing mobile subscriber traffic on the mobile interface.
      [edit]user@pe1# set routing-instances VRF3 interface mif unit 0 family inet

    Verification

    Verifying MPLS LSP Status

    Purpose

    Verify the MPLS LSP status for broadband gateway initiation.

    Action

    user@pe1> show mpls lsp
    Ingress LSP: 1 sessions
    To              From            State Rt P     ActivePath       LSPname
    192.168.100.5   10.102.32.59    Up     0 *                      LSP1
    Total 1 displayed, Up 1, Down 0
    
    Egress LSP: 1 sessions
    To              From            State   Rt Style Labelin Labelout LSPname
    10.102.32.59    192.168.100.5   Up       0  1 FF       0        - LSP2
    Total 1 displayed, Up 1, Down 0
    
    Transit LSP: 0 sessions
    Total 0 displayed, Up 0, Down 0
    

    Meaning

    The show mpls lsp command displays information about the configured label-switched paths, including the destination address.

    Verifying Broadband Gateway Status

    Purpose

    Verify the status and statistics on the broadband gateway for GGSN/P-GW initiation, call establishment, and Gn-to-Gi connectivity across the MPLS core.

    Action

    user@pe1> show unified-edge ggsn-pgw status
        Mobile gateway status:
        Active Subscribers   :               1
        Active Sessions      :               1
        Active Bearers       :               1
        CPU Load (%)         :               0
        Memory Load (%)      :               28
    
    user@pe1> show unified-edge ggsn-pgw statistics gateway MBG1
    Control plane statistics:
        Session establishment attempts:             0
        Successful session establishments:          0
        MS/peer initiated session deactivations:    0
        Successful MS/peer initiated deactivations: 0
        Gateway initiated session deactivations:    0
        Successful gateway initiated deactivations: 0
    Data plane GTP statistics (Gn/S5/S8):
        Input     packets:          20
        Input     bytes:            2560
        Output    packets:          0
        Output    bytes:            0
        Discarded packets:          0
    Data plane GTP statistics (Gi):
        Input     packets:          0
        Input     bytes:            0
        Output    packets:          20
        Output    bytes:            2560
        Discarded packets:          0
    

    Meaning

    The show unified-edge ggsn-pgw status command displays the status of the broadband gateway, including the number of active subscribers, active sessions, and active bearers. It also displays the CPU load and memory load.

    The show unified-edge ggsn-pgw statistics command displays the control plane and data plane statistics for the broadband gateway.

    Verifying Mobile Interfaces

    Purpose

    Verify that there is no data loss across the mobile interfaces for call establishment and Gn-to-Gi connectivity across the MPLS core.

    Action

    user@pe1> show interfaces mif.0 extensive
      Logical interface mif.0 (Index 85) (SNMP ifIndex 812) (Generation 165)
        Flags: SNMP-Traps Encapsulation: GTP-over-MIF
        Bandwidth: 1000mbps
        Traffic statistics:
         Input  bytes  :              6160000
         Output bytes  :              6084936
         Input  packets:                70000
         Output packets:                69147
        Local statistics:
         Input  bytes  :                    0
         Output bytes  :                    0
         Input  packets:                    0
         Output packets:                    0
        Transit statistics:
         Input  bytes  :              6160000                    0 bps
         Output bytes  :              6084936                    0 bps
         Input  packets:                70000                    0 pps
         Output packets:                69147                    0 pps
        Protocol inet, MTU: 1440, Generation: 219, Route table: 12
          Flags: Sendbcast-pkt-to-re, Is-Primary
    

    Meaning

    The show interfaces mif.number extensive command displays detailed information about the specified mobile interface.

    Published: 2011-11-16