Cisco Cisco ASR 5000
MTC Congestion Control
▀ Configuring MTC Congestion Control
▄ SGSN Administration Guide, StarOS Release 18
If an Attach Request or RAU Request or Service Request is rejected due to congestion, then the T3346 value
will be included in the reject message with GMM cause code 22 (congestion). The backoff timer value sent
will be chosen randomly from within the configured T3346 timer value range.
will be chosen randomly from within the configured T3346 timer value range.
If T3346 timer value is configured in a Call-Control Profile then it will override the backoff timer values defined
for either the SGSN Service or GPRS Service configurations.
The timer will be ignored if an Attach Request or RAU Request is received after congestion has cleared.
Verifying the T3346 Configurations
To verify the configuration for the 2G service, use the following command:
[local]SGSN1-NH# show gprs-service name service_name
To verify the configuration for the 3G service, use the following command:
[local]SGSN1-NH# show sgsn-service name service_name
To verify the configuration for the in the Call-Control Profile, use the following command:
[local]SGSN1-NH# show call-control-profile full name profile_name
Configuring O&M Triggered Congestion
Enabling Congestion
For operations and maintenance purposes (e.g., testing), this command triggers a congestion state at the global level.
sgsn trigger-congestion level { critical | major | minor }
Notes:
critical | major | minor
: Selecting one of the three congestion severity levels indicates the associated
congestion-action-profile to be chosen and applied. Reminder: the profile is associated with the severity level
with the
with the
congestion-control policy
command.
Disabling Congestion
For operations and maintenance purposes (e.g., testing), this command clears congestion triggered using the
sgsn
trigger congestion
command.
sgsn clear-congestion
Notes:
If the command is applied then the SGSN resumes normal operations and does not apply any congestion control
policy.