Understanding Counter Discontinuity; Configuring Collectors And Receivers - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - SYSTEM BASICS CONFIGURATION GUIDE 2010-10-04 Configuration Manual

Understanding Counter Discontinuity

Configuring Collectors and Receivers

Copyright © 2010, Juniper Networks, Inc.
Table 23: Interface Strings (continued)
Type of Interface
Sg interfaces
MPLS L2 Shim interfaces
MPLS VC Sub interfaces
LacGen interfaces
Bridge interfaces
IpSec Transport interfaces
IPv6 interfaces
IPv6 Tunnel interfaces
IPv6 loopback interfaces
OSI interfaces
LAG interfaces
Ip Tunnel MDT interfaces
Interface counter discontinuity can occur when a counter wraps or after a line module is
reloaded or reset. If one of these actions occurs, applications that utilize the counters in
expressions or calculations generate erroneous values and misleading graphs.
Because counters are 64 bits long, the possibility of a counter's wrapping naturally would
occur so infrequently (for example, in many hundreds of years) that this scenario is not
recognized as an issue.
Counter discontinuity does occur, however, when you reload or reset a line module. To
indicate reloading or resetting, bulk statistics files contain a record similar to the following:
{Controller down slot 3, TUE OCT 29 2004 14:25:10.370 UTC}
This record provides a mechanism by which applications can detect discontinuity events.
To take advantage of this detection capability, the bulk statistics parsing entity should
use the record to terminate expression or formula calculations for the indicated slot and
to establish a new baseline.
To configure the router to collect statistics:
Common Description
Format-Mode Disabled
SgInterface
MplsL2Shim
MplsL3Shim
LacGen
BridgeIf
IPSecTransportIf
IPv6If
IPv6TunnelIf
IPv6LoopbackIf
Osi
Lag
IpTunnelMdt
Chapter 4: Configuring SNMP
Common Description
Format-Mode Enabled
SgInterface
MplsL2Shim
MplsVcSub
LacGen
Bridge
IpsecTransport
Ipv6
Ipv6Tunnel
Ipv6Loopback
Osi
Lag
IpTunnelMdt
187