- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
06-06-2017 02:10 PM
When one is looking at interface counters, does "rate severity" provide context for the "value"?
Since in some cases 1000 drops is not a big deal while others it may be.
name value rate severity category aspect description
--------------------------------------------------------------------------------
session_state_error 27215 0 drop session pktproc Session state error
session_dup_pkt_drop 838866 0 drop session resource Duplicate packet: Applies only for multi-DP platform with
06-06-2017 02:17 PM
Those are actually two different fields.
Rate is the number of packets per second for the duration you've run.
So if you run the counter command after 5 seconds and the total number of counters is 1000, then your rate would be 200 (1000/5 seconds).
Severity is the type of counter: flow, drop, error, info, etc.
In your example, the first counter has 27215 as the value, 0 as the rate (none incremented since the last time the counters were displayed) and drop is the severity. Same explanation for the 2nd counter.
Hope this helps,
Greg
06-07-2017 07:05 AM
Thanks, that makes sense. I knew you could see the difference in counters from each time it was checked with
> show counter global filter severity drop
> show counter global filter delta yes severity drop
But I didn't know the "rate" was tied to that as well.
Thanks.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!