Download Print this page

Advertisement

Advertisement

   Summary of Contents for Cisco ASR 5000 Series

  • 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

    Management System Overview ........................37 Bulk Statistics Support ..........................38 Threshold Crossing Alerts (TCA) Support ....................39 ANSI T1.276 Compliance ..........................40 Features and Functionality - External Application Support ................... 41 Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 4

    Trace Session ..............................86 Trace Recording Session ..........................86 Network Element (NE) ............................86 Activation ................................86 Management Activation ..........................87 Signaling Activation ............................. 87 Start Trigger ..............................87 Deactivation ..............................87 ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 5

    Interface and Port Rules ............................102 S1-U/S11 Interface Rules ..........................102 S5/S8 Interface Rules ............................102 MAG to LMA Rules ........................... 102 S-GW Service Rules ............................. 104 S-GW Subscriber Rules ............................105 Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-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 Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 8: Conventions Used

    Description Conventions 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 command syntax. ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 9

    (also known as a pipe filter). Pipe filters can be used in conjunction with required or optional keywords or variables. For example: Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-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: Serving Gateway Overview

    Network Deployment(s) Features and Functionality - Base Software Features and Functionality - External Application Support Features and Functionality - Optional Enhanced Feature Software How the Serving Gateway Works Supported Standards Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 12: Ehrpd Network Summary

    Core (EPC). The EPC is a high-bandwidth, low-latency packet network also know as System Architecture Evolution (SAE), supporting the Long Term Evolution Radio Access Network (LTE RAN). The following figure shows the relationship of the eHRPD network with the EPC. ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 13: Ehrpd Network Components

    The eAN is a logical entity in the radio access network used for radio communications with an access terminal (mobile device). The eAN is equivalent to a base station in 1x systems. The eAN supports operations for EPS – eHRPD RAN in addition to legacy access network capabilities. Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 14: Evolved Packet Control Function (epcf)

    LTE and HRPD with the following requirements: Sub 300ms bearer interruption Inter-technology handoff between 3GPP E-UTRAN and HRPD Intra-technology handoff between an HSGW and an existing PDSN Support for inter-HSGW fast handoff via PMIPv6 Binding Update ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 15: Sae Network Summary

    UMTS, and LTE) and non-3GPP radio access technologies, including CDMA, WiMAX, WiFi, High Rate Packet Data (HRPD), evolved HRPD, and ETSI defined TISPAN networks. The following figure shows the interworking of the EPC with the different radio access technologies. Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 16: E-utran Epc Network Components

    O F C S E n te rp rise In te rn e t W L A N E-UTRAN EPC Network Components The E-UTRAN EPC network is comprised of the following components: ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 17: Enodeb

    HRPD access, as specified in the pre-registration and handover flows Serving Gateway (S-GW) For each UE associated with the EPS, there is a single S-GW at any given time providing the following basic functions: Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 18: Pdn Gateway (p-gw)

    DL rate enforcement based on AMBR (Aggregate Max Bit Rate) and based on the accumulated MBRs of the aggregate of SDFs with the same GBR QCI DHCPv4 and DHCPv6 functions (client, relay and server) LMA for PMIP6 ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 19: Product Description

    The S-GW is also involved in mobility by forwarding down link data during a handover from the E-UTRAN to the eHRPD network. An interface from the eAN/ePCF to an MME provides signaling that creates a GRE tunnel between the S-GW and the eHRPD Serving Gateway. Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 20

    (terminating the S4 interface from an SGSN and relaying the traffic between 2G/3G system and a PDN gateway. packet buffering for ECM-IDLE mode downlink and initiation of network triggered service request procedure. ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 21

    Lawful Interception is required. transport level packet marking. user accounting and QCI granularity for charging. uplink and downlink charging per UE, PDN, and QCI. Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 22: Product Specifications

    Information in this section describes the hardware required to enable S-GW services. Platforms The S-GW service operates on the ASR 5000 Series platforms: Components The following application and line cards are required to support S-GW functionality on an ASR 5000 platform: System Management Cards (SMCs): Provides full system control and management of all cards within the ASR 5000 platform.

  • Page 23: Operating System Requirements

    SAE services is located in the Hardware Platform Overview chapter of the Product Overview Guide. Operating System Requirements The S-GW is available for all Cisco ASR 5000 Platforms running StarOS Release 9.0 or later. Cisco ASR 5000 Series Serving Gateway Administration Guide ▄...

  • Page 24: Network Deployment(s)

    S 2 b E n te rp rise T ru ste d /U n triste d N o n -3 G P P D e vice s In te rn e t ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 25: Supported Logical Network Interfaces (reference Points)

    This reference point provides tunneling (bearer channel) and management (signaling channel) between the S-GW and the P-GW. The S8 interface is used for roaming scenarios. The S5 interface is used for non-roaming. Supported protocols: Transport Layer: UDP, TCP Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 26

    This reference point provides bearer channel tunneling between the eNodeB and the S-GW. It also supports eNodeB path switching during handovers. Supported protocols: Transport Layer: UDP, TCP Tunneling: IPv4 or IPv6 GTP-U (bearer channel) Network Layer: IPv4, IPv6 Data Link Layer: ARP Physical Layer: Ethernet ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 27

    This signaling interface supports the transfer of policy control and charging rules information (QoS) between the Bearer Binding and Event Reporting Function (BBERF) on the S-GW and a Policy and Charging Rules Function (PCRF) server. Supported protocols: Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 28

    T C P / S C T P T C P / S C T P IP v4 / IP v6 IP v4 / IP v6 L 1/L2 L 1/L2 ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 29: Features And Functionality - Base Software

    IPv6 Connections to Attached Elements IPv6 transport and interfaces are supported on all of the following connections: Diameter Gxc policy signaling interface Diameter Rf offline charging interface Lawful Intercept (X1, X2 interfaces) Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 30: Lawful Intercept

    X3 content delivery: Includes intercepted call content for all default and dedicated EPS bearers. 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 also includes other identifying information including sequence numbers, timestamps and session &...

  • Page 31: Session Recovery Support

    Performance Goals: As subscriber level trace is a CPU intensive activity the max number of concurrently monitored trace sessions per Cisco P-GW or S-GW is 32. Use in a production network should be restricted to minimize the impact on existing services.

  • Page 32: Quality Of Service Management Features

    Flow Templates (TFTs) in the downlink direction for mapping inbound Service Data Flows (SDFs) to EPS bearers. The P-GW maps the traffic based on the downlink TFT to the S5/S8 bearer. The Cisco P-GW offers all of the following bearer-level aggregate constructs: QoS Class Identifier (QCI): An operator provisioned value that controls bearer level packet forwarding treatments (e.g.

  • Page 33: Network Access And Charging Management Features

    GZIP. The Offline Charging implementation offers built-in heart beat monitoring of adjacent CGFs. If the Cisco P-GW have not heard from the neighbor CGF within the configurable polling interval, they will automatically buffer the charging records on the local drives until the CGF reactivates itself and is able to begin pulling the cached charging records.

  • Page 34: Network Operation Management Functions

    GERAN or UTRAN to E-UTRAN Inter-RAT handover with SGW change. Path management function: This functionality is responsible for managing the path between the tunnel endpoints. It includes messages like ECHO request, ECHO response and version not supported indication. ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 35: Multiple Pdn Support

    S5/S8 GTP (E-UTRAN EPC) In accordance with 3GPP TS 23.401 the Cisco S-GW platform supports GTPv2-C and GTPv1-U call control and user plane tunnelling. A GTP tunnel is identified in each node with a Tunnel Endpoint ID (TEID), an IP address and a UDP port number.

  • Page 36: Ip Access Control Lists

    For more information on IP access control lists, refer to the IP Access Control Lists chapter in the System Enhanced Feature Configuration Guide. System Management Features This section describes following features: Management System Overview Bulk Statistics Support Threshold Crossing Alerts (TCA) Support ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 37: Management System Overview

    In addition, all management is performed out-of-band for security and to maintain system performance. Cisco's O&M module offers comprehensive management capabilities to the operators and enables them to operate the system more efficiently. There are multiple ways to manage the system either locally or remotely using its out-of-band management interfaces.

  • Page 38: Bulk Statistics Support

    This simplifies the post-processing of statistical data since it can be formatted to be parsed by external, back-end processors. When used in conjunction with the Web Element Manager, the data can be parsed, archived, and graphed. ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 39: Threshold Crossing Alerts (tca) Support

    With this capability, the operator can configure threshold on these resources whereby, should the resource depletion cross the configured threshold, a SNMP Trap would be sent. The following thresholding models are supported by the system: Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 40: Ansi T1.276 Compliance

    RADIUS and SSH which are dependent on external elements. ANSI T1.276 compliance in such cases will be the domain of the external element. ANSI T1.276 guidelines will only be implemented for locally configured operators. ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 41: Features And Functionality - External Application Support

    CORBA interfaces. The server component is fully compatible with the fault-tolerant Sun® Solaris® operating system. The following figure demonstrates various interfaces between the Cisco Web Element Manager and other network components. Cisco ASR 5000 Series Serving Gateway Administration Guide ▄...

  • Page 42

    ▀ Features and Functionality - External Application Support Figure 5. Web Element Manager Network Interfaces MPORTANT For more information on WEM support, refer to the WEM Installation and Administration Guide. ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 43: Features And Functionality - Optional Enhanced Feature Software

    These capabilities are insured through use of cryptographic techniques. The Cisco S-GW supports IKEv1 and IPSec encryption using IPv4 addressing. IPSec enables the following two use cases: Encryption of S8 sessions and EPS bearers in roaming applications where the P-GW is located in a separate administrative domain from the S-GW IPSec ESP security in accordance with 3GPP TS 33.210 is provided for S1 control plane, S1 bearer plane and S1...

  • Page 44: Layer 2 Traffic Management (vlans)

    Therefore, each Ethernet port can be viewed as containing many logical ports when VLAN tags are employed. MPORTANT For more information on VLAN support, refer to the VLANs chapter in the System Enhanced Feature Configuration Guide. ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 45: How The Serving Gateway Works

    The following topics and procedure flows are included: Subscriber-initiated Attach (initial) Subscriber-initiated Detach Subscriber-initiated Attach (initial) This section describes the procedure of an initial attach to the EPC network by a subscriber. Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 46

    U p d a te L o c a tio n R e q U p d a te L o c a tio n R s p D a ta P D N ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 47

    If dynamic PCC is deployed, the P-GW interacts with the PCRF to get the default PCC rules for the UE. The IMSI, UE IP address, User Location Information, RAT type, AMBR are provided to the PCRF by the P-GW if received by the previous message. Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 48: Subscriber-initiated Detach

    The HSS stores the APN and P-GW address pair and sends an Update Location Response to the MME. Bidirectional data is passed between the UE and PDN. Subscriber-initiated Detach This section describes the procedure of detachment from the EPC network by a subscriber. ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 49

    If Switch Off indicates that the detach is not due to a switch off situation, the MME sends a Detach Accept message to the The MME releases the S1-MME signalling connection for the UE by sending an S1 Release command to the eNodeB with Cause = Detach. Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 50: Supported Standards

    3GPP TS 29.281: GPRS Tunnelling Protocol User Plane (GTPv1-U) 3GPP TS 32.251: Telecommunication management; Charging management; Packet Switched (PS) domain charging 3GPP TS 32.295: Charging management; Charging Data Record (CDR) transfer ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 51: 3gpp2 References

    RFC 4282: The Network Access Identifier RFC 4283: Mobile Node Identifier Option for Mobile IPv6 (MIPv6) RFC 4861: Neighbor Discovery for IP Version 6 (IPv6) RFC 4862: IPv6 Stateless Address Autoconfiguration Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 52: Object Management Group (omg) Standards

    Internet-Draft (draft-ietf-netlmm-grekey-option-01.txt): GRE Key Option for Proxy Mobile IPv6, work in progress Internet-Draft (draft-ietf-mext-binding-revocation-02.txt): Binding Revocation for IPv6 Mobility, work in progress Object Management Group (OMG) Standards CORBA 2.6 Specification 01-09-35, Object Management Group ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 53: Serving Gateway Configuration

    Optional configuration commands specific to the S-GW product are located in the Command Line Interface Reference. The following procedures are located in this chapter: Configuring the System as a Standalone eGTP S-GW Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 54: Configuring The System As A Standalone Egtp S-gw

    For example, port 17/1 identifies connector number 1 on the card in slot 17. A single physical port can facilitate multiple interfaces. ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 55: Required S-gw Ingress Context Configuration Information

    Used when configuring static IP routes from the interface(s) to a specific network. address GTP-U Service Configuration GTP-U service An identification string from 1 to 63 characters (alpha and/or numeric) by which the GTP-U service will be name recognized by the system. Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 56: Required S-gw Egress Context Configuration Information

    An identification string from 1 to 63 characters (alpha and/or numeric) by which the GTP-U service will be name recognized by the system. IP address S5/S8 interface IPv4 or IPv6 address. eGTP Egress Service Configuration ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 57: How This Configuration Works

    How This Configuration Works The following figure and supporting text describe how this configuration with a single ingress and egress context is used by the system to process a subscriber call. Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 58

    5. The P-GW responds with a Create Session Response message that includes the PGW S5/S8 Address for control plane and bearer information. 6. The S-GW conveys the control plane and bearer information to the MME in a Create Session Response message. ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 59: Egtp S-gw Configuration

    Configuration section. Step 4 Verify and save the configuration by following the instruction in the Verifying and Saving the Configuration section. Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 60: Initial Configuration

    Create a S-GW service within the newly created ingress context by applying the example configuration in the Creating an S-GW Service section. Modifying the Local Context Use the following example to set the default subscriber and configure remote access capability in the local context: ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 61

    The S1-U/S11 interface IP address(es) can also be specified as IPv6 addresses using the command. Creating an eGTP Ingress Service Use the following configuration example to create an eGTP ingress service: Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 62

    The S5/S8 interface IP address can also be specified as an IPv4 address using the command. Creating an eGTP Egress Service Use the following configuration example to create an eGTP egress service in the S-GW egress context: ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 63: Egtp Configuration

    Setting the System’s Role as an eGTP S-GW and Configuring GTP-U and eGTP Service Settings Use the following configuration example to set the system to perform as an eGTP S-GW and configure the GTP-U and eGTP services: Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 64

    Use the following example to configure the S-GW service: Configuring an IP Route Use the following example to configure an IP Route for control and user plane data communication with an eGTP PDN Gateway: ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 65: Verifying And Saving The Configuration

    Configuring the System as a Standalone eGTP S-GW ▀ Verifying and Saving the Configuration Refer to the Verifying and Saving the Configuration chapter to verify and save your S-GW configuration. Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 67: Verifying And Saving Your Configuration

    Chapter 3 Verifying and Saving Your Configuration This chapter describes how to save the system configuration. Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 68: Verifying The Configuration

    Using these examples, enter the following commands to verify proper feature configuration: The output displays the complete configuration for the APN. In this example, an APN called apn1 is configured. ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 69: 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. Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 70: 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 Serving Gateway Administration Guide OL-22986-01...

  • Page 71

    You must refine this command to specify particular sections of the configuration. Add the keyword and choose a section from the help menu: If the configuration contains no errors, an output similar to the following is displayed: Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 72: 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 Serving Gateway Administration Guide OL-22986-01...

  • Page 73: 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 Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 74

    192.168.34.156 on which you have an account with a username of administrator and a password of secure, use the following command: 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: ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 75: 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 for a detailed listing of these traps. Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 76: Monitoring System Status And Performance

    View Statistics for Subscribers using MAG Services on the System View statistics for subscribers using any MAG service on the system View statistics for subscribers using a specific MAG service on the system View Session Subsystem and Task Information ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 77

    View eGTP-C service statistics for a specific service View GTP-U service statistics for all GTP-U data traffic on the system View QoS/QCI Information View QoS Class Index to QoS mapping tables Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 78: Clearing Statistics And Counters

    (PPP, MIPHA, MIPFA, etc.). Statistics and counters can be cleared using the CLI command. Refer to Command Line Reference for detailed information on using this command. ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 79: 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 Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 80: 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 Serving Gateway Administration Guide OL-22986-01...

  • Page 81: 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 Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 82

    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 Serving Gateway Administration Guide OL-22986-01...

  • Page 83: Supported Standards

    (Release 8) 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 Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 84: 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 Serving Gateway Administration Guide...

  • Page 85: 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 Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 86: 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 Serving Gateway Administration Guide OL-22986-01...

  • Page 87: 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 Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 88: Trace Depth

    Trace Signaling (De)Activation TX eNodeB 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 Serving Gateway Administration Guide OL-22986-01...

  • Page 89: 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 Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 90: Subscriber Session Trace Configuration

    > 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). < > is the IP address of Trace collection Entity in IPv4 notation. ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 91: Trace File Collection Configuration

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

  • Page 92: Verifying Your Configuration

    View the session trace references active for various network elements in an EPC network by entering the following command in Exec Mode: The output of this command displays the summary of trace references for all network elements: ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 93

    Configuring Subscriber Session Tracing Verifying Your Configuration ▀ Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 95: Sample Configuration Files

    This appendix contains sample configuration files for the S-GW. The following configurations are supported: Standalone eGTP Serving Gateway In each configuration example, commented lines are labeled with the number symbol (#) and variables are identified using italics within brackets (< >). Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 96: Standalone Egtp Serving Gateway

    Sample Configuration Files ▀ Standalone eGTP Serving Gateway Standalone eGTP Serving Gateway Configuration Sample ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 97

    Sample Configuration Files Standalone eGTP Serving Gateway ▀ Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 98

    Sample Configuration Files ▀ Standalone eGTP Serving Gateway ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 99

    Sample Configuration Files Standalone eGTP Serving Gateway ▀ Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 100

    Sample Configuration Files ▀ Standalone eGTP Serving Gateway ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 101: S-gw Engineering Rules

    ASR 5000 for your network deployment. General and network-specific rules are located in the appendix of the System Administration Guide for the specific network type. The following rules are covered in this appendix: Interface and Port Rules S-GW Service Rules S-GW Subscriber Rules Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 102: Interface And Port Rules

    The logical interface(s) that will be used to facilitate the S5/S8 interface(s) must be configured within the egress context. MAG services must be configured within the egress context. MAG services must be associated with an S-GW service. ▄ Cisco ASR 5000 Series Serving Gateway Administration Guide OL-22986-01...

  • Page 103

    S-GW Engineering Rules Interface and Port Rules ▀ Depending on the services offered to the subscriber, the number of sessions facilitated by the S5/S8 interface can be limited. Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-01...

  • Page 104: S-gw Service 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 Serving Gateway Administration Guide OL-22986-01...

  • Page 105: S-gw Subscriber Rules

    The following engineering rule applies to subscribers configured within the system: A maximum of 2,048 local subscribers can be configured per context. Default subscriber templates may be configured on a per S-GW or MAG service. Cisco ASR 5000 Series Serving Gateway Administration Guide ▄ OL-22986-01...

Comments to this Manuals

Symbols: 0
Latest comments: