ActiveXperts Network Monitor 2019##AdminFavorites

CISCO-CLUSTER-MIB.mib object view, vendor Cisco

Introduction

Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2019 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers). This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.

ActiveXperts Network Monitor 2019 can import MIB file CISCO-CLUSTER-MIB and use it to monitor vendor specific OID's.

CISCO-CLUSTER-MIB file content

Object view of CISCO-CLUSTER-MIB:

Scalar Object
ccStatusClusterName .1.3.6.1.4.1.9.9.134.1.1.1
The name of the cluster. Cluster command switch functionality is only enabled if this object is a non-NULL string. Strings containing all blanks or a NULL string will disable the cluster. This object and ccStatusClusterMode in this MIB are the only objects that will be instantiated if the command switch functionality is not enabled.
ccStatusClusterMode .1.3.6.1.4.1.9.9.134.1.1.2
The mode of the device. A device can become a member switch only when it is added to the cluster at the command switch. For devices that do not belong to any cluster, the ccStatusClusterMode is set to 'none'.
ccStatusCommanderTDomain .1.3.6.1.4.1.9.9.134.1.1.3
Indicates the kind of transport service used by the command switch of the cluster. Possible values for this object, such as snmpUDPDomain, are defined in the Transport Mappings for SNMPv2 document (RFC 1906).
ccStatusCommanderTAddress .1.3.6.1.4.1.9.9.134.1.1.4
The transport service address of the command switch of the cluster. The address is formatted according to the corresponding value of ccStatusCommanderTDomain. For snmpUDPDomain, a TAddress is 6 octets long, the initial 4 octets containing the IP-address in network-byte order and the last 2 containing the UDP port in network-byte order. Consult 'Transport Mappings for Version 2 of the Simple Network Management Protocol' (RFC 1906) for further information on snmpUDPDomain.
ccStatusCommanderMacAddress .1.3.6.1.4.1.9.9.134.1.1.5
The management MAC address of the command switch of the cluster.
ccStatusTimeOfLastChange .1.3.6.1.4.1.9.9.134.1.1.6
The value of sysUpTime on the command switch when the last time the value of an instance of ccMemberOperStatus changed. The value 0 indicates that no member's status has ever changed since commander system initialization.
ccStatusLastNMSAddMemberTDomain .1.3.6.1.4.1.9.9.134.1.1.7
Indicates the kind of transport service used by the the last NMS tried to add a member to the cluster.
ccStatusLastNMSAddMemberTAddress .1.3.6.1.4.1.9.9.134.1.1.8
The transport service address of the last NMS which tried to add a member to the cluster. The address is formatted according to the corresponding value of ccStatusLastNMSAddMemberTDomain.
ccStatusLastFailureAddMember .1.3.6.1.4.1.9.9.134.1.1.9
The reason why the last NMS was unable to add a switch to be a member of the cluster. password: The member has an enable password configured. overmax: Adding the member exceeds the maximum number of cluster members supported by the command switch. See ccStatusMaxNumberOfMembers. noncandidate: The member is not a candidate switch, or it does not show up in the candidate table. memberNumberInUse: The member number is used by an existing member in the cluster. unreachable: The member is a candidate but is unreachable or has no connectivity.
ccStatusMaxNumberOfMembers .1.3.6.1.4.1.9.9.134.1.1.10
The maximum number of cluster members allowed in the cluster. The command switch is considered as a cluster member also.
ccStatusMemberOrder .1.3.6.1.4.1.9.9.134.1.1.11
The suggested order in which the cluster members are displayed in network management applications. The format of the string is n1,n2,n3,n4, ..., where <n#> is any valid member number in the cluster. The member numbers are separated by commas with no spaces in between. An example of the object's value is '3,8,14,0,2' for a cluster containing member numbers 0, 2, 3, 8, and 14.
ccMemberEntry .1.3.6.1.4.1.9.9.134.1.2.1.1
An entry containing cluster management information applicable to a particular cluster member.
ccCandidateEntry .1.3.6.1.4.1.9.9.134.1.3.1.1
An entry pertaining to a single candidate device.
Tabular Object
ccMemberMacAddress .1.3.6.1.4.1.9.9.134.1.2.1.1.1
The management MAC address of the member device.
ccMemberNumber .1.3.6.1.4.1.9.9.134.1.2.1.1.2
An arbitrary value which uniquely identifies the cluster member switch number. It ranges from 1 to ccStatusMaxNumberOfMembers.
ccMemberOperStatus .1.3.6.1.4.1.9.9.134.1.2.1.1.3
The status of cluster management connectivity between the command switch and a cluster member. Cluster management connectivity is determined by the exchange of cluster management messages between the command switch and a cluster member. A member that has failed to exchange cluster management messages with the command switch is deemed to be inactive. Otherwise, it is deemed to be active.
ccMemberEntityLogicalIndex .1.3.6.1.4.1.9.9.134.1.2.1.1.4
The value of entLogicalIndex in the ENTITY-MIB corresponding to this cluster member. Creating an entry in this table creates a corresponding entry in the entLogicalTable in the ENTITY-MIB.
ccMemberRowStatus .1.3.6.1.4.1.9.9.134.1.2.1.1.5
The status of this conceptual row. A device is added to the cluster of a command switch by creating an entry in this table for the device. The devices currently eligible to be added into the cluster are listed in the ccCandidateTable. An attempt to add a new member may fail. See ccStatusLastFailureAddMember for possible reasons for that failure.
ccCandidateMacAddress .1.3.6.1.4.1.9.9.134.1.3.1.1.1
The MAC address of a device qualified to to be a cluster member of the command switch cluster.
Table
ccMemberTable .1.3.6.1.4.1.9.9.134.1.2.1
This table contains one row per cluster member, including the command switch.
ccCandidateTable .1.3.6.1.4.1.9.9.134.1.3.1
This table contains one row per cluster candidate, A cluster candidate is a device that is currently eligible to be added to the cluster of a command switch. A device is eligible if it satisfies the following conditions: 1. It supports the cluster management protocol. 2. It is directly connected to an existing cluster member. The entries in this table and the entries in ccMemberTable are mutually exclusive at all times. That is, any device that is a cluster member never shows up in the ccCandidateTable or is never a candidate at the same time . Also, any candidate that shows up in ccCandidateTable should not appear in ccMemberTable.
Trap
ccStatusMemberStatusChange .1.3.6.1.4.1.9.9.134.2.0.1
A cluster member status change notification is generated whenever the value of any instance of ccClusterMemberOperStatus changes after the member is completely added to the cluster.
Object Identifier
ciscoClusterMIB .1.3.6.1.4.1.9.9.134
The MIB module for the management of a group of devices called a 'cluster'. A cluster comprises: 1. A command switch, which is a device that can provide a single point of management (including SNMP, Web Console and CLI/Telnet Console) for the devices in the cluster; 2. Zero or more expansion switches, or called the cluster members throughout the context of this MIB, which are devices that can be managed via a command switch. The command switch is also considered as a cluster member. Thus it has an entry in the MIB tables defined below for cluster members. Only the command switch IP address, passwords, and SNMP community strings need to be configured in order to provide management access to members of the cluster. The Entity MIB is cross-referenced from this MIB for some of its table entries, which contain useful information about a cluster. For example, in the Entity MIB, there is the logical table which contains the community string. This information is used to access detailed management information for some logical entity (the cluster, in this case). To determine if a particular device can be a command switch or a member switch please refer to the device's user's guide.
ciscoClusterMIBObjects .1.3.6.1.4.1.9.9.134.1
ccStatus .1.3.6.1.4.1.9.9.134.1.1
ccMember .1.3.6.1.4.1.9.9.134.1.2
ccCandidate .1.3.6.1.4.1.9.9.134.1.3
ciscoClusterMIBNotificationsPrefix .1.3.6.1.4.1.9.9.134.2
ciscoClusterMIBNotifications .1.3.6.1.4.1.9.9.134.2.0
ciscoClusterMIBConformance .1.3.6.1.4.1.9.9.134.3
ciscoClusterMIBCompliances .1.3.6.1.4.1.9.9.134.3.1
ciscoClusterMIBGroups .1.3.6.1.4.1.9.9.134.3.2
Group
ciscoClusterStatusGroup .1.3.6.1.4.1.9.9.134.3.2.1
The collection of objects which are used to represent the status of the cluster. These objects are accessible on the command switch.
ciscoClusterMemberStatusGroup .1.3.6.1.4.1.9.9.134.3.2.2
The collection of objects which are used to represent the status of the cluster. These objects are accessible on the cluster members and the command switch.
ciscoClusterMemberGroup .1.3.6.1.4.1.9.9.134.3.2.3
The collection of objects which are used to represent the members of a cluster. These objects are accessible on the command switch only.
ciscoClusterCandidateGroup .1.3.6.1.4.1.9.9.134.3.2.4
The collection of objects which are used to represent cluster candidates. These objects are accessible on the command switch only.