From: Carlos G Mendioroz (tron@xxxxxxxxxxx)
Date: Thu Jun 27 2002 - 20:20:27 GMT-3
David,
what has igrp got to do with it ?
I've just tested it under 12.1, and plain bgp, as soon as you set a
network
to backdoor, changes the AD to 200 (ok, I knew it was something
high, it's 200 not 170 :-)
There's smth else going on...
David Sapp wrote:
>
> Place 175.10.0.0 under igrp process of R2.
>
> Dave
>
> At 02:31 PM 6/27/02 -0700, Annu Roopa wrote:
> >Yes i know its not working.I cleared the routes and
> >also re-intialized BGP.Will try it tonight again.The
> >IP table shows as 20 it showuld show 100 for IGRP.Also
> >the traceroute takes the EBGP path.
> >
> >Annu
> >
> >--- Carlos G Mendioroz <tron@huapi.ba.ar> wrote:
> > > Have you tried a clear ip bgp after putting the
> > > backdor config ?
> > > The backdor command is not working... you can tell
> > > because
> > > the AD of your BGP route is 20 (and not 170).
> > >
> > > Annu Roopa wrote:
> > > >
> > > > Group,
> > > >
> > > > Here is a BGP scenario whic is troubling me. what
> > > am i
> > > > doing wrong ? The scenario is about BGP backdoor
> > > and
> > > > it looks like this.
> > > >
> > > > eBGP eBGP
> > > > 172.16.1.0 10.1.1.0
> > > >
> > > R2-------------R10---------------r12--175.10.10.1
> > > > | |
> > > > |---------------------------------
> > > >
> > > > 192.168.1.0 IGRP
> > > >
> > > > The configs look as below. even thought i
> > > configure
> > > > BGP backdoor the path taken is thru the EBGP link
> > > ?
> > > >
> > > > hostname R12
> > > > ip address 175.10.10.1 255.255.0.0
> > > > !
> > > > interface Serial0
> > > > ip address 10.1.1.2 255.255.255.0
> > > > no fair-queue
> > > > !
> > > > interface Serial1
> > > > ip address 192.168.1.2 255.255.255.0
> > > > !
> > > > router igrp 100
> > > > network 175.10.0.0
> > > > network 192.168.1.0
> > > > !
> > > > router bgp 300
> > > > bgp router-id 175.10.10.1
> > > > bgp log-neighbor-changes
> > > > network 10.1.1.0 mask 255.255.255.0
> > > > network 175.10.0.0
> > > > neighbor 10.1.1.1 remote-as 200
> > > > no auto-summary
> > > >
> > > > ------
> > > > hostname R2
> > > > interface Loopback0
> > > > ip address 190.10.10.1 255.255.255.0
> > > > !
> > > > interface Serial0
> > > > ip address 172.16.1.1 255.255.255.0
> > > > !
> > > > interface Serial1
> > > > ip address 192.168.1.1 255.255.255.0
> > > > clockrate 64000
> > > > !
> > > > router igrp 100
> > > > network 192.168.1.0
> > > > !
> > > > router bgp 400
> > > > bgp log-neighbor-changes
> > > > network 175.10.0.0 backdoor
> > > > network 190.10.10.0 mask 255.255.255.0
> > > > network 190.10.10.0
> > > > network 192.168.1.0
> > > > neighbor 172.16.1.2 remote-as 200
> > > >
> > > > ------
> > > > R2#show ip route
> > > > C 190.10.10.0 is directly connected,
> > > Loopback0
> > > > B 175.10.0.0/16 [20/0] via 172.16.1.2, 00:05:45
> > > > C 192.168.1.0/24 is directly connected, Serial1
> > > > B 200.10.10.0/24 [20/0] via 172.16.1.2,
> > > 00:00:43
> > > > 180.10.0.0/24 is subnetted, 1 subnets
> > > > B 180.10.10.0 [20/0] via 172.16.1.2,
> > > 00:05:46
> > > >
> > > > R2#show ip bgp
> > > > BGP table version is 120, local router ID is
> > > > 190.10.10.1
> > > > Status codes: s suppressed, d damped, h history, *
> > > > valid, > best, i - internal
> > > > Origin codes: i - IGP, e - EGP, ? - incomplete
> > > >
> > > > Network Next Hop Metric
> > > LocPrf
> > > > Weight Path
> > > > *> 175.10.0.0 172.16.1.2 0 200 300 i
> > > > *> 180.10.10.0/24 172.16.1.0 0 200 i
> > > > *> 190.10.10.0/24 0.0.0.0 0
> > > > 32768 i
> > > > *> 192.168.1.0 0.0.0.0 0
> > > > 32768 i
> > > >
> > > > Thanks in advance.
> > > >
This archive was generated by hypermail 2.1.4 : Tue Jul 02 2002 - 08:12:43 GMT-3