hit counter script

Configuring Bulk Statistics Transfer Options - Cisco NCS 5000 Series Manual

System management configuration guide for cisco ncs 5000 series routers
Hide thumbs Also See for NCS 5000 Series:
Table of Contents

Advertisement

Configuring Periodic MIB Data Collection and Transfer
Command or Action
• instance wild {interface interface-id [sub-if] |
oid oid}
• instance range start oid end oid
• instance repetition oid max repeat-number
Example:
RP/0/RP0/CPU0:router(config-bulk-sc)# instance
wild oid 1
or
RP/0/RP0/CPU0:router(config-bulk-sc)# instance
exact interface TenGigE 0/1.25
or
RP/0/RP0/CPU0:router(config-bulk-sc)# instance
range start 1 end 2
or
RP/0/RP0/CPU0:router(config-bulk-sc)# instance
repetition 1 max 4
Step 5
poll-interval minutes
Example:
RP/0/RP0/CPU0:router(config-bulk-sc)#
poll-interval 10
Step 6
commit

Configuring Bulk Statistics Transfer Options

The final step in configuring periodic MIB data collection and transfer is to configure the transfer options.
The collected MIB data are kept in a local file-like entity called a VFile (virtual file, referred to as a bulk
statistics file in this document). This file can be transferred to a remote network management station at intervals
you specify.
Before You Begin
The bulk statistics object lists and bulk statistics schemas must be defined before configuring the bulk statistics
transfer options.
Note
Sets how often data should be collected from the object instances
specified in this schema, in minutes. The default is once every 5
minutes. The valid range is from 1 to 20000.
System Management Configuration Guide for Cisco NCS 5000 Series Routers, IOS XR Release 6.2.x
Configuring Bulk Statistics Transfer Options
Purpose
• The instance wild command indicates that all subindices of
the specified OID belong to this schema. The wild keyword
allows you to specify a partial, "wild carded" instance.
• The instance range command indicates a range of instances
on which to collect data.
• The instance repetition command indicates data collection
to repeat for a certain number of instances of a MIB object.
Only one instance command can be configured per
schema. If multiple instance commands are executed,
the earlier ones are overwritten by new commands.
71

Advertisement

Table of Contents
loading

Table of Contents