Guest

Cisco 10000 Series Routers

CAC Algorithm Improvements

Table Of Contents

PPP Session CAC Algorithm Improvements in RP

Contents

Restrictions for PPP Session CAC Algorithm Improvements

PPP Session CAC Algorithm Improvements in RP

Call Admission Control—Accept or Reject

Session Charge Improvements

Platform Support

Configuring PPP Session CAC Algorithm Improvements

Enabling the New Model of CAC

Configuring CAC Based on CPU Utilization

Configuring CAC Based on Session Charges

Configuring CAC Charges Using a Session Charge Profile

Configuration Example

Verifying and Monitoring CAC Operation

Verification Examples

Example of No Configuration for CAC

Example of Verifying CAC Configuration

Example of CAC Operation Using the Original CAC Model

Additional References

Related Documents

Standards

MIBs

RFCs

Technical Assistance

Command Reference

call admission

call admission cpu-limit

call admission limit

call admission load

call admission new-model

debug call-admission trace

show call admission statistics

Feature Information for PPP Session CAC Algorithm Improvements in RP


PPP Session CAC Algorithm Improvements in RP


First Published: September, 2008

This document describes improvements to the PPP session call admission control (CAC) algorithm in the route processor (RP).

Finding Feature Information in This Module

Your Cisco IOS software release may not support all of the features documented in this module. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported, use the "Feature Information for PPP Session CAC Algorithm Improvements in RP" section.

Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images

Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

Contents

Restrictions for PPP Session CAC Algorithm Improvements

PPP Session CAC Algorithm Improvements in RP

Platform Support

Configuring PPP Session CAC Algorithm Improvements

Configuration Example

Verifying and Monitoring CAC Operation

Verification Examples

Additional References

Command Reference

Feature Information for PPP Session CAC Algorithm Improvements in RP

Restrictions for PPP Session CAC Algorithm Improvements

You should be familiar with the Call Admission Control operation and have a basic understanding of broadband aggregation.

DHCP sessions are not subject to Call Admission Control.

Call Admission Control for broadband is supported on VPDN, PPPoE, and PPPoA sessions.

Leased line (serial) connections are not subject to Call Admission Control.

PPP Session CAC Algorithm Improvements in RP

The Call Admission Control (CAC) feature allows a router to deny incoming calls, thereby protecting service provider network resources. Accepting too many calls might make the router inefficient in its operation, overloading both its own CPU and external peripherals such as a RADIUS server. The PPP Session CAC Algorithm Improvements in RP feature protects these resources of the router by enhancing the behavior of CAC operations.

In broadband networks, the broadband remote access system (BRAS) can scale to handle a high incoming rate of sessions. Each session that attempts to establish on the BRAS consumes the CPU and memory resources of the BRAS. If the BRAS uses external resources, such as RADIUS, to set up each session, RADIUS might not be able to handle all of the requests the router generates.

CAC aids the BRAS router in accepting calls by limiting the number of incoming calls based on either CPU or session charges. CAC protects the BRAS and external peripherals from getting overloaded by numerous requests that might come in during peak times.

The following sections describe the improvements to CAC operation in Cisco IOS Release 12.2(31)SB13:

Call Admission Control—Accept or Reject

Session Charge Improvements

Call Admission Control—Accept or Reject

In releases earlier than Cisco IOS Release 12.2(31)SB13, accepting or rejecting calls by Call Admission Control (CAC) is based on either of the following CAC models:

CPU load model—CAC accepts and rejects calls based on a CPU load threshold that you set using the call admission limit and call admission load commands. Typically, you use CPU-based CAC when the router starts or when a link is going up and down (flaps). This allows the router to efficiently use resources and to provide the best call setup rates during these times of stress.

Session charge model—CAC accepts and rejects calls based on a session per second charge so that CAC can reduce the number of incoming calls per second, regardless of the CPU load. Sessions CAC streamlines a number of requests in case you are using a slower RADIUS server, thereby preventing RADIUS server overload.

