RFC 2837: Definitions of Managed Objects for the Fabric Element in Fibre Channel Standard
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4044.
Current version: RFC 4044 — Fibre Channel Management MIB
In plain English — editorial summary, not part of the RFC
This memo defines an extension to the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines the objects for managing the operations of the Fabric Element portion of the Fibre Channel Standards. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2837
- Published
- May 2000
- Authors
- K. Teow
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 48
- Also known as
- —
- Obsoleted by:
- RFC 4044
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2366Definitions of Managed Objects for Multicast over UNI 3.0/3.1 based ATM NetworksObsoleted
July 1998
- RFC 1694Definitions of Managed Objects for SMDS Interfaces using SMIv2Current
August 1994
- RFC 1650Definitions of Managed Objects for the Ethernet-like Interface Types using SMIv2Obsoleted
August 1994
- RFC 1623Definitions of Managed Objects for the Ethernet-like Interface TypesObsoleted
May 1994
- 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 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?