BCN-DHCPV4-MIB :: bcnDhcpv4LeaseStatsSuccess

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › BCN-DHCPV4-MIB › bcnDhcpv4LeaseStatsSuccess

bcnDhcpv4LeaseStatsSuccess

Module: BCN-DHCPV4-MIB

OID (symbolic): BCN-DHCPV4-MIB::bcnDhcpv4LeaseStatsSuccess

OID (numeric): 1.3.6.1.4.1.13315.3.1.1.2.1.3

Node type: OBJECT-TYPE

Type: Gauge32

Access: read-only

Description: The number of successful DHCPv4 leases issued per second.

What is bcnDhcpv4LeaseStatsSuccess?

Measures the current rate of successfully issued DHCPv4 leases in leases per second. This throughput metric helps administrators assess the performance and load of the DHCPv4 service in real time.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.13315.3.1.1.2.1.3
snmpwalk -v2c -c public <target> BCN-DHCPV4-MIB::bcnDhcpv4LeaseStatsSuccess

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.13315.3.1.1.2.1.3.1
snmpget -v2c -c public <target> BCN-DHCPV4-MIB::bcnDhcpv4LeaseStatsSuccess.1

Start monitoring BlueCat Networks DNS/DHCP/IPAM appliances with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the BCN-DHCPV4-MIB::bcnDhcpv4LeaseStatsSuccess OID value, configure state conditions and alerts, and monitor any BlueCat Networks DNS/DHCP/IPAM appliances from a single console.

How to Use in IPNetwork Monitor

Select a BlueCat Networks DNS/DHCP/IPAM appliance as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type bcnDhcpv4LeaseStatsSuccess into the Find box to locate it in the OID tree, then select it and click OK. The number of successful DHCPv4 leases issued per second. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Gauge32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (9 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.13315bluecatnetworksBLUECATNETWORKS-MIB
1.3.6.1.4.1.13315.3bcnMgmtBCN-SMI-MIB
1.3.6.1.4.1.13315.3.1bcnServicesBCN-SMI-MIB
Numeric OIDNameModule
1.3.6.1.4.1.13315.3.1.1bcnDhcpv4BCN-DHCPV4-MIB
1.3.6.1.4.1.13315.3.1.1.2bcnDhcpv4ObjectsBCN-DHCPV4-MIB
1.3.6.1.4.1.13315.3.1.1.2.1bcnDhcpv4ServiceStatusBCN-DHCPV4-MIB
1.3.6.1.4.1.13315.3.1.1.2.1.3bcnDhcpv4LeaseStatsSuccessBCN-DHCPV4-MIB