Brocade Communications Systems 6650 SFlow support for IPv6 packets, Extended router information

sFlow 11

sFlow version 5 is backward-compatible with sFlow version 2. By default, the sFlow agent exports sFlow version 5 flow samples by default, but you can configure the device to export the data in sFlow version 2 format. You can switch between sFlow version 2 and sFlow version 5 formats. The sFlow collector automatically parses each incoming sample and decodes it based on the version number.

The configuration procedures for sFlow version 5 are the same as for sFlow version 2, except where explicitly noted. Configuration procedures for sFlow are in the section “Configuring and enabling sFlow” on page 257. The features and CLI commands that are specific to sFlow version 5 are described in the section “sFlow version 5 feature configuration” on page 264.

sFlow support for IPv6 packets

The Brocade implementation of sFlow features support IPv6 packets. This support includes extended router information and extended gateway information in the sampled packet. Note that sFlow support for IPv6 packets exists only on devices running software that supports IPv6.

The configuration procedures for this feature are the same as for IPv4, except where the collector is a link-local address on a Layer 3 switch. For details refer to “Specifying the collector” on page 258.

Extended router information

IPv6 sFlow sampled packets include the following extended router information:

•IP address of the next hop router

•Outgoing VLAN ID

•Source IP address prefix length

•Destination IP address prefix length

Note that in IPv6 devices, the prefix lengths of the source and destination IP addresses are collected if BGP is configured and the route lookup is completed. In IPv4 devices, this information is collected only if BGP is configured on the devices.

Extended gateway information

If BGP is enabled, extended gateway information is included in IPv6 sFlow sampled packets, including the following BGP information about a packet destination route:

•The autonomous system (AS) number for the router

•The source IP AS of the route

•The source peer AS for the route

•The AS patch to the destination

NOTE

AS communities and local preferences are not included in the sampled packets.

To obtain extended gateway information, use “struct extended_gateway” as described in RFC 3176.

Brocade ICX 6650 Administration Guide	255
53-1002600-01