Cisco Cisco Packet Data Gateway (PDG) Prospecto
Global Configuration Mode Commands (L-S)
network-overload-protection mme-new-connections-per-second ▀
Cisco ASR 5x00 Command Line Interface Reference ▄
5181
queue-size queue_size
Defines the maximum size of the pacing queue used for buffering the packets. If configured, the queue-size
should be greater than or equal to the
should be greater than or equal to the
#_new_connections
value and less than or equal to the optimal value
(the
wait_time
*
#_new_connections
). This validation is done in the CLI.
queue_size
Must be an integer from 250 to 25000.
Default: unconfigured. The default value is the
#_new_connections
*
wait-time
. This will be the
optimal value.
wait-time wait_time
Defines the maximum life-time (number of seconds) of the packets in the queue beyond which the packets
are considered to be “stale” and are dropped.
are considered to be “stale” and are dropped.
wait_time
Must be an integer from 1 to 15
Default: 5
Usage
Use this command to configure attach rate throttling on the MME.
When enabled, new connections (except emergency requests) are buffered and paced through the queue.
Messages in the queue are processed (FIFO) until they age-out when the queued message's lifetime crosses
the configured wait-time. The wait-time and the attach rate decide the optimal size of the queue. If the queue
is full, packets are rejected or dropped based on the configured action.
This feature functions at a system (chassis) level for all MME services. All MME services on the system are
controlled by a single pacing queue. For a combo MME-SGSN node, each type of service shall be controlled
by its own queue and its own configuration.
Emergency attaches are not be throttled when this feature is enabled.
When enabled, new connections (except emergency requests) are buffered and paced through the queue.
Messages in the queue are processed (FIFO) until they age-out when the queued message's lifetime crosses
the configured wait-time. The wait-time and the attach rate decide the optimal size of the queue. If the queue
is full, packets are rejected or dropped based on the configured action.
This feature functions at a system (chassis) level for all MME services. All MME services on the system are
controlled by a single pacing queue. For a combo MME-SGSN node, each type of service shall be controlled
by its own queue and its own configuration.
Emergency attaches are not be throttled when this feature is enabled.
Important:
This command is available only if a valid license (MME Resiliency) is installed. Contact your Cisco
account representative for more information.
Example
Configure the new connections per second rate at 2500, reject all (non-emergency) attaches and TAU
requests, and drop forward relocation requests if the new connection rate is exceeded. Rejects will return
emm cause code “Congestion”.
requests, and drop forward relocation requests if the new connection rate is exceeded. Rejects will return
emm cause code “Congestion”.
network-overload-protection mme-new-connections-per-second 2500 action
attach reject-with-emm-cause congestion tau reject-with-emm-cause
congestion fwd-reloc drop ddn drop wait-time 5
attach reject-with-emm-cause congestion tau reject-with-emm-cause
congestion fwd-reloc drop ddn drop wait-time 5
Set the attach rate to 500 per second, the same actions as the previous example, but set the wait time to 5
seconds, and the queue size to be calculated (as follows:
seconds, and the queue size to be calculated (as follows:
wait_time
*
#_new_connections
- i.e., 2500)
network-overload-protection mme-new-connections-per-second 500 action
attach reject-with-emm-cause congestion tau reject-with-emm-cause
congestion fwd-reloc drop ddn drop wait-time 5 5
attach reject-with-emm-cause congestion tau reject-with-emm-cause
congestion fwd-reloc drop ddn drop wait-time 5 5