In Cisco IOS Release 12.2(31)SB13 and later releases, call acceptance and rejection are based on more granular resource checks. If resources are available, CAC accepts the call. The following describes how the route processor (RP) checks CPU utilization and session charges to determine call acceptance or rejection:

CPU utilization—The RP polls the 5-second average system variable to determine the average 1-minute CPU load allowed on the system and compares that to the current CPU load. If the current CPU load is below the system variable limit, CAC accepts the call. If not, CAC rejects the call.


Note The CPU load variable is pre-computed and checking of this variable does not add any additional load to the CPU.


Session charges—The RP compares the existing outstanding session charges to a user-configurable system variable. If the session charges are below the system variable limit, CAC accepts the call and adds the session charges. If not, CAC rejects the call.


Note The session charges variable is pre-configured and checking of this variable does not require any additional computation.


In releases earlier than Cisco IOS Release 12.2(31)SB13:

Call admission control did not officially support session charge CAC. Cisco IOS Release 12.2(31)SB13 adds support for this.

The aggregate load computed by session charges, load charges, and buffer charges is compared to a single limit. The CAC improvements in Cisco IOS Release 12.2(31)SB13 add separate limits for session charge verification and load charge verification.


Note When permanent buffers are overused, CAC artificially sets the load charge to its maximum.


Session Charge Improvements

CAC adds session charges per session type (for example, VPDN, PPPoE, PPPoA). These session charges last for a configurable lifetime. After the configured lifetime expires, the CAC operation decrements the charge.

In Cisco IOS Release 12.2(31)SB13 and later releases, the RP compares the existing outstanding session charges to the configured limit.

If the session charges are:

Above the limit, CAC rejects the call.

Below the limit, CAC admits the call if the load charges are below the configured limit, and if resources are available CAC adds the session charges when the session is committed. Table 1 describes when the CAC check occurs and when sessions are committed.

Table 1 Description of the Times That Sessions are Committed 

Session
CAC Check
Session Committed

PPPoE

PADI Reception

A PPPoE Active Discovery Initiation (PADI) frame is received from the PPPoE client.

When the router sends a PPPoE Active Discovery Session (PADS) confirmation packet to the requesting host.

VPDN

ICRQ Reception

An Incoming-Call-Request (ICRQ) is received from the ATM PVC.

When the router sends an Incoming-Call-Reply (ICRP).

PPPoA

LCP Configure-Request Reception

A Link Control Protocol (LCP) Configure-Request packet is received.

When the router successfully creates an internal bind.

A Configure-Request, Configure-ACK, Configure-NAK, or Configure-Reject packet is sent to establish and configure the link.


Platform Support

The PPP Session CAC Algorithm Improvements in RP feature is available on all Cisco routers with CAC, and in particular on high scaling aggregation routers such as the following:

Cisco 7200 series routers

Cisco 7600 series routers

Cisco 10000 series routers

Configuring PPP Session CAC Algorithm Improvements

To configure the PPP Session CAC Algorithm Improvements in RP feature, perform the following configuration tasks in the order presented:

Enabling the New Model of CAC

Configuring CAC Based on CPU Utilization

Configuring CAC Based on Session Charges

Configuring CAC Charges Using a Session Charge Profile


Note Even though you can change the CAC configuration mode and session charges while the system is operating and busy, we do not recommend this because it might leave stale charges, which can cause erroneous call rejects. If you reconfigure CAC, when you are finished, enter the clear call admission statistics command to clear all current charges so that stale charges are not left.


Enabling the New Model of CAC

To enable the new model of CAC in which improvements to the CAC algorithm protect the router's CPU and memory resources, use the following procedure.

SUMMARY STEPS

1. enable

2. configure terminal

3. call admission new-model

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode. If prompted, enter your password.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

call admission new-model

Example:

Router(config)# call admission new-model

Enables the new model of CAC.

Configuring CAC Based on CPU Utilization

To configure CAC based on CPU use, use the following procedure.

SUMMARY STEPS

1. enable

2. configure terminal

3. call admission cpu-limit limit

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.If prompted, enter your password.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

call admission cpu-limit limit

Example:

Router(config)# call admission cpu-limit 90

Specifies the maximum CPU threshold upon which to start CAC and reject calls. This CPU load is measured from the average 1-minute CPU load, displayed using the show process cpu command.

Note Before you configure the call admission cpu-limit command, the new model of CAC must be enabled. If it is not enabled, the following error message appears:

Enable CAC new model first to use cpu-limit.

cpu-limit specifies the maximum CPU percentage at which CAC is to become active.

limit is the maximum CPU threshold at which CAC should reject calls, expressed as a percentage of the CPU load. Valid values are 0 to 100 percent. This option does not have a default value.

Note Setting the CPU threshold too low might cause an excessive amount of rejected calls. We recommend a value between 80 to 90 percent.

Configuring CAC Based on Session Charges

To configure CAC based on session charges, use the following procedure.

SUMMARY STEPS

1. enable

2. configure terminal

3. call admission limit charge

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode. If prompted, enter your password.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

call admission limit charge

Example:

Router(config)# call admission limit 20

(CAC new model) Specifies the maximum value of the total outstanding session charges upon which CAC is to start rejecting calls.

limit specifies the maximum total concurrent charges.

limit is the maximum outstanding session charges. Valid values are from 0 to 100,000. This option does not have a default value.

Note In releases earlier than Cisco IOS Release 12.2(31)SB13 (original CAC model), the call admission limit command specifies the maximum composite limit of sessions, buffers, and CPU use upon which CAC is to start rejecting calls.

Configuring CAC Charges Using a Session Charge Profile

To configure CAC charges using a session charge profile, use the following procedure.

SUMMARY STEPS

1. enable

2. configure terminal

3. call admission type charge lifetime

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.If prompted, enter your password.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

call admission type charge lifetime

Example:

Router(config)# call admission pppoa 10 1

(CAC new model) Specifies the call charge to add per session. All charges per session are set equal and no time period is used.

type specifies the type of session charge profile (for example, VPDN, PPPoA, PPPoE).

charge specifies the per-session charge. Valid values are from 0 to 1000. We recommend a value of 10.

lifetime specifies the session lifetime. Valid values are from 1 to 31. Session charges with high lifetime numbers take longer to disappear. We recommend a value of 1.

Note In releases earlier than Cisco IOS Release 12.2(31)SB, this command is a hidden command that determines the charge to add per call for a configurable time period. The charge values are set per-call type.

Configuration Example

The following configuration example configures a charge of 10 per session and a call admission limit of 50, which allows 5 calls per second (50/10) through the system:

Router(config)# call admission new-model
Router(config)# call admission limit 50
Router(config)# call admission pppoa 10 1

Verifying and Monitoring CAC Operation

To verify and monitor CAC operation, use any of the following commands in privileged EXEC mode:

Command
Purpose

Router# debug call-admission trace

Traces call admission control (CAC) operation and displays debugging messages.

Note Heavily loaded systems might generate several CAC debug messages.

Router# show call admission statistics

Displays statistical information about CAC operation, including if the new CAC model is enabled.

If the new CAC model is disabled, CAC operates in the same way as it does in the releases before Cisco IOS Release 12.2(34)SB and the original output of this command appears.


Verification Examples

This section provides the following examples of verifying CAC operation:

Example of No Configuration for CAC

Example of Verifying CAC Configuration

Example of CAC Operation Using the Original CAC Model

Example of No Configuration for CAC

The following example shows the information that appears when you enter the show call admission statistics command when CAC is not configured:

Router# show call admission statistics
Call Admission Control is not operational.

Example of Verifying CAC Configuration

The following example shows the kind of information that appears when you enter the show call admission statistics command when CAC is configured:

Router# show call admission statistics
CAC New Model is ACTIVE 
Total call Session charges: 10, limit 20
Total calls rejected 1576, accepted 306
Reject reason: CPU-limit: 1000 Session Charges 576
Current actual CPU: 3%, Limit: 20%

Table 2 describes the fields in the output of the show call admission statistics command when CAC is configured and using the CAC new model.

