Forum Discussion
one-arm scenario, external network?
- May 19, 2021
Hi Shurik,
>> Is there a need to configure external network?
No, there is no need to configure the external network. As long as the HA comms has a vlan to work over, it is happy.
I suspect you are referring to the "external", "internal" and "ha" vlans that get automatically created when you run through the wizard? Those are provided to help you get all the basics ready, but there is no specific requirement to follow them. In the wizard, you can also skip this section and manually create any vlans you want to use in your environment.
Once you have then created all your vlans and self IP's, you can configure the ones that HA needs to use via Device Management ›› Devices ›› <select your device>
Saying that, if you have configured them, and don't want to use them, also no problem. If preferred, you can delete them again after the wizard is complete via Network - Vlans.
Best practise is to have a dedicated HA vlan to keep production traffic and HA traffic separate, but even that is not a hard requirement - you can also reuse your internal vlan (or any other vlan) for HA traffic.
Hope this helps.
Hi Shurik,
>> Is there a need to configure external network?
No, there is no need to configure the external network. As long as the HA comms has a vlan to work over, it is happy.
I suspect you are referring to the "external", "internal" and "ha" vlans that get automatically created when you run through the wizard? Those are provided to help you get all the basics ready, but there is no specific requirement to follow them. In the wizard, you can also skip this section and manually create any vlans you want to use in your environment.
Once you have then created all your vlans and self IP's, you can configure the ones that HA needs to use via Device Management ›› Devices ›› <select your device>
Saying that, if you have configured them, and don't want to use them, also no problem. If preferred, you can delete them again after the wizard is complete via Network - Vlans.
Best practise is to have a dedicated HA vlan to keep production traffic and HA traffic separate, but even that is not a hard requirement - you can also reuse your internal vlan (or any other vlan) for HA traffic.
Hope this helps.
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