Thank you Vash and Дикевич Евгений Александрович
Everything worked in the end. what I had to do was : - put the cloudbr0 in UP state : cmd : ip link set cloudbr0 up - and then deactivate the eno1 interface : (I used the nmtui tool) As I always say you guys are my favourite community and I wish you a great weekend. Best Regards, On Fri, Oct 15, 2021 at 4:55 PM vas...@gmx.de <vas...@gmx.de> wrote: > Hi Serge, > > i really don't see the point in bonding those two interfaces, as they are > meant to be used for different taffic. > Therefore i guess you should at the moment remain on your inital > configuration. > > As far as i have read through all of this you would like to "clone" the > setup from the host which is already working: > Bridge: cloudbr0 <--- here ip configuration > interface: eno1 <--- no ip configuration / disable dhcp just to be > save > > Bridge: cloudbr1 <--- no ip configuration / disable dhcp just to be save > interface: eno4 <--- no ip configuration / disable dhcp just to be > save > > that should at least give you a basic connectivity again. > Afterwards, reading through you provided log agent.log i would check > connectivity from the host to the management server as well as to the > storage server - even try mounting a nfs-share. > As war as i read the log correctly the communication twards the > managementserver has worked out well but there where some trouble with the > connection to the storage provider. > > regards > > > Am Fr., 15. Okt. 2021 um 13:28 Uhr schrieb Bs Serge <sergeb...@gmail.com>: > > > I appreciate the help, > > > > I tried the above, created a bond and combined eno1 and eno4 but when I > > rebooted neither of the interfaces or the bond or bridges were showing up > > in ifconfig, which meant I couldn't even SSH, so I had to set them back > > manually. > > > > I'd like to mention that another host works perfectly with the same > network > > configuration, It has 2 NICs interfaces enp0s25 and enp3s0 and two > bridges > > cloudbr0 and cloudbr1. cloudbr0 has an IP but the child interface > > (enp0s25) does not. cloudbr1 does not have IP coz it is used for public > > traffic and its child interface is enp3s0. > > > > When I was configuring the first host this was a reply email I got from > > Andrija Panic after showing the same configuration. > > > > > > Hi Serge, > > > > > > that configuration looks OK - cloudbr0 has to has an IP as you want to > be > > > able to have your host on the management network (and you removed the > IP > > > from the child-interface). > > > cloudbr1 is use for public traffic, so that is also ok - NO IP should > be > > > there, as you do NOT want your host to be reachable via L3 on it's > public > > > IP address - only L2, pass through the traffic to the VMs. > > > > > > In short, yes, it looks good. > > > > > > When in ACS, make sure to set "cloudbr0" as KVM traffic label for > > > management/storage/guest traffic type, while "cloudbr1" (no quotes) > will > > > be the traffic label for public traffic. > > > > > > After all these changes, make sure to destroy SSVM/CPVM, and restart > any > > > networks/VPC with "cleanup" which will create new VRs attached to the > > > correct bridges, etc. > > > > > > > > > Good luck! > > > > > > > > > The traffic labelled in ACS are still set like mentioned above, that's > why > > the management server is trying to look for "cloudbr0" on the host. > > > > On the host which works fine, you can see that the cloudbr0 has an IP and > > its child interface enp0s25 does not, which I think is how it is supposed > > to be also on the new host. > > > > https://ibb.co/XbwkRVH > > > > So I guess that's where my problem lies on this new host, the cloudbr0 > > bridge is taking the IP as well as the child interface eno1. > > > > Again any help or guidance would be appreciated. > > > > Best Regards, > > > > On Fri, Oct 15, 2021 at 11:51 AM Дикевич Евгений Александрович < > > evgeniy.dikev...@becloud.by> wrote: > > > > > Mb better combine eno1 and eno4 in bond and then create bridge on this > > > bond: > > > > > > Smth like this: > > > > > > cat /etc/sysconfig/network-scripts/ifcfg-eno1 > > > TYPE=Ethernet > > > BOOTPROTO=none > > > NAME=eno1 > > > DEVICE=eno1 > > > ONBOOT=yes > > > MASTER=bond0 > > > SLAVE=yes > > > NM_CONTROLLED=no > > > > > > cat /etc/sysconfig/network-scripts/ifcfg-eno2 > > > TYPE=Ethernet > > > BOOTPROTO=none > > > NAME=eno2 > > > DEVICE=eno2 > > > ONBOOT=yes > > > MASTER=bond0 > > > SLAVE=yes > > > NM_CONTROLLED=no > > > > > > cat /etc/sysconfig/network-scripts/ifcfg-bond0 > > > NAME=bond0 > > > DEVICE=bond0 > > > NM_CONTROLLED=no > > > TYPE=Bond > > > BRIDGE=cloudbr0 > > > ONBOOT=yes > > > NM_CONTOLLED=no > > > BONDING_OPTS="mode=802.3ad miimon=100 lacp_rate=fast > > > xmit_hash_policy=layer2+3" > > > > > > cat /etc/sysconfig/network-scripts/ifcfg-cloudbr0 > > > NAME=cloudbr0 > > > DEVICE=cloudbr0 > > > TYPE=Bridge > > > ONBOOT=yes > > > NM_CONTROLLED=no > > > IPADDR=XXX.XXX.XXX.XXX > > > PREFIX=YY > > > > > > Or better read this: > > > > > > > > > > > > https://www.shapeblue.com/networking-kvm-for-cloudstack-2018-revisit-for-centos7-and-ubuntu-18-04/ > > > > > > -----Original Message----- > > > From: Bs Serge [mailto:sergeb...@gmail.com] > > > Sent: Friday, October 15, 2021 12:44 PM > > > To: users@cloudstack.apache.org > > > Subject: Re: [!!Mass Mail]Exception : Can not find network: cloudbr0 > > > > > > Yes, I just realized that > > > > > > On the host both the bridge cloudbr0 and the interface eno1 have the > same > > > IP : 192.168.1.10 which is the IP of the host server. the management > > > server IP is 192.168.1.8 > > > > > > I tried to reboot the host but the issue was not resolved > > > > > > This is my bridge configuration, > > > > > > cat ifcfg-cloudbr0 > > > DEVICE=cloudbr0 > > > TYPE=Bridge > > > ONBOOT=yes > > > BOOTPROTO=none > > > IPV6INIT=no > > > IPV6_AUTOCONF=no > > > DELAY=5 > > > IPADDR=192.168.1.10 > > > GATEWAY=192.168.1.1 > > > NETMASK=255.255.255.0 > > > STP=yes > > > > > > //------------------- > > > > > > cat ifcfg-eno1 > > > TYPE="Ethernet" > > > BOOTPROTO="none" > > > NAME="eno1" > > > DEVICE="eno1" > > > ONBOOT="yes" > > > BRIDGE=cloudbr0 > > > HOTPLUG=no > > > > > > > > > //------------------- > > > > > > cat ifcfg-cloudbr1 > > > DEVICE=cloudbr1 > > > TYPE=Bridge > > > ONBOOT=yes > > > BOOTPROTO=none > > > IPV6INIT=no > > > IPV6_AUTOCONF=no > > > DELAY=5 > > > STP=yes > > > > > > //----------- > > > > > > cat ifcfg-eno4 > > > TYPE=Ethernet > > > NAME=eno4 > > > UUID=949aef09-7aee-492f-82c3-969e445b8746 > > > DEVICE=eno4 > > > ONBOOT=yes > > > HOTPLUG=no > > > BOOTPROTO=none > > > BRIDGE=cloudbr1 > > > > > > Thanks for the prompt reply, > > > > > > Best Regards, > > > > > > > > > On Fri, Oct 15, 2021 at 11:16 AM Дикевич Евгений Александрович < > > > evgeniy.dikev...@becloud.by> wrote: > > > > > > > And you have management IP on eno1. Mb U should reboot your host > > > > first:) > > > > > > > > -----Original Message----- > > > > From: Дикевич Евгений Александрович > > > > [mailto:evgeniy.dikev...@becloud.by] > > > > Sent: Friday, October 15, 2021 12:14 PM > > > > To: users@cloudstack.apache.org > > > > Subject: RE: [!!Mass Mail]Exception : Can not find network: cloudbr0 > > > > > > > > Hi > > > > Your cloudbr0 is in DOWN state. Check your network again > > > > > > > > https://ibb.co/rFyh4Zk > > > > > > > > -----Original Message----- > > > > From: Bs Serge [mailto:sergeb...@gmail.com] > > > > Sent: Friday, October 15, 2021 11:57 AM > > > > To: users@cloudstack.apache.org > > > > Subject: [!!Mass Mail]Exception : Can not find network: cloudbr0 > > > > > > > > Hi, my favourite community, > > > > > > > > Cloudstack 4.15.2 > > > > Host KVM > > > > Centos 8 > > > > > > > > I'm trying to add a new KVM host to cloudstack and I'm getting this > > > > exception in the management server that says it can not find a > network > > > > named cloudbr0 on the agent while the bridge network cloudbr0 > exists, > > > > > > > > Below I shared the output of ifconfig on the agent and both the > > > > management server and the agent logs > > > > > > > > The new host has 4 NICs but only 2 of them are connected. > > > > > > > > https://ibb.co/5RGfGZS > > > > https://ibb.co/rFyh4Zk > > > > > > > > Management Logs > > > > https://ibb.co/KwbpDNb > > > > > > > > Agent Logs > > > > https://ibb.co/TRM8zXR > > > > > > > > Any kind of help would be appreciated. > > > > > > > > Best Regards, > > > > Внимание! > > > > Это электронное письмо и все прикрепленные к нему файлы являются > > > > конфиденциальными и предназначены исключительно для использования > > > > лицом (лицами), которому (которым) оно предназначено. Если Вы не > > > > являетесь лицом (лицами), которому (которым) предназначено это > письмо, > > > > не копируйте и не разглашайте его содержимое и удалите это сообщение > и > > > > все вложения из Вашей почтовой системы. Любое несанкционированное > > > > использование, распространение, раскрытие, печать или копирование > > > > этого электронного письма и прикрепленных к нему файлов, кроме как > > > > лицом (лицами) которому (которым) они предназначены, является > > > > незаконным и запрещено. Принимая во внимание, что передача данных > > > > посредством Интернет не является безопасной, мы не несем никакой > > > > ответственности за любой потенциальный ущерб, причиненный в > результате > > > > ошибок при передаче данных или этим сообщением и прикрепленными к > нему > > > файлами. > > > > > > > > Attention! > > > > This email and all attachments to it are confidential and are > intended > > > > solely for use by the person (or persons) referred to (mentioned) as > > > > the intended recipient (recipients). If you are not the intended > > > > recipient of this email, do not copy or disclose its contents and > > > > delete the message and any attachments to it from your e-mail system. > > > > Any unauthorized use, dissemination, disclosure, printing or copying > > > > of this e-mail and files attached to it, except by the intended > > > > recipient, is illegal and is prohibited. Taking into account that > data > > > > transmission via Internet is not secure, we assume no responsibility > > > > for any potential damage caused by data transmission errors or this > > > message and the files attached to it. > > > > > > > Внимание! > > > Это электронное письмо и все прикрепленные к нему файлы являются > > > конфиденциальными и предназначены исключительно для использования лицом > > > (лицами), которому (которым) оно предназначено. Если Вы не являетесь > > лицом > > > (лицами), которому (которым) предназначено это письмо, не копируйте и > не > > > разглашайте его содержимое и удалите это сообщение и все вложения из > > Вашей > > > почтовой системы. Любое несанкционированное использование, > > распространение, > > > раскрытие, печать или копирование этого электронного письма и > > прикрепленных > > > к нему файлов, кроме как лицом (лицами) которому (которым) они > > > предназначены, является незаконным и запрещено. Принимая во внимание, > что > > > передача данных посредством Интернет не является безопасной, мы не > несем > > > никакой ответственности за любой потенциальный ущерб, причиненный в > > > результате ошибок при передаче данных или этим сообщением и > > прикрепленными > > > к нему файлами. > > > > > > Attention! > > > This email and all attachments to it are confidential and are intended > > > solely for use by the person (or persons) referred to (mentioned) as > the > > > intended recipient (recipients). If you are not the intended recipient > of > > > this email, do not copy or disclose its contents and delete the message > > and > > > any attachments to it from your e-mail system. Any unauthorized use, > > > dissemination, disclosure, printing or copying of this e-mail and files > > > attached to it, except by the intended recipient, is illegal and is > > > prohibited. Taking into account that data transmission via Internet is > > not > > > secure, we assume no responsibility for any potential damage caused by > > data > > > transmission errors or this message and the files attached to it. > > > > > >
