Thanks for confirming. Also while on subject on VLAN tagging, should the NATIVE VLAN (1) be tagged or untagged on the LACP link, and tagged or untagged on the regular access ports?
I know this question is often asked, but I am confused as to whether if it should be.
As has been said, you loose connectivity because the newly formed logical interface has no config. But if you before hand make that logical interface by using the trunk command with an unused interface, you can configure the vlans in advance. Then remove the additional physical interface.
There are no rules about what should be untagged on a physical or logical interface except that only one vlan can be untagged and on most switch OSs, there must be one set (default is 1). Note that if different at the two end you end up with log entires in some switches. In comware you can have no untagged vlan but for your switch you will always have one even if not configured.
I like the best practice of tagging all used vlans. It makes them clear in the config and leaves the untagged for special use cases. Vlan1 is never used anywhere so this unconfigured vlan is passed without effect.
© Copyright 2023 Hewlett Packard Enterprise Development LPAll Rights Reserved.