Configuring acl-based inbound sflow – Brocade Multi-Service IronWare Switching Configuration Guide (Supporting R05.6.00) User Manual
Page 929
Multi-Service IronWare Switching Configuration Guide
899
53-1003036-02
ACL-based Inbound sFlow
23
Configuring ACL-based Inbound sFlow
The following sections describe how to configure ACL-based Inbound sFlow:
•
“Configuration considerations for ACL-based Inbound sFlow”
•
“Creating an ACL with an sFlow clause”
•
“Displaying sFlow information”
Configuration considerations for ACL-based Inbound sFlow
The following section describes configuration considerations for ACL-based Inbound sFlow:
•
sFlow must be enabled on the router.
•
ACL-based mirroring: The mirror and copy-sflow keywords are mutually exclusive on a per-ACL
clause basis.
•
Port-based monitoring: Port-based monitoring and ACL-based sFlow can co-exist on the same
interface.
•
Port-based sFlow: Port-based and ACL-based sFlow can co-exist on the same interface. When
both features are configured on an interface, packets that qualify as ACL-based sFlow packets
are sent to the collector as ACL sample packets. Also, the user can configure ACL-based sFlow
on an interface without configuring port-based sFlow.
•
IP Receive ACLs: IP Receive ACLs are used for filtering or rate-limiting management traffic. The
copy-sflow keyword is also supported for IP Receive ACLs.
•
Policy Based Routing: The copy-sflow keyword is applicable for PBR ACLs.