BROCADE-MCT-CLUSTER-MIB: View SNMP OID List / Download MIB

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.

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.

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

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.

This table provides Multi Chassis Trunking Cluster information.

An entry in this table represents the MCT Cluster.

The id for this MCT Cluster.

The name of this MCT Cluster. This object cannot be modified after creation.

The remote bridge id of this MCT Cluster. This remote bridge id is used by the peer to communicate with this cluster node.

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.

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.

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). Enumeration: 'strict': 2, 'loose': 1.

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.

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

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

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.

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. Enumeration: 'mgmtIpNotConfiguredInSessionVlan': 15, 'none': 1, 'rBridgeIdIsUsedInPeerOrClientConfig': 18, 'iclNotInSessionVlan': 11, 'nonIclInterfacesInSessionVlan': 13, 'unknown': 2, 'sessionVlanNotConfigured': 4, 'iclIsErpMsInterface': 9, 'mgmtIpNotInSubnetOfPeerIp': 17, 'iclNotInMemberVlans': 12, 'peerNotConfigured': 6, 'clientInterfaceIsNotInMemberVlan': 19, 'mgmtVeNotConfiguredInSessionVlan': 14, 'rBridgeIdNotConfigured': 3, 'iclNotConfigured': 5, 'iclIsErpFsInterface': 10, 'defaultVlanConfigForSessionOrMemberVlan': 20, 'iclIsErpRplInterface': 8, 'iclIsMrpSecondaryInterface': 7, 'mgmtIpIsUsedInPeerOrClientConfig': 16.

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)

This table provides Multi Chassis Trunking Cluster information.

An entry in this table represents the MCT Cluster ICL.

The name of ICL.

The interface index of the ICL. The ICL interface can be a single ethernet interface or trunk interface index.

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)

This table provides Multi Chassis Trunking Cluster Peers information. The objects in this table cannot be modified after the cluster is deployed

An entry in this table represents the MCT Cluster Peer.

The address type of this MCT Cluster Peer. The supported address types are ipv4(1) and ipv6(2).

The IPv4/IPv6 address of this MCT Cluster Peer.

The remote bridge Id of this MCT Cluster Peer.

The ICL name of this MCT Cluster Peer. This should be same as brcdMctClusterIclName object for this MCT Cluster

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.

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.

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.

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

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 Enumeration: 'ccpDown': 5, 'noState': 2, 'ccpUp': 4, 'unknown': 1, 'init': 3, 'reachable': 6.

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 Enumeration: 'holdTimeMismatch': 10, 'tcpConnCloseMesg': 14, 'shutdownMesgFromPeer': 12, 'upgradeInProgress': 4, 'iclInterfaceDown': 3, 'badProtocolVersionPktRecv': 21, 'fastFailoverMismatch': 11, 'invalidAppMesgRecv': 20, 'sendStateTimeoutExpired': 16, 'ccpTcpCommFail': 26, 'keepAliveMesgSendFail': 19, 'recvStateTimeoutExpired': 17, 'iclVeDown': 6, 'internalCcpErrorRecv': 25, 'loopbackInterfaceDown': 2, 'badPduLengthPktRecv': 22, 'holdTimeoutExpired': 15, 'none': 1, 'tcpKeepAliveTimeout': 13, 'keepAliveTimeMismatch': 9, 'routeNotAvailable': 5, 'invalidCcpPktRecv': 24, 'unknownCcpPktRecv': 23, 'clusterIdMismatch': 8, 'rBridgeIdMismatch': 7, 'initMesgSendFail': 18.

The time since this MCT Cluster Peer is up. If the brcdMctClusterPeerOperStatus is not in ccpUp(2) state, then zero will be returned.

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)

This table provides Multi Chassis Trunking Cluster Clients information.

An entry in this table represents the MCT Cluster Client.

The name of this MCT Cluster client.

The remote bridge id of this MCT Cluster client. This remote bridge ID is used by the client to communicate with this cluster node.

The interface index which is connected to this MCT Cluster client. The interface should be an ethernet interface or trunk interface.

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. Enumeration: 'adminUp': 5, 'slave': 9, 'remoteUp': 6, 'unknown': 1, 'localDeploy': 4, 'localUp': 7, 'up': 8, 'init': 3, 'noState': 2, 'master': 10, 'masterPeerUp': 11.

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.

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. Enumeration: 'none': 1, 'iclIsNotInMemberVlan': 9, 'clientInterfacePhysicallyNotUp': 6, 'clientInterfaceIsErpInterface': 8, 'unknown': 2, 'clientInterfaceIsMrpRingInterface': 7, 'rBridgeIdNotConfigured': 3, 'rBridgeIdUsedInClusterOrPeer': 5, 'clientInterfaceNotConfigured': 4.

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.