The MPLS-OPS Archive

Cell Relay Retreat>MPLS-OPS Archive>month:2001-Nov> msg00147



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

Fwd: FW: How to Differentiate Traffic ?

  • From: "Chris C.," <theguber@hotmail.com>
  • Date: Wed, 28 Nov 2001 01:38:31 +0000
  • Cc: mpls-ops@mplsrc.com
  • Resent-Date: Tue, 27 Nov 2001 23:27:09 -0500
  • To: raszuk@cisco.com
  • X-OriginalArrivalTime: 28 Nov 2001 01:38:31.0631 (UTC) FILETIME=[62F44DF0:01C177AD]
  • X-Originating-IP: [63.88.104.205]

Robert,

I have see this solution recommended several times before in real life. Both 
Cisco and Juniper seem to follow this path.

However how can this be implemented if:

1. You have a CPE that does not support this? Like a DSL Bridge as an 
example.

2. You do not have a CPE. EG: Ethernet port off a L2 LAN Switch in a MTU 
model.

It seems in this case you need to be able to cater for this functionality at 
the PE. Right?



>-----Original Message-----
>From: Robert Raszuk [mailto:raszuk@cisco.com]
>Sent: Tuesday, November 27, 2001 6:40 PM
>To: krishnak@sify.com
>Cc: MPLSRC
>Subject: Re: How to Differentiate Traffic ?
>
>KK,
>
> > In this situation, customer is using MPLS VPN for his VPN requirements.
>But some of his
> > traffic has to come out onto the Provider network, say for accessing
>server located on
> > Service provider's backbone.
>
>The simplest way to separate the traffic which destination is provider's
>global table at least from the forwarding perspective is to build a GRE
>tunnel on the PE-CE int and therefor have additional logical
>subinterface into your PE.
>
>R.
>

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp

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