Table 2 Fields in the show call admission statistics Command—CAC New-Model 

Field
Description

CAC New Model

Indicates whether or not the new CAC model is active. If inactive, CAC operates as in the releases earlier than Cisco IOS Release 12.2(31)SB13.

Total Call Session Charges

Indicates, in real time, the current number of outstanding sessions and the limit configured for session charges.

Total Calls Rejected and Accepted

Indicates the number of calls CAC accepted or rejected.

Reject Reason

Indicates the reason CAC rejected the calls and the number of calls rejected for each reason. CAC rejects calls based on either the configured CPU limit or the session charges limit.

Current Actual CPU

Indicates the actual CPU load based on an average 1-minute sampling and expressed as a percentage. Also displays the configured CPU load limit, expressed as a percentage.



Note If both session charges and CPU charges exceed their configured limits, the call rejection is counted against the session charge rejection reason because the session charges are always checked before the load charges.


Example of CAC Operation Using the Original CAC Model

The following example shows sample output from the show call admission statistics command. In this example, the new CAC model is inactive, but CAC is configured and is using the original CAC model.

Router# show call admission statistics
CAC New Model (SRSM) is INACTIVE.
Total call admission charges: 23, limit 20
Total calls rejected 0, accepted 0
Load metric: charge 23, unscaled 23%

Table 3 describes the fields in the output of the show call admission statistics command when CAC is configured and using the CAC original model.

Table 3 Fields in the show call admission statistics Command—CAC Original Model 

Field
Description

CAC New Model

Indicates whether or not the new CAC model is active. If inactive, CAC operates as in the releases earlier than Cisco IOS Release 12.2(31)SB13.

Total Call Admission Charges

Indicates, in real time, the current number of outstanding sessions and the limit configured for session charges.

The total charges is the sum of session charges and load charges.

Total Calls Rejected and Accepted

Indicates the reason CAC rejected the calls and the number of calls CAC accepted or rejected for each reason. CAC rejects calls based on either the configured CPU limit or the session charges limit.

Load Metric

Indicates the load charge and CPU usage.

The load charge is the charge added by the load component metric and the buffer load charges. In this example buffer usage is nil.

The unscaled load metric is the CPU usage.


Additional References

The following sections provide references related to the PPP Session Call Admission Control Algorithm Improvements in the RP feature.

Related Documents

Related Topic
Document Title

Call Admission Control

VoIP Call Admission Control


Standards

Standard
Title

No new or modified standards are supported by this feature, and support for existing standards is not modified by this feature.


MIBs

MIB
MIBs Link

No new or modified MIBs are supported by this feature, and support for existing MIBs is not modified by this feature.

To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at:

http://www.cisco.com/go/mibs


RFCs

RFC
Title

No new or modified RFCs are supported by this feature, and support for existing RFCs is not modified by this feature.


Technical Assistance

Description
Link

The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies.

To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds.

Access to most tools on the Cisco Support website requires a Cisco.com user ID and password.

http://www.cisco.com/techsupport


Command Reference

The following commands are modified in the feature documented in this module. For information about all Cisco IOS commands, use the Command Lookup Tool at http://tools.cisco.com/Support/CLILookup or a Cisco IOS master commands list.

call admission

call admission cpu-limit

call admission limit

call admission load

call admission new-model

debug call-admission trace

show call admission statistics

call admission

To configure the call admission control (CAC) charge for a call using a session charge profile, use the call admission command in global configuration mode. To disable this feature, use the no form of this command.

call admission type charge lifetime

no call admission type charge lifetime

Syntax Description

type

Specifies the type of session charge profile (for example, VPDN, PPPoA, PPPoE).

charge

Specifies the per-session charge. Valid values are from 0 to 1000. We recommend a value of 10.

lifetime

Specifies the session lifetime. Valid values are from 1 to 31. Session charges with high lifetime numbers take longer to disappear. We recommend a value of 1.


Defaults

This command has no default values or behavior.

Command Modes

Global configuration

Command History

Release
Modification

12.2(31)SB13

This command was introduced.


Usage Guidelines

