Chapter-5

BGP

1
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 Chapter Objectives

• BGP Concepts & Terminology

• Types of ISP Connections
• Options of BGP connecting to Internet
• BGP Neighbors
• LAB: Basic IBGP Peering
• BGP Split Horizon Rule
• LAB: IBGP Peering using loopbacks
• Configuring BGP Authentication on Cisco IOS
• Peer groups
• Lab - Peer Groups
• Route reflector
• Lab : route reflector
• Lab: route reflector using loopback
• Lab : route reflector with two servers for redundancy
2
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 Chapter Objectives

• EBGP Configuration
• BGP next hop behavior
• LAB: Basic EBGP Configuration & Verify Next-hop Behavior
• EBGP peering using Loopback Interfaces (using EBGP multihop)
• Synchronization rule
• LAB: Verify BGP Synchronization Rule
• BGP Attributes overview
• AS-path /next-hop/Origin attributes
• Weight Attribute

3
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 Chapter Objectives

• Lab: Using Weight Attribute

• Clearing the BGP Session
• Lab : Weight Attribute using Route-maps
• Understanding In/out
• Local Preference
• Lab: Using Local Preference
• Lab : Local preference using Route-maps
• BGP Path Selection Process

4
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 What is BGP?

• BGP (Border Gateway Protocol) is protocol that manages how packets are
routed across the internet through the exchange of routing and reachability
information between edge routers. BGP directs packets between autonomous
systems (AS) -- networks managed by a single
enterprise or service provider.

Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604

 Introduction to BGP

BGP characteristics:
• Biggest and most complex Routing protocol
• Routing protocol of the internet
• It is routing between Autonomous System
• BGP has slowest convergence time
• Mainly used in service provider
• Reliable updates: TCP port 179
• Customer exchanges routes with the ISP
• Supports routing policies
• Hello : 60 Sec and Dead: 180 Sec

6
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 TCP 3 Way Handshake

7
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 BGP Message Types

• OPEN – Establishing Peering Session

• KEEPALIVE – Handshake ta regular interval
• UPDATE – Shutdown a peering session
• NOTIFICATION – Announcing or withdrawing prefixes

8
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 States of BGP

• Idle
• Connect
• Active
• OpenSent
• OpenConfirm
• Established

9
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 BGP Autonomous Systems

► An AS is a collection of networks under a single technical administration.

► IGPs operate within an AS.
► BGP is used between autonomous systems.
► Exchange of loop-free routing information is guaranteed
► Private autonomous system (AS) numbers which range from 64512 to 65535 are used to
conserve globally unique AS numbers. Globally unique AS numbers (1 - 64511) are assigned
by InterNIC . ... A second way is by assigning a Private AS number in the range of 64512 to
65535
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
10
 IGP-EGP

• IGP operates within the Same Autonomous System

• EBGP operates in between Multiple Autonomous System

11
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 BGP Features

► Open Standard
► Exterior Gateway protocol
► Designed for Inter-AS Domain Routing
► Designed to scale huge inter-network like internet.
► Classless.
Support FLSM, VLSM, CIDR, auto and manual summary (BGP-4)
► Updates are incremental and trigger (5 seconds internal and 30 seconds external)
► Path vector protocol
►BGP decides the best route on the basis of attribute of prefix not the link.
►BGP can not route the network alone it relies on IGP for Transport.

12
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 Path Vector

13
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 BGP- AS Path Advertisement

14
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 BGP Loop Prevention Mechanism

15
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 BGP’s loop prevention mechanism

16
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 BGP’s loop prevention mechanism

17
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 When to use BGP

When to use BGP

• A S. working as transit A.S (Ex. ISP)
• A.S. connected to multiple A.S (when the AS is multi-homed) Data traffic path entering or
leaving A.S. need to manipulated
When not to use BGP
• If it is Single-home A.S
• Lack of recourses like memory and less processing power in routers
• Limited understanding about BGP route filtering and path selection processes

18
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 Types of ISP Connection

Types of ISP Connections

° Single Homed
° Dual-homed site
° Multi-homing
° Dual Multi-homed
Connecting to the Internet with BGP
° Default route from provider(s)
° Some routes + default route -
° All routes (full table) -

19
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 Types of ISP Connection

• Single Homed
• Dual-homed site
• Multi-homing
• Dual Multi-homed

20
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 Single homed site

► A site with a single ISP connection is single-homed.

► This is fine for a site that does not depend heavily on Internet or WAN connectivity.
► Either use static routes, or advertise the site routes to the ISP and receive a default
route from the ISP.

21
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 Multihomed site

► A dual-homed site has two connections to the same ISP, either from one router or two
routers.
► One link might be primary and the other backup, or the site might load balance over
both links.
► Either static or dynamic routing would work in this case.

22
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 Multi-homing

► Multi-homing means connecting to more than one ISP at the same time.
► It is done for redundancy and backup if one ISP fails and for better performance if one
ISP provides a better path to frequently used networks.
► This also gives you an ISP independent solution.
► BGP is typically used with multihomed connections.

23
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 Dual Multi-homed

24
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
Connecting to the Internet with BGP Route reception options

► Default route from provider(s)

• Easy on resources, internal traffic routed to nearest BGP router
► Some routes + default route
• Allows for selection of some paths with others falling back to a default route
► All routes (full table)
• Hard on resources, but guarantees the most direct path is taken

25
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 Example default routes from all Providers

26
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
Example default routes from all Providers and partial table

27
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 Full Routes from All Providers

28
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 BGP Neighbors ( IBGP/EBGP)

BGP Neighbor
► BGP neighbors are routers forming TCP connection for exchanging BGP updates.
► Also called as BGP Peers or BGP Speakers.
► Two type of BGP neighbor relationship.
• IBGP (Internal BGP)
• EBGP (external BGP)

29
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP neighbors

30
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 EBGP Neighbors

31
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 BGP Databases ( BGP tables)

Neighbor table
° A list of all configured BGP neighbors.
° Has to be manually configured using neighbor command
# show ip bgp summary
# show ip bgp neighbors
BGP forwarding table/database
A list of networks known by BGP, along with their paths and attributes.
# show ip bgp
IP routing table
° List of best paths to destination networks
# Sh ip route
32
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 Configuring BGP Routing Protocol

33
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Configuration

34
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 LAB: IBGP Peering

35
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Peering Configuration

TASK:
• Configure IBGP peering AS 500 as per the diagram using directly connected Interfaces.
• Make sure that all the routers should be able to see the routes from other routers in the
routing table through BGP
R1(config)#router bgp 500
Rl(config-router)# neighbor 1.1.1.2 remote-as 500
Rl(config-router)# neighbor 4.4.4.1 remote-as 500
R1(config-router)#network 10.0.0.0
Rl(config-router)# network 1.0.0.0
Rl(config-router)# network 4.0.0.0
Rl(config-router)#network 11.0.0.0 mask 255.255.255.0
Rl(config-router)# no auto-summary
36
Rl(config-router)# no Rathod
Prepared by: Jagdish synchronization
Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Peering Configuration

NOTE:
• To advertise with default mask value ex: 10.0.0.0/8 no need to use mask
• to advertise with exact mask other than default like 11.0.0.0/24
• make sure that the mask on the interface( shown in routing table as connected) and in the
network command should be same in order to advertise Routes in BGP.
Example: BGP network Command
Router(config-router)# network 192.168.1.1 mask 255.255.255.0
• The router looks for exactly 192.168.1.1/24 in the routing table, but cannot find it, so it will not
announce anything.
Router(config-router)# network 192.168.0.0 mask 255.255.0.0
• The router looks for exactly 192.168.0.0/16 in the routing table.
• If the exact route is not in the table, you can add a static route to nullO so that the route can be
announced

37
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Peering Configuration

R2(config)#router bgp 500

R2(config-router)# neighbor 1.1.1.1 remote-as 500
R2(config-router)# neighbor 2.2.2.2 remote-as 500
R2(config-router)# network 20.0.0.0
R2(config-router)# network 2.0.0.0
R2(config-router)# network 1.0.0.0
R2(config-router)# no auto-summary
R2(config-router)# no synchronization
R2(config-router)# end

38
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Peering Configuration

R3(config)#router bgp 500

R3(config-router)# neighbor 2.2.2.1 remote-as 500
R3(config-router)# neighbor 3.3.3.2 remote-as 500
R3(config-router)# network 30.0.0.0
R3(config-router)# network 3.0.0.0
R3(config-router)# network 2.0.0.0
R3(config-router)# no auto-summary
R3(config-router)# no synchronization
R3(config-router)# end

39
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Peering Configuration

R4(config)#Router bgp 500

R4(config-router)#neighbor 3.3.3.1 remote-as 500
R4(config-router)# neighbor 4.4.4.2 remote-as 500
R4(config-router)# network 40.0.0.0
R4(config-router)# network 4.0.0.0
R4(config-router)# network 3.0.0.0
R4(config-router)# no auto-summary
R4(config-router)# no synchronization
R4(config-router)# exit

40
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Peering Configuration

Check show ip bgp summary on all routers

41
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Peering Configuration

No network 30.0.0.0 in the routing table

42
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Peering Configuration

Here there is No network 40.0.0.0 in the routing table because of BGP SPLIT HORIZON
RULE

43
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 BGP Split horizon rule

► An update send by one IBGP neighbor should not be send back to another IBGP
neighbor
► Prevents Routing loops within an same AS.

44
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 Solution for BGP Split horizon rule

1. full mesh neighbor ship

every router should be a neighbor of every other router with in the AS
2. Use Route Reflector

45
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 Solution for BGP Split horizon rule

BGP SPLIT HORIZON RULE

• An update send by one IBGP neighbor should not be send back to another IBGP neighbor
• BGP split-horizon is necessary to ensure that routing loops are not started within an AS
full-mesh IBGP peering is required within an AS for all the routers within the AS to learn
about the BGP routes.

Why have these restrictions?

• No mechanism to detect an UPDATE loop exists in iBGP.
• What may be the consequences of not having a full iBGP mesh?
• Black holes and routing loops. UPDATE loops. 46
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 Solution for BGP Split horizon rule

