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

### 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
!

!
!
!
The Zone Has VXLANs for Primary storage, Management, and Guest.
!

!
!

!
!
!
Any Attemp to change the VLAN to VXLAN results on an error:
!

!
!
! 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.
!
!

### 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.

Commencez par reproduire la création d’une nouvelle Zone avec des VXLANs management, secondary-storage et guest sur cloudbr1, puis suivez les paramètres du pod et la configuration réseau du proxy de System VM. Vérifiez comment les types de trafic management et secondary-storage sont attribués lorsque le trafic public est forcé vers VLAN://untagged. Le travail est terminé lorsque management utilise le VXLAN attribué et que le stockage secondaire peut utiliser son propre réseau routé ou marqué sans routage manuel.

Rédigé par le modèle d'indexation à partir du texte de l'issue.