Enabling Congestion Control Redirect Overload Policy
To create a congestion control policy and configure a redirect overload policy for the service, apply the
following example configuration:
configure
congestion-control
context context_name
{service_configuration_mode}
policy overload redirect address
end
Notes:
•
Optional:
If the congestion control policy action was configured to
redirect
, then a redirect overload
policy must be configured for the service(s) that are affected.
•
There are several service configuration modes that you can configure. See the
Command Line Interface
Reference
for a complete list of modes.
•
You can set various options for redirection. See the
Command Line Interface Reference
for more
information.
•
Repeat this configuration example to configure overload policies for additional services configured in
the same context.
Verify the Service Overload Policies
To verify that the service overload policies were properly configured enter the following command in the
Exec Mode:
[local]
host_name
#
show service_type name service_name
This command lists the entire service configuration. Verify that the information displayed for the "Overload
Policy" is accurate.
Repeat this configuration example to configure additional services in other contexts.
Verify the Congestion Control Configuration
Verify MME Congestion Action Profiles
To verify MME multilevel congestion action profiles, run the following Exec mode command:
[local]
host_name
#
show lte-policy congestion-action-profile { name
profile_name
| summary }
Disconnecting Subscribers Based on Call or Inactivity Time
During periods of heavy system load, it may be necessary to disconnect subscribers in order to maintain an
acceptable level of system performance. You can establish thresholds to select subscribers to disconnect based
on the length of time that a call has been connected or inactive.
ASR 5500 System Administration Guide, StarOS Release 21.5
204
Congestion Control
Enabling Congestion Control Redirect Overload Policy