Collecting Bulk Statistics

The router offers an efficient data collection and transfer facility for accounting applications. The E Series router SNMP MIBs extend the accounting data collection mechanism defined in the Accounting-Control-MIB (RFC 2513) to include support for connectionless networks.

Service providers need reasonably accurate data about customers’ use of networks. This data is used for billing customers and must be available at a customer’s request. Accounting applications based on SNMP polling models consume significant network bandwidth because they poll large volumes of data frequently.

Unfortunately, SNMP is not well suited for gathering large volumes of data, especially over short time intervals. It is inadequate for use by accounting applications because:

The SNMP PDU layout has a low payload-to-overhead ratio.
Processing SNMP PDUs is expensive because objects and tables need to be sorted in lexicographic order.

The router avoids the need for continuous polling of SNMP statistics by using applications known as collectors to retrieve data. You can configure up to six collectors. The router sends collected statistics through FTP to assigned hosts, known as receivers. You must assign a primary receiver to each collector, and you can assign a secondary receiver for redundancy.

Note: The basic-encoding-rules (BER)–encoding choice is not supported.

You can collect interface bulk statistics based on sets of virtual router groups. If sets of virtual router groups generally correspond to ISPs, you can then forward the relevant data to a particular ISP.

To configure a collector to include data from a specific list of virtual routers, you must first configure a collector and then associate a router set with it. A collector can have up to 64 virtual routers associated with it.

To collect bulk statistics for a subset of all configured subinterfaces, you can define the subinterfaces using the following syntax:

Slot/Port[.subInterfaceId]

Per virtual router collection is supported on the if-stats and igmp schemas. It is supported on all interface types supported by BulkStats. Collectors modified to use per virtual router collection or configured after a collector has started have a time delay (up to the configured time in seconds) until an active collector starts again.

The maximum number of interfaces for each type of interface and line module can differ. Bulk statistics can collect these statistics when you configure the slots with their respective interfaces to the corresponding maximum values. For information about maximum values see JUNOSe Release Notes, Appendix A, System Maximums.

Note: Define all interface types before you map a collector to the if-stats schema to ensure that you display statistics for all configured interfaces in the first interval.

The name of the bulk statistics file that is transferred to the host when there is a collectorSequence attribute in the remote name is as follows:

fileName - z - mmddHHMM - s. sts

where:

fileName—Name of the file, which includes sysName, sysUpTime, depending on the attributes specified
-z—Receiver index value
mmddHHMM—Timestamp when the receiver is created in month/day/hour/minute format
-s—Actual sequence number

Interface Strings

Bulk statistics provides interface strings as described in Table 23.

Table 23: Interface Strings

Type of Interface	Common Description Format-Mode Disabled	Common Description Format-Mode Enabled
IP interfaces	IP	Ip
PPP interfaces	PPP	Ppp
DS0 interfaces	Ds0	Ds0
DS1 interfaces	SERIAL	Ds1
DS3 interfaces	SERIAL	Ds3
Frame Relay Major interfaces	FR	FrameRelayMajor
Ethernet interfaces	ENET	Ethernet
Sonet interfaces	SONET	Sonet
Sonet Path interfaces	SONET	SonetPath
ATM interfaces	ATM	Atm
ATM AAL5 interfaces	ATM	AtmAal5
ATM 1483 interfaces	ATM	Atm1483
Ft1 interfaces	SERIAL	Ft1
HDLC interfaces	HDLCIntf	HDLC
IpLoopback interfaces	Loopback	IpLoopback
IpVirtual interfaces	IpVirtual	IpVirtual
Frame Relay Sub interfaces	FR	FrameRelaySub
PppOE Major interfaces	PPPoE	PppoeMajor
PppOE Sub interfaces	PPPoE	PppoeSub
Bridged Ethernet	BRG-ET	BridgedEthernet
L2TP Tunnel	L2TP	L2tpTunnel
L2TP Session	L2TP	L2tpSession
PppLink interfaces	MLPPP	PppLink
HDLC interfaces	HDLCEncaps	Hdlc
L2TP Destinataion	L2TP	L2tpDestination
MPLS Major interfaces	MplsIfMajor	MplsMajor
MPLS Minor interfaces	MplsIfMinor	MplsMinor
Ppp Network interfaces	MLPPP	PppNetwork
Ethernet Sub interfaces	ENET	EthernetSub
MultiLink Frame Relay interfaces	MLFR	MultilinkFrameRelay
Ip Tunnel Interfaces	IP-TUNNEL	IpTunnel
Server Port Interfaces	ServerPort	ServerPort
Sonet VT interfaces	SONET	SonetVT
Vlan major interfaces	VLAN-MAJ	VlanMajor
Vlan sub interfaces	VLAN-SUB	VlanSub
Gtp interfaces	Gtp	Gtp
L2fTunnel interfaces	L2fTunnel	L2fTunnel
L2fSession interfaces	L2fSession	L2fSession
L2fDestination interfaces	L2fDestination	L2fDestination
IpSec Tunnel interfaces	IpSecTunnel	IpsecTunnel
Sg interfaces	SgInterface	SgInterface
MPLS L2 Shim interfaces	MplsL2Shim	MplsL2Shim
MPLS VC Sub interfaces	MplsL3Shim	MplsVcSub
LacGen interfaces	LacGen	LacGen
Bridge interfaces	BridgeIf	Bridge
IpSec Transport interfaces	IPSecTransportIf	IpsecTransport
IPv6 interfaces	IPv6If	Ipv6
IPv6 Tunnel interfaces	IPv6TunnelIf	Ipv6Tunnel
IPv6 loopback interfaces	IPv6LoopbackIf	Ipv6Loopback
OSI interfaces	Osi	Osi
LAG interfaces	Lag	Lag
Ip Tunnel MDT interfaces	IpTunnelMdt	IpTunnelMdt

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:

