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

The BGP password must match on both BGP peers to establish a session. This is
particularly important when peering with external organizations, such as an ISP in
which the peering router might not be under your direct control.
Configuring BGP authentication simply requires the password to be enabled on the
neighbor, as shown in Example 3-87.
Example 3-87. Configuring BGP Authentication
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)# neighbor 192.168.1.38
Congo(config-router-neighbor)# password bgppassword
Congo(config-router-neighbor)# end
You can verify the authentication on the peer session by using the show ip bgp neighbor
command, as demonstrated in Example 3-88.
Example 3-88. Verification of BGP Authentication
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:05:16
Peer is directly attached, interface Ethernet1/18
TCP MD5 authentication is enabled
Last read 00:00:14, hold time = 180, keepalive interval
is 60 seconds
Last written 00:00:15, keepalive timer expiry due
00:00:44
Received 31 messages, 0 notifications, 0 bytes in queue
Sent 37 messages, 1 notifications, 0 bytes in queue
Connections established 2, dropped 1
Last reset by us 00:05:36, due to holdtimer expired
error
Last reset by peer never, due to process restart