Hello Midhun, Faced an issue during last update Updating to Xcp-NG 8.2.1 causes bugs on some features.
Take a look at the issue i found about. There is a fix i tried and succeded to continue working with Xcp-NG 8.2.1 https://github.com/apache/cloudstack/issues/6349 Hope this could help Le mar. 12 avr. 2022 à 09:01, Midhun Jose <mid...@assistanz.com.invalid> a écrit : > Hi vivek/Nux, > > Our network department updated that the ethernet ports on our switch are > access ports, not trunk ports, and hence no vlans are allowed. > They asked us to check the configuration in the virtual router and make > sure the vlans are allowed. > could you please suggest anything on this. > > > Midhun Jose > > > ----- Original Message ----- > From: "Vivek Kumar" <vivek.ku...@indiqus.com.INVALID> > To: "users" <users@cloudstack.apache.org> > Sent: Thursday, April 7, 2022 1:17:07 PM > Subject: Re: ACS 4.16.1 ::XCP-ng 8.2.1 CS Guest VM can't communicate with > virtual routers when they are on different hosts > > Hello Midhun, > > This typically happens when your guest VLAN range is not allowed in the > backend switch ports. So allowed all of your VLAN range on the ports where > you have defined your guest traffic. > > > > Regards, > Vivek Kumar > > > > On 07-Apr-2022, at 12:13 PM, Midhun Jose <mid...@assistanz.com.INVALID> > wrote: > > > > Hi @All, > > > > I'm using Cloudstack 4.16.1 with XCP-ng Cluster having 2 hosts. > > I am facing issue When virtual router is created on host 1 and a guest > VM that uses that virtual router is created on host 2. there is no > connectivity from VM and the VR. > > (refer the screenshot attached.) > > But when both virtual router and guest VM are created on the same host > everything works like normal. > > Did I miss something on configuring the network? > > > > Best Regards, > > Midhun Jose > > > > > -- > 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. >