nx.os.and.cisco.nexus.switching.2nd.edition.1587143046

0 sent paths
Third-party Nexthop will not be computed.
Local host: 192.168.1.1, Local port: 58042
Foreign host: 192.168.1.2, Foreign port: 179
fd = 37
Establishing an external BGP (eBGP) session is similar to an internal BGP (iBGP) session
with the primary difference being the remote-as number used. For an iBGP session, the AS
number is the same as the AS number used on the BGP process, whereas with eBGP it is a
different AS number. Example 3-85 demonstrates the configuration of an eBGP session.
Example 3-85. Configuring an IPv4 eBGP Neighbor
Click here to view code image
Congo# config t
Enter configuration commands, one per line. End with
CNTL/Z.
Congo(config)# router bgp 65000
Congo(config-router)#
Congo(config-router)# neighbor 192.168.1.38 remote-as
65001
Congo(config-router-neighbor)# description Libya
Congo(config-router-neighbor)# address-family ipv4 unicast
Congo(config-router-neighbor-af)# end
You can verify the peering session by looking at the output from show ip bgp neighbor
192.168.1.38, as demonstrated in Example 3-86.
Example 3-86. Verification of an IPv4 eBGP Neighbor
Click here to view code image
Congo# show ip bgp neighbor 192.168.1.38
BGP neighbor is 192.168.1.38, remote AS 65001, ebgp
link, Peer index 2
Description: Libya
BGP version 4, remote router ID 192.168.1.3
BGP state = Established, up for 00:01:13
Peer is directly attached, interface Ethernet1/18
Last read 00:00:11, hold time = 180, keepalive interval
is 60 seconds
Last written 00:00:12, keepalive timer expiry due
00:00:47