Skip to content

Commit cccb67e

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 052fae8 commit cccb67e

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
@@ -355,6 +355,20 @@ Basic Zone Configuration
355355
drag and drop traffic types onto the network. You can also change the
356356
network name if desired.
357357

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

0 commit comments

Comments
 (0)