Configuring the SaMOG Gateway

This chapter provides configuration instructions for the SaMOG (S2a Mobility Over GTP) Gateway. Information about the commands in this chapter can be found in the Command Line Interface Reference.

Configuring the System to Perform as a SaMOG Gateway

This section provides a high-level series of steps and the associated configuration file examples for configuring the system to perform as a SaMOG Gateway in a test environment. For a configuration example without instructions, see the Sample SaMOG Gateway Configuration File section in this guide.

Required Information

The following sections describe the minimum amount of information required to configure and make the SaMOG Gateway operational in the network. To make the process more efficient, it is recommended that this information be available prior to configuring the system.

The following table lists the information that is required to configure the SaMOG Gateway context and service.


Table 1. Required Information for SaMOG Configuration
Required Information Description

SaMOG Context and MRME, CGW and SaMOG Service Configuration

SaMOG context name

The name of the SaMOG context, which can be from 1 to 79 alpha and/or numeric characters.

MRME service name

The name of the MRME service, which can be from 1 to 63 alpha and/or numeric characters.

IPv4 address

The IP address to which you want to bind the MRME service.

context DNS

The name of the context to use for PGW DNS.

IPV4_address/subnetmask

The IPv4 address and subnetmask for the destination RADIUS client the MRME service will use.

Key

The name of the encrypted key for use by the destination RADIUS server.

Port Number

The port number for RADIUS disconnect messages.

IPv4 address

The IPv4 address of the RADIUS client

Key

The encrypted key name for use by the RADIUS client.

Port

The port number used by the RADIUS client.

CGW service name

The name of the CGW service, which can be from 1 to 63 alpha and/or numeric characters.

IPv4 address

The IPv4 address to which the CGW service will bind.

Egress EGTP service name

The name of the egress EGTP service that the CGW service will use. This name must match the name of the EGTP service configured later in this procedure.

Timeout

The session delete delay timeout setting for use by CGW service.

SaMOG service name

The name of the SaMOG service, which can be from 1 to 63 alpha and/or numeric characters.

MRME service name

The name of the MRME service to associate with this SaMOG service. This is the MRME service name configured previously in this procedure.

CGW service name

The name of the CGW service to associate with this SaMOG service. This is the CGW service name configured previously in this procedure.

Subscriber map name

The subscriber map name to associate with the SaMOG service. This name must match the subscriber map name configured later in this procedure.

LTE Policy Configuration

Subscriber map name

The name of the subscriber map to associate with the LTE policy, which can be from which can be from 1 to 64 alpha and/or numeric characters.

Precedence priority

Specifies the prcedence for the subscriber map. Must be an integer from 1 to 1024.

Service criteria type

Specifies the service criteria that must be matched for the subscriber map. Must be one of imsi, service-plmnid or all.

MCC number

The Mobile Country Code for use in this LTE policy.

MNC

The Mobile Network code for use in this LTE policy.

Operator policy name

The name of the operator policy use with the subscriber map, which can be from 1 to 64 alpha and/or numeric characters.

TAI mgmt db name

The name of the Tracking Area Identifier database for use with the LTE policy, which can be from 1 to 64 alpha and/or numeric characters.

GTPU and EGTP Service Configuration

SaMOG context name

The name of the SaMOG context configured previously.

EGTP service name

The name for this EGTP service, which can be from 1 to 63 alpha and/or numeric characters.

EGTP service name

The name of the EGTP service name that you want to associate with the GTPU service. This is the EGTP service name configured previously.

IPv4 address

The IPv4 address to which you want to use to bind the EGTP service to the GTPU service.

GTPU service name

The name of the GTPU service, which can be from 1 to 63 alpha and/or numeric characters.

IPv4 address

The IP address to which the GTPU service will bind.

AAA and Diameter Endpoint Configuration

AAA context name

The name assigned to the AAA context, which can be from 1 to 79 alpha and/or numeric characters.

AAA interface name

The name assigned to the AAA interface, which can be from 1 to 79 alpha and/or numeric characters.

IPv4 address/subnetmask

The primary IPv4 address and subnetmask for use by the AAA interface.

IPv4 address subnetmask

The secondary IPv4 address and subnetmask for use by the AAA interface.

SaMOG context name

The name of the SaMOG context configured earlier.

AAA DIAMETER STa1 group name

