Forum Discussion
cpatte7372_2378
Nimbostratus
Dec 18, 2015Unable to Communicate Web Console or Access Virtual Web Servers for BIG-IP LTM
Hello All,
My first posting here.
I'm practising BIG-IP LTM using the VE edition with vSphere Client on ESXi5.5. I'm following the CBT Nuggets. The video shows on how create a BIG-IP LTM la...
StephanManthey
Nacreous
Dec 20, 2015Hi Carlton,
a virtual server will respond to an ICMP echo request (as long as you are not disabling it in the virtual address properties).
So do self IPs. In both cases the ping will be answered for IPs bound to the inbound VLAN only. Thats why your external client cannot ping the internal self IP of 10.3.0.145.
As long as your virtual server is of type host (/32 address range) and has destination address translation enabled it will not be able to forward ICMP echo requests to your pool members. This can be done by using forwarding virtual servers only with ANY protocol enabled and using SNAT supporting ANY protocol as well (global setting).
In your environment the BIG-IP should be able to ping the real servers from its internal self IP i.e.:
10.3.0.145/8 <-> 10.2.0.11/8
Btw, I´m wondering about the network configuration as the IP ranges of management interface and internal network overlap. This cannot be configured (without using routing domains).
In case you are using /24 subnets you want to configure a route (network -> routes) to describe the next hop how to reach the internal servers.
ESX 5.5 should be fine generally. Your internal switches are configured accordingly?
Thanks, Stephan
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)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