Re: BGP community attribute

From: damien (damien@xxxxxxxxxxx)
Date: Thu Sep 28 2000 - 11:09:43 GMT-3


   
I am not sure about the last statement, but basically, any ip prefix in the
update ( access-list 1 permit 0.0.0.0 255.255.255.255) sent to 2.2.2.2 will
have the community attribute field set to 300......I am not sure what he is
talking about any "Access list 1 denies any update for network 170.10.0.0
and permits updates for any other network.".......to me he/ she is talking
b0!!03..........
>

----- Original Message -----
From: "mark salmon" <masalmon@cisco.com>
To: <ccielab@groupstudy.com>
Sent: Thursday, September 28, 2000 6:09 AM
Subject: BGP community attribute

> 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