dpConfigLLMMulticastTierGroupTable

The LLM Multicast Tier Group identifies a configuration that combines a
group of two or more machines called tier members into a tier failover
group for stream-based Reliable and Consistent Message Streaming (RCMS). A
tier consists of a group of application components in a configuration
where each component is an identical replica. Each replica executes the
application logic as if it was the only component. RCMS, by synchronizing
inbound and outbound traffic for each tier member, ensures that the
application remains available in the case of a failure. As a result, any
new tier component can start fully functioning in parallel with its
existing running peers, and support them in case of failure. RCMS is a
part of LLM that provides high availability and consistent, ordered
message delivery. It supports the following features: Failure detection
and failover Total ordering State synchronization Component group
management RCMS is based on a component replication model where all
members of a tier group perform the following actions: Receive the same
input Perform same processing Produce the same output RCMS enhances the
high availability capabilities of RMM by ensuring that all instances of
the application get exactly the same input and can therefore maintain
identical state. For receiver tier topics this means that in all tier
members all the tier receiver topics deliver exactly the same set of
messages to the application. If the tier enforces total order, then all
the messages from all topics are delivered in exactly the same order.
Multiple instances of the application run simultaneously. If one of the
instances of the application fails, RCMS detects the failure and
automatically takes corrective actions (for example, to replace an
instance that failed). Stream failover allows receivers to switch from one
transmitter stream to another with little or no message loss when a
transmitter fails. Both RMM and RUM support stream failover. RCMS
implements basic stream failover by coordinating transmitters and
synchronizing application state and message sequence numbers.

MIB

DATAPOWER-CONFIG-MIB

OID

.1.3.6.1.4.1.14685.3.2.184

Type

table

Status

current

Parent

dpConfig

Children

1