Add names to the FTP host table for the primary and secondary (optional) receivers.
See Copying and Redirecting Files in Managing the System , for information about adding names to the host table.
Specify the type of interface on which you want to collect statistics.
host1(config)#bulkstats interface-type ppp collector 2
Specify the parameters for the receivers.
host1(config)#bulkstats receiver 1 remote-name js:/ftptest/bulk%s%s.sts sysName sysUpTime
Assign the data collector.
host1(config)#bulkstats collector 2
Specify the method for data collection.
host1(config)#bulkstats collector 2 collect-mode auto
Assign the primary receiver.
host1(config)#bulkstats collector 2 primary-receiver 1
(Optional) Assign the secondary receiver.
host1(config)#bulkstats collector 2 secondary-receiver 5
(Optional) Specify the time for which the system transfers data.
host1(config)#bulkstats collector 2 interval 1000
(Optional) Set the maximum size of the bulk statistics file.
host1(config)#bulkstats collector 2 max-size 20480
(Optional) Add descriptive information to the bulk statistics file.
host1(config)#bulkstats collector 2 description customer xyz
(Optional) Set the encoding scheme of the ifDescr and ifName objects.
host1(config)#bulkstats interfaces description-format common
(Optional) Set the system to retrieve bulk statistics once only.
host1(config)#bulkstats collector 2 single-interval
(Optional) Configure bulk statistics traps.
host1(config)#bulkstats traps nearly-full
(Optional) Collect bulk statistics per virtual router.
host1(config)#bulkstats virtual-router-group collector 2 routerISP3
Note: The bulk statistics feature supports generating files on a per interface basis.

bulkstats collector

Use to assign the data collector.
Example
host1(config)#bulkstats collector 2
Use the no version to delete the collector.
See bulkstats collector.

bulkstats collector

Use to specify the way the collector retrieves bulk statistics.
Example
host1(config)#bulkstats collector 2 collect-mode auto
Use the no version to specify that either the user or the system will initiate transfers manually.
See bulkstats collector.

bulkstats collector

Use to add descriptive information to the bulk statistics file.
Example
host1(config)#bulkstats collector 2 description customer xyz
Use the no version to remove descriptive text from the bulk statistics file.
See bulkstats collector.

bulkstats collector

Use to specify the time interval in seconds for which the collector transfers data to the receivers.
Example
host1(config)#bulkstats collector 2 interval 1000
Use the no version to set this time to the default, 360 seconds (6 minutes).
See bulkstats collector.

bulkstats collector

Use to set the maximum size of the bulk statistics file for all collectors combined. Even when you configure more than one collector, the first maximum file size configured is the combined size of all collectors.
The maximum file size that you can configure is 20971520 bytes. However, if you do not configure a maximum size, then the maximum file size defaults to 5767168 bytes.
Although the CLI accepts the commands, you cannot unconfigure or modify the configuration of the maximum file size until the router is rebooted.
Example
host1(config)#bulkstats collector 2 max-size 20480
Use the no version to set the size of the bulk statistics file to the default, 5767168 bytes.
See bulkstats collector.

bulkstats collector

Use to assign the primary receiver to which the system transfers data.
The index for the receiver must match the index that you specified with the bulkstats receiver remote-name command.
Example
host1(config)#bulkstats collector 2 primary-receiver 7
Use the no version to clear the primary receiver and disable the collector.
See bulkstats collector.

bulkstats collector

Use to assign the secondary (that is, the backup) receiver to which the system transfers data.
The index for the receiver must match the index you specified with the bulkstats receiver remote-name command.
Example
host1(config)#bulkstats collector 2 secondary-receiver 5
Use the no version to clear the secondary receiver.
See bulkstats collector.

bulkstats collector

Use to set the system to retrieve bulk statistics once only, rather than periodically.
Example
host1(config)#bulkstats collector 2 single-interval
Use the no version to set the system to retrieve bulk statistics periodically, the default situation.
See bulkstats collector.

bulkstats interfaces description-format common

Use to set the encoding scheme of the ifDescr object that the bulk statistics application reports to the conventional industry method.
This command provides compatibility with software that uses the industry encoding scheme.
For more information, see Configuring Encoding Method .
Example
host1(config)#bulkstats interfaces description-format common
Use the no version to return to the proprietary method of encoding.
See bulkstats interfaces description-format common.

bulkstats interface-type

Use to configure the interface or subinterface type on which you want to collect statistics.
You can provide an interface specifier (location) to identify a specific interface on which you want to collect statistics.
If you define more than one collector, you must specify a unique collector index, in the range 1–65535.
The supported interface types are:
- atm—Collects statistics on ATM interfaces
- atm1483—Collects statistics on ATM 1483 interfaces
- ethernet—Collects statistics on Ethernet interfaces
- frame-relay—Collects statistics on Frame Relay interfaces
- frame-relay-sub—Collects statistics on Frame Relay subinterfaces
- hdlc—Collects statistics on Cisco HDLC interfaces
- ip—Collects statistics on IP interfaces
- mplsMajor—Collects statistics on MPLS major interfaces
- mplsMinor—Collects statistics on MPLS minor interfaces
- mplsL2shim—Collects statistics on MPLS shim interfaces
- ppp—Collects statistics on PPP
- vlan—Collects statistics on VLAN subinterfaces
  Note: You cannot collect statistics on the SRP Ethernet interface.
