dpConfigQuotaEnforcementServerTable

DATAPOWER-CONFIG-MIB · .1.3.6.1.4.1.14685.3.2.504

Object

table
On each DataPower appliance, you configure the quota enforcement server to
store the thresholds and associated metadata in memory or persist them on
the RAID volume. The quota enforcement server can work in standalone mode
or peer group mode. A peer group is collection of at least three DataPower
appliances across which quota enforcement is implemented. In each peer
group, one appliance is the master and other appliances are slaves.
Failover might occur when the master becomes unavailable. When you enable
the peer group mode, the appropriate configuration properties are
displayed. You must configure the connection among peers. Based on your
requirements for quota enforcement, you can enable or disable strict mode.
Strict mode affects data-consistency across the peer group. When strict
mode is enabled, the following effects are caused: When the master is
operational and when strict mode of all appliances in a peer group is
enabled, threshold synchronization is more frequent to ensure
data-consistency across the peer group. However, more network bandwidth is
used. Therefore, strict mode is suitable for peers in the same data
center. When the master becomes unavailable, before failover occurs, the
slave with enabled strict mode cannot process the request. If service
performance and availability are more important than data-consistency, you
can disable strict mode for the slave so that this slave can process the
request. The slave with disabled strict mode writes the threshold and
associated metadata to the local data storage. After failover occurs, the
connection is resumed between the slave and the new master. The threshold
and associated metadata stored by the slave might be overwritten by the
new master when the new master synchronizes the data to all slaves.
Data-consistency might be affected across the peer group. By default, data
is stored in memory and quota enforcement server works in standalone mode.

Context

MIB
DATAPOWER-CONFIG-MIB
OID
.1.3.6.1.4.1.14685.3.2.504
Type
table
Status
current
Parent
dpConfig
Siblings
357
Children
1

Syntax

No syntax metadata recorded.

Values & Constraints

No enumerated values or constraints recorded.

Related Objects

Sibling Objects
Child Objects