Technical Documentation

Defining Flow Properties

Flow maps enable you to configure bandwidth variables and multicast forwarding cache timeout values for entries defined by the flow map policy. This section discusses the following flow properties:

Defining Bandwidth for Multicast Flows

You can define the bandwidth associated with multicast flows that match a flow map by specifying a bandwidth in bits per second, by specifying that the bandwidth is measured and adaptively modified, or by a combination of both methods where you specify an initial value for the bandwidth and the interface uses the adaptive value thereafter. For additional information about how to define flow bandwidth, see Defining Bandwidth for Multicast Flows.

Defining Forwarding Cache Timeout

The forwarding cache timeout value can range from 1 through 720 minutes, or you can set the value to never, making the entries permanent. If you set the value to never, you can also specify the non-discard-entry-only option to make an exception for entries that are in the pruned state. The never non-discard-entry-only statement allows entries in the pruned state to time out while entries in the forwarding state never time out. For additional information about how to configure forwarding cache properties, see Configuring General Multicast Forwarding Cache Properties.

Specifying Redundant Flow Sources

To specify redundant (backup) sources for flows identified by a flow map, include the redundant-sources statement:

redundant-sources [ addresses ];

You can include this statement at the following hierarchy levels:

  • [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options multicast flow-map flow-map-name]
  • [edit logical-systems logical-system-name routing-options multicast flow-map flow-map-name]
  • [edit routing-instances routing-instance-name routing-options multicast flow-map flow-map-name]
  • [edit routing-options multicast flow-map flow-map-name]

Outbound interfaces that are admitted for one of the forwarding entries are automatically admitted for any other entries identified by the redundant source configuration.

In the following example, forwarding entries (10.11.11.11, g1) and (10.11.11.12, g1) match the flow map flowMap1. In this case, if a particular outbound interface is admitted for entry (10.11.11.11, g1), it is automatically admitted for entry (10.11.11.12, g1), even if there is no longer enough remaining bandwidth available after creating entry (10.11.11.11, g1). The interface is added because only one of the two sources can send traffic at any time.

[edit routing-options]multicast {flow-map flowMap1 {redundant-sources [ 10.11.11.11 10.11.11.12 ];}}

Related Topics


Published: 2010-07-16

Help
|
My Account
|
Log Out