Cisco 10000 Series Router

In releases before Cisco IOS Release 12.2(31)SB, this command is a hidden command that determines the charge to add per call for a configurable time period. The charge values are set per-call type.

This command uses a session charge profile to determine call charges for CAC. The way in which the charge values are set depends on the CAC model that is enabled.

Original CAC model—If the original CAC model is enabled (releases before Cisco IOS Release 12.2(31)SB13), the charge is added per call for a configurable period of time. The charge values are set per call type.

New CAC model—If the new CAC model is enabled (Cisco IOS Release 12.2(31)SB13 and later releases), the time period is ignored and the call charge values are set per session and are all set equally.

Examples

The following example shows how to use a PPPoA session charge profile to set call charges using the new CAC model:

Router(config)# call admission new-model
Router(config)# call admission pppoa 10 1

Related Commands

Command
Description

call admission cpu-limit

Configures the maximum CPU percentage at which call admission control (CAC) is to become active.

call admission limit

Defines the maximum session charges allowed upon which the new call admission control model is to begin rejecting calls.

call admission new-model

Enables the new CAC model.

clear call admission statistics

Clears call admission statistics.

show call admission statistics

Monitors the global CAC configuration parameters and the behavior of CAC.


call admission cpu-limit

To configure the maximum CPU percentage at which call admission control (CAC) is to become active, use the call admission cpu-limit command in global configuration mode. To disable this feature, use the no form of this command.

call admission cpu-limit limit

no call admission cpu-limit limit

Syntax Description

limit

Specifies the maximum CPU threshold upon which the new CAC model is to begin rejecting calls. This CPU load is measured from the average 1-minute CPU load, displayed using the show process cpu command. Valid values are 1 to 100.


Defaults

Inactive

Command Modes

Global configuration

Command History

Release
Modification

12.2(31)SB13

This command was introduced.


Examples

The following example shows how to set the maximum CPU threshold for the new CAC. In this example, the CPU threshold is set for 80 percent.

Router(config)# call admission cpu-limit 80 

Related Commands

Command
Description

call admission limit

Defines the maximum session charges allowed upon which the new call admission control model is to begin rejecting calls.

call admission new-model

Enables an new CAC model.

clear call admission statistics

Clears call admission statistics.

show call admission statistics

Monitors the global CAC configuration parameters and the behavior of CAC.


call admission limit

To define the maximum session charges allowed upon which the new call admission control model is to begin rejecting calls, use the call admission limit command in global configuration mode. To disable this feature, use the no form of this command.

call admission limit charge

no call admission limit charge

Syntax Description

charge

Specifies the maximum session charges allowed. Valid values are 1 to 100,000.


Defaults

No default behavior or values

Command Modes

Global configuration

Command History

Release
Modification

12.3(8)T

This command was introduced.

12.2(18)SXD1

This command was integrated into Cisco IOS Release 12.2(18)SXD1.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.2(33)SXH

This command was integrated into Cisco IOS Release 12.2(33)SXH.

12.2(31)SB13

This command was integrated into Cisco IOS Release 12.2(31)SB13 and enhanced for a new CAC model, and implemented on the Cisco 10000 series router.


Usage Guidelines

Call Admission Control (New Model)

In Cisco IOS Release 12.2(31)SB13, this command determines the maximum outstanding session charges upon which the new CAC model is to begin rejecting calls. If the original CAC model is used, this command sets the maximum charge threshold, calculated using CPU, sessions, and buffer utilization.

If both the CPU load and session charges are above their thresholds, the call reject is counted against the CPU reason. The CPU load is always checked before the session charges.

Examples

The following example causes CAC to reject calls when the session charges reach a limit of 90,000:

Router(config)# call admission limit 90000 

Related Commands

Command
Description

call admission load

Configures a CAC metric for the CPU load.

show call admission statistics

Monitors the global CAC configuration parameters and the behavior of CAC.


call admission load

To configure a call admission control (CAC) metric for scaling WAN protocol session load or to configure a CAC metric for the CPU load, use the call admission load command in global configuration mode. To disable this feature, use the no form of this command.

