RE: Bridging over frame relay cloud.

From: Ronnie Royston (RonnieR@xxxxxxxxxxxxxxxxx)
Date: Wed Dec 27 2000 - 21:34:47 GMT-3


   
I don't know your exact senario, but bridging over frame relay should look
something like,

      enet--R1 - - -FRAME SWITCH- - - R2--enet
1.1.1.1/24 1.1.1.2/24

Your config should look something like:

interface ethernet 0
 ip address 1.1.1.1 255.255.255.0
!
interface serial 0
 no ip address
 encapsulation frame-relay
 no frame inverse
 frame map bridge (R2) broad
 bridge-group 10
!
bridge crb
bridge 10 proto ieee

-----Original Message-----
From: fwells12 [mailto:fwells12@hotmail.com]
Sent: Wednesday, December 27, 2000 4:01 PM
To: ccielab@groupstudy.com
Subject: Re: Bridging over frame relay cloud.

They were active until I disabled ip routing as part of the bridging
procedures.

----- Original Message -----
From: Sanjeewa Alahakone <sanjeewa@cisco.com>
To: fwells12 <fwells12@hotmail.com>
Sent: Wednesday, December 27, 2000 3:19 PM
Subject: RE: Bridging over frame relay cloud.

> Just a quick thought (only), your FR map says status=deleted,
> I'm not sure whether it is normal
> have you checked your pvc values
> rgds
> Sanjeewa
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> fwells12
> Sent: Thursday, 28 December 2000 3:25 AM
> To: ccielab@groupstudy.com
> Subject: Re: Bridging over frame relay cloud.
>
>
> Thanks for your reply Ronnie,
> There are routers at the edge of the frame cloud on all four egress
points.
> The e-nets are on the far sides of the routers. The ingress interfaces
are
> all on the same subnet.
>
> I think it may be a problem with either spanning tree and the bridge
> priority issue. I am working on some different labs right now but will
take
> another look at this later.
>
>
> ----- Original Message -----
> From: Ronnie Royston <RonnieR@globaldatasys.com>
> To: 'fwells12' <fwells12@hotmail.com>
> Sent: Wednesday, December 27, 2000 7:57 AM
> Subject: RE: Bridging over frame relay cloud.
>
>
> > You indicated that each ethernet has its own subnet. The e-nets must be
> on
> > the same subnet for layer 2 connectivity w/out a (layer 3) router.
> >
> > -----Original Message-----
> > From: fwells12 [mailto:fwells12@hotmail.com]
> > Sent: Saturday, December 23, 2000 10:46 PM
> > To: ccielab@groupstudy.com
> > Subject: Bridging over frame relay cloud.
> >
> >
> > Hey guys, the archives were no help thus far...
> >
> > Here's the setup:
> >
> > Fully meshed frame cloud with four routers connected using LMI. Each =
> > router has an ethernet segment with a unique network. Serial interfaces
=
> > are all on one subnet, and could ping each other fine (expected result)
=
> > before the 'no ip routing' statement was introduced.
> >
> > I want to be able to bridge IP traffic between the four ethernets over =
> > the frame cloud. Thus far I cannot ping anything from anywhere.
> > The configs were taken right from the Cisco Bridging IBM and Network =
> > Solutions book. IOS is 11.3 on all routers and switch.
> >
> > Questions:
> > Do I need to do anything to the frame-cloud router?
> > Is there any need for additional frame-relay bridge statements ?
> > Should I do away with LMI and go with frame relay map statements =
> > instead?
> > Does using the ' frame-relay map bridge' statement disable LMI anyway?
> >
> > Thoughts appreciated.
> >
> > The following configs are on each router:
> >
> > no ip routing
> > bridge 1 protocol ieee
> >
> > int s0
> > bridge-group 1
> > frame-relay map bridge <s0- dlci> broadcast
> >
> > int e0
> > bridge-group 1
> >
> > This is the same on all routers:
> >
> > router1#sh frame map
> > Serial0 (up): bridge dlci 104(0x68,0x1880), static,
> > broadcast,
> > CISCO, status deleted =20
> >
> > Router3 is the only one to have any bridge mappings:
> > router3#sh bridge
> >
> > Total of 300 station blocks, 297 free
> > Codes: P - permanent, S - self
> >
> > Bridge Group 1:
> >
> > Address Action Interface Age RX count TX count
> > 0000.0c4a.1c13 forward Ethernet0 0 0 0
> > 0060.083c.564f forward Ethernet0 0 62 0
> > 0060.0897.bf6c forward Ethernet0 1 2 0
=20
> >
> >
> > NOTE: All routers have the statement 'We are the root of the spanning =
> > tree' in their respective show span outputs.
> >
> >
> >
> >
> >
> >



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:26:11 GMT-3