From: Jung, Jin (jin.jung@lmco.com)
Date: Mon Mar 03 2003 - 11:07:39 GMT-3
I think this is IRB question,
You do not have to put IP addres on interface of R2, just create a BVI
interface on r2 and setup up IRB, BVI will provide Layer 3 routing function.
Jin jung...
-----Original Message-----
From: Bob Usa [mailto:boby2kusa@hotmail.com]
Sent: Saturday, March 01, 2003 2:35 AM
To: trust.hogo@sarcom.com; jhays@jtan.com; choyvick@cisco.com;
ccielab@groupstudy.com
Subject: RE: Question on 3550
Trunking the port will not make one subnet ping the other subnet without
layer three. trunking is a layer 2 protocol that allows a single port to
propagate traffic from different vlans. The packets are still in different
vlan identified by the vlan tag in the trunk encapsulation. So you've
bridge the two vlans (bridge-groups) in R2 you still don't have an ip to
ping. Layer 3 connectivity needs layer 3 address.
>From: trust.hogo@sarcom.com
>Reply-To: trust.hogo@sarcom.com
>To: jhays@jtan.com, choyvick@cisco.com, ccielab@groupstudy.com
>Subject: RE: Question on 3550
>Date: Fri, 28 Feb 2003 14:17:05 -0500
>
>Remember r2 has no IP address. That's the key to the question and I
>don't think the question requires you to put an IP on r2 interface
>connecting to port 2. I see it as 2 Vlans assigned the same subnet. The
>only way is to configure a trunk on r2 interface and create 2
>subinterfaces belonging to vlan1 and vlan2 and then bridge these two.
>
>Just thinking aloud I guess.
>
>-----Original Message-----
>From: Jonathan V Hays [mailto:jhays@jtan.com]
>Sent: Friday, February 28, 2003 12:24 PM
>To: 'Vickie Choy'; ccielab@groupstudy.com
>Subject: RE: Question on 3550
>
>
>Once you assign an IP address to a VLAN you can start thinking of the
>L3 switch as a many-ported router. The switch can route between the
>default vlan (vlan 1) and vlan 10 as follows:
>
>R4 140.10.1.4 (vlan 10)
>R6 140.10.1.6 (vlan 10)
>int vlan 10 140.10.1.7 (vlan 10)
> **switch routes between vlan 10 and vlan1**
>int vlan 1 140.11.12.7 (vlan 1)
>R2 140.11.12.2 (vlan 1)
>
>Here's the relevant link in the 3550 documentation.
>
>http://www.cisco.com/univercd/cc/td/doc/product/lan/c3550/12112cea/3550
>s
>cg/swint.htm#xtocid23
>
>
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
> > Of Vickie Choy
> > Sent: Friday, February 28, 2003 5:35 AM
> > To: ccielab@groupstudy.com
> > Subject: Question on 3550
> >
> >
> > Hi all,
> > -------------------------------
> > R4-------| port 4 port 2 |-----------R2
> > | 3550 |
> > R6-------| port 6 |
> > -----------------------------------
> >
> > Port 4 and port 6 belong to the same vlan vlan 10. Port 2 belong to
> > default vlan. Port 4 and 6 belong to the subnet 140.10.1.0/24, R4
> > has 140.10.1.4/24 and R6 has 140.10.1.6/24 on the Ethernet
> > interface. R2 has no IP address on the interface.
> >
> > Question is to create a command interface 140.10.1.7 on 3550 so that
> > R2, R4 and R6 be able to ping to that interface.
> >
> > If I create a SVI "int vlan 10" with ip address 140.10.1.7 only R4
> > and R6 can ping. If I configure an ip address say 140.11.12/24 on
> > the interface of R2, but is not allowed to configured a static route
> > on R2 to point to the 140.10.1.0/24 subnet. How to get R6 to be
> > able to ping to the command interface?
> >
> > Appreciate your input.
> >
> > Thanks
> >
> > Vickie
This archive was generated by hypermail 2.1.4 : Sat Apr 05 2003 - 08:51:31 GMT-3