DES3526-L2MGMT-MIB :: swL2IpMacBindingDHCPSnoopState

MIB Reference — IPNetwork Monitor · Updated October 02, 2026

All MIBs › DES3526-L2MGMT-MIB › swL2IpMacBindingDHCPSnoopState

swL2IpMacBindingDHCPSnoopState

Module: DES3526-L2MGMT-MIB

OID (symbolic): DES3526-L2MGMT-MIB::swL2IpMacBindingDHCPSnoopState

OID (numeric): 1.3.6.1.4.1.171.11.64.1.2.7.7

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: When the dhcp_snoop function is enabled, all address_binding disabled ports will act as DHCP server ports (the switch will learn IP addresses through DHCP server ports (by DHCP OFFER and DHCP ACK packets)).

The auto-learned IP-MAC binding entry will be mapped to a specific source port based on the MAC address learning function. This entry will be created as an ACL-mode binding entry for this specific port. Each entry is associated with a lease time. When the lease time expires, the expired entry will be removed from this port. The automatically learned binding entry can be moved from one port to another port if the DHCP snooping function has learned that the MAC address has moved to a different port.

Consider a case where DHCP snooping learns a binding entry, and the same IP-MAC binding entry has been statically configured. Suppose that the learned information is consistent with the statically configured entry, then the automatically learned entry will not be created. Suppose the entry is statically configured in ARP mode, since the automatically learned entry will be created in ACL mode, the entry will become ACL mode. Suppose the entry is statically configured on one port and the entry is automatically learned on another port, then both entries will exist.

When the dhcp_snoop function is disabled, all of the automatically learned binding entries will be removed.

What is swL2IpMacBindingDHCPSnoopState?

Enables DHCP snooping-based auto-learning of IP-MAC bindings on ports where strict binding isn't configured, treating address-binding-disabled ports as trusted DHCP server ports. Admins enable this so legitimately DHCP-assigned clients are automatically whitelisted without manual entries, while rogue DHCP servers elsewhere are still untrusted.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.171.11.64.1.2.7.7
snmpwalk -v2c -c public <target> DES3526-L2MGMT-MIB::swL2IpMacBindingDHCPSnoopState

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.171.11.64.1.2.7.7.1
snmpget -v2c -c public <target> DES3526-L2MGMT-MIB::swL2IpMacBindingDHCPSnoopState.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.171.11.64.1.2.7.7.1 i <value>

Start monitoring D-Link DES-3526 managed switch with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the DES3526-L2MGMT-MIB::swL2IpMacBindingDHCPSnoopState OID value, configure state conditions and alerts, and monitor any D-Link DES-3526 managed switch from a single console.

OID Breakdown

Upper-level ancestors (10 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.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.171d_linkDE1500-MIB
1.3.6.1.4.1.171.11dlink_mgmtDES2218-MIB
1.3.6.1.4.1.171.11.64des3500SeriesProdSW3500PRIMGMT-MIB
1.3.6.1.4.1.171.11.64.1des3526SW3500PRIMGMT-MIB
Numeric OIDNameModule
1.3.6.1.4.1.171.11.64.1.2swL2MgmtMIBDES3526-L2MGMT-MIB
1.3.6.1.4.1.171.11.64.1.2.7swL2IpMacBindingMgmtDES3526-L2MGMT-MIB
1.3.6.1.4.1.171.11.64.1.2.7.7swL2IpMacBindingDHCPSnoopStateDES3526-L2MGMT-MIB