Forum Discussion
NimbostratusNetwork routing from the VM guest to the VM host
Hello,
I've created many vlans, trunks, and associated the trunk to the vlans on the host.
I then created the vCMP guest, associated the some vlans to the guest in the deployment menu (bridged mgt)
I am able to access to the new guest and logged in and licensed all the modules and started configuration using the guided deployment wizard at startup.
Vlans are stating no interface is attached when assigning self ip's in wizard
Based on people's suggestion, in the wizard configuration, I setup a vlan for future routing to the external VLAN in the host from the guest`text`. So I used this ip as the default gateway, I have several vlan setup in the guest. But except the default network works, I can't route to any other vlan in the host. I did configure the routing entries and ip forward VS, no luck. Did I miss anything? Do we access to all vlans in the guest through a internal default gateway connected to the guest? Thanks!
6 Replies
- The_Bhattman
Hi Felix,
Did you assign interfaces from the vCMP host to the vCMP guests?
thanks,
Felix888_164906Thanks and sorry for the late reply. There is only option to assign the VLAN from Host to vCMP thoguh. I did that. However now my problem is I cannot ping the seflIP from the guest to the host or vice versa. I think they should be pingable ... Also if I setup the virtual server in the guest, it can be reachable by the host. TCPDUMP tells me the host is unable to detect the arp for the virtual server in the guest. Any idea?
- Felix888_164906
sorry for the typo, there we go: Thanks and sorry for the late reply. There is only option to assign the VLAN from Host to vCMP guest thoguh. I did that. However now my problem is I cannot ping the seflIP from the guest to the host or vice versa. I think they should be pingable ... Also if I setup the virtual server in the guest, it cannot be reachable by the host. TCPDUMP tells me the host is unable to detect the arp for the virtual server in the guest. Any idea?
- Felix888_164906
below is the scenario where I ping from the host to the guest, ping 10.0.2.3 (self ip for the guest) the tcpdump on the guest shows: 12:40:51.799490 arp who-has 10.0.2.3 tell 10.0.2.1 12:40:51.799505 arp reply 10.0.2.3 is-at 00:23:e9:89:04:45 12:40:52.799103 arp who-has 10.0.2.3 tell 10.0.2.1 12:40:52.799132 arp reply 10.0.2.3 is-at 00:23:e9:89:04:45 ping 10.0.20.31 (ip address of the virtual server in the guest): the tcpdump on the guest shows: 12:37:07.994748 arp who-has 10.0.20.31 tell 10.0.20.1 12:37:07.994782 arp reply 10.0.20.31 is-at 00:23:e9:89:04:4b 12:37:08.994823 arp who-has 10.0.20.31 tell 10.0.20.1 12:37:08.994835 arp reply 10.0.20.31 is-at 00:23:e9:89:04:4b Weird, 'cause it seems to reply back with the arp, but the host is not aware of this.... - Felix888_164906
the setup is this case is pretty straight forward: the self IPs have been configured on both Host and Guest, but they cannot ping to each other.
- Felix888_164906
I'm still stuck on this problem. I have done a test: If I create the vlan interface (on the same vlan id as the virtual server) on the core switch which trunked with F5 LTM, I am able to ping the virtual server. This means the arp for the virtual server (on vCMP guest) is unable to be detected by the vCMP host. Any help would be great. Thanks!
