Cisco Support Community
Community Member

VIP forward a request to a real server using the same host name but different IP address



Need some guidance in regard to the following:

Can a VIP forward a request to a real server using the same host name but different IP address?

For example, using IP forwards to real server


Any help as always will greatly be appreciated.





Cisco Employee

Hi Raman,I didn't get the

Hi Raman,

I didn't get the question here. Your URL will resolve to VIP and if real server name is, then it doesn't matter. The request would be forwarded to the real server



Note: Please mark answers if they are helpful.

Community Member

Wow, thanks for the quick

Wow, thanks for the quick response Kanwal!

I am asking my customer some additional questions. I think they may have some type of reverse proxy setup and it's causing problems. Not necessary with the ACE, but for the return traffic maybe.


I will update you with my findings.


Thanks again for your help.


Community Member

Hi Raman,if you are using

Hi Raman,

if you are using Nexus family product then you can now host the VIP without any ACE help.

You might want to check out this new product called ITD.

Simple and faster solution:

ITD provides :

  1. ASIC based multi-terabit/s L3/L4 load-balancing at line-rate
  2. No service module or external L3/L4 load-balancer needed. Every N7k port can be used as load-balancer.
  3. Redirect line-rate traffic to any devices, for example web cache engines, Web Accelerator Engines (WAE), video-caches, etc.
  4. Capability to create clusters of devices, for example, Firewalls, Intrusion Prevention System (IPS), or Web Application Firewall (WAF), Hadoop cluster
  5. IP-stickiness
  6. Resilient (like resilient ECMP)
  7. VIP based L4 load-balancing
  8. NAT (available for EFT/PoC). Allows non-DSR deployments.
  9. Weighted load-balancing
  10. Load-balances to large number of devices/servers
  11. ACL along with redirection and load balancing simultaneously.
  12. Bi-directional flow-coherency. Traffic from A-->B and B-->A goes to same node.
  13. Order of magnitude OPEX savings : reduction in configuration, and ease of deployment
  14. Order of magnitude CAPEX savings : Wiring, Power, Rackspace and Cost savings
  15. The servers/appliances don’t have to be directly connected to N7k
  16. Monitoring the health of servers/appliances.
  17. N + M redundancy.
  18. Automatic failure handling of servers/appliances.
  19. VRF support, vPC support, VDC support
  20. Supported on both Nexus 7000 and Nexus 7700 series.
  21. Supports both IPv4 and IPv6
  22. N5k / N6k support : coming soon


At a glance

ITD config guide

Email Query or

CreatePlease to create content