Help with "sh oer master traffic-class" output?

Unanswered Question
Mar 5th, 2010
  Hi everyone,

   I'm working with PfR/OER and am studying the output of "sh oer master traffic-class," trying to understand everything in that display.  Specifically, I'm interested in the below chart:

2811-LSL#show oer master traffic-class detail

Age       Border          Interface       OOP/RteChg Reasons
Pas: DSum  Samples  DAvg  PktLoss  Unreach   Ebytes   Ibytes     Pkts    Flows
Act: Dsum Attempts  DAvg    Comps  Unreach   Jitter LoMOSCnt   MOSCnt
00:55:33         Se1/0.394
        0        0     0     1069        0  1023281        0     8691     2149
      750        5   150        5        0        N        N        N


What I'm looking for is a detailed definition of what all those values in the chart are.  For example:  I presume "Dsum" is "Delay Summary" and the measured unit is milliseconds.  And what exactly are "LoMOSCnt," "Comps," "OOP/RteChg," or "Ibytes?"  The online Cisco documentation I've seen does not say.

   Can anyone point me to some more specific info?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Giuseppe Larosa Sat, 03/06/2010 - 06:27

Hello Peter,

not all fields are described in OER command reference

but you can find there some explanations

Los = Loss

MOS : indicates packets containing MOS payload in order to perform VoIP quality test

so LoMOSCnt should be number of MOS packets lost

MOSCnt : total number of MOS packets

Ibytes = ingress bytes

Ebytes= egress bytes

OOP/Rtechg =  second part should stay for route change, first part could mean out of path packets that have travelled on other paths rather then on monitored /expected ones

Dsum could be the sum of delays (750) to be used to calculate average delay and jitter (delay variation)

if so Comps could mean compliant samples (with delay in SLA)

Hope to help


Peter Hummon Mon, 03/08/2010 - 06:38

Hi Giuseppe,

Thanks for the tip! I wonder why Cisco doesn't document this information. These statistics seem meaningless if you don't know what they are. Oh well.

Do you mind taking a quick glance at the below; I've tried to expressly document every stat. In particular, I'm still confused about "Samples," "Attempts," "Comps," and "Jitter." (I know what jitter is, but don't see how it is calculated here.)

Peter Hummon Mon, 03/08/2010 - 06:41

Sorry, for some reason the rest of my email was chopped off.  Here's what should have appeared after the above text:


Age               Timestamp marking the end of a monitoring period

Border            IP of Border Router

Interface         Int on Border Router

OOP/RteChg        Reasons     Number of packets which have traveled on Out Of Path (OOP) routes than over monitored ones.

Pas:DSum          Sum of packet delays to be used to calculate average delay and jitter

Pas:Samples       ???

Pas:DAvg          Average Delay per packet  (Pas:Dsum/Pas:Pkts)

Pas:PktLoss       Number of packets lost

Pas:Unreach       Number of packets sent to an unreachable prefix

Pas:Ebytes        Number of bytes egressing the router

Pas:Ibytes        Number of bytes ingressing the router

Pas:Pkts          Total number of packets seen on this interface

Pas:Flows         Total number of flows seen on this interface

Act:Dsum          Sum of packet delays to be used to calculate average delay and jitter

Act:Attempts      ???

Act:DAvg          Average Delay per packet  (Act:Dsum/Act:Pkts)

Act:Comps         Compliant samples  (???)

Act:Unreach       Number of packets sent to an unreachable prefix

Act:Jitter        ???

Act:LoMOSCnt      Number of MOS packets lost

Act:MOSCnt        Total number of MOS packets



                  -Pete Hummon

Giuseppe Larosa Sat, 03/13/2010 - 12:11

Hello Pete,

I tried to look for MOS test description.

There are a number of qualifiers frequently appended to MOS, including MOS-CQS, MOS-LQS, etc.  Refer to ITU-T Recommendation P.800.1 for a description of those.

Resources: ITU-T Recommendations P.10, P.800, and P.800.1

this should give you hopefully a background to understand all the terms

Hope to help


Peter Hummon Mon, 03/15/2010 - 06:55

   Great, thanks Giuseppe!

   I'm surprised Cisco doesn't have some official documentation, but oh well.  The link you've found looks very promising, though.  I think it will do. 

          Many thanks!


Peter Hummon Mon, 03/15/2010 - 07:13


   I can't for the life of me figure out how to mark this thread as "Answered."  OK to close this out...


Giuseppe Larosa Mon, 03/15/2010 - 07:22

Hello Pete,

it is not possible to rate your own posts, but you are allowed to rate the posts of other people using the stars on the left bottom corner

Best Regards


Peter Hummon Mon, 03/15/2010 - 07:26

   Thanks again Giuseppe,

   I don't want to rate my posts; just close out this thread.  You successfully answered the question I posted. 

            Thanks again!



This Discussion

Related Content