DHCP-based Enhanced Wireless Access Gateway Configuration

This chapter provides information on configuring the DHCP-based Enhanced Wireless Access Gateway (D-eWAG) solution.

The following topics are covered in this chapter:

Before You Begin

Before you can configure the D-eWAG service:

  1. Confirm that the chassis on which the D-eWAG software will be configured has been set up as described in the System Administration Guide.
  2. Confirm that the eWAG license is installed.
    The eWAG is a licensed Cisco product. Separate session and feature licenses may be required. Contact your Cisco account representative for information on licensing requirements.
    For information on installing and verifying licenses, refer to the Managing License Keys section of the Software Management Operations chapter in the System Administration Guide.

D-eWAG Configuration

This section describes how to configure the D-eWAG service.

  1. Create and configure the D-eWAG service as described in the Creating and Configuring the D-eWAG Service section.

    IMPORTANT:

    From configuration perspective, note that the D-eWAG service is the IPSG service configured in D-eWAG mode. There is no separate D-eWAG configuration mode.

  2. Create and configure a DHCP service for D-eWAG as described in the Configuring DHCP Service section.
  3. Create/configure subscriber template for D-eWAG as described in the Configuring the Subscriber Template section.
  4. Create and configure an SGTP service for D-eWAG as described in the Configuring the SGTP Service section.
  5. Save your configuration to the 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, refer to the System Administration Guide and the Command Line Interface Reference.

IMPORTANT:

Commands used in the configuration examples in this section provide base functionality to the extent that the most common or likely commands and/or keyword options are presented. In many cases, other optional commands and/or keyword options are available. Refer to the Command Line Interface Reference for complete information regarding all commands.

Creating and Configuring the D-eWAG Service

This section describes how to create and configure the D-eWAG service.

Creating the D-eWAG Service

To create the D-eWAG service use the following configuration:

configure
   context <context_name> [ -noconfirm ]
      ipsg-service <ewag_service_name> mode radius-server
ewag [ -noconfirm ]
      end

Notes:

  • The ewag keyword enables the D-eWAG service (IPSG service in D-eWAG mode), and enters the IPSG RADIUS Server Configuration Mode, which is common for the eWAG and IPSG services.
  • You can configure a maximum of 64 eWAG/IPSG services in the system, one per context. Only one IPSG service must be configured per context. Multiple eWAG services must not be configured in the same context as they will not be able to differentiate between uplink and downlink packets.

Configuring the D-eWAG Service

This section describes how to configure the D-eWAG service.

configure
   context <context_name>
      ipsg-service <D-eWAG_service_name> mode radius-server ewag
#To bind the
D-eWAG service to a logical AAA interface and specify the number
of allowed subscriber sessions:
bind authentication-proxy
address <ip_address> [ acct-port <port_number> | auth-port <port_number> | source-context <source_context> | max-subscribers <max_sessions> ]
#To configure
the list of W-APN names that can be connected through D-eWAG and
the default-gateway IP addresses to be used by UE for connecting
to the W-APN network:
w-apn <apn_name> default-gw <ip_address>/<maskbits> +
#To associate
an SGTP service:
         associate
sgtp-service <sgtp_service_name> [ context <sgtp_context_name> ]
#To bind the
D-eWAG service to a logical AAA interface and configure the number
of subscriber sessions allowed:
         bind
address   <ipv4/ipv6_address> [ max-subscribers <max_sessions> | port <port_number> | source-context <source_context_name> ]
#To configure
location-specific mobile network identifiers:
         plmn
id mcc <mcc_number> mnc <mnc_number>
#To enable
subscriber template profile for D-eWAG:
         profile subscriber
#To configure
QoS DSCP parameters:
         ip { gnp-qos-dscp | qos-dscp } qci { { { 1 | 2 | 3 | 4 | 9 } | { 5 | 6 | 7 | 8 } allocation-retention-priority { 1 | 2 | 3 } } { af11 | af12 | af13 | af21 | af22 | af23 | af31 | af32 | af33 | af41 | af42 | af43 | be | ef | pt } } +
#To configure
RADIUS dictionary:
         radius
dictionary <dictionary_name>
#To configure
RADIUS accounting parameters:
         radius
