Brocade Multi-Service IronWare Switching Configuration Guide (Supporting R05.6.00) - Manual (Page 918)

888 Multi-Service IronWare Switching Configuration Guide
53-1003036-02
sFlow event workflow
23
• Non-default VRF IPv4 sampled packets
• Non-default VRF IPv6 sampled packets
• Default VRF IPv4 sampled packets
• Default VRF IPv6 sampled packets
RFC 3176, “InMon Corporation's sFlow: A Method for Monitoring Traffic in Switched and Routed
Networks” describes sFlow. Refer to this RFC to determine the contents of the sampled packet.
Brocade supports sFlow v5, which replaces the version outlined in RFC 3176.
sFlow event workflow
If the sFlow destination is IPV6 and the sFlow Agent IPv6, then an IPv6 agent will be selected from
the configured interface. Otherwise, IPv4 will be selected from the configured interface ID from the
sFlow agent command. If the sFlow agent is not configured, the router ID is used.
If the sFlow destination is IPv4, and the sFlow agent is configured, then an IPv4 agent will be
selected from the configured interface. If the sFlow agent is not configured, the router-ID is used.
The Agent IP address selects the first IP address in the interface IP address list. The Agent IPv6
address is unspecified by default. Use the show sflow command to verify the interface IP address
list.
The status of an IP-port (UP, DOWN) will not impact the sFlow source IP.
The adding or deleting of IP addresses on the interface upon which the sFlow agent interface is
configured or a router ID change will trigger the following events:
1. Router ID event:
If the sFlow agent is not configured, or has been configured but an IP interface does not
contain an IP address, then the sFlow agent will use the current management VRF router ID (if
any). If the management VRF has changed, then the sFlow agent will also update the agent IP
address. However, if the management VRF is disabled or assigned to the default VRF (default
behavior), then a router ID event will be applied for the global router ID. The sFlow agent will be
updated accordingly.
2. Adding IP address event:
Adding an IP address on an interface upon which the sFlow agent is configured on will impact
an agent-IP based on the following scenarios:
• If this IP address is the first IP address in the table then the sFlow agent selects it.
• If the added IP address is positioned on the top of the IP table (due to IP address
sequence order), then an agent IP will be reassigned to it. However, if it is not, then it
will not impact the agent IP address.
3. Deleting IP address event:
Deleting an IP address on an interface that the sFlow agent is configured on will impact an
agent-IP based on the following scenarios:
• If the deleted IP address is an equivalent to agent IP address then the next IP address
on the same interface will be selected.