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
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.
Parsed from file CISCO-CLUSTER-MIB.mib
Module: CISCO-CLUSTER-MIB
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
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.
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
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.
Parsed from file cisco-cluster.mib.txt
Company: None
Module: CISCO-CLUSTER-MIB
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
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.
ccStatusMemberOrder OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-write STATUS current DESCRIPTION "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 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." DEFVAL { "" } ::= { ccStatus 11 }
ccStatusMemberOrder OBJECT-TYPE SYNTAX SnmpAdminString ACCESS read-write STATUS mandatory DESCRIPTION "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 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." DEFVAL { "" } ::= { ccStatus 11 }
Vendor: Cisco
Module: CISCO-CLUSTER-MIB
[Automatically extracted from oidview.com]
ccStatusMemberOrder OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-write STATUS current DESCRIPTION "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 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." DEFVAL { "" } ::= { ccStatus 11 }
ccStatusMemberOrder OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-write STATUS current DESCRIPTION "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 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." DEFVAL { "" } ::= { ccStatus 11 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.134.1.1.11.0 | ccStatusMemberOrder | 0 | 0 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.134.1.1.1 | ccStatusClusterName | 1 | 1 | The name of the cluster. Cluster command switch functionality is only enabled if this object is a non-NULL string. Strings cont… |
| 1.3.6.1.4.1.9.9.134.1.1.2 | ccStatusClusterMode | 1 | 1 | 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 dev… |
| 1.3.6.1.4.1.9.9.134.1.1.3 | ccStatusCommanderTDomain | 1 | 1 | Indicates the kind of transport service used by the command switch of the cluster. Possible values for this object, such as snmp… |
| 1.3.6.1.4.1.9.9.134.1.1.4 | ccStatusCommanderTAddress | 1 | 1 | The transport service address of the command switch of the cluster. The address is formatted according to the corresponding valu… |
| 1.3.6.1.4.1.9.9.134.1.1.5 | ccStatusCommanderMacAddress | 1 | 1 | The management MAC address of the command switch of the cluster. |
| 1.3.6.1.4.1.9.9.134.1.1.6 | ccStatusTimeOfLastChange | 1 | 1 | The value of sysUpTime on the command switch when the last time the value of an instance of ccMemberOperStatus changed. The valu… |
| 1.3.6.1.4.1.9.9.134.1.1.7 | ccStatusLastNMSAddMemberTDomain | 1 | 1 | Indicates the kind of transport service used by the the last NMS tried to add a member to the cluster. |
| 1.3.6.1.4.1.9.9.134.1.1.8 | ccStatusLastNMSAddMemberTAddress | 1 | 1 | The transport service address of the last NMS which tried to add a member to the cluster. The address is formatted according to … |
| 1.3.6.1.4.1.9.9.134.1.1.9 | ccStatusLastFailureAddMember | 1 | 1 | 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 passwor… |
| 1.3.6.1.4.1.9.9.134.1.1.10 | ccStatusMaxNumberOfMembers | 1 | 1 | The maximum number of cluster members allowed in the cluster. The command switch is considered as a cluster member also. |