From: Marius Venter (marius@aict.co.za)
Date: Wed Mar 22 2006 - 02:46:49 GMT-3
Hi John
To add to my previous post.
I only got to the actual post now.
I am just wondering if you could ping the 54.1.1.254 from router 3 and 5.
If you can I am also baffled.
My gut feel however suggests that if you can't you should consider the next
hop self option as discussed in the previous post or you should redistribute
the 54.1.1.0 address into an IGP process on router 6.
Just a thought.
Marius Venter
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of John
Matus
Sent: Tuesday, March 21, 2006 10:50 PM
To: ccielab@groupstudy.com
Subject: bgp frustration IE lab 1
ok, this is frustrating me to no end...........and i used to be so good w/
bgp
this is lab 1 IE 3.0
R3, R4, R5, R6 are all in AS 100
R5 is a route-reflector for all other routers in the AS. AS 100 is
learning prefixes from AS 54 from 2 connections, R3 and R6, but the routes
are not propagating as expected........i would expect R3 and R6 to
advertise to R5 which would then advertise to R4 and back to the spokes.
but here is what i get in my BGP tables.
R3
r3#bb
BGP table version is 78, local router ID is 150.1.3.3
Status codes: s suppressed, d damped, h history, * valid, > best, i -
internal,
r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 28.119.16.0/24 204.12.1.254 0 0 54 i
*> 28.119.17.0/24 204.12.1.254 0 0 54 i
*> 112.0.0.0 204.12.1.254 0 54 50 60 i
*> 113.0.0.0 204.12.1.254 0 54 50 60 i
*> 114.0.0.0 204.12.1.254 0 54 i
*> 115.0.0.0 204.12.1.254 0 54 i
*> 116.0.0.0 204.12.1.254 0 54 i
*> 117.0.0.0 204.12.1.254 0 54 i
*> 118.0.0.0 204.12.1.254 0 54 i
*> 119.0.0.0 204.12.1.254 0 54 i
* i205.90.31.0 183.1.58.8 0 100 0 200 254 ?
*> 183.1.123.1 0 200 254 ?
* i220.20.3.0 183.1.58.8 0 100 0 200 254 ?
*> 183.1.123.1 0 200 254 ?
* i222.22.2.0 183.1.58.8 0 100 0 200 254 ?
*> 183.1.123.1 0 200 254 ?
r4#bb
BGP table version is 174, local router ID is 150.1.4.4
Status codes: s suppressed, d damped, h history, * valid, > best, i -
internal,
r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*>i28.119.16.0/24 204.12.1.254 0 100 0 54 i
*>i28.119.17.0/24 204.12.1.254 0 100 0 54 i
*>i112.0.0.0 204.12.1.254 0 100 0 54 50 60 i
*>i113.0.0.0 204.12.1.254 0 100 0 54 50 60 i
*>i114.0.0.0 204.12.1.254 0 100 0 54 i
*>i115.0.0.0 204.12.1.254 0 100 0 54 i
*>i116.0.0.0 204.12.1.254 0 100 0 54 i
*>i117.0.0.0 204.12.1.254 0 100 0 54 i
*>i118.0.0.0 204.12.1.254 0 100 0 54 i
*>i119.0.0.0 204.12.1.254 0 100 0 54 i
*>i205.90.31.0 183.1.58.8 0 100 0 200 254 ?
*>i220.20.3.0 183.1.58.8 0 100 0 200 254 ?
*>i222.22.2.0 183.1.58.8 0 100 0 200 254 ?
r4#
r5#bb
BGP table version is 294, local router ID is 150.1.5.5
Status codes: s suppressed, d damped, h history, * valid, > best, i -
internal,
r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
* i28.119.16.0/24 54.1.1.254 0 500 0 54 i
*>i 204.12.1.254 0 100 0 54 i
* i28.119.17.0/24 54.1.1.254 0 500 0 54 i
*>i 204.12.1.254 0 100 0 54 i
* i112.0.0.0 54.1.1.254 0 100 0 54 50 60 i
*>i 204.12.1.254 0 100 0 54 50 60 i
* i113.0.0.0 54.1.1.254 0 100 0 54 50 60 i
*>i 204.12.1.254 0 100 0 54 50 60 i
* i114.0.0.0 54.1.1.254 0 500 0 54 i
*>i 204.12.1.254 0 100 0 54 i
* i115.0.0.0 54.1.1.254 0 500 0 54 i
*>i 204.12.1.254 0 100 0 54 i
* i116.0.0.0 54.1.1.254 0 500 0 54 i
*>i 204.12.1.254 0 100 0 54 i
* i117.0.0.0 54.1.1.254 0 500 0 54 i
*>i 204.12.1.254 0 100 0 54 i
* i118.0.0.0 54.1.1.254 0 500 0 54 i
Network Next Hop Metric LocPrf Weight Path
*>i 204.12.1.254 0 100 0 54 i
* i119.0.0.0 54.1.1.254 0 500 0 54 i
*>i 204.12.1.254 0 100 0 54 i
* i205.90.31.0 183.1.123.1 0 100 0 200 254 ?
*> 183.1.58.8 0 200 254 ?
* i220.20.3.0 183.1.123.1 0 100 0 200 254 ?
*> 183.1.58.8 0 200 254 ?
* i222.22.2.0 183.1.123.1 0 100 0 200 254 ?
*> 183.1.58.8 0 200 254 ?
r5#
r6#bb
BGP table version is 14, local router ID is 150.1.6.6
Status codes: s suppressed, d damped, h history, * valid, > best, i -
internal,
r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
* i28.119.16.0/24 204.12.1.254 0 100 0 54 i
*> 54.1.1.254 500 0 54 i
* i28.119.17.0/24 204.12.1.254 0 100 0 54 i
*> 54.1.1.254 500 0 54 i
* i112.0.0.0 204.12.1.254 0 100 0 54 50 60 i
*> 54.1.1.254 0 0 54 50 60 i
* i113.0.0.0 204.12.1.254 0 100 0 54 50 60 i
*> 54.1.1.254 0 0 54 50 60 i
* i114.0.0.0 204.12.1.254 0 100 0 54 i
*> 54.1.1.254 0 500 0 54 i
* i115.0.0.0 204.12.1.254 0 100 0 54 i
*> 54.1.1.254 0 500 0 54 i
* i116.0.0.0 204.12.1.254 0 100 0 54 i
*> 54.1.1.254 0 500 0 54 i
* i117.0.0.0 204.12.1.254 0 100 0 54 i
*> 54.1.1.254 0 500 0 54 i
* i118.0.0.0 204.12.1.254 0 100 0 54 i
Network Next Hop Metric LocPrf Weight Path
*> 54.1.1.254 0 500 0 54 i
* i119.0.0.0 204.12.1.254 0 100 0 54 i
*> 54.1.1.254 0 500 0 54 i
*>i205.90.31.0 183.1.58.8 0 100 0 200 254 ?
*>i220.20.3.0 183.1.58.8 0 100 0 200 254 ?
*>i222.22.2.0 183.1.58.8 0 100 0 200 254 ?
r6#
now it appears that R6 is learning the prefixes from AS 54 from r3 as well
as BB1, but R3 is not learning the prefixes that R6 is learning from BB1.
in addition, i have a local-pref set to route to BB1, but it seems to be
choosing internal routes rather than BGP routes and i have no idea where it
is getting these internal routes since i did not redistribute BGP into IGP.
ANY IDEAS??
TIA
Regards,
John D. Matus
Technical Support / PAS
Fujitsu Consulting
626-568-7716
John.Matus@tokiom.com
============================================================================
============================
This e-mail is intended solely for the individual to whom it is
addressed. The information contained in this transmission contains
confidential and/or proprietary information or is otherwise privileged. If
the reader of this message is not the intended recipient, please be advised
that any dissemination, distribution or copying of this transmission is
strictly prohibited. If you have received this e-mail in error, please
notify us immediately by returning it to the sender and deleting this copy
from your system. Thank you for your cooperation.
============================================================================
============================
This archive was generated by hypermail 2.1.4 : Sat Apr 01 2006 - 10:07:39 GMT-3