From: Bob Usa (boby2kusa@hotmail.com)
Date: Sat Mar 01 2003 - 04:07:08 GMT-3
Fallback Bridging is only supported for non-IP protocols. It does not make
sense to bridge two vlans for IP when vlan-ing can do a better job. Tha's
what the switch is for.
http://www.cisco.com/univercd/cc/td/doc/product/lan/c3550/12112cea/3550scg/swfallbk.htm#xtocid4
This chapter describes how to configure fallback bridging (VLAN bridging) on
your Catalyst 3550 switch. With fallback bridging, you can forward non-IP
packets that the switch does not route between VLAN bridge domains and
routed ports.
>From: "Michael Snyder" <msnyder@revolutioncomputer.com>
>Reply-To: "Michael Snyder" <msnyder@revolutioncomputer.com>
>To: <trust.hogo@sarcom.com>
>CC: <ccielab@groupstudy.com>
>Subject: RE: Question on 3550
>Date: Fri, 28 Feb 2003 16:29:01 -0600
>
>Can you post that config?
>
>I've tried to bridge two vlans on a 3550, but couldn't get traffic to
>flow. Everything looked ok, just across vlan pings wouldn't work.
>
>-----Original Message-----
>From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
>trust.hogo@sarcom.com
>Sent: Friday, February 28, 2003 1:17 PM
>To: jhays@jtan.com; choyvick@cisco.com; ccielab@groupstudy.com
>Subject: RE: Question on 3550
>
>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/3550s
>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:30 GMT-3