RFC Errata
RFC 4268, "Entity State MIB", November 2005
Source of RFC: entmib (ops)See Also: RFC 4268 w/ inline errata
Errata ID: 2611
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Mark Ellison
Date Reported: 2010-11-06
Verifier Name: Dan Romascanu
Date Verified: 2010-11-23
Section 5 says:
entStateOperEnabled NOTIFICATION-TYPE . . . ...to find out whether there were any known alarms against the entity at that time that may explain why the physical entity has become operationally disabled." ::= { entStateNotifications 1 } entStateOperDisabled NOTIFICATION-TYPE . . . ...to find out whether there were any known alarms against the entity at that time that may affect the physical entity's ability to stay operationally enabled." ::= { entStateNotifications 2 }
It should say:
entStateOperEnabled NOTIFICATION-TYPE . . . ...to find out whether there were any known alarms against the entity at that time that may affect the physical entity's ability to stay operationally enabled." ::= { entStateNotifications 1 } entStateOperDisabled NOTIFICATION-TYPE . . . ...to find out whether there were any known alarms against the entity at that time that may explain why the physical entity has become operationally disabled." ::= { entStateNotifications 2 }
Notes:
It appears that the text was inadvertently swapped in the DESCRIPTION clauses for the ~Enabled and ~Disabled notification definitions.