The MPLS-OPS Archive

["Amos Rosenboim" <r.amos@zahav.net.il>]

Hi, 
I can think of two options. 
One of them is working for us and the other I didn't ever try.
The first option involves creating different logical interfaces on the
leased line. You can do that by runing frame-relay encapsulation on the
leased line and creating different subinterfaces for each dlci. In that
case you can put one interface in the vrf and keep another outside of
the vrf.

The other option is to use a feature called source address based vrf
selection.

Regards
Amos


-----Original Message-----
From: Garry Glendown [mailto:garry@regio.net] 
Sent: Tuesday, October 26, 2004 8:49 AM
To: mpls-ops@mplsrc.com
Subject: [MPLS-OPS]: Combining MPLS- and non-MPLS-Traffic

Hi,

after getting comfortable with "regular" MPLS connections, I have come 
across a problem I could not yet solve with what I know and/or could 
find in the docs I have ...

Problem: A customer of ours is getting several MPLS connections through 
dedicated DSL lines. Currently he has a leased line for regular Internet

access (w/o MPLS on it). The CE router is not MPLS aware (1600 w/o MPLS 
IOS). The DSL lines ordered for this site are delayed, which results in 
the requirement of routing the MPLS traffic over the regular line.

Now, sending the incoming MPLS traffic to that site is probably not the 
problem, I recon a normal

	ip route vrf CUSTOMER 192.168.1.0 255.255.255.0 cutomer-gw-ip

should do (please correct me if I'm wrong). The question is how do I 
split up the traffic from the customer into the MPLS VPN up? That is, 
keeping all "regular" IP traffic in the internet, but forwarding MPLS 
VPN targeted traffic into the customer vrf?

Tnx, -garry

-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplsrc.com/mpls-ops_archive.shtml

-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplsrc.com/mpls-ops_archive.shtml