All MIBs › ZTE-AN-EPON-SERVICE-MIB › dot3EponFecPCSCodingViolation
dot3EponFecPCSCodingViolation
Module: ZTE-AN-EPON-SERVICE-MIB
OID (symbolic): ZTE-AN-EPON-SERVICE-MIB::dot3EponFecPCSCodingViolation
OID (numeric): 1.3.6.1.4.1.3902.1082.500.31.4.1.1.1
Node type: OBJECT-TYPE
Type: Counter64
Access: read-only
Description: For 100 Mbps operation it is a count of the number of times an invalid code-group is received, other than the /H/ code-group. For 1000 Mbps operation it is a count of the number of times an invalid codegroup is received, other than the /V/ code-group. /H/ denotes a special 4b5b codeword of [802.3] 100 Mbps PCS layer (clause 24), and /V/ denotes a special 8b10b codeword of the [802.3] 1000 Mbps PCS layer (clause 36). This object is applicable for an OLT and an ONU. At the OLT it has a distinct value for each virtual interface. Discontinuities of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of the ifCounterDiscontinuityTime object of the Interface MIB module.
What is dot3EponFecPCSCodingViolation?
This read-only 64-bit counter, in octets, reports the number of invalid PCS code-groups received on this EPON interface (excluding the special /H/ or /V/ idle codewords depending on link speed), and is unaffected by whether FEC is enabled. An admin monitors it as a raw physical-layer error indicator that can reveal a degrading optical signal even before FEC statistics show a problem. For example, a steadily rising coding-violation count on an ONU's uplink suggests a deteriorating fiber connection or transceiver worth inspecting.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.3902.1082.500.31.4.1.1.1 snmpwalk -v2c -c public <target> ZTE-AN-EPON-SERVICE-MIB::dot3EponFecPCSCodingViolation
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.3902.1082.500.31.4.1.1.1.1 snmpget -v2c -c public <target> ZTE-AN-EPON-SERVICE-MIB::dot3EponFecPCSCodingViolation.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::dot3EponFecPCSCodingViolation OID value, configure state conditions and alerts, and monitor any ZTE EPON OLTs/ONUs from a single console.
How to Use in IPNetwork Monitor
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.1 | dot3EponFecPCSCodingViolation | ZTE-AN-EPON-SERVICE-MIB |