Scribd
Upload
440 views3 pages

Chained Composite Next Hop

- The route for 122.1.1.0/30 is learned from BGP neighbor 10.247.11.27 and has a next hop of 10.247.10.2 via interface xe-1/0/2.0. - Chained composite next hops were configured to allow pushing multiple labels for L3VPN routes. - After configuration, the next hop for 122.1.1.0/30 is now shown as composite in the routing table and forwarding table, consisting of the indirect and label operations.

Uploaded by

Sivaraman Alagappan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
440 views3 pages

Chained Composite Next Hop

- The route for 122.1.1.0/30 is learned from BGP neighbor 10.247.11.27 and has a next hop of 10.247.10.2 via interface xe-1/0/2.0. - Chained composite next hops were configured to allow pushing multiple labels for L3VPN routes. - After configuration, the next hop for 122.1.1.0/30 is now shown as composite in the routing table and forwarding table, consisting of the indirect and label operations.

Uploaded by

Sivaraman Alagappan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 3

admin@MX2020-re0> show route 122.1.1.

0/30 extensive table test-bgp

test-bgp.inet.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)


122.1.1.0/30 (1 entry, 1 announced)
TSI:
KRT in-kernel 122.1.1.0/30 -> {indirect(1048579)}
*BGP Preference: 170/-101
Route Distinguisher: 64999:1
Next hop type: Indirect
Address: 0x98f8a28
Next-hop reference count: 3
Source: 10.247.11.27
Next hop type: Router, Next hop index: 856
Next hop: 10.247.10.2 via xe-1/0/2.0, selected
Label operation: Push 16, Push 167(top)
Label TTL action: no-prop-ttl, no-prop-ttl(top)
Session Id: 0x1
Protocol next hop: 10.247.16.98
Push 16
Indirect next hop: 0x95f8b2c 1048579 INH Session ID: 0xbb
State: <Secondary Active Int Ext ProtectionPath ProtectionCand>
Local AS: 64999 Peer AS: 64999
Age: 7 Metric2: 10125
Validation State: unverified
Task: BGP_64999.10.247.11.27+45668
Announcement bits (1): 0-KRT
AS path: I (Originator)
Cluster list: 10.247.11.27 0.0.0.2
Originator ID: 10.247.16.98
Communities: target:64999:2
Import Accepted
VPN Label: 16
Localpref: 100
Router ID: 10.247.11.27
Primary Routing Table bgp.l3vpn.0
Indirect next hops: 1
Protocol next hop: 10.247.16.98 Metric: 10125
Push 16
Indirect next hop: 0x95f8b2c 1048579 INH Session ID: 0xbb
Indirect path forwarding next hops: 1
Next hop type: Router
Next hop: 10.247.10.2 via xe-1/0/2.0
Session Id: 0x1
10.247.16.98/32 Originating RIB: inet.3
Metric: 10125 Node path count: 1
Forwarding nexthops: 1
Nexthop: 10.247.10.2 via xe-1/0/2.0

admin@MX2020-re0> show route forwarding-table destination 122.1.1.0/30 table test-


bgp extensive
Routing table: test-bgp.inet [Index 12]
Internet:

Destination: 122.1.1.0/30
Route type: user
Route reference: 0 Route interface-index: 0
Flags: sent to PFE
Next-hop type: indirect Index: 1048574 Reference: 2
Nexthop: 10.247.10.2
Next-hop type: Push 16, Push 167(top) Index: 855 Reference: 2
Next-hop interface: xe-1/0/2.0

******************* After configuring chained-composite-next-hop


*******************

[edit]
admin@MX2020-re0# show | compare
[edit routing-options forwarding-table]
+ chained-composite-next-hop {
+ ingress {
+ l3vpn;
+ }
+ }

admin@MX2020-re0> show route 122.1.1.0/30 extensive table test-bgp

test-bgp.inet.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)


122.1.1.0/30 (1 entry, 1 announced)
TSI:
KRT in-kernel 122.1.1.0/30 -> {composite(856)}
*BGP Preference: 170/-101
Route Distinguisher: 64999:1
Next hop type: Indirect
Address: 0x98f89dc
Next-hop reference count: 3
Source: 10.247.11.27
Next hop type: Router, Next hop index: 855
Next hop: 10.247.10.2 via xe-1/0/2.0, selected
Label operation: Push 167
Label TTL action: no-prop-ttl
Session Id: 0x1
Protocol next hop: 10.247.16.98
Push 16
Composite next hop: 0x98fa860 856 INH Session ID: 0xb5
Indirect next hop: 0x95f8b2c 1048579 INH Session ID: 0xb5
State: <Secondary Active Int Ext ProtectionPath ProtectionCand>
Local AS: 64999 Peer AS: 64999
Age: 1:01 Metric2: 10125
Validation State: unverified
Task: BGP_64999.10.247.11.27+18820
Announcement bits (1): 0-KRT
AS path: I (Originator)
Cluster list: 10.247.11.27 0.0.0.2
Originator ID: 10.247.16.98
Communities: target:64999:2
Import Accepted
VPN Label: 16
Localpref: 100
Router ID: 10.247.11.27
Primary Routing Table bgp.l3vpn.0
Composite next hops: 1
Protocol next hop: 10.247.16.98 Metric: 10125
Push 16
Composite next hop: 0x98fa860 856 INH Session ID: 0xb5
Indirect next hop: 0x95f8b2c 1048579 INH Session ID: 0xb5
Indirect path forwarding next hops: 1
Next hop type: Router
Next hop: 10.247.10.2 via xe-1/0/2.0
Session Id: 0x1
10.247.16.98/32 Originating RIB: inet.3
Metric: 10125 Node path count: 1
Forwarding nexthops: 1
Nexthop: 10.247.10.2 via xe-1/0/2.0

admin@MX2020-re0> show route forwarding-table destination 122.1.1.0/30 table test-


bgp extensive
Routing table: test-bgp.inet [Index 12]
Internet:

Destination: 122.1.1.0/30
Route type: user
Route reference: 0 Route interface-index: 0
Flags: sent to PFE
Nexthop:
Next-hop type: composite Index: 856 Reference: 2
Next-hop type: indirect Index: 1048579 Reference: 2
Nexthop: 10.247.10.2
Next-hop type: Push 167 Index: 855 Reference: 2
Next-hop interface: xe-1/0/2.0

You might also like