Cisco Cisco ASR 5000 Technical Manual
Lapi: This indicates that requests with LAPI will be rejected for the call events; otherwise, both LAPI
and non−LAPI events will be rejected. Here is the CLI syntax:
and non−LAPI events will be rejected. Here is the CLI syntax:
reject <call−event> lapi
•
Apn−based: This indicates that requests for the APNs that are configured for the congestion control in
operator policy will be rejected. Here is the CLI syntax:
operator policy will be rejected. Here is the CLI syntax:
reject <call−event> lapi
Note: The apn network−identifier command in the operator policy is used in order to configure the
congestion control for an APN.
congestion control for an APN.
•
Note: If the congestion action profile is configured with both the LAPI and APN−based options, then the call
events are rejected only if both conditions are matched.
events are rejected only if both conditions are matched.
Report Overload
This enables the MME to report overload conditions to the eNodeBs in order to alleviate congestion scenarios.
The MME invokes the S1 overload procedure with the S1AP Overload Start message in order to report the
overload condition to the specified proportion of eNodeBs to which the MME has an S1−interface connection.
The MME invokes the S1 overload procedure with the S1AP Overload Start message in order to report the
overload condition to the specified proportion of eNodeBs to which the MME has an S1−interface connection.
The MME selects the eNodeBs at random. Two overloaded MMEs in the same pool do not send overload
messages to the same eNodeBs. When the MME has recovered and can increase its load, it sends an S1AP
overload Stop message. Here is the CLI syntax:
messages to the same eNodeBs. When the MME has recovered and can increase its load, it sends an S1AP
overload Stop message. Here is the CLI syntax:
report−overload { permit−emergency−sessions−and−mobile−terminated−services |
permit−highpriority−sessions−and−mobile−terminated−services |
reject−delay−tolerant−access | reject−new−sessions |
reject−non−emergency−sessions } enodeb−percentage <percent>
These are the options that can be configured with this action:
permit−emergency−sessions−and−mobile−terminated−services: This specifies in the overload
message to the eNodeB that only emergency sessions are allowed to access the MME during the
overload period.
message to the eNodeB that only emergency sessions are allowed to access the MME during the
overload period.
•
permit−high−priority−sessions−and−mobile−terminated−services: This specifies in the overload
message to the eNodeB that only high priority sessions and mobile−terminated services are allowed to
access the MME during the overload period.
message to the eNodeB that only high priority sessions and mobile−terminated services are allowed to
access the MME during the overload period.
•
reject−delay−tolerant−access: This specifies in the overload message to the eNodeB that
delay−tolerant access destined for the MME should be rejected during the overload period.
delay−tolerant access destined for the MME should be rejected during the overload period.
•
reject−new−sessions: This specifies in the overload message to the eNodeB that all new connection
requests destined for the MME should be rejected during the overload period.
requests destined for the MME should be rejected during the overload period.
•
reject−non−emergency−sessions: This specifies in the overload message to the eNodeB that all
non−emergency sessions should be rejected during the overload period.
non−emergency sessions should be rejected during the overload period.
•
enobeb−percentage: This configures the percentage of known eNodeBs that will receive overload
report.
report.
•