Cisco Cisco Packet Data Gateway (PDG) Veröffentlichungshinweis
MME Changes in Release 15.0
▀ MME Enhancements for 15.0 MR6
▄ Cisco ASR 5x00 Release Change Reference
286
The
show lte-policy paging-map name map_name
command allows you to see the precedence information
configured, for example:
asr5000# show lte-policy paging-map name pm1
=====================================================================
Paging Map : pm1
=====================================================================
Precedence 1 : Signaling-IDR ; Paging is performed as per paging-profile pp1
--------------------------------------------------------------------
show hss-peer-service statistics
In support of the new 'State/Location Information Retrieval' flag functionality, new counters have been added to the
output generated by the
output generated by the
show hss-peer-service statistics
command :
Asynchronous Message Stats:
Asynchronous ISDR Req
Asynchronous ISDA
Aynchronous ISDA Dropped
CSCur27407 - NewConnectionsDisallowed SNMP trap firing a lot
Feature Changes
Processing SessMgr Location
Previous Behavior: When the SessMgr Location procedure failed during the MME's processing of a received request
(Attach / TAU request with FGUTI, GTPv2 Forward Relocation request, and GTPv1 Forward Relocation request), then
the MME rejects the request and sends a trap "MMENewConnectionsDisallowed" with reason "location of sessmgr
resource failed".
(Attach / TAU request with FGUTI, GTPv2 Forward Relocation request, and GTPv1 Forward Relocation request), then
the MME rejects the request and sends a trap "MMENewConnectionsDisallowed" with reason "location of sessmgr
resource failed".
New Behavior: If the SessMgr Location procedure fails during the MME's processing of a received request (Attach /
TAU request with FGUTI, GTPv2 Forward Relocation request, and GTPv1 Forward Relocation request), then a new
SessMgr is allocated, the request is processed, and the MME does not send the trap "MMENewConnectionsDisallowed"
with reason "location of sessmgr resource failed".
TAU request with FGUTI, GTPv2 Forward Relocation request, and GTPv1 Forward Relocation request), then a new
SessMgr is allocated, the request is processed, and the MME does not send the trap "MMENewConnectionsDisallowed"
with reason "location of sessmgr resource failed".
Customer Impact: Fewer requests rejected.