BROCADE-MCT-CLUSTER-MIB :: brcdMctClusterClientDeployFailureReason

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › BROCADE-MCT-CLUSTER-MIB › brcdMctClusterClientDeployFailureReason

brcdMctClusterClientDeployFailureReason

Module: BROCADE-MCT-CLUSTER-MIB

OID (symbolic): BROCADE-MCT-CLUSTER-MIB::brcdMctClusterClientDeployFailureReason

OID (numeric): 1.3.6.1.4.1.1991.1.1.12.1.1.5.1.6

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: The failure reason for the last cluster client deploy operation through SNMP. The following failure reasons are supported: none(1) - The last deploy is successful. unknown(2) - The last deploy is failed for unknown reason. rBridgeIdNotConfigured(3) - Remote bridge is not configured. clientInterfaceNotConfigured(4) - Client interface is not configured. rBridgeIdUsedInClusterOrPeer(5) - Remote bridge id is used in cluster or peer configuration. clientInterfaceNotPresent(6) - Client interface is physically not present clientInterfaceIsMrpRingInterface(7) - Client interface is configured as MRP ring interface. clientInterfaceIsErpInterface(8) - Client interface is configured as ERP interface. iclIsNotInMemberVlan(9) - ICL is not in member VLAN.

What is brcdMctClusterClientDeployFailureReason?

Reports the reason the most recent SNMP-initiated MCT cluster client deploy operation failed, such as resource exhaustion or a configuration conflict. Returns 'none' when the last deploy operation succeeded.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1991.1.1.12.1.1.5.1.6
snmpwalk -v2c -c public <target> BROCADE-MCT-CLUSTER-MIB::brcdMctClusterClientDeployFailureReason

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.1991.1.1.12.1.1.5.1.6.1
snmpget -v2c -c public <target> BROCADE-MCT-CLUSTER-MIB::brcdMctClusterClientDeployFailureReason.1

Start monitoring Brocade NetIron XMR/MLX CES/CER chassis routers and switches with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the BROCADE-MCT-CLUSTER-MIB::brcdMctClusterClientDeployFailureReason OID value, configure state conditions and alerts, and monitor any Brocade NetIron XMR/MLX CES/CER chassis routers and switches from a single console.

OID Breakdown

Upper-level ancestors (10 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.1991foundryFOUNDRY-SN-ROOT-MIB
1.3.6.1.4.1.1991.1productsFOUNDRY-SN-ROOT-MIB
1.3.6.1.4.1.1991.1.1switchFOUNDRY-SN-ROOT-MIB
1.3.6.1.4.1.1991.1.1.12brcdMctFOUNDRY-SN-ROOT-MIB
Numeric OIDNameModule
1.3.6.1.4.1.1991.1.1.12.1brcdMctMIBBROCADE-MCT-CLUSTER-MIB
1.3.6.1.4.1.1991.1.1.12.1.1brcdMctObjectsBROCADE-MCT-CLUSTER-MIB
1.3.6.1.4.1.1991.1.1.12.1.1.5brcdMctClusterClientTableBROCADE-MCT-CLUSTER-MIB
1.3.6.1.4.1.1991.1.1.12.1.1.5.1brcdMctClusterClientEntryBROCADE-MCT-CLUSTER-MIB
1.3.6.1.4.1.1991.1.1.12.1.1.5.1.6brcdMctClusterClientDeployFailureReasonBROCADE-MCT-CLUSTER-MIB