RFC 3176: InMon Corporation's sFlow: A Method for Monitoring Traffic in Switched and Routed Networks
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC3176
- Published
- September 2001
- Authors
- P. Phaal; S. Panchen; N. McKee
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 31
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1694Definitions of Managed Objects for SMDS Interfaces using SMIv2Current
August 1994
- RFC 2837Definitions of Managed Objects for the Fabric Element in Fibre Channel StandardObsoleted
May 2000
- RFC 2674Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering and Virtual LAN ExtensionsObsoleted
August 1999
- RFC 2666Definitions of Object Identifiers for Identifying Ethernet Chip SetsCurrent
August 1999
- RFC 2665Definitions of Managed Objects for the Ethernet-like Interface TypesObsoleted
August 1999
- RFC 2493Textual Conventions for MIB Modules Using Performance History Based on 15 Minute IntervalsObsoleted
January 1999
- RFC 2366Definitions of Managed Objects for Multicast over UNI 3.0/3.1 based ATM NetworksObsoleted
July 1998
- RFC 2358Definitions of Managed Objects for the Ethernet-like Interface TypesObsoleted
June 1998
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?