call admission load multiplier metric-poll-rate

no call admission load multiplier metric-poll-rate

Syntax Description

multiplier

Multiplier value that provides a scaling factor for determining total load. Valid values are from 1 to 1000, and the default is 100.

metric-poll-rate

Load metric poll rate, in seconds. Valid values are from 1 to 32 seconds, and the default is 1.


Defaults

The default values are 100 for the multiplier and 1 for the poll rate. These values should not be changed without guidance from Cisco technical personnel.

Command Modes

Global configuration

Command History

Release
Modification

12.3(2)T

This command was introduced.

12.2(31)SB13

This command was integrated into Cisco IOS Release 12.2(31)SB13 and implemented on the Cisco 10000 series router.


Usage Guidelines

This command enables CAC to limit overconsumption of Cisco IOS CPU cycles. On hardware-forwarded router platforms, established sessions tend not to consume much of the router processor resources, but there is a need to reduce resource utilization during session establishment, especially, to determine when a call cannot be handled and then to determine when it can be handled again.

For the call admission load command, the router load is calculated when software routines average the current CPU utilization. The command is configured as a mathematical formula—call admission load multiplier metric-poll-rate—where CPU utilization is polled every metric-poll-rate seconds and multiplied by a multiplier, which is the scaling factor. This formula results in a metric value for the current router load determined by existing sessions. The value is compared to that set for the call admission limit command, and if it exceeds the value, the call is rejected; otherwise, the call is accepted.


Note We suggest that you not modify the default values without guidance from Cisco technical personnel.


Usage Guidelines for CAC Metric for CPU Load (Cisco 10000 Series Router)

The call admission load command is not used for the new CAC model.

The multiplier configuration is used to set the value to be added to the charge in the original CAC model at 100 percent load. Therefore, the command call admission load 150 1 means that if the CPU is 100 percent, the load charge is 150. If the CPU is 50 percent, the load charge is 75.

The metric poll rate is used to "damp" the CPU load charges, which means that you can save a couple of previous CPU loads and average them out over the metric-poll-rate number of times.

We recommend a value of 1 for the metric-poll-rate.

Examples

The following example shows recommended settings for the call admission load and call admission limit commands on the Cisco 10000 ESR:

Router(config)# call admission limit 90 
Router(config)# call admission load 100 1

Related Commands

Command
Description

call admission limit

Defines the maximum session charges allowed upon which the call admission control new model is to begin rejecting calls.

clear call admission statistics

Clears call admission statistics.

show call admission statistics

Monitors the global CAC configuration parameters and the behavior of CAC.


call admission new-model

To enable the new call admission control (CAC) model, use the call admission new-model command in global configuration mode. To disable this feature, use the no form of this command.

call admission new-model

no call admission new-model

Syntax Description

This command has no arguments.

Defaults

Disabled

Command Modes

Global configuration

Command History

Release
Modification

12.2(31)SB13

This command was introduced.


Examples

The following example shows how to use a PPPoA session charge profile to set call charges using the new CAC model:

Router(config)# call admission new-model
Router(config)# call 

Related Commands

Command
Description

call admission cpu-limit

Sets the maximum CPU threshold upon which to start rejecting calls.

call admission limit

Defines the maximum session charges allowed upon which the new call admission control model is to begin rejecting calls.

clear call admission statistics

Clears call admission statistics.

show call admission statistics

Monitors the global CAC configuration parameters and the behavior of CAC.


debug call-admission trace

To trace call admission control (CAC) operation and display debugging messages, use the debug call-admission trace command in global configuration mode. To turn off debugging of CAC, use the no form of this command.

debug call-admission trace

no debug call-admission trace

Syntax Description

This command has no arguments.

Defaults

Disabled

Command Modes

Global configuration

Command History

Release
Modification

12.2(31)SB13

This command was introduced.


Usage Guidelines

The debug call-admission trace command displays information about the operations of the original CAC model and of the new CAC model that was introduced in Cisco IOS Release 12.2(31)SB13.

