Friday, October 7, 2011

LAB: BGP Communities No-Advertise

- Configure R2 so that it does not advertise prefixes received from AS 254 to any peer.
- Do not use any sort of prefix filtering to accomplish this

configuration:

R2:
route-map SET_COMMUNITY
set community no-advertise
!
router bgp 200
neighbor 192.10.1.254 route-map SET_COMMUNITY in

verification:

Rack1R2#
Rack1R2#show ip bgp regexp 254
BGP table version is 78, local router ID is 222.22.1.1
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
              r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete

   Network          Next Hop            Metric LocPrf Weight Path
*> 205.90.31.0      192.10.1.254             0             0 254 ?
*> 220.20.3.0       192.10.1.254             0             0 254 ?
*> 222.22.2.0       192.10.1.254             0             0 254 ?


Rack1R2#show ip bgp 205.90.31.0
BGP routing table entry for 205.90.31.0/24, version 81
Paths: (1 available, best #1, table Default-IP-Routing-Table, not advertised to any peer)
Flag: 0x880
  Not advertised to any peer
  254
    192.10.1.254 from 192.10.1.254 (222.22.2.1)
      Origin incomplete, metric 0, localpref 100, valid, external, best
      Community: no-advertise

No comments:

Post a Comment