>[оверквотинг удален]
> FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0032 0104 FDEE 00B4
> 0A3A FF01 1502 0601
> 0400 0100 0102 0280 0002 0202 0002 0383 0100
> .Nov 13 00:33:02.440: %BGP-3-NOTIFICATION: received from neighbor xx.xx.xxx.x ac
> tive 2/3 (BGP identifier wrong) 4 bytes 0A3AFF01
> .Nov 13 00:33:02.440: %BGP_SESSION-5-ADJCHANGE: neighbor xx.xx.xxx.xIPv4 Unicas
> t topology base removed from session Unknown path error
> При чем до этого аналогичные настройки и топология отрабатывала на 75х маршрутизаторах,
> в чем засада и чем не угодили 76, есть ли у
> кого-то соображения?циску.ком смотрели?
вот первое что попалось..
CSCth94205
Symptom
The BFD BGP adjacency does not comes up after the removal of an IP address from the
interface. The BFD BGP adjacency is not formed and does not comes up even after the configuration is
present. System messages similar to the following may appear:
6: %BGP-3-NOTIFICATION: sent to neighbor 10.78.170.130 active 2/3 (BGP identifier wrong) 4
bytes AC122CD7 14:55:36: %BGP-4-MSGDUMP: unsupported or mal-formatted message received
from 10.78.170.130: FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0032 0104 0082 00B4 AC12 2CD7
1502 0601 0400 0100 0102 0280 0002 0202 0002 0383 0100
Conditions
The symptom occurs when:
• An IP address is removed from one end of the BFD adjacency formation.
• The neighboring device’s address is configured on its interface.
• It is deregistered and the original IP address is configured back again.
Workaround
Remove the enitre BFD and BGP configuration. Reconfigure the Cisco ITP.