Download Print this page

Advertisement

Cisco ASR 5000 Series Mobility
Management Entity Administration Guide
Version 10.0
Last Updated June 30, 2010
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
Text Part Number: OL-22987-01

Advertisement

   Related Manuals for Cisco ASR 5000 Series

   Summary of Contents for Cisco ASR 5000 Series

  • Page 1

    Cisco ASR 5000 Series Mobility Management Entity Administration Guide Version 10.0 Last Updated June 30, 2010 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 Text Part Number: OL-22987-01...

  • Page 2

    ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks.

  • Page 3: Table Of Contents

    NAS Signalling Security ..........................33 Features and Functionality - Licensed Enhanced Feature Software ............... 34 Session Recovery Support ..........................34 License ................................35 IPv6 Support ..............................35 License ................................36 Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 4

    Verifying MME-HSS Service Configuration ....................75 Event IDs for MME Service........................... 77 Verifying and Saving Your Configuration ............79 Verifying the Configuration ........................... 80 Feature Configuration ............................80 Service Configuration ............................81 ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 5

    Using the DHCP Test Command ........................111 Engineering Rules................... 113 APN Engineering Rules ............................114 DHCP Service Engineering Rules ........................115 Lawful Intercept Engineering Rules ........................116 Service Engineering Rules ........................... 117 Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 7: About This Guide

    About this Guide This document pertains to features and functionality that run on and/or that are related to the Cisco® ASR 5000 Chassis, formerly the Starent Networks ST40. Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 8: Conventions Used

    Required keywords and variables are surrounded by grouped brackets. Required keywords and variables are those components that are required to be entered as part of the variable } command syntax. ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01 viii...

  • Page 9

    Pipe filters can be used in conjunction with required or optional keywords or variables. For example: { nonce | timestamp } [ count number_of_packets | size number_of_bytes ] Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 10: Contacting Customer Support

    Use the information in this section to contact customer support. For New Customers: Refer to the support area of http://www.cisco.com for up-to-date product documentation or to submit a service request. A valid username and password is required to this site. Please contact your local sales or service representative for additional information.

  • Page 11: Mme In Lte/sae Wireless Data Services

    Chapter 1 MME in LTE/SAE Wireless Data Services The Cisco® ASR 5000 chassis provides LTE/SAE wireless carriers with a flexible solution that functions as a Mobility Management Entity (MME) in 3GPP Long-Term Evolution/System Architecture Evolution wireless data networks. This overview provides general information about the MME including:...

  • Page 12: Product Description

    LTE and 2G/3G access networks with the S3 interface terminating at the MME from the SGSN. The MME also terminates the S6a interface towards the home HSS for roaming UEs. ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 13

    Warning message transfer function (including selection of appropriate eNodeB) UE Reachability procedures Interfaces with MSC for Voice paging Interfaces with Gn/Gp SGSN for interconnecting to legacy network MAP based Gr interface to legacy HLR Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 14

    MME in LTE/SAE Wireless Data Services ▀ Product Description MPORTANT Some of the features may not be available in this release. Kindly contact your local Cisco representative for more information on supported features. ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide...

  • Page 15: Product Specification

    Packet Services Cards (PSC/PSC2): Within the ASR 5000 platform, PSCs/PSC2s provide high-speed, multi- threaded EPS Bearer context processing capabilities for MME services. Up to 14 PSCs/PSC2s can be installed, allowing for multiple active and/or redundant cards. Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 16: Operating System Requirements

    LTE/SAE services is located in the Hardware Platform Overview chapter of the Product Overview Guide. Operating System Requirements The MME is available for ASR 5000 platforms running StarOS™ Release 9.0 or later. ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 17: Network Deployment And Interfaces

    Figure 2. The MME in LTE/SAE Networks and Interfaces Supported Interfaces In support of both mobile and network originated subscriber UE contexts, the system MME provides the following network interfaces: Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 18

    Gr Interface: This is the interface used by the MME to communicate with the Home Location Register (HLR) via a eGTP-to-MAP (Mobile Application Part) protocol convertor. This interface is used for network initiated UE contexts. ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 19

    Note: This interface will be supported in furture release. MPORTANT MME Software also supports additional interfaces. For more information on additional interfaces, refer Features and Functionality - Licensed Enhanced Feature Software section. Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 20: Features And Functionality - Base Software

    3GPP TS 36.413 V8.4.0 (2008-12): 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) (Release 8) IETF RFC 4960, Stream Control Transmission Protocol, December 2007 ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 21: Nas Protocol Support

    This feature is used to provide the subscriber session management for bearer context activation, deactivation, modification, and update procedures. EPS GTPv2 Support on S11 Interface Support for the EPS GTPv2 on S11 interface in accordance with the following standards: Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 22: Subscriber Level Session Trace

    UE connects to the access network. As a complement to Cisco's protocol monitoring function, the MME supports 3GPP standards based session level trace capabilities to monitor all call control events on the respective monitored interfaces including S6a, S1-MME and S11.

  • Page 23: Session And Quality Of Service Management

    This support provides a foundation for contributing towards improved Quality of User Experience (QoE) by enabling deterministic end-to-end forwarding and scheduling treatments for different services or classes of applications pursuant Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 24: Network Access Control Functions

    2. Key agreement: Performs key agreement by, generating the cipher key; and generating the integrity key. 3. Protection: When the AKA procedure is performed it protects, the integrity of messages; confidentiality of signalling data; and confidentiality of user data ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 25: Hss Support Over S6a Interface

    HSS server has been selected, all subsequent AAA messages for the session will be delivered to the same server. Network Entity Management This section describes following features: MME Selection Packet Data Network Gateway (P-GW) Selection Serving Gateway (S-GW) Selection Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 26: Mme Selection

    GTP. This means the S-GW selected for such subscribers may need to support both GTP and PMIP, so that it is possible to set up both local breakout and home routed sessions for these subscribers. ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 27: 3gpp R8 Identity Support

    TAI list assigned to the UE. The tracking area list assigned to different UEs moving in from the same tracking area should be different so as to avoid Tracking Area Update message overflow. Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 28: Reachability Management

    MME. However, extreme care is needed to ensure that this load re-balancing does not overload other MMEs within the pool area (or neighboring SGSNs) as this might lead to a much wider system failure. ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 29: Radio Resource Management Functions

    PDNs. Up to 11 PDNs are supported per subscriber. System Management Features This section describes following features: Management System Overview Bulk Statistics Support Threshold Crossing Alerts (TCA) Support NAS Signalling Security Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 30: Management System Overview

    Can be easily integrated with higher-level network, service, and business layer applications using the Object Management Group's (OMG‟s) Interface Definition Language (IDL) The following figure demonstrates these various element management options and how they can be utilized within the wireless carrier network. ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 31: Bulk Statistics Support

    When used in conjunction with the Web Element Manager, the data can be parsed, archived, and graphed. Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 32: Threshold Crossing Alerts (tca) Support

    Alarm: Both high and low threshold are defined for a value. An alarm condition occurs when the value reaches or exceeds the configured high threshold within the specified polling interval. The alert is generated then generated and/or sent at the end of the polling interval. ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 33: Nas Signalling Security

    The MME implements AES algorithm (128-EEA1 and 128-EEA2) for NAS signalling ciphering and SNOW 3G algorithm (128-EIA1 and 128-EIA2) for NAS signalling integrity protection. 128-EIA1= SNOW 3G 128-EIA2= AES Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 34: Features And Functionality - Licensed Enhanced Feature Software

    In this mode, recovery is performed by using the mirrored “standby-mode” session manager task(s) running on active packet processing cards. The “standby- ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 35: License

    Control and configuration of the above is specified as part of the APN configuration on the MME, e.g., IPv6 address prefix and parameters for the IPv6 router advertisements. RADIUS VSAs may be used to override the APN configuration. Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 36: License

    IPSec is supported for the new subscriber sessions. Data for existing Mobile IP sessions is unaffected. L2TP: L2TP-encapsulated packets are routed from the system to an LNS/secure gateway over an IPSec tunnel. The following figure shows IPSec configurations. ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 37: License

    In accordance with 3GPP TS 33.108 Release 8 requirements the Cisco MME supports the Lawful Intercept Access Function for intercepting control plane traffic pursuant to a court ordered subpoena. Lawful Intercept involves the process of mirroring subscriber call control or call content based on a request from a law enforcement agency to a telecom service provider.

  • Page 38: License

    CLI over SSH connections from a DF mediation server. Our solution is currently interoperable with leading third party solutions. The intercepted call control data is encoded in a Cisco proprietary message header format using an optional TLV field to pack the IRI information. The message header includes other identifying information including sequence numbers, timestamps and session &...

  • Page 39: Web Element Management System

    CORBA interfaces. The server component is fully compatible with the fault-tolerant Sun® Solaris® operating system. The following figure demonstrates these various element management options and how they can be utilized within the wireless carrier network. Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 40

    ▀ Features and Functionality - Licensed Enhanced Feature Software Figure 6. Element Management Methods MPORTANT MME management functionality is enabled by default for console-based access. For GUI- based management support, refer Web Element Management System. ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 41: How Mme Works

    Purge Procedure The purge procedure is employed by the Cisco MME to inform the concerned node that the MME has removed the EPS bearer contexts of a detached UE. This is usually invoked when the number of records exceeds the maximum capacity of the system.

  • Page 42: Paging Procedure

    MME, will initiate the process of paging the MS and establishing a EPS Bearer context. Subscriber Registration Setup Procedure The following figure and the text that follows describe the message flow for a successful user-initiated subscriber registration setup procedure. ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 43

    10. Once S-GW receives the Create Bearer Response from P-GW it reserves the EPS bearer and sends Create Bearer Response to the MME and establishes the EPS bearer with MME for this user. Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 44: User-initiated Subscriber De-registration Setup Procedure

    6. S-GW forwards the Delete Session Request to P-GW for this subscriber. 7. P-GW deletes the EPS bearer for this subscriber and sends the Delete Session Response to S-GW. ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 45: Service Request Procedure

    Prohibition of services Enforce identity check User-initiated Service Request Procedure The following figure and the text that follows describe the message flow for a successful user-initiated subscriber registration setup procedure. Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 46

    12. UE sends RB_Establishment Response to eNodeB and radio bearer established. 13. eNodeB sends initial Context Setup Request Response to MME. 14. MME sends Modify Bearer Request to S-GW. ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 47: Network-initiated Service Request Procedure

    6. Once identified UE located S-GW and eNodeB starts messaging through UE Paging response. 7. S-GW sends Stop Paging message to MME. 8. Data downlink starts between identified UE and PDN. Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 48: Supported Standards

    3GPP TS 36.413 V8.4.0 (2008-12): 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) (Release 8) IETF References RFC-768, User Datagram Protocol (UPD), August 1980 ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 49

    RFC-2002, IP Mobility Support, May 1995 RFC-2003, IP Encapsulation within IP, October 1996 RFC-2004, Minimal Encapsulation within IP, October 1996 RFC-2005, Applicability Statement for IP Mobility Support, October 1996 Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 50

    RFC-2866, RADIUS Accounting, June 2000 RFC-2867, RADIUS Accounting Modifications for Tunnel Protocol Support, June 2000 RFC-2868, RADIUS Attributes for Tunnel Protocol Support, June 2000 RFC-2869, RADIUS Extensions, June 2000 ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 51: Object Management Group (omg) Standards

    Draft, Route Optimization in Mobile IP Draft, Generalized Key Distribution Extensions for Mobile IP Draft, AAA Keys for Mobile IP Object Management Group (OMG) Standards CORBA 2.6 Specification 01-09-35, Object Management Group Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 53: Understanding The Service Operation

    Prior to connecting to the command line interface (CLI) and beginning the system's configuration, there are important things to understand about how the system supports these applications. This chapter provides terminology and background information that must be considered before attempting to configure the system. Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 54: Terminology

    Local context: This is the default context on the system used to provide out-of-band management functionality. The local context is described in the Command Line Reference. ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 55: Logical Interfaces

    Ethernet 10/100 or Ethernet 1000 Line Cards or on the four-port Quad Gig-E Line Card (QGLC). S13 Interface: This interface provides communication between MME and Equipment Identity Register (EIR). This interface is not supported in this release. Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 56: Bindings

    Services Services are configured within a context and enable certain functionality. The following services can be configured on the system: ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 57

    When the system receives a Create EPS bearer Context Request message from the eNodeB, it examines the available S-GW and P-GW that can serve APN provided from UE or HSS or Operator Policy in MME. Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 58

    For HSS-based AAA the system uses the source context for AAA. That context may be overridden by configuring a different AAA context to use in the MME service configuration. ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 59: Mme Service Configuration Procedures

    Access Control List configuration, use of inappropriate port number may result in communication loss. Refer respective feature configuration document carefully before assigning any port number or IP address for communication with internal or external network. Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 60: Information Required To Configure The System As An Mme

    Open or encrypted passwords can be used. administrator password Remote access The type of remote access that will be used to access the system such as telnetd, sshd, and/or ftpd. type(s) ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 61: Required Mme Context Configuration Information

    Optionally tracking area identifier can be configured for an S-GW. P-GW address Specifies the PDN Gateway (P-GW) address to use P-MIP/GTP protocol for S5 and S8 interface and weightage for specific P-GW while selecting P-GW for MME service Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 62: Required Egtp Context Configuration Information

    Multiple addresses and subnets are needed if multiple S11 interfaces will be configured. Required AAA Context Configuration Information The following table lists the information that is required to configure the AAA (MME-HSS) context on an MME. ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 63

    The S6a origin realm name described above. Peer address and The IPv6 address and port number of the HSS. port number Route-entry peer The S6a endpoint name described above. Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 64: Mme Service Configuration

    Save your configuration as described in the Verifying and Saving Your Configuration chapter. S1-MME Interface Configuration Use the following example to configured the S1-MME interfaces in source context: configure context <vpn_ctxt_name> -noconfirm interface <intf_name> ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 65: Creating And Binding Mme Service

    Configuring Network Id Parameters Use the following example to configure the network parameters. configure context <vpn_ctxt_name> mme-service <mme_svc_name> dest-sctp address <ip_address> dest-sctp port <port_num> plmn-id mcc <mcc_value> mnc <mnc_value> Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 66: Associating Egtp Service And Mme-hss Service

    Use the following example to configure the DNS Client service on the system to use for locating S-GW and P-GW in LTE network: configure context <dns_ctxt_name> ip domain-lookup ip name-server <ns_ip_address> ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 67: Configuring S-gw And P-gw With Mme

    { pgw | sgw } dns-service <dns_svc_name> context <dns_ctxt_name> Notes: <dns_svc_name> is a preconfigured DNS client service as configured in Configuring DNS Client Service section. Only one DNS client service can be associated with MME service. Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 68: Configuring Session And Security Parameters For Eps Bearer Contexts

    In this example, an MME service called mmesvc was configured and you can see some parameters configured as default. Service name : mmesvc Context : ingress Status : STARTED Bind : Done ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 69

    PGW DNS Service : Not defined SGW DNS Service : Not defined Implicit Detach Timeout : 3600s Auth Max Retransmissions Count Identity Max Retransmissions Count T3412 Timeout : 6s Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 70

    Verify configuration for errors by entering the following command in Exec Mode: show configuration-errors section mme-service The output of this command displays the errors, if any, in MME service configuration. ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 71: Egtp Service Configuration

    <egtp_ctxt_name> is name of the destination context in which eGTP service is to be configured for S11 interface functionality with S-GW. <mme_ip_address> is the local IP address of this MME service and should not conflict with any other service. Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 72: Verifying Egtp Service Configuration

    Verify configuration for errors by entering the following command in Exec Mode: show configuration-errors section egtp-service The output of this command displays the errors, if any, in eGTP service configuration. ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 73: Mme-hss Service Configuration

    HSS. Typically this can be the same context where MME service is configured. A maximum of 256 services (regardless of type) can be configured per system. <dur> is the timeout duration in second for application message retransmission between MME and HSS. Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 74: Associating Diameter Endpoint With Mme-hss Service

    } action {continue | retry-and-terminate | terminate } Notes: For more information on Diameter endpoint configuration, refer Configuring Diameter AAA Functionality section provided in AAA Interface Administration and Reference. ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 75: Verifying Mme-hss Service Configuration

    State: ACTIVE Pending Requests: 0 API Requests: Open: Close: Update Location: Purge UE: Authenticate: Notify: Identity Check: Recoveries: Micro Checkpoint: Full Checkpoint: User Data Query: API Successes: Open: Close: Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 76

    User Data Req: Server Successes: Update Location: Purge UE: Authenticate: Notify: Identity Check: User Data Req: Server Errors: Update Location: Purge UE: Authenticate: Notify: Identity Check: User Data Req: ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 77: Event Ids For Mme Service

    Mobile IPv6 Facility Events 129000-129999 Network Access Signaling Facility Events 153000-153999 Statistics Facility Events 31000-31999 System Facility Events 1000-1999 System Initiation Task (SIT) Main Facility Events 4000-4999 Threshold Facility Events 61000-61999 Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 78

    MME Service Configuration Procedures ▀ Event IDs for MME Service Facility Event ID Range Virtual Private Network Facility Events 5000-5999 ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 79: Verifying And Saving Your Configuration

    Chapter 4 Verifying and Saving Your Configuration This chapter describes how to save the system configuration. Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 80: Verifying The Configuration

    128 ip output access-group: ip input access-group: ppp authentication: allow noauthentication: Enabled imsi authentication:Disabled ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 81: Service Configuration

    The output is a concise listing of the service parameter settings similar to the sample displayed below. In this example, a P-GW service called pgw is configured. Service name : pgw1 Service-Id : 1 Context : test1 Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 82: Context Configuration

    This command displays errors it finds within the configuration. For example, if you have created a service named “service1”, but entered it as “srv1” in another part of the configuration, the system displays this error. ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 83

    If the configuration contains no errors, an output similar to the following is displayed: ################################################################################ Displaying Global AAA-configuration errors ################################################################################ Total 0 error(s) in this section ! Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 84: Saving The Configuration

    Files saved locally can be stored in the SPC‟s/SMC‟s CompactFlash or on an installed PCMCIA memory card on the SPC/SMC. Files that are saved to a remote network node can be transmitted using either FTP, or TFTP. ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 85: Saving The Configuration On The Chassis

    (a PC-Card in Slot 1 of the standby SPC/SMC) must be available. Otherwise, a failure message is displayed. Note: If saving the file to an external network (non-local) device, the system disregards this keyword. Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 86

    To save a configuration file called init_config.cfg to the root directory of a TFTP server with a hostname of config_server, enter the following command: save configuration tftp://config_server/init_config.cfg ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 87: Monitoring The Service

    In addition to the CLI, the system supports the sending of Simple Network Management Protocol (SNMP) traps that indicate status and alarm conditions. Refer to the SNMP MIB Reference Guide for a detailed listing of these traps. Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 88: Monitoring System Status And Performance

    Display Session Duration Statistics View session duration statistics show session duration Display Session State Statistics View session state statistics show session progress Display Session State PCF Statistics ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 89

    View eGTPC peer information show egtpc peers interface sgw-egress address ip_address View eGTPC session information show egtpc sessions View eGTPC session statistics show egtpc statistics View Subscriber Session Trace Statistics Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 90

    MME trace_ref_id network-element mme View Trace Collection Entity connections and statistics show session trace tce-summary for all network elements ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 91: Clearing Statistics And Counters

    (MME, MME-HSS, MME DB, etc.). Statistics and counters can be cleared using the CLI clear command. Refer to Command Line Reference for detailed information on using this command. Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 93: Configuring Subscriber Session Tracing

    This chapter discusses following topics for feature support of Subscriber Session Tracing in LTE service: Introduction Supported Standards Supported Networks and Platforms Licenses Subscriber Session Tracing Functional Description Subscriber Session Trace Configuration Verifying Your Configuration Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 94: Introduction

    MPORTANT Only Maximum Trace Depth is supported in the current release. The following figure shows a high-level overview of the session-trace functionality and deployment scenario: ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 95: Supported Functions

    This section provides the list of supported functionality of this feature support: Support to trace the control flow through the access network. Trace of specific subscriber identified by IMSI Trace of UE identified by IMEI(SV) Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 96

    Trace Collection Entity (TCE) Support Active pushing of files to the TCE Passive pulling of files by the TCE 1 TCE support per context Trace Session Recovery after Failure of Session Manager ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 97: Supported Standards

    3GPP TS 32.423 V8.2.0 (2009-09): 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Subscriber and equipment trace: Trace data definition and management (Release 8) Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 98: Supported Networks And Platforms

    ▀ Supported Networks and Platforms Supported Networks and Platforms This feature supports all ASR 5000 Series Platforms with StarOS Release 9.0 or later running MME/S-GW/P-GW service(s) for the core LTE network functions. ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide...

  • Page 99: Licenses

    Configuring Subscriber Session Tracing Licenses ▀ Licenses This is a base feature and available for configuration with default LTE component license(s) on the system: Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 100: Subscriber Session Trace Functional Description

    (typically when the subscriber/UE under trace initiates a connection). A failure to activate a trace (due to max exceeded or some other failure reason) results in a notification being sent to the TCE indicating the failure. ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 101: Management Activation

    All data collected by the NE is formatted into standard XML file format and forwarded to the TCE via (S)FTP. The specific format of the data is defined in 3GPP standard 3GPP TS 32.423 V8.2.0 (2009-09) Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 102: Trace Depth

    SGSN S-GW S-GW The S-GW support tracing of the following interfaces with the following trace capabilities: Interface Name Remote Device Trace Signaling (De)Activation RX Trace Signaling (De)Activation TX ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 103: P-gw

    The PDN-GW support tracing of the following interfaces with the following trace capabilities: Interface Name Remote Device Trace Signaling (De)Activation RX Trace Signaling (De)Activation TX S2abc Various NEs S-GW (Intra-PLMN) AAA Server/Proxy S-GW (Inter-PLMN) Policy Server Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 104: Subscriber Session Trace Configuration

    <trace_ref_id> is the configured Trace Id to be used for this trace collection instance. It is composed of MCC (3 digit)+MNC (3 digit)+Trace Id (3 byte octet string). <ip_address> is the IP address of Trace collection Entity in IPv4 notation. ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 105: Trace File Collection Configuration

    <string> is the location/path on the trace collection entity (TCE) where trace files will be stored on TCE. For more information, refer session trace command in Command Line Interface Reference. Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 106: Verifying Your Configuration

    Exec Mode: show session trace trace-summary The output of this command displays the summary of trace references for all network elements: Trace Reference: 310012012345 Trace Reference: 310012012346 Trace Reference: 310012012345 ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 107

    Configuring Subscriber Session Tracing Verifying Your Configuration ▀ Trace Reference: 310012012346 Trace Reference: 310012012347 Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 109: Troubleshooting The Service

    Chapter 7 Troubleshooting the Service This chapter provides information and instructions for using the system command line interface (CLI) for troubleshooting issues that may arise during service operation. Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 110: Test Commands

    The following figure displays a sample of this command‟s output showing a successful PPP echo-test to a subscriber named user2@aaa. USERNAME: user2@aaa MSID: 0000012345 CALLID: 001e8481 Tx/Rx 1/0 RTT(min/max/avg) 0/0/0 USERNAME: user2@aaa MSID: 0000012345 CALLID: 001e8481 Tx/Rx 1/1 RTT(min/max/avg) 77/77/77 (COMPLETE) ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 111: Using The Egtpc Test Echo Command

    This command must be executed from within the context in which at least one MME service is configured. The command has the following syntax: dhcp test dhcp-service svc_name [ all | server ip_address ] Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 112

    DHCP-Gi to a server with an IP address of 192.168.16.2. The IP address provided during the test was 192.168.16.144. DHCP test status for service <DHCP-Gi>: Server address: 192.168.16.2 Status: Tested Lease address: 192.168.16.144 Lease Duration: 600 secs. ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 113: Engineering Rules

    This section provides engineering rules or guidelines that must be considered prior to configuring the system for your network deployment. This appendix describes following engineering rules for MME services: APN Engineering Rules DHCP Service Engineering Rules Lawful Intercept Engineering Rules Service Engineering Rules Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 114: Apn Engineering Rules

    APN Engineering Rules The following engineering rules apply to APNs: APNs must be configured within the context used for authentication. A maximum of 1,024 APNs per system can be configured. ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 115: Dhcp Service Engineering Rules

    The following engineering rule applies to the DHCP Service: Up to 8 DHCP servers may be configured per DHCP service. A maximum of 3 DHCP server can be tried for a call. Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

  • Page 116: Lawful Intercept Engineering Rules

    ▀ Lawful Intercept Engineering Rules Lawful Intercept Engineering Rules The following engineering rules apply to Lawful Intercept on supported MME service: A maximum of 20000 Lawful Intercepts can be performed simultaneously. ▄ Cisco ASR 5000 Series Mobility Management Entity Administration Guide OL-22987-01...

  • Page 117: Service Engineering Rules

    Even though service names can be identical to those configured in different contexts on the same system, this is not a good practice. Having services with the same name can lead to confusion, difficulty troubleshooting problems, and make it difficulty understanding outputs of show commands. Cisco ASR 5000 Series Mobility Management Entity Administration Guide ▄ OL-22987-01...

Comments to this Manuals

Symbols: 0
Latest comments: