From: Jonathan V Hays (jhays@jtan.com)
Date: Fri Jul 25 2003 - 21:36:58 GMT-3
I think you mean that a routed-port does *not* have a VLAN number
associated with it, correct?
http://www.cisco.com/univercd/cc/td/doc/product/lan/c3550/12113ea1/3550s
cg/swint.htm#1035057
quote:
A routed port is a physical port that acts like a port on a router; it
does not have to be connected to a router. A routed port is not
associated with a particular VLAN, as is an access port. A routed port
behaves like a regular router interface, except that it does not support
VLAN subinterfaces. Routed ports can be configured with a Layer 3
routing protocol.
end quote.
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.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Deepesh Chouhan
Sent: Friday, July 25, 2003 8:27 PM
To: Jonathan V Hays; ccielab@groupstudy.com
Subject: RE: Routed ports on the 3550
If you disect routed-port it is actually a
SVI with vlan number 1006-4009 (reserved VLAN).
So from layer 3 perspective they are same.
From layer 2 perspective - there are some differences like mac-address
etc.
(routed port inherits ports mac-address)
I think routed ports gives you an option to convert a 50 port switch to
a 50
port router with physical interfaces (SVI are virtual interfaces)
But i agree with you - i haven't seen any difference either in L3
perspective
thanks
deepesh
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> Jonathan V Hays
> Sent: Friday, July 25, 2003 4:17 PM
> To: ccielab@groupstudy.com
> Subject: RE: Routed ports on the 3550
>
>
> Since an SVI (switched virtual interface) is more flexible than a
routed
> port and doesn't use up a physical interface, the important question
is
> this - is there anything the routed port can do that the SVI cannot?
>
>
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> Deepesh Chouhan
> Sent: Friday, July 25, 2003 6:24 PM
> To: MMoniz; pierreg; ccielab@groupstudy.com
> Subject: RE: Routed ports on the 3550
>
>
> I would use a router port to get routes from other routers (like ospf,
> rip
> routes).
>
> This will be then used by VLAN traffic
> Routed port can also be used as an uplink to backbone (exit point for
> vlans)
>
> thanks
> deepesh
>
>
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf
Of
> > MMoniz
> > Sent: Friday, July 25, 2003 2:06 PM
> > To: pierreg; ccielab@groupstudy.com
> > Subject: RE: Routed ports on the 3550
> >
> >
> > You would use it just like you would on a router. Connect it to a
> layer 2
> > only switch and have that
> > as the default gateway is one use. Connect it to another router
> > on the same
> > subnet is another.
> >
> > HTH
> >
> >
> >
> >
> >
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf
Of
> > pierreg
> > Sent: Friday, July 25, 2003 5:00 PM
> > To: ccielab@groupstudy.com
> > Subject: Routed ports on the 3550
> >
> >
> > "A routed port is a physical port that acts like a port on a
router;
> it
> > does not have to be connected to a router."
> >
> > I don't get it! A routed port not connected to a router. How
> > would you use
> > the port then?
> >
> > http://www.cisco.com/univercd/cc/td/doc/product/lan/c3550/12111ea1
> /3550scg/s
> wint.htm#xtocid9
>
> Thanks,
>
> Pierre-Alex
>
>
>
This archive was generated by hypermail 2.1.4 : Wed Aug 06 2003 - 06:52:53 GMT-3