This object indicates the current status of this cluster of
Cisco LiveData servers. A cluster is a group of one or more
Cisco LiveData servers that work cooperatively to consume and
process inbound real-time data from one or more data sources.
Work is distributed between worker nodes within the cluster
by the master node. A cluster may have a peer cluster in a
fault-tolerant deployment model that will assume data
processing duties in the event where its active peer cluster
fails.
'pairedActive': The cluster is actively processing data
and is communicating with its remote
peer cluster.
'pairedStandby': The cluster is standing by (waiting to
process data if necessary) and is
communicating with its remote peer
cluster.
'isolatedActive': The cluster is is actively processing
data but has lost peer-to-peer
communication with it's remote peer
cluster.
'isolatedStandby': The cluster is standing by (waiting to
process data if necessary) but has lost
peer-to-peer communication with its
remote peer cluster.
'testing': The cluster is unable to communicate
with the remote peer cluster via the
peer-to-peer connection and it is
invoking the 'test-other-side' procedure
to decide whether to become active or to
go into a standby state.
'outOfService': The cluster is out of service.
This object indicates the current status of this cluster of
Cisco LiveData servers. A cluster is a group of one or more
Cisco LiveData servers that work cooperatively to consume and
process inbound real-time data from one or more data sources.
Work is distributed between worker nodes within the cluster
by the master node. A cluster may have a peer cluster in a
fault-tolerant deployment model that will assume data
processing duties in the event where its active peer cluster
fails.
'pairedActive': The cluster is actively processing data
and is communicating with its remote
peer cluster.
'pairedStandby': The cluster is standing by (waiting to
process data if necessary) and is
communicating with its remote peer
cluster.
'isolatedActive': The cluster is is actively processing
data but has lost peer-to-peer
communication with it's remote peer
cluster.
'isolatedStandby': The cluster is standing by (waiting to
process data if necessary) but has lost
peer-to-peer communication with its
remote peer cluster.
'testing': The cluster is unable to communicate
with the remote peer cluster via the
peer-to-peer connection and it is
invoking the 'test-other-side' procedure
to decide whether to become active or to
go into a standby state.
'outOfService': The cluster is out of service.
cldClusterStatus OBJECT-TYPE SYNTAX INTEGER { pairedActive(1), pairedStandby(2), isolatedActive(3), isolatedStandby(4), testing(5), outOfService(6) } ACCESS read-only STATUS mandatory DESCRIPTION "This object indicates the current status of this cluster of Cisco LiveData servers. A cluster is a group of one or more Cisco LiveData servers that work cooperatively to consume and process inbound real-time data from one or more data sources. Work is distributed between worker nodes within the cluster by the master node. A cluster may have a peer cluster in a fault-tolerant deployment model that will assume data processing duties in the event where its active peer cluster fails. 'pairedActive': The cluster is actively processing data and is communicating with its remote peer cluster. 'pairedStandby': The cluster is standing by (waiting to process data if necessary) and is communicating with its remote peer cluster. 'isolatedActive': The cluster is is actively processing data but has lost peer-to-peer communication with it's remote peer cluster. 'isolatedStandby': The cluster is standing by (waiting to process data if necessary) but has lost peer-to-peer communication with its remote peer cluster. 'testing': The cluster is unable to communicate with the remote peer cluster via the peer-to-peer connection and it is invoking the 'test-other-side' procedure to decide whether to become active or to go into a standby state. 'outOfService': The cluster is out of service." ::= { cldCluster 2 }
cldClusterStatus OBJECT-TYPE SYNTAX INTEGER { pairedActive(1), pairedStandby(2), isolatedActive(3), isolatedStandby(4), testing(5), outOfService(6) } MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the current status of this cluster of Cisco LiveData servers. A cluster is a group of one or more Cisco LiveData servers that work cooperatively to consume and process inbound real-time data from one or more data sources. Work is distributed between worker nodes within the cluster by the master node. A cluster may have a peer cluster in a fault-tolerant deployment model that will assume data processing duties in the event where its active peer cluster fails. 'pairedActive': The cluster is actively processing data and is communicating with its remote peer cluster. 'pairedStandby': The cluster is standing by (waiting to process data if necessary) and is communicating with its remote peer cluster. 'isolatedActive': The cluster is is actively processing data but has lost peer-to-peer communication with it's remote peer cluster. 'isolatedStandby': The cluster is standing by (waiting to process data if necessary) but has lost peer-to-peer communication with its remote peer cluster. 'testing': The cluster is unable to communicate with the remote peer cluster via the peer-to-peer connection and it is invoking the 'test-other-side' procedure to decide whether to become active or to go into a standby state. 'outOfService': The cluster is out of service." ::= { cldCluster 2 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.814.1.2.1 | cldClusterID | 0 | 0 | This object indicates a cluster- unique textual identifier for this cluster (e.g. 'sideA'). |
| 1.3.6.1.4.1.9.9.814.1.2.3 | cldClusterAddress | 0 | 0 | This object indicates the hostname or the IP address of the remote peer cluster for peer-to-peer communication with the remote cl… |