o  block check error

    Frame with FCS error was received.

    On OpenVMS, this event cannot be logged due to VMS device driver
    restrictions.  However, if such an event occurs, its corresponding
    counter will be incremented.

 o  directed beacon received

    A directed beacon was received.

    On OpenVMS, this event cannot be logged due to VMS device driver
    restrictions.  However, if such an event occurs, its corresponding
    counter will be incremented.

 o  duplicate address test failure

    Duplicate address algorithm detected a duplicate.

    On OpenVMS, this event cannot be logged due to VMS device driver
    restrictions.  However, if such an event occurs, its corresponding
    counter will be incremented.

 o  duplicate token detected

    Duplicate token is detected.

    On OpenVMS, this event cannot be logged due to VMS device driver
    restrictions.  However, if such an event occurs, its corresponding
    counter will be incremented.

 o  fci strip error

    Frame content independent strip was terminated by a token.

    On OpenVMS, this event cannot be logged due to VMS device driver
    restrictions.  However, if such an event occurs, its corresponding
    counter will be incremented.

 o  frame status error

    Frame with good FCS, but E indicator set was received.

    On OpenVMS, this event cannot be logged due to VMS device driver
    restrictions.  However, if such an event occurs, its corresponding
    counter will be incremented.

 o  link buffer unavailable

    No buffer was available to to receive a frame.

    On OpenVMS, this event cannot be logged due to VMS device driver
    restrictions.  However, if such an event occurs, its corresponding
    counter will be incremented.

 o  pdu length error

    Frame of invalid length or odd number of symbols was received.

    On OpenVMS, this event cannot be logged due to VMS device driver
    restrictions.  However, if such an event occurs, its corresponding
    counter will be incremented.

 o  receive data overrun

    A receive overrun hardware error was detected.

    On OpenVMS, this event cannot be logged due to VMS device driver
    restrictions.  However, if such an event occurs, its corresponding
    counter will be incremented.

 o  ring beacon initiated

    Link started the beacon process.

    On OpenVMS, this event cannot be logged due to VMS device driver
    restrictions.  However, if such an event occurs, its corresponding
    counter will be incremented.

 o  ring initialization initiated

    Ring is reinitialized by this link.

    On OpenVMS, this event can only be logged by certain versions of
    the VMS device drivers.  Even in those cases where the drivers
    support this event, it will not be logged on a one-to-one basis
    with increases in its corresponding counter.  Instead, only one
    error report will be issued for any number of these events that
    occur within a sampling period.  This is intended to prevent the
    possibility of flooding OPCOM with these events.

 o  ring initialization received

    Ring is reinitialized by some other link.

    On OpenVMS, this event can only be logged by certain versions of
    the VMS device drivers.  Even in those cases where the drivers
    support this event, it will not be logged on a one-to-one basis
    with increases in its corresponding counter.  Instead, only one
    error report will be issued for any number of these events that
    occur within a sampling period.  This is intended to prevent the
    possibility of flooding OPCOM with these events.

 o  ring purge error

    Ring purger received a token while purging.

    On OpenVMS, this event cannot be logged due to VMS device driver
    restrictions.  However, if such an event occurs, its corresponding
    counter will be incremented.

 o  trace initiated

    PC-trace was initiated by this link.

    On OpenVMS, this event cannot be logged due to VMS device driver
    restrictions.  However, if such an event occurs, its corresponding
    counter will be incremented.

 o  transmit failure

    Failure to transmit operation other than underrun.

    On OpenVMS, this event cannot be logged due to VMS device driver
    restrictions.  However, if such an event occurs, its corresponding
    counter will be incremented.

 o  transmit underrun

    Transmit failed due to underrun.

    On OpenVMS, this event cannot be logged due to VMS device driver
    restrictions.  However, if such an event occurs, its corresponding
    counter will be incremented.

 o  unrecognized individual pdu destination

    Frame with unrecognized DSAP or port-id.

 o  unrecognized multicast pdu destination

    Frame with unrecognized DSAP or port-id.

    On OpenVMS, this event is blocked by default.  If you wish to
    unblock this event, you may do so using the NET$EVENT_LOCAL
    script.  For more information about that script, refer to
    HELP NETWORK_MANAGEMENT EVENT_DISPATCHER.

 o  user buffer unavailable

    Data link user did not supply a receive buffer.