The MPLS-OPS Archive

Cell Relay Retreat>MPLS-OPS Archive>month:2004-Oct> msg00081



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

Combining MPLS- and non-MPLS-Traffic

  • From: Garry Glendown <garry@regio.net>
  • Date: Tue, 26 Oct 2004 08:48:44 +0200
  • Resent-Date: Tue, 26 Oct 2004 03:14:58 -0400
  • User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
  • X-Enigmail-Supports: pgp-inline, pgp-mime
  • X-Enigmail-Version: 0.86.1.0

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