Cisco Cisco Packet Data Gateway (PDG)

Seite von 360
Congestion Control   
▀  Configuring Congestion Control 
 
 
▄  VPC-VSM System Administration Guide, StarOS Release 19 
200 
   
  mme-service: drop 
  henbgw-network-service: none 
  asngw-service: none 
  asnpc-service: none 
  phsgw-service: none 
  phspc-service: none 
  mipv6ha-service: none 
  lma-service: none 
  saegw-service: none 
  sgw-service: none 
  pgw-service: none 
  hnbgw-service: none 
  pcc-policy-service: none 
  pcc-quota-service: none 
  pcc-af-service: none 
  ipsg-service: none 
  samog-service: none 
The primary threshold to observe is license utilization. This threshold is defaulted to 80%. Overload controls on the 
system enables the Congestion-control Policy when the system has only 80% of the licenses used. The overload 
condition will not clear until the utilization drops below the tolerance limit setting. The tolerance limit is defaulted to 
10%. If the system goes into overload due to license utilization (threshold at 80%), the overload condition will not clear 
until the license utilization reaches 70%. 
The system may go into overload if threshold settings are set too low and congestion control is enabled. You will need 
to review all threshold values and become familiar with the settings. 
Since the recommendation for license utilization overload threshold is 100%, you should enable a license threshold 
alarm at 80%. An alarm is then triggered when the license utilization hits 80%. When the congestion-control policy 
setting is set to drop, the system drops incoming packets containing new session requests. 
Important:
  For additional information on configuring the alarm threshold, refer to the Threshold Configuration 
Guide
Verify MME Congestion Action Profiles 
To verify MME multilevel congestion action profiles, run the following Exec mode command: