Forum Discussion
Network Failover
Can we Directly connect two F5 LAN ports for Network Fail over with HA Vlan.
Yes, and it's generally recommended to do so.
I'd even recommend to use two physical interfaces (as Aggregated Trunk) for HA, unless you plan to use all other 7 interfaces for something else. It would make sense to use that HA trunk interface for three things: Config Sync, Network fail-over, Traffic Mirror
32 Replies
Yes, and it's generally recommended to do so.
I'd even recommend to use two physical interfaces (as Aggregated Trunk) for HA, unless you plan to use all other 7 interfaces for something else. It would make sense to use that HA trunk interface for three things: Config Sync, Network fail-over, Traffic Mirror
- thanks for your reply kindly guide me If we have HA both from Hard Wire and Network configured and we have configured Vlan Failsafe, dose failover happens if we shut the Vlan of Active F5, however it can detect heartbeat on Hardwire,
- In normal circumstances HW and network failover together the HW failover takes precedence. However, in your case vlan failsafe has Reboot as the default action. So disabling this vlan should cause the active to reboot and failover to occur. That's my view anyway. Note, I wouldn't myself specify vlan failsafe in the HA vlan. Interested to hear other views on that.
- Your active appliance should reboot(or take another chosen action) 90 seconds after disabling a VLAN where the VLAN failsafe feature is enabled, regardless of hardwired failover that is in place. If you use VLAN failsafe feature, the HA VLAN itself doesn't have to be monitored. I do not see a good reason to enable VLAN failsafe feature on HA VLAN. Not to say that it's a best practice or anything, but my personal preference is to never use hardwired failover. It's great due to it's responsiveness, but it can only check the appliance's health on a very low level. I find the network failover feature reliable, and what's most important, it doesn't have any limitations (more on limitations in SOL article). Another option is to have both in place, hardwired failover as well as network failover, but I would rather keep things simple and stick to just one. You can read more on topic here: https://support.f5.com/kb/en-us/solutions/public/2000/300/sol2397.html
Yes, and it's generally recommended to do so.
I'd even recommend to use two physical interfaces (as Aggregated Trunk) for HA, unless you plan to use all other 7 interfaces for something else. It would make sense to use that HA trunk interface for three things: Config Sync, Network fail-over, Traffic Mirror
- thanks for your reply kindly guide me If we have HA both from Hard Wire and Network configured and we have configured Vlan Failsafe, dose failover happens if we shut the Vlan of Active F5, however it can detect heartbeat on Hardwire,
- In normal circumstances HW and network failover together the HW failover takes precedence. However, in your case vlan failsafe has Reboot as the default action. So disabling this vlan should cause the active to reboot and failover to occur. That's my view anyway. Note, I wouldn't myself specify vlan failsafe in the HA vlan. Interested to hear other views on that.
- Your active appliance should reboot(or take another chosen action) 90 seconds after disabling a VLAN where the VLAN failsafe feature is enabled, regardless of hardwired failover that is in place. If you use VLAN failsafe feature, the HA VLAN itself doesn't have to be monitored. I do not see a good reason to enable VLAN failsafe feature on HA VLAN. Not to say that it's a best practice or anything, but my personal preference is to never use hardwired failover. It's great due to it's responsiveness, but it can only check the appliance's health on a very low level. I find the network failover feature reliable, and what's most important, it doesn't have any limitations (more on limitations in SOL article). Another option is to have both in place, hardwired failover as well as network failover, but I would rather keep things simple and stick to just one. You can read more on topic here: https://support.f5.com/kb/en-us/solutions/public/2000/300/sol2397.html
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