Example 1
host1(config)#bulkstats interface-type ppp 3/1 collector 2
Example 2
host1(config)#bulkstats interface-type vlan 2/3:1 collector 1
Example 3
host1(config)#bulkstats interface-type mplsMajor 2/3:1 collector 1
Use the no version to delete the interface type from bulk statistics collection. Deletion of a particular interface type takes effect at the next collection interval.
See bulkstats interface-type.

bulkstats receiver remote-name

Use to configure the parameters for receivers.
Bulk statistics transfers require the configuration of a remote FTP server.
The receivers must appear in the FTP host table. The name of the host must match the name you specify with this command. The hostname is relative to the virtual router’s context when you issue this command.
When specifying the remote filename for bulk statistics, you must precede the filename with the hostname followed by the :/ characters.
Example
host1(config)#bulkstats receiver 1 remote-name js:/ftptest/bulk%s%s.sts sysName sysUpTime
Note: The % variables in the remote name are replaced at runtime with the sysName and sysUpTime parameters to produce variable filenames on the remote host.
Use the no version to delete the receiver.
See bulkstats receiver remote-name.

bulkstats traps

Use to configure bulk statistics traps.
You must configure SNMP correctly and specify a valid trap source. Otherwise, the system will not send SNMP traps.
Example
host1(config)#bulkstats traps nearly-full
Use the no version to disable the trap.
See bulkstats traps.

bulkstats virtual-router-group

Use to collect interface statistics for each virtual router.
A collector can have a maximum of 64 virtual routers associated with it.
Routers are identified by their assigned name or router index.
Supported only on if-stats and igmp schemas.
Supported on all interface types supported by the bulk statistics application.
Collectors modified to use per virtual router collection or configured after a collector has started have a time delay until an active collector starts again.
Example
host1(config)#bulkstats virtual-router-group collector 2 routerISP3
Use the no version to prevent bulkstats from being reported for virtual router groups.
See bulkstats virtual-router-group.

Deleting All Bulkstats Configurations

Although individual bulkstats commands allow you to disable or delete a specific bulkstats parameter, the CLI also allows you to remove all bulkstats configurations from the router at one time.

no bulkstats

Use to remove all bulkstats configurations from the router at one time.
Example
host1(config)#no bulkstats
See no bulkstats.

Monitoring Collection Statistics

To view the parameters the router uses to collect statistics, use the following show bulkstats commands.

To include or exclude lines of output based on a text string that you specify, use the output filtering feature for show commands. For details, see Command-Line Interface.

show bulkstats

Use to display the bulk statistics data collection configuration.
Field descriptions
- AdminStatus—Administrative status of the bulk statistics application
- OperStatus—Operational status of the bulk statistics application, enabled or disabled
- Interface Description Setting—Method used to encode the ifDescr object: common, proprietary, industry-common
- File Format—End of the line format in bulkstats files, carriage return and line feed (CR+LF) or LF
- Current Time—Current system time used to compare with the collection stop/start time
- Intervals—Number of times the bulk statistics collector has cycled through a collection
- PrimaryXfers—Number of times the bulk statistics collector has attempted a data file transfer to a primary server
- PrimaryFails—Number of primary server transfer failures
- SecondaryXfers—Number of times the bulk statistics collector has attempted a data file transfer to a secondary server
- SecondaryFails—Number of secondary server transfer failures
- BulkStats Collector Information:
  - Index—Bulk statistics collector index number
  - CurrSize—Current size of the bulk statistics file in bytes
  - MaxSize—Maximum size configured for the bulk statistics file in bytes
  - Intrvl—Time interval between bulk collections in seconds
  - Mode—How often the collector is set up to collect statistics:
    - periodic—Collects statistics periodically
    - single-interval—Collects statistics once only
  - XferMode—Collect mode configured for the collector:
    - auto—Agent transfers file when interval expires
    - manual—Network management system or the user initiates transfers
    - onFull—Agent transfers file when it reaches the maximum size
  - State
    - inProg—Collector is properly configured and currently active
    - notInSvc—Collector has been decommissioned by a management client
    - notReady—Collector does not have enough configuration information to go active
    - error—Configuration or operational error
  - Index—Bulk statistics collector index number
  - Primary-Receiver—Index number of the primary receiver to which the system transfers data, if defined
  - Second-Receiver—Index of the secondary receiver to which the system transfers data
  - Last Transfer Failure—Last time that the collector attempted to retrieve statistics and was unsuccessful
  - Interval Start Time—Start of current interval of bulk collections. The collector began collecting bulk statistics at this time.
  - Interval Stop Time—End of current interval of bulk collections.
- Schema Information:
  - Index—Index number of the schema
  - Subtree—Type of bulk statistics schema configured on the collector: if-stack, if-stats, or system
  - CollectorIndex—Bulk statistics collector index number
  - Create-Delete Time Stats—State of final statistics collection (enabled or disabled)
  - Create-Delete Interface Type—Interface type associated with final statistics collection (ATM 1483, IP, PPP)
  - State
    - active—Schema is properly configured and currently active
    - notInSvc—Schema has been decommissioned by a management client
    - notReady—Schema does not have enough configuration information to go active
    - error—Configuration or operational error
  - Subtree List—Types of statistics the schema is configured to receive
- Interface Types:
  - Index—Index number of the interface type entry
  - Type—Interface type for which bulk statistics collection is configured
  - CollectorIndex—Index number of the collector to which the interface type applies
  - State
    - active—Interface type is properly configured and currently active
    - notInSvc—Interface type has been decommissioned by a management client
    - notReady—Interface type does not have enough configuration information to go active
    - error—Configuration or operational error
