Router on a stick

[polm]

I am setting up a simple "router on a stick" with a 2611 and a 3550. I was planning on using SubInterfaces to allow routing between vlans, but I noticed that the 2611 has an "interface vlan" command.

How could I use the "interface vlan" command as opposed to using sub-interfaces in order to allow routing between multiple vlans ?

 

[ScottMac]

What versions of IOS are you running?

Scott

 

[polm]

Originally posted by: ScottMac
What versions of IOS are you running?

Scott

12.1(20)

 

[spidey07]

there was a post that described this in great detail, search for stick.

use sub interfaces and trunk

 

[polm]

Originally posted by: spidey07
there was a post that described this in great detail, search for stick.

use sub interfaces and trunk

This one ?

I'm starting to question the abilities of my little 2611 now. I have encapsulation (isl & dot1q) options available in the sub-interface config menu.

I am currently only routing for 1 vlan via the E0/0 interface, and therefore I have not enabled any trunking options. Guess I'll find out when I try to configure the trunk.

I still don't understand why there is a "Vlan" option in the interface config menu. Why would the router have an option for SVI if the best practice is to use sub-if ?

 

[spidey07]

Originally posted by: polm

Originally posted by: spidey07
there was a post that described this in great detail, search for stick.

use sub interfaces and trunk

This one ?

I'm starting to question the abilities of my little 2611 now. I have encapsulation (isl & dot1q) options available in the sub-interface config menu.

I am currently only routing for 1 vlan via the E0/0 interface, and therefore I have not enabled any trunking options. Guess I'll find out when I try to configure the trunk.

I still don't understand why there is a "Vlan" option in the interface config menu. Why would the router have an option for SVI if the best practice is to use sub-if ?

because depending on the hardware you can have VLAN interfaces (think a 8/16 port switch in the NM slot)

this is what you're trying to do for router on a stick.
int f0/0
encap 802.1q
no ip add

int f0/0.50
ip add
<some kind of command to specify the tagging>

int f0/0.100
<some kind of command to specify the tagging>

so you are specifying the encapsulation/framing on the [/b]physical interface/layer2 [/b] and then using sub interfaces to differentiate layer3 and set the mappings.

make sense?

if you search cisco for router on a stick I'm sure you'll find more than you ever wanted to know.

 

[polm]

Originally posted by: spidey07

Originally posted by: polm

Originally posted by: spidey07
there was a post that described this in great detail, search for stick.

use sub interfaces and trunk

This one ?

I'm starting to question the abilities of my little 2611 now. I have encapsulation (isl & dot1q) options available in the sub-interface config menu.

I am currently only routing for 1 vlan via the E0/0 interface, and therefore I have not enabled any trunking options. Guess I'll find out when I try to configure the trunk.

I still don't understand why there is a "Vlan" option in the interface config menu. Why would the router have an option for SVI if the best practice is to use sub-if ?

because depending on the hardware you can have VLAN interfaces (think a 8/16 port switch in the NM slot)

this is what you're trying to do for router on a stick.
int f0/0
encap 802.1q
no ip add

int f0/0.50
ip add
<some kind of command to specify the tagging>

int f0/0.100
<some kind of command to specify the tagging>

so you are specifying the encapsulation/framing on the [/b]physical interface/layer2 [/b] and then using sub interfaces to differentiate layer3 and set the mappings.

make sense?

if you search cisco for router on a stick I'm sure you'll find more than you ever wanted to know.

gotcha. I guess I was thinking that the OS shouldn't give me commands to use that don't apply to my current hardware.

 

[spidey07]

HA!

You have much to learn daniel-san.

Just because the command is there doesn't mean it applies. IOS is still software and software has mistakes. They can't very well push out software applicable for every single combination of modular hardware out there. So IOS for a 2600 covers just about every hardware combination.

 

[polm]

Originally posted by: spidey07
HA!

You have much to learn daniel-san.

Just because the command is there doesn't mean it applies. IOS is still software and software has mistakes. They can't very well push out software applicable for every single combination of modular hardware out there. So IOS for a 2600 covers just about every hardware combination.

clearly. Oh well, back to painting the fence. Or was it, waxing the car? ;-)