Home/Catalog/CISCO-APPLIANCE-REDUNDANCY-MIB

CISCO-APPLIANCE-REDUNDANCY-MIB

AI MIB Summary

The CISCO-APPLIANCE-REDUNDANCY-MIB monitors High Availability cluster states, active/standby roles, and virtual IP ownership for Cisco network management appliances such as the Wireless LAN Solution Engine (WLSE). It tracks switchover events, heartbeat polling status, and data mirroring synchronization to ensure non-disruptive failover between redundant hardware units.

This mib defines the SNMP objects to report the status of High Availability (HA) functionality in Cisco network management appliance devices. The HA functinality is achieved via the redundancy of network management appliance devices. An network management appliance is a device which combines hardware and software to provide specific network management services. Cisco WLSE, Wireless Service Engine (WLSE) is such an appliance. The High Availability is achieved via redundancy of appliances. This redundancy scheme is designed to support hardware or software failure of the appliances in a non- disruptive manner. Redundancy is achieved by configuring a cluster of two appliances with one common virtual IP address. The data is mirrored from the active appliance to the standby appliance at regular intervals. One of the appliances is in active mode, performing all normal functions. The other appliance is in warm standby mode; that is, the appliance is up but no application services are running. Both the active and standby appliances have their own IP addresses. The active appliance also owns the virtual IP address to which all the service requests are made. The active appliance and standby appliance periodically poll each other. If the standby appliance cannot reach the active appliance, it will become the active appliance. This is called a switchover event. The switchover can be caused by other causes, for example, via user commands. Both the active and standby appliances should implement this MIB and report any exceptions caused by switchover events.
Main OID:
ciscoApplianceRedundancyMIB.1.3.6.1.4.1.9.9.458
36
Objects
Active
Status
6
Dependencies

Imported Objects

Objects