The primary AAA group name for use over the STa interface, which can be from 1 to 63 alpha and/or numeric characters.

DIAMETER endpoint name

The DIAMETER authentication endpoint name for use with this AAA group.

AAA DIAMETER STa2 group name

The secondary AAA group name for use over the STa interface, which can be from 1 to 63 alpha and/or numeric characters.

DIAMETER endpoint name

The DIAMETER authentication endpoint name for use with the secondary AAA group.

AAA Accounting Group Name

The name of the AAA Accounting group, which can be from 1 to 63 alpha and/or numeric characters.

Diameter authentication dictionary

The name of the Diameter dictionary used for authentication. This must be configured as the aaa-custom13 dictionary.

DIAMETER endpoint name

The name of the DIAMETER endpoint, which can be from 1 to 63 alpha and/or numeric characters. This is the name of the external 3GPP AAA server.

STa endpoint name

The name of the DIAMETER endpoint, which can be from 1 to 63 alpha and/or numeric characters. This is the name of the external 3GPP AAA server.

Origin real name

Name of the local Diameter realm, which can be a a string from 1 to 127 alpha and/or numeric characters.

Origin host STa endpoint IPv4 address

The IPv4 address of the origin host STa endpoint.

IPv4 address

The IPv4 address used for the origin host STa endpoint.

Port

The port used for the origin host STa endpoint.

Peer name

The name of the Diameter peer, which can be from 1 to 63 alpha and/or numeric characters.

SaMOG realm name

The name of the peer Diameter realm, which can be from 1 to 63 alpha and/or numeric characters.

IPv4 address

The IPv4 address for the peer STa endpoint.

Port

The port used for the peer STa endpoint.

DNS Configuration

DNS context name

The name of the context in which DNS will be configured, which can be from 1 to 79 alpha and/or numeric characters.

DNS interface name

The name of the DNS interface, which can be from 1 to 79 alpha and/or numeric characters.

IPv4 address

The IPv4 address of the DNS server.

IP name server IP address

The IP name server IPv4 address.

DNS client

The name of the DNS client, which can be from 1 to 63 alpha and/or numeric characters.

IPv4 address

The IPv4 address to which you want to bind the DNS client service.

Configuring and Binding the Interfaces

SaMOG service Interface port/slot

The slot and port number to which you want to bind the SaMOG service.

GTP SaMOG interface name and context

The SaMOG interface and context name that will be bound to the SaMOG interface port/slot.

STa Accounting service interface port/slot

The slot and port number to which you want to bind the STa accounting interface.

STa Accounting service name and context

The name and context name of the STa accounting interface that you want to bind to the STa accounting port/slot.

DNS service Interface slot/port

The slot and port number that to which you want to bind the DNS service.

DNS service interface name and context.

The name and context name that you want to bind to the DNS interface slot/port.

Radius PMIP-side service interface port/slot.

The slot and port number to which you want to bind the PMIP-side RADIUS interface.

Radius PMIP-side service interface name and context.

The name and context name of the PMIP side RADIUS interface you want to bind to the RADIUS interface port/slot.

Radius SaMOG-side service interface port/slot.

The slot and port number to which you want to bind the SaMOG-side RADIUS interface.

GTPU interface port/slot.

The slot and port number to which you want to bind the GTPU-interface.



SaMOG Gateway Configuration

  1. Set system configuration parameters such as activating PSC2s, ports, and enabling session recovery by following the configuration examples in the System Administration Guide.
  2. Create the SaMOG context by applying the example configuration in the Creating the SaMOG Gateway Context section.
  3. Configure the MRME, CGW, and SaMOG services by applying the example configuration in the Configuring the MRME, CGW and SaMOG Services section.
  4. Configure the LTE policy by applying the example configuration in the section Configuring the LTE Policy.
  5. Create the GTPU and EGTP services by applying the example configuration in the Configuring the GTPU and EGTP Services section.
  6. Create and configure the AAA group for Diameter and AAA authentication and accounting by applying the example configuration in the Configuring AAA section.
  7. Configure the DNS service by applying the example configuration in the Configuring DNS section.
  8. Configure and bind interfaces to the relevant interfaces by applying the example configuration in the Configuring and Binding the Interfaces section.
  9. Optional. Enable event logging by applying the example configuration in the Enabling Logging section.
  10. Optional. Enable the sending of CGW and SaMOG SNMP traps by applying the example configuration in the Enabling SNMP Traps section.
  11. Optional. Configure the system to gather and transfer bulk statistics by applying the example configuration in the Configuring Bulk Statistics section.
  12. Save the completed configuration by following the instructions in the Saving the Configuration.

