All MIBs › APERTUS-UA-FALLBACK-MIB
Category: Device Management
Description: Apertus Technologies universal access fallback policy configuration for redundancy management.
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 APERTUS-UA-FALLBACK-MIB?
APERTUS-UA-FALLBACK-MIB is Apertus Technologies' proprietary MIB governing fallback/redundancy policy for its Universal Access (UA) remote-access server line, per its stated purpose of tracking the "status of Universal Access server." It is meant to expose configuration and state related to failover behavior between a primary UA server and a backup, so a management station can tell which unit is currently active. Its hardware/software status role is centered on overall server operational status and fallback trigger state, i.e., whether the device has failed over to a standby role. The sample objects available in the source are only the generic SMI tree roots (internet, private, enterprises, etc.) rather than any fallback-specific object, so the MIB clearly sits within the standard SNMP enterprise OID hierarchy but no concrete fallback objects can be confirmed from source. It was deployed in legacy Apertus UA remote-access server installations requiring redundant server pairs. Engineers can download the APERTUS-UA-FALLBACK-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in APERTUS-UA-FALLBACK-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
- Apertus Technologies Universal Access remote-access server
Monitoring Examples
The sample objects available for this module are only standard SMI tree roots (internet, private, enterprises) rather than real fallback-policy objects, so no concrete monitoring scenario with genuine object names can be constructed honestly; based on the module description, the intended use would be polling a server status object to determine whether the unit is operating as primary or has fallen back to standby.
What Can Be Monitored
- universal access server operational status
- primary/fallback server state
Imported Objects
From RFC1213-MIB
| mib-2 |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| OBJECT-GROUP |
From SNMPv2-SMI
| Counter32 | |
| Gauge32 | |
| IpAddress | |
| MODULE-IDENTITY | |
| OBJECT-IDENTITY | |
| OBJECT-TYPE | |
| TimeTicks |
From SNMPv2-TC
| DisplayString | |
| RowStatus | |
| TEXTUAL-CONVENTION | |
| TruthValue |
OIDs
RFC description
SNMP MIB module providing fallback management capabilities for APERTUS network devices, enabling secondary connection or operation modes when primary systems become unavailable.
Start monitoring Apertus Technologies Universal Access server (legacy) 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.