- Receiver Information:
  - Index—Index number of the receiver
  - RemoteFileName—Hostname, path, and filename of the remote FTP server
  - State
    - active—Receiver is properly configured and currently active
    - notInSvc—Receiver has been decommissioned by a management client
    - notReady—Receiver does not have enough configuration information to go active
    - error—Configuration or operational error
  - Status
    - Success
    - Copy source does not exist or is unreachable
    - Copy failed
    - File in use
- Virtual Router Groups:
  - Collector—Number that identifies the particular data collector, in the range 1–65535
  - Virtual-Routers—Set of virtual router names (up to 64 names)

Example

host1#show bulkstats

  AdminStatus:  enabled
  OperStatus:   enabled
  Interface Description Setting: industry-common
  File Format: CR+LF 
Current Time: TUE AUG 15 2002 15:54:20 UTC

  Intervals PrimaryXfers PrimaryFails SecondaryXfers SecondaryFails
  --------- ------------ ------------ -------------- --------------
  0         0            0            0              0

  BulkStats Collector Information:
  Index  CurrSize  MaxSize   Intrvl  Mode      XferMode  State
  -----  --------  --------  ------  --------- --------  -------
  1      490       3670016   600     periodic  manual    inProg
  2      0         3670016   360     periodic  manual    notReady

  Index  Primary-Receiver  Second-Receiver  Last Transfer Failure
  -----  ----------------  ---------------  --------------------
  1      1                 not defined
  2      not defined       not defined

  Index Interval Start Time          Interval Stop Time
  ----- ---------------------------- -------------------------
  1     TUE AUG 15 2000 15:52:33 UTC TUE AUG 15 2000 16:02:33 UTC
  2     Not started                  N/A

Schema Information:
  Index  Subtree
  -----  -------------------------------------------------
  1      ifStats

  Index  CollectorIndex  State
  -----  --------------  --------
  1      1               active

  Index  Create-Delete Time Stats  Create-Delete Interface Types
  -----  ------------------------  -----------------------------
  1      enabled                   IP

  Index  Subtree List
  -----  -------------------------------------------------------------
  1      all

  Interface Types:
  Index         Type             CollectorIndex  State
  -----  ----------------------  --------------  --------
  1      Ppp                     1               active
  6      Ethernet                1               active
  11     Atm1483                 1               active

  Receiver Information:
  Index  RemoteFileName
  -----  -------------------------------------------------------
  1      host:/upload/bulkStas.sts

  Index  State     Status
  -----  --------  ---------------------------------------------
  1      notReady  Copy source does not exist or is unreachable

Collector  Virtual-Routers
---------  ---------------
33             serviceProviderABC
655             default

See show bulkstats.

show bulkstats collector description

Use to display information about the collector’s file description.
Field descriptions
- Index—Index number of the bulk statistics collector
- FileDescription—Descriptive information added to the bulk statistics file with the bulkstats collector description command

Example

host1#show bulkstats collector description
  Index  FileDescription
  -----  -----------------------
  1      Bulk SNMP Statistics Collection

See show bulkstats collector description.

show bulkstats collector interval

Use to display information about the collector transfer interval configuration.
Field descriptions
- Index—Index number of the bulk statistics collector
- Interval—Amount of time, in seconds, that the collector transfers data to the receiver

Example

host1#show bulkstats collector interval
Index  Interval
-----  --------
1      360

See show bulkstats collector interval.

show bulkstats collector max-size

Use to display information about the bulk statistics maximum file size configuration.
Field descriptions
- Index—Index number of the bulk statistics collector
- MaxSize—Maximum size of the bulk statistics file in bytes

Example

host1#show bulkstats collector max-size
Index  MaxSize
-----  ------------
1      2097152

See show bulkstats collector max-size.

show bulkstats collector transfer-mode

Use to display information about the bulk statistics transfer mode configuration.
Field descriptions
- Index—Index number of the bulk statistics collector
- Transfer-Mode:
  - auto-xfer—Server automatically transfers the bulk statistics files to a remote FTP server
  - manual-xfer—Server expects the user to transfer bulk statistics files
  - on-file-full—Server transfers the bulk statistics file when the file reaches its maximum size
- Primary-Receiver—Receives the bulk statistics sent by the collector
- Secondary-Receiver—Serves as a backup to the primary receiver

Example

host1#show bulkstats collector transfer-mode
Index  Transfer-Mode  Primary-Receiver  Secondary-Receiver
-----  -------------  ----------------  ------------------
1      auto-xfer      1                 2

See show bulkstats collector transfer-mode.

show bulkstats interface-type

Use to display information about the bulk statistics interface types configuration.
Field descriptions
- Interface Types:
- Index—Index number of the interface type entry
- Type—Interface type for which bulk statistics collection is configured
- CollectorIndex—Index of the collector to which the interface type applies
- State
  - active—Interface type is properly configured and currently active
  - notInSvc—Interface type has been decommissioned by a management client
  - notReady—Interface type does not have enough configuration information to go active
  - error—Configuration/operational error

Example

host1#show bulkstats interface-type

Interface Types:
  Index         Type             Collector  State
  -----  ----------------------  ---------  --------
  1      ppp                     1          active

See show bulkstats interface-type.

show bulkstats receiver

Use to display information about the remote file configuration of the bulk statistics receiver.
Field descriptions
- Index—Index number of the receiver
- RemoteFileName—Hostname, path, and filename of the remote FTP server
- Index—Index number of the receiver
- State
  - active—Receiver is properly configured and currently active
  - notInSvc—Receiver has been decommissioned by a management client
  - notReady—Receiver does not have enough configuration information to go active
  - error—Configuration/operational error
