Re: Quickstart question - Network issues
Unable to allocate vnet as a part of network Ntwk[210|Guest|8] Check you Guest traffic to see if you assigned a vlan range from which ACS will provision VLAN/networks (each tenant network = separate VLAN) On Mon, 31 May 2021 at 08:11, Jeremy Hansen wrote: > Thank you for the response. I got much further. All my issues seem > networking related. Everything is up right now and I see the template for > CentOS 5.5 as an offering. > > My Cloudstack host is on 192.168.10.35. My System VMs is configured as > such: > > > > At this point, I’m trying to understand how to configured my Guest > networks. Ideally my guest vm’s would just use my external DHCP server to > allocate an IP address but I’m not having much luck finding documentation > on how to properly do that. I also see posts saying external DHCP servers > aren’t supported because Cloudstack needs to be aware of the guest’s IP for > a number of reasons. > > So my question becomes, what type and how should I configure my guest > network. Can I use IPs on the same subnet that my Cloudstack host is > sitting on? If I can’t use DHCP directly, I can specify a range that is > not in use by my external DHCP server so IPs will still end up on the > public network and I can access the VMs on that IP directly. > > Interfaces on my Cloudstack host: > > cloud0: flags=4163 mtu 1500 > inet 169.254.0.1 netmask 255.255.0.0 broadcast 0.0.0.0 > inet6 fe80::8c30:6dff:fe87:ed32 prefixlen 64 scopeid 0x20 > ether fe:00:a9:fe:91:b4 txqueuelen 1000 (Ethernet) > RX packets 440 bytes 80558 (78.6 KiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 539 bytes 96150 (93.8 KiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > cloudbr0: flags=4163 mtu 1500 > inet 192.168.10.35 netmask 255.255.255.0 broadcast 192.168.10.255 > inet6 fe80::4a2:a9ff:fecf:819 prefixlen 64 scopeid 0x20 > ether b4:b5:2f:db:a2:9b txqueuelen 1000 (Ethernet) > RX packets 1203750 bytes 3227151094 (3.0 GiB) > RX errors 0 dropped 5 overruns 0 frame 0 > TX packets 498851 bytes 2710603584 (2.5 GiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > eno1: flags=4163 mtu 1500 > ether b4:b5:2f:db:a2:9b txqueuelen 1000 (Ethernet) > RX packets 4650048 bytes 4876148565 (4.5 GiB) > RX errors 0 dropped 622 overruns 0 frame 0 > TX packets 3955493 bytes 5163648882 (4.8 GiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > device interrupt 20 memory 0xf7c0-f7c2 > > lo: flags=73 mtu 65536 > inet 127.0.0.1 netmask 255.0.0.0 > inet6 ::1 prefixlen 128 scopeid 0x10 > loop txqueuelen 1000 (Local Loopback) > RX packets 2322050 bytes 504114946 (480.7 MiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 2322050 bytes 504114946 (480.7 MiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > vnet0: flags=4163 mtu 1500 > inet6 fe80::fc00:a9ff:fefe:91b4 prefixlen 64 scopeid 0x20 > ether fe:00:a9:fe:91:b4 txqueuelen 1000 (Ethernet) > RX packets 50 bytes 9384 (9.1 KiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 98 bytes 15290 (14.9 KiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > vnet1: flags=4163 mtu 1500 > inet6 fe80::fc00:7cff:fe00:5 prefixlen 64 scopeid 0x20 > ether fe:00:7c:00:00:05 txqueuelen 1000 (Ethernet) > RX packets 15707 bytes 2225323 (2.1 MiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 127124 bytes 19795223 (18.8 MiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > vnet2: flags=4163 mtu 1500 > inet6 fe80::fc00:d8ff:fe00:7 prefixlen 64 scopeid 0x20 > ether fe:00:d8:00:00:07 txqueuelen 1000 (Ethernet) > RX packets 808 bytes 57456 (56.1 KiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 109119 bytes 17746092 (16.9 MiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > vnet3: flags=4163 mtu 1500 > inet6 fe80::fc00:a9ff:fefe:b767 prefixlen 64 scopeid 0x20 > ether fe:00:a9:fe:b7:67 txqueuelen 1000 (Ethernet) > RX packets 46 bytes 9168 (8.9 KiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 95 bytes 15068 (14.7 KiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > vnet4: flags=4163 mtu 1500 > inet6 fe80::fc00:c2ff:fe00:6 prefixlen 64 scopeid 0x20 > ether fe:00:c2:00:00:06 txqueuelen 1000 (Ethernet) > RX packets 144923 bytes 2256458775 (2.1 GiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 822253 bytes 1009838617 (963.0 MiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions
Re: Quickstart question - Network issues
I think I actually figured it out by defining fw and port forwarding rules. I can now ssh in to the launched vm. Is there a way to define a default set of rules that gets applied to new instances? Thanks > On May 31, 2021, at 6:42 AM, Jeremy Hansen wrote: > > 192.168.10.0/24 is my public network, so I expected to be able to ping > 192.168.10.22, which is the public IP that was assigned in this case. I did > choose isolated network. How would I go about allowing traffic for those > services? Or is there a better choice of network type? Shared? > > Thank you for your help > >> On May 31, 2021, at 6:34 AM, Nicolas Vazquez >> wrote: >> >> Hi Jeremy, >> >> This will depend on the type of network you are deploying your VM. If it is >> deployed on an isolated network, then you need to allow the traffic for >> those services to access externally. However, VMs deployed on the same >> network will be able accessible >> >> >> Regards, >> >> Nicolas Vazquez >> >> >> From: Jeremy Hansen >> Sent: Monday, May 31, 2021 9:09 AM >> To: users@cloudstack.apache.org >> Subject: Re: Quickstart question - Network issues >> >> I picked an arbitrary vlan range of 10-20 and defined this in my physical >> network setting in the zone. This allowed me to launch a vm guest, but I >> can’t ping its public interface. >> >> >> I would expect at this point I would be able to ping the public interface, >> ssh in, etc. >> >> Thanks >> >> >> >> >>>> On May 31, 2021, at 4:30 AM, Jeremy Hansen wrote: >>> >>> Thank you. This vlan range only applies to the network between the vm >>> guest and the vm host? Does this vlan range need to exist on my public >>> net? The vlan stuff did confuse me a bit and I believe on my latest try, I >>> didn’t define one. >>> >>> -jeremy >>> >>>>> On May 31, 2021, at 4:14 AM, Nicolas Vazquez >>>>> wrote: >>>> Hi Jeremy, >>>> Can you please check if you have a Vlan range defined for your guest >>>> physical network? You can check under Infrastructure -> Zone -> Physical >>>> Network -> Guest. In case the Vlan range is not defined you can update the >>>> guest physical network's VLAN/VNI to the format: VLAN_START-VLAN_END >>>> Regards, >>>> Nicolas Vazquez >>>> >>>> From: Jeremy Hansen >>>> Sent: Monday, May 31, 2021 3:11 AM >>>> To: users@cloudstack.apache.org >>>> Subject: Re: Quickstart question - Network issues >>>> Thank you for the response. I got much further. All my issues seem >>>> networking related. Everything is up right now and I see the template for >>>> CentOS 5.5 as an offering. >>>> My Cloudstack host is on 192.168.10.35. My System VMs is configured as >>>> such: >>>> [cid:D47FD2E4-F159-4778-973E-F96505D3ADD6] >>>> At this point, I’m trying to understand how to configured my Guest >>>> networks. Ideally my guest vm’s would just use my external DHCP server to >>>> allocate an IP address but I’m not having much luck finding documentation >>>> on how to properly do that. I also see posts saying external DHCP servers >>>> aren’t supported because Cloudstack needs to be aware of the guest’s IP >>>> for a number of reasons. >>>> So my question becomes, what type and how should I configure my guest >>>> network. Can I use IPs on the same subnet that my Cloudstack host is >>>> sitting on? If I can’t use DHCP directly, I can specify a range that is >>>> not in use by my external DHCP server so IPs will still end up on the >>>> public network and I can access the VMs on that IP directly. >>>> Interfaces on my Cloudstack host: >>>> cloud0: flags=4163 mtu 1500 >>>> inet 169.254.0.1 netmask 255.255.0.0 broadcast 0.0.0.0 >>>> inet6 fe80::8c30:6dff:fe87:ed32 prefixlen 64 scopeid 0x20 >>>> ether fe:00:a9:fe:91:b4 txqueuelen 1000 (Ethernet) >>>> RX packets 440 bytes 80558 (78.6 KiB) >>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>> TX packets 539 bytes 96150 (93.8 KiB) >>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>> cloudbr0: flags=4163 mtu 1500 >>>> inet 192.168.10.35 netmask 255.255.255.0 broadcast 1
Re: Quickstart question - Network issues
192.168.10.0/24 is my public network, so I expected to be able to ping 192.168.10.22, which is the public IP that was assigned in this case. I did choose isolated network. How would I go about allowing traffic for those services? Or is there a better choice of network type? Shared? Thank you for your help > On May 31, 2021, at 6:34 AM, Nicolas Vazquez > wrote: > > Hi Jeremy, > > This will depend on the type of network you are deploying your VM. If it is > deployed on an isolated network, then you need to allow the traffic for those > services to access externally. However, VMs deployed on the same network will > be able accessible > > > Regards, > > Nicolas Vazquez > > > From: Jeremy Hansen > Sent: Monday, May 31, 2021 9:09 AM > To: users@cloudstack.apache.org > Subject: Re: Quickstart question - Network issues > > I picked an arbitrary vlan range of 10-20 and defined this in my physical > network setting in the zone. This allowed me to launch a vm guest, but I > can’t ping its public interface. > > > I would expect at this point I would be able to ping the public interface, > ssh in, etc. > > Thanks > > > > >> On May 31, 2021, at 4:30 AM, Jeremy Hansen wrote: >> >> Thank you. This vlan range only applies to the network between the vm guest >> and the vm host? Does this vlan range need to exist on my public net? The >> vlan stuff did confuse me a bit and I believe on my latest try, I didn’t >> define one. >> >> -jeremy >> >>>> On May 31, 2021, at 4:14 AM, Nicolas Vazquez >>>> wrote: >>> Hi Jeremy, >>> Can you please check if you have a Vlan range defined for your guest >>> physical network? You can check under Infrastructure -> Zone -> Physical >>> Network -> Guest. In case the Vlan range is not defined you can update the >>> guest physical network's VLAN/VNI to the format: VLAN_START-VLAN_END >>> Regards, >>> Nicolas Vazquez >>> >>> From: Jeremy Hansen >>> Sent: Monday, May 31, 2021 3:11 AM >>> To: users@cloudstack.apache.org >>> Subject: Re: Quickstart question - Network issues >>> Thank you for the response. I got much further. All my issues seem >>> networking related. Everything is up right now and I see the template for >>> CentOS 5.5 as an offering. >>> My Cloudstack host is on 192.168.10.35. My System VMs is configured as >>> such: >>> [cid:D47FD2E4-F159-4778-973E-F96505D3ADD6] >>> At this point, I’m trying to understand how to configured my Guest >>> networks. Ideally my guest vm’s would just use my external DHCP server to >>> allocate an IP address but I’m not having much luck finding documentation >>> on how to properly do that. I also see posts saying external DHCP servers >>> aren’t supported because Cloudstack needs to be aware of the guest’s IP for >>> a number of reasons. >>> So my question becomes, what type and how should I configure my guest >>> network. Can I use IPs on the same subnet that my Cloudstack host is >>> sitting on? If I can’t use DHCP directly, I can specify a range that is >>> not in use by my external DHCP server so IPs will still end up on the >>> public network and I can access the VMs on that IP directly. >>> Interfaces on my Cloudstack host: >>> cloud0: flags=4163 mtu 1500 >>>inet 169.254.0.1 netmask 255.255.0.0 broadcast 0.0.0.0 >>>inet6 fe80::8c30:6dff:fe87:ed32 prefixlen 64 scopeid 0x20 >>>ether fe:00:a9:fe:91:b4 txqueuelen 1000 (Ethernet) >>>RX packets 440 bytes 80558 (78.6 KiB) >>>RX errors 0 dropped 0 overruns 0 frame 0 >>>TX packets 539 bytes 96150 (93.8 KiB) >>>TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>> cloudbr0: flags=4163 mtu 1500 >>>inet 192.168.10.35 netmask 255.255.255.0 broadcast 192.168.10.255 >>>inet6 fe80::4a2:a9ff:fecf:819 prefixlen 64 scopeid 0x20 >>>ether b4:b5:2f:db:a2:9b txqueuelen 1000 (Ethernet) >>>RX packets 1203750 bytes 3227151094 (3.0 GiB) >>>RX errors 0 dropped 5 overruns 0 frame 0 >>>TX packets 498851 bytes 2710603584 (2.5 GiB) >>>TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>> eno1: flags=4163 mtu 1500 >>>ether b4:b5:2f:db:a2:9b txqueuelen 1000 (Ethernet) >>>RX packets 4650048 bytes 4876148565 (4.5 GiB) >>>RX errors 0 dropped 622 overruns 0 fra
Re: Quickstart question - Network issues
Hi Jeremy, This will depend on the type of network you are deploying your VM. If it is deployed on an isolated network, then you need to allow the traffic for those services to access externally. However, VMs deployed on the same network will be able accessible Regards, Nicolas Vazquez From: Jeremy Hansen Sent: Monday, May 31, 2021 9:09 AM To: users@cloudstack.apache.org Subject: Re: Quickstart question - Network issues I picked an arbitrary vlan range of 10-20 and defined this in my physical network setting in the zone. This allowed me to launch a vm guest, but I can’t ping its public interface. I would expect at this point I would be able to ping the public interface, ssh in, etc. Thanks > On May 31, 2021, at 4:30 AM, Jeremy Hansen wrote: > > Thank you. This vlan range only applies to the network between the vm guest > and the vm host? Does this vlan range need to exist on my public net? The > vlan stuff did confuse me a bit and I believe on my latest try, I didn’t > define one. > > -jeremy > >> On May 31, 2021, at 4:14 AM, Nicolas Vazquez >> wrote: >> Hi Jeremy, >> Can you please check if you have a Vlan range defined for your guest >> physical network? You can check under Infrastructure -> Zone -> Physical >> Network -> Guest. In case the Vlan range is not defined you can update the >> guest physical network's VLAN/VNI to the format: VLAN_START-VLAN_END >> Regards, >> Nicolas Vazquez >> >> From: Jeremy Hansen >> Sent: Monday, May 31, 2021 3:11 AM >> To: users@cloudstack.apache.org >> Subject: Re: Quickstart question - Network issues >> Thank you for the response. I got much further. All my issues seem >> networking related. Everything is up right now and I see the template for >> CentOS 5.5 as an offering. >> My Cloudstack host is on 192.168.10.35. My System VMs is configured as such: >> [cid:D47FD2E4-F159-4778-973E-F96505D3ADD6] >> At this point, I’m trying to understand how to configured my Guest networks. >> Ideally my guest vm’s would just use my external DHCP server to allocate an >> IP address but I’m not having much luck finding documentation on how to >> properly do that. I also see posts saying external DHCP servers aren’t >> supported because Cloudstack needs to be aware of the guest’s IP for a >> number of reasons. >> So my question becomes, what type and how should I configure my guest >> network. Can I use IPs on the same subnet that my Cloudstack host is >> sitting on? If I can’t use DHCP directly, I can specify a range that is not >> in use by my external DHCP server so IPs will still end up on the public >> network and I can access the VMs on that IP directly. >> Interfaces on my Cloudstack host: >> cloud0: flags=4163 mtu 1500 >> inet 169.254.0.1 netmask 255.255.0.0 broadcast 0.0.0.0 >> inet6 fe80::8c30:6dff:fe87:ed32 prefixlen 64 scopeid 0x20 >> ether fe:00:a9:fe:91:b4 txqueuelen 1000 (Ethernet) >> RX packets 440 bytes 80558 (78.6 KiB) >> RX errors 0 dropped 0 overruns 0 frame 0 >> TX packets 539 bytes 96150 (93.8 KiB) >> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >> cloudbr0: flags=4163 mtu 1500 >> inet 192.168.10.35 netmask 255.255.255.0 broadcast 192.168.10.255 >> inet6 fe80::4a2:a9ff:fecf:819 prefixlen 64 scopeid 0x20 >> ether b4:b5:2f:db:a2:9b txqueuelen 1000 (Ethernet) >> RX packets 1203750 bytes 3227151094 (3.0 GiB) >> RX errors 0 dropped 5 overruns 0 frame 0 >> TX packets 498851 bytes 2710603584 (2.5 GiB) >> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >> eno1: flags=4163 mtu 1500 >> ether b4:b5:2f:db:a2:9b txqueuelen 1000 (Ethernet) >> RX packets 4650048 bytes 4876148565 (4.5 GiB) >> RX errors 0 dropped 622 overruns 0 frame 0 >> TX packets 3955493 bytes 5163648882 (4.8 GiB) >> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >> device interrupt 20 memory 0xf7c0-f7c2 >> lo: flags=73 mtu 65536 >> inet 127.0.0.1 netmask 255.0.0.0 >> inet6 ::1 prefixlen 128 scopeid 0x10 >> loop txqueuelen 1000 (Local Loopback) >> RX packets 2322050 bytes 504114946 (480.7 MiB) >> RX errors 0 dropped 0 overruns 0 frame 0 >> TX packets 2322050 bytes 504114946 (480.7 MiB) >> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >> vnet0: flags=4163 mtu 1500 >> inet6 fe80::fc00:a9ff:fefe:91b4 prefixlen 64 scopeid 0x20 >> ether fe:00:a9:fe:91:b4 txque
Re: Quickstart question - Network issues
I picked an arbitrary vlan range of 10-20 and defined this in my physical network setting in the zone. This allowed me to launch a vm guest, but I can’t ping its public interface. I would expect at this point I would be able to ping the public interface, ssh in, etc. Thanks > On May 31, 2021, at 4:30 AM, Jeremy Hansen wrote: > > Thank you. This vlan range only applies to the network between the vm guest > and the vm host? Does this vlan range need to exist on my public net? The > vlan stuff did confuse me a bit and I believe on my latest try, I didn’t > define one. > > -jeremy > >> On May 31, 2021, at 4:14 AM, Nicolas Vazquez >> wrote: >> Hi Jeremy, >> Can you please check if you have a Vlan range defined for your guest >> physical network? You can check under Infrastructure -> Zone -> Physical >> Network -> Guest. In case the Vlan range is not defined you can update the >> guest physical network's VLAN/VNI to the format: VLAN_START-VLAN_END >> Regards, >> Nicolas Vazquez >> >> From: Jeremy Hansen >> Sent: Monday, May 31, 2021 3:11 AM >> To: users@cloudstack.apache.org >> Subject: Re: Quickstart question - Network issues >> Thank you for the response. I got much further. All my issues seem >> networking related. Everything is up right now and I see the template for >> CentOS 5.5 as an offering. >> My Cloudstack host is on 192.168.10.35. My System VMs is configured as such: >> [cid:D47FD2E4-F159-4778-973E-F96505D3ADD6] >> At this point, I’m trying to understand how to configured my Guest networks. >> Ideally my guest vm’s would just use my external DHCP server to allocate an >> IP address but I’m not having much luck finding documentation on how to >> properly do that. I also see posts saying external DHCP servers aren’t >> supported because Cloudstack needs to be aware of the guest’s IP for a >> number of reasons. >> So my question becomes, what type and how should I configure my guest >> network. Can I use IPs on the same subnet that my Cloudstack host is >> sitting on? If I can’t use DHCP directly, I can specify a range that is not >> in use by my external DHCP server so IPs will still end up on the public >> network and I can access the VMs on that IP directly. >> Interfaces on my Cloudstack host: >> cloud0: flags=4163 mtu 1500 >> inet 169.254.0.1 netmask 255.255.0.0 broadcast 0.0.0.0 >> inet6 fe80::8c30:6dff:fe87:ed32 prefixlen 64 scopeid 0x20 >> ether fe:00:a9:fe:91:b4 txqueuelen 1000 (Ethernet) >> RX packets 440 bytes 80558 (78.6 KiB) >> RX errors 0 dropped 0 overruns 0 frame 0 >> TX packets 539 bytes 96150 (93.8 KiB) >> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >> cloudbr0: flags=4163 mtu 1500 >> inet 192.168.10.35 netmask 255.255.255.0 broadcast 192.168.10.255 >> inet6 fe80::4a2:a9ff:fecf:819 prefixlen 64 scopeid 0x20 >> ether b4:b5:2f:db:a2:9b txqueuelen 1000 (Ethernet) >> RX packets 1203750 bytes 3227151094 (3.0 GiB) >> RX errors 0 dropped 5 overruns 0 frame 0 >> TX packets 498851 bytes 2710603584 (2.5 GiB) >> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >> eno1: flags=4163 mtu 1500 >> ether b4:b5:2f:db:a2:9b txqueuelen 1000 (Ethernet) >> RX packets 4650048 bytes 4876148565 (4.5 GiB) >> RX errors 0 dropped 622 overruns 0 frame 0 >> TX packets 3955493 bytes 5163648882 (4.8 GiB) >> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >> device interrupt 20 memory 0xf7c0-f7c2 >> lo: flags=73 mtu 65536 >> inet 127.0.0.1 netmask 255.0.0.0 >> inet6 ::1 prefixlen 128 scopeid 0x10 >> loop txqueuelen 1000 (Local Loopback) >> RX packets 2322050 bytes 504114946 (480.7 MiB) >> RX errors 0 dropped 0 overruns 0 frame 0 >> TX packets 2322050 bytes 504114946 (480.7 MiB) >> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >> vnet0: flags=4163 mtu 1500 >> inet6 fe80::fc00:a9ff:fefe:91b4 prefixlen 64 scopeid 0x20 >> ether fe:00:a9:fe:91:b4 txqueuelen 1000 (Ethernet) >> RX packets 50 bytes 9384 (9.1 KiB) >> RX errors 0 dropped 0 overruns 0 frame 0 >> TX packets 98 bytes 15290 (14.9 KiB) >> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >> vnet1: flags=4163 mtu 1500 >> inet6 fe80::fc00:7cff:fe00:5 prefixlen 64 scopeid 0x20 >> ether fe:00:7c:00:00:05 txqueuelen 1000 (Ethernet) >> RX packets 15707 bytes 22253
Re: Quickstart question - Network issues
Thank you. This vlan range only applies to the network between the vm guest and the vm host? Does this vlan range need to exist on my public net? The vlan stuff did confuse me a bit and I believe on my latest try, I didn’t define one. -jeremy > On May 31, 2021, at 4:14 AM, Nicolas Vazquez > wrote: > > Hi Jeremy, > > Can you please check if you have a Vlan range defined for your guest physical > network? You can check under Infrastructure -> Zone -> Physical Network -> > Guest. In case the Vlan range is not defined you can update the guest > physical network's VLAN/VNI to the format: VLAN_START-VLAN_END > > > Regards, > > Nicolas Vazquez > > > > > > From: Jeremy Hansen > Sent: Monday, May 31, 2021 3:11 AM > To: users@cloudstack.apache.org > Subject: Re: Quickstart question - Network issues > > Thank you for the response. I got much further. All my issues seem > networking related. Everything is up right now and I see the template for > CentOS 5.5 as an offering. > > My Cloudstack host is on 192.168.10.35. My System VMs is configured as such: > > [cid:D47FD2E4-F159-4778-973E-F96505D3ADD6] > > > At this point, I’m trying to understand how to configured my Guest networks. > Ideally my guest vm’s would just use my external DHCP server to allocate an > IP address but I’m not having much luck finding documentation on how to > properly do that. I also see posts saying external DHCP servers aren’t > supported because Cloudstack needs to be aware of the guest’s IP for a number > of reasons. > > So my question becomes, what type and how should I configure my guest > network. Can I use IPs on the same subnet that my Cloudstack host is sitting > on? If I can’t use DHCP directly, I can specify a range that is not in use > by my external DHCP server so IPs will still end up on the public network and > I can access the VMs on that IP directly. > > Interfaces on my Cloudstack host: > > cloud0: flags=4163 mtu 1500 >inet 169.254.0.1 netmask 255.255.0.0 broadcast 0.0.0.0 >inet6 fe80::8c30:6dff:fe87:ed32 prefixlen 64 scopeid 0x20 >ether fe:00:a9:fe:91:b4 txqueuelen 1000 (Ethernet) >RX packets 440 bytes 80558 (78.6 KiB) >RX errors 0 dropped 0 overruns 0 frame 0 >TX packets 539 bytes 96150 (93.8 KiB) >TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > cloudbr0: flags=4163 mtu 1500 >inet 192.168.10.35 netmask 255.255.255.0 broadcast 192.168.10.255 >inet6 fe80::4a2:a9ff:fecf:819 prefixlen 64 scopeid 0x20 >ether b4:b5:2f:db:a2:9b txqueuelen 1000 (Ethernet) >RX packets 1203750 bytes 3227151094 (3.0 GiB) >RX errors 0 dropped 5 overruns 0 frame 0 >TX packets 498851 bytes 2710603584 (2.5 GiB) >TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > eno1: flags=4163 mtu 1500 >ether b4:b5:2f:db:a2:9b txqueuelen 1000 (Ethernet) >RX packets 4650048 bytes 4876148565 (4.5 GiB) >RX errors 0 dropped 622 overruns 0 frame 0 >TX packets 3955493 bytes 5163648882 (4.8 GiB) >TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >device interrupt 20 memory 0xf7c0-f7c2 > > lo: flags=73 mtu 65536 >inet 127.0.0.1 netmask 255.0.0.0 >inet6 ::1 prefixlen 128 scopeid 0x10 >loop txqueuelen 1000 (Local Loopback) >RX packets 2322050 bytes 504114946 (480.7 MiB) >RX errors 0 dropped 0 overruns 0 frame 0 >TX packets 2322050 bytes 504114946 (480.7 MiB) >TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > vnet0: flags=4163 mtu 1500 >inet6 fe80::fc00:a9ff:fefe:91b4 prefixlen 64 scopeid 0x20 >ether fe:00:a9:fe:91:b4 txqueuelen 1000 (Ethernet) >RX packets 50 bytes 9384 (9.1 KiB) >RX errors 0 dropped 0 overruns 0 frame 0 >TX packets 98 bytes 15290 (14.9 KiB) >TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > vnet1: flags=4163 mtu 1500 >inet6 fe80::fc00:7cff:fe00:5 prefixlen 64 scopeid 0x20 >ether fe:00:7c:00:00:05 txqueuelen 1000 (Ethernet) >RX packets 15707 bytes 2225323 (2.1 MiB) >RX errors 0 dropped 0 overruns 0 frame 0 >TX packets 127124 bytes 19795223 (18.8 MiB) >TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > vnet2: flags=4163 mtu 1500 >inet6 fe80::fc00:d8ff:fe00:7 prefixlen 64 scopeid 0x20 >ether fe:00:d8:00:00:07 txqueuelen 1000 (Ethernet) >RX packets 808 bytes 57456 (56.1 KiB) >
Re: Quickstart question - Network issues
Hi Jeremy, Can you please check if you have a Vlan range defined for your guest physical network? You can check under Infrastructure -> Zone -> Physical Network -> Guest. In case the Vlan range is not defined you can update the guest physical network's VLAN/VNI to the format: VLAN_START-VLAN_END Regards, Nicolas Vazquez From: Jeremy Hansen Sent: Monday, May 31, 2021 3:11 AM To: users@cloudstack.apache.org Subject: Re: Quickstart question - Network issues Thank you for the response. I got much further. All my issues seem networking related. Everything is up right now and I see the template for CentOS 5.5 as an offering. My Cloudstack host is on 192.168.10.35. My System VMs is configured as such: [cid:D47FD2E4-F159-4778-973E-F96505D3ADD6] At this point, I’m trying to understand how to configured my Guest networks. Ideally my guest vm’s would just use my external DHCP server to allocate an IP address but I’m not having much luck finding documentation on how to properly do that. I also see posts saying external DHCP servers aren’t supported because Cloudstack needs to be aware of the guest’s IP for a number of reasons. So my question becomes, what type and how should I configure my guest network. Can I use IPs on the same subnet that my Cloudstack host is sitting on? If I can’t use DHCP directly, I can specify a range that is not in use by my external DHCP server so IPs will still end up on the public network and I can access the VMs on that IP directly. Interfaces on my Cloudstack host: cloud0: flags=4163 mtu 1500 inet 169.254.0.1 netmask 255.255.0.0 broadcast 0.0.0.0 inet6 fe80::8c30:6dff:fe87:ed32 prefixlen 64 scopeid 0x20 ether fe:00:a9:fe:91:b4 txqueuelen 1000 (Ethernet) RX packets 440 bytes 80558 (78.6 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 539 bytes 96150 (93.8 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 cloudbr0: flags=4163 mtu 1500 inet 192.168.10.35 netmask 255.255.255.0 broadcast 192.168.10.255 inet6 fe80::4a2:a9ff:fecf:819 prefixlen 64 scopeid 0x20 ether b4:b5:2f:db:a2:9b txqueuelen 1000 (Ethernet) RX packets 1203750 bytes 3227151094 (3.0 GiB) RX errors 0 dropped 5 overruns 0 frame 0 TX packets 498851 bytes 2710603584 (2.5 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eno1: flags=4163 mtu 1500 ether b4:b5:2f:db:a2:9b txqueuelen 1000 (Ethernet) RX packets 4650048 bytes 4876148565 (4.5 GiB) RX errors 0 dropped 622 overruns 0 frame 0 TX packets 3955493 bytes 5163648882 (4.8 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 20 memory 0xf7c0-f7c2 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 2322050 bytes 504114946 (480.7 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2322050 bytes 504114946 (480.7 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vnet0: flags=4163 mtu 1500 inet6 fe80::fc00:a9ff:fefe:91b4 prefixlen 64 scopeid 0x20 ether fe:00:a9:fe:91:b4 txqueuelen 1000 (Ethernet) RX packets 50 bytes 9384 (9.1 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 98 bytes 15290 (14.9 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vnet1: flags=4163 mtu 1500 inet6 fe80::fc00:7cff:fe00:5 prefixlen 64 scopeid 0x20 ether fe:00:7c:00:00:05 txqueuelen 1000 (Ethernet) RX packets 15707 bytes 2225323 (2.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 127124 bytes 19795223 (18.8 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vnet2: flags=4163 mtu 1500 inet6 fe80::fc00:d8ff:fe00:7 prefixlen 64 scopeid 0x20 ether fe:00:d8:00:00:07 txqueuelen 1000 (Ethernet) RX packets 808 bytes 57456 (56.1 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 109119 bytes 17746092 (16.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vnet3: flags=4163 mtu 1500 inet6 fe80::fc00:a9ff:fefe:b767 prefixlen 64 scopeid 0x20 ether fe:00:a9:fe:b7:67 txqueuelen 1000 (Ethernet) RX packets 46 bytes 9168 (8.9 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 95 bytes 15068 (14.7 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vnet4: flags=4163 mtu 1500 inet6 fe80::fc00:c2ff:fe00:6 prefixlen 64 scopeid 0x20 ether fe:00:c2:00:00:06 txqueuelen 1000 (Ethernet) RX packets 144923 bytes 2256458775 (2.1 GiB) RX errors 0 dropped 0 overruns 0
