GitHub user fnavidan added a comment to the discussion: High Latency Between
Two VMs In a L2 Private Guest Network
Here are routing and network info:
[root@da1 ~]# ip route
default via 149.50.127.129 dev ens3 proto dhcp src 149.50.127.163 metric 100
10.0.0.0/24 dev ens9 proto kernel scope link src 10.0.0.1 metric 101
149.50.127.128/26 dev ens3 proto kernel scope link src 149.50.127.163 metric 100
[root@da1 ~]# traceroute -I ens9 10.0.0.2
ens9: Name or service not known
Cannot handle "host" cmdline arg `ens9' on position 1 (argc 2)
[root@da1 ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP
group default qlen 1000
link/ether 1e:01:2c:00:02:d1 brd ff:ff:ff:ff:ff:ff
altname enp0s3
inet 149.50.127.163/26 brd 149.50.127.191 scope global noprefixroute ens3
valid_lft forever preferred_lft forever
inet6 fe80::1c01:2cff:fe00:2d1/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: ens9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP
group default qlen 1000
link/ether 02:01:00:d4:00:01 brd ff:ff:ff:ff:ff:ff
altname enp0s9
inet 10.0.0.1/24 brd 10.0.0.255 scope global noprefixroute ens9
valid_lft forever preferred_lft forever
inet6 fe80::acc7:f278:d355:ff8f/64 scope link noprefixroute
valid_lft forever preferred_lft forever
Here are 4 samples of traceroute that shows variance in icmp tests:
[root@da1 ~]# traceroute -I -i ens9 10.0.0.2
traceroute to 10.0.0.2 (10.0.0.2), 30 hops max, 60 byte packets
1 da-node2 (10.0.0.2) 1.053 ms * *
[root@da1 ~]# traceroute -I -i ens9 10.0.0.2
traceroute to 10.0.0.2 (10.0.0.2), 30 hops max, 60 byte packets
1 da-node2 (10.0.0.2) 7.838 ms 8.433 ms 8.229 ms
[root@da1 ~]# traceroute -I -i ens9 10.0.0.2
traceroute to 10.0.0.2 (10.0.0.2), 30 hops max, 60 byte packets
1 da-node2 (10.0.0.2) 0.961 ms * *
[root@da1 ~]# traceroute -I -i ens9 10.0.0.2
traceroute to 10.0.0.2 (10.0.0.2), 30 hops max, 60 byte packets
1 da-node2 (10.0.0.2) 16.925 ms 16.459 ms 13.767 ms
And this is exact route path:
[root@da1 ~]# ip route get 10.0.0.2 from 10.0.0.1
10.0.0.2 from 10.0.0.1 dev ens9 uid 0
cache
And this ping results from exactly same private interface:
[root@da1 ~]# ping -I ens9 -c 100 10.0.0.2
PING 10.0.0.2 (10.0.0.2) from 10.0.0.1 ens9: 56(84) bytes of data.
...
100 packets transmitted, 100 received, 0% packet loss, time 100048ms
rtt min/avg/max/mdev = 0.268/2.195/21.840/2.881 ms
Interestingly even when I ping a VM's public IP inside its own KVM host, I get
same high ping result.
GitHub link:
https://github.com/apache/cloudstack/discussions/14380#discussioncomment-18854293
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
