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 the SRC 3GPP Gateway

    This example describes how to configure the SRC 3GPP gateway.

    Requirements

    This example uses the following hardware and software components:

    • One or more C Series Controllers running the Juniper Networks Session and Resource Control (SRC) software
    • One or more MX Series 3D Universal Edge Routers or E Series Broadband Services Routers
    • One PCRF
    • Junos OS Release 11.4 or later

    No special configuration beyond device initialization is required before you can configure this feature.

    Before you configure and apply the configurations in this example, be sure you have an understanding of the following:

    • SRC 3GPP gateway
    • Diameter
    • SAE

    Overview

    This example does not show all possible configuration choices.

    Topology

    This example shows how to configure the SRC software for the SRC 3GPP gateway component. The SRC 3GPP gateway is connected to a single PCRF over the Gx interface running the Diameter application. The C Series Controller is also connected to an MX Series router called mx1. In this example, the connection to the mx1 router is using the Junos OS device driver.

    This example does not show all possible configuration choices.

    Figure 1: SRC 3GPP Gateway Example Topology

    SRC 3GPP Gateway Example Topology

    Configuration

    To configure the SRC 3GPP gateway, perform these tasks:

    CLI Quick Configuration

    To quickly configure this example, copy the following commands, paste them in a text file, remove any line breaks, change any details necessary to match your network configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy level.

    set slot 0 gw-3gpp initial directory-connection credentials testing1set slot 0 gw-3gpp initial directory-connection principal cn=conf,o=operators,o=umcset slot 0 gw-3gpp initial directory-connection url ldap://127.0.0.1:389set slot 0 gw-3gpp initial directory-eventing eventingset slot 0 gw-3gpp gx address 10.10.10.2set slot 0 gw-3gpp gx diameter-peer primary-pcrf set slot 0 gw-3gpp gx origin-host dukeset slot 0 gw-3gpp gx origin-realm example.comset slot 0 gw-3gpp gx port 3868set slot 0 gw-3gpp gx protocol tcpset slot 0 gw-3gpp logger debug file filename var/log/3gpp-gx-debug.log filter /debugset slot 0 gw-3gpp logger debug file maximum-file-size 1000000set slot 0 gw-3gpp logger error file filename var/log/3gpp-gx-error.log filter /errorset slot 0 gw-3gpp logger error file maximum-file-size 2000000set slot 0 gw-3gpp logger error file rollover-filename var/log/3gpp-gx-error.altset slot 0 gw-3gpp logger info file filename var/log/3gpp-gx-info.log /infoset slot 0 gw-3gpp logger info file maximum-file-size 2000000set slot 0 gw-3gpp logger info file rollover-filename var/log/3gpp-gx-info.altset slot 0 gw-3gpp shared /3gpp-gw-shareset slot 0 nic hostname DemoHost scenario-name OnePopSessionHandle snmp-agent initial directory-connection credentials testing1 principal cn=nic,ou=Components,o=Operators url ldap://127.0.0.1:389/set slot 0 nic hostname DemoHost scenario-name OnePopSessionHandle snmp-agent initial directory-eventing eventing set shared gw-3gpp group 3gpp-gw-shareset shared gw-3gpp group 3gpp-gw-share configuration nic-proxy-configuration sessionHdl resolution key-type SessionHandle resolver-name /realms/sessionHandle/A1 value-type SessionHandleset shared gw-3gpp group 3gpp-gw-share configuration subscriber-types session-handle subscriber-id-type session-handleset shared network diameter peer primary-pcrf address [ 10.10.10.5 ]set shared network diameter peer primary-pcrf origin-host cabeset shared network diameter peer primary-pcrf port 3868set shared network diameter peer primary-pcrf protocol tcpset shared network device mx1 device-type junosset shared network device mx1 management-address 10.10.10.1set shared network device mx1 virtual-router * sae-connection 10.10.10.2set shared sae configuration driver junos beep-server-port 3333 tls-beep-server-port 3434 sdx-group-name sdx sdx-session-group-name sdx-sessionsset shared sae configuration plug-ins name 3gppgw-test external set corba-object-reference file:///opt/UMC/3gpp/var/run/3gpp-gw.ior set attributes service-session-namecommitExitenable component gw-3gpp

    Configure the Local Properties for the SRC 3GPP Gateway

    Step-by-Step Procedure

    Local properties for the SRC 3GPP gateway include the Gx interface, the connection to the Juniper Networks database directory, the directory-monitoring properties, logging, specifying which group configuration to use for the SRC 3GPP gateway, and configuring the NIC operating properties.

    1. Configure the directory-connection properties for the SRC 3GPP gateway.
      [edit slot 0 gw-3gpp initial directory-connection]user@host# set credentials credentials user@host# set principal principal user@host# set url ldap://127.0.0.1:389
    2. Configure directory-eventing.
      [edit slot 0 gw-3gpp initial directory-eventing]user@host# set eventing
    3. Configure the SRC 3GPP gateway Gx interface:
      [edit slot 0 gw-3gpp gx]user@host# set address 10.10.10.2 user@host# set diameter-peer primary-pcrf user@host# set origin-host duke user@host# set origin-realm example.com user@host# set port 3868 user@host# set protocol tcp
    4. Configure logging.
      [edit slot 0 gw-3gpp logger debug]user@host# set file filename var/log/3gpp-gx-debug.log user@host# set filter /debug- user@host# set maximum-file-size 1000000 user@host# up user@host# set logger error file filename var/log/3gpp-gx-error.log user@host# set filter /error- user@host# set maximum-file-size 2000000 user@host# set rollover-filename var/log/3gpp-gx-error.alt user@host# up user@host# set logger info file filename var/log/3gpp-gx-info.log user@host# set filter /info- user@host# set maximum-file-size 2000000 user@host# set rollover-filename var/log/3gpp-gx-info.alt user@host# up
    5. Specify the shared group for the local configuration.
      [edit slot 0 gw-3gpp]user@host# set shared /3gpp-gw-share user@host# commit
    6. Configure the NIC operating properties:
      [edit slot 0 nic]user@host# set hostname DemoHost user@host# set scenario-name OnePopSessionHandle user@host# set snmp-agent user@host# edit initial directory-connection [edit slot 0 nic initial directory-connection]user@host# set credentials testing1 user@host# set principal cn=nic,ou=Components,o=Operators user@host# set url ldap://127.0.0.1:389/ user@host# up user@host# edit initial directory-eventing [edit slot 0 nic initial directory-eventing]user@host# set eventing user@host# up user@host# up user@host# commit

    Results

    Confirm the local configuration properties. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.

    [edit slot 0 gw-3gpp]
    user@duke# show
    gx {
      address 10.10.10.2;
      diameter-peer primary-pcrf;
      origin-host duke;
      origin-realm example.com;
      port 3868;
      protocol tcp;
    }
    initial {
      directory-connection {
        backup-urls '';
        credentials ********;
        principal cn=conf,o=operators,o=umc;
        url ldap://127.0.0.1:389/;
      }
      directory-eventing {
        eventing;
        polling-interval 30;
      }
    }
    logger debug {
      file {
        filename var/log/3gpp-gx-debug.log;
        filter /debug-;
        maximum-file-size 1000000;
      }
    }
    logger error {
      file {
        filename var/log/3gpp-gx-error.log;
        filter /error-;
        maximum-file-size 2000000;
        rollover-filename var/log/3gpp-gx-error.alt;
      }
    }
    logger info {
      file {
        filename var/log/3gpp-gx-info.log;
        filter /info-;
        maximum-file-size 2000000;
        rollover-filename var/log/3gpp-gx-info.alt;
      }
    }
    shared /3gpp-gw-share;
    
    [edit slot 0 gw-3gpp]
    user@duke#
    
    [edit slot 0 nic]
    user@duke# show
    base-dn o=umc;
    hostname DemoHost;
    initial {
      directory-connection {
        backup-urls '';
        credentials ********;
        principal cn=nic,ou=Components,o=Operators,<base>;
    url ldap://10.10.10.10:389/;
      }
      directory-eventing {
        eventing;
        polling-interval 15;
      }
    }
    scenario-name OnePopSessionHandle;
    snmp-agent;
    
    [edit slot 0 nic]
    user@duke#
    

    Configure the Shared Properties for the SRC 3GPP Gateway

    Step-by-Step Procedure

    Configure the shared properties for the SRC 3GPP gateway including the shared group configuration, NIC proxy configuration, and subscriber type.

    1. Specify the group to configure:
      [edit shared gw-3gpp]user@host# edit group 3gpp-gw-share
    2. Configure the NIC proxy configuration:
      [edit shared gw-3gpp group 3gpp-gw-share configuration]user@host# edit nic-proxy-configuration sessionHdl resolution [edit shared gw-3gpp group 3gpp-gw-share configuration nic-proxy-configuration sessionHdl resolution]user@host# set key-type SessionHandle user@host# set resolver-name /realms/sessionHandle/A1 user@host# set value-type SessionHandle
    3. Configure the subscriber type:
      [edit shared gw-3gpp]user@host# edit configuration subscriber-types session-handle [edit shared gw-3gpp group 3gpp-gw-share configuration subscriber-types session-handle]user@host# set subscriber-id-type session-handle

    Results

    Confirm the shared configuration properties. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.

    [edit shared gw-3gpp group 3gpp-gw-share]
    user@duke show
    configuration {
      nic-proxy-configuration {
        sessionHdl {
          resolution {
            key-type SessionHandle;
            resolver-name /realms/sessionHandle/A1;
            value-type SaeId;
          }
        }
      }
      subscriber-types {
        session-handle {
          nic-proxy sessionHdl;
          subscriber-id-type session-handle;
        }
      }
    }
    
    [edit shared gw-3gpp group 3gpp-gw-share]
    user@duke#
    

    Adding the PCRF as a Diameter Peer

    Step-by-Step Procedure

    You must specify the PCRF as a Diameter peer. This example uses a single PCRF, which connects to the C Series Controller over the SRC 3GPP gateway Gx interface using the Diameter application.

    1. To add the PCRF as a Diameter peer:
      [edit shared network diameter peer] user@host# edit primary-pcrf [edit shared network diameter peer primary-pcrf] user@host# set address [ 10.10.10.5 ] user@host# set origin-host cabe user@host# set port 3868 user@host# set protocol tcp

    Results

    From configuration mode, confirm the configuration for the PCRFs. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.

    [edit shared network diameter peer primary-pcrf]
    user@duke# show
    address [ 10.10.10.5 ];
    connect-timeout 10;
    origin-host cabe;
    port 3868;
    protocol tcp;
    
    [edit shared network diameter peer primary-pcrf]
    user@duke#
    

    Add the MX Series Router as a Shared Network Device.

    Step-by-Step Procedure

    Add the MX Series router as a shared network device using the Junos OS device driver.

    1. Add the MX Series router as a shared network device.
      [edit shared network device mx1]user@host# set management-address 10.10.10.1 user@host# set device-type junos user@host# set virtual-router * sae-connection 10.10.10.2user@host# commit
    2. Configure the SAE to manage the MX Series router.
      [edit shared network device mx1]user@host# topuser@host# edit shared sae configuration driver junos user@host# set beep-server-port 3333 user@host# set tls-beep-server-port 3434 user@host# set sdx-group-name sdx user@host# set sdx-session-group-name sdx-sessions user@host# commit

    Results

    [edit shared network device mx1]
    user@duke# show
    device-type junos;
    management-address 10.10.10.1;
    virtual-router * {
      sae-connection 10.10.10.2;
    }
    
    [edit shared network device mx1]
    user@duke#
    
    [edit shared sae configuration driver junos]
    user@host# show
    beep-server-port 3333;
    tls-beep-server-port 3434;
    connection-attempts 50;
    keepalive-interval 45;
    message-timeout 30000;
    batch-size 10;
    transaction-batch-time 2000;
    sdx-group-name sdx;
    sdx-session-group-name sdx-sessions;
    send-commit-check true;
    
    [edit shared sae configuration driver junos]
    user@duke#
    

    Configuring the SRC 3GPP Gateway as an External Plug-In for the SAE

    Step-by-Step Procedure

    1. Configure the SRC 3GPP gateway as an external plug-in for the SAE.
      user@host# edit shared sae configuration plug-ins name 3gppgw-test external user@host# set corba-object-reference file:///opt/UMC/3gpp/var/run/3gpp-gw.ior user@host# set attributes service-session-name user@host# commit

    Results

    [edit shared sae configuration plug-ins name 3gppgw-test external]
    user@duke# show
    attributes service-session-name;
    corba-object-reference file:///opt/UMC/3gpp/var/run/3gpp-gw.ior;
    
    [edit shared sae configuration plug-ins name 3gppgw-test external]
    user@duke#
    

    Published: 2014-06-12