www.howtonetwork.org

CCNA & CCNP Certifcation Training

  • About
  • Contact
  • FAQ
  • Join
  • Home
  • CCNA
    • ICND1
    • ICND2
    • 101 CCNA LABS
  • CCNP
    • ROUTE
    • SWITCH
    • TSHOOT
    • 101 CCNP LABS
  • CompTIA
    • Security+
    • Network+
  • Design
    • CCDA
    • CCDP
You are here: Home / ROUTE / Module 6 / iBGP and eBGP Fundamentals – Configuring and Verifying Internal BGP

iBGP and eBGP Fundamentals – Configuring and Verifying Internal BGP

The configuration of iBGP peers in Cisco IOS follows the same basic sequence of steps that is used when configuring eBGP peers. There are two ways to configure iBGP neighbor relationships. These two methods, which also apply to external BGP peers, are as follows:

  • Peer the routers using the physical interface IP addresses
  • Peer the routers using indirectly connected interfaces

Configuring Directly Connected iBGP Neighbor Relationships

The configuration of directly connected iBGP neighbors is straightforward. After BGP has been enabled on the router, the neighbor [address] remote-as [autonomous system number] router configuration command must be manually configured for each desired neighbor using the IP address assigned to the physical interface and referencing the autonomous system that remote neighbor resides in. Figure 6-29 illustrates a basic neighbor which shows two routers. Both R1 and R2 reside in AS 65001:

6-29Fig. 6-29. Internal BGP Peering Using Physical Interface Addresses

The configuration of the iBGP peer on R1 is performed as follows:

R1(config)#router bgp 65001
R1(config-router)#bgp router-id 1.1.1.1
R1(config-router)#neighbor 10.0.0.2 remote-as 65001
R1(config-router)#exit

The configuration of the eBGP peer on R2 is performed as follows:

R2(config)#router bgp 65001
R2(config-router)#bgp router-id 2.2.2.2
R2(config-router)#neighbor 10.0.0.1 remote-as 65001
R2(config-router)#exit

Following this configuration, the show ip bgp summary command can be used to verify the state of the configured neighbors. The output of this command shows the following:

R1#show ip bgp summary
BGP router identifier 1.1.1.1, local AS number 65001
BGP table version is 1, main routing table version 1Neighbor    V    AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down  State/PfxRcd
10.0.0.2    4 65001       2       2        0    0    0 00:00:15        0

On R2, the output of the show ip bgp summary also shows the established peer relationship:

R2#show ip bgp summary
BGP router identifier 2.2.2.2, local AS number 65001
BGP table version is 1, main routing table version 1Neighbor    V    AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down  State/PfxRcd
10.0.0.1    4 65001       2       2        0    0    0 00:00:05        0

For iBGP peers, the output of the show ip bgp neighbors command is similar to that of the same command when eBGP peers have been configured on the router, with the primary difference being that the link type is internal versus external as shown in the following output:

R1#show ip bgp neighbors 10.0.0.2
BGP neighbor is 10.0.0.2,  remote AS 65001, internal link
  BGP version 4, remote router ID 2.2.2.2
  BGP state = Established, up for 00:00:26
Last read 00:00:26, last write 00:00:26, hold time is 180, keepalive interval is 60 seconds[Truncated Output]

Configuring Non-directly Connected eBGP Neighbor Relationships

The configuration of iBGP peers that are not directly connected requires additional commands in Cisco IOS software as is the case when configuring eBGP peers that are not directly connected. While the neighbor [address] update-source [interface name] command is still required for TCP connectivity, the multihop command is not required when configuring iBGP peers that are not directly connected.

The reason the multihop command is not required is because Cisco IOS software sets the IP TTL to 255 because it is assumed that iBGP peers are not always directly connected. There is currently no command in Cisco IOS software to modify this default behavior, i.e. to change the IP TTL of these packets when configuring iBGP peers that are not directly connected. The primary advantage of setting the TTL to 255 is that it allows iBGP peers to use alternate paths to maintain the adjacency in case some physical interfaces within the interior network fail.
Unlike with eBGP peers, where the preferred peer configuration uses the physical interface IP addresses, with iBGP, the preferred peer configuration is to use Loopback interfaces. These interfaces are the most resilient interfaces in Cisco IOS routers. In addition to this, because most interior networks have multiple paths between devices for redundancy, this peering implementation allows iBGP sessions to stay up even when some of the physical links in the interior network fail. This also allows for greater stability within the autonomous system.

Figure 6-30 shows a basic network comprised of two routers. Both routers reside in autonomous system 65001. The Loopback0 interface of R1 is 1.1.1.1/32, while the Loopback0 interface of R2 is 2.2.2.2/32. Two physical links are provisioned between the routers for redundancy.

The network is running OSPF as the IGP of choice. OSPF is primarily used to provide router Loopback-to-Loopback connectivity between the two routers. The logical topology is below:

6-30
Fig. 6-30. External BGP Peering Using Physical Interface Addresses

Prior to configuring the non-directly connected peer relationship, it is always prudent to verify IP connectivity or reachability between the two routers. Following is the output of the show ip route command on R1 for the 2.2.2.2/32 address, which is the address of R2s Loopback0:

R1#show ip route 2.2.2.2 255.255.255.255
Routing entry for 2.2.2.2/32
Known via “ospf 1”, distance 110, metric 65, type intra area
Last update from 10.0.0.2 on Serial0/0, 00:00:52 ago
Routing Descriptor Blocks:
* 10.0.1.2, from 10.0.1.2, 00:00:52 ago, via Serial0/1
Route metric is 65, traffic share count is 1
  10.0.0.2, from 10.0.1.2, 00:00:52 ago, via Serial0/0
Route metric is 65, traffic share count is 1

However, as we learned in previous chapters, just because a route is in the routing table does not mean that it is reachable. It is always therefore good practice to also verify Loopback-to-Loopback connectivity using a simple ping, for example, as is shown in the following output:

R1#ping 2.2.2.2 source 1.1.1.1 repeat 10Type escape sequence to abort.
Sending 10, 100-byte ICMP Echos to 2.2.2.2, timeout is 2 seconds:
Packet sent with a source address of 1.1.1.1
!!!!!!!!!!
Success rate is 100 percent (10/10), round-trip min/avg/max = 1/2/4 ms

Once connectivity has been confirmed, the non-directly connected iBGP peers are configured following the same sequence of steps used when configuring non-directly connected eBGP peers; however, the neighbor [address] ebgp-multihop command is omitted. This is implemented as follows on R1:

R1(config)#router bgp 65001
R1(config-router)#bgp router-id 1.1.1.1
R1(config-router)#neighbor 2.2.2.2 remote-as 65001
R1(config-router)#neighbor 2.2.2.2 update-source loopback 0
R1(config-router)#exit

Similar configuration is also implemented on R2, as illustrated in the following output:

R2(config)#router bgp 65001
R2(config-router)#bgp router-id 2.2.2.2
R2(config-router)#neighbor 1.1.1.1 remote-as 65001
R2(config-router)#neighbor 1.1.1.1 update-source loopback 0
R2(config-router)#exit

Again, the show ip bgp summary should be used to verify that the peer relationship has been established. This is confirmed on R1 as follows:

R1#show ip bgp summary
BGP router identifier 1.1.1.1, local AS number 65001
BGP table version is 1, main routing table version 1Neighbor   V    AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down  State/PfxRcd
2.2.2.2    4 65001       4       4        1    0    0 00:00:28        0

Now that we have a solid understanding on how to enable iBGP and eBGP using both directly connected interfaces and non-directly connected interfaces, we will conclude this chapter by learning about the different methods that can be used advertise networks when running BGP.

Prev

Next

About Us

This is a free bonus site for members of www.howtonetwork.com

Copyright

The content on this copyright Reality Press Ltd.
Copyright Reality Press Ltd.