EFM-CU-MIB :: efmCuPAFRemoteDiscoveryCode

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsEFM-CU-MIBefmCuPAFRemoteDiscoveryCode

efmCuPAFRemoteDiscoveryCode

Module: EFM-CU-MIB

OID (symbolic): EFM-CU-MIB::efmCuPAFRemoteDiscoveryCode

OID (numeric): 1.3.6.1.2.1.167.1.2.1.1.3

Node type: OBJECT-TYPE

Type: PhysAddress

Access: read-write

Description: PAF Remote Discovery Code of the PME port at the CO. The 6-octet Discovery Code of the peer PCS connected via the PME. Reading this object results in a Discovery Get operation. Setting this object to all zeroes results in a Discovery Clear_if_Same operation (the value of efmCuPAFDiscoveryCode at the peer PCS SHALL be the same as efmCuPAFDiscoveryCode of the local PCS associated with the PME for the operation to succeed). Writing a non-zero value to this object results in a Discovery Set_if_Clear operation. A zero-length octet string SHALL be returned on an attempt to read this object when PAF aggregation is not enabled.

This object is irrelevant in CPE port (-R) subtypes: in this case, a zero-length octet string SHALL be returned on an attempt to read this object; writing to this object SHALL be rejected.

Discovery MUST be performed when the link is Down. Attempts to change this object MUST be rejected (in case of SNMP with the error inconsistentValue), if the link is Up or Initializing.

If a Clause 45 MDIO Interface to the PMA/PMD is present, then this object is a function of 10P/2B aggregation discovery control register, Discovery operation result bits in 10P/2B aggregation and discovery status register and 10P/2B aggregation discovery code register.

What is efmCuPAFRemoteDiscoveryCode?

This read-write value represents the PAF Discovery Code of the peer central-office PCS as seen through this individual PME. Reading it triggers a Discovery Get; writing all zeros triggers a Clear_if_Same operation, and writing a non-zero value triggers a Set_if_Clear operation, all part of the aggregation-discovery handshake between bonded PMEs. It's irrelevant on CPE (-R) side ports, which always return a zero-length string.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.167.1.2.1.1.3
snmpwalk -v2c -c public <target> EFM-CU-MIB::efmCuPAFRemoteDiscoveryCode

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.167.1.2.1.1.3.1
snmpget -v2c -c public <target> EFM-CU-MIB::efmCuPAFRemoteDiscoveryCode.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.2.1.167.1.2.1.1.3.1 s <value>

Start monitoring DSLAM/EFM access multiplexer or CPE (802.3ah EFM Copper, vendor-neutral IETF standard) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the EFM-CU-MIB::efmCuPAFRemoteDiscoveryCode OID value, configure state conditions and alerts, and monitor any DSLAM/EFM access multiplexer or CPE (802.3ah EFM Copper, vendor-neutral IETF standard) from a single console.

OID Breakdown

Upper-level ancestors (6 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.2mgmtAXON-MIB
1.3.6.1.2.1mib_2AXON-MIB
Numeric OIDNameModule
1.3.6.1.2.1.167efmCuMIBEFM-CU-MIB
1.3.6.1.2.1.167.1efmCuObjectsEFM-CU-MIB
1.3.6.1.2.1.167.1.2efmCuPmeEFM-CU-MIB
1.3.6.1.2.1.167.1.2.1efmCuPmeConfTableEFM-CU-MIB
1.3.6.1.2.1.167.1.2.1.1efmCuPmeConfEntryEFM-CU-MIB
1.3.6.1.2.1.167.1.2.1.1.3efmCuPAFRemoteDiscoveryCodeEFM-CU-MIB