Cisco Cisco Packet Data Interworking Function (PDIF)
show lte-policy
▀ show lte-policy congestion-action-profile name
▄ Statistics and Counters Reference, StarOS Release 18
4110
show lte-policy congestion-action-profile name
Table 436.
show lte-policy congestion-action-profile name
Command Output Descriptions
Field
Description
handovers
Indicates the action the MME is configured to take for handovers when a congestion control
threshold is reached. Possible actions are none (ignore), reject, drop.
threshold is reached. Possible actions are none (ignore), reject, drop.
combined-attaches
Indicates the action the MME is configured to take for combined Attach requests when a congestion
control threshold is reached. Possible actions are none (ignore), reject, drop.
control threshold is reached. Possible actions are none (ignore), reject, drop.
ps-attaches
Indicates the action the MME is configured to take for packet switched Attach requests when a
congestion control threshold is reached. Possible actions are none (ignore), reject, drop.
congestion control threshold is reached. Possible actions are none (ignore), reject, drop.
addn-pdn-connects
Indicates the action the MME is configured to take for additional PDN context connections when a
congestion control threshold is reached. Possible actions are none (ignore), reject, drop.
congestion control threshold is reached. Possible actions are none (ignore), reject, drop.
addn-brr-requests
Indicates the action the MME is configured to take for additional bearer requests when a congestion
control threshold is reached. Possible actions are none (ignore), reject, drop.
control threshold is reached. Possible actions are none (ignore), reject, drop.
brr-ctxt-mod-requests
Indicates the action the MME is configured to take for Bearer Resource Context Modification
Requests when a congestion control threshold is reached. Possible actions are none (ignore), reject,
drop.
Requests when a congestion control threshold is reached. Possible actions are none (ignore), reject,
drop.
service-request
Indicates the action the MME is configured to take for service requests when a congestion control
threshold is reached. Possible actions are none (ignore), reject, drop.
threshold is reached. Possible actions are none (ignore), reject, drop.
tau-request
Indicates the action the MME is configured to take for TAU requests when a congestion control
threshold is reached. Possible actions are none (ignore), reject, drop.
threshold is reached. Possible actions are none (ignore), reject, drop.
s1-setups
Indicates the action the MME is configured to take for S1 setup attempts when a congestion control
threshold is reached. Possible actions are none (ignore), reject, drop.
threshold is reached. Possible actions are none (ignore), reject, drop.
init-ues
Indicates the action the HeNBGW is configured to take for Initial UE messages received when a
congestion control threshold is reached. Possible actions are none (ignore), reject, drop.
congestion control threshold is reached. Possible actions are none (ignore), reject, drop.
paging
Indicates the action the HeNBGW is configured to take for Paging requests when a congestion
control threshold is reached. Possible actions are none (ignore), reject, drop.
control threshold is reached. Possible actions are none (ignore), reject, drop.
exclude-emergency-events Indicates whether the MME is configured to exclude emergency calls when a congestion control
threshold is reached. This setting is disabled when ‘no exclude-emergency-events’ is displayed.
exclude-voice-events
Indicates whether the MME is configured to exclude voice calls when a congestion control threshold
is reached. This setting is disabled when ‘no exclude-voice-events’ is displayed.
is reached. This setting is disabled when ‘no exclude-voice-events’ is displayed.
report-overload
Indicates whether the MME is configured to report overload conditions to eNodeBs to alleviate
congestion scenarios.
congestion scenarios.