Indicates that an AUI segment has no cable attached,
or the cable or transceiver is faulty.
Parsed from file ph-core.mib.txt
Company: None
Module: POWERHUB-CORE-MIB
Indicates that an AUI segment has no cable attached,
or the cable or transceiver is faulty.
Parsed from file POWERHUB-CORE-MIB.mib
Module: POWERHUB-CORE-MIB
Vendor: Fore Systems, Inc.
Module: POWERHUB-CORE-MIB
[Automatically extracted from oidview.com]
portStatsLossOfCarrier OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Indicates that an AUI segment has no cable attached, or the cable or transceiver is faulty." ::= { portStatsEntry 17 }
portStatsLossOfCarrier OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "Indicates that an AUI segment has no cable attached, or the cable or transceiver is faulty." ::= { portStatsEntry 17 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.326.2.6.2.2.4.1.1 | portStatsPort | 0 | 0 | Segment for which the statistics collected. |
| 1.3.6.1.4.1.326.2.6.2.2.4.1.2 | portStatsPktsIn | 0 | 0 | Good packets received on the segment. Packets are listed regardless of packet type, or whether the packet is forwarded to another… |
| 1.3.6.1.4.1.326.2.6.2.2.4.1.3 | portStatsPktsOut | 0 | 0 | Packets transmitted on the segment. This statistic is incremented when a packet is scheduled for transmission, not when it is act… |
| 1.3.6.1.4.1.326.2.6.2.2.4.1.4 | portStatsOctetsIn | 0 | 0 | Good octets received on the segment. This statistic includes 8 octets per packet to account for the preamble. |
| 1.3.6.1.4.1.326.2.6.2.2.4.1.5 | portStatsOctetsOut | 0 | 0 | Octets transmitted from the segment. This statistic is incremented when a packet is scheduled for transmission, not when it is ac… |
| 1.3.6.1.4.1.326.2.6.2.2.4.1.6 | portStatsMulticastPktsIn | 0 | 0 | Broadcast multicast packets received on the segment. This statistic is incremented for each good broadcast or multicast packet re… |
| 1.3.6.1.4.1.326.2.6.2.2.4.1.7 | portStatsMulticastPktsOut | 0 | 0 | Broadcast multicast packets transmitted from the segment. This statistic is incremented once for each broadcast or multicast pac… |
| 1.3.6.1.4.1.326.2.6.2.2.4.1.8 | portStatsTableMisses | 0 | 0 | Packets received that have unknown destination addresses. When address learning is enabled, this statistic is usually incremente… |
| 1.3.6.1.4.1.326.2.6.2.2.4.1.9 | portStatsRcvBuffErrs | 0 | 0 | Incremented each time the hub detects an incoming packet but does not have a buffer in which to store the packet. |
| 1.3.6.1.4.1.326.2.6.2.2.4.1.10 | portStatsXmitBuffErrs | 0 | 0 | Incremented each time the hub attempts to forward a packet to a busy destination segment whose output buffers all are full. |
| 1.3.6.1.4.1.326.2.6.2.2.4.1.11 | portStatsTotalCollisions | 0 | 0 | The total number of collisions detected on the segment while attempting to transmit and receive packets. For FDDI segments, this … |
| 1.3.6.1.4.1.326.2.6.2.2.4.1.12 | portStatsRcvCollisions | 0 | 0 | The number of collisions detected on the segment while listening for incoming packets. This statistic is only available for UTP … |
| 1.3.6.1.4.1.326.2.6.2.2.4.1.13 | portStatsXmitCollisions | 0 | 0 | The number of collisions detected on the segment while attempting to transmit packets. For FDDI segments, this statistic is alway… |
| 1.3.6.1.4.1.326.2.6.2.2.4.1.14 | portStatsXmitQLen | 0 | 0 | The number of outgoing packets in the transmit queue. These packets have been scheduled for transmission, but have not been trans… |
| 1.3.6.1.4.1.326.2.6.2.2.4.1.15 | portStatsPeakUtilization | 0 | 0 | The segment's maximum utilization during a one-second interval since the statistics last were cleared. For Ethernet segments, the… |
| 1.3.6.1.4.1.326.2.6.2.2.4.1.16 | portStatsCurrUtilization | 0 | 0 | For Ethernet segments, the current utilization is calculated as follows: Once per second, the current one-second utilization is co… |
| 1.3.6.1.4.1.326.2.6.2.2.4.1.18 | portStatsExcessRetries | 0 | 0 | Incremented whenever all of 15 attempts to transmit a single packet cause collisions. This can happen in very busy networks, or w… |