Test #6 -Standby Server Loses then Re-establishes Network Connectivity
This demonstrates mediation behavior when the standby server loses network connectivity temporarily. Here, we simulate the temporary loss of network connectivity by pulling the network cable from the mediation server while it is actively processing events, waiting two minutes and then plugging the network cable back in.
• The standby server should discard events until it loses network connectivity.
• The active server should not be affected by the standby server losing connectivity and should continue to deliver events.
• After losing network connectivity, the standby server should switch to an active mode and attempt to deliver any spooled events that it may have.
• Once network connectivity is re-established both servers are active. Both should be attempting to deliver traps while they re-negotiate roles.
• Once negotiation is complete one of the servers reverts to standby and begins discarding events.
• The total number of delivered events may be more then 30,000 since this process delivers duplicate events. Since the standby server is at most 15 seconds behind the active server (the timeout period) the maximum number of duplicate events processed is approximately 1500 (15 seconds @ 100 per second).
Actual Results: SUCCESS
• Active Server - The active server delivered events continuously even after the standby server disconnected. It delivered 19400 events before assuming a standby mode.
• Standby Server - The standby server discarded 4800 events before it disconnected, with 1100 remaining in batch. Once disconnected, it switched to active mode. Once reconnected, it retained active mode, and delivered a total of 12600 events (including those it had held in batch).
The total number of events delivered was 32000, with 2000 of those being duplicates.