Forum Discussion
Unable to communicate with VIP in new external VLAN (dmz)
Adding 2nd DMZ VLAN, unable to ping Virtual Server in that new VLAN.
We are running F5 VE v13.0 , we have internal virtual servers and external (dmz vlan1) virtual servers. We have added a new vlan (dmz vlan2) in our dmz and would need to create a virtual Server and assign an IP from that ip range. The physical nic of our ESXi for external network is connected to a trunk port in our DMZ switch, that port is trunked for vlan1 and vlan2. We have created a new VIP with an IP in the new range of vlan2 , the member server is in than vlan2 and the status is green. From SSH , i can ping that server in vlan2 but not the new VIP in that same vlan.
Do i need to tag my vlan's on the interface connected to the dmz ? do i need to configure trunking ?
Appreciate your help.
- Simon_Blakely
Employee
You can either have a single untagged vlan associated with an interface, or the vlans need to be tagged.
I'd start with ensuring that the vlans are tagged on the interface. Ensure you have a non-floating and a floating self-ip on the vlan. Assign the floating self-ip to a traffic group, and ensure your VIP is also assigned the correct traffic-group.
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