Forum Discussion
Felix888_164906
Aug 14, 2014Nimbostratus
I've got something improved, although I am still unable to ping from the host to the guest. But some other servers from the remote are able to ping the virtual servers in the guest. The solution is simply: Just use the self-IP of the guest as the gateway for the real servers in the vCMP guest. Isn't that simply? Previously I used the self-IP of the host as the gateway.
Now I am facing to problems:
we have the admin vlan in the vCMP host, say valn 2. This vlan2 needs to see all network and servers for admin purposes. The server in these vlan 2 connecting the Nexus has been configured to use the vCMP host self-IP as the gateway. I found this server cannot access to any real or virtual servers in the guest. Unless I add the static route in the server, basically like this:
route add (guest vlan network) mask 255.255.255.0 guest-self-ip
This way this vlan 2 server can ping the servers in the guest. Obviously I can not do this for hundreds servers in the future. Any suggest? there are still issues forwarding the traffic from ther host to the guest. As I am still unable to ping from the host to the guest.
2. the real servers in the guest is unable to access to the Internet. The servers are able to forward the internal traffic through the self ip from the guest to the host for all vlans except the Internet. But it won't forward the Internet traffic from the guest to the host. I have route setup to route all vlans through the address pool which contains all selfIP of the vCMP host (for routing to the next hop). I also setup the IP forward VS to forward all IP traffic.
But the server is unable to ping the Internet.
Please help!!