Forum Discussion
smp_86112
Apr 15, 2011Cirrostratus
Virtual Server/Server IP Address Conflict
We encountered an unusual situation yesterday where a server in an internal LTM VLAN suddenly became inaccessible. The server became inaccessible because it had been rebooted and saw an IP address co...
hoolio
Apr 15, 2011Cirrostratus
Hi SMP,
I don't have exact answers for all of your questions, but...
If you already had a wildcard VS which allowed access to the server, there shouldn't be a need to have a more specific VS defined.
If you did want to allow access by original IP (without destination address translation) through LTM to that specific host, you can define a host VS on port 0 or a specific port with the destination address set to the original IP. You'd set the type to forwarding and ensure ARP and destination address translation are disabled. You'd then need to configure clients with a static ARP entry for that destination IP pointing to an LTM self IP. The key there is the ARP config on LTM and clients. You do not want LTM answering ARP broadcasts for the destination IP or you'll get IP conflicts. Clients would need to know that LTM will answer for the destination IP without getting an ARP response. They'd also need a route for the destination IP pointing to an LTM self IP.
I think it's simpler to either use a network forwarding virtual server or a one to one VS on a new IP pointing to a pool with a single member of the server address you want them to reach.
Aaron
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