Skip to content

Commit dfebc2c

Browse files
Update docs/upgrade/v1-5-x-to-v1-6-0.md
Co-authored-by: Jillian Maroket <[email protected]> Signed-off-by: Renuka Devi Rajendran <[email protected]>
1 parent db243c9 commit dfebc2c

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

docs/upgrade/v1-5-x-to-v1-6-0.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -203,7 +203,11 @@ Before upgrading to v1.6.x, perform the following steps:
203203
bridge vlan show
204204
```
205205
206-
For example, consider user having a mgmt interface configured with vlan `2021` during installation and have the following under `/oem/99_vlan-ifcfg.yaml`
206+
#### Upgrade Scenario
207+
208+
Starting with v1.6.0, only the primary VLAN ID is assigned to the `mgmt-br` bridge and the `mgmt-bo` interface, rather than the entire VLAN ID range (2–4094). Consequently, communications that use secondary VLANs on the `mgmt` interface are affected.
209+
210+
In the following example, a v1.5.x cluster was initially installed with a [primary VLAN interface](../install/harvester-configuration.md#installmanagement_interface) (VLAN ID: `2021`). To add a secondary VLAN interface (VLAN ID: `2113`), the `/oem/99_vlan-ifcfg.yaml` file was created on the management hosts with the following contents:
207211
208212
```
209213
stages:

0 commit comments

Comments
 (0)