Table Of Contents
Configuring Data Border Element Overload Reporting
Contents
Prerequisites—Implementing DBE Overload
DBE Overload Reporting
Configuring DBE Overload Reporting
Configuring Data Border Element Overload Reporting
This chapter describes configuration commands that facilitate the Session Border Controller's (SBC) reporting of data border element (DBE) overload conditions. The DBE reports the following:
•
Overload of the control plane
•
Overload of the data plane
•
Congestion of resources
Overload and congestion are reported, and SBC differentiates the causes.
Note
For ACE SBC Release 3.0.00, this feature is supported in both the unified model and the distributed model.
For a more information on commands used in this chapter, refer to Chapter 39, "Cisco Session Border Controller Commands." To locate documentation for other commands that appear in this chapter, use the command reference master index, or search online.
Feature History for Configuring DBE Overload Reporting
Release
|
Modification
|
ACE SBC Release 3.0.00
|
Added support for SBC unified model.
|
ACE SBC Release 2.0.00
|
This feature was introduced on the Cisco 7600 series router.
|
Contents
This module contains the following sections:
•
Prerequisites—Implementing DBE Overload
•
DBE Overload Reporting
•
Configuring DBE Overload Reporting
Prerequisites—Implementing DBE Overload
The following prerequisites are required to implement SBC redundancy:
•
On the Application Control Engine Module (ACE), you must be an Admin user to enter SBC commands. For more information, see the Application Control Engine Module Administration Guide at: http://www.cisco.com/en/US/products/hw/modules/ps2706/products_configuration_guide_book09186a00806838f4.html
•
Before implementing interworking DBE overload, the SBC must already be created. See the procedures described in Chapter 2, "ACE Configuration Prerequisites for the SBC."
DBE Overload Reporting
H.248 protocol (or Megaco), a VoIP signaling protocol, is used to communicate between a Media Gateway Controller (MGC) and DBE in a distributed SBC system. The Megaco package H.248.11 allows a media gateway (MG) to generate events when requests to add new terminations exceed a defined threshold.
The DBE is extended to support this package.
MGC is not extended to use this package.
The H.248.11 package is added as an option in the H.248 Gate Control profile.
Configuring DBE Overload Reporting
This section contains the steps for configuring DBE overload reporting.
SUMMARY STEPS
1.
configure
2.
sbc sbc-name
3.
dbe
4.
overload-time-threshold time
5.
exit
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
configure
Example:
host1/Admin# configure
|
Enables global configuration mode.
|
Step 2
|
sbc sbc-name
Example:
host1/Admin(config)# sbc mysbc
|
Enters the mode of an SBC service.
• Use the sbc-name argument to define the name of the service.
|
Step 3
|
dbe
Example:
host1/Admin(config-sbc)# dbe
|
Enters the mode of the DBE function of the SBC.
|
Step 4
|
overload-time-threshold time
Example:
host1/Admin(config-sbc-dbe)# sbc dbe
overload-time-threshold 400
|
Configures the threshold time (in milliseconds) for MG overload control detection.
If an SBE has subscribed for overload control events, the DBE sends an overload event notification every time a request to add a new flow takes longer than this threshold to process.
The range is 0 - 2000000000. The default is 100.
|
Step 5
|
exit
Example:
host1/Admin(config-sbc-dbe)# exit
|
Exits the DBE mode and returns to the Exec mode.
|