tatay188 commented on issue #11983: URL: https://github.com/apache/cloudstack/issues/11983#issuecomment-3665770912
@weizhouapache @wido @DaanHoogland Yes I have it like that: vxlan.YYY -> cloudbr2 (kvmnetworklabel of Storage network). It's routed with its own VNI, I did not add to cloudstack - Works vxlan.XXX -> cloudbr1 (kvmnetworklabel of Management network). it's routed with its own VNI - but this data is filled during the Zone creation, and the zone creation forces me to have a range of IP addresses assigned for management. Are you saying this management ip address part is irrelevant ? What are this range of management IP addresses are used for? I see This are used by the System VMs only, so far. On the system VM's is using the cloudbr1 on the Management VNI, And using the **virsh list,** **virsh domiflist** is using the **cloudbr1**, on the management **VNI.XXX** I don't see any of this range of Management IP addresses used Anywhere else , I checked on the VMs, I neither see this IP addresses assigned to the VR (Virtual Routers) @wido although was long time ago you set your zones, I hope is not too much to ask, kindly can your engineers check if you have this filled on your zone for the management. @weizhouapache @wido @DaanHoogland If Wido can confirm he have also configured the Management IP range with a vlan://whatever we can close this case as this is mostly a **"cosmetic issue"**, not a "functional issue" as it will use the vxlan.XXX VNI.XXX regardless of what is presented on the UI. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
