BROCADE-MCT-CLUSTER-MIB

All MIBs › BROCADE-MCT-CLUSTER-MIB

Organization: Brocade Communications Systems, Inc.

Last Updated: 2012-01-12

Category: VLAN and Bridging, Vendor: Foundry/Brocade

Description: Manages MCT (Multi-Chassis Trunking) cluster configuration and inter-chassis link status on Brocade switches.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is BROCADE-MCT-CLUSTER-MIB?

BROCADE-MCT-CLUSTER-MIB is a Brocade Communications Systems enterprise MIB (supported on NetIron XMR/MLX CES/CER platforms) that models Multi-Chassis Trunking (MCT), Brocade's technology for forming an inter-chassis link-aggregation cluster between two switches so they appear as one logical device to downstream partners. Its brcdMctClusterTable, indexed by brcdMctClusterId, defines cluster identity and VLAN scope (brcdMctClusterName, brcdMctClusterRbridgeId, brcdMctClusterSessionVlan, brcdMctClusterKeepAliveVlan, brcdMctClusterMemberVlans/ActiveMemberVlans) plus deployment/lifecycle control via brcdMctClusterDeploy and brcdMctClusterRowStatus. Companion tables brcdMctClusterIclTable (inter-chassis link), brcdMctClusterPeerTable (peer session state), and brcdMctClusterClientTable (dual-homed client/CE devices) expose the runtime topology of the cluster, while NOTIFICATION-TYPE objects brcdMctClusterPeerStatus and brcdMctClusterClientStatus alert an NMS when a peer or client status changes — critical events since an MCT peer failure can affect traffic forwarding for every dual-homed client. It depends on FOUNDRY-SN-SWITCH-GROUP-MIB and FOUNDRY-SN-ROOT-MIB for VLAN types and OID registration, plus IF-MIB and INET-ADDRESS-MIB for interface/address typing, and is deployed on Brocade NetIron XMR/MLX/CES/CER chassis routers/switches forming MCT clusters. Data-center network teams rely on the BROCADE-MCT-CLUSTER-MIB MIB to confirm cluster and inter-chassis-link health.

IPNetwork Monitor allows you to monitor SNMP objects defined in BROCADE-MCT-CLUSTER-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Brocade NetIron XMR/MLX CES/CER chassis routers and switches

Monitoring Examples

An operator subscribes to brcdMctClusterPeerStatus notifications and polls brcdMctClusterPeerTable to confirm the peer session is up and brcdMctClusterIclTable shows the inter-chassis link active; a brcdMctClusterPeerStatus trap indicating peer down, especially combined with brcdMctClusterClientShutdown set to true, would indicate the cluster has lost its peer and dual-homed clients may be forced into single-homed forwarding.

What Can Be Monitored

MCT cluster identity and VLAN/session configuration
inter-chassis link (ICL) table status
cluster peer session state
dual-homed client table entries
peer/client status change notifications
cluster deploy/undeploy lifecycle status

Imported Objects

From FOUNDRY-SN-ROOT-MIB

brcdMct

OBJECT-IDENTITY

From FOUNDRY-SN-SWITCH-GROUP-MIB

BrcdVlanIdOrNoneTC
BrcdVlanIdTC

From IF-MIB

InterfaceIndex

From INET-ADDRESS-MIB

InetAddress
InetAddressType

From P-BRIDGE-MIB

EnabledStatus

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

DisplayString
RowStatus
TEXTUAL-CONVENTION
TimeInterval
TruthValue

OIDs

