Juniper JUNOSE 11.3, Configuration Manual

Page: 217 / 632

Table 23: Interface Strings (continued)
Common Description
Format-Mode Enabled Common Description
Format-Mode Disabled
Type of Interface
SgInterface SgInterface Sg interfaces
MplsL2Shim MplsL2Shim MPLS L2 Shim interfaces
MplsVcSub MplsL3Shim MPLS VC Sub interfaces
LacGen LacGen LacGen interfaces
Bridge BridgeIf Bridge interfaces
IpsecTransport IPSecTransportIf IpSec Transport interfaces
Ipv6 IPv6If IPv6 interfaces
Ipv6Tunnel IPv6TunnelIf IPv6 Tunnel interfaces
Ipv6Loopback IPv6LoopbackIf IPv6 loopback interfaces
Osi Osi OSI interfaces
Lag Lag LAG interfaces
IpTunnelMdt IpTunnelMdt Ip 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.
Configuring Collectors and Receivers
To configure the router to collect statistics:
187 Copyright © 2010, Juniper Networks, Inc.
Chapter 4: Configuring SNMP