Hi Matt, Remove route-map sequence 30. You are already exporting 100:1 so you don't need that.
Also, a good way to test what prefixes are getting tagged with an extcommunity is to do the following: 1. Configure an ip extcommunity-list permitting the RT you want to check 2. Configure a route-map matching the extcommunity-list you have configured above, don't apply this route-map to anything. 3. Run the command "show ip bgp vpnv4 all route-map <route-map name> The above just creates a route-map filter for confirming all is working properly and the prefixes you wish to tag are being tagged. Do a hard clear of the BGP process too which will help too. Also, give your route-map and prefix-lists a worded name and not just numerical, I know it sounds silly but its caught me out before in the past. Thanks. Joe. On Mon, Mar 29, 2010 at 3:00 AM, <[email protected]>wrote: > Send CCIE_SP mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://onlinestudylist.com/mailman/listinfo/ccie_sp > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of CCIE_SP digest..." > > > Today's Topics: > > 1. Vol 1 Lab16.11 VRF import/export (Matt Hill) > 2. Service Provider Labs in ProctorLabs (Volume 1 and Volume 2) > (Marko Milivojevic) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 28 Mar 2010 16:45:19 +1100 > From: Matt Hill <[email protected]> > Subject: [OSL | CCIE_SP] Vol 1 Lab16.11 VRF import/export > To: "<[email protected]>" <[email protected]> > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi There, > > Trying do do the exporting into other VRFs here, but it is not > working. All of the routes are appearing in R5's routing table when > they should not be. > > R5: > ! > ip vrf GREEN > rd 100:1 > route-target export 100:2 > route-target import 100:2 > route-target import 100:1 > route-target import 100:100 <------ want to see these > ! > ! > ! > ! > ! > ! > interface FastEthernet0/0 > ip vrf forwarding GREEN > ip address 150.50.55.5 255.255.255.0 > speed 100 > full-duplex > ! > ! > router bgp 100 > no bgp default ipv4-unicast > bgp log-neighbor-changes > neighbor 200.0.0.2 remote-as 100 > neighbor 200.0.0.2 update-source Loopback0 > ! > address-family ipv4 > neighbor 200.0.0.2 activate > no auto-summary > no synchronization > exit-address-family > ! > address-family vpnv4 > neighbor 200.0.0.2 activate > neighbor 200.0.0.2 send-community extended > exit-address-family > ! > address-family ipv4 vrf GREEN > redistribute connected > no synchronization > exit-address-family > ! > ip forward-protocol nd > ! > ! > no ip http server > no ip http secure-server > > > ! > ! > ! > R5#show ip route vrf GREEN > > Routing Table: GREEN > Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP > D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area > N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 > E1 - OSPF external type 1, E2 - OSPF external type 2 > i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2 > ia - IS-IS inter area, * - candidate default, U - per-user static > route > o - ODR, P - periodic downloaded static route > > Gateway of last resort is not set > > 100.0.0.0/24 is subnetted, 2 subnets > B 100.100.100.0 [200/0] via 200.0.0.2, 00:09:34 > B 100.100.200.0 [200/0] via 200.0.0.2, 00:09:34 <---- dont > want to see this one > 200.0.0.0/32 is subnetted, 1 subnets > B 200.0.0.1 [200/0] via 200.0.0.2, 00:09:34 > 150.50.0.0/24 is subnetted, 2 subnets > C 150.50.55.0 is directly connected, FastEthernet0/0 > B 150.50.12.0 [200/0] via 200.0.0.2, 00:09:34 > R5# > > > Now for R2 > ! > ip vrf RED > rd 100:1 > export map 100 > route-target export 100:1 > route-target import 100:1 > route-target import 100:2 > ! > > interface FastEthernet1/0 > no switchport > ip vrf forwarding RED > ip address 150.50.12.2 255.255.255.0 > duplex full > speed 100 > ! > router bgp 100 > no bgp default ipv4-unicast > bgp log-neighbor-changes > neighbor AS100 peer-group > neighbor AS100 remote-as 100 > neighbor AS100 update-source Loopback0 > neighbor 150.50.12.1 remote-as 10000 > neighbor 200.0.0.4 peer-group AS100 > neighbor 200.0.0.5 peer-group AS100 > neighbor 200.0.0.6 peer-group AS100 > ! > address-family ipv4 > neighbor 200.0.0.5 activate > no auto-summary > no synchronization > exit-address-family > ! > address-family ipv4 multicast > neighbor AS100 route-reflector-client > neighbor 200.0.0.4 activate > neighbor 200.0.0.6 activate > no auto-summary > no synchronization > exit-address-family > ! > address-family vpnv4 > neighbor AS100 send-community extended > neighbor 200.0.0.5 activate > exit-address-family > ! > address-family ipv4 vrf RED > neighbor 150.50.12.1 remote-as 10000 > neighbor 150.50.12.1 activate > no synchronization > exit-address-family > ! > ip prefix-list 100 seq 5 permit 100.100.100.0/24 > ! > ip prefix-list 200 seq 5 permit 100.100.200.0/24 <---match this > ! > route-map 100 permit 10 > match ip address prefix-list 100 > set extcommunity rt 100:100 > ! > route-map 100 permit 20 > match ip address prefix-list 200 <------ match this > set extcommunity rt 100:200 <---- I am not importing this on R5 > ! > route-map 100 permit 30 > set extcommunity rt 100:1 > ! > > > it appears that my export map is not tagging the extcommunity 100:100 > & 100:200 for some reason... > > R5#show ip bgp vpnv4 vrf GREEN 100.100.200.0 > BGP routing table entry for 100:1:100.100.200.0/24, version 7 > Paths: (1 available, best #1, table GREEN) > Not advertised to any peer > 10000 > 200.0.0.2 (metric 65) from 200.0.0.2 (200.0.0.2) > Origin IGP, metric 0, localpref 100, valid, internal, best > Extended Community: RT:100:1 > mpls labels in/out nolabel/22 > R5#show ip bgp vpnv4 vrf GREEN 100.100.100.0 > BGP routing table entry for 100:1:100.100.100.0/24, version 6 > Paths: (1 available, best #1, table GREEN) > Not advertised to any peer > 10000 > 200.0.0.2 (metric 65) from 200.0.0.2 (200.0.0.2) > Origin IGP, metric 0, localpref 100, valid, internal, best > Extended Community: RT:100:1 > mpls labels in/out nolabel/21 > > > Anyone know why? > > > Cheers, > Matt > > CCIE #22386 > CCSI #31207 > > > ------------------------------ > > Message: 2 > Date: Sun, 28 Mar 2010 14:21:54 +0000 > From: Marko Milivojevic <[email protected]> > Subject: [OSL | CCIE_SP] Service Provider Labs in ProctorLabs (Volume > 1 and Volume 2) > To: OSL Service Provider <[email protected]> > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=UTF-8 > > Hello everyone, > > We noticed some errors in few of our SP labs in both Volume 1 and > Volume 2. These are minor errors that are the result of upcoming > changes in the ProctorLabs topology. > > R2's Frame Relay connection has DLCIs that start with 1 (104, 105, > 106) and routers R4, R5 and R6 have DLCIs pointing to R2 that end with > 1 (401, 501 and 601). On some of the ProctorLabs racks, these DLCIs > have been rerouted elsewhere, therefore breaking these few labs. If > you see these in your workbooks, please, replace number 1 with 2 (204, > 205, 206, 402, 502 and 602) and you should be fine. > > We have already corrected all of our workbooks, solutions guides and > configurations. Corrected material should be coming your way early > next week. ProctorLabs scripts that load configurations will be > updated today. > > Sorry about this guys. I hope you were not inconvenienced too much. > > -- > Marko Milivojevic - CCIE #18427 > Senior Technical Instructor - IPexpert > > YES! We include 400 hours of REAL rack > time with our Blended Learning Solution! > > Mailto: [email protected] > Telephone: +1.810.326.1444 > Fax: +1.810.454.0130 > Web: http://www.ipexpert.com/ > > > End of CCIE_SP Digest, Vol 36, Issue 18 > *************************************** >
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
