From: Ken Diliberto (ken@kdmd.net)
Date: Sat Jul 26 2003 - 18:35:24 GMT-3
You have two options if you want to route with a 3550 (not counting an
external router):
1 - Assign a port to a VLAN and create the VLAN interface to route.
Downside: This gives you another VLAN to worry about pruning from your
trunks.
Upside: You can have multiple ports on the same VLAN which could
include trunk ports to other switches.
2 - Assign an IP address to the port.
Downside: No other ports on the 3550 can use that subnet.
Upside: Great for making point-to-point connections with other routers.
This method is a good layer 3 boundary that will keep Spanning Tree
from bringing down all the ports on the 3550 during convergence.
There are many more Upside/Downside combinations that really depend on
the situation.
The ability to configure a port as a switch port or a router port also
exists on the Catalyst 4000/4500/6500 boxes running IOS. For some
situations, I prefer the router port over the switch port with a VLAN
for routing.
Ken
>>> "Jonathan V Hays" <jhays@jtan.com> 07/25/03 05:36PM >>>
I think you mean that a routed-port does *not* have a VLAN number
associated with it, correct?
[snip]
Yes. I have seen little use for the routed port, other than playing
around with scenarios for the lab test. The SVI seems much more useful
and flexible.
[snip]
This archive was generated by hypermail 2.1.4 : Wed Aug 06 2003 - 06:52:54 GMT-3