22.05.2017 Views

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

Nexus Switching 2nd Edition

Nexus Switching 2nd Edition

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

!Time: Thu Sep 27 16:10:10 2012<br />

version 5.2(3a)<br />

feature bgp<br />

router bgp 65000<br />

router-id 192.168.1.1<br />

address-family ipv4 unicast<br />

address-family ipv6 unicast<br />

BGP Neighbors<br />

After the address family is configured, the next step would be to configure the iBGP <strong>and</strong><br />

eBGP peers using the neighbor comm<strong>and</strong>s. iBGP is used between BGP speakers in the<br />

same autonomous system, whereas eBGP is used between BGP speakers in different<br />

autonomous systems. Example 3-83 notes the update source as Loopback 0 to make peering<br />

simpler by using the loopback 0 IP address as the source IP for a peering session.<br />

Example 3-83. Configuring an IPv4 iBGP Neighbor<br />

Click here to view code image<br />

Congo# config t<br />

Enter configuration comm<strong>and</strong>s, one per line. End with<br />

CNTL/Z.<br />

Congo(config)# router bgp 65000<br />

Congo(config-router-af)# neighbor 192.168.1.2 remote-as<br />

65000<br />

Congo(config-router-neighbor)# description Egypt<br />

Congo(config-router-neighbor)# update-source loopback0<br />

Congo(config-router-neighbor)# address-family ipv4 unicast<br />

Congo(config-router-neighbor-af)# end<br />

You can verify the peering session by looking at the output from the show ip bgp neighbor<br />

192.168.1.2 comm<strong>and</strong>, as demonstrated in Example 3-84.<br />

Example 3-84. Verification of an IPv4 iBGP Neighbor<br />

Click here to view code image<br />

Congo# show ip bgp neighbors 192.168.1.2<br />

BGP neighbor is 192.168.1.2, remote AS 65000, ibgp<br />

link, Peer index 1<br />

Description: Egypt

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!