Juniper SYSTEM BASICS - CONFIGURATION GUIDE V 11.1.X

Table 23: Interface Strings (continued)
Common Description
Format-Mode Enabled
Common Description
Format-Mode DisabledType of Interface
L2fSessionL2fSessionL2fSession interfaces
L2fDestinationL2fDestinationL2fDestination interfaces
IpsecTunnelIpSecTunnelIpSec Tunnel interfaces
SgInterfaceSgInterfaceSg interfaces
MplsL2ShimMplsL2ShimMPLS L2 Shim interfaces
MplsVcSubMplsL3ShimMPLS VC Sub interfaces
LacGenLacGenLacGen interfaces
BridgeBridgeIfBridge interfaces
IpsecTransportIPSecTransportIfIpSec Transport interfaces
Ipv6IPv6IfIPv6 interfaces
Ipv6TunnelIPv6TunnelIfIPv6 Tunnel interfaces
Ipv6LoopbackIPv6LoopbackIfIPv6 loopback interfaces
OsiOsiOSI interfaces
LagLagLAG interfaces
IpTunnelMdtIpTunnelMdtIp Tunnel MDT interfaces
Understanding Counter Discontinuity
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.
198 ■ Collecting Bulk Statistics
JUNOSe 11.1.x System Basics Configuration Guide