[c-nsp] Connected routes / Static routes advertised to RR's
CiscoNSP List
CiscoNSP_list at hotmail.com
Wed Jun 29 06:25:28 EDT 2016
Hi Everyone,
Have an issue with an RR client and advertising its connected and static routes to RR's (Note - From all other RR-clients, static and connected routes are working fine)
The prefixes on the RR client are advertised, and I can reach the "connected" prefix IP's, but a static route to one of the connected prefixes is showing up as "inaccessible", even though I can ping/reach that IP from the RR?
Eg.
>From RR
Connected route showing as received and used from the RR-client, and I can ping it:
sh ip bgp xxx.xxx.79.106
BGP routing table entry for xxx.xxx.79.104/30, version 253735
BGP Bestpath: compare-routerid
Paths: (1 available, best #1, table default)
Additional-path-install
Path advertised to update-groups:
2 3 13 346 347 348 350
351 361 363 364 365 366
Refresh Epoch 1
Local, (Received from a RR-client), (received & used)
xxx.xxx.76.201 (metric 3) from xxx.xxx.76.201 (xxx.xxx.76.201)
Origin incomplete, metric 0, localpref 100, valid, internal, af-export(2), best
Community: YYYYY:1000 YYYYY:1301 YYYYY:14000
rx pathid: 0, tx pathid: 0x0
#ping xxx.xxx.79.105
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to xxx.xxx.79.105, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 2/2/2 ms
#ping xxx.xxx.79.106
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to xxx.xxx.79.106, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 5/5/7 ms
Static route to that prefix on the RR-client, shows as "no best path" as the 79.106 prefix is "inaccessible"? but as above, it is accessible and I can ping it? (So the static is not advertised to any other RR-clients):
sh ip bgp xxx.xxx.71.228
BGP routing table entry for xxx.xxx.71.228/30, version 0
BGP Bestpath: compare-routerid
Paths: (1 available, no best path)
Additional-path-install
Path not advertised to any peer
Refresh Epoch 1
Local, (Received from a RR-client), (received & used)
xxx.xxx.79.106 (inaccessible) from xxx.xxx.76.201 (xxx.xxx.76.201)
Origin incomplete, metric 0, localpref 100, valid, internal, af-export(2)
Community: YYYYY:1000 YYYYY:1301 YYYYY:14000
rx pathid: 0, tx pathid: 0
And trying to ping an IP in that subnet, of course fails..
#ping xxx.xxx.71.229
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to xxx.xxx.71.229, timeout is 2 seconds:
U.U.U
Success rate is 0 percent (0/5)
Why would the RR report 79.106 IP as "inaccessible"
Any assistance is greatly appreciated - cheers
More information about the cisco-nsp
mailing list