From: Lupi, Guy (Guy.Lupi@xxxxxxxxxxxxx)
Date: Thu Feb 14 2002 - 21:23:59 GMT-3
You should just have to have the following, which will allow all other
routes to pass untouched.
route-map setcomm permit 10
match ip address 1
set community no-export
!
route-map setcomm permit 20
!
access-list 1 permit 172.16.0.0 0.0.255.255
~-----Original Message-----
~From: Jaspreet Bhatia [mailto:jasbhati@cisco.com]
~Sent: Thursday, February 14, 2002 7:04 PM
~To: ccielab@groupstudy.com
~Subject: Route Maps
~
~
~Folks ,
~ Can someone help me understand this concept ..
~
~
~If I use the following route map
~
~
~neighbor 3.3.3.3 remote-as 300
~neighbor 3.3.3.3 send-community
~neighbor 3.3.3.3 route-map setcomm out
~
~route-map setcomm permit 10
~match ip address 1
~set community no-export
~
~access-list 1 permit 172.16.0.0 0.0.255.255
~
~up to here I understand that for all routing updates belonging to the
~172.16.0.0 network going to the neighbor 3.3.3.3 in remote-as
~300 , they
~will have their community attribute set to no-export and the
~updates will
~not leave as 300 .
~
~Now do I have to add the line for the other networks in my as to flow
~through untouched and not have their community attribute
~changed ???????
~
~route-map setcomm permit 20
~set community none
~
~
~in order for all the routes to pass through the as 300
~
~Thanks
~
~Jaspreet
This archive was generated by hypermail 2.1.4 : Thu Jun 20 2002 - 13:46:23 GMT-3