- Status
  - Success
  - Copy source does not exist or is unreachable
  - Copy failed
  - File in use

Example

host1#show bulkstats receiver

  Index  RemoteFileName
  -----  ----------------------------------------------
  1      f:/upload/bulkStas.sts

  Index  State     Status
  -----  --------  ---------------------------------------------
  1      notReady  Copy source does not exist or is unreachable

See show bulkstats receiver.

show bulkstats statistics

Use to display bulk statistics counters.
Field descriptions
- AdminStatus—Administrative status of the bulk statistics application
- OperStatus—Operational status of the bulk statistics application
- HdwDetects—Number of times the bulk statistics application detected a line module bulkstat collector’s presence
- HdwCollectorCreates—Number of line module collectors created
- CollectorCreateReqs—Number of times the bulk statistics application requested the creation of a line module collector
- CollectorStopReqs—Number of times the bulk statistics application requested the line module collectors to stop
- CollectorDeleteReqs—Number of times the bulk statistics application requested the deletion of a line module collector
- CollectorStarts—Number of times the bulk statistics collector has started
- CollectorIncompleteCfgs—Number of times the bulk statistics collector attempted to start a collector, but failed because the collector’s configuration was incomplete
- CollectorStopFailures—Number of times the bulk statistics collector failed during a collector stop request
- DriverErrors—Number of bulk statistics driver errors
- FileSizeFulls—Number of times the bulk statistics application ran out of storage space
- CollectorFileNearlyFullTraps—Number of nearly full events posted to the SNMP agent on this router
- CollectorFileFullTraps—Number of file full events posted to the SNMP agent on this router
- Intervals—Number of times the bulk statistics collector has cycled through a collection
- PrimaryXfers—Number of times the bulk statistics collector has attempted a data file transfer to a primary server
- PrimaryFails—Number of primary server transfer failures
- SecondaryXfers—Number of times the bulk statistics collector has attempted a data file transfer to a secondary server
- SecondaryFails—Number of secondary server transfer failures
- BulkStats Collector Statistics:
  - Index—Bulk statistics collector index
  - CurrSize—Current size of the bulk statistics storage file in bytes
  - CreateErrs—Number of bulk statistics collector create errors
  - Last Transfer Failure—Last time that the collector attempted to retrieve statistics and was unsuccessful
  - Interval Start Time—Start of current interval or bulk collections. The collector began collecting bulk statistics at this time.
  - Interval Stop Time—End of current interval of bulk collections
- Dynamic Interface Collector statistics:
  - Collector Index—Bulk statistics collector index
  - Slot#—Slot number from which the statistics were obtained
  - Received—Number of records for dynamic interfaces that were reported by the specified interface
  - Transferred—Number of record for dynamic interface that were written to the bulk statistics (.sts) file.
  - Dropped—Number of records for dynamic interfaces that were dropped (that is, not written to the bulk statistics [.sts] file)

Example

host1#show bulkstats statistics

AdminStatus:                  enabled
OperStatus:                   enabled
HdwDetects:                   4
HdwCollectorCreates:          8
CollectorCreateReqs:          2
CollectorStopReqs:            0
CollectorDeleteReqs:          0
CollectorStarts:              25
CollectorIncompleteCfgs:      3
CollectorStopFailures:        0
DriverErrors:                 0
FileSizeFulls:                0
CollectorFileNearlyFullTraps: 0
CollectorFileFullTraps:       0

  Intervals PrimaryXfers PrimaryFails SecondaryXfers  SecondaryFails
  --------- ------------ ------------ --------------  --------------
  24         18            5             0               0

  BulkStats Collector Statistics:
  Index  CurrSize  CreateErrs  Last Transfer Failure
  -----  --------  ----------  ----------------------------
  1      331       0           MON JAN 24 2001 17:21:33 UTC
  2      0         0

  Index Interval Start Time          Interval Stop Time
  ----- ---------------------------- -------------------------
  1     MON JAN 24 2001 19:09:33 UTC MON JAN 24 2001 19:15:33 UTC
  2     Not started                  N/A

Dynamic Interface Collector statistics:
  CollectorIndex  Slot#  Received    Transferred  Dropped
  --------------  -----  ----------  -----------  ----------
  1               1      0           0            0

See show bulkstats statistics.

show bulkstats traps

Use to display information about the bulk statistics traps configured to collect statistics.
Field descriptions
- Trap Type
  - nearly-full—Trap will be posted to the SNMP entity on this system when the threshold is reached
  - file-full—Trap will be posted to the SNMP entity on this system when the trap reaches 100%
- State—Configuration setting: enabled, disabled
- Threshold—Nearly full trap will be posted to the SNMP entity on this system when this percentage is reached
- Traps Sent—Number of times this event was posted to the SNMP entity on this system

Example

host1#show bulkstats traps
Trap Type    State   Threshold    Traps Sent
-----------  -------  ----------  ----------
file-full    enabled  N/A         0
nearly-full  enabled  5           0

See show bulkstats traps.

show bulkstats virtual-routers

Use to display information about the bulk virtual router group configuration.
Field descriptions
- Collector—Number that identifies the particular data collector, in the range 1–65535
- Virtual-Routers—Set of virtual router names (up to 64 names)

Example

host1#show bulkstats virtual-routers

Collector  Virtual-Routers
---------  ---------------
33             serviceProviderABC
655             default

See show bulkstats virtual-routers.

Configuring Schemas

You can also set a management schema for bulk statistics. A schema is a group of attributes or counters that provide an efficient way to retrieve specific types of information about the router. The bulk statistics application supports five schema configurations: igmp, if-stack, if-stats, policy, and system.

