From: Kevin Baumgartner (kbaumgar@xxxxxxxxx)
Date: Thu Sep 28 2000 - 01:26:35 GMT-3
Actually the examples of have seen more commonly used are setting
the community no-export. What happens then is the route 0.0.0.0 will
be sent to BGP neighbor router 2.2.2.2. Router 2.2.2.2 will not forward
the 0.0.0.0 route on any neighbor routers.
Also need to add "neighbor 2.2.2.2 send-community" in your configuration.
A excellent book on BGP with configurations is Internal Routing
Architecures by Bassam Halabi.
Kevin
>
> Hey guys, I need some help with something. CAn someone explain for me
> the community attribute. I understand that it can be used to control
> which routes are sent by a downstream router to its downstream
> router(s). However, see below really confuses me. Can someone explain
> it? THanks.
>
> Assume that on Router C you want to set to 300 the community attribute
> of outgoing updates for network 170.10.0.0. The following
> commands apply a route map to outgoing updates on Router C:
>
> !Router C
> router bgp 300
> network 170.10.0.0
> neighbor 2.2.2.2 remote-as 100
> neighbor 2.2.2.2 route-map SETCOMMUNITY out
> !
> route-map SETCOMMUNITY permit 10
> match ip address 1
> set community 300
> !
> access-list 1 permit 0.0.0.0 255.255.255.255
>
>
> Access list 1 denies any update for network 170.10.0.0 and permits
> updates for any other network.
>
> FYI it is from the BGP section of the Cisco CD.
> --
>
>
>
> Mark Salmon
> Network Support Engineer
> SBC OP HQ
> Cisco Systems Inc
> 8735 W. Higgins Road
> Suite 300
> Chicago IL 60631
> Phone:773-695-8235
> Pager:800-365-4578
> email: masalmon@cisco.com
> Empowering The Internet Generation.
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:25:08 GMT-3