Solution:
1. full mesh neighbor ship (means every router should be a neighbor of every other router
with in the AS.)
2. Use Route Reflector
Note : IBGP neighbors need not to be directly connected ( but they must be reachable to
each other )

47
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 Solution for BGP Split horizon rule

Rl(config)#Router bgp 500

Rl(config-router)#Neighbor 2.2.2.2 remote-as 500 (Use Same direction address )
R1(config-router)#end

R2(config)#Router bgp 500

R2(config-router)#Neighbor 3.3.3.2 remote-as 500 (Use Same direction address )
R2(config-router)#end

R3(config)#Router bgp 500

R3(config-router)#Neighbor 1.1.1.1 remote-as 500 (Use Same direction address )
R3(config-router)#end

48
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 Solution for BGP Split horizon rule

R4(config)#Router bgp 500

R4(config-router)#Neighbor 2.2.2.1 remote-as 500 (Use Same direction address )
R4(config-router)#end

49
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 Solution for BGP Split horizon rule

50
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 Solution for BGP Split horizon rule

51
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Peering using loopbacks Interfaces

• Provides Neighbor Redundancy

R1(config)#router bgp 500
R1(config-router)#neighbor 12.0.0.1 remote-as 500
R1(config-router)#neighbor 13.0.0.1 remote-as 500
R1(config-router)#neighbor 14.0.0.1 remote-as 500
R1(config-router)#network 10.0.0.0
R1(config-router)#exit

52
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 BGP Active State Troubleshooting

Active:
The router has sent an open packet and is waiting for a response.
The state may cycle between active and idle.
The neighbor may not know how to get back to this router because of the
following reasons:
• Neighbor is peering with the wrong address.
• Neighbor does not have a neighbor statement for this router.
• AS number is misconfiguration.
• Neighbor does not have a route to the source IP address of the BGP open packet
generated by this router.
• Any extra command missing.(update source)
53
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 Issues with IBGP peering using Loopbacks

Loopbacks must be Reachable

► to send unicast BGP open messages.
► Advertise Loopback interface inside IGP (OSPF/EIGRP/RIP)

Problem with Source

► Default Source will be exit interface
► Change source address to loopback address

54
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 LAB: IBGP Peering USING LOOPBACKS

55
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Peering USING LOOPBACKS

TASK:
• Remove the BGP configurations in the previous lab.
• Configure IBGP AS 500 as per the diagram using directly Loopback Interfaces.
• Make sure that IBGP neighbor relationship should not be affected by the physical status
of the link
• Make sure that all the routers should be able to see the routes from other routers in the
BGP table On Rl, R2 R3 R4
Rx(config)# No Router bgp 500

56
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Peering USING LOOPBACKS

Rl
R1(config)#router bgp 500
R1(config-router)#neighbor 12.0.0.1 remote-as 500
Rl(config-router)#neighbor 13.0.0.1 remote-as 500
Rl(config-router)#neighbor 14.0.0.1 remote-as 500
Rl(config-router)#network 10.0.0.0
Rl(config-router)#no auto-summary
Rl(config-router)#no sync
Rl (config-router)#exit

57
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Peering USING LOOPBACKS

WAN interfaces not preferably advertised in real networks ( It makes your BGP or
routing table more big).
R2(config)#router bgp 500
R2(config-router)#neighbor 11.0.0.1 remote-as 500
R2(config-router)#neighbor 13.0.0.1 remote-as 500
R2(config-router)#neighbor 14.0.0.1 remote-as 500
R2(config-router)#network 20.0.0.0
R2(config-router)#no auto-summary
R2(config-router)#no sync
R2(config-router)#exit

58
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Peering USING LOOPBACKS

R3(config)#router bgp 500

R3(config-router)#neighbor 12.0.0.1 remote-as 500
R3(config-router)#neighbor 11.0.0.1 remote-as 500
R3(config-router)#neighbor 14.0.0.1 remote-as 500
R3(config-router)#network 30.0.0.0
R3(config-router)#no auto-summary
R3(config-router)#no sync
R3(config-router)#exit

59
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Peering USING LOOPBACKS

R4(config)#router bgp 500

R4(config-router)#neighbor 12.0.0.1 remote-as 500
R4(config-router)#neighbor 13.0.0.1 remote-as 500
R4(config-router)#neighbor 11.0.0.1 remote-as 500
R4(config-router)#network 40.0.0.0
R4(config-router)#no auto-summary
R4(config-router)#no sync
R4(config-router)#exit

60
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Peering USING LOOPBACKS

Rl#sh ip bgp summary on R2, R3 and R4

61
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Peering USING LOOPBACKS

Active means its actively trying to establish the neighbor ship (still trying)
BGP Active State Troubleshooting
Active: The router has sent an open packet and is waiting for a response. The state may
cycle between active and idle. The neighbor may not know how to get back to this router
because of the following reasons:
1. Neighbor is peering with the wrong address.
2. Neighbor does not have a neighbor statement for this router.
3. AS number is misconfiguration.
4. Neighbor does not have a route to the source IP address of the BGP open packet
generated by this router.
5. Any extra command missing