Note: There are no explicit schema objects for the if-stack and system schemas.

Table 24 shows the type of data each schema retrieves.

Table 24: Data Retrieved According to Schema

Schema	Retrieves
igmp	Statistics associated with various IGMP components.
if-stack	The interface and interface column configuration. It is a complete retrieval of the ifStackTable, and using it can dramatically reduce the time to discover the configured interfaces and their stacking relationship on a router.
if-stats	Usage data on sets of interface types. The interface usage data is the ifTable/ifXTable counters. Note that the ifXTable supports 64-bit counters and the data written into the bulk statistics file supports the 64-bit counters.
policy	Statistics associated with a specified policy, a policy type, or traffic tagged by a policy with a color tag.
system	Global system and per-module statistics and information. The global system statistics retrieved are the sysUpTime and nvsUtilPct. The per-module statistics and information retrieved include the intPhysicalDesc, the cpuUtilPct, and the memUtilPct.

igmp Objects

Table 25 presents igmp objects you can configure using the bulkstats schema subtree command.

Table 25: Schema igmp Objects

Object	Definition
all	Configure IGMP schema for all attributes
dest-address	Configure IGMP schema for destination address
igmp-cmd	Configure IGMP schema for IGMP command
lower-interface	Configure IGMP schema for lower interface
multicast-group	Configure IGMP schema for multicast group
router-index	Configure IGMP schema for router index
source-address	Configure IGMP schema for source address
time-stamp	Configure IGMP schema for time stamp

if-stats Objects

Table 26 presents if-stats objects you can configure using the bulkstats schema subtree command.

Table 26: Schema ifStats Objects

Object	Definition
all	Configure IfStats schema for all stats
correlator	Configure IfStats schema for correlator
in-bcast-pkts	Configure IfStats schema for in-bcast-pkts
in-discards	Configure IfStats schema for in-discards
in-errors	Configure IfStats schema for in-errors
in-mcast-octets	Configure IfStats schema for in-mcast-octets
in-mcast-pkts	Configure IfStats schema for in-mcast-pkts
in-octets	Configure IfStats schema for in-octets
in-policed-octets	Configure IfStats schema for in-policed-octets
in-policed-pkts	Configure IfStats schema for in-policed-pkts
in-spoofed-pkts	Configure IfStats schema for in-spoofed-pkts
in-ucast-pkts	Configure IfStats schema for in-ucast-pkts
in-unknown-protos	Configure IfStats schema for in-unknown-protos
lower-interface	Configure IfStats schema for lower-interface
out-bcast-pkts	Configure IfStats schema for out-bcast-pkts
out-discards	Configure IfStats schema for out-discards
out-errors	Configure IfStats schema for out-errors
out-mcast-octets	Configure IfStats schema for out-mcast-octets
out-mcast-pkts	Configure IfStats schema for out-mcast-pkts
out-octets	Configure IfStats schema for out-octets
out-policed-octets	Configure IfStats schema for out-policed-octets
out-policed-pkts	Configure IfStats schema for out-policed-pkts
out-sched-octets	Configure IfStats schema for out-sched-octets
out-sched-pkts	Configure IfStats schema for out-sched-pkts
out-ucast-pkts	Configure IfStats schema for out-ucast-pkts
time-offset	Configure IfStats schema for time-offset

All the schema if-stats objects in Table 26 apply to both layer 2 and layer 3 interfaces, except usdAcctngSpoofedPkts, which is specific to layer 3.

Defining all interface types before you map a collector to the if-stats schema ensures that you display statistics for all configured interfaces in the first interval.

You can get more accurate rate statistics by using the time-offset parameter. To use this parameter you must navigate to the if-stats subtreelist. The time-offset parameter is included in each bulk statistics interface record and is the offset from the master interval at which the record was collected.

policy Objects

Table 27 presents policy objects you can configure using the bulkstats schema subtree command.

Table 27: Schema Policy Objects

Object	Definition
all	Configure policy schema for all statistics
green-bytes	Configure policy schema for green bytes
green-packets	Configure policy schema for green packets
red-bytes	Configure policy schema for red bytes
red-packets	Configure policy schema for red packets
upper-green-bytes	Configure policy schema for upper green bytes
upper-green-packets	Configure policy schema for upper green packets
upper-red-bytes	Configure policy schema for upper red bytes
upper-red-packets	Configure policy schema for upper red packets
upper-yellow-bytes	Configure policy schema for upper yellow bytes
upper-yellow-packets	Configure policy schema for upper yellow packets
yellow-bytes	Configure policy schema for yellow bytes
yellow-packets	Configure policy schema for yellow packets

bulkstats schema

Use to create the schema for collecting bulk statistics.
Example
host1(config)#bulkstats schema 4

Use the no version to delete the specified schema.

Note: If you create a collector but there is no schema for that collector, the collector will not be active, and a schema will be created automatically for that collector to collect if-stats for all subtree attributes.

See bulkstats schema.

bulkstats schema subtree

Use to set the schema for collecting data. Specify one of the following keywords:
- if-stack—Retrieves the interface and interface column configuration.
- if-stats—Retrieves interface usage data on sets of interface types; using the subtreelist keyword along with the if-stats keyword lets you specify specific counters and lets you set the time-offset parameter; using the if-create-delete-time-stats keyword along with the if-stats keyword retrieves interface final statistics (interface statistics that may be lost during higher create or delete frequency) on a per-interface basis.
- igmp—Retrieves IGMP usage data; using the subtreelist keyword along with the igmplist keyword lets you obtain statistics for one or more specific IGMP lists.
- policy—Retrieves policy usage data.
- system—Retrieves global system and per-module statistics and information.
Example 1
host1(config)#bulkstats schema 1 subtree if-stats subtreelist lower-interface

