Sorry for the delayed response. I don't remember all the details of the
lab, but I can tell you that the purpose of neighbor <neighbor-address>
send-community"
string is to instruct the router to pass along any community information
that may be included in each prefix. If you are flagging any routing info
with community information, you must specify to include this info when
exchanging updates with neighbors, either by "neighbor x.x.x.x send
community" or by assigning that attribute (and any other common
info/attributes) to a peer-group, then putting each BGP peer in that peer
group.
Dan Pontrelli
Customer Installation Engineer - Verio NYC
CCNP, MCSE, CNA
----- Original Message -----
From: "Nigel Taylor" <[EMAIL PROTECTED]>
To: "Dan" <[EMAIL PROTECTED]>; "David FAHED" <[EMAIL PROTECTED]>
Cc: "CCIE_Lab Group Study" <[EMAIL PROTECTED]>; "Cisco Group Study"
<[EMAIL PROTECTED]>; "Bryant Andrews" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Sunday, February 25, 2001 7:35 PM
Subject: Re: Fatkid - Adv BGP Lab 325
> Dan,
> I understand the fatkid solution to flag the inbound routing
> information as it enters AS200. I don't have a problem with this at all.
>
> My question was on the need for the various "neighbor <neighbor-address>
> send-community" on all of the bgp peers within AS200. This command
enables
> the use of the community attribute but you also need a route-map to pass
the
> "no-export" variable. In the fatkid solution all the neighbor peers on
R2,
> R3, and R4 have
>
> "neighbor <neighbor-address> send-community" on them so I was trying to
> figure out the purpose for this.
>
> Compared to the configuration I came up with, I applied the above noted
> configuration to R2 and R3(outbound) pointing to R4. I didn't see the
need
> for the extra commands on R4 to the route-rreflector-clients
>
> I know there's a number of ways to achieve specific goals but I was just
> trying to get an overall understanding of the solution provided looking at
> requirements to a lab or using best design/configuration practices. My
> thinking suggest that since task 11 asked for the routes from AS300 not to
> be exported to AS100, then the emphasis on filtering these inbound routes
> shouldn't be of major concern. As long as the both entry points apply the
> outward "no-export" community attribute then there is really no way R4
would
> pass the external (AS300)routes to AS100. Another key reason I'm thinking
> is the use of the bgp router-id providing a IGP routable path to all BGP
> peers.
>
> I included a paste of my final relevant configs... compared to the fatkid
> solution...
>
> thoughts.
>
> Nigel..
>
> R2:
>
> router bgp 200
> bgp router-id 190.19.15.145
> redistribute eigrp 200 route-map localnet
> neighbor 190.19.15.177 remote-as 200
> neighbor 190.19.15.177 update-source Loopback0
> neighbor 190.19.15.177 send-community
> neighbor 190.19.15.177 route-map setcom out
> neighbor 210.10.10.5 remote-as 300
> neighbor 210.10.10.5 weight 450
> no auto-summary
> !
> ip classless
> !
> dialer-list 1 protocol ip permit
> route-map setcom permit 10
> set community no-export
>
>
>
> R3:
>
> router bgp 200
> bgp router-id 190.19.15.161
> redistribute eigrp 200 route-map localnet
> neighbor 190.19.15.177 remote-as 200
> neighbor 190.19.15.177 update-source Loopback0
> neighbor 190.19.15.177 send-community
> neighbor 190.19.15.177 route-map setcom out
> neighbor 210.10.10.1 remote-as 300
> no auto-summary
> !
> ip classless
> !
> dialer-list 1 protocol ip permit
> route-map setcom permit 10
> set community no-export
>
>
> R4:
> router bgp 200
> bgp router-id 190.19.15.177
> bgp log-neighbor-changes
> redistribute eigrp 200 route-map localnet
> neighbor 190.19.15.145 remote-as 200
> neighbor 190.19.15.145 update-source Loopback0
> neighbor 190.19.15.145 route-reflector-client
> neighbor 190.19.15.161 remote-as 200
> neighbor 190.19.15.161 update-source Loopback0
> neighbor 190.19.15.161 route-reflector-client
> neighbor 192.19.15.1 remote-as 100
> neighbor 192.19.15.1 route-map weight250 in
> no auto-summary
>
>
>
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
