B100-MIB

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsB100-MIB

Organization: KEMP Technologies

Last Updated: 2011-12-01

Category: Device Management

Description: Manages KEMP Technologies B100 load balancer appliances, monitoring virtual services, real servers, and health check status.

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 B100-MIB?

B100-MIB is KEMP Technologies' proprietary MIB for the B100-series LoadMaster load balancer/application delivery controller appliances. It exposes system version/configuration info, a virtual service (VS) table and a real server (RS) table, and daemon operational state. It directly supports hardware/software status monitoring: version tracks the running software version, daemonState reports whether the core load-balancing daemon process is up, numServices reports the count of configured/active virtual services, and b100VSTable/b100RSTable let an operator check the status of individual virtual services and the backend real servers behind each — central to catching a failed backend server or a virtual service with no healthy targets. It uses its own private enterprise MIB tree (b100Notifications) and follows standard load-balancer/health-check monitoring conventions without an explicit dependency on external standard MIBs evident here. It's deployed on KEMP LoadMaster/B100 appliances in front of application server farms, polled by NMS platforms to track load-balancing service and backend server health. Engineers can download the B100-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in B100-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

  • KEMP Technologies B100/LoadMaster application delivery controller (load balancer)

Monitoring Examples

Walking b100VSTable reveals each configured virtual service, while the paired b100RSTable shows the real (backend) servers behind each one; combined with numServices and daemonState, an admin can confirm the load-balancing daemon is running and quickly spot a virtual service that currently has zero healthy real servers behind it. Checking tcpTimeOut and udpTimeOut settings alongside this can reveal whether overly aggressive timeout values are causing premature connection drops for legitimate client sessions.

What Can Be Monitored

  • virtual service configuration and count
  • real server status per virtual service
  • load-balancing daemon state
  • TCP/UDP timeout settings
  • software version
Imported Objects

From INET-ADDRESS-MIB

InetAddress
InetAddressType
InetPortNumber

From ONE4NET-MIB

one4netMODULE-IDENTITY

From SNMPv2-SMI

Counter32
Counter64
Integer32
IpAddress
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE

From SNMPv2-TC

TEXTUAL-CONVENTION
TimeInterval

How to Use in IPNetwork Monitor

Example using vSConns OID:

Select a KEMP Technologies B100/LoadMaster application delivery controller 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 vSConns into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The total number of connections for this VS. 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 Counter32-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.
OIDs

RFC description

Load Master configuration and monitoring for KEMP Technologies load balancing, managing virtual services and real servers.

Start monitoring KEMP Technologies B100/LoadMaster application delivery controller 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.

Download B100-MIB