RFC 3877: Alarm Management Information Base (MIB)
In plain English — editorial summary, not part of the RFC
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes management objects used for modelling and storing alarms. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3877
- Published
- September 2004
- Authors
- S. Chisholm; D. Romascanu
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 75
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3878Alarm Reporting Control Management Information Base (MIB)Current
September 2004
- RFC 3895Definitions of Managed Objects for the DS1, E1, DS2, and E2 Interface TypesObsoleted
September 2004
- RFC 3896Definitions of Managed Objects for the DS3/E3 Interface TypeCurrent
September 2004
- RFC 3747The Differentiated Services Configuration MIBCurrent
April 2004
- RFC 4011Policy Based Management MIBCurrent
March 2005
- RFC 3737IANA Guidelines for the Registry of Remote Monitoring (RMON) MIB modulesCurrent
April 2004
- RFC 3729Application Performance Measurement MIBCurrent
March 2004
- RFC 3728Definitions of Managed Objects for Very High Speed Digital Subscriber Lines (VDSL)Current
February 2004
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?