JETNEXUS-MIB

All MIBs › JETNEXUS-MIB

Organization: jetNEXUS

Last Updated: 2014-10-18

Category: Domain: Network Management, Web and Application Servers

Description: Defines managed objects for jetNEXUS application delivery controllers and load balancers, supporting virtual service and pool monitoring.

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

JETNEXUS-MIB is a jetNEXUS proprietary MIB for its application delivery controller (ADC) and load-balancer appliances. At the jetnexusGlobal level it exposes overall device throughput (jetnexusOverallInputBytes/OutputBytes), compression effectiveness (jetnexusCompressedInputBytes/OutputBytes), software version, total client connections, and system resource gauges (jetnexusCpuPercent, jetnexusDiskFreePercent, jetnexusMemoryPercent). Below that, the jnvirtualserviceTable reports per-virtual-service load-balancing metrics — address:port, input/output byte counters, cache byte usage, compression percent, present client connections, hit count, and cache hit rate (jnvirtualserviceCacheHitsPercent) alongside a status object — while the jnrealserverTable reports the same class of metrics per backend real server bound to a virtual service, including jnrealserverPoolUsage and jnrealserverRSStatus. This structure lets an operator drill from overall appliance health down to a specific virtual service and further to an individual backend pool member. It depends on nothing beyond standard SNMPv2-SMI/CONF conventions and is self-contained under the jetnexusMIB enterprise arc. It is deployed on jetNEXUS ADC/load-balancer appliances in front of web application server pools, and administrators searching for the JETNEXUS-MIB download will use it to monitor virtual service and real server health via SNMP.

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

jetNEXUS application delivery controller / load balancer appliances

Monitoring Examples

An operator polls jnvirtualservicePresentClientConnections and jnvirtualserviceVSStatus for a given virtual service to confirm it's accepting traffic, then checks jnrealserverRSStatus and jnrealserverPresentClientConnections for each backend real server bound to it; a real server showing jnrealserverRSStatus as down while jnvirtualservicePresentClientConnections keeps climbing would indicate the remaining healthy servers are absorbing an uneven load.

What Can Be Monitored

overall device throughput and compression byte counters
system CPU, memory, and disk-free gauges
per-virtual-service connection counts and cache hit rate
virtual service status
per-real-server pool usage and status
per-real-server input/output byte and hit counters

Imported Objects

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter64
Integer32
MODULE-IDENTITY
OBJECT-TYPE
enterprises

How to Use in IPNetwork Monitor

Example using jetnexusOverallInputBytes OID:

Select a jetNEXUS application delivery controller / load balancer 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 jetnexusOverallInputBytes into the Find box to locate it in the OID tree, then select it and click OK. It reports from jetnexus shared memory. 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 Counter64-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

