EFM-CU-MIB :: efmCuPAFDiscoveryCode

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsEFM-CU-MIBefmCuPAFDiscoveryCode

efmCuPAFDiscoveryCode

Module: EFM-CU-MIB

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

OID (numeric): 1.3.6.1.2.1.167.1.1.1.1.2

Node type: OBJECT-TYPE

Type: PhysAddress

Access: read-write

Description: PAF Discovery Code of the EFMCu port (PCS). A unique 6-octet code used by the Discovery function, when PAF is supported. PCS ports incapable of supporting PAF SHALL return a zero-length octet string on an attempt to read this object. An attempt to write to this object SHALL be rejected for such ports. This object MUST be instantiated for the -O subtype PCS before writing operations on the efmCuPAFRemoteDiscoveryCode (Set_if_Clear and Clear_if_Same) are performed by PMEs associated with the PCS. The initial value of this object for -R subtype ports after reset is all zeroes. For -R subtype ports, the value of this object cannot be changed directly. This value may be changed as a result of writing operation on the efmCuPAFRemoteDiscoveryCode object of remote PME of -O subtype, connected to one of the local PMEs associated with the PCS.

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.

The PAF Discovery Code maps to the local Discovery code variable in PAF (note that it does not have a corresponding Clause 45 register).

What is efmCuPAFDiscoveryCode?

This is a 6-octet code used by the PME Aggregation Function's discovery process to match up PMEs that belong to the same bonded EFM copper port. Ports that don't support aggregation return a zero-length string here and reject writes, and any change must be made while the link is down. Admins normally don't set this by hand; it's populated as part of the bonding discovery handshake.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.167.1.1.1.1.2
snmpwalk -v2c -c public <target> EFM-CU-MIB::efmCuPAFDiscoveryCode

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.167.1.1.1.1.2.1
snmpget -v2c -c public <target> EFM-CU-MIB::efmCuPAFDiscoveryCode.1

Set instance 1 (SNMPv2c):

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

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> efmCuPAFDiscoveryCode.1

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::efmCuPAFDiscoveryCode 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.1efmCuPortEFM-CU-MIB
1.3.6.1.2.1.167.1.1.1efmCuPortConfTableEFM-CU-MIB
1.3.6.1.2.1.167.1.1.1.1efmCuPortConfEntryEFM-CU-MIB
1.3.6.1.2.1.167.1.1.1.1.2efmCuPAFDiscoveryCodeEFM-CU-MIB