BROCADE-MCT-CLUSTER-MIB :: brcdMctClusterPeerDownReason

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

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

brcdMctClusterPeerDownReason

Module: BROCADE-MCT-CLUSTER-MIB

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

OID (numeric): 1.3.6.1.4.1.1991.1.1.12.1.1.4.1.10

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: The reason for the brcdMctClusterPeerOperStatus is in ccpDown(3) state. The following values are supported as down reason: none(1) - Peer is not in down state loopbackInterfaceDown(2) - Loopback interface down iclInterfaceDown(3) - ICL interface down upgradeInProgress(4) - All local client interfaces disabled routeNotAvailable(5) - Route to cluster Peer is not available iclVeDown(6) - ICL VE interface down rBridgeIdMismatch(7) - RBridge ID does not match with Peer clusterIdMismatch(8) - Cluster ID does not match with Peer keepAliveTimeMismatch(9) - KeepAlive Time does not match with Peer holdTimeMismatch(10) - Hold Time does not match with Peer fastFailoverMismatch(11) - Fast Failover parameter does not match with Peer shutdownMesgFromPeer(12) - ShutDown message came from Peer tcpKeepAliveTimeout(13) - TCP keepalive timeout message came tcpConnCloseMesg(14) - TCP connection close message came holdTimeoutExpired(15) - Hold timeout expired sendStateTimeoutExpired(16) - Send State timeout expired recvStateTimeoutExpired(17) - Recieve State timeout expired initMesgSendFail(18) - Unable to send the Init message keepAliveMesgSendFail(19) - Unable to send the Keepalive message invalidAppMesgRecv(20) - Invalid Application packet received message came from peer badProtocolVersionPktRecv(21) - Bad Protocol version packet received message came from peer badPduLengthPktRecv(22) - Bad PDU length packet received message came from peer unknownCcpPktRecv(23) - Unknown CCP message type packet received message came from peer invalidCcpPktRecv(24) - Invalid CCP message length packet received message came from peer internalCcpErrorRecv(25) - Internal CCP error message came from peer ccpTcpCommFail(26) - Cluster CCP TCP communication failed

What is brcdMctClusterPeerDownReason?

Identifies why an MCT cluster peer's CCP (Cluster Control Protocol) session transitioned to the ccpDown state, such as a loopback interface failure or ICL (Inter-Chassis Link) going down. Returns 'none' when the peer is not currently in a down state.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1991.1.1.12.1.1.4.1.10
snmpwalk -v2c -c public <target> BROCADE-MCT-CLUSTER-MIB::brcdMctClusterPeerDownReason

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.1991.1.1.12.1.1.4.1.10.1
snmpget -v2c -c public <target> BROCADE-MCT-CLUSTER-MIB::brcdMctClusterPeerDownReason.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::brcdMctClusterPeerDownReason 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.4brcdMctClusterPeerTableBROCADE-MCT-CLUSTER-MIB
1.3.6.1.4.1.1991.1.1.12.1.1.4.1brcdMctClusterPeerEntryBROCADE-MCT-CLUSTER-MIB
1.3.6.1.4.1.1991.1.1.12.1.1.4.1.10brcdMctClusterPeerDownReasonBROCADE-MCT-CLUSTER-MIB