VLAN/dot1q over ethernet

Just curious, can't seem to find a definite answer, as googling "dot1q ethernet" is pretty ambiguous.

Is VLAN Tagging via 802.1q possible over regular ethernet links, or is this restricted to fastethernet and above? What, in general, are dependencies of dot1q trunking? I've been looking at gear and playing around with some at work, and some routers don't run the encap dot1q command....and I figured it was the IOS version, but I'm not sure.

What should I look for to make sure dot1q is supported? More generally, what are the base requirements to run dot1q, and subsequently, inter-VLAN routing, which is what I'm getting at in the first place.

Find more posts tagged with

Free for TechExams community: Cybersecurity salary guide

Compare cert salaries and plan your next career move

Button

Comments

hypnotoad

dot1q is an ethernet-centric idea. You cant do dot1q in a T1 or something like that. So the first thing you need is an ethernet environment.

10 meg ethernet can support dot1q. Many ethernet interfaces on older routers are 10 megabit. 100 and 1000 can too.

The basic requirement for dot1q tagging is a switch that supports VLANs. The manufacturer will advertise VLAN Trunking, or Dot1Q, or something like that. It's found on most commercial switches but not small office/home office ones. C

That being said, VLANs are a Layer 2 idea and they separate out networks, so to get the VLANs to communicate with each other, you need a Layer 3 device. This can be a router or a L3 switch. The router/L3switch takes packets (it operates at layer 3) and routes them to the other VLANis f that is their destination.

For example, create 2 VLANs on your L2 HP switch (or anyone, including cisco), then tell a 2610XM's FE that it is part of those VLAN/subnets. It will send packets back and forth. This is called Router on a Stick. The way most people do it nowadays is to just use an L3 switch.

BTW, Cisco used to have a proprietary method of VLANning called ISL. It's on most older routers but deprecated in newer machines. It's for only-cisco networks. I believe it's still part of the CCNA exam.

mikej412

You can do QinQ or 802.1q tunneling to extend your layer 2 Ethernet between two sites.

Mierdin

What about routers? Can only certain IOS versions support it? And still run over 10Mb links?

I have extensive knowledge of vlans and how they're configured, and that they're an ethernet concept. I understand all that, but whenever I get out of the sim and try to configure a device, I find out that specific router doesn't support dot1q for one reason or another.

I'm just trying to do router on a stick, and to do it properly, a dot1q trunk to a router is required. Instead of taking chances with the hardware I purchase, I'm asking what I should look for to ensure dot1q is supported.

Forsaken_GA

Mierdin wrote: »

What about routers? Can only certain IOS versions support it? And still run over 10Mb links?

I have extensive knowledge of vlans and how they're configured, and that they're an ethernet concept. I understand all that, but whenever I get out of the sim and try to configure a device, I find out that specific router doesn't support dot1q for one reason or another.

I'm just trying to do router on a stick, and to do it properly, a dot1q trunk to a router is required. Instead of taking chances with the hardware I purchase, I'm asking what I should look for to ensure dot1q is supported.

dot1q used to not be supported on 10 meg links, this is why most RoAS guides will say fastethernet is required. Cisco also used to not support full duplex on 10 meg links as well, so things have come a long way

I'm not sure when the software changeover occurred to allow dot1q on 10meg (translation - I don't care enough to actually go look it up

), but yes, older software will not support dot1q on the slower links, and newer will.

Your best bet is to boot the image you're going to be using up in gns3/dynamips and see if the commands are there, or make sure you don't buy anything with a 10 meg interface

mikej412

Forsaken_GA wrote: »

I'm not sure when the software changeover occurred to allow dot1q on 10meg (translation - I don't care enough to actually go look it up ), but yes, older software will not support dot1q on the slower links, and newer will.

A link to the Cisco doc is in the Forum FAQ

802.1Q Encapsulation Support on Cisco 2600/3600 Series Routers

802.1Q encapsulation is now available on the built-in 10BaseT Ethernet interfaces of the Cisco 2610, 2611, and 2612 with Cisco IOS software 12.2(2)T and subsequent releases. Although this feature has been available on the Cisco 2600/3600 series since the release of Cisco IOS 12.1(5)T, support was previously limited to Fast Ethernet interfaces only. 802.1Q is not supported on any other Cisco 2600/3600 series 10BaseT Ethernet interface.

The 1720 routers are the only routers with 100Mb Fast Ethernet interfaces that do NOT support trunking. I've found that link a few times, but not tonight.

Edit: I totally zoned out reading the original post. Now if you'd said Router-on-A-Stick....

Mierdin

mikej412 wrote: »

