RE: IE Lab 16 :Frame-relay bridging

From: De Pauw, Wim (Wim.DePauw@getronics.com)
Date: Fri Feb 22 2008 - 06:28:29 ARST


Hi,

Found the answer in config guide :

 you want to bridge IP, you must disable IP routing because IP routing
is enabled by default on the Cisco IOS software. You can enable IP
routing when you decide to route IP packets. To disable or enable IP
routing, use one of the following commands in global configuration mode,
as needed

gr
wim

-----Original Message-----
From: Todd, Douglas M. [mailto:DTODD@PARTNERS.ORG]
Sent: donderdag 21 februari 2008 19:08
To: De Pauw, Wim; ccielab@groupstudy.com
Subject: RE: IE Lab 16 :Frame-relay bridging

I'll take a stab:

We are using IRB which etitles one can bridge on one interface but route
on another. Thus we are not completely bridging and not completely
routing, brouting....

the bridge 1 bridge ip make the whole box bridge, thus the box will
ignore ip
packets:

http://cisco.com/en/US/docs/optical/15000r7_0/ethernet/guide/454_327/547
bridg.ht
ml

"Bridge CRB Mode

In bridge crb mode, the default sub-mode for every bridge group is to
bridge but not route the IP packets. This is similar to the no ip
routing mode behavior.
But with bridge crb, packet handling is configured not globally but for
the specific bridge group. You can selectively disable bridge groups to
block IP packets or configure fallback bridging for a group of routed
interfaces.

Concurrent routing and bridging is enabled with the global command
bridge crb.
Enabling bridge crb disables the other modes.

The following rules help describe packet handling in this mode:

*The command bridge x bridge ip (where x is a bridge-group number)
configures a bridge-group to bridge IP packets. Input interfaces and
sub-interfaces belonging to the bridge-group will follow the rules for
no IP routing mode.

*The command bridge x route IP (where x is a bridge-group number)
configures a bridge-group to ignore IP packets. Input interfaces and
sub-interfaces belonging to this bridge-group will follow the rules for
IP routing mode (Example 6-8).

*When you enable bridge crb with pre-existing bridge groups, it will
generate a bridge x route IP configuration command for any pre-existing
bridge groups with an interface configured for routing (configured with
an IP address). This is a precaution when crb is first enabled.

*All of the interfaces or subinterfaces belonging to a specific
bridge-group need consistent configuration in regards to configuring or
not configuring IP addresses. Mixing interfaces configured with IP
addresses and interfaces not configured with IP addresses in the same
bridge group can cause inconsistent or unpredictable routing at the
network level.

*Routing between interfaces or subinterfaces that do not belong to the
same bridge group could result in inconsistent network behavior. This
mode is for routing between members of a bridge-group, but never for
routing into or out of a bridge group. "

Douglas

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
wim.depauw@getronics.com
Sent: Wednesday, February 20, 2008 2:49 PM
To: ccielab@groupstudy.com
Subject: IE Lab 16 :Frame-relay bridging

Hi,

I just configured frame-relay bridging according to the IE lab
requirements but I got a question about it:

This is the setup :

R6----ETH------R1-----FR-------R2---ETH------BB2

 I configured bridging on R1/R2 with the following statements

bridge irb
int fa0/0
 bridge-group 1
int s0/0
 frame-relay map bridge 102 broadcast
 bridge-group 1

bridge 1 protocol ieee
bridge 1 route ip

I first tried with the command bridg1 bridge ip but this didn't work . I
changed it bridge1 route ip and then all hosts were reachable.

Any idea why the bridge 1 bridge ip doesn't work ?

According to the doc cd you specify the protocols you want to route with
the command bridge 1 route XXX but the question states you should bridge
and not route....
gr
wim

No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.516 / Virus Database: 269.20.8/1289 - Release Date:
2/20/2008 10:26 AM
 

No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.516 / Virus Database: 269.20.8/1289 - Release Date:
2/20/2008 10:26 AM
 

The information transmitted in this electronic communication is intended
only for the person or entity to whom it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of or taking of any action in reliance upon
this information by persons or entities other than the intended
recipient is prohibited. If you received this information in error,
please contact the Compliance HelpLine at 800-856-1983 and properly
dispose of this information.



This archive was generated by hypermail 2.1.4 : Sat Mar 01 2008 - 16:54:49 ARST