The MPLS-OPS Archive[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] Re: REG: Mapping traffic to an LSP
Joe, Many people asked the same. so I am cc'ing the
group.
my topo:
R1-----Mpls cloud--------R2----VPN prefixes/nets
R1, R2 = PE's
R1 = igress, R2 =egress in this example
R5 is in the cloud, is the RR
goal:
from R1, traffic to prefixes with RT = 1:2 shd take
tunnel101. traffic to prefixes with RT = 1:3 shd take
tunnel102.
R2 config:
router bgp 1
neighbor 10.10.10.5 remote-as 1
address-family vpnv4
neighbor 10.10.10.5 activate
neighbor 10.10.10.5 route-map foo out
!
route-map foo permit 10
match extcommunity 99
set ip next-hop 10.10.10.101
!
route-map foo permit 20
match extcommunity 98
set ip next-hop 10.10.10.102
!
route-map foo permit 30
!
ip extcommunity-list 98 permit rt 1:3
ip extcommunity-list 99 permit rt 1:2
!
Config on R1:
interface Tunnel101
ip unnumbered Loopback0
tunnel destination 10.10.10.2
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng path-option 10 dynamic
!
interface Tunnel102
ip unnumbered Loopback0
tunnel destination 10.10.10.2
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng path-option 10 dynamic
!
ip route 10.10.10.101 255.255.255.255 Tunnel101
ip route 10.10.10.102 255.255.255.255 Tunnel102
!
Verification:
from R2:
R2#sho ip bgp v v Red 10.10.223.0
BGP routing table entry for 1:2:10.10.223.0/24,
version 12
Paths: (1 available, best #1)
Advertised to non peer-group peers:
10.10.10.5
Local
0.0.0.0 from 0.0.0.0 (10.10.10.102)
Origin incomplete, metric 0, localpref 100,
weight 32768, valid, sourced, best
Extended Community: RT:1:2
R2#sho ip bgp v v Blue 10.10.222.0
BGP routing table entry for 1:3:10.10.222.0/24,
version 13
Paths: (1 available, best #1)
Advertised to non peer-group peers:
10.10.10.5
Local
0.0.0.0 from 0.0.0.0 (10.10.10.102)
Origin incomplete, metric 0, localpref 100,
weight 32768, valid, sourced, best
Extended Community: RT:1:3
>From R1:
R1#sho ip bgp v v Red 10.10.223.0
BGP routing table entry for 1:2:10.10.223.0/24,
version 28
Paths: (1 available, best #1)
Advertised to non peer-group peers:
10.10.112.12
Local
10.10.10.101 from 10.10.10.5 (10.10.10.5)
Origin incomplete, metric 0, localpref 100,
valid, internal, best
Extended Community: RT:1:2
Originator: 10.10.10.102, Cluster list:
10.10.10.5
R1#
R1#sho ip bgp v v Blue 10.10.222.0
BGP routing table entry for 1:3:10.10.222.0/24,
version 29
Paths: (1 available, best #1)
Not advertised to any peer
Local
10.10.10.102 from 10.10.10.5 (10.10.10.5)
Origin incomplete, metric 0, localpref 100,
valid, internal, best
Extended Community: RT:1:3
Originator: 10.10.10.102, Cluster list:
10.10.10.5
R1#sho ip rou 10.10.10.101
Routing entry for 10.10.10.101/32
Known via "static", distance 1, metric 0 (connected)
Routing Descriptor Blocks:
* directly connected, via Tunnel101
Route metric is 0, traffic share count is 1
R1#sho ip rou 10.10.10.102
Routing entry for 10.10.10.102/32
Known via "static", distance 1, metric 0 (connected)
Routing Descriptor Blocks:
* directly connected, via Tunnel102
Route metric is 0, traffic share count is 1
--- Joseph Anthony <tonyjoe20002002@yahoo.co.in>
wrote:
>
> Hi Gopal,
> You are right, I was referring to the TE tunnels as
> LSPs. Yes I am using Cisco equipment as PE routers,
> Can you kindly give me any sample config
> illustrating the VRF mapping to a TE tunnel. Hope I
> am not asking too much out of you.
> Thanks in advance,
> Joe.
>
> Catch all the cricket action. Download Yahoo! Score
tracker
__________________________________________________
Do you Yahoo!?
Yahoo! Web Hosting - Let the expert host your site
http://webhosting.yahoo.com
-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
|
|