Aleksandr Gurbo wrote: > How to setup reflected route in route table with correct next-hop? > > I have iBGP RR on IPv6 addresses with two rr-clients. All ibgp peers between > routers from Loopbacks. For announce ipv6 Loopback addresses used OSPFv3.
> rtr4#show ip bgp ipv6 unicast 2001:1020:100::3/128
> BGP routing table entry for 2001:1020:100::3/128, version 0
> Paths: (1 available, no best path)
> Not advertised to any peer
> Local, (received & used)
> 2001:1020:100::3 (inaccessible) from 2001:1020:100::2 (10.10.1.14)
^^^^^^^^^^^^^^
I don't know for sure, but this seems like a reachability problem, not
necessarily a BGP problem.
The next-hop should appear valid and usable, and link-local is a valid
next-hop in your case. eg:
O>* 2607:f118:1::e3/128 [110/2] via fe80::21a:70ff:fe14:568a, em5, 05w2d23h
Can r2 reach r3? Can you provide some relevant BGP and OSPF config snips
from r2 and r4?
I have a network segment that is configured nearly identical to yours,
so I can compare config pieces with you if you'd like.
Steve
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
