actually we have been added static route for 10.10.24.10
and the other router is juniper
At 02:01 PM 1/30/2002 +0100, Ben Buxton wrote:
>The router is receiving a next-hop of 10.10.24.10 via bgp,
>however it does not have a valid IGP route to this IP
>address. Make sure 10.10.24.10 is in your routing
>table. However that is probably not what the real problem
>is...it looks like the peer 203.129.80.36 is giving this
>address as next-hop, when it probably wants to advertise
>a non-rfc1918 address.
>
>Be careful if you see rfc1918 together with BGP...
>
>BB
>
>-----Original Message-----
>From: Raymond Leung [mailto:rlcw@zonasa.com]
>Sent: Wednesday, January 30, 2002 1:21 PM
>To: cisco-nsp@puck.nether.net
>Cc: rlcw@zonasa.com
>Subject: [nsp] [nsp]Wanna ask about BGP on cisco
>
>
>why will like that ?
>
>tip#sh ip bgp 6.9.0.0/20
>BGP routing table entry for 6.9.0.0/20, version 103430615
>Paths: (1 available, no best path)
>Flag: 0x208
> Not advertised to any peer
> 10032 3549 7170 1455, (received & used)
> 10.10.24.10 (inaccessible) from 10.10.24.10 (203.129.80.36)
> Origin IGP, localpref 100, valid, internal
>
>please advice why will inaccessible , thx thx !!!!!
>
>With Regards,
>
>
>Raymond Leung
>Network Analyst
>Zonasa Network Limited
>
>
>Suite 903,Technology Plaza
>651 King's Road
>Quarry Bay
>Hong Kong
>
>AS4841 Object Maintainer
With Regards,
Raymond Leung
Network Analyst
Zonasa Network Limited
Suite 903,Technology Plaza
651 King's Road
Quarry Bay
Hong Kong
AS4841 Object Maintainer
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:13:02 EDT