Creating the SaMOG Gateway Context

Create the context in which the SaMOG service will reside. The MRME, CGW, SaMOG and other related services will be configured in this context. Create the SaMOG context by applying the configuration example below.

config
   context samog_context_name
   end

Configuring the MRME, CGW and SaMOG Services

The MRME and CGW services provide the SaMOG functionality. They must be configured in the SaMOG context and then associated with a SaMOG service name. Configure the MRME, CGW, and SaMOG services by applying the example configuration below.

      mrme-service mrme_service_name
         bind
address  ip4_address
         dns-pgw
context dns
         radius client ip4_address/subnetmask encrypted key key disconnect-message
dest-port port_no
         radius client ipv4_address encrypted key key disconnect-message
dest-port port_no
         exit
      cgw-service cgw_service_name
         bind
ipv4-address ipv4_address
         associate
egress-egtp_service egress-egtp_service_name
         revocation enable
         session-delete-delay timeout timeout_msecs
         exit
      samog-service samog_service_name
         associate mrme-service mrme_service_name
         assoicate
cgw-service cgw_service_name
         associate
subscriber-map subscriber_map_name
         exit

Configuring the LTE Policy

The LTE Policy Configure the LTE policy by applying the example configuration below.

config
   lte-policy
      subscriber-map  subscriber_map_name
         precedence precedence_priority match-criteria service_criteria_type mcc mcc_number mnc mnc_number operator-policy-name operator_policy_name
         precedence precedence_priority match-criteria service_criteria_type operator-policy-name operator_policy_name
         exit
      tai-mgmt-db tai_mgmt_db_name
      exit

Configuring the GTPU and EGTP Services

Configure the GTPU and EGTP services by applying the example configuration below.

config
   context samog_context_name
      egtp-service egtp_service_name
      associate
gtpu-service egtp_service_name
      gtpc
bind ipv4-address ipv4_address
      exit
   gtpu-service gtpu_service_name
      bind
ipv4-address ipv4_address
      exit

Configuring AAA

Create the AAA group for DIAMETER authentication and then configure AAA accounting and authentication by applying the example configuration below.

config
   contextaaa_context_name
      interface aaa_interface_name
         ip address ipv4_address/subnetmask
         ip address ipv4_address/subnetmask secondary
         end
config
   context samog_context_name
      aaa
group aaa_diameterSTa1_group_name
         diameter
authentication dictionary aaa-custom13
         diameter
authentication endpoint endpoint_name
         exit
      aaa group aaa_group_diameter_STa2_name
         diameter
authentication dictionary aaa-custom13
         diameter
authentication endpoint  endpoint_name
         exit
      aaa group aaa_acct_group_name
         radius
attribute nas-ip-address address ipv4-address
         radius
accounting server ipv4_address encrypted key key port port_no
         exit
      aaa
group default
      exit
   gtpp
group default
   exit
diameter endpoint STA_endpoint_name
   origin realm realm_name
   use-proxy
   origin
host STa_endpoint_ipv4_address address ipv4_address port port_no
   no
watchdog-timeout
   peer peer_name realm samog_realm_name address ipv4_address port port_no
   exit

Configuring DNS

Configure DNS for the SaMOG gateway by applying the example configuration below.

config
   context dns_context_name
      interface dns_interface_name
         ip address ipv4_address/subnetmask
         exit
      subscriber default
      exit
   aaa
group default
   exit
   gtpp
group default
   ip
domain-lookup
   ip
name-servers ipv4-address
   dns-client dns_client_name
      bind
address ipv4_address
   exit

Configuring and Binding the Interfaces

The interfaces created previously now must be bound to physical ports. Bind the system interfaces by applying the example configuration below.

config
   port
ethernet slot
no/port no
      no shutdown
      bind
interface gtp_samog_interface_name gtp_samog_context name
      exit
   port
ethernet slot
no/port no
      bind
interface interface STa_acct_interface_name STa_acct_context_name
      exit
   port
ethernet slot
no/port no
      bind
