[c-nsp] Matching all MPLS traffic for a class map

[Temkin, David]

Unfortunately because there's no IP involved, I don't think it would
work.  I could attempt to match it on ingress interface, but I have a
feeling that there's no "ingress interface" known to it on the egress
interface because the traffic was technically sourced at the router (as
mpls) when it was transformed from ATM. 

> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net 
> [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Marko 
> Milivojevic
> Sent: Tuesday, August 03, 2004 12:04 PM
> To: cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] Matching all MPLS traffic for a class map
> 
> > Over MPLS directly to another router
> 
>     Well, that doesn't help. Anyway, I had an idea, and I 
> will write it here, anyway. You see if you can use it:
> 
> 
> --->{ingress_1}[router_1]{egress_1}---{MPLS 
> --->CLOUD}---{ingress_2}[router_2]
> 
>     So, you have some traffic coming into router_1 on 
> ingress_1 interface and going out the egress_1. What you 
> *could* do is something like this (I admit, it is based on 
> assumption that there is IP involved, but it *could* be used somehow):
> 
> router_1:
> ---------
> 
> class-map INGRESS_1
>  match input-interface ingress_1
> !
> policy-map EGRESS_1_POLICY
>  class INGRESS_1
>   set <something_you_could_set>
> !
> interface egress_1
> !pvc x/y
>  service-policy out EGRESS_1_POLICY
> !
> 
> router_2:
> ---------
> class-map INGRESS_2
>  match <something_you_could_set> !ip precedence?
> !
> policy-map INGRESS_2_POLICY
>  class INGRESS_2
>   ...
> !
> interface ingress_2
> ! pvc x/y
>  service-policy in INGRESS_2_POLICY
> !
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net 
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
> 
> 

IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments.  Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited.  Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument.  Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.