Skip to main content

InMon Corporation's sFlow: A Method for Monitoring Traffic in Switched and Routed Networks

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3176.
Authors Sonia Panchen , Neil McKee , Peter Phaal
Last updated 2013-03-02 (Latest revision 2001-07-05)
RFC stream Legacy stream
Stream Legacy state (None)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 3176 (Informational)
Telechat date (None)
Responsible AD (None)
Send notices to (None)
A new Request for Comments is now available in online RFC libraries.

        RFC 3176

        Title:      InMon Corporation's sFlow: A Method for Monitoring
                    Traffic in Switched and Routed Networks
        Author(s):  P. Phaal, S. Panchen, N. McKee
        Status:     Informational
        Date:       September 2001
        Mailbox:    peter_phaal@INMON.COM, sonia_panchen@INMON.COM,
        Pages:      31
        Characters: 60171
        Updates/Obsoletes/See Also:  None

        I-D Tag:    draft-phaal-sflow-montraffic-01.txt


This memo defines InMon Corporation's sFlow system.  sFlow is a
technology for monitoring traffic in data networks containing switches
and routers.  In particular, it defines the sampling mechanisms
implemented in an sFlow Agent for monitoring traffic, the sFlow MIB
for controlling the sFlow Agent, and the format of sample data used by
the sFlow Agent when forwarding data to a central data collector.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.