Example 2

host1(config)#bulkstats schema 5 subtree if-stats if-create-delete-time-stats interfaceType ?

  atm1483     Configure bulkstats for ATM 1483 sub-interfaces
  ip          Configure bulkstats for IP interfaces
  mplsL2Shim  Configure bulkstats for MPLS shim Interfaces
  mplsMajor   Configure bulkstats for MPLS major Interfaces
  mplsMinor   Configure bulkstats for MPLS minor Interfaces
  ppp         Configure bulkstats for PPP interfaces
  vlan        Configure bulkstats for VLAN Sub-Interfaces

Use to collect statistics on a specified policy, a policy type, or based on color-coded tags applied by a policy. Specify one of the following keywords:
- policy-name—Collects statistics for a specified policy
- policy-type—Collects data on input policies, local input policies, output policies, or secondary output policies
- policy-subtreelist—Collects statistics based on color-coded tags applied by a policy
You create policies using the policy-list command. See JUNOSe Policy Management Configuration Guide .
Example
host1(config)#bulkstats schema 4 subtree policy policy-name XMYpolicy
Use the no version to delete the specified schema.
See bulkstats schema subtree.

Mapping Bulkstats Output to MIB Flies and CLI Configurations

Table 28 shows the mapping between the bulkstats output and the CLI and MIBs.

Table 28: Mapping Bulkstats Output to MIB Flies and CLI Configurations

Bulkstats Output Column Name	MIB File	MIB Object Name	CLI Configuration	Description
			all	Configure IfStats schema for all stats
ifDescr	RFC1213	ifDescr	–	A textual string containing information about the interface. This string should include the name of the manufacturer, the product name and the version of the interface hardware/software
ifType	RFC1213	ifType	-	The type of interface. Additional values for ifType are assigned by the Internet Assigned Numbers Authority (IANA), through updating the syntax of the IANAifType textual convention
usdIfType	juniIf	juniIfType	-	Identifies the type of this interface
ifIndex	RFC1213	ifIndex	-	A unique value, greater than zero, for each interface. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re- initialization
IfStatsReportState	-	-	-	Report State: IfStatsReportInterim = Interim Accounting data
ifHCInOctets	RFC2863	ifHCInOctets	in-octets	The total number of octets received on the interface, including framing characters. This object is a 64-bit version of ifInOctets Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime
ifHCInUcastPkts	RFC2863	ifHCInUcastPkts	in-ucast-pkts	The number of packets, delivered by this sub-layer to a higher (sub-)layer, which were not addressed to a multicast or broadcast address at this sub-layer. This object is a 64-bit version of ifInUcastPkts Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime
ifInDiscards	RFC1213	ifInDiscards	in-discards	The number of inbound packets which were chosen to be discarded even though no errors had been detected to prevent their being deliverable to a higher-layer protocol. One possible reason for discarding such a packet could be to free up buffer space Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime
ifInErrors	RFC1213	ifInErrors	in-errors	For packet-oriented interfaces, the number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol. For character- oriented or fixed-length interfaces, the number of inbound transmission units that contained errors preventing them from being deliverable to a higher-layer protocol Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime
ifInUnknownProtos	RFC1213	ifInUnknownProtos	in-unknown-protos	For packet-oriented interfaces, the number of packets received via the interface which were discarded because of an unknown or unsupported protocol. For character-oriented or fixed-length interfaces that support protocol multiplexing the number of transmission units received via the interface which were discarded because of an unknown or unsupported protocol. For any interface that does not support protocol multiplexing, this counter will always be 0 Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime
ifHCOutOctets	RFC2863	ifHCOutOctets	out-octets	The total number of octets transmitted out of the interface, including framing characters. This object is a 64-bit version of ifOutOctets Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime
ifHCOutUcastPkts	RFC2863	ifHCOutUcastPkts	out-ucast-pkts	The total number of packets that higher-level protocols requested be transmitted, and which were not addressed to a multicast or broadcast address at this sub-layer, including those that were discarded or not sent. This object is a 64-bit version of ifOutUcastPkts Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime
ifOutDiscards	RFC1213	ifOutDiscards	out-discards	The number of outbound packets which were chosen to be discarded even though no errors had been detected to prevent their being transmitted. One possible reason for discarding such a packet could be to free up buffer space Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of jjifCounterDiscontinuityTime
ifOutErrors	RFC1213	ifOutErrors	out-errors	For packet-oriented interfaces, the number of outbound packets that could not be transmitted because of errors. For character-oriented or fixed-length interfaces, the number of outbound transmission units that could not be transmitted because of errors Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime
ifCorrelato	juniAcctng	juniAcctngIfCorrelator	correlator	Customer correlation: • FR = DLCI • ATM = VPI, VCI • IP = RouterName • Everything else = not used
ifInPolicedOctets	juniAcctng	juniAcctngIfInPolicedOctets	in-policied-octets	Octets dropped due to ingress policy; support 64-bit counters
ifInPolicedPkt	juniAcctng	juniAcctngIfInPolicedPkts	in-policied-octets	Packets dropped due to ingress policy
ifInSpoofedPkts	juniAcctng	juniAcctngIfInSpoofedPkts	in-spoofed-pkts	Packets dropped due to invalid source address
ifOutPolicedOctets	juniAcctng	juniAcctngIfOutPolicedOctets	out-policied-octets	Octets dropped due to egress policy; support 64-bit counters
ifOutPolicedPkts	juniAcctng	juniAcctngIfOutPolicedPkts	out-policied-pkts	Packets dropped due to ingress policy
ifOutSchedOctets	juniAcctng	juniIpIfStatsOutSchedDropOctets	out-sched-octets	Scheduler octets dropped
ifOutSchedPkts	juniAcctng	juniIpIfStatsOutSchedDropPackets	out-sched-pkts	Scheduler packets dropped
ifLowerInterface	juniAcctng	juniAcctngIfLowerInterface	lower-interface	The ifIndex of the lower interface
ifTimeOffse	juniAcctng	juniAcctngIfTimeOffset	time-offset	-
ifHCInMulticastPkts	RFC2863	ifHCInMulticastPkts	in-mcast-pkts	The number of packets, delivered by this sub-layer to a higher (sub-)layer, which were addressed to a multicast address at this sub-layer. For a MAC layer protocol, this includes both Group and Functional addresses. This object is a 64-bit version of ifInMulticastPkts Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime
ifHCInBroadcastPkts	RFC2863	ifHCInBroadcastPkts	in-bcast-pkts	The number of packets, delivered by this sub-layer to a higher (sub-)layer, which were addressed to a broadcast address at this sub-layer. This object is a 64-bit version of ifInBroadcastPkts Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime
ifHCOutMulticastPkts	RFC2863	ifHCOutMulticastPkts	out-mcast-pkts	The total number of packets that higher-level protocols requested be transmitted, and which were addressed to a multicast address at this sub-layer, including those that were discarded or not sent. For a MAC layer protocol, this includes both Group and Functional addresses. This object is a 64-bit version of ifOutMulticastPkts Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime
ifHCOutBroadcastPkts	RFC2863	ifHCOutBroadcastPkts	out-bcast-pkts	The total number of packets that higher-level protocols requested be transmitted, and which were addressed to a broadcast address at this sub-layer, including those that were discarded or not sent. This object is a 64-bit version of ifOutBroadcastPkts Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime
ifHCInMulticastOctets	-	-	in-mcast-octets	Multicast octets received
ifHCOutMulticastOctets	-	-	out-mcast-octets	Multicast octets sent

