Cisco Cisco ASR 5000 Guía Para Resolver Problemas
[no] gtpc overload−protection Ingress
Here are some notes about this syntax:
no: This parameter disables the GTP inbound control message throttling for the GGSN/PGW services
in this context.
in this context.
•
msg−rate msg_rate: This parameter defines the number of GTP inbound messages that can be
processed per second. The msg_rate is an integer that ranges from one hundred to 12,000.
processed per second. The msg_rate is an integer that ranges from one hundred to 12,000.
•
delay−tolerance dur: This parameter defines the maximum number of seconds that an inbound GTP
message can be queued before it is processed. After this tolerance is exceeded, the message is
dropped. The dur is an integer that ranges from one to ten.
message can be queued before it is processed. After this tolerance is exceeded, the message is
dropped. The dur is an integer that ranges from one to ten.
•
queue−size size: This parameter defines the maximum queue size for the inbound GTP−C messages.
If the queue exceeds the defined size, then any new inbound messages are dropped. The size is an
integer that ranges from one hundred to 10,000.
If the queue exceeds the defined size, then any new inbound messages are dropped. The size is an
integer that ranges from one hundred to 10,000.
•
You can use this command in order to enable the GTP inbound control message throttling for the
GGSN/PGW services that are configured in the same context. As an example, this command enables the
inbound GTP control messages in a context with a message rate of 1,000 per second, a message queue size of
10,000, and a delay of one second:
GGSN/PGW services that are configured in the same context. As an example, this command enables the
inbound GTP control messages in a context with a message rate of 1,000 per second, a message queue size of
10,000, and a delay of one second:
gtpc overload−protection ingress msg−rate 1000 delay−tolerance 1 queue−size 10000
Neighbor Network Element Protection
Many neighbor network elements use their own mechanisms in order to protect themselves, and additional
network overload protection on the ASR5x00 side might not be needed. Protection of the neighbor network
elements might be required in cases where the overall network stability can be reached only when message
throttling is applied on the egress side.
network overload protection on the ASR5x00 side might not be needed. Protection of the neighbor network
elements might be required in cases where the overall network stability can be reached only when message
throttling is applied on the egress side.
Network Overload Protection with Diameter Throttling on an S6a
Interface
Interface
This feature protects the S6a and S13 interfaces in the egress direction. It protects the Home Subscriber Server
(HSS), the Diameter Routing Agent (DRA), and the Equipment Identity Register (EIR). The feature uses the
Rate Limiting Function (RLF).
(HSS), the Diameter Routing Agent (DRA), and the Equipment Identity Register (EIR). The feature uses the
Rate Limiting Function (RLF).
Consider these important notes when you apply the diameter endpoint configuration:
An RLF template must be associated with the peer.
•
An RLF is attached only on a per−peer basis (individually).
•
Configure Diameter Throttling on an S6a Interface
Here is the command syntax that is used in order to configure diameter throttling on an S6a interface:
[context_na>me]host_name(config−ctx−diameter)#>peer [*] peer_name [*]
[ realm realm_name ] { address ipv4/ipv6_address [ [ port port_number ]
[connect−on−application−access] [ send−dpr−before−disconnect disconnect−cause
disconnect_cause ] [ sctp ] ] + | fqdn fqdn [ [ port port_number ]
[ send−dpr−before−disconnect disconnect−cause disconnect_cause ]
[ rlf−template rlf_template_name ] ] }