Thanks everyone for the suggestions. I've gone ahead and created some
policy-maps on the 3600X that will set the correct qos-group and
imposition exp values so that I'm able to preserve the original CoS
markings in both directions.
Jose
On 11/6/2012 4:39 PM, Pshem Kowalczyk wrote:
Hi,
On 7
Hi everyone. I was hoping I could get some help with an EoMPLS config
I'm working on between an ME3600X and an ME6524 and being able to
preserve the CoS field values.
The xconnect pseudowire it actually up and able to pass traffic so
that's not a problem. The issue is that any CoS values I
Hi,
On 7 November 2012 08:04, Lobo loboti...@gmail.com wrote:
Hi everyone. I was hoping I could get some help with an EoMPLS config I'm
working on between an ME3600X and an ME6524 and being able to preserve the
CoS field values.
The xconnect pseudowire it actually up and able to pass
I was under the impression that the rewrite ingress tag pop 1
symmetric was required in order for the xconnect to work? Removing it
seems to break the xconnect as traffic no longer goes across it.
So is MQC with qos-groups is the only way to preserve the markings with
this platform?
Jose
Hi,
On 7 November 2012 09:47, Lobo loboti...@gmail.com wrote:
I was under the impression that the rewrite ingress tag pop 1 symmetric
was required in order for the xconnect to work? Removing it seems to break
the xconnect as traffic no longer goes across it.
It's required if the other end
