Table Of Contents
Tracking Policy Failure Statistics
Contents
Restrictions for Tracking Call Policy Failure Statistics
Information About Policy Failure Statistics
Policy Failure Statistics for a Specified Time Interval
Per-Table and Per-Entry Statistics
Automatic Tracking of Policy Failure Statistics
Policy Failure Statistics and Hunting
Global Statistics and Call Hunting
Per-table and Per-entry Statistics and Call Hunting
Per-adjacency and Per-Account Statistics and Call Hunting
Additional References
Related Documents
Standards
MIBs
Technical Assistance
Tracking Policy Failure Statistics
Users can track the number of calls that the SBC rejected based on the rules established in the number analysis policies, routing policies, or CAC policies. Users can also view and query the policy failure statistics associated with these rejected calls, which can help them determine whether changes need to be made to the existing policies.
Feature History for Policy Failure Statistics
Release
|
Modification
|
Release 3.4.1
|
This feature was introduced on the Cisco XR 12000 Series Router.
|
Release 3.5.0
|
No modification.
|
Release 3.6.0
|
No modification.
|
Contents
This module contains the following sections:
•
Restrictions for Tracking Call Policy Failure Statistics
•
Information About Policy Failure Statistics
•
Additional References
Restrictions for Tracking Call Policy Failure Statistics
Review the following restrictions for policy failure statistics:
•
Only new call failures are tracked by this feature.
•
Only call failures associated with local policy are recorded. Calls rejected by downstream signaling devices are not included in this statistics.
Information About Policy Failure Statistics
Policy Failure Statistics for a Specified Time Interval
Table 11 lists the commands to view and clear the failure statistics on the specified SBE for a certain time interval.
Table 11 Commands for Time-Based Policy Failure Statistics
show services sbc service-name sbe policy-failure-stats period
|
Displays the policy failure statistics for the time period specified. The value for the period parameter must be one of the following:
• current5mins
• previous5mins
• current15mins
• previous15mins
• currenthour
• previoushour
• currentday
• previousday
The policy failure statistics are recorded at 5-minute intervals.
|
clear services sbc service-name sbe policy-rejection-stats
|
Clears the policy failure statistics for the current and previous time interval.
|
Per-Table and Per-Entry Statistics
To determine whether calls failed because of policies configured in the routing, number validation, or CAC tables, users can view the policy failure statistics for a specific policy table or table entry. Table 12 lists the commands to view and clear the statistics in a policy table.
Table 12 Per-Table Statistics Commands
show services sbc service-name sbe cac-policy-set policy set-id tables
|
Displays a summary of the CAC policy tables associated with the given policy set, including the number of failed calls.
|
clear services sbc service-name sbe cac-rejection-stats
|
Clears all CAC policy failure statistics.
|
show services sbc service-name sbe call-policy-set policy set-id tables
|
Displays a summary of routing policy tables associated with the given policy set, including the number of failed calls.
|
clear services sbc service-name sbe call-rejection-stats
|
Clears all routing and number analysis policy rejection statistics.
|
Table 13 lists the commands to view the detailed information for a specific entry in a CAC policy table and routing table.
Table 13 Per-Entry Statistics Commands
show services sbc service-name sbe cac-policy-set policy set-id table name entry entry
|
Displays detailed statistics for the given entry in a CAC policy table.
|
show services sbc service-name sbe call-policy-set policy set-id table name entry entry
|
Displays a summary of the entries associated with the given routing table.
|
Automatic Tracking of Policy Failure Statistics
The SBC automatically tracks policy failure statistics for call attribute sets representing the following:
•
per-source adjacency statistics for all configured adjacencies
•
per-destination adjacency statistics for all configured adjacencies
•
per-source account statistics for all configured accounts
•
per-destination account statistics for all configured accounts
Table 14 lists the commands to view and clear automatically tracked policy failure statistics.
Table 14 Automatically-Tracked Statistics Commands
show services sbc service-name sbe policy-failure-stats src-adjacency table name period
|
Displays the policy statistics of the specified source adjacency for the specified time interval. The value for the period parameter must be one of the following:
• current5mins
• previous5mins
• current15mins
• previous15mins
• currenthour
• previoushour
• currentday
• previousday
|
clear services sbc service-name sbe policy-failure-stats src-adjacency table name period
|
Clears the policy statistics of the specified source adjacency.
|
show services sbc service-name sbe policy-failure-stats src-account account name period
|
Displays the policy statistics of the specified source account for the specified time interval.
|
clear services sbc service-name sbe policy-failure-stats src-account account name
|
Clears the policy statistics of the specified account.
|
show services sbc service-name sbe policy-failure-stats dst-adjacency target adjacency period
|
Displays the policy statistics of the specified target adjacency for the specified time interval.
|
clear services sbc service-name sbe policy-failure-stats dst-adjacency target adjacency period
|
Clears the policy statistics of the specified target adjacency.
|
show services sbc service-name sbe policy-failure-stats dst-account target adjacency period
|
Displays the policy statistics of the specified target account for the specified time interval.
|
clear services sbc service-name sbe policy-failure-stats dst-account target adjacency period
|
Clears the policy statistics of the specified target account.
|
Policy Failure Statistics and Hunting
If the CAC module refuses a call or if a call cannot be signaled to the chosen destination adjacency because of a negative or no response, call hunting occurs. Call hunting is the process of selecting an alternative adjacency from the routing tables and retrying the call using the newly selected destination adjacency.
Hunting continues until one of the following conditions is fulfilled:
•
The call gets connected.
•
No further adjacencies are available for retry.
•
The call has been hunted too many times.
Global Statistics and Call Hunting
If a call gets connected after hunting, the SBC does not include it in any of the following global statistics:
•
total call setup failures
•
total call setups failed due to number analysis
•
total call setups failed due to routing
•
total call setups failed due to CAC
•
CAC failure due to number of calls limit
•
CAC failure due to call rate limit
•
CAC failure due to media channels limit
•
CAC failure due to bandwidth limit
If a call fails after number analysis, hunting does not occur. The SBC includes it in the following global statistics:
•
total call setup failures
•
total call setups failed due to number analysis
If a call fails the first time it is routed because no destination adjacency is found in the routing table, then the SBC includes it in the following global statistics:
•
total call setup failures
•
total call setups failed due to routing
If a call fails because a CAC policy refused it permission to proceed, the SBC includes the failure in the total call setups failed due to CAC statistics. Additionally, the call is included in one of the following statistics depending on the nature of the CAC limit:
•
CAC failure due to number of calls limit
•
CAC failure due to call rate limit
•
CAC failure due to media channels limit
•
CAC failure due to bandwidth limit
Per-table and Per-entry Statistics and Call Hunting
If a call undergoes N iterations of hunting, then it traverses the number analysis tables once, and the routing and the CAC tables N times. But the CAC tables can reject the call each time it traverses the CAC table. For each time the CAC table rejects the call, the SBC finds the table and entry that was responsible for setting the CAC limit, and increments the following:
•
the number of calls refused by the CAC table
•
the number of calls refused by the table entry
Per-adjacency and Per-Account Statistics and Call Hunting
If a call gets connected after hunting, the SBC does not include it in the following per-account or per-adjacency statistics:
•
total call setup failures
•
total call setups failed due to number analysis
•
total call setups failed due to CAC
•
CAC failures due to rate limit
•
CAC failures due to media channels limit
•
CAC failures due to bandwidth limit
If a call fails due to number analysis, then hunting does not occur and the SBC includes the call in the following per-account and per-source adjacency statistics:
•
total call setup failures
•
total call setups failed due to number analysis
If a call fails in the routing tables before hunting occurs, the SBC includes the call in the following per-source account and per-source-adjacency statistics:
•
total call setup failures
•
total call setups failed due to routing
A call included in the total call setup failures statistics is included in the per-source adjacency, per-destination-adjacency, per-source-account adjacency, and per-destination account statistics. Additionally, if the most recent hunting attempt failed because a CAC policy refused the call permission to proceed, the SBC includes the failure in the total call setups failed due to CAC statistics in the per-source-adjacency, per-destination-adjacency, per-source-account, and per-destination-account statistics. The call is also included in one of the following statistics depending on the nature of the CAC limit depending on the nature of the CAC limit:
•
CAC failure due to number of calls limit
•
CAC failure due to call rate limit
•
CAC failure due to media channels limit
•
CAC failure due to bandwidth limit
Additional References
The following sections provide references related to tracking policy failure statistics.
Related Documents
Related Topic
|
Document Title
|
Cisco IOS XR master command reference
|
Cisco IOS XR Master Commands List
|
Cisco IOS XR SBC interface configuration commands
|
Cisco IOS XR Session Border Controller Command Reference
|
Initial system bootup and configuration information for a router using the Cisco IOS XR Software
|
Cisco IOS XR Getting Started Guide
|
Cisco IOS XR command modes
|
Cisco IOS XR Command Mode Reference
|
Standards
Standards
|
Title
|
No new or modified standards are supported by this feature, and support from existing standards has not been modified by this feature.
|
—
|
MIBs
Technical Assistance
Description
|
Link
|
The Cisco Technical Support website contains thousands of pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.
|
http://www.cisco.com/techsupport
|