Routing

Hi,

Could someone tell me what does below routing mean

inet.0: 490 destinations, 1120 routes (490 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

10.24.2.0/24 *[BGP/170] 00:33:09, MED 0, localpref 100, from 10.91.20.14
AS path: I
> to 10.91.20.22 via reth2.0

why segment 10.24.2.0/24 which I received from 10.91.20.14 is not routed via 10.91.20.14 but to 10.91.20.22.

I presume that that is an internal peer, correct?  What IP are you using to peer with that neighbor?  iBGP peers don't rewirte the nexthop attribute by default, that may be what is going on.  A 'show route 10.24.2.0/24 detail' might be helpful.

Hi,

Peer should be 10.91.20.14.

here's the detail 

BGP Preference: 200/-201
Next hop type: Indirect
Address: 0x15d0a74
Next-hop reference count: 2
Source: 10.91.20.14
Next hop type: Router, Next hop index: 592
Next hop: 10.91.20.22 via reth2.0, selected
Protocol next hop: 10.91.234.2
Indirect next hop: 1711d00 -
State: <Int Ext>
Inactive reason: Route Preference
Local AS: 65432 Peer AS: 65432
Age: 6:15 Metric: 0 Metric2: 10
Task: BGP_65432.10.91.20.14+179
AS path: I
Accepted
Localpref: 200
Router ID: 10.91.2.197

please advice..

is there something that I need to tune up?

I'm presuming that 10.91.20.14 has a route for that network with a next hop of 10.91.20.22, and since it is an IBGP peer, it is not rewriting the next hop as it advertises the route via BGP.  You can use a policy-statement on the export policy with a statement in the 'then' section of 'next-hop self', that should rewrite the next hop to 10.91.20.14 as it is advertised to the peer.