An ospfv3VirtIfStateChange notification signifies that
there has been a change in the state of an OSPFv3 virtual
interface.
          
This notification should be generated when the interface
state regresses (e.g., goes from Point-to-Point to Down)
or progresses to a terminal state (i.e., Point-to-Point).

An ospfv3IfStateChange notification signifies that there
has been a change in the state of a non-virtual
OSPFv3 interface.  This notification should be generated
when the interface state regresses (e.g., goes
from DR to Down) or progresses to a terminal
state (i.e., Point-to-Point, DR Other, DR, or
Backup).

An ospfv3NssaTranslatorStatusChange notification
indicates that there has been a change in the router's
ability to translate OSPFv3 NSSA LSAs into OSPFv3 External
LSAs.  This notification should be generated when the
Translator Status transitions from or to any defined
status on a per-area basis.

An ospfv3RestartStatusChange notification signifies that
there has been a change in the graceful restart
state for the router.  This notification should be
generated when the router restart status
changes.

An ospfv3NbrRestartHelperStatusChange notification
signifies that there has been a change in the
graceful restart helper state for the neighbor.
This notification should be generated when the
neighbor restart helper status transitions for a neighbor.

An ospfv3VirtNbrRestartHelperStatusChange
notification signifies that there has been a
change in the graceful restart helper state for
the virtual neighbor.  This notification should be
generated when the virtual neighbor restart helper status
transitions for a virtual neighbor.

An ospfv3NbrStateChange notification signifies that
there has been a change in the state of a
non-virtual OSPFv3 neighbor.  This notification should be
generated when the neighbor state regresses
(e.g., goes from Attempt or Full to 1-Way or
Down) or progresses to a terminal state (e.g.,
2-Way or Full).  When a neighbor transitions
from or to Full on non-broadcast multi-access
and broadcast networks, the notification should be
generated by the Designated Router.  A Designated
Router transitioning to Down will be noted by
ospfIfStateChange.

An ospfv3VirtNbrStateChange notification signifies
that there has been a change in the state of an OSPFv3
virtual neighbor.  This notification should be generated
when the neighbor state regresses (e.g., goes
from Attempt or Full to 1-Way or Down) or
progresses to a terminal state (e.g., Full).

An ospfv3IfConfigError notification signifies that a
packet has been received on a non-virtual
interface from a router whose configuration
parameters conflict with this router's
configuration parameters.  Note that the event
optionMismatch should cause a notification only if it
prevents an adjacency from forming.

An ospfv3VirtIfConfigError notification signifies that a
packet has been received on a virtual interface
from a router whose configuration parameters
conflict with this router's configuration
parameters.  Note that the event optionMismatch
should cause a notification only if it prevents an
adjacency from forming.

An ospfv3IfRxBadPacket notification signifies that an
OSPFv3 packet that cannot be parsed has been received on a
non-virtual interface.

An ospfv3VirtIfRxBadPacket notification signifies
that an OSPFv3 packet that cannot be parsed has been
received on a virtual interface.

An ospfv3LsdbOverflow notification signifies that the
number of LSAs in the router's link state
database has exceeded ospfv3ExtAreaLsdbLimit.

An ospfv3LsdbApproachingOverflow notification signifies
that the number of LSAs in the router's
link state database has exceeded ninety percent of
ospfv3ExtAreaLsdbLimit.