From: Brian McGahan (brian@cyscoexpert.com)
Date: Fri Sep 13 2002 - 12:23:45 GMT-3
Not necessarily. DLSw has nothing to do with transporting L3
(routable) traffic. DLSw is basically tunneling your non-routable
traffic over the IP cloud. Although the DLSw peering session itself can
be L3, the actual traffic you are transporting is not. Therefore, the
following is a valid config.
R1#
Dlsw local-peer peer-id 1.1.1.1
Dlsw remote-peer 0 tcp 2.2.2.2
Dlsw bridge-group 1
Bridge protocol IEEE
!
Interface Ethernet 0
Ip address 1.1.1.1 255.255.255.0
Bridge-group 1
!
IRB and DLSw are not directly related.
HTH
Brian McGahan, CCIE #8593
Director of Design and Implementation
brian@cyscoexpert.com
CyscoExpert Corporation
Internetwork Consulting & Training
http://www.cyscoexpert.com
Voice: 847.674.3392
Fax: 847.674.2625
> -----Original Message-----
> From: frank.yu@japan.bnpparibas.com
[mailto:frank.yu@japan.bnpparibas.com]
> Sent: Thursday, September 12, 2002 9:09 PM
> To: brian@cyscoexpert.com
> Cc: bpjain@cisco.com; ccielab@groupstudy.com
> Subject: RE: hsrp&dlsw
>
>
> Guys,
>
> Just want to clear my mind up, correct me if I am wrong.
> For example we have a simple scenario as following,
>
>
> (e0)R1-------------------------------------------------R2(e0)
> FR
>
> I want to setup a dlsw peer between R1 and R2, so I need to put E0
on
> both R1 and R2 into a certain group with "bridge-group X" under E0
> interface.
> Because E0 belongs to a certain bridge group now, so any layer3
> configuration under E0 including ip address has to be moved to
interface
> BVI X.
> Am I right??
>
> Frank
>
>
>
> Internet
> brian@cyscoexpert.com - 09/13/2002 07:30 AM
>
> To: bpjain, Frank Yu, ccielab
>
> cc:
>
>
> Subject: RE: hsrp&dlsw
>
>
> HSRP config would go on the BVI, assuming you're routing IP for
> this bridge group. Any layer 3 config for a protocol you're routing
and
> bridging would go on the BVI.
>
> As for the DLSw+ on a stick, I've had issues with this.
> Whenever I try this in the lab, it causes a spanning-tree loop, and
the
> trunk port keeps resetting itself. Try putting the subinterfaces in
two
> different DLSw bridge-groups, and see if that helps. Sometimes it
> works; sometimes it doesn't, so it must be version/platform specific.
>
> HTH
>
> Brian McGahan, CCIE #8593
> Director of Design and Implementation
> brian@cyscoexpert.com
>
> CyscoExpert Corporation
> Internetwork Consulting & Training
> http://www.cyscoexpert.com
> Voice: 847.674.3392
> Fax: 847.674.2625
>
>
> > -----Original Message-----
> > From: beda jain [mailto:bpjain@cisco.com]
> > Sent: Thursday, September 12, 2002 11:18 AM
> > To: Brian McGahan; frank.yu@japan.bnpparibas.com;
> ccielab@groupstudy.com
> > Subject: hsrp&dlsw
> >
> > Hi Brian,
> >
> > first question
> > --------------------
> > When you have irb configured and you need to configure hsrp, then
that
> > should be configure in BVI in intreface or
> > the ethernet interface ????. The ethernat inter face does not
> configure
> > with ip address.
> >
> > second question
> > -------------------------
> >
> > there are two sub interface in fa0/0 and each interface are in
> different
> > vlan.
> >
> > Now you want to configure dlsw between these vlan and a token ring
or
> a
> > vlan in other router.
> >
> > do i need to configure two diffrent dlsw bridge group or only one
> bridge
> > group.
> >
> > Thanks,
> > Beda
> >
> >
> >
> >
> > At 09:56 AM 9/11/2002 -0500, Brian McGahan wrote:
> > >Frank,
> > >
> > > This is the advantage of IRB over regular transparent
> bridging.
> > >IRB allows you to route a protocol on an interface (IP for
example),
> > >while routing & bridging another protocol on that interface (IPX
for
> > >example). The following example would accomplish just this:
> > >
> > >Interface Ethernet 0
> > > Ip address 1.1.1.1 255.0.0.0
> > > Bridge-group 1
> > >!
> > >Interface Ethernet 1
> > > Ip address 2.2.2.2 255.0.0.0
> > > Bridge-group 1
> > >!
> > >Interface BVI 1
> > > IPX network 1
> > >!
> > >Bridge IRB
> > >Bridge 1 protocol IEEE
> > >Bridge 1 route IPX
> > >
> > >
> > > IP is routed normally. Only IPX is affected by the IRB
> config.
> > >
> > >
> > >HTH
> > >
> > >Brian McGahan, CCIE #8593
> > >Director of Design and Implementation
> > >brian@cyscoexpert.com
> > >
> > >CyscoExpert Corporation
> > >Internetwork Consulting & Training
> > >http://www.cyscoexpert.com
> > >Voice: 847.674.3392
> > >Fax: 847.674.2625
> > >
> > >
> > > > -----Original Message-----
> > > > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On
> Behalf
> > >Of
> > > > frank.yu@japan.bnpparibas.com
> > > > Sent: Wednesday, September 11, 2002 6:32 AM
> > > > To: ccielab@groupstudy.com
> > > > Subject: irb bridging help
> > > >
> > > > Group,
> > > >
> > > > Just wonder if we have to bridging traffic through a
interface
> > >let's
> > > > say
> > > > fa0/0 and fa0/0 is also in ospf domain. Does that mean we have
to
> > >remove
> > > > all the interface commands under fa0/0 (including ip address)
and
> put
> > > > them
> > > > under a BVI interface?
> > > > Also I notice that in the above situation if I leave the ip
> address
> > > > under
> > > > fa0/0, I still be able to ping the ip address from the other
> router,
> > >why??
> > > > Thank for the input in advance.
> > > >
> > > > Frank
> > > >
> > > >
> > > >
> > > > This message and any attachments (the "message") is
> > > > intended solely for the addressees and is confidential.
> > > > If you receive this message in error, please delete it and
> > > > immediately notify the sender. Any use not in accord with
> > > > its purpose, any dissemination or disclosure, either whole
> > > > or partial, is prohibited except formal approval. The internet
> > > > can not guarantee the integrity of this message.
> > > > BNP PARIBAS (and its subsidiaries) shall (will) not
> > > > therefore be liable for the message if modified.
> > > >
> > > > ---------------------------------------------
> > > >
> > > > Ce message et toutes les pieces jointes (ci-apres le
> > > > "message") sont etablis a l'intention exclusive de ses
> > > > destinataires et sont confidentiels. Si vous recevez ce
> > > > message par erreur, merci de le detruire et d'en avertir
> > > > immediatement l'expediteur. Toute utilisation de ce
> > > > message non conforme a sa destination, toute diffusion
> > > > ou toute publication, totale ou partielle, est interdite, sauf
> > > > autorisation expresse. L'internet ne permettant pas
> > > > d'assurer l'integrite de ce message, BNP PARIBAS (et ses
> > > > filiales) decline(nt) toute responsabilite au titre de ce
> > > > message, dans l'hypothese ou il aurait ete modifie.
> This message and any attachments (the "message") is
> intended solely for the addressees and is confidential.
> If you receive this message in error, please delete it and
> immediately notify the sender. Any use not in accord with
> its purpose, any dissemination or disclosure, either whole
> or partial, is prohibited except formal approval. The internet
> can not guarantee the integrity of this message.
> BNP PARIBAS (and its subsidiaries) shall (will) not
> therefore be liable for the message if modified.
>
> ---------------------------------------------
>
> Ce message et toutes les pieces jointes (ci-apres le
> "message") sont etablis a l'intention exclusive de ses
> destinataires et sont confidentiels. Si vous recevez ce
> message par erreur, merci de le detruire et d'en avertir
> immediatement l'expediteur. Toute utilisation de ce
> message non conforme a sa destination, toute diffusion
> ou toute publication, totale ou partielle, est interdite, sauf
> autorisation expresse. L'internet ne permettant pas
> d'assurer l'integrite de ce message, BNP PARIBAS (et ses
> filiales) decline(nt) toute responsabilite au titre de ce
> message, dans l'hypothese ou il aurait ete modifie.
This archive was generated by hypermail 2.1.4 : Mon Oct 07 2002 - 07:43:50 GMT-3