OID symbolic	OID numeric	Type	Access	Description
brcdMctMIB	1.3.6.1.4.1.1991.1.1.12.1			The MIB module contains the managed object definition for Brocade Multi Chassis Trunking. Supported Platforms: - supported on NetIron XMR/MLX CES/CER platforms. Copyright 1996-2012 Brocade Communications Systems, Inc. All rights reserved. This Brocade Communications Systems SNMP Management Information Base Specification embodies Brocade Communications Systems confidential and proprietary intellectual property. Brocade Communications Systems retains all title and ownership in the Specification, including any revisions. This Specification is supplied AS IS, and Brocade Communications Systems makes no warranty, either express or implied, as to the use, operation, condition, or performance of the specification, and any unintended consequence it may on the user environment.
brcdMctNotifications	1.3.6.1.4.1.1991.1.1.12.1.0
NTF brcdMctClusterPeerStatus	1.3.6.1.4.1.1991.1.1.12.1.0.1			This notification is generated when the brcdMctClusterPeerOperStatus object for peer entry in brcdMctClusterPeerTable changes the state to ccpUp(3), ccpDown(4) or reachable(5) from any other state.
NTF brcdMctClusterClientStatus	1.3.6.1.4.1.1991.1.1.12.1.0.2			This notification is generated when the brcdMctClusterClientOperStatus object for peer entry in brcdMctClusterClientTable changes the state to remoteUp(5), localUp(6), up(7), slave(8), master(9) or masterPeerUp(10) from any other state. This notification is not generated when the client state change happens when brcdMctClusterPeerOperState changes from ccpUp(2) to ccpDown(3) or vice versa
brcdMctObjects	1.3.6.1.4.1.1991.1.1.12.1.1
ENA brcdMctL2Forward	1.3.6.1.4.1.1991.1.1.12.1.1.1	EnabledStatus	read-write	The global cluster L2 forward state for this system. When this object is set to disable, the STP protocol packets coming on the MCT VLANs are dropped.
brcdMctClusterTable	1.3.6.1.4.1.1991.1.1.12.1.1.2		not-accessible	This table provides Multi Chassis Trunking Cluster information.
brcdMctClusterEntry	1.3.6.1.4.1.1991.1.1.12.1.1.2.1		not-accessible	An entry in this table represents the MCT Cluster.
U32 brcdMctClusterId	1.3.6.1.4.1.1991.1.1.12.1.1.2.1.1	Unsigned32	not-accessible	The id for this MCT Cluster.
STR brcdMctClusterName	1.3.6.1.4.1.1991.1.1.12.1.1.2.1.2	DisplayString	read-create	The name of this MCT Cluster. This object cannot be modified after creation.
U32 brcdMctClusterRbridgeId	1.3.6.1.4.1.1991.1.1.12.1.1.2.1.3	Unsigned32	read-create	The remote bridge id of this MCT Cluster. This remote bridge id is used by the peer to communicate with this cluster node.
BRC brcdMctClusterSessionVlan	1.3.6.1.4.1.1991.1.1.12.1.1.2.1.4	BrcdVlanIdTC	read-create	The session VLAN of this MCT Cluster. The cluster session VLAN can be in the range of 1 to 4090, but cannot be default VLAN. The brcdMctClusterSessionVlan and brcdMctClusterKeepAliveVlan cannot be same.
BRC brcdMctClusterKeepAliveVlan	1.3.6.1.4.1.1991.1.1.12.1.1.2.1.5	BrcdVlanIdOrNoneTC	read-create	The keep-alive VLAN of this MCT Cluster. The keep-alive VLAN can be in the range of 0 to 4090, but cannot be default VLAN. The brcdMctClusterSessionVlan and brcdMctClusterKeepAliveVlan cannot be same. The value 0 indicates that keep-alive VLAN is not set for this cluster. If brcdMctClusterClientIsolationMode object is set to strict(2), then brcdMctClusterKeepAliveVlan cannot be set to except with value 0.
INT brcdMctClusterClientIsolationMode	1.3.6.1.4.1.1991.1.1.12.1.1.2.1.6	INTEGER	read-create	The client isolation mode of this MCT Cluster. When this object is set to loose(1), then whenever the CCP goes down the client performs the Master/Slave negotiation. After negotiation, the Slave shuts down its client ports whereas the Master client ports continue to forward the traffic. When this object is set to strict(2), then whenever the CCP goes down, the client interfaces on both the cluster nodes are administratively shutdown. In this mode, the client is completely isolated from the network if CCP is not operational. If brcdMctClusterKeepAliveVlan is set to a VLAN id except 0, then brcdMctClusterClientIsolationMode cannot be set to strict(2).
T/F brcdMctClusterClientShutdown	1.3.6.1.4.1.1991.1.1.12.1.1.2.1.7	TruthValue	read-create	The client shutdown state of this MCT Cluster. When set to true, shutdown all the local client interfaces in the cluster. This would result in failover of traffic to the cluster peer.
STR brcdMctClusterMemberVlans	1.3.6.1.4.1.1991.1.1.12.1.1.2.1.8	DisplayString	read-create	The list of the member VLAN ids on which this MCT cluster is operating. This would be the range of VLANs for which there would be MAC synchronization. The VLANs which are not continuous are represented with a space separated and continuous VLANs represented with the range. For example: 2 5 10 to 40 100
STR brcdMctClusterActiveMemberVlans	1.3.6.1.4.1.1991.1.1.12.1.1.2.1.9	DisplayString	read-only	The list of the active member VLANs of this MCT Cluster. The VLANs which are not continuous are represented with a space separated and continuous VLANs represented with the range. For example: 2 5 10 to 40 100
BRC brcdMctClusterDeploy	1.3.6.1.4.1.1991.1.1.12.1.1.2.1.10	BrcdDeployStatus	read-create	The admin status of this MCT Cluster. When this object is set to deploy, consistency check of the entire cluster configuration is done. Once the cluster is deployed, the configuration cannot be modified except for the brcdMctClusterMemberVlans, brcdMctClusterClientIsolationMode and brcdMctClusterDeploy objects.
INT brcdMctClusterDeployFailureReason	1.3.6.1.4.1.1991.1.1.12.1.1.2.1.11	INTEGER	read-only	The last failure reason for cluster deploy operation through SNMP. The following failure reason codes are supported: none(1) - The last deploy is successful. unknown(2) - The last deploy has failed for unknown reason. rBridgeIdNotConfigured(3) - Remote bridge id is not configured. sessionVlanNotConfigured(4) - Session VLAN is not configured. iclNotConfigured(5) - ICL is not configured. peerNotConfigured(6) - Peer is not configured. iclIsMrpSecondaryInterface(7) - In NI CES/CER devices, ICL should not be MRP secondary interface. iclIsErpRplInterface(8) - In NI CES/CER devices, ICL should not be ERP RPL interface. iclIsErpMsInterface(9) - In NI CES/CER devices, ICL should not be ERP MS interface. iclIsErpFsInterface(10) - In NI CES/CER devices, ICL should not be ERP FS interface. iclNotInSessionVlan(11) - ICL is not in session VLAN. iclNotInMemberVlans(12) - ICL is not in member VLANs. nonIclInterfacesInSessionVlan(13) - Non ICL interfaces are present under session VLAN. mgmtVeNotConfiguredInSessionVlan(14) - Management VE is not configured in session VLAN. mgmtIpNotConfiguredInSessionVlan(15) - Management IP is not configured in session VLAN. mgmtIpIsUsedInPeerOrClientConfig(16) - Management IP is used in peer or client configuration. mgmtIpNotInSubnetOfPeerIp(17) - Management IP is not in subnet of peer IP. rBridgeIdUsedInPeerOrClientConfig(18) - Remote bridge id is used in peer or client configuration. clientInterfaceIsNotInMemberVlan(19) - Client interface is not in member VLAN. defaultVlanConfigAsSessOrMemberVlan(20) - Default VLAN is configured as session or member VLAN.
ROW brcdMctClusterRowStatus	1.3.6.1.4.1.1991.1.1.12.1.1.2.1.12	RowStatus	read-create	The row status of this MCT Cluster. All the values of RowStatus are supported. The notInService(2) indicates that cluster is not yet activated. The following objects should be present in the same SNMP set request to create a row with brcdMctClusterRowStatus set to createAndGo(4) value: brcdMctClusterName, brcdMctClusterRbridgeId, brcdMctClusterSessionVlan, brcdMctClusterMemberVlans, objects. The brcdMctClusterName object should be present in the same SNMP set request to create a row in brcdMctClusterTable with brcdMctClusterRowStatus set to createAndWait(5) value. If the cluster is deployed, then brcdMctClusterRowStatus cannot be set destroy(6)
brcdMctClusterIclTable	1.3.6.1.4.1.1991.1.1.12.1.1.3		not-accessible	This table provides Multi Chassis Trunking Cluster information.
brcdMctClusterIclEntry	1.3.6.1.4.1.1991.1.1.12.1.1.3.1		not-accessible	An entry in this table represents the MCT Cluster ICL.
STR brcdMctClusterIclName	1.3.6.1.4.1.1991.1.1.12.1.1.3.1.1	DisplayString	not-accessible	The name of ICL.
NUM brcdMctClusterIclIfIndex	1.3.6.1.4.1.1991.1.1.12.1.1.3.1.2	InterfaceIndex	read-create	The interface index of the ICL. The ICL interface can be a single ethernet interface or trunk interface index.
ROW brcdMctClusterIclRowStatus	1.3.6.1.4.1.1991.1.1.12.1.1.3.1.3	RowStatus	read-create	The row status of this MCT Cluster ICL entry. Only the active(1), createAndGo(4) and destroy (6) values of RowStatus are supported. If the cluster is deployed, then brcdMctClusterIclRowStatus cannot be set destroy(6). If the brcdMctClusterIclName is used in the peer configuration for object brcdMctClusterPeerIclName, then the peer configuration should be removed before setting the brcdMctClusterIclRowStatus to destroy(6)
brcdMctClusterPeerTable	1.3.6.1.4.1.1991.1.1.12.1.1.4		not-accessible	This table provides Multi Chassis Trunking Cluster Peers information. The objects in this table cannot be modified after the cluster is deployed
brcdMctClusterPeerEntry	1.3.6.1.4.1.1991.1.1.12.1.1.4.1		not-accessible	An entry in this table represents the MCT Cluster Peer.
IPt brcdMctClusterPeerAddrType	1.3.6.1.4.1.1991.1.1.12.1.1.4.1.1	InetAddressType	not-accessible	The address type of this MCT Cluster Peer. The supported address types are ipv4(1) and ipv6(2).
IP brcdMctClusterPeerAddr	1.3.6.1.4.1.1991.1.1.12.1.1.4.1.2	InetAddress	not-accessible	The IPv4/IPv6 address of this MCT Cluster Peer.
U32 brcdMctClusterPeerRbridgeId	1.3.6.1.4.1.1991.1.1.12.1.1.4.1.3	Unsigned32	read-create	The remote bridge Id of this MCT Cluster Peer.
STR brcdMctClusterPeerIclName	1.3.6.1.4.1.1991.1.1.12.1.1.4.1.4	DisplayString	read-create	The ICL name of this MCT Cluster Peer. This should be same as brcdMctClusterIclName object for this MCT Cluster
ENA brcdMctClusterPeerFastFailover	1.3.6.1.4.1.1991.1.1.12.1.1.4.1.5	EnabledStatus	read-create	The fast failover status of this MCT Cluster Peer. When this object is set to enable, as soon as the ICL interface goes down the CCP goes down. All the remote MACs are flushed. When set to disable, even if the ICL interface goes down the CCP waits for the hold-time before making the CCP down. Remote MACs are flushed only when the CCP is down.
U32 brcdMctClusterPeerKeepAliveTime	1.3.6.1.4.1.1991.1.1.12.1.1.4.1.6	Unsigned32	read-create	The keep-alive time in seconds of this MCT Cluster Peer. The range of keep-alive time is 0 to 21845. The default is 30 seconds.
U32 brcdMctClusterPeerHoldTime	1.3.6.1.4.1.1991.1.1.12.1.1.4.1.7	Unsigned32	read-create	The hold time in seconds of this MCT Cluster Peer. The hold time must be at least 3 times the keep alive time. The range of hold time is 3 to 65535. The default is 90 seconds.
STR brcdMctClusterPeerActiveVlans	1.3.6.1.4.1.1991.1.1.12.1.1.4.1.8	DisplayString	read-only	The list of the active member VLANs of this MCT Cluster Peer. The VLANs which are not continuous are represented with a space separated and continuous VLANs represented with the range. For example: 2 5 10 to 40 100
INT brcdMctClusterPeerOperStatus	1.3.6.1.4.1.1991.1.1.12.1.1.4.1.9	INTEGER	read-only	The operational status of this MCT Cluster Peer. The follwoing values are supported for operational status unknown(1) - Unknown state noState(2) - The peer state machine is not started init(3) - The peer state machine is initializing ccpUp(4) - CCP is up ccpDown(5) - CCP is down reachable(6) - CCP is down, but peer is reachable through keep alive VLAN
INT brcdMctClusterPeerDownReason	1.3.6.1.4.1.1991.1.1.12.1.1.4.1.10	INTEGER	read-only	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
NUM brcdMctClusterPeerUpTime	1.3.6.1.4.1.1991.1.1.12.1.1.4.1.11	TimeInterval	read-only	The time since this MCT Cluster Peer is up. If the brcdMctClusterPeerOperStatus is not in ccpUp(2) state, then zero will be returned.
ROW brcdMctClusterPeerRowStatus	1.3.6.1.4.1.1991.1.1.12.1.1.4.1.12	RowStatus	read-create	The row status of this MCT Cluster Peer. Only the active(1), notInService(2), createAndGo(4) and destroy(6) values of RowStatus are supported. The notInService(2) indicates that cluster is not yet activated. The SNMP set request to create a row with brcdMctClusterPeerRowStatus set to createAndGo(4) value should contain the brcdMctClusterPeerRbridgeId and brcdMctClusterPeerIclName objects in the same SNMP set request. If the cluster is deployed, then brcdMctClusterPeerRowStatus cannot be set destroy(6)
brcdMctClusterClientTable	1.3.6.1.4.1.1991.1.1.12.1.1.5		not-accessible	This table provides Multi Chassis Trunking Cluster Clients information.
brcdMctClusterClientEntry	1.3.6.1.4.1.1991.1.1.12.1.1.5.1		not-accessible	An entry in this table represents the MCT Cluster Client.
STR brcdMctClusterClientName	1.3.6.1.4.1.1991.1.1.12.1.1.5.1.1	DisplayString	not-accessible	The name of this MCT Cluster client.
U32 brcdMctClusterClientRbridgeId	1.3.6.1.4.1.1991.1.1.12.1.1.5.1.2	Unsigned32	read-create	The remote bridge id of this MCT Cluster client. This remote bridge ID is used by the client to communicate with this cluster node.
NUM brcdMctClusterClientIfIndex	1.3.6.1.4.1.1991.1.1.12.1.1.5.1.3	InterfaceIndex	read-create	The interface index which is connected to this MCT Cluster client. The interface should be an ethernet interface or trunk interface.
INT brcdMctClusterClientOperStatus	1.3.6.1.4.1.1991.1.1.12.1.1.5.1.4	INTEGER	read-only	The operational status of this MCT Cluster client. The following values are taken by the operational status: unknown(1) - Unknown state noState(2) - The peer state machine is not started init(3) - The peer state machine is initializing localDeploy(4) - The client is up, but not configured at remote side adminUp(5) - The client is up, but both the client interfaces are operationally down remoteUp(6) - The client's remote side is up and locally down localUp(7) - The client is locallly up and remote side is down up(8) - The client is up locally and at remote side slave(9) - The client is down and it has taken the slave role master(10) - The client is down and it has taken the master role masterPeerUp(11) - The client is down, it has taken the master role and master peer is up.
BRC brcdMctClusterClientDeploy	1.3.6.1.4.1.1991.1.1.12.1.1.5.1.5	BrcdDeployStatus	read-create	The admin status of this MCT Cluster client. When this object is set to deploy and if cluster is not deployed, the configuration will be taken but the client state machine will not be started. The objects in this table are not allowed to modify after client is deployed except brcdMctClusterClientDeploy object.
INT brcdMctClusterClientDeployFailureReason	1.3.6.1.4.1.1991.1.1.12.1.1.5.1.6	INTEGER	read-only	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.
ROW brcdMctClusterClientRowStatus	1.3.6.1.4.1.1991.1.1.12.1.1.5.1.7	RowStatus	read-create	The row status of this MCT Cluster client. All the values of RowStatus are supported. The notInService(2) indicates that cluster client is not deployed. The brcdMctClusterClientRbridgeId and brcdMctClusterClientIfIndex objects should be present in the same SNMP set request to create a row with brcdMctClusterClientRowStatus set to createAndGo(4) value.

RFC description

Manages Brocade Multi Chassis Trunking for NetIron XMR/MLX platforms supporting clustered switch configurations.

Start monitoring Brocade NetIron XMR/MLX CES/CER chassis routers and switches with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download BROCADE-MCT-CLUSTER-MIB

What Is BROCADE-MCT-CLUSTER-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description