BCN-HA-MIB
AI MIB Summary
The BCN-HA-MIB module monitors the operational status and statistical performance metrics of High Availability (HA) services on Brocade (now Broadcom) network devices, specifically tracking failover states, synchronization health, and cluster membership data to ensure redundant path reliability.
This module provides status as well as statistical information about the HA service.
Main OID:
bcnHaMIB.1.3.6.1.4.1.13315.3.1.5.1
28
Objects
Active
Status
6
Dependencies
Imported Objects
Objects
28 total| Object Name |
|---|
bcnHa OBJECT IDENTIFIER .1.3.6.1.4.1.13315.3.1.5 |
bcnHaMIBThis module provides status as well as statistical information about the HA service. MODULE-IDENTITY .1.3.6.1.4.1.13315.3.1.5.1 |
bcnHaObjects OBJECT IDENTIFIER .1.3.6.1.4.1.13315.3.1.5.2 |
bcnHaServiceStatusGeneral state of the HA Service. OBJECT IDENTIFIER .1.3.6.1.4.1.13315.3.1.5.2.1 |
bcnHaSerOperStateOperational state of the Service. The possible states are: standalone(1) The node is not configured to provide clustering services. active(2) The system is operational and the node is providing clustering services. passive(3) The system is operational and the node is active as a passive standby for the cluster. stopped(4) The service is stopped either intentionally (i.e.: the service is not supposed to run on this node) or unintentionally (a problem has occurred). This state might apply to both standalong and clustered nodes. stopping(5) The service is in the process of stopping. Stopping a service might be necessary after a configuration change. becomingActive (6) The node is becoming active, either as a result of a switchover or by initial start. becomingPassive (7) The node is failing over. Another node is taking charge of the services. fault(8) An error has been detected and the state is undefined.ro Enumeration .1.3.6.1.4.1.13315.3.1.5.2.1.1 |
bcnHaSerReplicationStateThe current state of the replication. All nodes in a cluster must be in synch in order for HA to work correctly. The nodes might be temporarily out of synch during cluster creation or when one of the nodes has been down for a while.ro Enumeration .1.3.6.1.4.1.13315.3.1.5.2.1.2 |
bcnHaSerAddressTableThis table keeps the information about the network addresses for the clustered nodes. Most of the time this table will contain one or two rows, depending on the type of IPs configured for clustering. SEQUENCE OF BcnHaSerAddressEntry .1.3.6.1.4.1.13315.3.1.5.2.1.3 |
bcnHaSerAddressEntryA logical row in the bcnHaSerAddressTable. BcnHaSerAddressEntry .1.3.6.1.4.1.13315.3.1.5.2.1.3.1 |
bcnHaSerAddrTableIndexThis index will normally be 0 or 1 Unsigned32 .1.3.6.1.4.1.13315.3.1.5.2.1.3.1.1 |
bcnHaSerVirtualAddressTypeThe type of address stored in bcnHaSerVirtualAddress.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.13315.3.1.5.2.1.3.1.2 |
bcnHaSerVirtualAddressThe virtual IP address configured for this node. The type of this mib variable is defined in bcnHaSerVirtualAddressType. This address binds to the active node at all times.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.13315.3.1.5.2.1.3.1.3 |
bcnHaSerPhysicalAddressTypeThe type of address stored in bcnHaSerPhysicalAddress.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.13315.3.1.5.2.1.3.1.4 |
bcnHaSerPhysicalAddressThe physical IP address configured for this node. The type of this mib variable is defined in bcnHaSerPhisicalAddressType. This address is not affected by switchover events.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.13315.3.1.5.2.1.3.1.5 |
bcnHaSerPeerAddressTypeThe type of address stored in bcnHaSerPeerAddress.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.13315.3.1.5.2.1.3.1.6 |
bcnHaSerPeerAddressThe physical IP address configured for the peer node. The type of this mib variable is defined in bcnHaSerPeerAddressType. This address is not affected by switchover events.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.13315.3.1.5.2.1.3.1.7 |
bcnHaNotification OBJECT IDENTIFIER .1.3.6.1.4.1.13315.3.1.5.3 |
bcnHaNotificationEvents OBJECT IDENTIFIER .1.3.6.1.4.1.13315.3.1.5.3.0 |
bcnHaAlarmNotifA bcnHaAlarmNotif signifies that the HA service has transitioned state or a particular event has been detected on the service. NOTIFICATION-TYPE .1.3.6.1.4.1.13315.3.1.5.3.0.1 |
bcnHaNotificationData OBJECT IDENTIFIER .1.3.6.1.4.1.13315.3.1.5.3.1 |
bcnHaAlarmSeveritySeverity classification for the alarm.ro BcnAlarmSeverity (BCN-TC-MIB) .1.3.6.1.4.1.13315.3.1.5.3.1.1 |
bcnHaAlarmInfoDescriptive information about the alarm event.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.13315.3.1.5.3.1.2 |
bcnHaConformance OBJECT IDENTIFIER .1.3.6.1.4.1.13315.3.1.5.4 |
bcnHaServiceCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.13315.3.1.5.4.1 |
bcnHaStatusComplianceBasic conformance Unknown .1.3.6.1.4.1.13315.3.1.5.4.1.1 |
bcnHaServiceGroups OBJECT IDENTIFIER .1.3.6.1.4.1.13315.3.1.5.4.2 |
bcnHaServiceStatusGroupStatus conformance. Unknown .1.3.6.1.4.1.13315.3.1.5.4.2.1 |
bcnHaNotificationEventGroupServer statistics conformance. Unknown .1.3.6.1.4.1.13315.3.1.5.4.2.2 |
bcnHaNotificationDataGroupServer statistics conformance. Unknown .1.3.6.1.4.1.13315.3.1.5.4.2.3 |