36 total
Object Name
ciscoApplianceRedundancyMIBThis mib defines the SNMP objects to report the status of High Availability (HA) functionality in Cisco network management appliance devices. The HA functinality is achieved via the redundancy of network management appliance devices. An network management appliance is a device which combines hardware and software to provide specific network management services. Cisco WLSE, Wireless Service Engine (WLSE) is such an appliance. The High Availability is achieved via redundancy of appliances. This redundancy scheme is designed to support hardware or software failure of the appliances in a non- disruptive manner. Redundancy is achieved by configuring a cluster of two appliances with one common virtual IP address. The data is mirrored from the active appliance to the standby appliance at regular intervals. One of the appliances is in active mode, performing all normal functions. The other appliance is in warm standby mode; that is, the appliance is up but no application services are running. Both the active and standby appliances have their own IP addresses. The active appliance also owns the virtual IP address to which all the service requests are made. The active appliance and standby appliance periodically poll each other. If the standby appliance cannot reach the active appliance, it will become the active appliance. This is called a switchover event. The switchover can be caused by other causes, for example, via user commands. Both the active and standby appliances should implement this MIB and report any exceptions caused by switchover events.
MODULE-IDENTITY
.1.3.6.1.4.1.9.9.458
ciscoApplRedundancyMIBObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.458.1
carConfigObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.458.1.1
carRedundancySyncIntervalTime interval at which the active and standby appliances are synchronized. Synchronization consists of incrementally backing up the data on the active appliance and restoring on the standby appliance.ro
TimeInterval (SNMPv2-TC)
.1.3.6.1.4.1.9.9.458.1.1.1
carRedundancyCheckIntervalTime interval to check the availability status of each appliance. Both the active and standby appliances will check the status of each other in this time interval. If the standby appliance is not able to connect to the active appliance during this check, it will become the active appliance.ro
TimeInterval (SNMPv2-TC)
.1.3.6.1.4.1.9.9.458.1.1.2
carRedundancyStateThe HA redundancy state of this appliance device.ro
CarRedundancyState
.1.3.6.1.4.1.9.9.458.1.1.3
carNotificationEnabledEnable or disable HA switchover event notifications via SNMP.ro
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.9.9.458.1.1.4
carHAAddressTableThis 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 CarHAAddressEntry
.1.3.6.1.4.1.9.9.458.1.1.5
carHAAddressEntryAn entry containing address information for HA configuration on a network interface.
CarHAAddressEntry
.1.3.6.1.4.1.9.9.458.1.1.5.1
carHAAddrTableIndexThis index matches the interface number for which the Virtual IP configuration is maintained. For example, the Virtual IP configured on interface eth0 will be index 0. Entry for eth1 will be index 1,... and so on.
InterfaceIndexOrZero (IF-MIB)
.1.3.6.1.4.1.9.9.458.1.1.5.1.1
carVirtualAddressTypeThe type of address stored in carVirtualAddress.ro
InetAddressType (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.458.1.1.5.1.2
carVirtualAddressThe virtual IP address configured for this interface. The type of this mib variable is defined in carVirtualAddressType. This address binds to the active appliance at all times. All the management requests should be made to this address.ro
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.458.1.1.5.1.3
carMyAddressTypeThe type of address stored in carMyAddressro
InetAddressType (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.458.1.1.5.1.4
carMyAddressThe IP address of the interface configured for this HA configuration in this appliance. The type of this mib variable is defined in carMyAddressType. Note this value will not be affected by switchover events.ro
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.458.1.1.5.1.5
carPeerAddressTypeThe type of address stored in carPeerAddressro
InetAddressType (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.458.1.1.5.1.6
carPeerAddressThe IP address of the interface configured for this HA configuration in the peer appliance. The type of this mib variable is defined in carPeerAddressType. Note this value will not be affected by switchover events.ro
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.458.1.1.5.1.7
carSwitchOverObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.458.1.2
carLastSwitchOverReasonCause for the most recent switchover.ro
CarSwitchOverReason
.1.3.6.1.4.1.9.9.458.1.2.1
carLastSwitchOverTimeThe local date and time when the last switchover event occurred and was logged to the system.ro
DateAndTime (SNMPv2-TC)
.1.3.6.1.4.1.9.9.458.1.2.2
carTotalSwitchOversThe number of all HA switchover events.ro
Counter32
.1.3.6.1.4.1.9.9.458.1.2.3
carMaxSwitchOverHistoryRecordsThe maximun number of records to keep in carSwitchOverHistoryTable. New records will replace the old records on a first-in-first-out basis. A value of 0 indicates no history will be retained.ro
Unsigned32
.1.3.6.1.4.1.9.9.458.1.2.4
carSwitchOverHistoryTableThis table keeps an history of HA switchover events. The maximum number of records is equal or less than carMaxSwitchOverRecords.
SEQUENCE OF CarSwitchOverHistEntry
.1.3.6.1.4.1.9.9.458.1.2.5
carSwitchOverHistEntryAn entry containing information about a HA switchover event.
CarSwitchOverHistEntry
.1.3.6.1.4.1.9.9.458.1.2.5.1
carSWHistTableIndexAn monotonically increasing number for the sole purpose of indexing entries. When it reaches maximum value, the agent sets it back to 1.
Unsigned32
.1.3.6.1.4.1.9.9.458.1.2.5.1.1
carSWHistActiveNodeAddressTypeRepresents the type of address stored in carSWHistActiveNodeAddress.ro
InetAddressType (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.458.1.2.5.1.2
carSWHistActiveNodeAddressThe address of the active appliance after the switchover event. carSWHistActiveNodeAddressType specifies the type of this mib variable.ro
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.458.1.2.5.1.3
carSWHistStandbyNodeAddressTypeRepresents the type of address stored in carSWHistStandbyNodeAddress.ro
InetAddressType (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.458.1.2.5.1.4
carSWHistStandbyNodeAddressThe address of the standby appliance after the switchover event. carSWHistStandbyNodeAddressType specifies the type of this mib variable.ro
InetAddress (INET-ADDRESS-MIB)
.1.3.6.1.4.1.9.9.458.1.2.5.1.5
carSWHistEventTimeThe local date and time when the switchover event occurred and was logged to the system.ro
DateAndTime (SNMPv2-TC)
.1.3.6.1.4.1.9.9.458.1.2.5.1.6
carSWHistEventReasonCause of the switchover event.ro
CarSwitchOverReason
.1.3.6.1.4.1.9.9.458.1.2.5.1.7
carHAMIBNotifPrefix
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.458.2
carHAMIBNotifications
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.458.2.0
carSwitchOverNotificationThis notification is sent when a switchover event happened. This notification can be enabled or disabled via carNotificationEnabled.
NOTIFICATION-TYPE
.1.3.6.1.4.1.9.9.458.2.0.1
ciscoHAMIBConformance
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.458.3
ciscoHAMIBCompliances
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.458.3.1
ciscoHAMIBGroups
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.458.3.2
CISCO-APPLIANCE-REDUNDANCY-MIB - SNMP MIB Reference | MIBs Explorer