Forum Discussion
High Availability
Hello,
If your both F5 instances on Hyper V will communicate via switch or Core switch, you need to have at least that L2 VLAN on the switch and it should be flowed till the HyperV. Lets say, you've dedicated network 192.168.1.0/24 for HA configuration. Then you can create L2 VLAN on Core switch/switch through which both F5s will communicate. And flow that L2 VLAN till the HyperV. Once this is done, if you configure HA using any IP addresses from above dedicated HA subnet, you should be able to ping HA IP addresses from each other.
You can use the other VLAN segment present in HyperV but you need to make sure that you are using IP address from that VLAN segment only. And VLAN connectivity is present/flowed till the HyperV so both instances can communicate with each other.
Hope it helps!
- puluckDec 10, 2020Cirrus
Thanks for your reply Mayur .I did that but seeing some weird problem. When both F5 on same Host HA VLAN can ping each other when both or on different host its having issue now . I have created L2 VLAN on my switches which connect host and allowed same VLAN on Port channel.
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