-
Notifications
You must be signed in to change notification settings - Fork 1.1k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Virtual machine on different hosts but in same isolated network not able to communicate (can't ping each other). #9027
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! |
@akshaybachhav can you check iptables/firewall rules in the VM? Can you ping the VR from the VMs? |
+1 |
Thanks for your help. We checked the iptables/firewall rules and found below status. It is allowing all traffic by default. tcpdump command on vm which is on same host as on which VR is present gives below results: 04:54:50.697249 IP ubuntu-dev-vm-1.cs2cloud.internal.ssh > 10.0.1.10.42550: Flags [P.], seq 7368836:7369064, ack 4249, win 1002, options [nop,nop,TS val 718803065 ecr 1773071291], length 228 I am able to ping the VR from the VM which is on same host. But if I ping from VM to VR which is not on same host then it is not working. |
@akshaybachhav just to confirm, are both vms configured to get dhcp IPs from the VR ? or as static IPs ? |
both vms get dhcp ips from vr no static ip set in vms on both kvm machine status of ufw is |
Have you disabled apparmour on them, what guide or steps of installation if any did you follow @akshaybachhav |
i followed the tutorial from official documentation from apache cloudstack: this is my netplan configuration file. |
i followed the tutorial https://rohityadav.cloud/blog/cloudstack-kvm/ and done exactly same setup. |
@akshaybachhav
|
we have done setup of cloudstack using mini pc , asus chromebox and acer chromebox which has single nic. |
If you are testing communication between 2 VMs on the SAME network, but on different KVM hosts, then you should check:
The problem you have sounds like (99.999%) to be an underlying infrastructure/configuration issue |
It looks we forgot to ask you
|
@weizhouapache We are using We haven't specified any VLAN/VNI while creating the zone. @andrijapanicsb We are only able ssh the vm which is same host as of vr and the other vm which is on different host is not reachable. And I will check about TRUNK mode |
Hi @dineshjchoudhary @akshaybachhav Did you guys managed to resolve this? We have Compute 6 Nodes and our 6th Node is having this same issue. Using:
We have checked:
But in our situation, what we noticed:
|
Hi All, We managed to resolve our issue. Upon further checking, we found out that the VXLAN in Host 6 was down, while other VXLANs were up and running fine. This would explain why:
@dineshjchoudhary @akshaybachhav , maybe you guys should try checking this out too if the root cause is the same. When we manually bring back the VXLAN, it works. What we dont know now is, why the VXLAN suddenly went down. Ill probably raise another ticket for this. |
Interesting. When you say VXLAN interface, is it the physical interface (underlay) or the VTEP attached to the bridge? |
Do you use multicast group? If yes, can you check if the setting impacts you? https://docs.cloudstack.apache.org/projects/archived-cloudstack-getting-started/en/latest/networking/vxlan.html#important-note-on-max-number-of-multicast-groups-and-thus-vxlan-intefaces |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
ISSUE TYPE
COMPONENT NAME
CLOUDSTACK VERSION
CONFIGURATION
OS / ENVIRONMENT
SUMMARY
EXPECTED RESULTS
ACTUAL RESULTS
Screenshots
virtual router is running on the host 1 machine.
when we run diagnostics to ping from virtual router to the VM(10.1.1.158) the says network unreachable.
On one host machine I have created the vm and that also have virtual router, for this case the router is able to ping the same VM(10.1.1.96).
The text was updated successfully, but these errors were encountered: