Hello,
Please check your guest VLAN Range, looks like it’s not there, so when you
create any isolate network or VPC style network, It configure a public NIC and
a guest NIC and guest Nic is configured on a random VLAN (The VLAN which you
assign while creating the zone ).
>From the logs you provided -
eleased for network id 206 as a part of network implement
com.cloud.exception.InsufficientVirtualNetworkCapacityException: Unable to
allocate vnet as a part of network Network {"id": 206, "name": "MyIsolatedNe
twork", "uuid": "298ddc5f-bb2a-498e-a15f-7011dfa2e4dc", "networkofferingid": 9}
implement Scope=interface com.cloud.dc.DataCenter; id=1
Click on Zone, and then -> click on physical network —> then click on the
network where you have defined - traffic type guest , and then —> traffic type
—> select guest —> then edit the setting where you will have option to define
VLAN Range,
Note - These VLAN should be allowed on the physical switch port where your host
is connected, if you have multiple hosts
i.e
Vivek Kumar
Sr. Manager - Cloud & DevOps
TechOps | Indiqus Technologies
[email protected] <mailto:[email protected]>
www.indiqus.com <https://www.indiqus.com/>
> On 18-Jan-2023, at 1:18 AM, Leandro Ramos <[email protected]> wrote:
>
> Hi :)
>
> I'm trying to launch an instance on Cloudstack, but I got some errors.
> There's a pastebin with a "grep -i network
> /var/log/cloudstack/management/management-server.log" result here:
> https://pastebin.com/KY6FWm3t <https://pastebin.com/KY6FWm3t>
> Anyone can help me?
>
> In fact I didn't understand very well how to create an isolated network (even
> after seeing some tutorials and videos), so I have created one with default
> values:
>
> <XZRiz6JpqOTFNmms.png>
>
>
>
> Thank you.
>
--
This message is intended only for the use of the individual or entity to
which it is addressed and may contain confidential and/or privileged
information. If you are not the intended recipient, please delete the
original message and any copy of it from your computer system. You are
hereby notified that any dissemination, distribution or copying of this
communication is strictly prohibited unless proper authorization has been
obtained for such action. If you have received this communication in error,
please notify the sender immediately. Although IndiQus attempts to sweep
e-mail and attachments for viruses, it does not guarantee that both are
virus-free and accepts no liability for any damage sustained as a result of
viruses.
