This would be because you are matching DSCP EF packets in your TEST policy-map. Since you are sending a ping, or for that matter anything that is not EF, it would fall into the class-default class as that catches any packets which don't fall into any of the manually configured class-maps.
If you would like to test EF you could either send your pings with a TOS value of 184 which is the equivalent to EF DSCP, or you could make a new class-map matching icmp-echo using NBAR if supported, just to name a few, there are many other ways.
Thanks for the reply Joe, I guess I didn't explain it very well. I understand that I am matching EF traffic only and all other traffic should go to the default class but I don't see any traffic going to the default class apart from the ping traffic eventhough there is a constant flow of traffic on the interface as per the show interface output and input result. Why the packets aren't showing up in the default class if they aren't EF and only the ping traffic shows up in the default class?
Introduction: The "external-out enable" command is available for
configuration under the "router ospf process" in case of the IOS-XR
operating system. This command basically enables advertisement of
intra-area routes on the device as external routes in th...
IntroductionIn this article we'll discuss how to troubleshoot packet
loss in the asr9000 and specifically understanding the NP drop counters,
what they mean and what you can do to mitigate them. This document will
be an ongoing effort to improve troublesh...