Skipped - Displays the number of times when the session manager skips sending paging request to at least 1 busy MME manager Stage-1 / Stage-2 / Stage-3 / Stage-4 / Stage-5:Īttempted - Displays the number of times when the session manager sends paging request to at least 1 MME manager for the stage. Profile name - Displays the name of the configured paging profile. The output of this command includes the following fields: Show mme-service statistics paging-profile profile-name

show session subsystem facility mmemgr all.

show mme-service statistics paging-profile profile-name.

This section provides information regarding show commands and their outputs for the Paging Congestion feature. This section provides information regarding show commands and bulk statistics available to monitor and troubleshoot the Paging Show lte-policy paging-profile name profile-name Monitoring and Troubleshooting Use the following commands to verify the stage wise paging criticality configured per paging-profile: Stage-1ĭefault: Stage-1 is considered as critical if the operator does not configure paging criticality for any paging stages. No : Disables the paging criticality that is configured for all paging stages and applies the default configuration. Paging_stage specifies the paging stage precedence as an integer from 1 to 5 where 1 is the highest and 5 is the lowest.Ī maximum number of 5 entries are accepted. The paging procedure continues even when the MMEMgr is busy. paging_profile_name must be an alphanumeric string of 1 to 64 characters.Ĭritical paging_stage: Enables the paging criticality for the specified paging stages. If the profile name does not refer to an existing profile,Ī new profile is created. Paging-profile paging_profile_name: Specifies the name of the paging profile being created or accessed. Use the following configuration to enable paging criticality and continue the paging procedure even when the MME manager isĬonfigure lte-policy paging-profile paging_profile_name critical paging_stage end show session subsystem facility mmemgr all Configuring Critical Paging Events Use the following command to view the Congestion Configuration, Congestion State, and History per MME Manager instance. tolerance_value must be an inetger from 1 to 100. Tolerance tolerance_value: Specifies the tolerance limit. threshold_value must be an inetger from 1 to 100. Threshold threshold_value: Specifies the thresholds for various resources. MME Manager is marked busy if CPU utilization is above threshold value and it will be marked not-busy once CPU utilizationĬomes back to threshold - tolerance value.Įntering the mme-manager command results in the following prompt and changes to the MME Manager Configuration mode:Ĭongestion-control : Enables or disables congestion control.Ĭpu-utilization : Specifies the average CPU utilization in %. Use the following configuration to enable or disable CPU Usage based congestion control for MME Manager(s), and configureĬongestion parameters (CPU Threshold and Tolerance values).Ĭonfigure mme-manager congestion-control cpu-utilization no congestion-control end This section provides information on the CLI commands to configure the Paging Congestion feature. Mark critical and non-critical stages under paging profileĭisable paging for critical and non-critical stages, even if MME Managers are busyĭisable paging of unregistered IMSIs for busy MME Managers if it is from SGS interfaceįor more information on the Heuristics Paging and Intelligent Paging, see the Heuristic and Intelligent Paging feature chapter in the MME Administration Guide.

MME supports the following functionalities:ĬPU congestion parameters for MME Managers - Threshold and Tolerance levels Heuristics Paging and Intelligent Paging procedures are used to reduce the volume of Paging In previous releases, MME supported the paging implementations/algorithms - Default Non-Heuristics Paging, Default Heuristics The existing Paging features are enhanced to control the paging events and messages during MME Manager CPU congestion to provide

Non-critical paging triggers/events and allowing critical paging events at the same time. The Auto Disabling of eNodeB Paging feature optimizes the volume of Paging events in congestion scenarios by disabling the Uneven Distribution of eNodeBs in MME ManagersĪuto Disable of Paging During MME Manager CPU Congestionįeature Summary and Revision History Summary Data.State-Location Information Retrieval Flag.

IMEI Check during Periodic TAU Support for NB IoT Devices.

Controlling IMS Voice Over PS Session in S1 Mode.

Auto Disable of Paging During MME Manager CPU Congestion.

Razorsql disable paging