As far as I know 2 things could cause this.
1: You don't have a route to the next-hop address in the BGP table.
2: Has to do with the "Synchronization" rule which states that any route
received from IBGP speakers would have to also been learned through an IGP.
To get around this rule you
A little confusing below, 99% right, but "no sync" causes the IGP and EGP
to not be in sync and is probably what you want in most cases, like
multihoming to multiple ISP's etc.
On Thu, 17 Aug 2000, Hixon Sgt James R Jr wrote:
The reason for this is because your EGP is not synchronized with
Yang'; '[EMAIL PROTECTED]'
Subject: Re: Why the route in BGP table doesn't appear in IP table.
A little confusing below, 99% right, but "no sync" causes the IGP and EGP
to not be in sync and is probably what you want in most cases, like
multihoming to multiple ISP's etc.
On Thu, 17 Aug 2
vercd/cc/td/doc/cisintwk/ics/icsbgp4.htm
-Original Message-
From: Brian [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 17, 2000 7:10 AM
To: Hixon Sgt James R Jr
Cc: 'Luobin Yang'; '[EMAIL PROTECTED]'
Subject: Re: Why the route in BGP table doesn't appear in IP table.
A little confusin
Sent: Thursday, August 17, 2000 7:10 AM
To: Hixon Sgt James R Jr
Cc: 'Luobin Yang'; '[EMAIL PROTECTED]'
Subject: Re: Why the route in BGP table doesn't appear in IP table.
A little confusing below, 99% right, but "no sync" causes the IGP and EGP
to not be in sync
5 matches
Mail list logo
