This is an automated email from the ASF dual-hosted git repository.

abhisar pushed a commit to branch 4.20
in repository https://gitbox.apache.org/repos/asf/cloudstack-documentation.git


The following commit(s) were added to refs/heads/4.20 by this push:
     new a39b1e93 kvm,physical network: change in storage traffic behaviour 
(#563)
a39b1e93 is described below

commit a39b1e93111a73f265e64b384a09b2b546b73710
Author: Abhishek Kumar <[email protected]>
AuthorDate: Wed Apr 15 16:07:41 2026 +0530

    kvm,physical network: change in storage traffic behaviour (#563)
    
    * kvm,physical network: change in storage traffic behaviour
    
    Related: 
https://github.com/apache/cloudstack/issues/11634#issuecomment-3291359705
    
    Signed-off-by: Abhishek Kumar <[email protected]>
    
    * Update source/installguide/configuration.rst
    
    ---------
    
    Signed-off-by: Abhishek Kumar <[email protected]>
---
 source/installguide/configuration.rst | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/source/installguide/configuration.rst 
b/source/installguide/configuration.rst
index 9a492ba9..b065965b 100644
--- a/source/installguide/configuration.rst
+++ b/source/installguide/configuration.rst
@@ -353,6 +353,18 @@ 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.
+
+      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

Reply via email to