search

F5Networks / f5-cloud-failover-extension

F5 Cloud Failover Extension
Apache License 2.0
15 stars 2 forks source link

How to handle more than one VLAN for failover #136

Closed pedley-f5 closed 8 months ago

pedley-f5 commented 8 months ago

Do you already have an issue opened with F5 support?

No

Description

I have an HA Pair of BIG-IPs across AZ in AWS. I have two VLANs on each (likely more in the future) that require virtual servers to fail over from one BIG-IP to another, for example: BIG-IP1: External interface 1 self IP: 10.0.0.253/24 External interface 2 self IP: 10.0.1.253/24

BIG-IP2: External interface 1 self IP: 10.0.16.253/24 External interface 2 self IP: 10.0.17.253/24

I already have EIPs associated with all of my VIPs on BIG-IP1

Environment information

For bugs, enter the following information:

Severity Level

For bugs, enter the bug severity level. Do not set any labels.

Severity: N/A

Severity level definitions:

  1. Severity 1 (Critical) : Defect is causing systems to be offline and/or nonfunctional. immediate attention is required.
  2. Severity 2 (High) : Defect is causing major obstruction of system operations.
  3. Severity 3 (Medium) : Defect is causing intermittent errors in system operations.
  4. Severity 4 (Low) : Defect is causing infrequent interuptions in system operations.
  5. Severity 5 (Trival) : Defect is not causing any interuptions to system operations, but none-the-less is a bug.
mikeshimkus commented 8 months ago

Hi @pedley-f5, can you share your (sanitized) CFE configuration and any f5-cloud-failover errors from /var/log/restnoded/restnoded.log here? This should work today.

pedley-f5 commented 8 months ago

Hi @mikeshimkus , I don't have any errors in the log (yet) because this configuration is actually working for a single pair of VLANs (one external VLAN on each BIG-IP in the HA group), but now I want to configure a 2nd pair of external VLANs. The documentation doesn't make it very clear how this can be done.

{ "message": "success", "declaration": { "schemaVersion": "1.0.0", "class": "Cloud_Failover", "environment": "aws", "controls": { "class": "Controls", "logLevel": "silly" }, "externalStorage": { "encryption": { "serverSide": { "enabled": true, "algorithm": "AES256" } }, "scopingTags": { "f5_cloud_failover_label": "f5-bigip-ha-failover" } }, "failoverAddresses": { "enabled": true, "scopingTags": { "f5_cloud_failover_label": "f5-bigip-ha-failover" }, "requireScopingTags": false } } }

pedley-f5 commented 8 months ago

Hi @mikeshimkus , I think I figured this out. I needed to specify a unique value for f5_cloud_failover_nic_map. It was in the gitlab docs but not clouddocs. I think we're good to close. Thanks for your help!