All MIBs › LBHUB-MSH-MIB › a3ComRingStatLostFrames
a3ComRingStatLostFrames
Module: LBHUB-MSH-MIB
OID (symbolic): LBHUB-MSH-MIB::a3ComRingStatLostFrames
OID (numeric): 1.3.6.1.4.1.43.10.16.2.2.1.7
Node type: OBJECT-TYPE
Type: Counter
Access: read-only
Description: In the token ring architecture a station that transmits a frame will eventually receive that frame after it has gone all the way around the ring. The station that sent the frame then removes that frame from the ring. Whenever a station places a frame onto the ring it starts a timer. It is expected that the frame will return to the station before that timer expires. If this does not happen then this error counter is incremented.
Note that this is a non-isolating error and so it is not possible to determine where on the network the fault occurred.
GENERAL: Soft Errors
The token ring architecture includes an inherent error monitoring protocol. Each station records local errors. These errors are generically referred to as 'soft errors'. Soft errors represent intermittent faults that temporarily disrupt normal operation of the ring. Stations periodically transmit their soft error counters onto the ring where they can be received by any stations which have the ring error monitor functional address active.
There are two categories of soft error. Isolating errors and Non-isolating errors. An isolating error will be reported by exactly one station on the ring and the error is known to have occurred between that station and it's upstream neighbour. The second category are non-isolating. That is, errors of this nature may be seen and reported by more than one ring station. With these errors it is not possible to resolve the source of the error.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.43.10.16.2.2.1.7 snmpwalk -v2c -c public <target> LBHUB-MSH-MIB::a3ComRingStatLostFrames
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.43.10.16.2.2.1.7.1 snmpget -v2c -c public <target> LBHUB-MSH-MIB::a3ComRingStatLostFrames.1
Start monitoring 3Com LANBuilder MSH modular stackable hub with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the LBHUB-MSH-MIB::a3ComRingStatLostFrames OID value, configure state conditions and alerts, and monitor any 3Com LANBuilder MSH modular stackable hub from a single console.
OID Breakdown
Upper-level ancestors (9 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.43 | a3Com | A3COM-BRIDGE-R3-MIB |
| 1.3.6.1.4.1.43.10 | generic | A3Com-products-MIB |
| 1.3.6.1.4.1.43.10.16 | tokenRing | A3COM0004-GENERIC |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.43.10.16.2 | a3ComRingStationParams | LBHUB-MSH-MIB |
| 1.3.6.1.4.1.43.10.16.2.2 | a3ComRingStatStandardStats | LBHUB-MSH-MIB |
| 1.3.6.1.4.1.43.10.16.2.2.1 | a3ComRingStatStdStatsEntry | LBHUB-MSH-MIB |
| 1.3.6.1.4.1.43.10.16.2.2.1.7 | a3ComRingStatLostFrames | LBHUB-MSH-MIB |