The Redundancy Tab
The Redundancy section, shown in the following figure, displays the following information:
- General Settings
- Status
- Failover Triggers
General Settings
The general settings section of the Redundancy section displays the following information:
| Field | Description |
|---|---|
| Redundant Collector | If enabled, specifies that this is a redundant collector. |
| Backup For | Specifies the primary collector. Note: This configuration will be preserved if you disable collector redundancy. This allows you to temporarily take a redundant collector offline without losing its configuration. |
| Backed Up By | The name of the collector providing redundancy for the selected collector. |
Status
The status section of the Redundancy tab displays the following information:
| Field | Description |
|---|---|
| Collector Status (Status) | The current status of this collector |
| Redundancy Status | The current redundancy status of this collector. If a secondary collector has been activated, this will display. |
| Make Active Collector Now! | Select this button to bring the selected collector online immediately. This is useful for testing, or in situations where the primary collector must be brought offline quickly. |
Failover Triggers
The Failover Triggers section of the Redundancy tab displays the following information:
| Field | Description |
|---|---|
| Collector Status (Failover Triggers) | If enabled, the collector will fail over if the status changes to Unknown. |
| Watchdog Tag | Specifies a tag to use to determine the status of the collector. If the watchdog tag meets any of the conditions specified below, the secondary collector will be brought on line to replace it. |
| Failover on Bad Quality | If enabled, the secondary collector is promoted when a data sample from the watchdog tag is received with bad quality. Failover happens on every write of a bad data sample to the watchdog, not just on the transition from good to bad quality. |
| Failover When Value Transitions from Zero | If selected, the secondary collector is promoted when a data sample from the watchdog tag with a non-zero value is received from the primary collector. Failure happens every time when a non-zero value is received, not just when the value promotes from zero to non-zero value. |
| Failover When No Value Changes for X Seconds | If selected, the secondary collector is promoted when no data value changes have been received within the time period specified. This could be tied into a heartbeat status indicator. Refer to Collector Status Outputs for more information. The value is checked every 5 seconds. To prevent failure, there must be a value change. |