[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]

Configuring the Content Destination

You must specify a destination for the packets that match DFC PIC filter criteria. To configure the content destination, include the content-destination statement at the [edit services dynamic-flow-capture capture-group client-name] hierarchy level:




content-destination identifier {

address address;

hard-limit bandwidth;

hard-limit-target bandwidth;

soft-limit bandwidth;

soft-limit-clear bandwidth;

ttl hops;
}

Assign the content-destination a unique identifier. You must also specify its IP address and you can optionally include additional settings:

address—The DFC PIC interface appends an IP header with this destination address on the matched packet (with its own IP header and contents intact) and sends it out to the content destination.
ttl—The time-to-live (TTL) value for the IP-IP header. By default, the TTL value is 255. Its range is 0 through 255.
Congestion thresholds—You can specify per-content destination bandwidth limits that control the amount of traffic produced by the DFC PIC during periods of congestion. The thresholds are arranged in two pairs: hard-limit and hard-limit-target, and soft-limit and soft-limit-clear. You can optionally include one or both of these paired settings. All four settings are 10–second average bandwidth values in bits per second. Typically soft-limit-clear < soft-limit < hard-limit-target < hard-limit. When the content bandwidth exceeds the soft-limit setting:
1. A congestion notification message is sent to each control source of the criteria that point to this content destination
2. If the control source is configured for syslog, a system log message is generated.
3. A latch is set, indicating that the control sources have been notified. No additional notification messages are sent until the latch is cleared, when the bandwidth falls below the soft-limit-clear value.
When the bandwidth exceeds the hard-limit value:
1. The dynamic flow capture application begins deleting criteria until the bandwidth falls below the hard-limit-target value.
2. For each criterion deleted, a CongestionDelete notification is sent to the control source for that criterion.
3. If the control source is configured for syslog, a log message is generated.
The application evaluates criteria for deletion using the following data:
- Priority—Lower priority criteria are purged first, after adjusting for control source minimum priority.
- Bandwidth—Higher bandwidth criteria are purged first.
- Timestamp—The more recent criteria are purged first.

[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]