encapulation dot1q X native

Unanswered Question
Nov 10th, 2007

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!

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Jon Marshall Sat, 11/10/2007 - 12:51

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

glen.grant Sat, 11/10/2007 - 12:52

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

davegibelli Sat, 11/10/2007 - 12:58

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!

glen.grant Sat, 11/10/2007 - 16:46

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.

Actions

This Discussion