Skip to content

kvm,physical network: change in storage traffic behaviour #563

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

kvm,physical network: change in storage traffic behaviour #563

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions source/installguide/configuration.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -355,6 +355,20 @@ Basic Zone Configuration
drag and drop traffic types onto the network. You can also change the
network name if desired.

.. note::
Starting with CloudStack version 4.21.0 and 4.20.2, the behavior of
VLAN and networking configuration for the storage traffic type in KVM
zones has changed. When a VLAN tag is specified for storage traffic,
a new vNet interface will be created on the storage bridge. If a
dedicated bridge is used for storage traffic, it is recommended not to
configure a VLAN tag for this traffic type.
Copy link
Contributor

@rajujith rajujith Sep 16, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it is recommended not to
configure a VLAN tag for this traffic type

I think we should remove this statement, VLAN can be used for storage traffic, whether the bridge is dedicated to storage or it's used for other traffic as well.


This change in behavior may require administrators to review their
existing configurations. For environments where a dedicated storage
bridge is used and the creation of an additional vNet interface is not
desired, the traffic type configuration must be updated to clear the
VLAN tag.

#. Assign a network traffic label to each traffic type on the physical
network. These labels must match the labels you have already defined
on the hypervisor host. To assign each label, click the Edit button
Expand Down