- About this Guide
- Mobility Management Entity Overview
- Mobility Management Entity Configuration
- 128K eNodeB Connections
- A-MSISDN Functionality
- Access Restriction based on Regional Zone Code
- APN Override
- Backup and Recovery of Key KPI Statistics
- Cause Code #66
- Cell Broadcast Center - SBc Interface
- Cell Traffic Trace
- Closed Subscriber Groups
- CSFB and SMS over SGs Interface
- CSFB for 1xRTT
- DDN Throttling
- Default APN for DNS Failure
- eDRX Support on the MME
- Emergency Bearer Services
- Enhanced Congestion Control and Overload Control
- Enhanced Multimedia Priority Service (eMPS)
- Enhanced Event Logging
- Foreign PLMN GUTI Management
- GTP-C Load and Overload Control on MME
- GUTI Re-allocation
- Heuristic and Intelligent Paging
- HSS-based P-CSCF Restoration
- Idle-mode Signaling Reduction
- IMSI Manager Overload Control
- IMSI Manager Scaling on the MME
- Integrity and Confidentiality Algorithms for UE
- IPNE Service
- Limiting the Number of SGWs Tried
- Load Balancing and Rebalancing and VoLTE Offloading
- Local Emergency Numbers List
- Location Services
- MBMS for MME (eMBMS)
- Operator Policy
- Operator Specific QCI
- Operator Policy Selection Based on IMEI-TAC
- Overcharging Protection
- Paging Priority IE Support
- Power Saving Mode (PSM) in UEs
- QoS Profile Support
- S13 Additional IMEI Check
- Selective Authentication
- Session Tracing
- SGW Blacklisting on the MME
- SGSN-MME Combo Optimization
- Single Radio Voice Call Continuity
- SRVCC for 1xRTT
- State-Location Information Retrieval Flag
- TAI-based Routing for 20-bit and 28-bit eNB ID
- Timer-based GBR Bearer Deactivation
- UDPC2 Support for MME/SGSN
- UE Relocation
- VLR Management
- Troubleshooting the MME Service
- Monitor the MME Service
- Engineering Rules
Troubleshooting
the MME 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
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.
The system provides several redundancy and fail-over mechanisms to address issues with application and line cards in order to minimize system downtime and data loss. These mechanisms are described in the sections that follow.
Using the eGTPC Test Echo Command
This command tests the eGTP service's ability to exchange eGTPC packets with the specified peer which can be useful for troubleshooting and/or monitoring.
The test is performed by the system sending eGTP-C echo request messages to the specified peer(s) and waiting for a response.
This command must be executed from within the context in which at least one eGTP service is configured.
egtpc test echo peer-address peer_ip_address src-address egtp_svc_ip_address
Keyword/Variable | Description |
---|---|
peer-address peer_ip_address | Specifies that eGTP-C echo requests will be sent to a specific peer (HSS).ip_address is the address of the HSS receiving the requests. |
src-address egtp_svc_ip_address | Specifies the IP address of a S6a interface configured on the
system in eGTP service.
NOTE: The IP address of the system's S6a interface must be bound to a configured eGTP service prior to executing this command. |
EGTPC test echo -------------- Peer: 172.10.10.2 Tx/Rx: 1/1 RTT(ms): 2 (COMPLETE) Recovery: 10 (0x0A)