Re: MPLS VPN EIGRP PE-CE SOO

> 2 separate community values used for different operation and protocols, RT
> for importing routes in to the right VRF, SoO for 'tagging' and blocking
> routes being redistributed into BGP and back into EIGRP between sites...
>
> EIGRP MPLS VPN PE-CE Site of Origin Support Overview
> The EIGRP MPLS VPN PE-CE Site of Origin feature introduces SoO support for
> EIGRP-to-BGP and BGP-to-EIGRP redistribution. The SoO extended community is
> a BGP extended community attribute that is used to identify routes that have
> originated from a site so that the readvertisement of that prefix back to
> the source site can be prevented. The SoO extended community uniquely
> identifies the site from which a PE router has learned a route. SoO support
> provides the capability to filter MPLS VPN traffic on a per-EIGRP-site
> basis. SoO filtering is configured at the interface level and is used to
> manage MPLS VPN traffic and to prevent routing loops from occurring in
> complex and mixed network topologies, such as EIGRP VPN sites that contain
> both VPN and backdoor links.
>
> The configuration of the SoO extended community allows MPLS VPN traffic to
> be filtered on a per-site basis. The SoO extended community is configured in
> an inbound BGP route map on the PE router and is applied to the interface.
> The SoO extended community can be applied to all exit points at the customer
> site for more specific filtering but must be configured on all interfaces of
> PE routers that provide VPN services to CE routers.
>
>
> http://www.cisco.com/en/US/docs/ios/iproute_eigrp/configuration/guide/ire_mpls_vpn_ps6441_TSD_Products_Configuration_Guide_Chapter.html#wp1057043
>
>
> route-target
>
> The route-target command creates lists of import and export route target
> extended communities for the specified VRF.
>
>
> http://www.cisco.com/en/US/docs/ios/mpls/command/reference/mp_m4.html#wp1025916
>
>
>
>
> I have it working with different values, based on the topology from this
> INE blog...
>
>
> http://blog.ine.com/wp-content/uploads/2010/04/understanding-eigrp-soo-bgp-cost-community.pdf
>
>
> PE2#sh bgp vpnv4 unicast all 172.16.1.1/32
> BGP routing table entry for 100:4:172.16.1.1/32, version 24
> Paths: (1 available, best #1, no table)
> Not advertised to any peer
> Local
> 10.0.4.4 (metric 2297856) from 10.0.4.4 (10.0.4.4)
> Origin incomplete, metric 2297856, localpref 100, valid, internal,
> best
> Extended Community: SoO:100:100 RT:100:1
> Cost:pre-bestpath:128:2297856 (default-2145185791) 0x8800:32768:0
> 0x8801:100:640000 0x8802:65281:1657856 0x8803:65281:1500
> mpls labels in/out nolabel/26
> BGP routing table entry for 100:5:172.16.1.1/32, version 25
> Paths: (1 available, best #1, table VPN_A)
> Not advertised to any peer
> Local, imported path from 100:4:172.16.1.1/32
> 10.0.4.4 (metric 2297856) from 10.0.4.4 (10.0.4.4)
> Origin incomplete, metric 2297856, localpref 100, valid, internal,
> best
> Extended Community: SoO:100:100 RT:100:1
> Cost:pre-bestpath:128:2297856 (default-2145185791) 0x8800:32768:0
> 0x8801:100:640000 0x8802:65281:1657856 0x8803:65281:1500
> mpls labels in/out nolabel/26
>
>
> PE2#sh ip eigrp vrf VPN_A topology 172.16.1.1/32
> IP-EIGRP (AS 100): Topology entry for 172.16.1.1/32
> State is Passive, Query origin flag is 1, 1 Successor(s), FD is 2297856
> Routing Descriptor Blocks:
> 10.0.4.4, from VPNv4 Sourced, Send flag is 0x0
> Composite metric is (2297856/0), Route is Internal (VPNv4 Sourced)
> Vector metric:
> Minimum bandwidth is 1544 Kbit
> Total delay is 25000 microseconds
> Reliability is 255/255
> Load is 1/255
> Minimum MTU is 1500
> Hop count is 1
> Extended Community: SoO:100:100
> 172.16.25.1 (Serial0/1), from 172.16.25.1, Send flag is 0x0
> Composite metric is (2809856/2297856), Route is Internal
> Vector metric:
> Minimum bandwidth is 1544 Kbit
> Total delay is 45000 microseconds
> Reliability is 255/255
> Load is 1/255
> Minimum MTU is 1500
> Hop count is 2
>
> CE2#sh ip route 172.16.1.1
> Routing entry for 172.16.1.1/32
> Known via "eigrp 100", distance 90, metric 2297856, type internal
> Redistributing via eigrp 100
> Last update from 172.16.12.1 on Serial0/0, 02:07:37 ago
> Routing Descriptor Blocks:
> * 172.16.12.1, from 172.16.12.1, 02:07:37 ago, via Serial0/0
> Route metric is 2297856, traffic share count is 1
> Total delay is 25000 microseconds, minimum bandwidth is 1544 Kbit
> Reliability 255/255, minimum MTU 1500 bytes
> Loading 1/255, Hops 1
>
>
>
>
> --
> Garry L. Baker
>
> "With sufficient thrust, pigs fly just fine..." - RFC 1925
>
>
>
> On Tue, May 24, 2011 at 10:49 AM, imran ali <immrccie_at_gmail.com> wrote:
>
>> HI ALL
>>
>> Can eigrp Soo value and rt be different ?
>>
>>
>>
>> ce1--pe------pe---ce2 --backdoor link to ce1
>>
>>
>>
>> if i use rt value 100:1 and soo value of 100:2 ..wil this avoild tranisent
>> routing loops or soo value must match with RT for that VPN.
>>
>>
>> Blogs and organic groups at http://www.ccie.net
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Fri May 27 2011 - 19:25:10 ART