We have a two node cluster that originally was set to one subnet ending with 24 and 136. We migrated all our windows apps successfully. Now we have started migrating our CentOS apps. Those with 24 and 136 are working great. However one web app has a different ending 77. We've been able to ping the host using the new IP, but we are not able to ping the web app. We have 4 Vlan assignments within the host. We've assigned the 36 and 124 to one of the VMs. We tried doing this with the new IP but it didn't work, so now we are trying a direct IP connect between the application and the Internet. Any suggestions?
I'm just wondering if there is anyway of assigning a VLan# to a specific defined IP.
- 種類を変更済み Vincent HuModerator 2012年5月14日 5:59
Hope you're well. Virtual networks are described here
You assign VLAN#'s to interfaces, not to IP addresses. The first thing to verify would be whether or not you can ping the default gateway from the affected hosts (that's assigned to your VLAN77).
If the ping succeeds it's not likely an issue with your vlan/ip configuration on the VM or in Hyper-V (but perhaps another issue e.g. DNS/routing)
Let me know if you need any further clarification. If it's still not working, we may need further detail (IP addresses, VLANs, network overview etc).
We have a two node cluster that originally was set to one subnet ending with 24 and 136.
>> What did you mean by this? Did you an IP range such as 192.168.1.24 to 192.168.1.136?
By the way, please provide your network topology and networking settings in details, both on virtual machine and Hyper-V host machine. Thanks for your understanding.