All MIBs › ZTE-AN-EPON-SERVICE-MIB › dot3EponFecAbility
dot3EponFecAbility
Module: ZTE-AN-EPON-SERVICE-MIB
OID (symbolic): ZTE-AN-EPON-SERVICE-MIB::dot3EponFecAbility
OID (numeric): 1.3.6.1.4.1.3902.1082.500.31.4.1.1.2
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: An object that indicates the support of operation of the optional FEC sublayer of the 1000BASE-PX PHY, specified in [802.3ah] clause 65.2. unknown(1) value is assigned in initialization, for non FEC support state or type not yet known. unsupported(2) value is assigned when sublayer is not supported. supported(3) value is assigned when sublayer is supported. This object is applicable for an OLT, with the same value for all virtual interfaces, and for an ONU. the FEC counters will have a zero value, when the interface is not supporting FEC. The counters: dot3EponFecPCSCodingViolation - not affected by FEC ability. dot3EponFecCorrectedBlocks - has a zero value when dot3EponFecAbility is unknown (1) and unsupported (2). dot3EponFecUncorrectableBlocks - has a zero value when dot3EponFecAbility is unknown (1) and unsupported (2). dot3EponFecBufferHeadCodingViolation - has a zero value when dot3EponFecAbility is unknown (1) and unsupported (2).
What is dot3EponFecAbility?
This read-only value reports whether the optional Forward Error Correction (FEC) sublayer of the 1000BASE-PX PHY, per 802.3ah clause 65.2, is unknown, unsupported, or supported on this interface; several other FEC counters read as zero when this value is unknown or unsupported. An admin checks it before relying on the FEC-related correction counters, to confirm the hardware actually supports FEC. For example, seeing unsupported(2) here explains why dot3EponFecCorrectedBlocks always reads zero on that interface regardless of actual link error rates.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.3902.1082.500.31.4.1.1.2 snmpwalk -v2c -c public <target> ZTE-AN-EPON-SERVICE-MIB::dot3EponFecAbility
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.3902.1082.500.31.4.1.1.2.1 snmpget -v2c -c public <target> ZTE-AN-EPON-SERVICE-MIB::dot3EponFecAbility.1
Start monitoring ZTE EPON OLTs/ONUs with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ZTE-AN-EPON-SERVICE-MIB::dot3EponFecAbility OID value, configure state conditions and alerts, and monitor any ZTE EPON OLTs/ONUs 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.3902 | zte | DPI-MIB |
| 1.3.6.1.4.1.3902.1082 | zxAccessNode | ZTE-AN-SMI |
| 1.3.6.1.4.1.3902.1082.500 | zxAnPon | ZTE-AN-SMI |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.3902.1082.500.31 | dot3Objects | ZTE-AN-EPON-SERVICE-MIB |
| 1.3.6.1.4.1.3902.1082.500.31.4 | dot3EponFecObjects | ZTE-AN-EPON-SERVICE-MIB |
| 1.3.6.1.4.1.3902.1082.500.31.4.1 | dot3EponFecTable | ZTE-AN-EPON-SERVICE-MIB |
| 1.3.6.1.4.1.3902.1082.500.31.4.1.1 | dot3EponFecEntry | ZTE-AN-EPON-SERVICE-MIB |
| 1.3.6.1.4.1.3902.1082.500.31.4.1.1.2 | dot3EponFecAbility | ZTE-AN-EPON-SERVICE-MIB |