Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 03-Flow group configuration | 44.92 KB |
Configuring flow groups
About flow groups
A flow group can use an ACL to limit the traffic for which flow entries are generated. A flow entry is aged out if no matching packets are received before the aging timer expires.
The generated flow entries can be used by other features. In the current software version, the MOD feature relies on these flow entries to work correctly. For more information about MOD, see "Configuring MOD."
Restrictions and guidelines: Flow group configuration
A flow group can reference only one ACL. Because a flow can belong to only one flow group, make sure the same flow is not assigned to more than one flow group when specifying ACLs. For information about ACLs, see ACL and QoS Configuration Guide.
To delete an applied flow group, first remove the application and then delete the flow group.
Procedure
system-view
2. Create a flow group and enter its view.
telemetry flow-group group-id [ name group-name ]
3. Specify an ACL.
if-match acl [ ipv6 | mac ] { acl-number | name acl-name }
By default, no ACL is specified.
4. Configure the header fields used for generating flow entries.
template { destination-ip | destination-port | protocol | source-ip | source-port } *
By default, no header fields are used for generating flow entries.
After you execute this command, no flow entries will be generated. However, for the flow group to take effect, you must execute this command.
5. Return to system view.
quit
6. Apply the flow group.
telemetry apply flow-group { group-id | name group-name }
By default, no flow group is applied.
Verifying and maintaining flow group
To verify the flow group configuration and running status, execute the following command in any view:
display telemetry flow-group [ group-id | name group-name ] [ slot slot-number ]
