You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do you already have an issue opened with F5 support?
No
Description
I would like to know if we could have the CFE perform regular "dry-run" failovers, so that if a change was made in the AWS environment that would adversely affect CFE operations, we would find out right away.
Today's scenario:
NetOps team sets up F5 and CFE. Tests failover successfully.
6 months may pass. Another team may "clean up" tags, edit IAM Roles, or make other changes that aren't communicated.
DR situation occurs but CFE is unable to perform failover due to mis-configuration.
My preferred scenario:
NetOps team sets up F5 and tests CFE.
Another team makes a change to AWS infrastructure but CFE notices this change within a specified time, perhaps 60 mins? It could log the failed Dry Run attempt, which could be monitored by an external system. Ideally, CFE config and AWS config do not get out of sync in this scenario.
Severity level :
Severity 3 (Medium) : Defect is causing intermittent errors in system operations.
The text was updated successfully, but these errors were encountered:
Do you already have an issue opened with F5 support?
No
Description
I would like to know if we could have the CFE perform regular "dry-run" failovers, so that if a change was made in the AWS environment that would adversely affect CFE operations, we would find out right away.
Today's scenario:
My preferred scenario:
Severity level :
The text was updated successfully, but these errors were encountered: