Hi Rene,
Appreciate your wonderful insight.
Hope you bear with me for a couple more of clarifications
q1) I often read in MQC that classification is to be done during ingress and queueing at the egress.
But when defining an egress policy-map using CBWFQ, you will still somehow classify the traffic
e.g.
policy-map VOIP
class VOIP-class <<< isn’t this already classification ?
priority 888
What the point in classifying during ingress then ?
q2) I am seeing the below on my MPLS service provider CE router’s WAN side interface
interface GigabitEthernet0/1
service-policy input xxx-inpolicypolicy-map xxx-inpolicy
class ce_ef_input
class ce_af3_input
class class-default
In xxx-inpolicy, there are just class definitions without any bandwidth policy/shaping, queuing, nor marking done - nothing. What is the point/meaning of classifying the traffic without any action done in the service-policy ?
q3) is there anyway simple way we can monitor the bandwidth usage of a particular queue ? or even a particular class ? I am on 3850 and the show policy-map is reflecting 0 packets/bytes for class-maps (but the queues are reflecting incrementing bytes-output ) – seems like a bug after googling.
Regards,
Alan