ðÒÉ×ÅÔ
èÁÊ!
Ï ËÁËÏÊ ÓÔÁÂÉÌØÎÙÊ IOS ÐÏÓÏ×ÅÔÕÅÔ? ñ × ÏÂÝÅÍ ÎÁ Ó×ÏÊ ÎÅ ÖÁÌÏ×ÁÌÓÑ, ÎÏ ×ÏÔ ÎÁÒ×ÁÌÓÑ ÎÁ CSCdx26714
÷ ÔÁËÉÈ ×ÉÐÁÄËÁÈ Ñ ÐÒÏÓÔÏ ÎÅ ÓÏÒÏÍÌÀÓØ Ú×ÅÒÔÁÔÉÓÑ ÄÏ ÎÁÛÉÈ ×ÉÓÏËÏÐÏ×ÁÖÎÉÈ Cisco Systems Ukraine. ïÓÏÂÌÉ×Ï ×ÏÎÉ Ú×ÅÒÔÁÌÉ ÎÁ ÃÅ Õ×ÁÇÕ (ÝÏÂÉ ÎÅ ÓÏÒÏÍÉÌÉÓØ ÚÁÐÉÔÕ×ÁÔÉ × ÎÉÈ) Ú ÐÏÞÁÔËÏÍ ××ÏÄÕ 12.3....
1. Symptom :
If the prefix get Rib-Failre when installing into bgp table because of there is already has a prefix in the routing table with a prefered admin distance (like already learnd by ospf), then this prefix should not be advertised to other bgp peers unless the next-hop is the same as the prefix in the ip routing table. But the behavior is that even if the next-hop is the same, this prefix still does not advertise to it's bgp peers.
2. Conditions :
You should see the bgp prefix get a "Rib-Failure" in the output of "show ip bgp
". This will confirm that this prefix fails to install into the routing table. Then check the next-hop for the bgp prefix and the prefix that already in the ip table (it's ospf in this ddts). If they are the same, then bgp should still advertise this prfix to it's bgp peers. 3. Workaround :
Thers is not workaround for this problem.
-- Best regard, Aleksander Trotsai aka MAGE-RIPE aka MAGE-UANIC My PGP key at ftp://blackhole.adamant.ua/pgp/trotsai.key[.asc] Big trouble - We're upgrading /dev/null =================================================================== uanog mailing list. To Unsubscribe: send mail to majordomo@uanog.kiev.ua with "unsubscribe uanog" in the body of the message
-- Regards, Oleh Hrynchuk Mobile: +380675025446 E-mail: oleh@nextra.cz =================================================================== uanog mailing list. To Unsubscribe: send mail to majordomo@uanog.kiev.ua with "unsubscribe uanog" in the body of the message