62
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Peering USING LOOPBACKS

Sample output of AS number misconfiguration:

At the router with the wrong remote AS number:

%BGP-3-NOTIFICATION: sent to neighbor 172.31.1.3 2/2 (peer in wrong AS) 2 bytes FDE6
FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 002D 0104 FDE6 00B4 AC1F 0203 1002 0601 0400 0100
0102 0280 0002 0202 00

At the remote router:

%BGP-3-NOTIFICATION: received from neighbor 172.31.1.1 2/2 (peer in wrong AS) 2 bytes FDE6

To troubleshoot BGP neighborship

63
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Peering USING LOOPBACKS

First step: Make sure that there is a connectivity to neighbor

64
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Peering USING LOOPBACKS

No entry of the neighbor address (12.0.0.1, 13.0.0.1, 14.0.0.1)

• Here the router R1 don’t know how to reach neighbor address ( 12.0.0.1 ,13.0.0.1 ,
14.0.0.1 )
• To learn about those neighbors BGP relies on IGP protocol ( RIP/EIGRP/OSPF) running
inside the AS.
• Here is the issue is with Routing. To fix it Configure RIP, OSPF, EIGRP any one and make
sure that you also advertise the loopback interface used for IBGP peering

65
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Peering USING LOOPBACKS

R1(config)#router ospf 1
R1(config-router)#net 10.0.0.0 0.255.255.255 area 0 (not)
R1(config-router)#net 1.0.0.0 0.255.255.255 area 0
R1(config-router)#net 4.0.0.0 0.255.255.255 area 0
R1(config-router)#net 11.0.0.0 0.255.255.255 area 0
R1(config-router)#exit

R2(config)#router ospf 1
R2(config-router)#network 20.0.0.0 0.255.255.255 area 0 (not)
R2(config-router)#network 2.0.0.0 0.255.255.255 area 0
R2(config-router)#network 12.0.0.0 0.255.255.255 area 0
R2(config-router)#network 1.0.0.0 0.255.255.255 area 0 66
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Peering USING LOOPBACKS

R3(config)#router ospf 1
R3(config-router)#network 30.0.0.0 0.255.255.255 area 0 (not)
R3(config-router)#network 3.0.0.0 0.255.255.255 area 0
R3(config-router)#network 13.0.0.0 0.255.255.255 area 0
R3(config-router)#network 2.0.0.0 0.255.255.255 area 0
R3(config-router)#end

R4(config)#router ospf 1
R4(config-router)#network 40.0.0.0 0.255.255.255 area 0 (not)
R4(config-router)#network 4.0.0.0 0.255.255.255 area 0
R4(config-router)#network 3.0.0.0 0.255.255.255 area 0
R4(config-router)#network 14.0.0.0 0.255.255.255 area 0
R4(config-router)#end

67
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Peering USING LOOPBACKS

68
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Peering USING LOOPBACKS

Step-2 the other issue can be Problem with source address.

BGP Issues with Source IP Address
• When creating a BGP packet, the neighbor statement defines the destination IP
address and the outbound interface defines the source IP address.
• When a BGP packet is received for a new BGP session, the source address of the packet
is compared to the list of neighbor statements:
• If a match is found, a relationship is established.
• If no match is found, the packet is ignored.
• Make sure that the source IP address matches the address that the other router has in
its neighbor statement.

69
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Peering USING LOOPBACKS

70
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Peering USING LOOPBACKS

• Update-source command allows the BGP process to use the IP address of a specified
interface as the source IP address of all BGP updates to that neighbor.
• A loopback interface is usually used, because it will be available as long as the router is
operational.
• The IP address used in the neighbor command on the other router will be the destination
IP address of all BGP updates and should be the loopback interface of this router.
• The neighbor update-source command is normally used only with IBGP neighbors

71
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Peering USING LOOPBACKS

72
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Peering USING LOOPBACKS

Rl(config)#Router bgp 500

R1(config-router)#Neighbor 12.0.0.1update-source loop 0
R1(config-router)#Neighbor 13.0.0.1update-source loop 0
R1(config-router)#Neighbor 14.0.0.1update-source loop 0
R1(config-router)#end
R2(config)#Router bgp 500
R2(config-router)#Neighbor 11.0.0.1update-source loop 0
R2(config-router)#Neighbor 13.0.0.1update-source loop 0
R2(config-router)#Neighbor 14.0.0.1update-source loop 0
R3(config)#Router bgp 500
R3(config-router)#Neighbor 12.0.0.1update-source loop 0
R3(config-router)#Neighbor 11.0.0.1update-source loop 0
R3(config-router)#Neighbor 14.0.0.1update-source loop 0
R3(config-router)#end
R4(config)#Router bgp 500
R4(config-router)#Neighbor 12.0.0.1update-source loop 0
R4(config-router)#Neighbor 13.0.0.1update-source loop 0
R4(config-router)#Neighbor 11.0.0.1update-source loop 0
R4(config-router)#end
73
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Peering USING LOOPBACKS

74
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Peering USING LOOPBACKS

Rl(config)#int sl/0
R1(config-if)#shutdown

75
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Peering USING LOOPBACKS

76
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Peering USING LOOPBACKS

R1(config)#int sl/0
Rl(config-if)#no shutdown

77
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Peering USING LOOPBACKS

Configuring BGP Authentication on Cisco IOS:

• Border Gateway Protocol (BGP) supports authentication mechanism using Message
Digest 5 (MD5) algorithm.
• When authentication is enabled, any Transmission Control Protocol (TCP) segment
belonging to BGP exchanged between the peers is verified and accepted only if
authentication is successful.
• For authentication to be successful, both the peers must be configured with the same
password.
• If authentication fails, the BGP neighbor relationship is not be established.
Router(config-router)# neighbor {ip-address | peer-group-name} <password string>

78
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Peering USING LOOPBACKS

79
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 BGP Authentication

R1(config)# router bgp 500

Rl(config-router)# neighbor 12.0.0.1 password cisco123
Rl(config-router)# neighbor 13.0.0.1 password ciscol23
Rl(config-router)# neighbor 14.0.0.1 password ciscol23
Rl(config-router)# neighbor 12.0.0.1 version 4
Rl(config-router)# neighbor 13.0.0.1 version 4
Rl(config-router)# neighbor 14.0.0.1 version 4

80
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 Lab: BGP Authentication

81
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 BGP Authentication

TASK
• Make sure that the authentication is established between all the peers and they should
use password as ciscol23.
• The peering should establish only if both the routers runs BGP v4

82
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 BGP Authentication

Continue from previous lab

Rl(config)# router bgp 500

R1(config-router)# neighbor 12.0.0.1 password cisco123
R1(config-router)# neighbor 13.0.0.1 password cisco123
R1(config-router)# neighbor 14.0.0.1 password cisco123
R1(config-router)# neighbor 12.0.0.1 version4
R1(config-router)# neighbor 13.0.0.1 version4
R1(config-router)# neighbor 14.0.0.1 version4
R1(config-router)# end

R2(config)# router bgp 500

R2(config-router)# neighbor 11.0.0.1 password cisco123
R2(config-router)# neighbor 13.0.0.1 password cisco123
R2(config-router)# neighbor 14.0.0.1 password cisco123
R2(config-router)# neighbor 11.0.0.1 version4 83
R2(config-router)# neighbor
Prepared by: Jagdish 13.0.0.1Mail:
Rathod version4
jagdishrj01@gmail.com Mo: 7259459745/8779606604
 BGP Authentication

R3(config)# router bgp 500

R3(config-router)# neighbor 12.0.0.1 password cisco123
R3(config-router)# neighbor 14.0.0.1 password cisco123
R3(config-router)# neighbor 11.0.0.1 password cisco123
R3(config-router)# neighbor 12.0.0.1 version4
R3(config-router)# neighbor 14.0.0.1 version4
R3(config-router)# neighbor 11.0.0.1 version4
R3(config-router)# end

R4(config)# router bgp 500

R4(config-router)# neighbor 11.0.0.1 password cisco123
R4(config-router)# neighbor 12.0.0.1 password cisco123
R4(config-router)# neighbor 13.0.0.1 password cisco123
R4(config-router)# neighbor 11.0.0.1 version4
R4(config-router)# neighbor 12.0.0.1 version4
R4(config-router)# neighbor 13.0.0.1 version4 84
R4(config-router)# end Rathod
Prepared by: Jagdish Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 BGP Authentication

85
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 BGP- Peer-groups

• Apply same policies to multiple neighbors

• useful when many neighbors have the same policies.
• Updates are generated once per peer group.
• Configuration is simplified

86
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 BGP- Peer-groups : configuration

R1(config)#router bgp 500

Rl(config-router)# neighbor CCIE peer-group
Rt(config-router)# neighbor CCIE remote-as 500
Rl(config-router)# neighbor CCIE update-source loopback0
Rl(config-router)# neighbor CCIE version 4
Rl(config-router)# neighbor CCIE password ciscol23
Rl(config-router)# neighbor 12.0.0.1 peer-group CCIE
Rl(config-router)# neighbor 13.0.0.1 peer-group CCIE
Rl(config-router)# neighbor 14.0.0.1 peer-group CCIE

87
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 LAB - PEER GROUPS

88
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 PEER GROUPS

TASK:
Configure peering between R1 R2 R3 R4 with the below configurations:
• Peering to be established using the loop 0 ip address ( X. 0.0.1) of every router
• Make sure that the authentication is established between all the peers and they should
use password as ciscol23.
• The peering should establish only if both the routers runs BGP v4
• Use minimum commands as possible (peer groups).
• Configure IGP as OSPF area 0 to Provide reachability between loopbacks
• Advertise only LAN network only in BGP

89
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 PEER GROUPS

R1(config)#router ospf 1
R1(config-router)#net 10.0.0.0 0.255.255.255 area 0
Rl(config-router)#net 1.0.0.0 0.255.255.255 area 0
Rl(config-router)#net 4.0.0.0 0.255.255.255 area 0
Rl(config-router)#net 11.0.0.0 0.255.255.255 area 0
R1(config-router)#exit

R2(config)#router ospf 1
R2(config-router)#network 20.0.0.0 0.255.255.255 area 0
R2(config-router)#network 2.0.0.0 0.255.255.255 area 0
R2(config-router)#network 12.0.0.0 0.255.255.255 area 0
R2(config-router)#network 1.0.0.0 0.255.255.255 area 0 90
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 PEER GROUPS

R3(config)#router ospf 1
R3(config-router)#network 30.0.0.0 0.255.255.255 area 0
R3(config-router)#network 3.0.0.0 0.255.255.255 area 0
R3(config-router)#network13.0.0.0 0.255.255.255 area 0
R3(config-router)#network 2.0.0.0 0.255.255.255 area 0
R3(config-router)#end

R4(config)#router ospf 1
R4(config-router)#network 40.0.0.0 0.255.255.255 area 0
R4(config-router)#network 4.0.0.0 0.255.255.255 area 0
R4(config-router)#network 3.0.0.0 0.255.255.255 area 0
R4(config-router)#network14.0.0.0 0.255.255.255 area 0
R4(config-router)#end 91
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 PEER GROUPS

R1(config)#router bgp 500

R1(config-router)# neighbor CCIE peer-group
R1(config-router)# neighbor CCIE remote-as 500
R1(config-router)# neighbor CCIE update-source loopback 0
R1(config-router)# neighbor CCIE version 4
R1(config-router)#neighbor CCIE password ciscol23

R1(config-router)# neighbor12.0.0.1 peer-group CCIE

R1(config-router)# neighbor13.0.0.1 peer-group CCIE
R1(config-router)# neighbor14.0.0.1 peer-group CCIE
R1(config-router)# net 10.0.0.0
Rl(config-router)#no auto-summary
R1(config-router)# no synchronization 92
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 PEER GROUPS

R2(config)#router bgp 500

R2(config-router)# neighbor CCIE peer-group
R2(config-router)# neighbor CCIE remote-as 500
R2(config-router)# neighbor CCIE update-source loopback 0
R2(config-router)# neighbor CCIE version 4
R2(config-router)# neighbor CCIE password ciscol23

R2(config-router)# neighbor11.0.0.1 peer-group CCIE

R2(config-router)# neighbor13.0.0.1 peer-group CCIE
R2(config-router)# neighbor14.0.0.1 peer-group CCIE
R2(config-router)#net 20.0.0.0
R2(config-router)#no auto-summary
R2(config-router)# no synchronization 93
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 PEER GROUPS

R3(config)#router bgp 500

R3(config-router)# neighbor CCIE peer-group
R3(config-router)# neighbor CCIE remote-as 500
R3(config-router)# neighbor CCIE update-source loopback 0
R3(config-router)# neighbor CCIE version 4
R3(config-router)# neighbor CCIE password ciscol23

R3(config-router)# neighbor 12.0.0.1peer-group CCIE

R3(config-router)# neighbor 11.0.0.1peer-group CCIE
R3(config-router)# neighbor 14.0.0.1peer-group CCIE
R3(config-router)#net 30.0.0.0
R3(config-router)#no auto-summary
R3(config-router)# no synchronization 94
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 PEER GROUPS

R4(config)#router bgp 500

R4(config-router)# neighbor CCIE peer-group
R4(config-router)# neighbor CCIE remote-as 500
R4(config-router)# neighbor CCIE update-source loopback 0
R4(config-router)# neighbor CCIE version 4
R4(config-router)# neighbor CCIE password ciscol23

R4(config-router)# neighbor 12.0.0.1peer-group CCIE

R4(config-router)# neighbor 13.0.0.1peer-group CCIE
R4(config-router)# neighbor 11.0.0.1peer-group CCIE
R4(config-router)#net 40.0.0.0
R4(config-router)#no auto-summary
R4(config-router)# no synchronization 95
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 PEER GROUPS

96
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 PEER GROUPS

97
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 BGP Split Horizon Rule : Review

► An update send by one IBGP neighbor should not be send back to another IBGP
neighbor
► BGP split-horizon is necessary to ensure that routing loops are not started within an AS

Solution :
1. full mesh neighborship
means every router should be a neighbor of every other router with in AS.
2. Use Route Reflector

98
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Full Mesh Scalability Concerns

Administration
Configuration management on increasingly large number of routers.
Number of TCP Sessions
Total number of sessions = n(n-1)/2
Maintaining extreme numbers of TCP sessions creates Extra overhead.
BGP Table Size
A higher number of neighbors generally translate to a higher number of paths for each route.
Memory consumption

99
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 Route Reflector

► Scalable alternative to an IBGP full mesh.

► Allows a router (route reflector - RR) to advertise routes received from an iBGP peer
to other iBGP peers.
► Client updates server. (Client to client neighborship is not possible) – Only with Server
► Server updates to all the remaining clients.

100
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 IBGP Full Mesh Scalability Concerns

• All Clients should establish neighbor with only servers

• Clients will not establish neighbor with any other client
• In case if you have 2 servers (server establish neighbor with other servers & clients)

101
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 Lab: Route Reflector

102
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 Route Reflector

TASK
• Configure IBGP AS 500 as per the diagram
• Make sure that all the routers should be able to see the routes from other routers in the
routing table through BGP. Do not use full mesh peering.
R1(config)#router bgp 500
R1(config-router)# neighbor 1.1.1.2 remote-as 500
R1(config-router)# network10.0.0.0
R1(config-router)# network 1.0.0.0
R1(config-router)# no auto-summary
R1(config-router)# no synchronization
R1(config-router)# exit

103
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 Route Reflector

R2(config)#router bgp 500

R2(config-router)# neighbor 1.1.1.1 remote-as 500
R2(config-router)# neighbor 2.2.2.2 remote-as 500
R2(config-router)# network 20.0.0.0
R2(config-router)# network 1.0.0.0
R2(config-router)# network 2.0.0.0
R2(config-router)# no synchronization
R2(config-router)# no auto-summary
R2(config-router)#

104
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 Route Reflector

R3(config)#router bgp 500

R3(config-router)# neighbor 2.2.2.1 remote-as 500
R3(config-router)# network 30.0.0.0
R3(config-router)# network 2.0.0.0
R3(config-router)# no auto-summary
R3(config-router)# no synchronization
R3(config-router)# end

105
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 Route Reflector

106
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 Route Reflector

107
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 Route Reflector

R1 and R3 cannot see each other routes in their respective BGP table because of split
horizon rule
In order to get the routes to be learned we have two Solutions:
1. Full mesh neighborship ( which the requirement says not to use here )
2. Route reflector
To Configure Route-reflector
• All Clients should establish neighbor with only servers
• Clients will not establish neighbor with any other client
• In case if you have 2 servers ( server establish neighbor with other servers and clients )

108
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 Route Reflector

R2(config)#Router bgp 500

R2(config-router)# neighbor 1.1.1.1 route-reflector-client
R2(config-router)# neighbor 2.2.2.2 route-reflector-client
R2(config-router)# end

109
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 Route Reflector

110
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 LAB: ROUTE REFLECTOR USING LOOBACK

111
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 ROUTE REFLECTOR USING LOOBACK

TASK:
• Configure BGP AS 500 as per the diagram using Loopback Interfaces.
• To provide Reachability configure RIPv2 as IGP protocol inside AS 500
Rl(config)#router bgp 500
R1(config-router)#neighbor 12.0.0.1 remote-as 500
Rl(config-router)#neighbor 12.0.0.1 update-source loopback 0
Rl(config-router)#network 10.0.0.0
R1(config-router)#no synchronization
Rl(config-router)#no auto-summary
R1(config-router)#exit

112
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 ROUTE REFLECTOR USING LOOBACK

R2(config)#router bgp 500

R2(config-router)#neighbor 11.0.0.1 remote-as 500
R2(config-router)#neighbor 11.0.0.1 update-source loopback 0
R2(config-router)#neighbor 13.0.0.1 remote-as 500
R2(config-router)#neighbor 13.0.0.1 update-source loopback 0
R2(config-router)#network 20.0.0.0
R2(config-router)#no auto-summary
R2(config-router)#no synchronization
R2(config-router)#exit

113
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 ROUTE REFLECTOR USING LOOBACK

R3(config)#router bgp 500

R3(config-router)#neighbor 12.0.0.1 remote-as 500
R3(config-router)#neighbor 12.0.0.1 update-source loopback 0
R3(config-router)#network 30.0.0.0
R3(config-router)#no auto-summary
R3(config-router)#no synchronization
R3(config-router)#exit

R2#sh ip bgp summary

114
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 ROUTE REFLECTOR USING LOOBACK

R1Do Not Have R3 Routes (30.0.0.0) Because Of Split Horizon Rule

115
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 ROUTE REFLECTOR USING LOOBACK

116
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 ROUTE REFLECTOR USING LOOBACK

R3 do not have R1 routes (10.0.0.0) because of split Horizon rule

117
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 ROUTE REFLECTOR USING LOOBACK

TASK: Configure R2 as RR Server and R1 and R3 as RR Clients

R2(config)#router bgp 500
R2(config-router)#neighbor 11.0.0.1 route-reflector-client
R2(config-router)#neighbor 13.0.0.1 route-reflector-client
R2(config-router)#end

118
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 ROUTE REFLECTOR USING LOOBACK

119
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
LAB: ROUTE REFLECTOR WITH TWO SERVERS FOR REDUNDANCY

120
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 ROUTE REFLECTOR WITH TWO SERVERS FOR REDUNDANCY

TASK:
• Configure RIPv2 to provide Reachability between BGP peers
• Configure R2/R4 as RR Server and R1/R3 as Clients
R1(config)#router rip
Rl(config-router)# version 2
Rl(config-router)# network 1.0.0.0
Rl(config-router)# network 4.0.0.0
Rl(config-router)# network 10.0.0.0
Rl(config-router)# network 11.0.0.0
Rl(config-router)# no auto-summary
R1(config-router)#exit
121
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 ROUTE REFLECTOR WITH TWO SERVERS FOR REDUNDANCY

R2(config)#router rip
R2(config-router)# version 2
R2(config-router)# network 1.0.0.0
R2(config-router)# network 2.0.0.0
R2(config-router)# network 20.0.0.0
R2(config-router)# network 12.0.0.0
R2(config-router)# no auto-summary
R2(config-router)#
R2(config-router)#end

122
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 ROUTE REFLECTOR WITH TWO SERVERS FOR REDUNDANCY

R3(config)#router rip
R3(config-router)# version 2
R3(config-router)# network 3.0.0.0
R3(config-router)# network 2.0.0.0
R3(config-router)# network 30.0.0.0
R3(config-router)# network 13.0.0.0
R3(config-router)# no auto-summary
R3(config-router)#end
R3#

123
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 ROUTE REFLECTOR WITH TWO SERVERS FOR REDUNDANCY

R4(config)#router rip
R4(config-router)# version 2
R4(config-router)# network 3.0.0.0
R4(config-router)# network 4.0.0.0
R4(config-router)# network 40.0.0.0
R4(config-router)# network 14.0.0.0
R4(config-router)# no auto-summary
R4(config-router)#end
R4#
R4#sh ip route rip

124
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 ROUTE REFLECTOR WITH TWO SERVERS FOR REDUNDANCY

R1 (RR CLIENT)
Rl(config)#router bgp 500
Rl(config-router)#neighbor 12.0.0.1 remote-as 500
Rl(config-router)#neighbor 12.0.0.1 update-source loopback 0
Rl(config-router)#neighbor 14.0.0.1 remote-as 500
Rl(config-router)#neighbor 14.0.0.1 update-source loopback 0

125
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 ROUTE REFLECTOR WITH TWO SERVERS FOR REDUNDANCY

R3 (RR CLIENT)
R3(config)#router bgp 500
R3(config-router)#neighbor 12.0.0.1 remote-as 500
R3(config-router)#neighbor 12.0.0.1 update-source loopback 0
R3(config-router)#neighbor 14.0.0.1 remote-as 500
R3(config-router)#neighbor 14.0.0.1 update-source loopback 0
R3(config-router)#network 30.0.0.0
R3(config-router)#no auto-summary
R3(config-router)#no synchronization
R3(config-router)#exit

126
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 ROUTE REFLECTOR WITH TWO SERVERS FOR REDUNDANCY

R2 (RR SERVER)
R2(config)#router bgp 500
R2(config-router)#neighbor 11.0.0.1 remote-as 500
R2(config-router)#neighbor 11.0.0.1 update-source loopback 0
R2(config-router)#neighbor 11.0.0.1 route-reflector-client
R2(config-router)#neighbor 13.0.0.1 remote-as 500
R2(config-router)#neighbor 13.0.0.1 update-source loopback 0
R2(config-router)#neighbor 13.0.0.1 route-reflector-client
R2(config-router)#neighbor 14.0.0.1 remote-as 500
R2(config-router)#neighbor 14.0.0.1 update-source loopback 0
R2(config-router)#neighbor 14.0.0.1 route-reflector-client
127
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 ROUTE REFLECTOR WITH TWO SERVERS FOR REDUNDANCY

R2(config-router)#network 20.0.0.0
R2(config-router)#no auto-summary
R2(config-router)#no synchronization
R2(config-router)#exit

128
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 ROUTE REFLECTOR WITH TWO SERVERS FOR REDUNDANCY

R4 (RR server)
R4(config)#router bgp 500
R4(config-router)#neighbor 11.0.0.1 remote-as 500
R4(config-router)#neighbor 11.0.0.1 update-source loopback 0
R4(config-router)#neighbor 11.0.0.1 route-reflector-client
R4(config-router)#neighbor 12.0.0.1 remote-as 500
R4(config-router)#neighbor 12.0.0.1 update-source loopback 0
R4(config-router)#neighbor 12.0.0.1 route-reflector-client
R4(config-router)#neighbor 13.0.0.1 remote-as 500
R4(config-router)#neighbor 13.0.0.1 update-source loopback 0
R4(config-router)#neighbor 13.0.0.1 route-reflector-client
129
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 ROUTE REFLECTOR WITH TWO SERVERS FOR REDUNDANCY

R4(config-router)#network 40.0.0.0
R4(config-router)#no auto-summary
R4(config-router)#no synchronization
R4(config-router)#exit

130
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
ROUTE REFLECTOR WITH TWO SERVERS FOR REDUNDANCY

131
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
ROUTE REFLECTOR WITH TWO SERVERS FOR REDUNDANCY

132
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
ROUTE REFLECTOR WITH TWO SERVERS FOR REDUNDANCY

133
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 Questions and Answer

Q1: Explain BGP?

Q2: Explain Route Map?
Q3: Explain Weight Attribute?
Q4: What is Local Preference?
Q5:Explain MED?

134
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604
 Thank You

135
Prepared by: Jagdish Rathod Mail: jagdishrj01@gmail.com Mo: 7259459745/8779606604