Hi Wei,
Yes, of course 😊 I'm able to create the network with any of the network offering, which are with tags, the problem is when the router is starting to deploy, I get the same error without to many details, tested in 2 cloudstack environment 4.15.1 and 4.15.2, in 1 I have multiple zones and in the test one I have only 1 zone with 2 hosts KVM and VMware. For me is pretty simple: Zone X: 1 . Assign a tag to each physical network, for the default 1 and for any additional network. 2. Create a network offering with the corresponding tags, I also saw that you can update the tags for default network offering. 3. Create network with any of those offerings Here I attached screenshots : https://imgur.com/a/VtvYsvS I do not see any issue in my configuration. Regards, Cristian -----Original Message----- From: Wei ZHOU <ustcweiz...@gmail.com> Sent: Tuesday, October 12, 2021 3:21 PM To: users <users@cloudstack.apache.org> Subject: Re: Multiple Network labels - custom Hi Cristian, I think it is good. You do not need to change the physical networks. Have you created a new "network offering" with a tag (A or B) ? -Wei On Tue, 12 Oct 2021 at 14:02, < <mailto:cristian.c@istream.today> cristian.c@istream.today> wrote: > I have only 1 network by default : > > 1. Management / Storage / Public / Guest - Tag A > 2. Guest - Tag B > > Now, if I understand right, this is not working in this way? I should > have separated network for guest from the beginning? > > 1 . Management / Storage /Public - Tag A 2. Guest - Tag B 3. Guest - > Tag C > > > Regarding running networks, I will try to rebuild after I have the > current issue fixed. > > Zone, I think the same, but not sure yet.... > > Thank you, > Cristian > >
