All MIBs › JUNIPER-TLB-MIB
Organization: Juniper Networks, Inc.
Last Updated: 2014-02-12
Category: Technology: VPN, Vendor: Juniper
Description: Juniper Networks MIB for monitoring Tunnel Load Balancing (TLB) statistics across tunnel endpoints on Juniper router platforms.
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 JUNIPER-TLB-MIB?
JUNIPER-TLB-MIB is a Juniper Networks proprietary MIB that models the Tunnel Load Balancing (TLB) feature used on Juniper routing platforms (e.g., MX-series with load-balancing PICs) to distribute traffic across pools of real servers behind virtual services. It exposes configuration and status data organized around load-balancer instances, real servers, real-server groups, virtual services, and health-check profiles. It is explicitly useful for monitoring software/service health: it reports the network monitor's CPU usage (tlbNetmonCpuUsage) and monitor mode, alongside real-server reachability implied by the IP/port bindings, making it central to confirming that the load-balancing control plane and its member servers are functioning correctly. It builds on Juniper's general chassis/PIC identification model (e.g., correlating tlbMultiservicePIC/tlbMultiserviceInterface to physical interfaces) rather than a formal external standard. It is deployed on Juniper MX-series edge/core routers configured for in-line server load balancing or traffic steering, where JUNIPER-TLB-MIB SNMP monitoring confirms real-server health across the load-balancing pool.
IPNetwork Monitor allows you to monitor SNMP objects defined in JUNIPER-TLB-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
- Juniper Networks MX-series router with Multiservices/load-balancing PIC
Monitoring Examples
An administrator would poll tlbRealServerIpAddress and tlbRealServerGroupName across the real-server table to verify which backend servers are currently members of a given group, and cross-reference tlbVirtualServiceIpAddr/tlbVirtualServicePort to confirm the front-end virtual service mapping. Watching tlbNetmonCpuUsage over time reveals whether the health-monitoring process on the multiservices PIC (tlbMultiServicePIC) is becoming overloaded, which could delay detection of a failed real server. A sudden drop in reachable real servers under a given tlbProfileName signals a load-balancing pool degradation that needs investigation.
What Can Be Monitored
- real server pool membership
- virtual service IP/port mapping
- load balancer profile assignment
- network monitor CPU usage
- monitor mode configuration
- tunnel instance status
Imported Objects
From IF-MIB
| InterfaceIndex |
From INET-ADDRESS-MIB
| InetAddress | |
| InetAddressIPv4 | |
| InetAddressType |
From JUNIPER-SMI
| jnxSDKApplicationsRoot | OBJECT-IDENTITY |
From SNMP-FRAMEWORK-MIB
| SnmpAdminString |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| OBJECT-GROUP |
From SNMPv2-MIB
| sysContact | OBJECT-TYPE |
| sysLocation | OBJECT-TYPE |
| sysName | OBJECT-TYPE |
From SNMPv2-SMI
| Counter32 | |
| Counter64 | |
| Gauge32 | |
| Integer32 | |
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-IDENTITY | |
| OBJECT-TYPE | |
| Unsigned32 |
From SNMPv2-TC
| DateAndTime | |
| DisplayString |
How to Use in IPNetwork Monitor
Example using jnxTLBRSClientPacketForwardCount OID:
OIDs
RFC description
Traffic load balancer attributes monitoring for real servers, virtual services, and server groups.
Start monitoring Juniper Networks MX-series router with Multiservices/load-balancing PIC (Tunnel Load Balancing) 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.