The packet is classified on input.
*UNLESS* you use table-label in a l3vpn, then it gets re-classified
after the label POP.
On 2/3/13 6:03 PM, Chris Kawchuk wrote:
It was my understanding that the label was logically popped on
Egress (in terms of how one would envision the packet flow);
*UNLESS* you use table-label in a l3vpn, then it gets re-classified after the
label POP.
Aha, Very true - Good ole vrf-table-label
So, to Alexandre for L3VPN, just do this:
class-of-service {
routing-instances {
all {
classifiers {
exp MY-CLASIFIER;
2 matches
Mail list logo