11-10-2007 12:49 PM - edited 03-03-2019 05:47 AM
interface f0/0.1
encapulation dot1q X native
x can be any number right?
The actual number has no effect because the packet is native and thus has no tag!
11-10-2007 12:51 PM
Hi
The x can be any vlan number yes but if you are specifying a particular vlan number make sure it is the same on both ends of the link.
You are correct in that the native vlan is the vlan that is not tagged across an 802.1q trunk.
HTH
Jon
11-10-2007 12:52 PM
no it doesn't matter as long as it matches the switch native on the other end .
11-10-2007 12:58 PM
Glen is correct, matching vlans at each end only matters if the vlan spans the intermediate switch as this could cause routing loops.
I am just trying to get this straight in my head! We have to specify a vlan number but it can be any number because it has absolutely NO effect whatsoever, weird!
11-10-2007 04:46 PM
It is best to use some kind of scheme though to your addressing say the subnet is like 192.168.85.0 , it would be a lot easier to remember and troubleshoot if you made the vlan number like vlan 85 . Just makes it easier if there is some kind of commonality between the vlan number and the subnet number . If you are only dealing with a few vlans then it probably doesn't matter.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: