diff --git a/doc/vlan/switchport-mode-support/Switchport Mode and VLAN CLI Enhancement.md b/doc/vlan/switchport-mode-support/Switchport Mode and VLAN CLI Enhancement.md index 5c943c39d6..29d5688e67 100644 --- a/doc/vlan/switchport-mode-support/Switchport Mode and VLAN CLI Enhancement.md +++ b/doc/vlan/switchport-mode-support/Switchport Mode and VLAN CLI Enhancement.md @@ -1,3 +1,4 @@ + # Switch Port Modes and Vlan CLI Enhancement @@ -14,6 +15,9 @@ |0.4| Addition of Use Cases, Db Migrator and Config-Db Enchanements| [Muhammad Hamza Iqbal](https://github.com/ham-xa)| [Rida Hanif](https://github.com/ridahanif96) , [Umar Asad](https://github.com/MuhammadUmarAsad), [Hafiz Mati ur Rehman](https://github.com/Mati86) & [Arsalan Ahmad](https://github.com/ahmadarsalan/)| 06 Mar 2023| |0.5| Detailed Examples Section | [Muhammad Hamza Iqbal](https://github.com/ham-xa)| [Rida Hanif](https://github.com/ridahanif96) , [Umar Asad](https://github.com/MuhammadUmarAsad), [Hafiz Mati ur Rehman](https://github.com/Mati86) & [Arsalan Ahmad](https://github.com/ahmadarsalan/)| 05 May 2023| + + + ## Table of Contents @@ -521,12 +525,26 @@ admin@sonic:~$ show int switchport status **4.** Untagged Vlan Member Assignment on Access Port +a) One Untagged Vlan member can be added on access port by using following command: + ``` admin@sonic:~$ sudo config vlan member add 2 -u Ethernet0 ``` +b) Adding a Tagged Vlan Member on Access Port + + If a VLAN member is initially added as an untagged member and then later added as a tagged member, this action is not permitted and will result in the following error being displayed: + +``` +admin@sonic:~$ sudo config vlan member add 2 Ethernet0 +``` + + + +**Note: This is exisiting VLAN funcationality, This HLD has not proposed any changes/modifications on exisiting behavior of VLAN.** + **5.** Multiple Untagged Vlan Member Assignment on Access Port Ethernet0 is in Access mode, it can have only 1 untagged member. Configuring More than 1 untagged member on Access Port will show following error: @@ -547,10 +565,20 @@ Ethernet0 is in Access mode, IP assignment on the access port is not allowed. Co **8.** Change Mode from Access to Routed -Ethernet0 is in Access mode, switching an access port to routed is not possible until it has an untagged member. Changing mode from access to routed will show following error: +a) Ethernet0 is in Access mode, switching an access port to routed is not possible until it has an untagged member. Changing mode from access to routed will show following error: +b) Ethernet0 is in Access mode, in order to change mode from access to routed, user first has to remove untagged member assigned to it. +After removal of vlan membership, mode can be changed by using switchport mode command as show below. +Here, in example Interface Ethernet0 is in "routed" mode which means it has no VLAN membership. It may not have ip address configured either and still qualify as mode "routed". This can be verified by config_db as well after changing mode to "routed" as show below: + + + + + + +**Note: This works in the same way for PortChannels as they do for physical ports.** **9.** Change Mode from Access to Trunk @@ -587,47 +615,77 @@ admin@sonic:~$ sudo config interface ip remove Ethernet4 10.0.0.2/31 admin@sonic:~$ sudo config switchport mode Trunk Ethernet4 ``` + **3.** Untagged Vlan Member Assignment on Trunk Port +a) Adding one Untagged Member on Trunk port is allowed. This can be done by follwing command: + ``` admin@sonic:~$ sudo config vlan member add 3 -u Ethernet4 ``` +b) Adding a Tagged Vlan Member on Trunk Port + +If a VLAN member is initially added as an untagged member and then later added as a tagged member, this action is not permitted and will result in the following error being displayed: + +``` +admin@sonic:~$ sudo config vlan member add 3 Ethernet4 +``` + + +**Note: This is existing VLAN functionality, This HLD has not proposed any changes/modifications on exisiting behavior of VLAN.** + **4.** Multiple Untagged Vlan Member Assignment on Trunk Port -Ethernet4 is in Trunk mode, it can have only 1 untagged member. Configuring More than 1 untagged member on trunk Port will show following error: +Ethernet4 is in Trunk mode, it can have only 1 untagged member. Configuring More than 1 untagged member on trunk Port will show following error: -**5.** Tagged Vlan Member Assignment on Trunk Port +**5.** Single Tagged Vlan Member Assignment on Trunk Port + +Ethernet4 is in trunk mode, it can have single tagged member. Configuring tagged member on trunk Port will show following: -Ethernet4 is in trunk mode, it can have multiple tagged members. Configuring tagged member on trunk Port will show following + + + +**6.** Tagged Vlan Member Assignment on Trunk Port + +Ethernet4 is in trunk mode, it can have multiple tagged members. Configuring tagged member on trunk Port will show following: -**6.** IP Assignment on Trunk Port +**7.** IP Assignment on Trunk Port Ethernet4 is in Trunk mode, IP assignment on the Trunk port is not allowed. Configuring IP Assignment on Trunk Port will show following error: -**7.** Change Mode from Trunk to Routed +**8.** Change Mode from Trunk to Routed -Ethernet4 is in Trunk mode, Changing Trunk port to routed is not possible until it has an untagged and tagged members. Changing Trunk to routed will show following error: +a) Ethernet4 is in Trunk mode, Changing Trunk port to routed is not possible until it has an untagged and tagged members. Changing Trunk to routed will show following error: - -**8.** Change Mode from Trunk to Access + +b) Ethernet4 is in trunk mode, in order to change mode from trunk to rounted, user first has to remove untagged and tagged member assigned to it. After removal of vlan membership, mode can be changed by using switchport mode command as show below. +Here, in example Interface Ethernet4 is in "routed" mode which means it has no VLAN membership. It may not have ip address configured either and still qualify as mode "routed". This can be verified by config_db as well after changing mode "routed" as show below: + + + + + +**Note: This works in the same way for PortChannels as they do for physical ports.** + +**9.** Change Mode from Trunk to Access Ethernet4 is in Trunk mode, Changing Trunk port to access is possible and its untagged members wll retain. Changing Trunk to access will show following: - + * PortChannel Configurations