[c-nsp] ASR901 EoMPLS Customer COS bits trashed

[George Giannousopoulos]

Hello Caillin,

We have also seen some issues with the ASR901 QoS
In fact the config is very restricting at the moment..

What I know for sure is that the ingress cos markings are copied to the
MPLS EXP bit, so you can try to remark your customer traffic at the other
end

George


On Wed, Oct 10, 2012 at 7:50 AM, Caillin Bathern <caillinb at commtelns.com>wrote:

> Hi list,
>
>
>
> I am seeing some odd behaviour in the lab and I am wondering if anyone
> else knows why this is happening or any alternative...
>
>
>
> I have a simple setup - CE---PE(ASR901)---EoMPLS---PE(ASR901)---CE - I
> also have inline packet capturing devices on all physical links and MPLS
> explicit null turned on to ensure EXP marking is carried through.
>
> A single VLAN (10) in a service instance is been xconnected through on
> the ASR901s as follows:
>
>
>
> pseudowire-class eth
>
> encapsulation mpls
>
> interworking ethernet
>
> !
>
> interface GigabitEthernet0/1
>
> service instance 10 ethernet
>
>   encapsulation dot1q 10
>
>   xconnect 6.6.6.6 10 encapsulation mpls pw-class eth
>
> !
>
>
>
> The CE is a network tester sending VID10 with COS 3, this traffic is
> received on the remote CE however my COS 3 marking is lost...
>
> This behaviour is consistent with tag pop/no tag pop, Ethernet or VLAN
> interworking, service policies or no service policies.
>
>
>
> Why are my customer COS markings being destroyed by the ASR901 when
> within an EoMPLS circuit and is there a way to fix this?
>
>
>
> Cheers,
>
> Caillin
>
> _______________________________________________
> 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/
>