Cisco Cisco ASR 5000 Technical Manual

Here are some notes about this syntax:

Message Type/call Event: When the SM messages policy is defined, it is applied to all of the activate
or modification requests. For this reason, the message/call event type is required in this CLI
command.

• 

Actions: This defines the actions to be completed when the SGSN receives the previously mentioned
message and the congestion control threshold has been reached. The reject action instructs the SGSN
to reject the SM messages when the congestion control threshold has been reached.

Note: The reject actions can further be refined for LAPI and APN−based. The low−priority−ind−ue
and apn−based keywords are used with the drop/reject actions.

• 

low−priority−ind−ue: This instructs the SGSN to reject the SM message only if the message from the
UE includes a LAPI when the congestion control threshold has been reached.

• 

apn−based: This instructs the SGSN to reject the SM messages based on the APN if the congestion
control threshold has been reached. This only occurs if the APN is configured under the operator
policy with congestion control.

Note: If the congestion action profile is configured with both the LAPI and APN−based options, then
the new call events are rejected only if both of the conditions are matched.

• 

The congestion control threshold defines the threshold values for the various parameters that can invoke
congestion control when the threshold is exceeded. Here is the CLI syntax:

 max−sessions−per−service−utilization <percent> |  message−queue−utilization <percent>

| message−queue−wait−time <time> | port−rx−utilization <percent> | port−specific

 { <slot/port> | all } [ tx−utilization <percent> ] [ rx−utilization <percent> ]

port−specific−rx−utilization critical | port−specific−tx−utilization critical |

 port−tx−utilization <percent> | service−control−cpu−utilization

<percent> | system−cpu−utilization <percent> | system−memory−utilization <percent>

| tolerance <percent> }

Here are the different parameters that can be configured with threshold values and can trigger congestion

control when the threshold has been reached:

License−utilization: This parameter defines the percent utilization of the licensed capacity, as
measured in ten−second intervals. This value is formatted as a percentage and can range between zero
and one hundred (the default value is one hundred).

• 

max−sessions−per−service−utilization: This parameter defines the percent utilization of the
maximum sessions allowed per service, as measured in real−time. This threshold is based on the
maximum number of sessions, or the PDP context that is configured for a particular service. This
value ranges between zero and one hundred, with a default value of 80.

• 

message−queue−utilization: This parameter defines the percent utilization of the DEMUX manager
software task message queue, as measured in ten−second intervals. This queue has the capability to
store 10,000 messages. This value ranges between zero and one hundred, with a default value of 80.

• 

message−queue−wait−time: This parameter defines the maximum time (in seconds) that a message
can remain in the queue, as measured by the packet time stamps. This value ranges between one and

•