Noelantogerorge commented on issue #7318:
URL: https://github.com/apache/cloudstack/issues/7318#issuecomment-1461522271
Please find my updates below
- ping works, from systemvm to kvm host (10.60.0.121) - **yes it works**
- ping does not work, from system vm to management server (10.60.0.120) -
**yes ping does not work**
- ping does not work, from system vm to other ips (10.60.0.1, 10.60.0.191,
8.8.8.8, etc) - **yes ping does not work**
From SystemVM
root@s-9-VM:~# 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
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UP group default qlen 1000
link/ether 0e:00:a9:fe:7e:e8 brd ff:ff:ff:ff:ff:ff
altname enp0s3
altname ens3
inet 169.254.126.232/16 brd 169.254.255.255 scope global eth0
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UP group default qlen 1000
link/ether 1e:00:3d:00:00:10 brd ff:ff:ff:ff:ff:ff
altname enp0s4
altname ens4
inet 10.60.0.210/24 brd 10.60.0.255 scope global eth1
valid_lft forever preferred_lft forever
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UP group default qlen 1000
link/ether 1e:00:d4:00:00:1b brd ff:ff:ff:ff:ff:ff
altname enp0s5
altname ens5
inet 10.60.0.190/24 brd 10.60.0.255 scope global eth2
valid_lft forever preferred_lft forever
root@s-9-VM:~# ip route
default via 10.60.0.1 dev eth2
8.8.8.8 via 10.60.0.1 dev eth1
10.60.0.0/24 dev eth1 proto kernel scope link src 10.60.0.210
10.60.0.0/24 dev eth2 proto kernel scope link src 10.60.0.190
169.254.0.0/16 dev eth0 proto kernel scope link src 169.254.126.232
I use virtual instance as KVM host..
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