The following describes the debugging messages that might display when you use the debug call-admission trace command:

session_charges now <session_charges>

Displays the current session charges after expirations.

Call charges added for session, curr.charges: <session_charges>

Displays the charges after the session commitment. The broadband component uses this to add session charges to the system.

Reject on session_charges (current <session_charges>)

Displays the reason CAC had to reject a session and displays the current session charges.

CAC enabled > session charges (<session_charges>/<configured session_charges limit>)

Displays when CAC is rejecting sessions because of session charges.

Reject on CPU charge (current <current cpu util>)

Displays the reason CAC has to reject a session based on the CPU charge and displays the actual current CPU utilization.

CAC enabled > CPU threshold (<current cpu util>/<configured cpu limit threshold>)

Displays when CAC is rejecting sessions because of CPU utilization.

CAC is no longer active, cpu/session charges are below thresholds:

CPU=<current cpu util>, Sess=<current session charges>

Displays when CAC is deactivated because the CPU and session charges are below the thresholds.

Examples

The following example shows how to use a PPPoA session charge profile to set call charges using the new CAC model:

Router(config)# debug call-admission trace
Router(config)# 

Related Commands

Command
Description

call admission cpu-limit

Sets the maximum CPU threshold upon which to start rejecting calls.

call admission limit

Defines the maximum session charges allowed upon which the new call admission control model is to begin rejecting calls.

clear call admission statistics

Clears call admission statistics.

show call admission statistics

Monitors the global CAC configuration parameters and the behavior of CAC.


show call admission statistics

To monitor the global call admission control (CAC) configuration parameters and the behavior of CAC, use the show call admission statistics command in user EXEC or privileged EXEC mode.

show call admission statistics

Syntax Description

This command has no arguments or keywords.

Command Modes

User EXEC
Privileged EXEC

Command History

Release
Modification

12.3(8)T

This command was introduced.

12.2(18)SXD1

This command was integrated into Cisco IOS Release 12.2(18)SXD1.

12.2(33)SRA

This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.2(33)SXH

This command was integrated into Cisco IOS Release 12.2(33)SXH.

12.2(31)SB13

This command was enhanced in Cisco IOS Release 12.2(31)SB13 to display statistics for a new call admission control (CAC) model.


Examples

The following is sample output from the show call admission statistics command for the original CAC model:

Router# show call admission statistics 

Total call admission charges: 0, limit 25 
Total calls rejected 12, accepted 51 
Load metric: charge 0, unscaled 0

The load metric charge is computed using the following formula and is potentially damped with multiple values if the metric poll rate is greater than 1:

CPU_Load percent * Multiplier / 100

Table 4 describes the significant fields shown in the display.

Table 4 show call admission statistics Field Descriptions 

Field
Description

Total call admission charges

Percentage of system resources being charged to the system. If you configured a resource limit, CA requests are dropped when this field is equal to that limit.

limit

Maximum allowed number of total call admission charges. Valid values are 0 to 100000.

Total calls rejected

Number of CA requests that were not accepted.

accepted

Number of CA requests that were accepted.

unscaled

(New CAC model) Real CPU load value without poll rate damping and multipliers applied.


Related Commands

Command
Description

call admission limit

Defines the maximum session charges allowed upon which the call admission control new model is to begin rejecting calls.

call admission load

Configures a CAC metric for the CPU load.


Feature Information for PPP Session CAC Algorithm Improvements in RP

Table 5 lists the release history for this feature.

Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.

Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.


Note Table 5 lists only the Cisco IOS software release that introduced support for a feature in a Cisco IOS software release train. Unless noted otherwise, subsequent releases of that Cisco IOS software release train also support that feature.


Table 5 Feature Information for PPP Session CAC Algorithm Improvements in RP

Feature Name
Releases
Feature Information

PPP Session CAC Algorithm Improvements in RP

12.2(31)SB13

Provides a new CAC model and supporting commands.

The behavior of the following commands was modified: call admission limit, show call admission statistics. The following commands were introduced: call admission, call admission cpu-limit, call admission new-model, debug call-admission trace.