PreviousNextJavaScript must be enabled to correctly display this content
Bandwidth CAC Fallback Based on ICMP Failure Configuration
You can set up ICMP heartbeats and fallback bandwidth pools in the realm configuration. Leaving the icmp-detect-multiplier,
icmp-advertisement-interval, or
icmp-target-ip parameters blank or set to zero turns the feature off.
To enable bandwidth CAC fallback based on ICMP failure:
In Superuser mode, type
configure terminal and press Enter.
icmp-detect-multiplier—Enter the multiplier you want to use when determining how long to send ICMP pings before considering a target unreachable. This number multiplied by the time you set for the
icmp-advertisement-interval determines the length of time. For example, if you set this parameter to 10 and the advertisement interval to 20, the
Oracle® Enterprise Session Border Controller will send ICMP pings for 200 seconds before declaring the target unreachable.
icmp-advertisement-interval—Enter the time in seconds between ICMP pings the
Oracle® Enterprise Session Border Controller sends to the target. The default is 0.
icmp-target-ip—Enter the IP address to which the
Oracle® Enterprise Session Border Controller should send the ICMP pings so that it can detect when they fail and it needs to switch to the fallback bandwidth for the realm. There is no default.
fallback-bandwidth—Enter the amount of bandwidth you want available once the
Oracle® Enterprise Session Border Controller has determined that the target is unreachable.
If the fallback amount is less than the
max-bandwidth value, the
Oracle® Enterprise Session Border Controller might start to reject calls. It does so until enough calls are released to free adequate bandwidth to stay under the fallback limit and still accept calls.