Monitoring Schema Statistics

You are able to display your configuration and monitor the data generated by schemas.

show bulkstats schema

Use to display data on the bulk statistics schema.
Field descriptions
- Schema Information:
- Index—Index number of the schema
- Subtree—Type of bulk statistics schema configured on the collector: igmp, if-stack, if-stats, policy, or system
- CollectorIndex—Bulk statistics collector index (same as the SNMP table index)
- State
  - active—Schema is properly configured and currently active
  - notInService—Schema has been decommissioned by a management client
  - notReady—Schema does not have enough configuration information to go active
  - error—Configuration/operational error
- Subtree List—Types of statistics the schema is configured to receive

Example 1

host1#show bulkstats schema

  Schema Information:
  Index  Subtree            CollectorIndex  State
  -----  -----------------  --------------  --------
  1      ifStack            1               active
  2      system             2               active

  Index  Subtree List
  -----  -------------------------------------------------
  1      N/A
  2      N/A

Example 2

host1#show bulkstats schema

  Schema Information:
  Index  Subtree            CollectorIndex  State
  -----  -----------------  --------------  --------
  1      ifStats            1               active
  2      system             2               active

  Index  Subtree List
  -----  --------------------------------------------------
  1      ifOutErrors; ifLowerInterface; ifTimeOffset
  2      N/A

See show bulkstats schema.

Configuring Interface Numbering Mode

E Series routers support the RFC 1213 interface numbering mode on bulkstats. This mode is contrasted with the default interface numbering mode.

The RFC 1213 numbering mode is based on a 32-bit contiguous integer value starting from 1 and ranging to ifNumber. This mode differs from the default interface numbering mode, which encodes a type field in the upper 8 bits of a 32-bit integer. The use of the upper 8 bits creates large gaps in the ifIndex numbering scheme.

There is no re-use of ifIndex values in RFC 1213 mode, whereas in the default interface numbering mode, ifIndex values can be re-used. In the default interface numbering mode, re-use of ifIndex values across reboots is permitted and is basically known as ifIndex re-numbering.

In RFC 1213 mode, however, the interface numbers are not re-used during a single initialization of the device and renumbering of ifIndexes occurs after a system reboot. In the default interface numbering mode, ifIndexes are persistent across system reboots and can be reused without resetting the value of sysUpTime.

In RFC 1213 mode, two parameters control the size of the ifIndex range and the total number of interfaces in the standard interface tables—maxIfIndex and maxIfNumber. There is no such control in the default interface numbering mode.

In RFC 1213 mode, interface creations should not result in gaps in the ifIndex range. A gap that results from the deletion of an interface is acceptable because it is handled by older network management applications. The gaps are eliminated after the router is rebooted. However, in the default interface numbering mode, large gaps occur from the creation of interfaces due to the use of the upper 8 bits of the ifIndex for interface type encoding. Gaps are not eliminated after a system reboot.

In RFC 1213 mode, small gaps can occur in the creation of IP interfaces when virtual routers are used. These gaps are minimized but not eliminated when the router is rebooted.

Rather than seeing an ifIndex value of 1 and 10066329, for example, a management client would see ifIndex values of 1 and 2.

bulkstats interfaces rfc1213

Use to enable the RFC 1213 interface numbering mode on bulkstats.
Example
host1(config)#bulkstats interfaces rfc 1213
Use the no version to disable the RFC 1213 interface numbering mode on bulkstats.
See bulkstats interfaces rfc1213.