Cisco Cisco ASR 5000 Technical Manual

Note: The action−profile parameter defines the action profile that is associated with the previously mentioned
policy type (minor, major, or critical).

The MME congestion control policy action profile is configurable under the lte−policy. Here is the CLI
syntax:

congestion−action−profile <profile_name>

The sections that follow describe the available actions that can be configured under the congestion action
profile.

This action causes a drop of new session requests when the congestion control threshold is reached. Here is
the CLI syntax:

It allows more granular control in regards to the type of requests/call events that should be dropped. Here are
the details:

Addn−brr−request: This drops packets that contain UE−initiated bearer resource requests. This is a
licensed keyword.

• 

Addn−pdn−connect: This drops packets that contain additional PDN context connections. This is a
licensed keyword.

• 

Brr−ctxt−mod−requests: This drops packets that contain bearer context modification requests. This is
a licensed keyword.

• 

Combined−attaches: This drops packets that contain combined attach requests.

• 

Handovers: This drops packets that contain handover attempts.

• 

Ps−attaches: This drops packets that contain packet−switched attach requests.

• 

S1−setups: This drops packets that contain S1 setup attempts. This is a licensed keyword.

• 

Service−requests: This drops packets that contain all service requests. This is a licensed keyword.

• 

Tau−requests: This drops packets that contain all of the tracking area update requests.

• 

These two options can also be configured with the previously mentioned call event type (both of these options
are license−controlled):

Lapi: This indicates that requests with Low Access Priority Indication (LAPI) will be dropped for the
call events; otherwise, both LAPI and non−LAPI events will be dropped. Here is the CLI syntax:

•