Home/Catalog/UBQS-REDUNDANCY-MIB

UBQS-REDUNDANCY-MIB

AI MIB Summary

The UBQS-REDUNDANCY-MIB monitors and configures redundancy appliance states, failover mechanisms, and cluster synchronization parameters for Ubiquiti Networks (UB) hardware. It provides visibility into high-availability status, link health, and redundancy protocol operations to ensure continuous network service during component failures.

The UBQS-REDUNDANCY-MIB is used to monitor and configure the redundancy appliances.
Main OID:
ubiRedundancyMIB.1.3.6.1.4.1.7800.100.29
58
Objects
Active
Status
5
Dependencies

Imported Objects

Objects

58 total
Object Name
ubiRedundancyMIBThe UBQS-REDUNDANCY-MIB is used to monitor and configure the redundancy appliances.
MODULE-IDENTITY
.1.3.6.1.4.1.7800.100.29
ubiRedundancyMIBNotificationPrefix
OBJECT IDENTIFIER
.1.3.6.1.4.1.7800.100.29.0
ubiSwitchOverNotificationThe agent generates this trap when a switchover occurs.
NOTIFICATION-TYPE
.1.3.6.1.4.1.7800.100.29.0.1
ubiRedundancyConnectionStateNotificationThe agent generates this trap when the connection state of standby appliance device is changed.
NOTIFICATION-TYPE
.1.3.6.1.4.1.7800.100.29.0.2
ubiRedundancySyncNotificationThe agent generates this trap when the synchronization process with standby SCU is done. This notification occurs after standby is connected.
NOTIFICATION-TYPE
.1.3.6.1.4.1.7800.100.29.0.3
ubiRedundancySyncStateChangeNotificationThe agent generates this trap when the synchronization state has been changed.
NOTIFICATION-TYPE
.1.3.6.1.4.1.7800.100.29.0.4
ubiRedundancyObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.7800.100.29.1
ubiRedundancy
OBJECT IDENTIFIER
.1.3.6.1.4.1.7800.100.29.1.1
ubiRedundancyReloadReload Active/Standby or Peer device.rw
Enumeration
.1.3.6.1.4.1.7800.100.29.1.1.1
ubiRedundancyMyRedundancyStateThe HA redundancy state of this appliance device.ro
RedundancyState
.1.3.6.1.4.1.7800.100.29.1.1.2
ubiRedundancyTableThis table keeps the current configuration of the redundancy information of the active and standby units.
SEQUENCE OF UbiRedundancyEntry
.1.3.6.1.4.1.7800.100.29.1.1.3
ubiRedundancyEntryAn entry containing redundancy information of the active and standby units
UbiRedundancyEntry
.1.3.6.1.4.1.7800.100.29.1.1.3.1
ubiRedundancyIsActivePreferredThis status indicates whether this appliance device is preferred to active or not. Commonly upper(or left) device has this value as True(1) and low(or right) device has this value as False(0).
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.7800.100.29.1.1.3.1.1
ubiRedundancyStateThe HA redundancy state of the appliance device. Role states for redundancy. Valid values are : notConfigured (1) The appliance is not configured for redundancy. active (2) The appliance is the active appliance. standby (3) The appliance is warm standby mode activeLostStandby (4) The active appliance is not getting any response from the standby appliance.ro
RedundancyState
.1.3.6.1.4.1.7800.100.29.1.1.3.1.2
ubiRedundancyConnectionStateThe HA redundancy connection state of standby appliance device.ro
Enumeration
.1.3.6.1.4.1.7800.100.29.1.1.3.1.3
ubiRedundancyConnStateNotificationEnabledEnable or disable redundancy connection state notification via SNMP.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.7800.100.29.1.1.4
ubiRedundancySyncTableThis table keeps the information of the redundancy sync state of the active and standby units.
SEQUENCE OF UbiRedundancySyncEntry
.1.3.6.1.4.1.7800.100.29.1.1.5
ubiRedundancySyncEntryAn entry containing redundancy sync information of the active and standby units
UbiRedundancySyncEntry
.1.3.6.1.4.1.7800.100.29.1.1.5.1
ubiRedundancySyncStateThe redundancy sync state of active appliance device for standby. This sync state is related with 'redundancy-check' function. ACTIVE periodically checks sync state with STANDBY using this function. Valid values are : sync (1) synchronized with standby. notSync (2) some mismatch occurs with standby.ro
Enumeration
.1.3.6.1.4.1.7800.100.29.1.1.5.1.1
ubiRedundancySyncNotificationEnabledEnable or disable redundancy sync notification via SNMP.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.7800.100.29.1.1.5.1.2
ubiRedundancySyncStateChangeNotificationEnabledEnable or disable redundancy sync state change notification via SNMP.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.7800.100.29.1.1.5.1.3
ubiRedundancyAddrTableThis table keeps the current configuration of the address information of the active and standby appliances. There is an entry in this table corresponding to each network interface that is configured for redundancy. Thus, the number of entries in this table corresponds to the number of interfaces configured for redundancy.
SEQUENCE OF UbiRedundancyAddrEntry
.1.3.6.1.4.1.7800.100.29.1.2
ubiRedundancyAddrEntryAn entry containing address information for redundancy configuration on a network interface.
UbiRedundancyAddrEntry
.1.3.6.1.4.1.7800.100.29.1.2.1
ubiRedundancyAddrIfIndexThe index value which uniquely identifies the interface to which this entry is applicable.ro
InterfaceIndex (IF-MIB)
.1.3.6.1.4.1.7800.100.29.1.2.1.1
ubiRedundancyAddrMyAddressTypeThe type of address stored in ubiMyAddressType.ro
InetAddressType (INET-ADDRESS-MIB)
.1.3.6.1.4.1.7800.100.29.1.2.1.2
ubiRedundancyAddrMyAddressThe IP address of the interface configured for this HA configuration in this appliance. The type of this mib variable is defined in ubiMyAddressType.ro
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.4.1.7800.100.29.1.2.1.3
ubiRedundancyAddrPeerAddressTypeThe type of address stored in ubiPeerAddressTypero
InetAddressType (INET-ADDRESS-MIB)
.1.3.6.1.4.1.7800.100.29.1.2.1.4
ubiRedundancyAddrPeerAddressThe IP address of the interface configured for this HA configuration in the peer appliance. The type of this mib variable is defined in ubiPeerAddressType.ro
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.4.1.7800.100.29.1.2.1.5
ubiRedundancyPeerObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.7800.100.29.2
ubiPeerSysInfo
OBJECT IDENTIFIER
.1.3.6.1.4.1.7800.100.29.2.1
ubiPeerSWVersionSoftware version of the peer HA systemro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.7800.100.29.2.1.1
ubiPeerSerialNumberSerial Number of the peer HA systemro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.7800.100.29.2.1.2
ubiPeerPhysicalAddressPeer's physical address.ro
PhysAddress (SNMPv2-TC)
.1.3.6.1.4.1.7800.100.29.2.1.3
ubiPeerResource
OBJECT IDENTIFIER
.1.3.6.1.4.1.7800.100.29.2.2
ubiPeerCpuFiveSecCPU busy percentage in the last 5 second period.
Counter32 UNITS "%"
.1.3.6.1.4.1.7800.100.29.2.2.1
ubiPeerCpuOneMinCPU busy percentage in the last 1 minute period.ro
Counter32 UNITS "%"
.1.3.6.1.4.1.7800.100.29.2.2.2
ubiPeerCpuFiveMinCPU busy percentage in the last 5 minute period.ro
Counter32 UNITS "%"
.1.3.6.1.4.1.7800.100.29.2.2.3
ubiPeerMemoryAllocMemory allocation usage.
Counter32 UNITS "kbyte"
.1.3.6.1.4.1.7800.100.29.2.2.4
ubiPeerMemoryFreeMemory free usage.ro
Counter32 UNITS "kbyte"
.1.3.6.1.4.1.7800.100.29.2.2.5
ubiPeerMemoryTotalCPU busy percentage in the last 5 minute period.ro
Counter32 UNITS "kbyte"
.1.3.6.1.4.1.7800.100.29.2.2.6
ubiPeerMemoryFreePercentageIt indicates available memory allocation space in percentage.ro
Counter32 UNITS "%"
.1.3.6.1.4.1.7800.100.29.2.2.7
ubiPeerEnvironment
OBJECT IDENTIFIER
.1.3.6.1.4.1.7800.100.29.2.3
ubiPeerTemperaturepeer's current temperature.ro
Gauge32 UNITS "'C"
.1.3.6.1.4.1.7800.100.29.2.3.1
ubiPeerBootInfo
OBJECT IDENTIFIER
.1.3.6.1.4.1.7800.100.29.2.4
ubiPeerNextBootImageBooting OS Image's name for peer unit when setting this object, It should be specified the file name with path under /flash directory and Peer's next booting mode will be Flash booting. Valid paths under /flash directory are : - os1/ - os2/ e.g) os1/BootImageName.Zrw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.7800.100.29.2.4.1
ubiPeerImageModify
OBJECT IDENTIFIER
.1.3.6.1.4.1.7800.100.29.2.4.2
ubiPeerImagePathwarning : It operates for only Active unit, not Standby Unit. Path of the file that you want to copy or erase. Represents 'copy (os1:|os2:) peer <FILENAME>' or 'erase (os1:|os2:) peer <FILENAME>' CLIs. for copy operation, path of Active unit and for erase operation, path of Standby unit.rw
Enumeration
.1.3.6.1.4.1.7800.100.29.2.4.2.1
ubiPeerImageFileNamewarning : It operates for only Active unit, not Standby Unit. Name of the file that you want to copy or erase. for copy operation, file name at Active unit and for erase operation, file anme at Standby unit.rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.7800.100.29.2.4.2.2
ubiPeerImageModifyOperateexecute to copy or erase configurations.rw
Enumeration
.1.3.6.1.4.1.7800.100.29.2.4.2.3
ubiSwitchoverObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.7800.100.29.3
ubiSwitchover
OBJECT IDENTIFIER
.1.3.6.1.4.1.7800.100.29.3.1
ubiLastSwitchOverReasonReason for the most recent switchover. Valid values are : nont (0) none of the following lossConnWithActive (1) lost connection with active forcedSwitchOver (2) Switchover occurs by force unknown (3) Switchover occurs by unknown reasonro
SwitchOverReason
.1.3.6.1.4.1.7800.100.29.3.1.1
ubiLastSwitchOverTimeThe local date and time when the last switchover event occurred and was logged to the system.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.7800.100.29.3.1.2
ubiSwitchoverNotificationEnabledEnable or disable switchover notification via SNMP.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.7800.100.29.3.1.3
ubiSwitchOverRedundancySyncStateThe HA redundancy sync state of the appliance device after switchover. Valid values are : sync (1) SCU synchronization is done . notSync (2) SCU synchronization is fail or still in progress.ro
Enumeration
.1.3.6.1.4.1.7800.100.29.3.1.4
ubiRedundancyMIBConformance
OBJECT IDENTIFIER
.1.3.6.1.4.1.7800.100.29.4
ubiRedundancyMIBCompliance
OBJECT IDENTIFIER
.1.3.6.1.4.1.7800.100.29.4.1
ubiRedundancyMIBGroups
OBJECT IDENTIFIER
.1.3.6.1.4.1.7800.100.29.4.2
UBQS-REDUNDANCY-MIB - SNMP MIB Reference | MIBs Explorer