On 08/21/2019 11:24 AM, Doug McIntyre
wrote:
[log in to unmask]"
type="cite">On Wed, Aug 21, 2019 at 01:00:21PM +0000, Frank Bulk
wrote:
Our route logged these two items Monday
morning with MICE's AS:
Aug 19 10:35:41 207.32.15.28 Rib: mpbgp_recv_mpreach: peer
2001:504:27::d1af:0:2 (AS 53679) link-local next hop
fe80::e2ac:f1ef:fe4b:d93b%10000 improper, ignoring this next-hop
Aug 19 11:08:50 207.32.15.28 Rib: mpbgp_recv_mpreach: peer
2001:504:27::d1af:0:2 (AS 53679) link-local next hop
fe80::e2ac:f1ef:fe4b:d93b%10000 improper, ignoring this next-hop
Not sure what that was about.
Odd, the 2nd RR's link local address is fe80::f21f:afff:fedb:a5d5
I don't find the one listed above known by either of the RR's ND
process.
Something freaked out for a minute?
That is indeed strange. The IPv6 address above is one of our MICE
connected routers. We are not sure what caused this, but, the
timing would suggest that it may have been related to the
replacement of the CNS MICE switch.