[V13] Veeam Software Appliance VLAN configuration

[JasonOrchardIMNZ]

Veeam Software Appliance 13

Observation: Missing VLAN Configuration Capability During or After Installation

During the installation process—or in the post-installation configuration via the management interface on port 10443—there is currently no option to assign VLANs to the Ethernet interface. As a result, all traffic is untagged or implicitly tagged with the default VLAN ID 1.

This limitation requires VLAN tagging to be enforced at the physical switch port level. However, this approach is not always viable, particularly in environments where the switch port expects tagged traffic from the host or where multiple VLANs are required for segmentation.

Request for Enhancement: Are there any plans to introduce support for VLAN configuration:

As part of the initial installation workflow?
Or as a post-installation option within the management interface?
This capability would significantly improve deployment flexibility, especially in enterprise or multi-tenant environments.

[jasonede]

Seconded. We run some tagged vlan ports to our VBR server to maximise use of the 10Gbps NIC's so be really good to be able to set on install and edit after.

[HannesK]

Hello,
VLANs and bonding are currently only in the "advanced" network configuration where the Host Management Console opens nmtui.

We plan to bring VLAN & bonding configuration into the web interface, but no timeline yet.

Best regards
Hannes

[Gostev]

@HannesK please add to VSA FAQ draft.

[HannesK]

done

[JasonOrchardIMNZ]

Hello,
VLANs and bonding are currently only in the "advanced" network configuration where the Host Management Console opens nmtui.

We plan to bring VLAN & bonding configuration into the web interface, but no timeline yet.

Best regards
Hannes

I’ve tried to add vlan and bonding but I get permission denied, even with root admin group enabled.

I’m unable run nmtui into root (SU -) or sudo veeamadmin
As veeamadmin isn’t part of sudo group.

While understand the preharding is important
Basic network functionality is also equally as important.

[HannesK]

Hello,
sounds like a bug. Did you do that during installation / first boot wizard or after the installation?

Best regards
Hannes

[JasonOrchardIMNZ]

@hannesk
I’ve tried changing these both post and pre installation.
I’ve tried with both ova install and with clean install using iso with same results.

[HannesK]

hmm okay, can you maybe describe step by step what you did? I do not get "permission denied" when configuring the network in the "first boot wizard". When exactly does that error appear?

I did the following in the first boot wizard:
1. configure nothing with the Veeam Host Management Console and only use "advanced"
2. tick the checkbox on all physical interfaces I want to use to start automatically
3. create bond with two interfaces with active / backup (I don't have LACP)
4. create VLAN on top of that bond interface and assign IP address there
5. continue with the wizard
6. I noticed that my network connection went down for some seconds, but it came back. So I got a warning at the NTP step
7. finish the wizard with credential settings