A link to the Cisco doc is in the Forum FAQ

Thanks! That link is exactly what I wanted.

I don't remember which router models specifically I was using when I ran into problems, but I figured it was more an issue with the IOS version than the router itself, and the routers I traditionally have access to are in a "junk" closet, since they've been retired from service, so the IOS versions are probably a bit dated.

Thanks for the help! This will help a bunch.

Mierdin

mikej412 wrote: »

A link to the Cisco doc is in the Forum FAQ

802.1Q Encapsulation Support on Cisco 2600/3600 Series Routers

Okay - sorry to drag this up again but I got home from holiday and I've been able to get more information specific to my situation.

R1#show version
Cisco Internetwork Operating System Software
IOS (tm) C2600 Software (C2600-I-M), Version 12.3(22), RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2007 by cisco Systems, Inc.
Compiled Wed 24-Jan-07 16:48 by ccai
Image text-base: 0x80008098, data-base: 0x80CEA424

ROM: System Bootstrap, Version 11.3(2)XA4, RELEASE SOFTWARE (fc1)
ROM: C2600 Software (C2600-I-M), Version 12.3(22), RELEASE SOFTWARE (fc2)
....
System image file is "flash:c2600-i-mz.123-22.bin"

cisco 2610 (MPC860) processor (revision 0x203) with 28672K/4096K bytes of memory.
......
1 Ethernet/IEEE 802.3 interface(s)

As you can see from the above, its a 2610 with an integrated 10BaseT Ethernet port.

After perusing the Cisco documentation provided to me in the quoted text from the previous post, I read - under the "Availability" section:

802.1Q encapsulation on 2610, 2611, and 2612 built-in 10BaseT Ethernet ports is available starting in IOS 12.2(2)T and all supported subsequent releases.

As you saw in my router specs, I'm running IOS 12.3. According to the quotation above, I should meet the requirements. Yet, when I try to run the command, still a no-go.

R1(config)#int ethernet0/0
R1(config-if)#encapsulation dot1q 100
                            ^
% Invalid input detected at '^' marker.

R1(config-if)#encap?
% Unrecognized command

Now, I've tried ever since I regained access to the router to pursue different IOS versions (still a weak point for me) and I read somewhere that perhaps the "ipbase" version was required, which is a more feature-rich IOS version.
Now that you know what I'm running, see anything I didn't?

mikej412

You need at least an IP Plus feature set.

The i in your IOS file name means it's IP Routing feature set.

An s means Plus, so an is in the name would be IP Plus feature set (or IP Routing Plus).

A j means Enterprise, etc.

This where the link to the Cisco Feature Navigator comes in handy -- and the Cisco Partner Central IOS Packaging PDF (near the end of the doc) to decode the old file names.

alan2308

Mierdin wrote: »
R1(config)#int ethernet0/0
R1(config-if)#encapsulation dot1q 100
                            ^
% Invalid input detected at '^' marker.

R1(config-if)#encap?
% Unrecognized command
Now, I've tried ever since I regained access to the router to pursue different IOS versions (still a weak point for me) and I read somewhere that perhaps the "ipbase" version was required, which is a more feature-rich IOS version.
Now that you know what I'm running, see anything I didn't?

Another thing I see here is that you're trying to apply the encapsulation directly to the interface. What you want to do is create subinterfaces for each vlan and apply the settings there. You won't apply any configuration except for "no shutdown' to the actual interface in this case.

So let's say you have vlan's 1, 10 and 20 with subnets 192.168.1.0/24, 192.168.10.0/24 and 192.168.20.0/24, respectively where vlan 1 is the native vlan:

R1(config)interface eth0/0
R1(config-if)no shutdown
R1(config-if)interface eth0/0.1
R1(config-if)encapsulation dot1q 1 native
R1(config-if)interface eth0/0.10
R1(config-if)encapsulation dot1q 10
R1(config-if)ip address 192.168.10.1 255.255.255.0
R1(config-if)int eth0/0.20
R1(config-if)encap dot1q 20
R1(config-if)ip address 192.168.20.1 255.255.255.0

and some more reading on the topic:

Configuring InterVLAN Routing and ISL/802.1Q Trunking on a Catalyst 2900XL/3500XL/2950 Switch Using an External Router - Cisco Systems

Mierdin

Ooops, my bad.

I threw that together too hastily and didn't realize what I was doing when I was trying to show you my problem.

When running encap dot1q, I'm normally in subinterface mode. It is there that I get the error message.
I've done inter-VLAN routing a LOT in other labs and in sims, so I know better, just was too quick to get it copied and pasted in my post.

Thanks for pointing it out, though. Keeps me sharp.