poddm commented on code in PR #563:
URL:
https://github.com/apache/cloudstack-documentation/pull/563#discussion_r2718008311
##########
source/installguide/configuration.rst:
##########
@@ -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.
Review Comment:
> it is recommended not to
configure a VLAN tag for this traffic type.
Why?
This note is critical and could use thorough documentation. If I'm
understanding correctly, if the vlan tag is provided cloudstack will create its
own bridge (`brbond0-###`). If its not provided then it will use a predefined
bridge.
Upgrading from 4.19 to 4.22 this change in behavior caused a lot of digging.
```
1-21 20:34:01,539 DEBUG [kvm.resource.BridgeVifDriver]
(AgentRequest-Handler-1:[]) (logid:be187ea6)
nic=[Nic:Storage-10.58.67.209-storage://###]
2026-01-21 20:34:01,540 DEBUG [kvm.resource.BridgeVifDriver]
(AgentRequest-Handler-1:[]) (logid:be187ea6) creating a vNet dev and bridge for
Storage traffic per traffic label cloud-brnnas
2026-01-21 20:34:01,540 DEBUG [kvm.resource.BridgeVifDriver]
(AgentRequest-Handler-1:[]) (logid:be187ea6) Executing command
[/usr/share/cloudstack-common/scripts/vm/network/vnet/modifyvlan.sh -v ### -p
bond0 -b brbond0-### -o add ].
2026-01-21 20:34:01,573 DEBUG [kvm.resource.BridgeVifDriver]
(AgentRequest-Handler-1:[]) (logid:be187ea6) Successfully executed process
[3482737] for command
[/usr/share/cloudstack-common/scripts/vm/network/vnet/modifyvlan.sh -v ### -p
bond0 -b brbond0-### -o add ].
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