OID symbolic	OID numeric	Type	Access	Description
jetnexusMIB	1.3.6.1.4.1.38370			TODO
jetnexusData	1.3.6.1.4.1.38370.1
jetnexusGlobal	1.3.6.1.4.1.38370.1.1
C64 jetnexusOverallInputBytesEx	1.3.6.1.4.1.38370.1.1.1	Counter64	read-only	from jetnexus shared memory
C64 jetnexusOverallOutputBytes	1.3.6.1.4.1.38370.1.1.2	Counter64	read-only	from jetnexus shared memory
C64 jetnexusCompressedInputBytes	1.3.6.1.4.1.38370.1.1.3	Counter64	read-only	from jetnexus shared memory
C64 jetnexusCompressedOutputBytes	1.3.6.1.4.1.38370.1.1.4	Counter64	read-only	from jetnexus shared memory
OCT jetnexusVersionInfo	1.3.6.1.4.1.38370.1.1.5	OCTET STRING	read-only	from jetnexus shared memory
C64 jetnexusTotalClientConnections	1.3.6.1.4.1.38370.1.1.6	Counter64	read-only	from jetnexus shared memory
I32 jetnexusCpuPercent	1.3.6.1.4.1.38370.1.1.7	Integer32	read-only	from jetnexus shared memory
I32 jetnexusDiskFreePercent	1.3.6.1.4.1.38370.1.1.8	Integer32	read-only	from jetnexus shared memory
I32 jetnexusMemoryPercent	1.3.6.1.4.1.38370.1.1.9	Integer32	read-only	from jetnexus shared memory
I32 jetnexusCurrentConnections	1.3.6.1.4.1.38370.1.1.10	Integer32	read-only	from jetnexus shared memory
jnvirtualserviceTable	1.3.6.1.4.1.38370.1.2		not-accessible	Virtual Service info from Shared memory
jnvirtualserviceEntry	1.3.6.1.4.1.38370.1.2.1		not-accessible	Virtual Service data
I32 jnvirtualserviceIndexVirtualService	1.3.6.1.4.1.38370.1.2.1.1	Integer32	not-accessible	Virtual Service data
OCT jnvirtualserviceVSAddrPort	1.3.6.1.4.1.38370.1.2.1.2	OCTET STRING	read-only	Virtual Service data
C64 jnvirtualserviceOverallInputBytes	1.3.6.1.4.1.38370.1.2.1.3	Counter64	read-only	Virtual Service data
C64 jnvirtualserviceOverallOutputBytes	1.3.6.1.4.1.38370.1.2.1.4	Counter64	read-only	Virtual Service data
C64 jnvirtualserviceCacheBytes	1.3.6.1.4.1.38370.1.2.1.5	Counter64	read-only	Virtual Service data
I32 jnvirtualserviceCompressionPercent	1.3.6.1.4.1.38370.1.2.1.6	Integer32	read-only	Virtual Service data
I32 jnvirtualservicePresentClientConnections	1.3.6.1.4.1.38370.1.2.1.7	Integer32	read-only	Virtual Service data
C64 jnvirtualserviceHitCount	1.3.6.1.4.1.38370.1.2.1.8	Counter64	read-only	Virtual Service data
C64 jnvirtualserviceCacheHits	1.3.6.1.4.1.38370.1.2.1.9	Counter64	read-only	Virtual Service data
I32 jnvirtualserviceCacheHitsPercent	1.3.6.1.4.1.38370.1.2.1.10	Integer32	read-only	Virtual Service data
OCT jnvirtualserviceVSStatus	1.3.6.1.4.1.38370.1.2.1.11	OCTET STRING	read-only	Virtual Service data
jnrealserverTable	1.3.6.1.4.1.38370.1.3		not-accessible	Real server data
jnrealserverEntry	1.3.6.1.4.1.38370.1.3.1		not-accessible	Real server data
I32 jnrealserverIndexVirtualService	1.3.6.1.4.1.38370.1.3.1.1	Integer32	not-accessible	Real server data
I32 jnrealserverIndexRealServer	1.3.6.1.4.1.38370.1.3.1.2	Integer32	not-accessible	Real server data
OCT jnrealserverVSAddrPort	1.3.6.1.4.1.38370.1.3.1.3	OCTET STRING	read-only	Real server data
OCT jnrealserverRSAddrPort	1.3.6.1.4.1.38370.1.3.1.4	OCTET STRING	read-only	Real server data
C64 jnrealserverOverallInputBytes	1.3.6.1.4.1.38370.1.3.1.5	Counter64	read-only	Real server data
C64 jnrealserverOverallOutputBytes	1.3.6.1.4.1.38370.1.3.1.6	Counter64	read-only	Real server data
I32 jnrealserverCompressionPercent	1.3.6.1.4.1.38370.1.3.1.7	Integer32	read-only	Real server data
I32 jnrealserverPresentClientConnections	1.3.6.1.4.1.38370.1.3.1.8	Integer32	read-only	Real server data
I32 jnrealserverPoolUsage	1.3.6.1.4.1.38370.1.3.1.9	Integer32	read-only	Real server data
C64 jnrealserverHitCount	1.3.6.1.4.1.38370.1.3.1.10	Counter64	read-only	Real server data
OCT jnrealserverRSStatus	1.3.6.1.4.1.38370.1.3.1.11	OCTET STRING	read-only	Real server data
jetnexusConformance	1.3.6.1.4.1.38370.2
jetnexusGroups	1.3.6.1.4.1.38370.2.1
jetnexusCurrentGroup	1.3.6.1.4.1.38370.2.1.1			The objects relating to the MIB module registered by jetNEXUS.
jetnexusCompliances	1.3.6.1.4.1.38370.2.2
jetnexusBasicCompliance	1.3.6.1.4.1.38370.2.2.1			jetNEXUS MODULE-COMPLIANCE.

RFC description

JetNEXUS (Edgenexus) vendor-specific MIB for load balancer management; defines objects for monitoring CPU, memory, disk, and throughput metrics.

Start monitoring jetNEXUS application delivery controller / load balancer appliance 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 JETNEXUS-MIB