Hi Wilken, For each hypervisor type, you can set a traffic label per traffic type in each zone. You should be able to find that under zone-> Physical networks.
-Jithin From: W. Verleger - proIO GmbH <w.verle...@proio.com> Date: Tuesday, 22 August 2023 at 6:41 PM To: users@cloudstack.apache.org <users@cloudstack.apache.org> Subject: KVM Host Integration - Network Interfaces Hi all, We are running ACS 4.18.0.0 with one XCP-ng Host integrated in one Zone already. As physical network we defined "Mgmt" (Management) and "Frontnet" (Guest, Public). Now we want to add a new KVM host to the same Zone but a different cluster. Therefor we defined on the KVM host two new Bonds and on top of them two Bridges. While trying to add the new host we received a timeout: Error 530 Unable to add the host: Cannot find the server resources at http://IP And the following cloudstack-agent error message on the KVM host: DEBUG:root:cloudbr0 is not a network device, is it down? Is it mandatory to name the Bridges exactly "cloudbr0", "cloudbr1, ... ? If so, how to add a KVM host to an existing Zone with different Interface names (Mgmt / Frontnet)? Thank you! Mit freundlichen Grüßen / With kind regards Wilken Verleger proIO GmbH Kleyerstr. 79 - 89 / Tor 13 D-60326 Frankfurt am Main - Support - Mail: supp...@proio.com 24h: +(49) (0) 1805 522 855 - proIO GmbH - Geschäftsführer: Swen Brüseke Sitz der Gesellschaft: Frankfurt am Main USt-IdNr. DE 267 075 918 Registergericht: Frankfurt am Main - HRB 86239 Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht gestattet. This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
