All MIBs › H3C-DHCPSNOOP-MIB
Organization: Huawei-3com Technologies Co.,Ltd.
Last Updated: 2005-01-14
Category: Protocol: DHCP, Vendor: H3C/HH3C
Description: H3C MIB for DHCP snooping configuration, maintaining binding tables to prevent rogue DHCP server attacks.
Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.
What Is H3C-DHCPSNOOP-MIB?
H3C-DHCPSNOOP-MIB is an H3C private-enterprise MIB for DHCP Snooping, a Layer 2 security feature that inspects DHCP traffic on untrusted ports and builds a binding table of legitimate IP-to-MAC-to-port leases to block rogue DHCP servers and DHCP-based spoofing attacks. It is expected to expose snooping profile/policy configuration per VLAN or interface along with a table of learned DHCP bindings. Its monitoring focus is security/fault detection rather than hardware health: an operator checks whether snooping is enabled where expected and inspects the binding table for anomalies suggesting an attack or misconfigured trust setting. It naturally complements H3C-DHCPRELAY-MIB and standard bridge/VLAN management concepts, since bindings are indexed by port and VLAN. Deployment context is H3C access-layer switches in enterprise/campus networks protecting against DHCP spoofing and rogue-server attacks, and administrators can download the H3C-DHCPSNOOP-MIB file to load it directly into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in H3C-DHCPSNOOP-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- H3C access-layer switch
Monitoring Examples
This excerpt lists no object or table names beyond the brief description 'the DHCP Snooping profile', so a concrete polling scenario cannot be grounded in confirmed identifiers from the source. In a real deployment, an administrator would typically poll a per-VLAN/interface enable flag and a DHCP binding table to detect an unauthorized DHCP server responding to client requests, but none of these object names are verified here.
What Can Be Monitored
- DHCP snooping enable state per VLAN/interface
- DHCP binding table entries
- rogue DHCP server / spoofing detection
Imported Objects
From HUAWEI-3COM-OID-MIB
| h3cCommon | OBJECT-IDENTITY |
From HUAWEI-LswVLAN-MIB
| hwdot1qVlanIndex | OBJECT-TYPE |
From INET-ADDRESS-MIB
| InetAddress | |
| InetAddressType |
From RFC1213-MIB
| ifIndex |
From SNMPv2-SMI
| Integer32 | |
| IpAddress | |
| MODULE-IDENTITY | |
| OBJECT-TYPE |
From SNMPv2-TC
| MacAddress | |
| RowStatus | |
| TruthValue |
OIDs
RFC description
H3C vendor-specific MIB for DHCP Snooping feature management, detecting unauthorized DHCP servers on networks.
Start monitoring H3C access-layer switch (DHCP Snooping) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.