CPS vDRA supports
configurable retries, so that the specific behavior of CPS vDRA in congestion
scenarios can be configured.
mechanism (i.e., number of retries) per:
This should be in the
form of a CRD and applied to a peer group. The user can use the SRK peers to
select an alternate peer.
If all SRK peers
fail, the user should use one alternate CPS vDRA if it connects to the SRK. If
the SRK matches exactly, CPS vDRA would look for the second label match of SRK
like clusterb.dc1 and clusterc.dc1 and retry the message to other peer group.
Figure 16. Message Retry
Profile - Control Center
Wild card match is
supported for Peer Group, Application Id, Command Code, Result Code columns.
For example, 300.* supports all RC starting with 300.
* is supported to
allow all RC.
* is supported
for all peer groups.
Match = GX_DC_.*
is supported for groups starting with GX_DC
RC = 7000 is
interpreted as retry for timeout.
code is for future purposes and value in that column has no effect on retry
Match check box needs to be checked in Policy Builder if you want
to use the wildcard feature.
Message Retry Profile
for configuration in