o block check errors Number of times a received frame containing an integral number of octets failed the FCS check. o creation time Time at which the station was created. o directed beacons received Number of times the link detected the directed beacon process. o duplicate address test failures Number of times the duplicate address test failed (detected that the link address was a duplicate). o duplicate tokens detected Number of times the MAC address test failed (detected that the link address was a duplicate). o error count Total number of frames that were in error with the E indicator reset, indicating that the error occurred between the upstream MAC and this one. o fci strip errors Number of times a frame content independent strip operation (bridge strip) was terminated by receipt of a token. o frame count Total number of frames seen by this link, other than tokens. o frame status errors Number of times a received frame had the E indicator in error (missing or set) and the FCS was correct. o lost count Counter lost count. o multicast octets received Number of multicast data octets that were successfully received in multicast frames of type LLC, implementer, reserved, or SMT. The count does not include the MAC envelope. o multicast octets sent Number of multicast data octets that were successfully sent in multicast frames of type LLC, implementer, reserved, or SMT. The count does not include the MAC envelope. o multicast pdus received Number of multicast frames that were successfully received of type LLC, implementer, reserved, or SMT. o multicast pdus sent Number of multicast frames that were successfully sent of type LLC, implementer, reserved, or SMT. o octets received Number of octets successfully received in frames of type LLC, implementer, reserved, or SMT. The count does not include the MAC envelope. o octets sent Number of octets successfully sent in frames of type LLC, implementer, reserved, or SMT. The count does not include the MAC envelope. o pdu length errors Number of times a received frame had an invalid length, either too long or short for the type, or had an alignment error (odd number of symbols). o pdus received Number of frames successfully received in frames of type LLC, implementer, reserved, or SMT. o pdus sent Number of frames successfully sent in frames of type LLC, implementer, reserved, or SMT. o receive data overruns Number of times the hardware lost one or more consecutive, only partially complete incoming frames because it was unable to keep up with the medium rate. An example is overrun of a bit or octet FIFO queue because of inability to copy data from adapter to host promptly. In conjunction with total frames received, provides a measure of hardware resource and bandwidth failures. o ring beacons initiated Number of times the ring beacon process was initiated by this link. o ring initializations initiated Number of times a ring reinitialization was initiated by this link. o ring initializations received Number of times a ring reinitialization was initiated by some other link. o ring purge errors Number of times the ring purger received a token while still in the ring purge state. o token count Number of times a token has been seen by this link. o transmit underruns Number of times a transmit underrun occurred. This indicates the transmit FIFO became empty during frame transmission. o traces initiated Number of times the pc trace process was initiated by this link. o transmit failures Number of times a transmit error, other than underrun, occurred. This does not include errors in transmitting MAC type frames. o unavailable link buffers Number of times a complete, fully received frame was discarded because no link buffer was available. In conjunction with total frames received, provides a measure of station-buffer-related receive problems. o unavailable user buffers Number of times no user buffer was available for an incoming frame that passed all filtering for the port. These are the buffers supplied by users on receive requests. In conjunction with total frames received, provides a measure of user-buffer- related receive problems. o unrecognized individual destination pdus Number of times a received LLC frame with an individual destination MAC address was discarded because there was no port with the Ethernet protocol type, SNAP protocol identifier, or LLC SAP address enabled. Only frames containing individual destination MAC addresses are counted. o unrecognized multicast destination pdus Number of times a received LLC frame with a multicast destination MAC address was discarded because there was no port with the Ethernet protocol type, SNAP protocol identifier, or LLC SAP address enabled. Only frames containing multicast destination MAC addresses are counted.