[j-nsp] about counter statistics interface

[Stefan Fouant]

The Netscreen docs certainly leave a lot to be desired in this case...

The 'Early Frame' and 'Late Frame' counters are essentially buffer
management counters.  If there was a wide discrepancy between the two
numbers there might be reasonable cause for alarm, but in your case the
numbers are almost identical so it's not a problem.
The 'In Overrun' counter displays the number of times that the receiver
hardware was incapable of passing the received data to a hardware buffer.
This is usually caused because the input rate exceeded the receiver's
capability to handle the data.

Regards,

Stefan Fouant

On 12/5/07, Ibariouen Khalid <ibariouen.khalid at ericsson.com> wrote:
>
> All,
>
> I am having problems interpreting some results that I am getting when I
> run the command - get counter statistics interface ****.
>
> I am seeing an unusually high number of "Early Frame" and "Late Frame"
> packets as well as "in overrun"
>
>
> Can anyone give me a better description of how to interpret these
> errors?  What does it mean if a packet is "in overrun" what is an
> "early/late frame"?
>
> Appreciate the help!
>
>
>
>
>
>
> ******************
>
>
>
> FWCMN1(M)-> get counter statistics interface ethernet2/2 Hardware counters
> for interface ethernet2/2:
>
> in bytes 2243249951 | out bytes 1911354492 | early frame
>
> 74773910
>
> in packets 2030137468 | out packets 1737737719 | late frame
>
> 74773912
>
> in no buffer 0 | out no buffer 54 | re-xmt limit
>
> 0
>
> in overrun 8019232 | out underrun 0 | drop vlan
>
> 110654
>
> in coll err 0 | out coll err 0 | out cs lost
>
> 0
>
> in misc err 8019232 | out misc err 104 |
>
> in dma err 0 | out bs pak 0 |
>
> in crc err 0 | out discard 0 |
>
> in align err 0 | out defer 0 |
>
> in short frame 0 | out heartbeat 0 |
>
> Hardware 64-bit counters for interface ethernet2/2:
>
> in bytes 2875576382018 | out bytes
>
> 2621841407080
>
> in ucast 116 | out ucast
>
> 0
>
> in mcast 0 | out mcast
>
> 0
>
> in bcast 0 | out bcast
>
> 0
>
> Total flow counters for interface ethernet2/2:
>
> in bytes 3974849114 | out bytes 403077707 | tcp proxy
>
> 0
>
> in packets 2007008032 | out packets 1732980484 | tear drop
>
> 191
>
> in vlan 2022116880 | out vlan 3470745392 | in permit
>
> 3880638718
>
> out permit 3563191518 | src route 0 | no g-parent
>
> 102881
>
> ping of death 0 | no gate sess 0 | address spoof
>
> 275
>
> in icmp 86695711 | no nat vector 57040 | land attack
>
> 0
>
> in self 0 | no map 0 | icmp flood
>
> 0
>
> in un-auth 0 | no conn 0 | udp flood
>
> 0
>
> in unk prot 0 | no dip 145164 | winnuke
>
> 0
>
> in vpn 165401645 | no gate 0 | port scan
>
> 173604
>
> in other 0 | no xmit vpnf 0 | ip sweep
>
> 422
>
> no mac 0 | no route 63153 | tcp out of seq
>
> 0
>
> mac relearn 0 | no frag sess 0 | wrong intf
>
> 0
>
> slow mac 0 | no frag netpak 0 | wrong slot
>
> 0
>
> trmng queue 0 | no sa 12510 | icmp broadcast
>
> 0
>
> trmng drop 0 | no sa policy 0 | illegal pak
>
> 6200062
>
> tiny frag 0 | sa inactive 58531 | url block
>
> 0
>
> syn frag 0 | sa policy deny 0 | encrypt fail
>
> 0
>
> connections 313225640 | policy deny 41482251 | mp fail
>
> 0
>
> misc prot 0 | auth deny 0 | auth fail
>
> 0
>
> loopback drop 0 | big bkstr 0 | proc sess
>
> 0
>
> mal url 0 | sessn thresh 611158 | invalid zone
>
> 0
>
> null zone 0 | no nsp-tunnel 0 | IP cls failure
>
> 0
>
> first pak frag 0 | unknown pak 15511226 | multiauth drop
>
> 0
>
> multi-DIP drop 0 |
>
> multi-DIP drop 0 |
>
>
>
>
>
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>