Hello Wei. Thank you for your suggestion. I moved the second KVM nic to a
different subnet and reprovisioned the Zone with new public and guest IPs.
However, the system VMs still cannot access the network.
Is there any sysctl settings that could be blocking this? The KVM installation
guide and CloudStack guide don’t mention any changes to sysctl settings.
root@s-6-VM:~# /usr/local/cloud/systemvm/ssvm-check.sh
================================================
First DNS server is 172.18.5.71
PING 172.18.5.71 (172.18.5.71): 56 data bytes
--- 172.18.5.71 ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss
WARNING: cannot ping DNS server
route follows
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 172.18.8.1 0.0.0.0 UG 0 0 0 eth2
10.120.120.0 0.0.0.0 255.255.252.0 U 0 0 0 eth1
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
172.18.5.71 10.120.120.1 255.255.255.255 UGH 0 0 0 eth1
172.18.8.0 0.0.0.0 255.255.252.0 U 0 0 0 eth2
================================================
ERROR: DNS not resolving cloudstack.apache.org
resolv.conf follows
nameserver 172.18.5.71
nameserver 172.18.5.71
nameserver 172.18.5.72
root@s-6-VM:~#
root@s-6-VM:~# ip addr
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:9f:a2 brd ff:ff:ff:ff:ff:ff
altname enp0s3
altname ens3
inet 169.254.159.162/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:b8:00:00:05 brd ff:ff:ff:ff:ff:ff
altname enp0s4
altname ens4
inet 10.120.123.163/22 brd 10.120.123.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:39:00:00:07 brd ff:ff:ff:ff:ff:ff
altname enp0s5
altname ens5
inet 172.18.10.221/22 brd 172.18.11.255 scope global eth2
valid_lft forever preferred_lft forever
root@s-6-VM:~#
From: Wei ZHOU <[email protected]>
Sent: Tuesday, May 2, 2023 1:29 PM
To: [email protected]
Subject: [EXTERNAL] Re: SSVM agent state greyed out in web UI
CAUTION: This email originated from outside of the organization. Do not follow
guidance, click links, or open attachments unless you recognize the sender and
know the content is safe.
Hi,
In ssvm, the eth1 has ip
10.120.123.166/22<http://10.120.123.166/22>, eth2 has ip
10.120.123.160/22<http://10.120.123.160/22>
They are in same subnet, but.. it seems eth1 is on cloudbr0 and eth2 is on
cloudbr1.
I think they should use ips in different subnet, or on same bridge (network
traffic label)
-Wei
Disclaimer
The information contained in this communication from the sender is
confidential. It is intended solely for use by the recipient and others
authorized to receive it. If you are not the recipient, you are hereby notified
that any disclosure, copying, distribution or taking action in relation of the
contents of this information is strictly prohibited and may be unlawful.
This email has been scanned for viruses and malware, and may have been
automatically archived by Mimecast Ltd, an innovator in Software as a Service
(SaaS) for business. Providing a safer and more useful place for your human
generated data. Specializing in; Security, archiving and compliance. To find
out more visit the Mimecast website.
