Is the next-hop reachable?
-----Original Message----- From: juniper-nsp-boun...@puck.nether.net [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Eric Van Tol Sent: Tuesday, March 17, 2009 7:14 PM To: juniper-nsp Subject: [j-nsp] Missing BGP Routes Hi all, In what instance would a router be missing routes that are advertised to it? And by missing, I don't mean 'inactive' or 'hidden'. I have four routers peering through a full-mesh IBGP, one of which is advertising several routes that were received from a route reflector client. The routes are being sent from the route reflector router to all IBGP sessions and they are seen by only three out of four of the non-client peers. This one particular "problem" router doesn't have the prefixes anywhere in its RIB. There are no import policies on IBGP sessions denying any prefixes. Routes received from route-reflector client: edge02# run show route receive-protocol bgp 192.168.205.51 inet.0: 280459 destinations, 1146831 routes (279785 active, 3 holddown, 1448 hidden) Restart Complete Prefix Nexthop MED Lclpref AS path * 172.16.234.0/25 192.168.205.54 0 100 I * 172.16.236.0/27 192.168.205.55 0 100 I * 172.16.236.32/28 192.168.205.55 0 100 I * 172.16.236.48/30 192.168.205.56 0 100 I * 172.16.236.144/28 192.168.205.55 0 100 I * 172.16.236.160/29 192.168.205.55 0 100 I * 172.16.237.128/25 192.168.205.56 0 100 I * 172.16.239.224/27 192.168.205.51 0 100 I 192.168.206.129 is sending these routes to 192.168.206.128, which is a non-client peer: edge02# run show route advertising-protocol bgp 192.168.206.128 172.16.236.0/22 inet.0: 280471 destinations, 1146944 routes (279808 active, 0 holddown, 1399 hidden) Restart Complete Prefix Nexthop MED Lclpref AS path * 172.16.236.0/27 192.168.205.55 0 100 I * 172.16.236.32/28 192.168.205.55 0 100 I * 172.16.236.48/30 192.168.205.56 0 100 I * 172.16.236.144/28 192.168.205.55 0 100 I * 172.16.236.160/29 192.168.205.55 0 100 I * 172.16.237.128/25 192.168.205.56 0 100 I * 172.16.239.224/27 192.168.205.51 0 100 I 192.168.206.128 doesn't show these routes anywhere: edge01> show route receive-protocol bgp 192.168.206.129 172.16.192.0/18 inet.0: 280324 destinations, 940059 routes (279811 active, 0 holddown, 1210 hidden) Restart Complete edge01> show route receive-protocol bgp 192.168.206.129 172.16.192.0/18 hidden inet.0: 280327 destinations, 940062 routes (279815 active, 0 holddown, 1210 hidden) Restart Complete And the view from the other two non-client peers: core02> show route receive-protocol bgp 192.168.206.129 172.16.192.0/18 table inet.0 inet.0: 280139 destinations, 567582 routes (279540 active, 0 holddown, 770 hidden) Restart Complete Prefix Nexthop MED Lclpref AS path * 172.16.234.0/25 192.168.205.54 0 100 I * 172.16.236.0/27 192.168.205.55 0 100 I * 172.16.236.32/28 192.168.205.55 0 100 I * 172.16.236.48/30 192.168.205.56 0 100 I * 172.16.236.144/28 192.168.205.55 0 100 I * 172.16.237.128/25 192.168.205.56 0 100 I * 172.16.239.224/27 192.168.205.51 0 100 I core01> show route receive-protocol bgp 192.168.206.129 172.16.192.0/18 table inet.0 inet.0: 280147 destinations, 567688 routes (279612 active, 0 holddown, 727 hidden) Restart Complete Prefix Nexthop MED Lclpref AS path * 172.16.234.0/25 192.168.205.54 0 100 I * 172.16.236.0/27 192.168.205.55 0 100 I * 172.16.236.32/28 192.168.205.55 0 100 I * 172.16.236.48/30 192.168.205.56 0 100 I * 172.16.236.144/28 192.168.205.55 0 100 I * 172.16.237.128/25 192.168.205.56 0 100 I * 172.16.239.224/27 192.168.205.51 0 100 I Thanks, evt _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp