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.

Empieza reproduciendo la creación de una nueva Zone con VXLANs de management, secondary-storage y guest en cloudbr1; después, sigue la configuración del pod y la configuración de red del proxy de System VM. Verifica cómo se asignan los tipos de tráfico management y secondary-storage cuando se fuerza el tráfico público a VLAN://untagged. Se considera terminado cuando management usa el VXLAN asignado y el almacenamiento secundario puede usar su propia red enrutada o etiquetada sin enrutamiento manual.

Escrito por el modelo de indexación a partir del texto del issue.