Forum Discussion
genseek_32178
Nimbostratus
Jan 16, 2012Virtual Server Cmds
Hi,
In our environment, we have Virtual Servers configured in the following way,
virtual apps_critical_BTK
{
pool bzt_pool destination 200.36.134.131:https
ip protocol tcp
persist persist_default
profiles tcp_default {}
vlans {
c_10.201.20.25_27
c_200.36.134.128_26
c_16.25.42.36_26
} enable
I want to understand, why, once the virutal server has been defined, the following 3 vlans
c_10.201.20.25_27
c_200.36.134.128_26
c_16.25.42.36_26
have been enabled or mapped to the virtual server?
what is the purpose? What if i remove the specific VLAN on which the VIP is sitting?
Help would to understand this would...appreciated.
- hoolio
Cirrostratus
Can you try enabling the virtual server on all VLANs and retest? If that works then I'd guess the client wasn't on one of the VLANs that was enabled. If that doesn't work, then like Nitass suggested, try opening a case as something weird is going on. - genseek_32178
Nimbostratus
Ok, i will try opening a support case. - hoolio
Cirrostratus
When you're testing this, make sure in the GUI that it says VLAN and Tunnel Traffic: All VLANs and Tunnels. If you select Enabled On but don't select any VLANs then the VS won't accept connections.v11.1 ltm virtual ltm_ve_1_http_vs { destination 10.1.0.113:http ip-protocol tcp mask 255.255.255.255 profiles { http { } tcp { } } rules { name_to_ipv6_geo_rule } snat automap vlans-enabled }
- genseek_32178
Nimbostratus
1)..........By VIP do you mean virtual server IP address (ie, virtual address)?
Recent Discussions
Related Content
DevCentral Quicklinks
* 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
Discover DevCentral Connects