I have a BGP-learned prefix 130.130.0.0/24
with protocol next hop 10.0.2.5
:
root@r2> show route 130.130.0.0 detail
inet.0: 60 destinations, 61 routes (57 active, 0 holddown, 4 hidden)
130.130.0.0/24 (1 entry, 1 announced)
*BGP Preference: 170/-101
Next hop type: Indirect, Next hop index: 0
Address: 0xd30c210
Next-hop reference count: 6
Source: 10.0.3.4
Next hop type: Router, Next hop index: 0
Next hop: 10.0.4.9 via ge-0/0/3.0, selected
Session Id: 0x0
Next hop: 10.0.4.1 via ge-0/0/6.0
Session Id: 0x0
Protocol next hop: 10.0.2.5
Indirect next hop: 0xba9dd80 1048582 INH Session ID: 0x1aa
State: <Active Int Ext>
Local AS: 65001 Peer AS: 65001
Age: 44:28 Metric2: 20
Validation State: unverified
ORR Generation-ID: 0
Task: BGP_65001.10.0.3.4+179
Announcement bits (2): 0-KRT 5-Resolve tree 4
AS path: (65000) 65222 I
Communities: 65412:200
Accepted
Localpref: 100
Router ID: 10.0.3.4
root@r2>
As seen above, the 10.0.2.5
is resolved to next-hops 10.0.4.9
(selected) and 10.0.4.1
. However, the output of the show route 10.0.2.5
selects a 10.0.4.1
as a next-hop:
root@r2> show route 10.0.2.5
inet.0: 60 destinations, 61 routes (57 active, 0 holddown, 4 hidden)
+ = Active Route, - = Last Active, * = Both
10.0.2.4/30 *[IS-IS/15] 1w5d 02:17:27, metric 20
to 10.0.4.9 via ge-0/0/3.0
> to 10.0.4.1 via ge-0/0/6.0
root@r2> show route forwarding-table matching 10.0.2.4/30 table default
Routing table: default.inet
Internet:
Enabled protocols: Bridging,
Destination Type RtRef Next hop Type Index NhRef Netif
10.0.2.4/30 user 0 10.0.4.1 ucst 595 5 ge-0/0/6.0
root@r2>
Why is the BGP protocol next hop
using a different next-hop address than ISIS?
forwarding-table export
policy look like? Does it doload-balance per-packet
on the ISIS-learnt route? – Jeff Wheeler Nov 4 '20 at 17:09