User guide

Chapter 6 Control Configuration
The RDR Formatter
SCE 1000 2xGBE Release 2.0.10 User Guide
6-22 OL-7117-02
Protocol Version
The RDR protocol is used to export the application reports from the SCE 1000 to an external
destination. Currently, Cisco supports two versions o the RDR protocol: RDR protocol version 1
(RDRv1) protocol and RDR protocol version 2 (RDRv2). The SCE 1000 can support the
formatting of RDRs based on either of these protocols. The selection of the configured protocol
should be based on the destination capabilities. Please note that RDRv2 is superior to RDRv1
with respect to redundancy, robustness, and reliability.
The RDR formatter can be configured to work with exclusively RDRv1 protocol or RDRv2
protocol for the selected RDR formatter destination.
Note
The RDR formatter must be disabled when configuring the protocol version.
The RDRv1 does not support RDR aggregation (the ability to combine and store separate RDR
streams in case of failure), so the following restrictions should be noted:
• The simple-load-balancing forwarding mode is not to be used with RDRv1.
Note that no error message will appear if the simple-load-balancing forwarding mode is
defined with the RDRv1 protocol, even though it is not recommended with this protocol.
• The size of the history buffer must be zero bytes (the default value). Other values may cause
duplication of RDRs.
• The connection timeout parameter is not supported by the RDRv1 protocol.
Forwarding Modes
When more than one RDR destination is defined for a category, the system must decide which of
these destinations is to receive the RDRs. This is determined by the forwarding mode. There are
three forwarding modes:
• Redundancy: All RDRs are sent only to the primary (active) connection. If the primary
connection fails, the RDRs will be sent to the connected destination with the next highest
priority.
When the formatter switches to the secondary connection, it resends the messages collected in
the history buffer to that destination.
• Simple load balancing: Each successive RDR is sent to a different destination, one destination
after the other, in a round robin manner. It is the responsibility of the collectors to aggregate
the RDRs.
If one connection fails, the contents of the history buffer are sent to all connected destinations.
Note
Do not use the load-balancing feature with the RDRv1 protocol, as this protocol does not support RDR
aggregation.
• Multicast: All RDRs are sent to all destinations. This feature may negatively affect
performance in an installation with a high rate of RDRs.