Forum Discussion
Davidfisher_345
Jul 20, 2018Altocumulus
Trying Active-Active-Standby in LAB, 2 devices show as offline.
Hey Gents,
This was the plan:
BIGIP1-A TG1
BIGIP2-A TG2
BIGIP3-S For both TG1 and TG2
But right now all TGs are only ACTIVE on BIGIP3 and shows as "Initializing / Not Synced".
On BIGIP3 I...
Andy_McGrath
Aug 20, 2018Cumulonimbus
First make sure each device in the Device Group has the following configured correctly,
- Configsync Ip
- Mirroring IP
- Failover Unitcast IP/Multicast IP
Once corrected ensure each device has the other 2 devices listed correctly and as connected under
Device Management ›› Device Trust : Peer List
You may need to delete and redo the Trusts to ensure all three trust each other and see each other as connected.
If you run
show cm device
you should see something like this:
-----------------------------------------------------------------
CentMgmt::Device: f5vm01.test.lab
-----------------------------------------------------------------
Hostname f5vm01.test.lab
Mgmt Ip 10.0.0.11
Configsync Ip 192.168.0.11
Mirroring IP 192.168.0.11
Mirroring Secondary IP ::
Failover Multicast IP ::
Failover Unicast IP(s) 192.168.0.11
Device HA State active
Device HA Load Capacity 0
Device Current Load Factor 1
Device Next Active Load Factor 0
-----------------------------------------------------------------
CentMgmt::Device: f5vm02.test.lab
-----------------------------------------------------------------
Hostname f5vm02.test.lab
Mgmt Ip 10.0.0.12
Configsync Ip 192.168.0.12
Mirroring IP 192.168.0.12
Mirroring Secondary IP ::
Failover Multicast IP ::
Failover Unicast IP(s) 192.168.0.12
Device HA State standby
Device HA Load Capacity 0
Device Current Load Factor 0
Device Next Active Load Factor 1
-----------------------------------------------------------------
CentMgmt::Device: f5vm03.test.lab
-----------------------------------------------------------------
Hostname f5vm03.test.lab
Mgmt Ip 10.0.0.13
Configsync Ip 192.168.0.13
Mirroring IP 192.168.0.13
Mirroring Secondary IP ::
Failover Multicast IP ::
Failover Unicast IP(s) 192.168.0.13
Device HA State standby
Device HA Load Capacity 0
Device Current Load Factor 0
Device Next Active Load Factor 0
Then setup your traffic groups, one at a time,
show cm traffic-group traffic-group-1 traffic-group-2
should look like this:
-------------------------------------------------------------------
CM::Traffic-Group
Name Device Status Next
Active
-------------------------------------------------------------------
traffic-group-1 f5vm01.test.lab active false
traffic-group-1 f5vm02.test.lab standby false
traffic-group-1 f5vm03.test.lab standby true
traffic-group-2 f5vm01.test.lab standby false
traffic-group-2 f5vm02.test.lab active false
traffic-group-2 f5vm03.test.lab standby true
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects