Scribd
Upload
40 views3 pages

Commands

The document provides configuration instructions for BGP on multiple routers (R1, R6, R2, R3, R4, R5) within different autonomous systems, including setting up a confederation in AS 200. It also includes steps to check for errors and resolve issues related to unreachable next hops by using the 'next-hop-self' command. Finally, verification commands are suggested to ensure proper BGP route propagation.

Uploaded by

sagar002100
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
40 views3 pages

Commands

The document provides configuration instructions for BGP on multiple routers (R1, R6, R2, R3, R4, R5) within different autonomous systems, including setting up a confederation in AS 200. It also includes steps to check for errors and resolve issues related to unreachable next hops by using the 'next-hop-self' command. Finally, verification commands are suggested to ensure proper BGP route propagation.

Uploaded by

sagar002100
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 3

++ Configure BGP on R1:

config t
router bgp 100
neighbor 130.10.12.2 remote-as 200
network 11.11.11.0 mask 255.255.255.0
exit

-------------------------------------------------------------

++ Configure BGP on R6:

config t
router bgp 300
neighbor 130.10.56.5 remote-as 200
network 33.33.33.0 mask 255.255.255.0
exit

-------------------------------------------------------------

++ Configure BGP in AS 200 with Confederation:

--> On R2:

config t
router bgp 64512
neighbor 130.10.12.1 remote-as 100
neighbor 170.10.3.3 remote-as 64513
neighbor 170.10.3.3 update-source loopback 0
neighbor 170.10.3.3 ebgp-multihop 255
bgp confederation identifier 200
exit

--> On R3:

config t
router bgp 64513
neighbor 170.10.2.2 remote-as 64512
neighbor 170.10.2.2 update-source loopback 0
neighbor 170.10.2.2 ebgp-multihop 255
neighbor 170.10.4.4 remote-as 64514
neighbor 170.10.4.4 update-source loopback 0
neighbor 170.10.4.4 ebgp-multihop 255
bgp confederation identifier 200
exit

--> On R4:

config t
router bgp 64514
neighbor 170.10.3.3 remote-as 64513
neighbor 170.10.3.3 update-source loopback 0
neighbor 170.10.3.3 ebgp-multihop 255
neighbor 170.10.5.5 remote-as 64515
neighbor 170.10.5.5 update-source loopback 0
neighbor 170.10.5.5 ebgp-multihop 255
bgp confederation identifier 200
exit
--> On R5:

config t
router bgp 64515
neighbor 130.10.56.6 remote-as 300
neighbor 170.10.4.4 remote-as 64514
neighbor 170.10.4.4 update-source loopback 0
neighbor 170.10.4.4 ebgp-multihop 255
bgp confederation identifier 200
exit
=============================================================

NOTE: CHECK ERRORS ON ALL 4 ROUTERS::

To solve it,

--> ON R2,

config t
router bgp 64512
bgp confederation peers 64513
end

--> ON R3,

config t
router bgp 64513
bgp confederation peers 64512 64514
end

--> ON R4,

config t
router bgp 64514
bgp confederation peers 64513 64515
end

--> ON R5,

config t
router bgp 64515
bgp confederation peers 64514
end
=============================================================

++ Verification :::
On all routers,

R# clear ip bgp *
R# show ip bgp

(Routes are received but they are not the best path because next hop is
unreachable)

To solve this,

On R2:
config t
router bgp 64512
neighbor 170.10.3.3 next-hop-self
end

On R3:

config t
router bgp 64513
neighbor 170.10.2.2 next-hop-self
neighbor 170.10.4.4 next-hop-self
end

On R4:

config t
router bgp 64514
neighbor 170.10.3.3 next-hop-self
neighbor 170.10.5.5 next-hop-self
end

On R5:

config t
router bgp 64515
neighbor 170.10.4.4 next-hop-self
end
=======================================================

You might also like