very old video, but I have to say auto fallback feature is very usefull if the connectivity between both F5 (and traffic group) are in different locations, so you may be running on the standby because failover happened moving that traffic group to the other site, because of that the inter CPD communication and lag may increase a lot. With this, after the delay set (to avoid flapping) it will go back automatically to the primary one solving those things
Hi I have few queries here regarding election of Active and Standby Unit in active and standby scenario. Could you please explain on what basis the unit is elected as Active. Second query I have regarding the monitoring if one of the link connected on Active unit fails, will it failover to standby unit and how. Thanks in advance
is that correct, that ... ? BIGIP 1 machine external vlan have tag 4093, internal vlan have tag 4094 BIGIP 2 machine external vlan have tag 4094, internal vlan have tag 4093
Summary Steps: -Both Devices Self IPs - inside, outside etc DNS NTP Create HA Vlan, self IP - dedicated ha vlan Go to device - config sync - mention HA vlan - for confi sync between devices Go to device - failover - mention HA vlan - port udp 1026 - for hello, device state etc Go to device - mirroring - mention HA vlan - port tcp 1029-1055 for live connection mirroring device A device - device trust - peer device discovery - add peer device adding peer device -after this both in sync and active (No pools, vs sync yet) create device groups -name -sync-failover - this is config sync with device failover -add both devices -network -manual with incremental sync config and test failover..
You're english is better than a lot of native english speakers. Great video!
The greatest video I've watched so far with the best explanations and illustrations. Thank you sir
Great HA video. Excellent explanation and live configuration. Thanks for uploading. No need to worry about your English.
Nice video. The explanation is very clear. Kindly make more videos for other F5 products as well
very old video, but I have to say auto fallback feature is very usefull if the connectivity between both F5 (and traffic group) are in different locations, so you may be running on the standby because failover happened moving that traffic group to the other site, because of that the inter CPD communication and lag may increase a lot. With this, after the delay set (to avoid flapping) it will go back automatically to the primary one solving those things
You are correct. Yes, Time sync is very essential. Thanks for sharing :)
I couldn't found such an excellent video on any topic related to F5. Thanks for uploading it .. good job
Thank you.
Excellent video and very patient explanation, thanks!
Thank you and you are welcome.
Very good video. Thanks. It works in 13.1 as well.
Great Video
Can both F5s have the same Floating IP Address? Why?
Thanks for the video. It helped me a lot getting started.
Thanks, saved my day!
Very helpful video. Thank you.
Thanks, its really helpful.
Thanks, it was really helpful
It was a very good video guide! If I have two boxes (VE actually), must their self-IP and floating IP be the same?
Li Davis must be in same subnet
Hi I have few queries here regarding election of Active and Standby Unit in active and standby scenario. Could you please explain on what basis the unit is elected as Active. Second query I have regarding the monitoring if one of the link connected on Active unit fails, will it failover to standby unit and how. Thanks in advance
good video , is it possible to get another with ASM
are you still available to answer one query !!
Thanks , its a very helpful Video.
Also make sure that NTP is set up and connected to NTP servers by running "ntpq -np" from bash.
such an excellent video
Thank you.
Its Okay hope its made a little more simpler
is that correct, that ... ?
BIGIP 1 machine external vlan have tag 4093, internal vlan have tag 4094
BIGIP 2 machine external vlan have tag 4094, internal vlan have tag 4093
Great tutorial.
Ranjit rakhi
Summary Steps:
-Both Devices
Self IPs - inside, outside etc
DNS
NTP
Create HA Vlan, self IP - dedicated ha vlan
Go to device - config sync - mention HA vlan - for confi sync between devices
Go to device - failover - mention HA vlan - port udp 1026 - for hello, device state etc
Go to device - mirroring - mention HA vlan - port tcp 1029-1055 for live connection mirroring
device A
device - device trust - peer device discovery - add peer device
adding peer device
-after this both in sync and active (No pools, vs sync yet)
create device groups
-name
-sync-failover - this is config sync with device failover
-add both devices
-network
-manual with incremental
sync config and test failover..
tmsh list net self-allow defaults