The MPLS-OPS Archive

[Robert Raszuk <raszuk@cisco.com>]

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.

> krishnak@sify.com wrote:
> 
> Hi,
> 
> I would like to differentiate VPN traffic and non VPN traffic on the same link from CE to PE.
> 
> 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.
> I can actually configure access-lists to classify this traffic, since I know the source address/port from which the traffic originates.
> 
> Specifically, when I configure this on Cisco, on customer interface, I would like to apply this access-list to the command - "ip vrf forwarding VPN1" so that traffic mathcing to this ACL should not get tagged with this VPN.
> I don't see a way in this interface configuration or address-family definitions, or any where else....
> Is it possible like this?...
> 
> Any help, configuration sample is highly appreciated..
> 
> KK
> -------------------------------------------------
> This mail helped a tree grow. Know more at http://green.sify.com
> 
> Want to win a PC or Palm Tops or Digital Diaries or T-Shirts?
> Click here http://promos.sify.com/niit/main.asp?mail
> 
> -------
> 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