0% found this document useful (0 votes)
71 views4 pages

Configuring BGP No Advertise Community

The document describes configuring BGP community no advertise on a network topology. The tasks are to: 1) Configure IP addresses and check connectivity between routers. 2) Configure IBGP and EBGP and verify route distribution. 3) Configure a route map on R1 to set the no-advertise community and prevent advertising 1.1.1.1/32 to R3 and R4. 4) Verify that R3 and R4 no longer receive the route in their BGP tables.

Uploaded by

Alex Machado
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
71 views4 pages

Configuring BGP No Advertise Community

The document describes configuring BGP community no advertise on a network topology. The tasks are to: 1) Configure IP addresses and check connectivity between routers. 2) Configure IBGP and EBGP and verify route distribution. 3) Configure a route map on R1 to set the no-advertise community and prevent advertising 1.1.1.1/32 to R3 and R4. 4) Verify that R3 and R4 no longer receive the route in their BGP tables.

Uploaded by

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

Download PNETLab Platform

PNETLAB Store
[Link]

BGP Community No Advertise

Lab Topology:
Please use the following topology to complete this lab exercise:

Lab Objective:
The objective of this lab exercise is for you to learn and understand how can you configure BGP
Community No Advertise

Task list:
Task 1: Configure the hostname and IP address for the interface for Routers as topo. Check the
reachability between Routers.
Task 2: Configure BGP (IBGP, EBGP) at all Router. R1 advertise L0 interface to BGP. Check the
status of [Link]/32 at the others Router.
Task 3: Config Community BGP at R1 so that R1 tell R2 will not advertise prefix to others
Router (R3,R4)
Task 4: Check BGP Table on R2, R3 and R4 to verify the configuration at Task 3.

1
Download PNETLab Platform
PNETLAB Store
[Link]

SOLUTION:
Task 1: Configure the hostname and IP address for the interface for Routers as topo. Check the
reachability between Routers.
On R1
!
interface Loopback0
ip address [Link] [Link]
!
interface Ethernet0/0
ip address [Link] [Link]
!
On R2
!
interface Ethernet0/0
ip address [Link] [Link]
!
interface Ethernet0/1
ip address [Link] [Link]
!
interface Ethernet0/2
ip address [Link] [Link]
!
On R3
!
interface Ethernet0/1
ip address [Link] [Link]
!
On R4
!
interface Ethernet0/2
ip address [Link] [Link]
!
Verification:
R2#ping [Link]
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to [Link], timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
R2#ping [Link]
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to [Link], timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/2 ms
R2#ping [Link]
Type escape sequence to abort.
2
Download PNETLab Platform
PNETLAB Store
[Link]

Sending 5, 100-byte ICMP Echos to [Link], timeout is 2 seconds:


!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/2 ms
Task 2: Configure BGP (IBGP, EBGP) at all Router. R1 advertise L0 interface to BGP. Check the
status of [Link]/32 at the others Router.
On R1
!
router bgp 1
bgp log-neighbor-changes
network [Link] mask [Link]
neighbor [Link] remote-as 23
!
On R2
!
router bgp 23
bgp log-neighbor-changes
neighbor [Link] remote-as 1
neighbor [Link] remote-as 23
neighbor [Link] next-hop-self
neighbor [Link] remote-as 4
neighbor [Link] next-hop-self
!
On R3
!
router bgp 23
bgp log-neighbor-changes
neighbor [Link] remote-as 23
!
On R4
!
router bgp 4
bgp log-neighbor-changes
neighbor [Link] remote-as 23
!
Verification:
R2#show ip bgp
Network Next Hop Metric LocPrf Weight Path
*> [Link]/32 [Link] 0 0 1 i

R3#show ip bgp
Network Next Hop Metric LocPrf Weight Path
*>i [Link]/32 [Link] 0 100 0 1 i

R4#show ip bgp
Network Next Hop Metric LocPrf Weight Path
3
Download PNETLab Platform
PNETLAB Store
[Link]

*> [Link]/32 [Link] 0 23 1 i


// So every Router has the prefix [Link]/32 in BGP Table. No need to talk so much in here.

Task 3: Config Community BGP at R1 so that R1 tell R2 will not advertise prefix to others
Router (R3,R4)
On R1
!
route-map SET_COMMUNITY permit 10
set community no-advertise
!
router bgp 1
neighbor [Link] send-community
neighbor [Link] route-map SET_COMMUNITY out
!
//Create Route-map to set community no-advertise
//Configure bgp neighbor with R2 but specify we will send 1 community with note that R2 don’t
advertise to other Router.
//After configuration, please use command “clear ip bgp * soft” in both R1 and R2.

Task 4: Check BGP Table on R2, R3 and R4 to verify the configuration at Task 3.
On R2
R2#show ip bgp [Link]
BGP routing table entry for [Link]/32, version 3
Paths: (1 available, best #1, table default, not advertised to any
peer)
Not advertised to any peer
Refresh Epoch 2
1
[Link] from [Link] ([Link])
Origin IGP, metric 0, localpref 100, valid, external, best
Community: no-advertise
rx pathid: 0, tx pathid: 0x0

R2#show ip bgp
Network Next Hop Metric LocPrf Weight Path
*> [Link]/32 [Link] 0 0 1 i

R3#show ip bgp

R4#show ip bgp

//So we will recognize that, in R2, it still get the prefix [Link]/32 but it will not advertise to
other Router (R3,R4).

You might also like