02.10.2013 Views

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 15 sFlow<br />

Configuring sFlow is supported on plat<strong>for</strong>ms c e s<br />

• Enabling and Disabling sFlow on page 304<br />

• sFlow Show Commands on page 305<br />

• Specifying Collectors on page 307<br />

• Polling Intervals on page 307<br />

• Sampling Rate on page 308<br />

• Back-off Mechanism on page 309<br />

• sFlow on LAG ports on page 309<br />

• Extended sFlow on page 309<br />

Important Points to Remember<br />

Note: sFlow is not supported on S-<strong>Series</strong> stacked units.<br />

• <strong>Force10</strong> <strong>Networks</strong> recommends that <strong>the</strong> sFlow Collector be connected to <strong>the</strong> <strong>Force10</strong> chassis through<br />

a line card port ra<strong>the</strong>r than <strong>the</strong> RPM Management E<strong>the</strong>rnet port.<br />

• <strong>FTOS</strong> exports all sFlow packets to <strong>the</strong> collector. A small sampling rate can equate to a large number of<br />

exported packets. A backoff mechanism will automatically be applied to reduce this amount. Some<br />

sampled packets may be dropped when <strong>the</strong> exported packet rate is high and <strong>the</strong> backoff mechanism is<br />

about to or is starting to take effect. The dropEvent counter, in <strong>the</strong> sFlow packet, will always be zero.<br />

• Community list and local preference fields are not filled in extended gateway element in sFlow<br />

datagram.<br />

• 802.1P source priority field is not filled in extended switch element in sFlow datagram.<br />

• Only Destination and Destination Peer AS number are packed in <strong>the</strong> dst-as-path field in extended<br />

gateway element<br />

• If packet being sampled is redirected using PBR (Policy-Based Routing), sFlow datagram may contain<br />

incorrect extended gateway/router in<strong>for</strong>mation.<br />

• sFlow does not support packing extended in<strong>for</strong>mation <strong>for</strong> IPv6 packets. Only <strong>the</strong> first 128 bytes of <strong>the</strong><br />

IPv6 packet is shipped in <strong>the</strong> datagram.<br />

• Source VLAN field in <strong>the</strong> extended switch element will not be packed in case of routed packet.<br />

• Destination VLAN field in <strong>the</strong> extended switch element will not be packed in case of Multicast packet.<br />

• On <strong>the</strong> S-<strong>Series</strong>, up to 700 packets can be sampled and processed per second.<br />

• On <strong>the</strong> C-<strong>Series</strong> up to 1000 packets can be sampled and processed per second.<br />

• On <strong>the</strong> E-<strong>Series</strong>, <strong>the</strong> maximum number of packets that can be sampled and processed per second is:<br />

— 7500 packets when no extended in<strong>for</strong>mation packing is enabled.<br />

— 7500 packets when only extended-switch in<strong>for</strong>mation packing is enabled.<br />

<strong>FTOS</strong> <strong>Configuration</strong> <strong>Guide</strong>, version 7.7.1.0 303

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!