BCN-HA-MIB: View SNMP OID List / Download MIB

VENDOR: BLUECAT NETWORKS


 Home MIB: BCN-HA-MIB
Download as:   
SNMPv2-CONF, SNMPv2-SMI, BCN-SMI-MIB, INET-ADDRESS-MIB, BCN-TC-MIB, SNMPv2-TC

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 bcnHa 1.3.6.1.4.1.13315.3.1.5
     bcnHaMIB 1.3.6.1.4.1.13315.3.1.5.1
This module provides status as well as statistical information about the HA service.
     bcnHaObjects 1.3.6.1.4.1.13315.3.1.5.2
         bcnHaServiceStatus 1.3.6.1.4.1.13315.3.1.5.2.1
General state of the HA Service.
             bcnHaSerOperState 1.3.6.1.4.1.13315.3.1.5.2.1.1 integer read-only
Operational 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. Enumeration: 'standalone': 1, 'fault': 8, 'becomingActive': 6, 'passive': 3, 'stopping': 5, 'stopped': 4, 'becomingPassive': 7, 'active': 2.
             bcnHaSerReplicationState 1.3.6.1.4.1.13315.3.1.5.2.1.2 integer read-only
The 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. Enumeration: 'replicating': 2, 'synchronized': 3, 'notConfigured': 1.
             bcnHaSerAddressTable 1.3.6.1.4.1.13315.3.1.5.2.1.3 no-access
This 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.
                 bcnHaSerAddressEntry 1.3.6.1.4.1.13315.3.1.5.2.1.3.1 no-access
A logical row in the bcnHaSerAddressTable.
                     bcnHaSerAddrTableIndex 1.3.6.1.4.1.13315.3.1.5.2.1.3.1.1 unsigned32 no-access
This index will normally be 0 or 1
                     bcnHaSerVirtualAddressType 1.3.6.1.4.1.13315.3.1.5.2.1.3.1.2 inetaddresstype read-only
The type of address stored in bcnHaSerVirtualAddress.
                     bcnHaSerVirtualAddress 1.3.6.1.4.1.13315.3.1.5.2.1.3.1.3 inetaddress read-only
The 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.
                     bcnHaSerPhysicalAddressType 1.3.6.1.4.1.13315.3.1.5.2.1.3.1.4 inetaddresstype read-only
The type of address stored in bcnHaSerPhysicalAddress.
                     bcnHaSerPhysicalAddress 1.3.6.1.4.1.13315.3.1.5.2.1.3.1.5 inetaddress read-only
The 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.
                     bcnHaSerPeerAddressType 1.3.6.1.4.1.13315.3.1.5.2.1.3.1.6 inetaddresstype read-only
The type of address stored in bcnHaSerPeerAddress.
                     bcnHaSerPeerAddress 1.3.6.1.4.1.13315.3.1.5.2.1.3.1.7 inetaddress read-only
The 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.
     bcnHaNotification 1.3.6.1.4.1.13315.3.1.5.3
         bcnHaNotificationEvents 1.3.6.1.4.1.13315.3.1.5.3.0
             bcnHaAlarmNotif 1.3.6.1.4.1.13315.3.1.5.3.0.1
A bcnHaAlarmNotif signifies that the HA service has transitioned state or a particular event has been detected on the service.
         bcnHaNotificationData 1.3.6.1.4.1.13315.3.1.5.3.1
             bcnHaAlarmSeverity 1.3.6.1.4.1.13315.3.1.5.3.1.1 bcnalarmseverity no-access
Severity classification for the alarm.
             bcnHaAlarmInfo 1.3.6.1.4.1.13315.3.1.5.3.1.2 displaystring no-access
Descriptive information about the alarm event.
     bcnHaConformance 1.3.6.1.4.1.13315.3.1.5.4
         bcnHaServiceCompliances 1.3.6.1.4.1.13315.3.1.5.4.1
             bcnHaStatusCompliance 1.3.6.1.4.1.13315.3.1.5.4.1.1
Basic conformance
         bcnHaServiceGroups 1.3.6.1.4.1.13315.3.1.5.4.2
             bcnHaServiceStatusGroup 1.3.6.1.4.1.13315.3.1.5.4.2.1
Status conformance.
             bcnHaNotificationEventGroup 1.3.6.1.4.1.13315.3.1.5.4.2.2
Server statistics conformance.
             bcnHaNotificationDataGroup 1.3.6.1.4.1.13315.3.1.5.4.2.3
Server statistics conformance.