COMPAT-MIB

All MIBs › COMPAT-MIB

Category: Device Management

Description: Compatibility MIB providing legacy object mappings and aliases to maintain backward compatibility across different MIB versions.

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

COMPAT-MIB is a legacy compatibility MIB that provides object mappings and aliases so that management stations built against older MIB definitions can continue to resolve objects when the underlying agent has migrated to newer or renamed MIB structures. No module description or sample objects were available in the source, indicating this is a thin structural/aliasing module rather than one exposing substantial runtime data of its own. Its monitoring relevance is indirect: it exists purely to preserve backward-compatible OID resolution during a MIB transition, not to expose hardware or software health data itself. Because its whole purpose is bridging between MIB versions, it is inherently dependent on whichever base MIB(s) it maps aliases onto. It would be deployed on any device or agent implementation undergoing a MIB revision where legacy management tools still need to resolve the old object names. Engineers can download the COMPAT-MIB file directly to load it into their MIB browser.

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

vendor-neutral, standards-based MIB, not tied to a specific manufacturer
generic SNMP-managed device undergoing MIB version migration

Monitoring Examples

No sample objects were provided for this module, and given its stated purpose as an alias/compatibility layer, it likely does not expose independent runtime monitoring data beyond redirecting to objects defined elsewhere; a concrete polling scenario cannot be described from the available information.

Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

Counter
Gauge
IpAddress
TimeTicks
enterprises

OIDs

OID symbolic	OID numeric	Type	Access	Description
compatible	1.3.6.1.4.1.255
compatVars	1.3.6.1.4.1.255.1
GAU processorUtilizationPercentage	1.3.6.1.4.1.255.1.1	Gauge	read-only	The percentage of time the processor is spending not idle.
compatVPN	1.3.6.1.4.1.255.2
vpnLoginTable	1.3.6.1.4.1.255.2.1
CTR failedLogins	1.3.6.1.4.1.255.2.1.1	Counter	read-only	The number of failed logins since boot time.
CTR failedSecurID	1.3.6.1.4.1.255.2.1.2	Counter	read-only	The number of failed Secure ID logins since boot time.
CTR failedRadiusAuth	1.3.6.1.4.1.255.2.1.3	Counter	read-only	The number of failed RADIUS logins since boot time.
vPNTunnelTable	1.3.6.1.4.1.255.2.2.1		not-accessible	This table contains information useful when tracking vpn tunnels currently active for this NAS.
vpnTunnelTableEntry	1.3.6.1.4.1.255.2.2.1.1		not-accessible	The tunnel active table. An entry in this table is uniquely identified by the value of the vpnTunnelTableIndex variable to which the entry refers.
INT vpnTunnelTableIndex	1.3.6.1.4.1.255.2.2.1.1.1	INTEGER	read-only	A unique value, greater than zero, for each tunnel interface.
STR vpnTunnelTableUserName	1.3.6.1.4.1.255.2.2.1.1.2	DisplayString	read-only	The name of the VPN user
STR vpnTunnelTableGroupName	1.3.6.1.4.1.255.2.2.1.1.3	DisplayString	read-only	The name of the VPN group
IP vpnTunnelTableIpAddress	1.3.6.1.4.1.255.2.2.1.1.4	IpAddress	read-only	The VPN partner's IP Address.
IP vpnTunnelTableAssignedIpAddress	1.3.6.1.4.1.255.2.2.1.1.5	IpAddress	read-only	The Client's dynamically assigned IP Address.
CTR vpnTunnelTableIpBytesRcvd	1.3.6.1.4.1.255.2.2.1.1.6	Counter	read-only	The total number of inbound IP bytes handled by this tunnel as counted by the STEP layer.
CTR vpnTunnelTableIpBytesSent	1.3.6.1.4.1.255.2.2.1.1.7	Counter	read-only	The total number of outbound IP bytes handled by this tunnel as counted by the STEP layer.
CTR vpnTunnelTableIpxBytesRcvd	1.3.6.1.4.1.255.2.2.1.1.8	Counter	read-only	The total number of inbound IPX bytes handled by this tunnel as counted by the STEP layer.
CTR vpnTunnelTableIpxBytesSent	1.3.6.1.4.1.255.2.2.1.1.9	Counter	read-only	The total number of outbound IPX bytes handled by this tunnel as counted by the STEP layer.
CTR vpnTunnelTableAppletalkBytesRcvd	1.3.6.1.4.1.255.2.2.1.1.10	Counter	read-only	The total number of inbound Appletalk bytes handled by this tunnel as counted by the STEP layer.
CTR vpnTunnelTableAppletalkBytesSent	1.3.6.1.4.1.255.2.2.1.1.11	Counter	read-only	The total number of outbound Appletalk bytes handled by this tunnel as counted by the STEP layer.
TIK vpnTunnelTableUptime	1.3.6.1.4.1.255.2.2.1.1.12	TimeTicks	read-only	The time since the tunnel was established.
INT vpnTunnelTableLatency	1.3.6.1.4.1.255.2.2.1.1.13	INTEGER	read-only	SLA latency metric.
INT vpnTunnelTableBandwidthOut	1.3.6.1.4.1.255.2.2.1.1.14	INTEGER	read-only	SLA metric for measuring outbound data bandwidth through this tunnel.
INT vpnTunnelTableBandwidthReturn	1.3.6.1.4.1.255.2.2.1.1.15	INTEGER	read-only	SLA metric for measuring inbound data bandwidth through this tunnel.

RFC description

Compatible MIB for VPN login statistics and tunnel management on enterprise gateways.

Start monitoring Vendor-neutral SNMP compatibility/aliasing module 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 COMPAT-MIB

What Is COMPAT-MIB?

Supported Devices

Monitoring Examples

This MIB depends on

Related MIBs

RFC description