All MIBs › EtherLike-MIB › dot3HCStatsSymbolErrors
dot3HCStatsSymbolErrors
Module: EtherLike-MIB
OID (symbolic): EtherLike-MIB::dot3HCStatsSymbolErrors
OID (numeric): 1.3.6.1.2.1.10.7.11.1.6
Node type: OBJECT-TYPE
Type: Counter64
Access: read-only
Description: For an interface operating at 100 Mb/s, the number of times there was an invalid data symbol when a valid carrier was present.
For an interface operating in half-duplex mode at 1000 Mb/s, the number of times the receiving media is non-idle (a carrier event) for a period of time equal to or greater than slotTime, and during which there was at least one occurrence of an event that causes the PHY to indicate 'Data reception error' or 'carrier extend error' on the GMII.
For an interface operating in full-duplex mode at 1000 Mb/s, the number of times the receiving media is non-idle (a carrier event) for a period of time equal to or greater than minFrameSize, and during which there was at least one occurrence of an event that causes the PHY to indicate 'Data reception error' on the GMII.
For an interface operating at 10 Gb/s, the number of times the receiving media is non-idle (a carrier event) for a period of time equal to or greater than minFrameSize, and during which there was at least one occurrence of an event that causes the PHY to indicate 'Receive Error' on the XGMII.
The count represented by an instance of this object is incremented at most once per carrier event, even if multiple symbol errors occur during the carrier event. This count does not increment if a collision is present.
This counter is a 64 bit version of dot3StatsSymbolErrors. It should be used on interfaces operating at 10 Gb/s or faster.
Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.
What is dot3HCStatsSymbolErrors?
This 64-bit counter records invalid physical-layer symbol events on this interface: for 100 Mb/s links it counts invalid data symbols seen during a valid carrier, and for half-duplex 1000 Mb/s links it counts carrier events with at least one such error. Admins treat rising symbol errors as a sign of physical-layer signal quality problems, distinct from higher-layer frame errors, and use the 64-bit version on fast links to avoid counter wraparound. For example, a climbing symbol error count on a 1000 Mb/s half-duplex segment could point to electrical noise or a marginal cable run degrading the physical signal.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.2.1.10.7.11.1.6 snmpwalk -v2c -c public <target> EtherLike-MIB::dot3HCStatsSymbolErrors
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.2.1.10.7.11.1.6.1 snmpget -v2c -c public <target> EtherLike-MIB::dot3HCStatsSymbolErrors.1
Start monitoring Vendor-neutral Ethernet interface, any manufacturer (IEEE 802.3 EtherLike statistics) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the EtherLike-MIB::dot3HCStatsSymbolErrors OID value, configure state conditions and alerts, and monitor any Vendor-neutral Ethernet interface, any manufacturer (IEEE 802.3 EtherLike statistics) from a single console.
OID Breakdown
Upper-level ancestors (7 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.2 | mgmt | AXON-MIB |
| 1.3.6.1.2.1 | mib_2 | AXON-MIB |
| 1.3.6.1.2.1.10 | transmission | CHECKPOINT-MIB-2 |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.2.1.10.7 | dot3 | EtherLike-MIB |
| 1.3.6.1.2.1.10.7.11 | dot3HCStatsTable | EtherLike-MIB |
| 1.3.6.1.2.1.10.7.11.1 | dot3HCStatsEntry | EtherLike-MIB |
| 1.3.6.1.2.1.10.7.11.1.6 | dot3HCStatsSymbolErrors | EtherLike-MIB |