show ip bgp evpn routes
show ip bgp
evpn routes [
detail
]
[
num
|
age num
|
as-path-access-list
name
|
as-path-filter number
| best |
community |
community-access-list
name
|
community-filter number |
community-reg-expression
expression |
ead-es [
es-id unique-es ]
[
l2vni
l2vni-id
]
[
tunnel-ip
tunnel-address
]
|
ead-evi
[
es-id unique-es ]
[
l2vni
l2vni-id
]
[
tunnel-ip
tunnel-address ]
|
es
[
es-id unique-es ]
[
l2vni
l2vni-id
]
[
tunnel-ip
tunnel-address
]
|
imet [
l2vni
l2vni-id
|
tunnel-ip
tunnel-address ]
|
local |
mac [
l2vni
l2vni-id
|
mac-addr
mac-address
]
|
neighbor ip-addr
[
ead-es [ es-id
unique-es ]
[
l2vni
l2vni-id
]
[
tunnel-ip
tunnel-address
]
[
ead-evi
[ es-id unique-es
]
[
l2vni
l2vni-id
]
[
tunnel-ip
tunnel-address ]
]
[
es
[ es-id unique-es
]
[
l2vni
l2vni-id
]
[
tunnel-ip
tunnel-address
]
]
[
imet
[
l2vni
l2vni-id
tunnel-ip
tunnel-address |
mac
l2vni
l2vni-id
mac-addr
mac-address
]
|
nexthop ip-addr |
summary |
unreachable ]- num
- Displays the table entry at which the display starts. For example, if you want to list entries beginning with table entry 100, specify 100.
- as-path-access-list name
- Displays BGP EVPN route information that is filtered by autonomous system (AS)-path access control list (ACL).
- as-path-filter number
- Displays BGP EVPN route information that is filtered using the specified AS-path filter.
- community-access-list name
- Displays BGP EVPN route information for an AS-path community access list.
- community-filter number
- Displays BGP EVPN route information that matches a specific community filter.
- community-reg-expression expression
- Displays BGP EVPN route information for an ordered community list regular expression.
- imet
- Displays BGP EVPN information for P-Multicast Service Interface Tunnel (PMSI Tunnel) path attributes associated with the route.
- nexthop ip-addr
- Displays BGP EVPN information about routes that are received from the specified next hop.
User EXEC mode
BGP maintains two types of EVPN Routing Information Bases (RIBs): ES-RIB for Ethernet Segment (ES) scope routes and EVI-RIB for Ethernet Virtual Instance (EVI) scope routes. Routes from ES-RIB are organized and displayed under individual Ethernet Segment Identifiers (ESIs).
The following example shows sample output from the show
ip bgp evpn routes command.
device> show ip bgp evpn routes
Total number of BGP EVPN Routes: 5 (R: 3, L: 2)
Status A:AGGREGATE B:BEST b:NOT-INSTALLED-BEST C:CONFED_EBGP D:DAMPED
E:EBGP H:HISTORY I:IBGP L:LOCAL M:MULTIPATH m:NOT-INSTALLED-MULTIPATH
S:SUPPRESSED F:FILTERED s:STALE
Prefix Next Hop MED LocPrf Weight Status
Route Distinguisher: 2.2.2.8:30
1 [3]:[0]:[32]:[2.2.2.8]/72
2.2.2.8 0 100 0 BL
AS_PATH: Not Applicable
2 [3]:[0]:[32]:[2.2.2.11]/72
2.2.2.11 0 100 0 BI
AS_PATH: Not Applicable
Route Distinguisher: 2.2.2.8:31
3 [2]:[0]:[48]:[0001.0001.0001]/128
2.2.2.11 0 100 0 BI
AS_PATH: Not Applicable
4 [3]:[0]:[32]:[2.2.2.8]/72
2.2.2.8 0 100 0 BL
AS_PATH: Not Applicable
5 [3]:[0]:[32]:[2.2.2.11]/72
2.2.2.11 0 100 0 BI
AS_PATH: Not Applicable
The following example shows sample output from the
show
ip bgp evpn routes command when the mac keyword is used.
device> show ip bgp evpn routes mac
Searching for matching routes, use ^C to quit...
Status A:AGGREGATE B:BEST b:NOT-INSTALLED-BEST C:CONFED_EBGP D:DAMPED
E:EBGP H:HISTORY I:IBGP L:LOCAL M:MULTIPATH m:NOT-INSTALLED-MULTIPATH
S:SUPPRESSED F:FILTERED s:STALE
Prefix Next Hop MED LocPrf Weight Status
Route Distinguisher: 2.2.2.8:31
1 [2]:[0]:[48]:[0001.0001.0001]/128
2.2.2.11 0 100 0 BI
AS_PATH: Not Applicable
The following example shows sample output from
the show ip bgp evpn
routes command when the imet keyword is used.
device> show ip bgp evpn routes imet
Searching for matching routes, use ^C to quit...
Status A:AGGREGATE B:BEST b:NOT-INSTALLED-BEST C:CONFED_EBGP D:DAMPED
E:EBGP H:HISTORY I:IBGP L:LOCAL M:MULTIPATH m:NOT-INSTALLED-MULTIPATH
S:SUPPRESSED F:FILTERED s:STALE
Prefix Next Hop MED LocPrf Weight Status
Route Distinguisher: 2.2.2.8:30
1 [3]:[0]:[32]:[2.2.2.8]/72
2.2.2.8 0 100 0 BL
AS_PATH: Not Applicable
2 [3]:[0]:[32]:[2.2.2.11]/72
2.2.2.11 0 100 0 BI
AS_PATH: Not Applicable
Route Distinguisher: 2.2.2.8:31
3 [3]:[0]:[32]:[2.2.2.8]/72
2.2.2.8 0 100 0 BL
AS_PATH: Not Applicable
4 [3]:[0]:[32]:[2.2.2.11]/72
2.2.2.11 0 100 0 BI
AS_PATH: Not Applicable
The following example shows sample output from
the show ip bgp evpn
routes command when the detail keyword is used.
device> show ip bgp evpn routes detail
Total number of BGP EVPN Routes: 5 (R: 3, L: 2)
Status A:AGGREGATE B:BEST b:NOT-INSTALLED-BEST C:CONFED_EBGP D:DAMPED
E:EBGP H:HISTORY I:IBGP L:LOCAL M:MULTIPATH m:NOT-INSTALLED-MULTIPATH
S:SUPPRESSED F:FILTERED s:STALE
Route Distinguisher: 2.2.2.8:30
1 Prefix: [3]:[0]:[32]:[2.2.2.8]/72, Status: BL, Age: 18h12m30s
NEXT_HOP: 2.2.2.8, Learned from Peer: Local Router
LOCAL_PREF: 100, MED: 0, ORIGIN: igp, Weight: 0
AS_PATH: Not Applicable
PMSI Tunnel Type: Ingress-Replication, L2VNI: 10030, Endpoint: 2.2.2.8
Extended Community: RT 1000:30 Bgp-Encap: Tunnel-Type: 8
Adj_RIB_out count: 1, Admin distance 1
2 Prefix: [3]:[0]:[32]:[2.2.2.11]/72, Status: BI, Age: 18h11m14s
NEXT_HOP: 2.2.2.11, Learned from Peer: 1.1.1.11 (1000)
LOCAL_PREF: 100, MED: 0, ORIGIN: igp, Weight: 0
AS_PATH: Not Applicable
PMSI Tunnel Type: Ingress-Replication, L2VNI: 10030, Endpoint: 2.2.2.11
Extended Community: RT 1000:30 Bgp-Encap: Tunnel-Type: 8
Route Distinguisher: 2.2.2.8:31
3 Prefix: [2]:[0]:[48]:[0001.0001.0001]/128, Status: BI, Age: 18h11m14s
NEXT_HOP: 2.2.2.11, Learned from Peer: 1.1.1.11 (1000)
LOCAL_PREF: 100, MED: 0, ORIGIN: igp, Weight: 0
AS_PATH: Not Applicable
L2VNI: 10031
Extended Community: RT 1000:31 Bgp-Encap: Tunnel-Type: 8 MAC-Mobility: Static-flag: 1 Seq-no: 0
4 Prefix: [3]:[0]:[32]:[2.2.2.8]/72, Status: BL, Age: 18h12m30s
NEXT_HOP: 2.2.2.8, Learned from Peer: Local Router
LOCAL_PREF: 100, MED: 0, ORIGIN: igp, Weight: 0
AS_PATH: Not Applicable
PMSI Tunnel Type: Ingress-Replication, L2VNI: 10031, Endpoint: 2.2.2.8
Extended Community: RT 1000:31 Bgp-Encap: Tunnel-Type: 8
Adj_RIB_out count: 1, Admin distance 1
5 Prefix: [3]:[0]:[32]:[2.2.2.11]/72, Status: BI, Age: 18h11m14s
NEXT_HOP: 2.2.2.11, Learned from Peer: 1.1.1.11 (1000)
LOCAL_PREF: 100, MED: 0, ORIGIN: igp, Weight: 0
AS_PATH: Not Applicable
PMSI Tunnel Type: Ingress-Replication, L2VNI: 10031, Endpoint: 2.2.2.11
Extended Community: RT 1000:31 Bgp-Encap: Tunnel-Type:
The following example shows sample output from the
show
ip bgp evpn routes command when the detail and mac keywords are used.
device> show ip bgp evpn routes detail mac
Searching for matching routes, use ^C to quit...
Status A:AGGREGATE B:BEST b:NOT-INSTALLED-BEST C:CONFED_EBGP D:DAMPED
E:EBGP H:HISTORY I:IBGP L:LOCAL M:MULTIPATH m:NOT-INSTALLED-MULTIPATH
S:SUPPRESSED F:FILTERED s:STALE
Route Distinguisher: 2.2.2.8:31
1 Prefix: [2]:[0]:[48]:[0001.0001.0001]/128, Status: BI, Age: 18h16m21s
NEXT_HOP: 2.2.2.11, Learned from Peer: 1.1.1.11 (1000)
LOCAL_PREF: 100, MED: 0, ORIGIN: igp, Weight: 0
AS_PATH: Not Applicable
L2VNI: 10031
Extended Community: RT 1000:31 Bgp-Encap: Tunnel-Type: 8 MAC-Mobility: Static-flag: 1 Seq-no: 0
The following example shows sample output from the
show
ip bgp evpn routes command when the detail and imet keywords are used.
device> show ip bgp evpn routes detail imet
Searching for matching routes, use ^C to quit...
Status A:AGGREGATE B:BEST b:NOT-INSTALLED-BEST C:CONFED_EBGP D:DAMPED
E:EBGP H:HISTORY I:IBGP L:LOCAL M:MULTIPATH m:NOT-INSTALLED-MULTIPATH
S:SUPPRESSED F:FILTERED s:STALE
Route Distinguisher: 2.2.2.8:30
1 Prefix: [3]:[0]:[32]:[2.2.2.8]/72, Status: BL, Age: 18h18m3s
NEXT_HOP: 2.2.2.8, Learned from Peer: Local Router
LOCAL_PREF: 100, MED: 0, ORIGIN: igp, Weight: 0
AS_PATH: Not Applicable
PMSI Tunnel Type: Ingress-Replication, L2VNI: 10030, Endpoint: 2.2.2.8
Extended Community: RT 1000:30 Bgp-Encap: Tunnel-Type: 8
Adj_RIB_out count: 1, Admin distance 1
2 Prefix: [3]:[0]:[32]:[2.2.2.11]/72, Status: BI, Age: 18h16m47s
NEXT_HOP: 2.2.2.11, Learned from Peer: 1.1.1.11 (1000)
LOCAL_PREF: 100, MED: 0, ORIGIN: igp, Weight: 0
AS_PATH: Not Applicable
PMSI Tunnel Type: Ingress-Replication, L2VNI: 10030, Endpoint: 2.2.2.11
Extended Community: RT 1000:30 Bgp-Encap: Tunnel-Type: 8
Route Distinguisher: 2.2.2.8:31
3 Prefix: [3]:[0]:[32]:[2.2.2.8]/72, Status: BL, Age: 18h18m3s
NEXT_HOP: 2.2.2.8, Learned from Peer: Local Router
LOCAL_PREF: 100, MED: 0, ORIGIN: igp, Weight: 0
AS_PATH: Not Applicable
PMSI Tunnel Type: Ingress-Replication, L2VNI: 10031, Endpoint: 2.2.2.8
Extended Community: RT 1000:31 Bgp-Encap: Tunnel-Type: 8
Adj_RIB_out count: 1, Admin distance 1
4 Prefix: [3]:[0]:[32]:[2.2.2.11]/72, Status: BI, Age: 18h16m47s
NEXT_HOP: 2.2.2.11, Learned from Peer: 1.1.1.11 (1000)
LOCAL_PREF: 100, MED: 0, ORIGIN: igp, Weight: 0
AS_PATH: Not Applicable
PMSI Tunnel Type: Ingress-Replication, L2VNI: 10031, Endpoint: 2.2.2.11
Extended Community: RT 1000:31 Bgp-Encap: Tunnel-Type: 8
The following
example shows sample output from the show
ip bgp evpn routes command, including
information for multihoming routes. Two type-4/ES routes are
shown for the ESI "03:00:00:00:00:00:03:01:01:01" — one is
locally generated, and the other is received from an ES
member peer. EVI-RIB routes are grouped and displayed under
individual EVI Route Distinguishers (RDs). This includes
MAC/IP Multicast Ethernet Tag (IMET) routes, Ethernet
Auto-Discovery for ES (EAD-ES), and Ethernet Auto-Discovery
for EVI (EAD-EVI) routes.
device> show ip bgp evpn routes
Total number of BGP EVPN Routes: - (R: x, L: y)
Status A:AGGREGATE B:BEST b:NOT-INSTALLED-BEST C:CONFED_EBGP D:DAMPED
E:EBGP H:HISTORY I:IBGP L:LOCAL M:MULTIPATH m:NOT-INSTALLED-MULTIPATH
S:SUPPRESSED F:FILTERED s:STALE
Prefix Next Hop MED LocPrf Weight Status
Ethernet Segment Id: 03:00:00:00:00:00:03:01:01:01
1 [4]:[03:00:00:00:00:00:03:01:01:01]:[32]:[2.2.2.35]/120
2.2.2.35 0 100 0 BL
AS_PATH: Not Applicable
2 [4]:[03:00:00:00:00:00:03:01:01:01]:[32]:[2.2.2.38]/120
2.2.2.38 0 100 0 BI
AS_PATH: Not Applicable
Route Distinguisher: 2.2.2.35:30
< ... IMET and MAC route outputs are removed ...>
5 [1]:[03:00:00:00:00:00:03:01:01:01]:[0]/112
2.2.2.35 0 100 0 BL
AS_PATH: Not Applicable
6 [1]:[03:00:00:00:00:00:03:01:01:01]:[0]/112
2.2.2.38 0 100 0 BI
AS_PATH: Not Applicable
7 [1]:[03:00:00:00:00:00:03:01:01:01]:[0xFFFFFFFF]/112
2.2.2.35 0 100 0 BL
AS_PATH: Not Applicable
8 [1]:[03:00:00:00:00:00:03:01:01:01]:[0xFFFFFFFF]/112
2.2.2.38 0 100 0 BI
AS_PATH: Not Applicable
Route Distinguisher: 2.2.2.35:32
< ... IMET and MAC route outputs are removed ...>
9 [1]:[03:00:00:00:00:00:03:01:01:01]:[0]/112
2.2.2.35 0 100 0 BL
AS_PATH: Not Applicable
10 [1]:[03:00:00:00:00:00:03:01:01:01]:[0]/112
2.2.2.38 0 100 0 BI
AS_PATH: Not Applicable
11 [1]:[03:00:00:00:00:00:03:01:01:01]:[0xFFFFFFFF]/112
2.2.2.35 0 100 0 BL
AS_PATH: Not Applicable
12 [1]:[03:00:00:00:00:00:03:01:01:01]:[0xFFFFFFFF]/112
2.2.2.38 0 100 0 BI
AS_PATH: Not Applicable
The following example shows sample output from the show
ip bgp evpn routes command when the
ead-evi
keyword is used so that information for EAD routes is
displayed.
device> show ip bgp evpn routes ead-evi Status A:AGGREGATE B:BEST b:NOT-INSTALLED-BEST C:CONFED_EBGP D:DAMPED E:EBGP H:HISTORY I:IBGP L:LOCAL M:MULTIPATH m:NOT-INSTALLED-MULTIPATH S:SUPPRESSED F:FILTERED s:STALE Prefix Next Hop MED LocPrf Weight Status Route Distinguisher: 6.6.6.6:100 1 [1]:[01:34:15:93:39:4a:90:4e:21:00]:[6.6.6.6:100]:[0]/176 6.6.6.6 0 100 0 BL AS_PATH: Not Applicable Ethernet Segment Id: 01:34:15:93:39:4a:90:4e:21:00 2 [1]:[01:34:15:93:39:4a:90:4e:21:00]:[7.7.7.7:100]:[0]/176 7.7.7.7 0 100 0 BI AS_PATH: Not Applicable Ethernet Segment Id: 01:34:15:93:39:4a:90:4e:21:00 3 [1]:[01:c8:03:f5:3a:65:cc:4e:21:00]:[4.4.4.4:100]:[0]/176 4.4.4.4 0 100 0 BI AS_PATH: Not Applicable Ethernet Segment Id: 01:c8:03:f5:3a:65:cc:4e:21:00 Route Distinguisher: 6.6.6.6:110 4 [1]:[01:c8:03:f5:3a:65:cc:4e:21:00]:[4.4.4.4:110]:[0]/176 4.4.4.4 0 100 0 BI AS_PATH: Not Applicable Ethernet Segment Id: 01:c8:03:f5:3a:65:cc:4e:21:00 Route Distinguisher: 6.6.6.6:111 5 [1]:[01:34:15:93:39:4a:90:4e:21:00]:[6.6.6.6:111]:[0]/176 6.6.6.6 0 100 0 BL AS_PATH: Not Applicable Ethernet Segment Id: 01:34:15:93:39:4a:90:4e:21:00 6 [1]:[01:34:15:93:39:4a:90:4e:21:00]:[7.7.7.7:111]:[0]/176 7.7.7.7 0 100 0 BI AS_PATH: Not Applicable Ethernet Segment Id: 01:34:15:93:39:4a:90:4e:21:00 Route Distinguisher: 6.6.6.6:112 7 [1]:[01:34:15:93:39:4a:90:4e:21:00]:[6.6.6.6:112]:[0]/176 6.6.6.6 0 100 0 BL AS_PATH: Not Applicable Ethernet Segment Id: 01:34:15:93:39:4a:90:4e:21:00 8 [1]:[01:34:15:93:39:4a:90:4e:21:00]:[7.7.7.7:112]:[0]/176 7.7.7.7 0 100 0 BI AS_PATH: Not Applicable Ethernet Segment Id: 01:34:15:93:39:4a:90:4e:21:00 Route Distinguisher: 6.6.6.6:113 9 [1]:[01:34:15:93:39:4a:90:4e:21:00]:[6.6.6.6:113]:[0]/176 6.6.6.6 0 100 0 BL AS_PATH: Not Applicable Ethernet Segment Id: 01:34:15:93:39:4a:90:4e:21:00 10 [1]:[01:34:15:93:39:4a:90:4e:21:00]:[7.7.7.7:113]:[0]/176 7.7.7.7 0 100 0 BI AS_PATH: Not Applicable Ethernet Segment Id: 01:34:15:93:39:4a:90:4e:21:00 Route Distinguisher: 6.6.6.6:114 11 [1]:[01:34:15:93:39:4a:90:4e:21:00]:[6.6.6.6:114]:[0]/176 6.6.6.6 0 100 0 BL AS_PATH: Not Applicable Ethernet Segment Id: 01:34:15:93:39:4a:90:4e:21:00 12 [1]:[01:34:15:93:39:4a:90:4e:21:00]:[7.7.7.7:114]:[0]/176 7.7.7.7 0 100 0 BI AS_PATH: Not Applicable Ethernet Segment Id: 01:34:15:93:39:4a:90:4e:21:00 Route Distinguisher: 6.6.6.6:115 13 [1]:[01:34:15:93:39:4a:90:4e:21:00]:[6.6.6.6:115]:[0]/176 6.6.6.6 0 100 0 BL AS_PATH: Not Applicable Ethernet Segment Id: 01:34:15:93:39:4a:90:4e:21:00 14 [1]:[01:34:15:93:39:4a:90:4e:21:00]:[7.7.7.7:115]:[0]/176 7.7.7.7 0 100 0 BI AS_PATH: Not Applicable Ethernet Segment Id: 01:34:15:93:39:4a:90:4e:21:00 Route Distinguisher: 6.6.6.6:120 15 [1]:[01:c8:03:f5:3a:65:cc:4e:21:00]:[1.1.1.1:120]:[0]/176 1.1.1.1 0 100 0 BI AS_PATH: Not Applicable Ethernet Segment Id: 01:c8:03:f5:3a:65:cc:4e:21:00 16 [1]:[01:c8:03:f5:3a:65:cc:4e:21:00]:[4.4.4.4:120]:[0]/176 4.4.4.4 0 100 0 BI AS_PATH: Not Applicable Ethernet Segment Id: 01:c8:03:f5:3a:65:cc:4e:21:00 Number of Routes matching supplied condition : 16