Timeline for Tagged-only VLANs
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 11, 2022 at 10:45 | comment | added | Zac67♦ |
Yes, switchport mode trunk is easy, but Procurves/HPE Provision/Aruba don't do it that way. They require explicit tagged/untagged configuration (which I actually find more transparent) or GVRP/MVRP.
|
|
| Feb 11, 2022 at 10:38 | comment | added | Soulimane Mammar | @Zac67 I know but it's more simpler to configure a port as trunk by a single command and then eventually forbid/allow some vlans on it (if there is a need) than a bunch of commands that are error prone. Network admin's life is already complicated, no need to add on that | |
| Feb 11, 2022 at 7:16 | comment | added | Zac67♦ | @SoulimaneMammar Mostly true, but tagging is generally required for trunk ports. | |
| Feb 11, 2022 at 6:45 | comment | added | Soulimane Mammar | The most general use case of vlans is quite simple. Affect ports to different vlans and designate as trunks those used to interconnect switches and/or vlan-aware hosts. But some switch vendors complicate things (probably for more flexibility) the configuration task by introducing notions like ingress vlan egress vlan, tagged/untagged port ...etc. All these can confuse even a skilled network admin | |
| Feb 10, 2022 at 9:48 | history | edited | Zac67♦ | CC BY-SA 4.0 |
added 61 characters in body
|
| Feb 10, 2022 at 9:40 | history | edited | Zac67♦ | CC BY-SA 4.0 |
deleted 2 characters in body
|
| Feb 10, 2022 at 7:59 | comment | added | user815129 | Ah.. didn't think about vlan aware things.. and yes, multi-switch vlans.. thanks | |
| Feb 10, 2022 at 7:59 | vote | accept | user815129 | ||
| Feb 10, 2022 at 7:43 | history | answered | Zac67♦ | CC BY-SA 4.0 |