For IPv4 and IPv6 address families:
show bgp {neighbor} remoteaddr {address-family [ipv4-unicast | ipv4-multicast |ipv6-unicast | ipv6-multicast | ipv4-vxlan | {l2vpn-evpn [inclusive-multicast | mac-ip | auto-discovery | esi | ip-prefix]}]} [accepted-routes | received-routes | rejected-routes | transmitted-routes] {detail} [all | as-path path-expression | community [no-advertise | no-export | no-export-subconfed | number community_number | autonomous-system-id : bgp-community] | network [any/netMaskLen | networkPrefixFilter] {exact}]For the VPNv4 address family:
show bgp {neighbor} remoteaddr address-family vpnv4 [accepted-routes | received-routes | rejected-routes | transmitted-routes] {detail} [all | as-path path-expression | community [no-advertise | no-export | no-export-subconfed | number community_number | autonomous-system-id :bgp-community] | rd rd_value network [any/netMaskLen | networkPrefixFilter] {exact}]Displays information about routes to a specified neighbor.
| remoteaddr | Specifies an IPv4 or IPv6 address that identifies a BGP neighbor. |
| ipv4-unicast | Specifies IPv4 unicast routes. |
| ipv4-multicast | Specifies IPv4 multicast routes. |
| ipv6-unicast | Specifies IPv6 unicast routes. |
| ipv6-multicast | Specifies IPv6 multicast routes. |
| ipv4-vxlan | Specifies IPv4 VXLAN routes. |
| l2vpn-evpn | Specifies an L2VPN EVPN address family. |
| inclusive-multicast | Displays EVPN inclusive-multicast (type 3) routes |
| mac-ip | Displays EVPN MAC/IP (type 2) routes. |
| auto-discovery | Displays EVPN auto-discovery (type 1) routes. |
| esi | Displays EVPN Ethernet segment (type 4) routes. |
| ip-prefix | Displays EVPN ip-prefix (type 5) routes. |
| vpnv4 | Specifies VPNv4 routes. |
| accepted-routes | Specifies that only accepted routes are displayed. |
| received-routes | Specifies that only received routes are displayed. |
| rejected-routes | Specifies that only rejected routes are displayed. |
| transmitted-routes | Specifies that only transmitted routes are displayed. |
| detail | Specifies to display the information in detailed format. |
| all | Specifies all routes. |
| path-expression | Display routes that match the specified AA path expression. |
| no-advertise | Specifies the no-advertise community attribute. |
| no-export | Specifies the no-export community attribute. |
| no-export-subconfed | Specifies the no-export-subconfed community attribute. |
| community_number | Specifies a community number. |
| autonomous-system-id | Specifies an autonomous system ID (0-65535). |
| bgp-community | Specifies the BGP community number. |
| rd | Specifies the Route Distinquisher (RD) value for the Layer 3 VPN routes for which you want to clear flap statistics. |
| any | Specifies all routes with a given or larger mask length. |
| netMaskLen | Specifies a IPv4 or IPv6 subnet mask length (number of bits). |
| networkPrefixFilter | Specifies an IPv4 or IPv6 address and netmask. |
| exact | Specifies an exact match with the IP address and subnet mask. |
If no address family is specified, IPv4 unicast is the default.
show bgp neighbor now supports v6 unicast and multicast and vpnv4 address families. This command applies to the current VR or VRF context.
Note
If this command displays Bad Source Address, the BGP neighbor IP address is unavailable. Possible causes for this condition include a deleted or unconfigured This command is available on the ExtremeSwitching X440-G2, X450-G2, X460-G2, X465, X590, X620, and X695 series switches. or IP address.
The option network any / netMaskLen displays all BGP routes whose mask length is equal to or greater than maskLength, irrespective of their network address.
The option network any / netMaskLen exact displays all BGP routes whose mask length is exactly equal to maskLength, irrespective of their network address.
If you do not specify an address family, this command applies to the IPv4 unicast address family. To apply this command to an address family other than the IPv4 unicast address family, you must specify the address family.
Note
For an IPv6 peer, an IPv6 address family must be specified, because an IPv6 peer does not support IPv4 address families. If no address family is specified for an IPv6 peer, the default address-family, i.e. IPv4 unicast is assumed and hence no address-family information appears. Similarly an IPv4 peer only supports IPv4 address families and no address-family information appears if an IPv6 address family is specified.
To display Layer 3 VPN information, you must enter this command in the context of on the MPLS-enabled VR; it is not supported for BGP neighbors on the CE (VRF) side of the PE router.
The following command displays sample output when an error message is generated when the user attempts to create more than the limit of 2 peering sessions with a Base license on VR-Default (including any child VRFs of VR-Default:
# show bgp neighbor
Peer AS Weight State InMsgs OutMsgs(InQ) Up/Down
------------------------------------------------------------------------------------------------------------
Id-- 10.1.1.1 10 1 IDLE 0 0 (0 ) 0:0:13:53
Id-- 20.1.1.1 10 1 IDLE 0 0 (0 ) 0:0:00:07
Flags: (d) disabled, (e) enabled, (E) external peer, (I) internal peer
switch-model-EXOS.24 # create bgp neighbor 30.1.1.1 remote-AS-number 10
Error: Core license is required to configure more than 2 peers
Base License (User VR):
* (vr user1) switch-model-EXOS.29 # create bgp neighbor 30.1.1.1 remote-AS-number 50
Error: vr user1: Core license is required to configure peer on VR other than VR-Default
The following command displays sample output for show bgp neighbor summary:
# show bgp neighbor
Peer AS Weight State InMsgs OutMsgs(InQ) Up/Down
-------------------------------------------------------------------------------
Ie-- 11.0.0.2 100 0 OPENSENT 0 9 (0 ) 0:8:27:21
Ie-- 3001::1 100 0 ESTABLISEHD 4 3 (0 ) 0:8:27:21
Flags: (d) disabled, (e) enabled, (E) external peer, (I) internal peer
(m) EBGP multihop, (r) route reflector client
BGP Peer Statistics
Total Peers : 2
EBGP Peers : 0
IBGP Peers : 2
RR Client : 0
EBGP Multihop : 0
Enabled : 2
Disabled : 0
The following example displays show output for an IPv4 peer:
# show bgp neighbor 192.168.66.2 Peer Description : EBGP Peer : 192.168.66.2 AS : 38 Enabled : Yes OperStatus : Up Weight : 1 Shutdown-Priority : 1024 ConnectRetry : 120 MinAsOrig : 30 HoldTimeCfg : 180 KeepaliveCfg : 60 Source Interface : Not configured RRClient : No EBGP-Multihop : No Remove Private AS : No BFD : Off BFD Status : Not Required Capabilities Config : ipv4-unicast,ipv4-multicast,4-Byte-As,route-refresh (old & new),l2vpn-evpn Policy for NLRI Type ipv4-unicast In Policy : None Out Policy : None NextHopSelf : Disabled Send Communities : No Soft Input Recfg : Disabled Allow Looped AS-Path: No NextHopUnchanged : Disabled . . . Policy for NLRI Type ipv4-vxlan In Policy : None Out Policy : None NextHopSelf : Enabled Send Communities : No Soft Input Recfg : Disabled Allow Looped AS-Path: No NextHopUnchanged : Disabled Policy for NLRI Type l2vpn-evpn In Policy : None Out Policy : None NextHopSelf : Disabled Send Communities : No Soft Input Recfg : Disabled Allow Looped AS-Path: No NextHopUnchanged : Enabled State : ESTABLISHED FSM Up since : Sat May 5 04:05:30 2018 (Duration: 0:0:08:19) Remote Addr : 192.168.66.2 Local Addr : 192.168.66.1 Remote Port : 179 Local Port : 51612 Remote RouterId : 1.0.0.38 Local RouterId : 1.0.0.25 HoldTimeNegotiated : 180 KeepAliveNegotiated : 60 FsmTransitions : 1 InUpdateElapsedTime : 00:00:08:25 InMsgElapsedTime : 0:0:08:25 InUpdates : 2 OutUpdates (in TxQ) : 3 (0) InTotalMsgs : 14 OutTotalMsgs : 15 InRouteRefreshes : 0 OutRouteRefreshes : 0 Route Statistics for NLRI Type ipv4-unicast Received : 1 Accepted : 1 Rejected : 0 Active : 1 Suppressed : 0 . . . Route Statistics for NLRI Type l2vpn-evpn Received : 0 Accepted : 0 Rejected : 0 Active : 0 Suppressed : 0 Capabilities Tx : ipv4-unicast,ipv4-multicast,4-Byte-As,route-refresh (old & new),l2vpn-evpn Capabilities Rx : ipv4-unicast,ipv4-multicast,4-Byte-As,route-refresh (old & new),l2vpn-evpn NLRI for the session: ipv4-unicast,ipv4-multicast,ipv4-vxlan,l2vpn-evpn Last State : ESTABLISHED Last Event : RX_KEEP LastError : 'Cease - Peer Connection Rejected' (RX) on: Sat May 5 04:05:15 2018 BGP Peer Statistics Total Peers : 1 EBGP Peers : 1 IBGP Peers : 0 RR Client : 0 EBGP Multihop : 0 Enabled : 1 Disabled : 0
The following example displays output for an IPv6 peer:
# show bgp neighbor 3001::1 detail
EBGP Peer : 3001::1 AS : 5
Enabled : Yes OperStatus : Up
Weight : 1 Shutdown-Priority : 1024
ConnectRetry : 120 MinAsOrig : 15
HoldTimeCfg : 180 KeepaliveCfg : 60
Source Interface : Not configured RRClient : No
EBGP-Multihop : No Remove Private AS : No
BFD : Off BFD Status : Inactive
Capabilities Config : ipv6-unicast, ipv6-multicast, 4-Byte-As, route-refresh
Policy for NLRI Type ipv6-unicast
In Policy : None
Out Policy : None
NextHopSelf : Disabled Send Communities : No
Soft Input Recfg : Disabled Allow Looped AS-Path: No
RFD HalfLife : 0m RFD Reuse : 0
RFD Suppress : 0 RFD Max-Suppress : 0m
Policy for NLRI Type ipv6-multicast
In Policy : None
Out Policy : None
NextHopSelf : Disabled Send Communities : No
Soft Input Recfg : Disabled Allow Looped AS-Path: No
RFD HalfLife : 0m RFD Reuse : 0
RFD Suppress : 0 RFD Max-Suppress : 0m
State : ESTABLISHED
FSM Up since : Mon Apr 19 21:20:02 2010 (Duration: 0:0:00:23)
Remote Addr : 3001::1 Local Addr : 3001::6
Remote Port : 56539 Local Port : 179
Remote RouterId : 1.0.0.5 Local RouterId : 1.0.0.6
HoldTimeNegotiated : 180 KeepAliveNegotiated : 60
FsmTransitions : 5
InUpdateElapsedTime : 00:00:00:23 InMsgElapsedTime : 0:0:00:23
InUpdates : 1 OutUpdates (in TxQ) : 4 (0)
InTotalMsgs : 1 OutTotalMsgs : 4
InRouteRefreshes : 0 OutRouteRefreshes : 0
Route Statistics for NLRI Type ipv6-unicast
Received : 6
Accepted : 6
Rejected : 0
Active : 6
Suppressed : 0
Route Statistics for NLRI Type ipv6-multicast
Received : 0
Accepted : 0
Rejected : 0
Active : 0
Suppressed : 0
Capabilities Tx : ipv6-unicast, ipv6-multicast, 4-Byte-AS, route-refresh (old &
new), vpnv4
Capabilities Rx : ipv6-unicast, ipv6-multicast
NLRI for the session: ipv6-unicast, ipv6-multicast
Error : 'Hold Timer Expired' Tx: 3 Rx: 0
Last State : ESTABLISHED Last Event : RX_UPDATE
LastError : 'Hold Timer Expired' (TX) on: Mon Apr 19 20:50:26 2010
BGP Peer Statistics
Total Peers : 1
EBGP Peers : 1 IBGP Peers : 0
RR Client : 0 EBGP Multihop : 0
Enabled : 1
Disabled : 0
The following example displays show output for transmitted routes:
#show bgp 11.0.0.2 transmitted-routes all
Advertised Routes:
Destination LPref Weight MED Peer Next-Hop AS-Path
------------------------------------------------------------------------------------
>? 1.1.1.1/32 100 11.0.0.1 100
>? 11.0.0.0/24 100 11.0.0.1 100
>? 101.0.0.0/24 100 11.0.0.1 100
>? 103.0.0.0/24 100 11.0.0.1 100
>? 103.0.0.1/32 100 11.0.0.1 100
Flags: (*) Preferred BGP route, (>) Active, (d) Suppressed, (h) History
(s) Stale, (m) Multipath, (u) Unfeasible
Origin: (?) Incomplete, (e) EGP, (i) IGP
BGP Route Statistics
Advertised Routes : 5
The following example displays show output for rejected routes:
# show bgp 11.0.0.2 rejected-routes all
Rejected Routes:
Destination LPref Weight MED Peer Next-Hop AS-Path
------------------------------------------------------------------------------------
u ? 1.1.1.1/32 100 11.0.0.1 100
Flags: (*) Preferred BGP route, (>) Active, (d) Suppressed, (h) History
(s) Stale, (m) Multipath, (u) Unfeasible
Origin: (?) Incomplete, (e) EGP, (i) IGP
BGP Route Statistics
Total Rxed Routes : 5
Rejected Routes : 1
Unfeasible Routes : 1
The following example displays show output for accepted routes:
# show bgp 11.0.0.2 accepted-routes all
Rejected Routes:
Destination LPref Weight MED Peer Next-Hop AS-Path
------------------------------------------------------------------------------------
>? 11.0.0.0/24 100 11.0.0.1 100
>? 101.0.0.0/24 100 11.0.0.1 100
>? 103.0.0.0/24 100 11.0.0.1 100
>? 103.0.0.1/32 100 11.0.0.1 100
Flags: (*) Preferred BGP route, (>) Active, (d) Suppressed, (h) History
(s) Stale, (m) Multipath, (u) Unfeasible
Origin: (?) Incomplete, (e) EGP, (i) IGP
BGP Route Statistics
Total Rxed Routes : 5
Feasible Routes : 4
Active Routes : 4
The following example shows BGP IPv4 VXLAN routes received from the BGP neighbor located at 192.168.68.1:
# show bgp neighbor 192.168.68.1 ipv4-vxlan received-routes all Routes: LTEP VNI Peer Next-Hop LPref Weight MED AS-Path ----------------------------------------------------------------------------- i 1.0.0.15/32 777 192.168.68.1 192.168.68.1 100 1 0 15
The following example shows L2VPN EVPN accepted and rejected MAC/IP routes for neighbor 192.168.120.119:
# show bgp neighbor 192.168.120.119 l2vpn-evpn mac-ip received-routes all
EVPN MAC/IP Routes:
MAC IP VNI Peer Next-Hop AS-Path
-------------------------------------------------------------------------------------------
*>? RD: 65535:4294967295 ESI: 00:01:02:03:04:05:06:07:08:09
00:04:96:98:87:62 192.168.110.109 16777215 192.168.120.119 192.168.120.119 50 40 30 20 10
*>i RD: 4294967295:65535 ESI: 00:01:02:03:04:05:06:07:08:09
00:04:96:98:87:64 192.168.110.110 777 192.168.120.119 192.168.120.119 50 40 30 20 10
# show bgp neighbor 192.168.99.2 l2vpn-evpn ip-prefix received-routes all
Routes:
EVPN IP-Prefix Routes:
IP Prefix/Length VNI Peer Next-Hop AS-Path
--------------------------------------------------------------------------------------------------------------------------------
? RD: 1.0.0.25:48 ESI: 00:00:00:00:00:00:00:00:00:00
125.126.127.128/32 777 192.168.99.2 1.0.0.25 38 25
? RD: 1.0.0.25:49 ESI: 00:00:00:00:00:00:00:00:00:00
1.0.0.0/8 778 192.168.99.2 1.0.0.25 38 25
This command was first available in ExtremeXOS 10.1.
The any / netMaskLen options were added in ExtremeXOS 11.0.
This command required a specific license in ExtremeXOS 11.1.
Support for IPv6 was added in ExtremeXOS 12.6 BGP.
Support for Layer 3 VPNs was added in ExtremeXOS 15.3.
Support for BFD on neighbors was added in ExtremeXOS 21.1
Support for IPv4 VXLAN was added in ExtremeXOS 22.3.
Support for L2VPN EVPN was added in ExtremeXOS 30.2.
Support for EVPN auto-discovery and EVPN Ethernet Segment routes was added in ExtremeXOS 30.4.
Support for Type 5 routes (ip-prefix) was added in ExtremeXOS 30.6.
This command is available on platforms that support the appropriate license. For complete information about software licensing, including how to obtain and upgrade your license and which licenses support the BGP feature, see the ExtremeXOS 32.1 Feature License Requirements document.