accounting { client { <ipv4/ipv6_address> | <ipv4/ipv6_address/mask> } [ encrypted ] key <key> [ acct-onoff [ aaa-context <aaa_context_name> ] [ aaa-group <aaa_server_group_name> ] [ clear-sessions ] + ] [ dictionary <dictionary_name> ] [ disconnect-message [ dest-port <destination_port_number> ] + | interim create-new-call }
#To enable
mapping of UE MAC address to IMEIsV IE of GTP message in order to
send it to the GGSN:
         map
ue-mac-to-imei
#To configure
timeout for D-eWAG session setup attempts:
         setup-timeout <setup_timeout>
         end

Notes:

  • <dictionary_name> specifies the RADIUS dictionary to use for the D-eWAG service. For information on which dictionary to use in your setup, contact your Cisco account representative. For D-eWAG, the default dictionary is starent.
  • In the RADIUS accounting parameter configurations, the disconnect-message option enables sending RADIUS accounting messages to the configured RADIUS accounting client if the call goes down due to any failure. If this option is not configured, the D-eWAG will not send Disconnect-Message in call failure scenarios.
  • In the binding configuration, the source-context option specifies the source context where RADIUS accounting requests are received. This keyword should be configured if the source of the RADIUS requests is in a different context than the D-eWAG service. If not configured, the system will default to the context in which the D-eWAG service is configured.
  • The map ue-mac-to-imei CLI command supports enabling/disabling UE MAC to IMEI mapping. When enabled, the UE MAC received in “Calling-Station-Id” RADIUS attribute is mapped to IMEIsV and sent in GTP CPC message towards the GGSN.
  • A maximum of four W-APN can be configured per D-eWAG service. Also, note that a maximum of four default gateways can be configured per W-APN.

Configuring DHCP Service

This section describes how to configure a DHCP service for the D-eWAG service.

To create and configure the DHCP service for D-eWAG use the following configuration:

configure
   context <context_name>
      dhcp-service <dhcp_service_name> [ -noconfirm ]
#To configure
DHCP servers with which the DHCP service is to communicate:
         dhcp
server <ipv4_address> [ priority <priority> ]
#To bind the
DHCP service to a logical IP interface facilitating the system's
connection to the DHCP server:
         bind
address <ipv4_address>
         exit

Notes:

  • The DHCP service must be configured in the same context as the D-eWAG service, and must use the same IP address as used for the D-eWAG service bind.

Configuring the Subscriber Template

This section describes how to configure subscriber profile for the D-eWAG service. The D-eWAG uses this configuration to specify certain attributes in the subscriber profile.

To configure a subscriber template for D-eWAG use the following configuration:

configure
   context <context_name>
      subscriber { default | name <user_name> }
#To configure
the accounting mode:
         accounting-mode gtpp
#To configure
the default APN to be used for UE connections when the AAA server
does not return the subscriber APN name in the service-selection
AVP in RADIUS Access-Accept message:
         w-apn <wapn_name>
         exit
#To configure
realm part for subscriber. This command must be configured in the
same context where the AAA Group is defined.
      domain <domain_name>
      end

Configuring the SGTP Service

To create and configure the SGTP service use the following configuration:

configure
   context <context_name>
      sgtp-service <sgtp_service_name>
#To configure
GTP-C parameters:
         gtpc { bind
address <ipv4_address> | dns-sgsn
context  <context_name> | echo-interval
 <echo_interval_seconds> | echo-retransmission { exponential-backoff [ [ min-timeout <min_retrans_timeout_seconds> ] [ smooth-factor <smooth_factor> ] + ] | timeout <retrans_timeout_seconds> } | guard-interval <guard_interval_seconds> | ignore response-port-validation | ip
qos-dscp { af11 | af12 | af13 | af21 | af22 | af23 | af31 | af32 | af33 | af41 | af42 | af43 | be | ef } | max-retransmissions <max_retransmissions> | retransmission-timeout <retrans_timeout_seconds> | send { common
flags | rab-context | target-identification-preamble } }
#To configure
GTP-U parameters:
         gtpu { bind
address <ipv4_address> | echo-interval <echo_interval_seconds> | echo-retransmission { exponential-backoff [ [ min-timeout <min_retrans_timeout_seconds> ] [ smooth-factor <smooth_factor> ] + ] | timeout <retrans_timeout_seconds> } | max-retransmissions <max_retransmissions> | retransmission-timeout <retrans_timeout_seconds> }
#To configure
path failure detection policy:
         path-failure
detection-policy gtp { echo | non-echo } +
#To configure
the restart counter change window to avoid service deactivations
and activations that could cause large bursts of network traffic
if the restart counter change messages from the GGSN are erroneous:
         max-remote-restart-counter-change <variance>
         end

Notes:

  • The SGTP service must be associated in the D-eWAG service configuration.

Configuring NAT for Local Traffic Breakout Support

To configure NAT for Local Traffic Breakout support, use the following sample configuration:

configure
   active-charging
service ecs_service_name
      fw-and-nat firewall_nat_policy_name
         nat
policy ipv4-only default-nat-realm nat_pool_default
            access-rule
priority 10 access-ruledef ruledef_1 permit
nat-realm nat_pool_1
            access-rule
priority 15 access-ruledef ruledef_2 permit
nat-realm nat_pool_2
            access-rule
priority 100 access-ruledef ruledef_3 permit
nat-realm nat_pool_1
            access-rule
priority 105 access-ruledef ruledef_4 permit
            access-rule
priority 115 access-ruledef ruledef_5 permit
bypass-nat
            access-rule
no-ruledef-matches uplink action permit nat-realm nat_pool_3
            access-rule
no-ruledef-matches downlink action permit
            end

Notes:

  • NAT is applied only on packets in the uplink direction.
  • The Firewall-and-NAT policy can either be specified in the ECS rulebase, which can in turn be specified in the Subscriber Template, or the policy can be specified directly in the Subscriber Template. Note that the Subscriber configuration has higher priority than the ECS rulebase configuration. Therefore, if Firewall-and-NAT policies are configured both in the Subscriber Template and in the ECS rulebase, the policy specified in the Subscriber Template will be applied for the subscriber.
  • A maximum of three realms can be configured in a Firewall-and-NAT policy. In the above sample configuration nat_pool_1, nat_pool_2, nat_pool_3, and nat_pool_default are the realm names.
  • In the above sample configuration:
    • NAT realm nat_pool_1 will be used for all packets matching the ruledef ruledef_1.
    • NAT realm nat_pool_2 would be used for all packets matching the ruledef ruledef_2.
    • NAT realm nat_pool_1 would be used for all packets matching the ruledef ruledef_3.
    • NAT realm nat_pool_default would be used for all the packets matching the ruledef ruledef_4.
    • NAT will be bypassed for all the packets matching the ruledef ruledef_5.
    • In case there are no rules matching a packet, then the NAT realm to be used for the flow is taken from the following configuration:
      access-rule no-ruledef-matches uplink action permit nat-realm nat_pool_3
      That is, if no ruledef matches the packet, NAT realm nat_pool_3 will be used for those packets. If there was no realm name configured as part of matching ruledef, and default-nat-realm is not configured, then NAT will be bypassed.

Additional Configurations

This section covers the following configurations:

Configuring Bulk Statistics

To configure bulk statistics collection for D-eWAG service, use the following configuration:

configure
   bulkstats mode
      ipsg
schema <schema_name> format <schema_format>
      end

Notes:

  • For detailed information on D-eWAG-related bulk statistics available in the IPSG schema, refer to the IPSG Schema chapter of the Statistics and Counters Reference, and for those available in the System schema, refer to the System Schema chapter of the Statistics and Counters Reference.
  • Apart from the IPSG and System schema, as needed you can also configure variables available in the other schema, including:
    • APN: For Access Point Name (APN) related statistics
    • Card: For card-level statistics
    • Context: For context service related statistics
    • Port: For port-level statistics
    • RADIUS: For per-RADIUS server statistics
  • The following is a sample schema format for D-eWAG statistics:
    “D-eWAG Schema: Test\n ----------------------\nVPN Name:%vpnname%,\nService Name:%servname%,\n Session Statistics: \n Total Current Sessions :%total_current_sessions%,\n Total Sessions Setup: %total_sessions_setup%,\n ----------------------\n”

Configuring Congestion Control

IMPORTANT:

In this release the Congestion Control Support feature is not qualified, it is available only for lab / testing purposes.

To enable Congestion Control, use the following configuration:

configure
#To enable
Congestion Control:
   congestion-control
#To configure
Congestion Control policy:
   congestion-control
policy ipsg-service action { drop | none }
#To configure
Congestion Control thresholds:
   congestion-control
threshold { { license-utilization | max-sessions-per-service-utilization | message-queue-utilization | port-rx-utilization | port-specific { <slot/port> | all { rx-utilization | tx-utilization } } | port-specific-rx-utilization | port-specific-tx-utilization | port-tx-utilization | service-control-cpu-utilization | system-cpu-utilization | system-memory-utilization | tolerance } [ critical ] <percentage> | message-queue-wait-time [ critical ] <seconds> | { port-specific-rx-utilization | port-specific-tx-utilization } [ critical ] }
   end

Notes:

  • Congestion policies are configurable for each service. These policies dictate how the services respond when the system detects that a congestion condition threshold has been crossed. For more information on the Congestion Control feature, refer to the Congestion Control chapter of the System Administration Guide.
  • In the above configuration, the Congestion Control thresholds featured are at the system level and are not specific to D-eWAG.
  • eWAG supports only critical threshold values.

Verifying your Configuration

To verify your Congestion Control configuration, in the Exec Mode issue the following command:

show congestion-control configuration

The output of this command displays information including whether or not Congestion Control is enabled/disabled, Congestion Control threshold parameter settings, Congestion Control policy, and more.

Configuring Session Recovery

To enable Session Recovery, use the following configuration:

configure
   require
session recovery
   end

Notes:

  • For more information on the Session Recovery feature, refer to the Session Recovery chapter of the System Administration Guide.
  • A valid feature key is required for this configuration. This command enables/disables the feature to try to perform hitless session recovery for all session types supported by the software release. After enabling session recovery through this configuration, make sure that session recovery status is “ready”.

Configuring Offline Charging for D-eWAG

To configure Offline Charging for D-eWAG, use the following configuration:

configure
   gtpp
single-source
   context <context_name>
#To configure
GTPP Group:
      gtpp
group <gttp_group_name>
#To
configure charging agent:
         gtpp
charging-agent address <server_ip_address>
#To
configure GTPP dictionary:
         gtpp
dictionary <gtpp_dictionary>
#To
configure remote server address:
         gtpp
server <ip_address>
#To configure
triggers:
         gtpp
trigger volume-limit
#To configure
CDR attributes:
         gtpp
attribute local-record-sequence-number
         gtpp
attribute msisdn
         gtpp
attribute rat
         exit
#To configure
accounting policy:
      policy
accounting <accounting_policy>
         cc
profile <profile_bit_value> volume total <no_of_octets>
         exit
#To configure
accounting in IPSG service configuration:
      ipsg-service <service_name> mode radius-server ewag
         accounting-context <ewag_accounting_context_name>
         associate
accounting-policy <accounting_policy_name>
         exit
#To configure
accounting mode in the Subscriber configuration:
      subscriber default
         accounting-mode gtpp
         end

Notes:

  • For information on the GTPP dictionary to use contact your Cisco account representative.

D-eWAG Administration

This section describes D-eWAG administrative procedures.

This section includes the following topics:

Logging Support

To view IPSG-related logs, in the Exec Mode use the following command:

logging filter active
facility { ipsg | ipsgmgr } level <severity_level> [ critical-info | no-critical-info ]

To view SGTP-related logs, in the Exec Mode use the following command:

logging filter active
facility { sgsn-gtpc | sgsn-gtpu | sgtpcmgr } level <severity_level> [ critical-info | no-critical-info ]

To view SessMgr-related logs, in the Exec Mode use the following command.

logging filter active
facility sessmgr level <severity_level> [ critical-info | no-critical-info ]

To view ECS and NAT related logs for Local traffic Breakout support, in the Exec Mode use the following command.

logging filter active
facility { acl-log | acsmgr | ecs-css | firewall } level <severity_level> [ critical-info | no-critical-info ]

Protocol Monitoring Support

The system provides protocol monitor and test utilities that can are useful when troubleshooting or verifying configurations. The information generated by these utilities can in many cases either identify the root cause of a software or network configuration issue or, at the very least, greatly reduce the number of possibilities.

For troubleshooting purposes, the system provides a powerful protocol monitoring utility. This tool can be used to display protocol information for a particular subscriber session or for every session being processed.

For more information on Monitor Protocol and Monitor Subscriber, refer to the System Administration Guide.

Monitor Protocol

The system’s protocol monitor displays information for every session that is currently being processed. Depending on the number of protocols monitored, and the number of sessions in progress, a significant amount of data is generated. It is highly recommended that logging be enabled on your terminal client in order to capture all of the information that is generated.

To view monitor protocol based logging information, in the Exec Mode use the following command:

monitor protocol

For D-eWAG use the following filters:

  • 12 — RADIUS Authentication
  • 13 — RADIUS Accounting
  • 19 — User L3
  • 20 — USERTCP STACK
  • 24 — GTPC
  • 26 — GTPU
  • 27 — GTPP
  • 28 — DHCP
  • 29 — CDR
  • 31 — RADIUS COA
  • 34 — CSS Data: In case of Local Traffic Breakout support, shows data packets after NAT is done.
  • 41 — IPSG RADIUS Signal: Must be used to view the RADIUS accounting messages on the control path for IPSG session management.
  • 70 — DNS Client

Monitor Subscriber

The system’s protocol monitor can be used to display information for a specific subscriber session that is currently being processed. Depending on the number of protocols monitored, and the number of sessions in progress, a significant amount of data is generated. It is highly recommended that logging be enabled on your terminal client in order to capture all of the information that is generated.

To view monitor subscriber based logging information, in the Exec Mode use the following command:

monitor subscriber

The following filters are available for monitor subscriber based logging in D-eWAG.

Monitor Subscriber for full call flow can be checked with the options next-call, type, and username. Other options like IMSI, MSISDN, and MSID are not applicable for calls as they are not known to D-eWAG at the initial stage of authentication (D-eWAG gets this information only after receiving Access-Accept from the AAA server.

Gathering D-eWAG-related Statistics and Information


Table 1. D-eWAG-related Statistics and Information
D-eWAG-related statistics or information CLI command to use

To view concise D-eWAG service-level information.

show ipsg service all

To view detailed D-eWAG service-level information.

show ipsg service all verbose

To view D-eWAG service-level statistics, including session and RADIUS message-level statistics.

show ipsg statistic

To view D-eWAG session counter information.

show ipsg sessions counters

To view D-eWAG subscriber information.

show subscribers ipsg-only

To view detailed D-eWAG session information, for all sessions.

show ipsg sessions full all

To view detailed subscriber information, for all subscribers.

show subscribers full all

To view session progress information for in-progress calls.

show session progress

To view IPSG Manager related information.

show session subsystem facility ipsgmgr

To view APN-related information.

show apn name <apn_name>

To view SNMP trap history.

show snmp trap history | grep IPSG

To view SNMP trap statistics, for all services including D-eWAG and SGTP.

show snmp trap statistics

To view IPSG facility information.

logging filter active facility ipsg

To view IPSG Manager facility information.

logging filter active facility ipsgmgr

To view information of logging filters for current context.

show logging

To view DHCP related information.

show dhcp

To view DHCP service related information.

show dhcp statistics dhcp-service <dhcp_service>

To view counters associated with DHCP.

show dhcp counters all

To view all available DHCP related information.

show dhcp full all

To view status of DHCP servers.

show dhcp status

To view summary of DHCP related statistics.

show dhcp summary all

To view DHCP related information for specified IMSI.

show dhcp imsi <imsi>

To view thresholding related information.

show threshold

To view alarm related information.

show alarm all

To view SNMP event statistics.

show snmp trap statistics

To view counters for configured RADIUS servers.

show radius counters all

For Local Traffic Breakout support. To view ECS Stateful Firewall statistics.

show active-charging firewall statistics { acsmgr instance <instance_number> | callid <call_id> | domain-name <domain_name>| protocol <protocol>| nat-realm <realm_name> | username <user_name>} [ debug-info | verbose ]

For Local Traffic Breakout support. To view session information for sessions with NAT required or not required.

show active-charging sessions nat { required [ nat-realm <realm_name> ] | not-required }

For Local Traffic Breakout support. To view information for subscribes with NAT enabled or disabled.

show subscribers nat { required [ nat-realm <realm_name> ] [ nat-ip <ip_address> ] | not-required }

For Local Traffic Breakout support. To view ALG statistics.

show active-charging analyzer statistics name <analyzer_name>

To view GTPP statistics.

show gtpp statistics