Forum Discussion
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 did tmsh list cm device unicast address
root@(bigip3)(cfg-sync In Sync)(Active)(/Common)(tmos) list cm device unicast-address
cm device bigip1.akm.com {
unicast-address {
{
effective-ip 192.168.20.50
effective-port cap
ip 192.168.20.50
port cap
}
{
effective-ip 10.128.1.243
effective-port cap
ip 10.128.1.243
port cap
}
}
}
cm device bigip2.akm.com {
unicast-address {
{
effective-ip 192.168.20.51
effective-port cap
ip 192.168.20.51
port cap
}
{
effective-ip 10.128.1.244
effective-port cap
ip 10.128.1.244
port cap
}
}
}
cm device bigip3.akm.com {
unicast-address none
}
Since its's all a lab, here are the QKVIEWs on gdrive for all 3 devices.
Thanks a ton for the help!
What are the unicast network failover ip addresses on bigip3.akm.com??
Cheers,
Kees
- Andy_McGrathCumulonimbus
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
you should see something like this:show cm device
----------------------------------------------------------------- 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,
should look like this:show cm traffic-group traffic-group-1 traffic-group-2
------------------------------------------------------------------- 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
* 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