an interface whose trunk encapsulation is “auto” can not be configured to “trunk” mode.,

0
66
interface
finger, touch, hand @ Pixabay

Auto encapsulated interfaces can not be configured as trunks. Configuration of an auto-encapsulated interface to trunk mode is not supported. It is possible to configure an auto-encapsulated interface as not trunking, but configured this way the interface will always be a member of one VLAN. Existing interfaces that have been configured as trunks may retain their original configuration when they are encapsulated with “auto.” This could result in some network administrators being unaware that these interfaces do not support other configurations such as 802.q tagging or subinterfaces. In addition, if you assign IP addresses on an interface set up for automatic encapsulation and then later put it into trunk mode, you might encounter problems because all of your existing IP-address assignments would no longer apply (since the said interface now belongs to more than one VLAN). Therefore, it is recommended that you use the “auto” encapsulation only for interfaces which are not trunking, or configure them to be a member of one VLAN. Configuration of an auto-encapsulated interface to trunk mode is not supported. This could result in some network administrators being unaware that these interfaces do not support other configurations such as 802.q tagging or subinterfaces. In addition, if you assign IP addresses on an interface set up for automatic encapsulation and then later put it into trunk mode, you might encounter problems because all of your existing IP-address assignments would no longer apply (since the said interface now belongs to more than one VLAN). Therefore, it is recommended that you use the “auto”

LEAVE A REPLY

Please enter your comment!
Please enter your name here