HeNB-GW Administration Guide, StarOS Release 19 First Published: September 30, 2015 Last Modified: December 15, 2015 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
CONTENTS Preface About this Guide vii Conventions Used vii Supported Documents and Resources viii Related Common Documentation viii Related Product Documentation viii Obtaining Documentation ix Contacting Customer Support ix CHAPTER 1 HeNB Gateway in Wireless LTE Network 1 Product Description 1 Protocol Architecture 3 Deployment Scenarios for HeNB Access Network 5 HeNB Access Network Elements 8 Home eNodeB 9 Security Gateway (SeGW) 9 HeNB Gateway (HeNB-GW) 9 HeNB Management System (HeMS) 10 CSG List Ser
Contents DSCP Marking on S1-U Relay 17 Fault Reporting Support 17 Location Reporting Support 17 QoS Support 17 Redundancy Support 17 Troubleshooting Features Support 18 X2 Handover Procedure Support 19 MME Pool size 19 Cell Broadcast Support 20 3GPP Standard Support for Overload Control 21 DHCPv4 Proxy support for HeNBGW with IPSec 22 HeNBGW Multi Operator Core Network (MOCN) 23 s1ap-reset/partial-reset messages from HeNBGW 27 X2 Proxy Gateway support 28 Features and Functionality - Optional Enhanced Featu
Contents IPSec Configuration 49 GTP-U Service Configuration 51 LTE Policy Configuration 51 Verifying HeNB-GW Configuration 52 Logging Facility Configuration 52 Displaying Logging Facility 53 Alarm and Alert Trap Configuration 53 SNMP MIB Traps for HeNB-GW Service 54 Event IDs for HeNB-GW Service 55 DHCP Configuration 56 Configuring DHCP Service 56 Configuring Subscriber Template for HeNB 56 CHAPTER 4 Multi HeNBGW Access Services support 59 Feature Description 59 Overview 59 How It Works 60 Configuring Mu
Contents HeNB-GW Administration Guide, StarOS Release 19 vi
About this Guide This preface describes the HeNBGW Administration Guide, how it is organized, and its document conventions. The Home eNodeB Gateway Administration Guide (HeNBGW) is a StarOS application that runs on Cisco ASR 5x00 platforms. For additional platform information, refer to the appropriate System Administration Guide and/or contact your Cisco account representative.
About this Guide Supported Documents and Resources Typeface Conventions Description Text represented as commands This typeface represents commands that you enter, for example: show ip access-list This document always gives the full form of a command in lowercase letters. Commands are not case sensitive.
About this Guide Obtaining Documentation Obtaining Documentation The most current Cisco documentation is available on the following website: http://www.cisco.com/cisco/web/psa/default.html Use the following path selections to access the HNBGW documentation: Products > Wireless > Mobile Internet> Network Functions > HeNB-GW Administration Guide. Contacting Customer Support Use the information in this section to contact customer support. Refer to the support area of http://www.cisco.
About this Guide Contacting Customer Support HeNB-GW Administration Guide, StarOS Release 19 x
CHAPTER 1 HeNB Gateway in Wireless LTE Network eNode B is the node with radio access capabilities in LTE radio access network (RAN) that is responsible for radio transmission and reception from UEs in absence of Radio Network Controller (RNC) in LTE. The functionality of eNode B is enhanced to handle the tasks which were handled by the RNC in the 3G network. The Home eNode B (HeNB) provides LTE radio coverage for LTE devices/handsets within a home residential or enterprise coverage area.
HeNB Gateway in Wireless LTE Network Product Description The figure given describes a high level view of LTE network with Femtocell and HeNB-GW. Figure 1: Home eNodeB Gateway Network Architecture In the above figure, the S1 interface has been defined as an interface between • HeNB-GW and the Core Network (CN)/EPC • HeNB and the HeNB-GW • HeNB and the CN An HeNB-GW provides standards-based S1-MME and S1-U network interfaces.
HeNB Gateway in Wireless LTE Network Protocol Architecture • Optionally performing paging optimization Important Some of the features may not be available in this release. Kindly contact your local Cisco representative for more information on supported features. Protocol Architecture This section provides a brief description and pictorial representation of protocol stacks for User as well as Control planes in context to HeNB-GW.
HeNB Gateway in Wireless LTE Network Protocol Architecture Protocol Stacks for S1 Control Plane The two figures below show the S1-MME protocol stacks with and without the HeNB-GW. When the HeNB-GW is not present, all the S1 procedures are terminated at the HeNB and the MME. Figure 3: Control plane for S1-MME Interface for HeNB to MME without the HeNB-GW The HeNB-GW terminates the non-UE-dedicated procedures: both with the HeNB, and with the MME.
HeNB Gateway in Wireless LTE Network Deployment Scenarios for HeNB Access Network scope of any protocol function associated to a non-UE-dedicated procedure lies between HeNB and HeNB-GW, and/or between HeNB-GW and MME. Figure 4: Control plane for S1-MME Interface for HeNB to MME with the HeNB-GW Any protocol function associated to a UE-dedicated-procedure resides within the HeNB and the MME only.
HeNB Gateway in Wireless LTE Network Deployment Scenarios for HeNB Access Network • Variant I: With dedicated HeNB-GW where HeNBs connect via HeNB-GW for control and data aggregation.
HeNB Gateway in Wireless LTE Network Deployment Scenarios for HeNB Access Network • Variant II: With HeNB-GW for control plane aggregation only and directly connect to SGW for data plane.
HeNB Gateway in Wireless LTE Network HeNB Access Network Elements There is another deployment scenario for HeNBs where HeNB-GW is absent. In this deployment, HeNBs connect directly to highly scalable MMEs. This deployment scenario is displayed in the following figure: Figure 7: Without HeNB-GW Cisco's LTE Femtocell network solution focuses on Variant 1 where HeNB-GW is mandatory for HeNBs to connect. Communication between the HeNB and the HeNB GW is secured by a security Gateway (SeGW) function.
HeNB Gateway in Wireless LTE Network HeNB Access Network Elements Home eNodeB A Home eNodeB (HeNB) is the a customer premise equipment that offers Uu interface to UE and S1 interface over IPSec tunnel to HeNB-GW for accessing LTE Core Network in Femtocell access network. It also provides the support to HeNB registration and UE registration over S1 interface with the HeNB-GW.
HeNB Gateway in Wireless LTE Network Licenses The HeNB-GW may optionally terminate the user plane towards the HeNB and towards the S-GW, and may provide a relay function for relaying User Plane data between the HeNB and the S-GW. The HeNB-GW supports NAS Node Selection Function (NNSF). NAS Node Selection Function (NNSF) supports S1-Flex or multiple S1-MME connections towards the EPC from any one HeNB. Important HeNB Management System (HeMS) It is a network element management system for HeNB access.
HeNB Gateway in Wireless LTE Network Platform Requirements Contact your Cisco account representative for detailed information on specific 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. Platform Requirements The HeNB-GW service runs on a Cisco® ASR 5x00 and virtualized platforms running StarOS Rel. 15.0 or later.
HeNB Gateway in Wireless LTE Network Supported Logical Interfaces Compression. All of these functions are carried by the physical layer over the air as shown in the following figure: Figure 8: e-UTRAN Uu Interface Logical Representation The physical layer in LTE is based upon the Orthogonal Frequency Division Multiplexing (OFDM) using Orthogonal Frequency Division Multiple Access (OFDMA) in the downlink and variant of this Single Carrier Frequency Division Multiple Access (SC-FDMA) in the uplink.
HeNB Gateway in Wireless LTE Network Features and Functionality - Base Software ◦Error Indication functionality for allowing a proper error reporting/handling in cases where no failure messages are defined. ◦Overload function for indicating the load situation in the control plane of the S1 interface. ◦Load balancing function for ensuring equally loaded MMEs within an MME pool area. ◦S1 Setup functionality for initial S1 interface setup for providing configuration information.
HeNB Gateway in Wireless LTE Network AAA Server Group Support • Fault Reporting Support, on page 17 • Location Reporting Support, on page 17 • QoS Support, on page 17 • Redundancy Support, on page 17 • Troubleshooting Features Support, on page 18 • X2 Handover Procedure Support, on page 19 • MME Pool size, on page 19 • Cell Broadcast Support, on page 20 • 3GPP Standard Support for Overload Control, on page 21 • DHCPv4 Proxy support for HeNBGW with IPSec, on page 22 • HeNBGW Multi Operator Core Network (MOC
HeNB Gateway in Wireless LTE Network Bulk Statistics Support • All traffic facilitated by a context (known as a policy ACL) • An individual subscriber • All subscriber sessions facilitated by a specific context There are two primary components of an ACL: • Rule: A single ACL consists of one or more ACL rules. As discussed earlier, the rule is a filter configured to take a specific action on packets matching specific criteria. Up to 128 rules can be configured per ACL.
HeNB Gateway in Wireless LTE Network Congestion Control and Management Support When the Web Element Manager is used as the receiver, it is capable of further processing the statistics data through XML parsing, archiving, and graphing. The Bulk Statistics Server component of the Web Element Manager parses collected statistics and stores the information in the PostgreSQL database.
HeNB Gateway in Wireless LTE Network DSCP Marking on S1-U Relay DSCP Marking on S1-U Relay Cisco supports the DSCP marking of S1-U traffic traversing the HeNB-GW. This functionality on HeNB-GW is supported through command line interface (CLI). CLI configuration capability has been enabled for DSCP marking for both Access and Network service. CLIs are used for the dscp marking configuration for IP packets sent out on the S1-U interface, from the HeNB-GW to the Access/Network side.
HeNB Gateway in Wireless LTE Network Troubleshooting Features Support task should not be started on a PSC in which SMGRs are started. Regardless of whether session recovery is enabled or not, the HENBGW DEMUX task should always be started on the Demux PSC.
HeNB Gateway in Wireless LTE Network X2 Handover Procedure Support The above listed in addition to the existing facilities can be enabled to capture logs at different levels, for example: information, trace, debug etc. Important For more information on troubleshooting, refer the Troubleshooting the Service chapter of this guide.
HeNB Gateway in Wireless LTE Network Cell Broadcast Support Cell Broadcast Support The Cell Broadcast Support is in compliance with the Warning system aspects of the S1-MME interface between eNodeB and MME, and the S1AP protocol defined by the 3GPP specification TS 36.413 Release 10. S1AP Messages supported by HeNBGW for CMAS • Write Replace Warning Request • Write Replace Warning Response • Kill Request • Kill Response All the above messages are supported in the protocol monitor trace.
HeNB Gateway in Wireless LTE Network 3GPP Standard Support for Overload Control 7 On receiving a Kill request for an existing AWR, HeNGBW will forward the request to all HeNB as per WAL IE in the request message • The HeNBGW will collect the responses from the HeNBs and send a single Kill Response to the MME from which the KILL request was received. • A configurable wait for response timer will be used.
HeNB Gateway in Wireless LTE Network DHCPv4 Proxy support for HeNBGW with IPSec ◦Combine the MME Code list from all MMEs and discard duplicates End For ◦HeNBGW's logic eNB shall populate aggregated GUMMEI list from all MMEs in a MME-pool in the S1 SETUP Response message to HeNB. ◦GUMMEI list status changes for any MME (i.e.
HeNB Gateway in Wireless LTE Network HeNBGW Multi Operator Core Network (MOCN) 3 The PNR then receives these DHCP requests maintains a mapping between the LTE FAP ID and the assigned "Inner" IP Address 4 The RMS queries the PNR to get the LTE FAP inner IP Address, to use this inner IP Address to send TR-069 Connection Requests to the LTE FAP.
HeNB Gateway in Wireless LTE Network HeNBGW Multi Operator Core Network (MOCN) Below diagram depicts complete radio network shared among different operators, while each operator maintains its own separate core network. Figure 9: Multi Operator Core Network Architecture Limitations & Assumptions Below are the limitations and assumptions for HeNBGW MOCN feature. • HENB will send list of PLMNs and TAC to the HeNBGW with S1 Setup Request message.
HeNB Gateway in Wireless LTE Network HeNBGW Multi Operator Core Network (MOCN) • Each TAIDB list associated for a logical EnodeB shall be configured with only one PLMN. If operator has multiple PLMNs then, configure different PLMNs in multiple TAIDB list and associate each to a different logical ENB. • HeNBGW now support up to 256 TAIs per TAIDB. Given max of 8 logical EnodeBs, it can support up to (8*256) 2048 unique TAIs.
HeNB Gateway in Wireless LTE Network HeNBGW Multi Operator Core Network (MOCN) Initial UE Message / MME selection Figure 10: Modified NAS Node Selection function (NNSF) HeNB-GW Administration Guide, StarOS Release 19 26
HeNB Gateway in Wireless LTE Network s1ap-reset/partial-reset messages from HeNBGW • When UE's connect to the HeNB they indicate to the PLMN they want to connect. Based on the UE's choice, the HeNB populates the TAI corresponding to the selected PLMN in the S1AP Initial UE Message. • The HeNBGWs modified NAS Node Selection Function (NNSF) only routes this S1AP message to one of the MMEs of a logical HeNBs that supports the selected PLMN in their S1AP Setup Request Response or S1AP MME Configuration Update.
HeNB Gateway in Wireless LTE Network X2 Proxy Gateway support • Sends Full/Partial RESET messages with the list of UEs associate to the MME and forwards to the corresponding HeNBs. Full/Partial Reset messages generated towards MME • If one of the HeNB association goes down, deletes all the UEs corresponding to HeNB. • Sends Partial RESET messages with the list of UEs corresponding to the HeNB and forwards to the associated MMEs.
HeNB Gateway in Wireless LTE Network X2 Proxy Gateway support This section describes the EUTRAN Architecture from 3GPP 36.300. Figure 11: E-UTRAN Architecture from 3GPP 36.300 Figure 12: X2 GW logical architecture from 3GPP 36.
HeNB Gateway in Wireless LTE Network Features and Functionality - Optional Enhanced Feature Software Limitations Below are the limitations for the Proxy X2 Gateway support feature. • Session Manager Crash/Recovery will not recover SCTP associations. • Multi-homing not supported towards (H)enbs. • IPv6 peers support will be part of later releases. • Integrated IPsec/SecGW support will be part of later releases. • X2GWDemux task recovery support will be part of later releases.
HeNB Gateway in Wireless LTE Network Automatic Neighbor Relation (ANR) Support Important Some of the following features may require the purchase of an additional license to implement the functionality with the HeNB-GW service. This section describes following features: • Automatic Neighbor Relation (ANR) Support, on page 31 • CSG-ID Based Paging Optimization Support, on page 31 • License-based Control for No. of HeNB Connections, on page 32 • License-based Control for No.
HeNB Gateway in Wireless LTE Network License-based Control for No. of HeNB Connections Important This feature makes dependency on MME to initiate Paging messages containing CSG list. License-based Control for No. of HeNB Connections Number of HeNBs connecting to the HeNB-GW are controlled/limited based on the license configuration. Important SNMP traps are generated during Over/Under License capacity situation.
HeNB Gateway in Wireless LTE Network Session Recovery Enhancements Important For troubleshooting License related issues, refer the Troubleshooting the Service chapter of this guide. Session Recovery Enhancements The HeNBGW is the concentrator of HeNBs. Session Recovery feature of HeNBGW will enable it to best-effort attempt to recover from software and hardware faults.
HeNB Gateway in Wireless LTE Network Session Recovery Enhancements HeNB-GW Administration Guide, StarOS Release 19 34
CHAPTER 2 Understanding the Service Operation The system provides wireless carriers with a flexible solution for providing Security Gateway (SeGW) and Home-eNodeB Gateway (HeNB-GW) functionality for LTE Femtocell networks. The system functioning as an HeNB-GW is capable of supporting the following types of subscriber sessions: • PS Session over S1AP: The subscriber is provided packet switch connection with different traffic class on PS session with P-GW in PS.
Understanding the Service Operation Logical Interfaces In HeNB-GW service implementation, the contexts can be classified into source or destination contexts. This is because GTP-U tunnels as well as HeNB-GW Access and Network services can be created over a single context. The IP addresses as well as interfaces can also under the defined under the same context.
Understanding the Service Operation Bindings Important RADIUS/AAA is only applicable when SeGW is co-located with HeNB-GW. In the roaming case, the 3GPP AAA Proxy can act as a stateful proxy between the SeGW and 3GPP AAA Server. The AAA server is responsible for transfer of subscription and authentication data for authenticating/authorizing user access and UE authentication. The SeGW communicates with the AAA on the PLMN using DIAMETER protocol.
Understanding the Service Operation Services and Networks ◦HeNB-GW Access Service: This service is configured under the Context Configuration Mode in order to initialize the HeNB-GW functionality. The configuration of this service controls the functionality of S1-MME interface between HeNB-GW and the HeNBs. This service is bound to a local SCTP end-point address (IP address) to listen the incoming SCTP associations from HeNBs.
CHAPTER 3 HeNB-GW Service Configuration Procedures This chapter is meant to be used in conjunction with the other chapters that describes the information needed to configure the system to support HeNB-GW functionality for use in HeNB access networks. It is recommended that you identify the options from the previous chapters that are required for your specific deployment. You can then use the procedures in this chapter to configure those options.
HeNB-GW Service Configuration Procedures Information Required to Configure the System as an HeNB-GW Information Required to Configure the System as an HeNB-GW This section provides a high-level series of steps and the associated configuration file examples for configuring the system to perform as an HeNB-GW node in a test environment. Important The following sections describe the minimum amount of information required to configure and make the HeNB-GW operational on the LTE Femtocell network.
HeNB-GW Service Configuration Procedures Required Source Context Configuration Information Required Source Context Configuration Information Table 2: Required Information for Source Context Configuration Required Information Description Source context name An identification string from 1 to 79 characters (alpha and/or numeric) by which the Source context is recognized by the system.Generally it is identified as source context.
HeNB-GW Service Configuration Procedures Required Destination Context Configuration Information Required Information Description S1-AP Configuration (To/from Home-eNodeB) HeNB-GW access service Name An identification string from 1 to 63 characters (alpha and/or numeric) by which the HeNB-GW Access service can be identified on the system. It is configured in Context Configuration Mode. At a time, only one HeNB-GW Access Service can be configured per system.
HeNB-GW Service Configuration Procedures Required Destination Context Configuration Information Required Information Description S1-MME interface IP address IPv4/IPv6 addresses assigned to the S1-MME interface as SCTP bond address.This address will be used for binding the SCTP (local bind address(es)) to communicate with the MME using eGTP. The HeNB-GW passes this IP address during setting up the association with the MME.
HeNB-GW Service Configuration Procedures Required Destination Context Configuration Information Required Information Description Endpoint Name An identification string from 1 to 63 characters (alpha and/or numeric) by which the Diameter endpoint configuration is recognized by the system. This Diameter Endpoint is required by the SeGW to communicate with the AAA server. Origin realm name An identification string between 1 through 127 characters. The realm is the Diameter identity. The originator.
HeNB-GW Service Configuration Procedures Required Destination Context Configuration Information Required Information Description Logical eNodeB The Logical eNodeB configuration option enables the configuration of one or more logical eNodeBs within the HeNB-GW. The Logical eNodeB configuration is usually used to support load balancing within a pool of TAIs. At least one logical eNodeB configuration is required to START an HeNB-GW Network service.
HeNB-GW Service Configuration Procedures HeNB-GW Service Configuration Required Information Description MCC Mobile Country Code (MCC): The MCC can be configured to any integer value from 0 to 999. MNC Mobile Network Code (MNC): The MNC can be configured to any integer value from 0 to 999. Tracking Area Code (TAC) TAC is an integer value ranging from 0..65535. The HeNB-GW Network service searches these TACs for establishing UE connections.
HeNB-GW Service Configuration Procedures HeNB-GW Service Configuration Service Configuration example. These IP addresses are used to bind to different services including GTP-U Access and Network services and even interfaces like S1-MME. Step 3 Configure the Access and Network GTP-U services, as shown in the Access and Network GTP-U Services Configuration section of the HeNB-GW Service Configuration example. These services are bound individually to the IP addresses configured in the Step 2.
HeNB-GW Service Configuration Procedures HeNB-GW Service Configuration ip address 255.255.255.
HeNB-GW Service Configuration Procedures IPSec Configuration • is the IPv4 type address used to bind with the S1-MME interface. • is the MME pool name as defined while the LTE policy configuration. Important This MME pool is associated with the HeNB-GW network service. • is the tracking area information database name as defined while the LTE policy configuration.
HeNB-GW Service Configuration Procedures IPSec Configuration exit exit exit For Certificate Based Authentication Only Configure certificate name pem url private-key pem|der url|data ca-cert name pem|der url|data url or data format context ipsec transform-set exit ikev2-ikesa transform-set exit crypto template ikev2-dynamic authentication remote certificate aut
HeNB-GW Service Configuration Procedures GTP-U Service Configuration Notes: • is the context name on which unique EAP name is to configured. • is a string of size 1 to 128 which configure the context level unique Extensible Authentication Profile (EAP) Name. • configures the context level name to be used for the IKEv2 IKE Security Association Transform Set. It is a string of size 1 to 127.
HeNB-GW Service Configuration Procedures Verifying HeNB-GW Configuration tai mcc mnc tac exit end Notes: • is a string of size 1 to 63, which configures a specified MME pool. • is a string of size 1 to 63, which configures a specific MME. • is the remote SCTP IP address for S1 association to configured MME. • is the SCTP port which is an integer ranging from 1 to 65535.
HeNB-GW Service Configuration Procedures Displaying Logging Facility Important This section provides the minimum instruction set for configuring logging facilities for system monitoring that allows the user to monitor the events and logging. commands that configure additional logging facilities are provided in the Exec Mode Command chapter of Command Line Interface Reference.
HeNB-GW Service Configuration Procedures SNMP MIB Traps for HeNB-GW Service snmp trap { enable | suppress} HenbgwAccessServiceStop [ target ] snmp trap { enable | suppress} HenbgwMMESCTPAllAssocDown [ target ] snmp trap { enable | suppress} HenbgwMMESCTPAllAssocDownClear [ target ] snmp trap { enable | suppress} HenbgwMMESCTPAssocDown [ target ] snmp trap { enable | suppress} HenbgwMMESCTPAssocUp [ target ] snmp trap { enable |
HeNB-GW Service Configuration Procedures Event IDs for HeNB-GW Service Important For more information on SNMP trap configuration and supported object ids, refer System SNMP-MIB Reference. Event IDs for HeNB-GW Service Identification numbers (IDs) are used to reference events as they occur when logging is enabled on the system. Logs are collected on a per facility basis. Each facility possesses its own range of event IDs as indicated in the following table.
HeNB-GW Service Configuration Procedures DHCP Configuration DHCP Configuration To configure DHCP Proxy interface support on chassis for HeNB-GW service: Step 1 Step 2 Step 3 Create a DHCP service specific to HeNB-GW service by applying the example configuration in the Configuring DHCP Service section.
HeNB-GW Service Configuration Procedures Configuring Subscriber Template for HeNB Notes: • is name of the source context in which Security gateway is configured. • is name of the pre-configured DHCP service configured in Context Configuration mode for DHCP interface support in HeNB-GW service. • For more commands and keyword options, refer Command Line Interface Reference.
HeNB-GW Service Configuration Procedures Configuring Subscriber Template for HeNB HeNB-GW Administration Guide, StarOS Release 19 58
CHAPTER 4 Multi HeNBGW Access Services support This chapter describes Multi HeNBGW Service support, below are the links to the main sections of the document: • Feature Description, page 59 • How It Works, page 60 Feature Description Currently a single HeNBGW Access service is supported in StarOS. As part of this feature, multiple HeNBGW Access services will be supported. There will be no change in the number of HeNBGW Network services.
Multi HeNBGW Access Services support How It Works How It Works Configuring Multiple Access Services An HENBGW Access service is defined in a VPN context. A minimum of the following critical parameters must beconfigured in an access service to move the service to started state: • SCTP bind address • SCTP bind port • MME group id and PLMN ID • HENBGW Network service • GTPU services if S1U is enabled A maximum of 16 HENBGW Access services in the same or different VPN contexts can be configured.
CHAPTER 5 Monitoring the HeNB-GW Service This chapter provides information for monitoring service status and performance using the show commands found in the Command Line Interface (CLI). These commands have many related keywords that allow them to provide useful information on all aspects of the system ranging from current software configuration through call activity and status.
Monitoring the HeNB-GW Service Monitoring System Status and Performance To do this: Enter this command: View HeNB-GW session information specific to an S1 peer show henbgw session s1-peer ipv4-addr Monitoring HeNB and UE by Protocol Monitoring Monitor HeNB through Protocol Monitoring monitor protocol Use following protocol options for HeNB monitoring: • S1-AP • SCTP • GTP-U Monitor UE through Protocol Monitoring monitor protocol Use following protocol options for HeNB monitoring: • S1-AP • SCTP • GT
Monitoring the HeNB-GW Service Monitoring System Status and Performance To do this: Enter this command: View Session Statistics and Information Display Historical Session Counter Information View all historical information for all sample intervals show session counters historical Display Session Duration Statistics View session duration statistics show session duration Display Session State Statistics View session state statistics show session progress Display Session Subsystem and Task Statistics
Monitoring the HeNB-GW Service Monitoring Logging Facility To do this: Enter this command: View HeNB-GW Access Service Related Statistics View HeNB-GW Access service statistics filtered on an show henbgw-access-service statistics HeNB-GW Access service henbgw-access-service henbgw_access-svc_name verbose View HeNB-GW Access service statistics filtered by a peer id show henbgw-access-service statistics peer-id peer_identifier View HeNB-GW Access service S1AP statistics show henbgw-access-service statis
Monitoring the HeNB-GW Service Clearing Statistics and Counters To do this: Enter this command: Monitor logging facility based on user name used logging trace username name in session on system Monitor HeNB App logging facility on HeNB-GW system logging filter active facility henbapp level { critical | error | warning | unusual | info | trace | debug } Monitor HeNB-GW logging facility on HeNB-GW system logging filter active facility henbgw level { critical | error | warning | unusual | info | trace |
Monitoring the HeNB-GW Service Clearing Statistics and Counters HeNB-GW Administration Guide, StarOS Release 19 66
CHAPTER 6 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. • Test Commands, page 67 Test Commands In the event that an issue was discovered with an installed application or line card, depending on the severity, it may be necessary to take corrective action.
Troubleshooting the Service Using the SNMP TRAP command for debugging Keyword/Variable Description peer-address ip_addr Specifies the IP address of the HeNB node. NOTE: The IP address of the system's interface must be bound to a configured HeNB-GW service prior to executing this command. all Specifies that GTP-U echo requests will be sent to all Nodes that currently have sessions with the HeNB-GW service. gtpu-version { 0 | 1 } Specifies the the GTPU version of peer node.
Troubleshooting the Service Using the RESOURCES SESSION command for debugging In case, the number of sessions are over the license capacity, the output of this command looks as the following sample (only HeNB-GW related sessions have been shown): HENBGW Service: In Use Max Used Limit License Status HENBGW UE Service: In Use Max Used Limit License Status : : : : 2000 2000 ( Monday May 06 05:22:00 IST 2013 ) 2000 Over License Capacity (Rejecting Excess Calls) : : : : 2000 2000 ( Monday May 06 05:20:10 IS
Troubleshooting the Service Using the RESOURCES SESSION command for debugging HeNB-GW Administration Guide, StarOS Release 19 70
