Skip to content

Commit 12173c7

Browse files
committed
kvm,physical network: change in storage traffic behaviour
Related: apache/cloudstack#11634 (comment) Signed-off-by: Abhishek Kumar <[email protected]>
1 parent 1b8f2ca commit 12173c7

File tree

1 file changed

+14
-0
lines changed

1 file changed

+14
-0
lines changed

source/installguide/configuration.rst

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -353,6 +353,20 @@ Basic Zone Configuration
353353
drag and drop traffic types onto the network. You can also change the
354354
network name if desired.
355355

356+
.. note::
357+
Starting with CloudStack version 4.21.0 and 4.20.2, the behavior of
358+
VLAN and networking configuration for the storage traffic type in KVM
359+
zones has changed. When a VLAN tag is specified for storage traffic,
360+
a new vNet interface will be created on the storage bridge. If a
361+
dedicated bridge is used for storage traffic, it is recommended not to
362+
configure a VLAN tag for this traffic type.
363+
364+
This change in behavior may require administrators to review their
365+
existing configurations. For environments where a dedicated storage
366+
bridge is used and the creation of an additional vNet interface is not
367+
desired, the traffic type configuration must be updated to clear the
368+
VLAN tag.
369+
356370
#. Assign a network traffic label to each traffic type on the physical
357371
network. These labels must match the labels you have already defined
358372
on the hypervisor host. To assign each label, click the Edit button

0 commit comments

Comments
 (0)