interface
dns_interface_name dns_context name
      exit
   port
ethernet slot
no/port no
      bind
interface
wlc_pmip_side_interface_name wlc_pmip_side_context_name
      exit
   port
ethernet slot
no/port no
      bind
interface
wlc_side_samog_interface_name wlc_side_samog_context
name
   port
ethernet slot
no/port no
      bind
interface
gtpu_interface_name gtpu/gtpc_context name
      end

Enabling Logging

Optional. Enable event logging for the SaMOG Gateway by applying the example configuration below from the Command Line Interface Exec Mode.

[local]asr5000# logging filter active
facility mrme level error_reporting_level
[local]asr5000# logging filter active
facility cgw level error_reporting_level
[local]asr5000# logging filter active
facility ipsgmgr level error_reporting_level
[local]asr5000# logging filter active
facility radius-coa level error_reporting_level
[local]asr5000# logging filter active
facility radius-auth level error_reporting_level
[local]asr5000# logging filter active
facility radius-acct level error_reporting_level
[local]asr5000# logging filter active
facility diabase level error_reporting_level
[local]asr5000# logging filter active
facility diameter-auth level error_reporting_level
[local]asr5000# logging filter active
facility aaamgr level error_reporting_level
[local]asr5000# logging filter active
facility aaa-client level error_reporting_level
[local]asr5000# logging filter active
facility diameter level error_reporting_level
[local]asr5000# logging filter active
facility mobile-ipv6 level error_reporting_level
[local]asr5000# logging filter active
facility hamgr level  error_reporting_level
[local]asr5000# logging filter active
facility ham diameter-ecs level  error_reporting_level
[local]asr5000# logging filter active
facility egtpc level error_reporting_level
[local]asr5000# logging filter active
facility egtpmgr level error_reporting_level

Enabling SNMP Traps

Optional. Enable the sending of SaMOG gateway-related SNMP traps by applying the example configuration below.

config
   context samog_context_name
      snmp
trap enable SaMOGServiceStart
      snmp
trap enable SaMOGServiceStop
      snmp
trap enable CGWServiceStart
      snmp
trap enable CGWServiceStop
      end

To disable the generation of an SNMP trap:

config
   contextsamog_context_name
      snmp
trap suppress trap_name
      end

Configuring Bulk Statistics

Use the following configuration example to enable SaMOG bulk statistics:

config
   bulkstats collection
   bulkstats mode
      sample-interval minutes
      transfer-interval minutes
      file no
         remotefile format format /localdisk/bulkstats/bulkstat%date%%time%.txt
         receiver ipv4_or_ipv6_address primary mechanism sftp login login_name encrypted password samog schema schema_name format schema_format

Notes:

  • The bulkstats collection command in this example enables bulk statistics, and the system begins collecting pre-defined bulk statistical information.
  • The bulkstats mode command enters Bulk Statistics Configuration Mode, where you define the statistics to collect.
  • The sample-interval command specifies the time interval, in minutes, to collect the defined statistics. The minutes value can be in the range of 1 to 1440 minutes. The default value is 15 minutes.
  • The transfer-interval command specifies the time interval, in minutes, to transfer the collected statistics to the receiver (the collection server). The minutes value can be in the range of 1 to 999999 minutes. The default value is 480 minutes.
  • The file command specifies a file in which to collect the bulk statistics. A bulk statistics file is used to group bulk statistics schema, delivery options, and receiver configuration. The number can be in the range of 1 to 4.
  • The receiver command in this example specifies a primary and secondary collection server, the transfer mechanism (in this example, ftp), and a login name and password.
  • The samog schema command specifies that the SaMOG schema is used to gather statistics. The schema_name is an arbitrary name (in the range of 1 to 31 characters) to use as a label for the collected statistics defined by the format option. The format option defines within quotation marks the list of variables in the SaMOG schema to collect. The format string can be in the range of 1 to 3599.

For descriptions of the SaMOG schema variables, see “SaMOG Schema Statistics” in the Statistics and Counters Reference. For more information on configuring bulk statistics, see the System Administration Guide.

Saving the Configuration

Save the SaMOG configuration file to flash memory, an external memory device, and/or a network location using the Exec mode command save configuration.

For additional information on how to verify and save configuration files, see the System Administration Guide and the Command Line Interface Reference.