Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

encapulation dot1q X native

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!

4 REPLIES
Hall of Fame Super Blue

Re: encapulation dot1q X native

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

Purple

Re: encapulation dot1q X native

no it doesn't matter as long as it matches the switch native on the other end .

New Member

Re: encapulation dot1q X native

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!

Purple

Re: encapulation dot1q X native

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.

181
Views
0
Helpful
4
Replies