|
|
Description:
|
brcdMctClusterPeerDownReason OBJECT-TYPE
SYNTAX INTEGER {none(1), loopbackInterfaceDown(2), iclInterfaceDown(3), upgradeInProgress(4), routeNotAvailable(5), iclVeDown(6), rBridgeIdMismatch(7), clusterIdMismatch(8), keepAliveTimeMismatch(9), holdTimeMismatch(10), fastFailoverMismatch(11), shutdownMesgFromPeer(12), tcpKeepAliveTimeout(13), tcpConnCloseMesg(14), holdTimeoutExpired(15), sendStateTimeoutExpired(16), recvStateTimeoutExpired(17), initMesgSendFail(18), keepAliveMesgSendFail(19), invalidAppMesgRecv(20), badProtocolVersionPktRecv(21), badPduLengthPktRecv(22), unknownCcpPktRecv(23), invalidCcpPktRecv(24), internalCcpErrorRecv(25), ccpTcpCommFail(26)}
MAX-ACCESS read-only
STATUS current
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) - Graceful upgrade in progress
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"
|
|
