You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by "tatay188 (via GitHub)" <gi...@apache.org> on 2025/11/04 21:15:46 UTC
[I] CS 4.20.1 Unable to run Management and secondary Storage on VXLAN - System AutoConfigures ON VLAN Untagged: the VXLAN Management and SecondaryStorage Forced to run on VLAN://untagged [cloudstack]
tatay188 opened a new issue, #11983:
URL: https://github.com/apache/cloudstack/issues/11983
### problem
We did some manual, routing corrections as a work around but want to know if this is a Bug.
!
I have the management on a vxlan, but when creating the Zone the system adds the IPs to a VLAN://untagged. that VLAN is for public.
!
There is no way for me to move them to VXLAN the Management:
!
!
!
The Management Interface was created during the Installation: But was loaded to a vlan://untagged - I do not have how as I specifically set for vxlan on cloudbr1
!
<img width="776" height="388" alt="Image" src="https://github.com/user-attachments/assets/d297ee4d-6b14-4ddb-82c2-2fe4e1005a59" />
!
!
!
The Zone Has VXLANs for Primary storage, Management, and Guest.
!
<img width="610" height="412" alt="Image" src="https://github.com/user-attachments/assets/a2115ea3-f395-4076-a4fd-69d1f9eb970c" />
!
!
<img width="786" height="401" alt="Image" src="https://github.com/user-attachments/assets/6ea626b2-9106-4ae6-ad3d-f368b7a70ea6" />
!
!
!
Any Attemp to change the VLAN to VXLAN results on an error:
!
<img width="318" height="94" alt="Image" src="https://github.com/user-attachments/assets/4adc2cab-aa97-4de4-b951-ff83360e7ef4" />
!
!
! Additionally The Secondary Storage is affected by this routing.
!
!
Is the Storage Traffic type solely for Primary storage ? I will like to have the secondary storage on a separate routed or L2/Vlan tagged
Our primary Storage is CEPH running on VXLAN and have no problems at all - Primary storage and Guest VXLAN are the only thing working as it should per the documentation.
!
!
<img width="612" height="350" alt="Image" src="https://github.com/user-attachments/assets/7d4acb42-b211-4b83-8f8a-e7fbb016c0f9" />
### versions
CS 4.20.1
PRI STORAGE: CEPH
SEC STORAGE: NFS EMC
VXLAN
Forced VLAN for Public - but System auto-configures the Management on vlan://untagged which also uses Secondary Storage.
### The steps to reproduce the bug
1. Create a new Zone, all new systems.
2. put on vxlan management, secondary-storage and guest on cloudbr1
3. pod settings: Assign the IP range for management - there is nowhere to add a VXLAN ports for Management during the initial setup/configuration
4. System VM proxy have to be routed manually, same as Secondary storage.
Not possible to set secondary storage using routing without VRFs, as systemVM automatically try to push it over VLAN://untagged being forced to manually route over vlan://untagged...
As a workaround we route sec Storage and Management over vlan://untagged
### What to do about it?
The management should use the vxlan://assigend, and secondary storage should be able to have its own route if needed.
The UI configures the Storage for the primary Storage only.
--
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: commits-unsubscribe@cloudstack.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] CS 4.20.1 Unable to run Management and secondary Storage on VXLAN - System AutoConfigures ON VLAN Untagged: the VXLAN Management and SecondaryStorage Forced to run on VLAN://untagged [cloudstack]
Posted by "weizhouapache (via GitHub)" <gi...@apache.org>.
weizhouapache commented on issue #11983:
URL: https://github.com/apache/cloudstack/issues/11983#issuecomment-3664729114
@tatay188
would the following setup work ?
- vxlan.XXX -> cloudbr1 (kvmnetworklabel of Management network).
- vxlan.YYY -> cloudbr2 (kvmnetworklabel of Storage network).
VLAN/VNI is set to ``vlan://untagged` for both networks.
IMHO, I would suggest the public/guest network to be managed by ACS.
but for mgmt/storage network, I would them to be preconfigured and not changed by ACS.
--
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: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] CS 4.20.1 Unable to run Management and secondary Storage on VXLAN - System AutoConfigures ON VLAN Untagged: the VXLAN Management and SecondaryStorage Forced to run on VLAN://untagged [cloudstack]
Posted by "tatay188 (via GitHub)" <gi...@apache.org>.
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: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] CS 4.20.1 Unable to run Management and secondary Storage on VXLAN - System AutoConfigures ON VLAN Untagged: the VXLAN Management and SecondaryStorage Forced to run on VLAN://untagged [cloudstack]
Posted by "tatay188 (via GitHub)" <gi...@apache.org>.
tatay188 commented on issue #11983:
URL: https://github.com/apache/cloudstack/issues/11983#issuecomment-3650104390
@DaanHoogland
I am a bit confused, when you have a chance Can you elaborate. How is this a new feature, If I have the Management configured for VXLAN and the system internally is vlan://untagged, same for secondary storage ? that seems like a Bug, or somewhere in the documentation should have a Warning Note on this regard for "advanced networking" the Management network and secondary storage network will use vlan regardless of the setting of the zone, and if no vlan assigned will use the untagged vlan.
--
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: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] CS 4.20.1 Unable to run Management and secondary Storage on VXLAN - System AutoConfigures ON VLAN Untagged: the VXLAN Management and SecondaryStorage Forced to run on VLAN://untagged [cloudstack]
Posted by "wido (via GitHub)" <gi...@apache.org>.
wido commented on issue #11983:
URL: https://github.com/apache/cloudstack/issues/11983#issuecomment-3665023333
Yes, it could work, but just keep in mind that CloudStack really doesn't care that much. We have created a device "vni200" which is underneath cloudbr1. CloudStack has no knowledge about this at all, it just uses cloudbr1.
cloudbr0 is never used as with VXLAN there is no central bridge where all the traffic is connected to.
Regarding Storage networks: I have never used it so I wouldn't know to be honest.
--
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: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] CS 4.20.1 Unable to run Management and secondary Storage on VXLAN - System AutoConfigures ON VLAN Untagged: the VXLAN Management and SecondaryStorage Forced to run on VLAN://untagged [cloudstack]
Posted by "tatay188 (via GitHub)" <gi...@apache.org>.
tatay188 commented on issue #11983:
URL: https://github.com/apache/cloudstack/issues/11983#issuecomment-3658015756
Thank you @DaanHoogland but @wido have this working on vxlan @weizhouapache
I will appreciate if any of you can guide us on this platform, should I remove this entry for the management to work with VXLAN ?
<img width="786" height="401" alt="Image" src="https://github.com/user-attachments/assets/23b5d6a4-67b8-4f79-88bf-c4df0b031a52" />
Any attempt to add, reconfigure, recreate, enter a VXLAN interface throws an error like, I was planning to treat the management just as another guest, but when I did that nothing worked, although the VXLAN and endpoints VTEPs everything loos good.
<img width="314" height="88" alt="Image" src="https://github.com/user-attachments/assets/29edf3bd-c97e-4f82-8736-1f26e8134b94" />
@rohityadavcloud mentioned on the following discussion that the vxlan may work only for guests:
https://github.com/apache/cloudstack/discussions/10694
--
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: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] CS 4.20.1 Unable to run Management and secondary Storage on VXLAN - System AutoConfigures ON VLAN Untagged: the VXLAN Management and SecondaryStorage Forced to run on VLAN://untagged [cloudstack]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #11983:
URL: https://github.com/apache/cloudstack/issues/11983#issuecomment-4856144982
## ๐ฏ Triage report
The reporter wants to use VXLAN for the management and secondary storage traffic types, but CloudStack currently does not expose a way to assign a VXLAN broadcast domain to these traffic types via the zone setup wizard or the "Edit traffic type" UI. Maintainer feedback in comments confirms VXLAN on the management network is not officially supported today; the feature only works for guest networks. Several community members clarified that the typical workaround is to configure the VXLAN interface at the host OS level and point CloudStack to a standard bridge (`cloudbr1`) without teaching CloudStack about the underlying VNI.
### ๐ Assessment
| Dimension | Value | Reasoning |
|---|---|---|
| **Type** | type:new-feature | VXLAN support for management/storage traffic types is not currently implemented |
| **Component** | component:networking, component:vxlan | Network traffic type configuration; VXLAN isolation method |
| **Severity** | n/a | Not a code defect; unsupported feature |
| **Labels** | type:new-feature, component:networking, component:vxlan | As above |
| **Coding agent** | Not suitable | Requires design decisions on supported topology, traffic type isolation model, and zone setup wizard changes |
<details><summary>๐ก Notes and suggestions</summary>
- Current workaround (confirmed by community): configure the VXLAN VNI/bridge (`vxlan.XXX` โ `cloudbr1`) at the host OS level; CloudStack only sees `cloudbr1` and uses `(untagged/redacted) for management. This is a supported operational pattern even if not visible in the UI.
- Management IPs in the Pod are only used by System VMs (on KVM/XenServer); Virtual Routers use them as Control IP on VMware only.
- Related discussion: https://github.com/apache/cloudstack/discussions/10694 โ `@rohityadavcloud` noted VXLAN is guest-only in the current implementation.
- Implementation would require changes to zone wizard, traffic type DAO, and agent network configuration logic for KVM.
</details>
> Generated by [Daily Issue Triage](https://github.com/apache/cloudstack/actions/runs/28523943189) ยท [โท](https://github.com/search?q=repo%3Aapache%2Fcloudstack+%22gh-aw-workflow-call-id%3A+apache%2Fcloudstack%2Fdaily-issue-triage%22&type=issues)
>
<details>
<summary>Add this agentic workflows to your repo</summary>
To install this agentic workflow, run
```
gh aw add githubnext/agentics/workflows/daily-issue-triage.md@d7c1dc4b72b00607a67caaffdcc216cb64379cf9
```
</details>
<!-- gh-aw-agentic-workflow: Daily Issue Triage, engine: copilot, version: 1.0.52, model: claude-sonnet-4.6, id: 28523943189, workflow_id: daily-issue-triage, run: https://github.com/apache/cloudstack/actions/runs/28523943189 -->
<!-- gh-aw-workflow-call-id: apache/cloudstack/daily-issue-triage -->
--
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: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] CS 4.20.1 Unable to run Management and secondary Storage on VXLAN - System AutoConfigures ON VLAN Untagged: the VXLAN Management and SecondaryStorage Forced to run on VLAN://untagged [cloudstack]
Posted by "DaanHoogland (via GitHub)" <gi...@apache.org>.
DaanHoogland commented on issue #11983:
URL: https://github.com/apache/cloudstack/issues/11983#issuecomment-3654494734
@tatay188 , as I understand it vxlan on management network is not supported. In the end it does not matter as it is an opensource project, whether it is a bug or a feature or a task, someone needs to implement it for it to go through.
--
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: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] CS 4.20.1 Unable to run Management and secondary Storage on VXLAN - System AutoConfigures ON VLAN Untagged: the VXLAN Management and SecondaryStorage Forced to run on VLAN://untagged [cloudstack]
Posted by "wido (via GitHub)" <gi...@apache.org>.
wido commented on issue #11983:
URL: https://github.com/apache/cloudstack/issues/11983#issuecomment-3664251091
I don't I have this exactly working in that way. We have no separate management network, we just have a POD network which we route over a VNI, but CloudStack doesn't know about it.
cloudbr1 (pod internal traffic) is using a VNI which we configure manually underneath. Over this VNI the hypervisors communicate with the management server and Secondary Storage, but that's it.
For the public networks we use vxlan://XXX as the broadcast domain and that is then being used for the VMs which are being deployed.
Must say, it has been a few years since we have set this up, so I don't know exactly anymore what we did in the mgmt server.
But again, we don't use a separate management or storage network.
--
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: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] CS 4.20.1 Unable to run Management and secondary Storage on VXLAN - System AutoConfigures ON VLAN Untagged: the VXLAN Management and SecondaryStorage Forced to run on VLAN://untagged [cloudstack]
Posted by "weizhouapache (via GitHub)" <gi...@apache.org>.
weizhouapache commented on issue #11983:
URL: https://github.com/apache/cloudstack/issues/11983#issuecomment-3665871919
> 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.
I can answer these questions:
- on KVM/xen, the management IPs are used by System VMs only (for communication between mgmt servers and agent inside SSVM)
- on VMware, the management IPs are used by System VMs, and also Virtual Routers (as Control IP)
--
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: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] CS 4.20.1 Unable to run Management and secondary Storage on VXLAN - System AutoConfigures ON VLAN Untagged: the VXLAN Management and SecondaryStorage Forced to run on VLAN://untagged [cloudstack]
Posted by "DaanHoogland (via GitHub)" <gi...@apache.org>.
DaanHoogland commented on issue #11983:
URL: https://github.com/apache/cloudstack/issues/11983#issuecomment-3626109416
> let me know if you need any additional information.
@tatay188 , a bit disappointing reply, Iโm sure but: this looks like a new feature and not much interest is triggered on it yet.
--
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: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org