 Feedback
|
Table Of Contents
Periodic MIB Data Collection and Transfer Mechanism
Prerequisites for Periodic MIB Data Collection and Transfer Mechanism
Restrictions for Periodic MIB Data Collection and Transfer Mechanism
Information About Periodic MIB Data Collection and Transfer Mechanism
Bulk Statistics Transfer Options
Benefits of the Periodic MIB Data Collection and Transfer Feature
How to Configure Periodic MIB Data Collection and Transfer Mechanism
Configuring a Bulk Statistics Object List
Configuring a Bulk Statistics Schema
Configuring a Bulk Statistics Transfer Options
Enabling Monitoring for Bulk Statistics Collection
Monitoring and Troubleshooting the Periodic MIB Data Collection and Transfer Mechanism
Configuration Examples for Periodic MIB Data Collection and Transfer Mechanism
Configuring Periodic MIB Data Collection and Transfer Mechanism: Example
Schema Definition Configuration
Transfer Parameter Configuration
show snmp mib bulkstat transfer
snmp-server enable traps bulkstat
Appendix A: Object Names Supported for the add Command
Periodic MIB Data Collection and Transfer Mechanism
First Published: January 20, 2003Last Updated: June 29, 2007This feature provides the ability to periodically transfer selected MIB data from Cisco IOS-based devices to specified Network Management Stations (NMS). Using the CLI, data from multiple MIBs can be grouped into lists, and a polling interval (frequency of data collection) can be configured. All the MIB objects in a list are periodically polled using this specified interval. The collected data from the lists can then be transferred to a specified NMS at a user-specified transfer interval (frequency of data transfer) using TFTP, RCP, or FTP.
History for Periodic MIB Data Collection and Transfer Mechanism
Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Prerequisites for Periodic MIB Data Collection and Transfer Mechanism
•
•
•
•
•
Prerequisites for Periodic MIB Data Collection and Transfer Mechanism
To use this feature, you should be familiar with the Simple Network Management Protocol (SNMP) model of management information. You should also know what MIB information you want to monitor on your network devices, and the OIDs or object names for the MIB objects to be monitored.
Restrictions for Periodic MIB Data Collection and Transfer Mechanism
Cisco Data Collection MIB configuration using SNMP is not currently implemented.
For specific restrictions, see the tasks in the "How to Configure Periodic MIB Data Collection and Transfer Mechanism" section.
Information About Periodic MIB Data Collection and Transfer Mechanism
To configure the Periodic MIB Data Collection and Transfer Mechanism, you must understand the following concepts:
•
Note
SNMP Objects and Instances
A type (or class) of SNMP management information is called an object. A specific instance from a type of management information is called an object instance (or SNMP variable). To configure a bulk statistics collection, you must specify the object types to be monitored using a bulk statistics object list and the specific instances of those objects to be collected using a bulk statistics schema.
MIBs, MIB tables, MIB objects, and object indices can all be specified using a series of numbers called an object identifier (OID). OIDs are used in configuring a bulk statistics collection in both the bulk statistics object lists (for general objects) and in the bulk statistics schemas (for specific object instances).
Bulk Statistics Object Lists
To group the MIB objects to be polled, you will need to create one or more object lists. A bulk statistics object list is a user-specified set of MIB objects that share the same MIB index. Object lists are identified using a name that you specify. Named bulk statistics object lists allow the same configuration to be reused in different bulk statistics schemas.
All the objects in an object list must share the same MIB index. However, the objects do not need to be in the same MIB and do not need to belong to the same MIB table. For example, it is possible to group ifInOctets and an Ethernet MIB object in the same schema, because the containing tables for both objects are indexed by the ifIndex.
Bulk Statistics Schemas
Data selection for the Periodic MIB Data Collection and Transfer Mechanism requires the definition of a schema with the following information:
•
•
•
A bulk statistics schema is also identified using a name that you specify. This name is used when configuring the transfer options.
Bulk Statistics Transfer Options
After configuring the data to be collected, a single virtual file (VFile or "bulk statistics file") with all collected data is created. This file can be transferred to a network management station (NMS) using FTP, RCP, or TFTP. You can specify how often this file should be transferred. The default transfer interval is once every 30 minutes. You can also configure a secondary destination for the file to be used if, for whatever reason, the file cannot be transferred to the primary network management station.
The value of the transfer interval is also the collection period (collection interval) for the local bulk statistics file. After the collection period ends, the bulk statistics file is frozen, and a new local bulk statistics file is created for storing data. The frozen bulk statistics file is then transferred to the specified destination.
By default, the local bulk statistics file is deleted after successful transfer to an NMS. However, you can configure the routing device to keep the bulk statistics file in memory for a specified amount of time.
An SNMP notification (trap) can be sent to the NMS if a transfer to the primary or secondary NMS is not successful. Additionally, a syslog message will be logged on the local device if transfers are unsuccessful.
Benefits of the Periodic MIB Data Collection and Transfer Feature
The Periodic MIB Data Collection and Transfer Mechanism (Bulk Statistics feature) allows many of the same functions as the Bulk File MIB (CISCO-BULK-FILE-MIB.my), but offers some key advantages.
The main advantage is that this feature can be configured through the CLI and does not require an external monitoring application.
The Periodic MIB Data Collection and Transfer Mechanism is mainly targeted for medium to high-end platforms that have sufficient local storage (volatile or permanent) to store bulk statistics files. Locally storing bulk statistics files helps minimize loss of data during temporary network outages.
This feature also has more powerful data selection features than the Bulkfile MIB; it allows grouping of MIB objects from different tables into data groups (object lists). It also incorporates a more flexible instance selection mechanism, where the application is not restricted to fetching an entire MIB table.
How to Configure Periodic MIB Data Collection and Transfer Mechanism
•
•
•
•
•
Configuring a Bulk Statistics Object List
The first step in configuring the Periodic MIB Data Collection and Transfer Mechanism is to configure one or more object lists.
Restrictions
All the objects in a bulk statistics object list have to be indexed by the same MIB index. However, the objects in the object list do not need to belong to the same MIB or MIB table.
When specifying an object name instead of an OID (using the add command), only object names from the Interfaces MIB (IF-MIB.my), Cisco Committed Access Rate MIB (CISCO-CAR-MIB.my) and the MPLS Traffic Engineering MIB (MPLS-TE-MIB.my) may be used.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Configuring a Bulk Statistics Schema
The next step in configuring Periodic MIB Data Collection and Transfer is to configure one or more schemas.
Prerequisites
The bulk statistics object list to be used in the schema must be defined.
Restrictions
Only one object list can be associated with a schema at a time.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Configuring a Bulk Statistics Transfer Options
The final step in configuring the Periodic MIB Data Collection and Transfer Mechanism 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 (NMS) at intervals you specify.
Prerequisites
The bulk statistics object lists and bulk statistics schemas should be defined before configuring the bulk statistics transfer options.
Restrictions
Transfers can only be performed using schemaASCII (cdcSchemaASCII) format. SchemaASCII is an ASCII format that contains parser-friendly hints for parsing data values.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
DETAILED STEPS
Troubleshooting Tips
If the maximum buffer size for a bulk statistics file is reached before the transfer interval time expires, the transfer operation will still be initiated, and bulk statistics data will be collected into a new file in the system buffer. To correct this behavior, you can decrease the polling frequency, or increase the size of the bulk statistics buffer. If retain 0 is configured, no retries will be attempted. This is because the interval between retries is the retain value divided by the retry value. For example, if retain 10 and retry 2 are configured, retries will be attempted once every 5 minutes. Therefore, if you configure the retry command, you should also configure an appropriate value for the retain command.
Enabling Monitoring for Bulk Statistics Collection
Optionally, you can enable SNMP notifications to be sent, which provide information on the transfer status of the Periodic MIB Data Collection and Transfer Mechanism (Bulk Statistics feature).
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Monitoring and Troubleshooting the Periodic MIB Data Collection and Transfer Mechanism
The show command for this feature displays the status of the bulk statistics processes. The debug command enables the standard set of debugging messages for technical support purposes.
SUMMARY STEPS
1.
2.
DETAILED STEPS
Configuration Examples for Periodic MIB Data Collection and Transfer Mechanism
This section provides the following configuration example:
•
Configuring Periodic MIB Data Collection and Transfer Mechanism: Example
This section provides a complete example of configuring the Periodic MIB Data Collection and Transfer Mechanism (Bulk Statistics feature). The example is described in the following subsections:
•
•
Transfer Parameters
The following transfer parameters were used for the "Configuring the Periodic MIB Data Collection and Transfer Mechanism" example:
•
•
•
•
•
Polling Requirements
The following polling requirements for ATM interface 2/0 and Ethernet interface 2/1 were used for the "Configuring the Periodic MIB Data Collection and Transfer Mechanism" example:
ATM interface 2/0
•
•
•
•
Ethernet Interface 2/1
•
•
•
•
Object List Configuration
Note that since the IF-MIB objects and the CAR-MIB objects do not have the same index, they will have to be a part of different schemas. However, since the objects required are the same for the ATM interface and the Ethernet interface, the object list can be reused for each schema. Therefore, in the following example, an object list is created for the for the IF-MIB objects and another object list is created for the CAR-MIB objects.
Router(config)# snmp mib bulkstat object-list ifmibRouter(config-bulk-objects)# add ifInoctetsRouter(config-bulk-objects)# add ifOutoctetsRouter(config-bulk-objects)# add ifInUcastPktsRouter(config-bulk-objects)# add ifInDiscardsRouter(config-bulk-objects)# exitRouter(config)# snmp mib bulkstat object-list CAR-mibRouter(config-bulk-objects)# add CcarStatSwitchedPktsRouter(config-bulk-objects)# add CcarStatSwitchedBytesRouter(config-bulk-objects)# add CcarStatFilteredBytesRouter(config-bulk-objects)# exitSchema Definition Configuration
For the following bulk statistics schema configuration, two schemas are defined for each interface—one for the IF-MIB object instances and one for the CAR-MIB object instances.
! ATM IF-MIB schemaRouter(config)# snmp mib bulkstat schema ATM2/0-IFMIB! The following command points to the IF-MIB object list, defined above.Router(config-bulk-sc)# object-list ifmibRouter(config-bulk-sc)# poll-interval 5Router(config-bulk-sc)# instance exact interface ATM2/0 subifRouter(config-bulk-sc)# exit! ATM CAR-MIB schemaRouter(config)# snmp mib bulkstat schema-def ATM2/0-CARRouter(config-bulk-sc)# object-list CAR-mibRouter(config-bulk-sc)# poll-interval 5Router(config-bulk-sc)# instance wildcard interface ATM2/0 subifRouter(config-bulk-sc)# exit!Ethernet IF-MIB schemaRouter(config)# snmp mib bulkstat schema Ethernet2/1-IFMIBRouter(config-bulk-sc)# object-list ifmibRouter(config-bulk-sc)# poll-interval 5Router(config-bulk-sc)# instance exact interface Ethernet2/1Router(config-bulk-sc)# exit! Ethernet CAR-MIB schemaRouter(config)# snmp mib bulkstat schema Ethernet2/1-CARRouter(config-bulk-sc)# object-list CAR-mibRouter(config-bulk-sc)# poll-interval 5! Note: ifindex of Ethernet2/1 is 3Router(config-bulk-sc)# instance wildcard oid 3.1Router(config-bulk-sc)# exitTransfer Parameter Configuration
For the transfer of the bulk statistics file, the transfer configuration is given the name bulkstat1. All of the four schema definitions are included in the following transfer configuration.
Router(config)# snmp mib bulkstat transfer bulkstat1Router(config-bulk-tr)# schema ATM2/0-IFMIBRouter(config-bulk-tr)# schema ATM2/0-CARRouter(config-bulk-tr)# schema Ethernet2/1-IFMIBRouter(config-bulk-tr)# schema Ethernet2/1-CARRouter(config-bulk-tr)# url primary ftp://username1:pswrd@cbin2-host/users/username1/bulkstat1Router(config-bulk-tr)# url secondary tftp://username1@10.1.0.1/tftpboot/username1/bulkstat1Router(config-bulk-tr)# format schemaASCIIRouter(config-bulk-tr)# transfer-interval 30Router(config-bulk-tr)# retry 5Router(config-bulk-tr)# buffer-size 1024Router(config-bulk-tr)# retain 30Router(config-bulk-tr)# endRouter# copy running-config startup-configDisplaying Status
The following sample output for the show snmp mib bulkstat transfer command shows that the initial transfer attempt and the first retry has failed for the newest file, and four additional retry attempts will be made:
Router# show snmp mib bulkstat transferTransfer Name : bulkstat1Primary URL ftp://user:XXXXXXXX@192.168.200.162/Secondary ftp://user:XXXXXXXX@192.168.200.163/Retained filesFile Name : Time Left (in seconds) : STATE----------------------------------------------------------------------bulkstat1_Router_030307_102519739: 1196 :Retry(4 Retry attempt(s) Left)bulkstat1_Router_030307_102219739: 1016 :Retainedbulkstat1_Router_030307_101919739: 836 :RetainedThe filename for the bulk statistics file is generated with the following extensions to the name you specify in the url command:
specified-filename_device-name_date_time-stamp
The device name is the name of the sending device, as specified in the CLI prompt.
The time-stamp format will depend on your system configuration. Typically, the format for the date is YYYYMMDD or YYMMDD. The time stamp uses a 24-hour clock notation, and the format is HHMMSSmmm (where mmm are milliseconds).
In the example above, the files were created on March 7, 2003, at 10:25 a.m., 10:22 a.m., and 10:19 a.m.
Bulk Statistics Output File
The following is sample output as it appears in the bulk statistics file received at the transfer destination. In this output, the name of the bulk statistics file is bulkstat1_Router_20030131_193354234. Also, note that the schema definition (Schema-def) for the schema Ethernet2/1-IFMIB was added to the file as the configuration was changed (see comment lines indicated by "!").
Schema-def ATM2/0-IFMIB "%u, %s, %u, %u, %u, %u"epochtime ifDescr instanceoid ifInOctets ifOutOctets ifInUcastPkts ifInDiscardsSchema-def ATM2/0-CAR "%u, %s, %s, %u, %u, %u, %u "epochtime ifDescr instanceoid CcarStatSwitchedPkts ccarStatSwitchedBytes CcarStatSwitchedPkts ccarStatSwitchedBytesSchema-def Ethernet2/1-IFMIB "%u, %u, %u, %u, %u, %u"epochtime ifDescr instanceoid ifInOctets ifOutOctets ifInUcastPkts ifInDiscardsSchema-def Ethernet2/1-CAR "%u, %s, %u, %u, %u, %u "Epochtime instanceoid CcarStatSwitchedPkts ccarStatSwitchedBytes CcarStatSwitchedPkts ccarStatSwitchedBytesSchema-def GLOBAL "%s, %s, %s, %u, %u, %u, %u"hostname data timeofday sysuptime cpu5min cpu1min cpu5secATM2/0-IFMIB: 954417080, ATM2/0, 2, 95678, 23456, 234, 3456ATM2/0-IFMIB: 954417080, ATM2/0.1, 8, 95458, 54356, 245, 454ATM2/0-IFMIB: 954417080, ATM2/0.2, 9, 45678, 8756, 934, 36756ATM2/0-CAR: 954417083, ATM2/0, 2.1.1, 234, 345, 123, 124ATM2/0-CAR: 954417083, ATM2/0, 2.2.1, 452, 67, 132, 145ATM2/0-CAR: 954417083, ATM2/0.1, 8.1.1, 224, 765, 324 234ATM2/0-CAR: 954417083, ATM2/0.1, 8.2.1, 234, 345, 123, 124ATM2/0-CAR: 954417083, ATM2/0.2, 9.1.1, 234, 345, 123, 124ATM2/0-CAR: 954417083, ATM2/0.2, 9.2.1, 452, 67, 132, 145Ethernet2/1-IFMIB: 954417090, Ethernet2/1, 3, 45678, 8756, 934, 36756Ethernet2/1-CAR: 954417093, 3.1.1, 234, 345, 123, 124Ethernet2/1-CAR: 954417093, 3.1.2, 134, 475, 155, 187ATM2/0-IFMIB: 954417100, ATM2/0, 2, 95678, 23456, 234, 3456ATM2/0-IFMIB: 954417101, ATM2/0.1, 8, 95458, 54356, 245, 454ATM2/0-IFMIB: 954417102, ATM2/0.2, 9, 45678, 8756, 934, 36756ATM2/0-CAR: 954417106, ATM2/0, 2.1.1, 234, 345, 123, 124ATM2/0-CAR: 954417107, ATM2/0, 2.2.1, 452, 67, 132, 145ATM2/0-CAR: 954417107, ATM2/0.1, 8.1.1, 224, 765, 324 234ATM2/0-CAR: 954417108, ATM2/0.1, 8.2.1, 234, 345, 123, 124ATM2/0-CAR: 954417113, ATM2/0.2, 9.1.1, 234, 345, 123, 124ATM2/0-CAR: 954417114, ATM2/0.2, 9.2.1, 452, 67, 132, 145! Here the Schema-def for "Ehternet2/1-IFMIB" was changed on the originating device.Schema-def Ethernet2/1-IFMIB "%u, %u, %u, %u, %u, %u"! The object ifOutDiscards has been added to the object list for this schema.epochtime ifDescr instanceoid ifInOctets ifOutOctets ifInUcastPkts ifInDiscardsifOutDiscards! The following data sample reflects the change in the configuration.Ethernet2/1-IFMIB: 954417090, Ethernet2/1, 3, 45678, 8756, 934, 36756, 123Ethernet2/1-CAR: 954417093, 3.1.1, 234, 345, 123, 124Ethernet2/1-CAR: 954417093, 3.1.2, 134, 475, 155, 187GLOBAL: Govinda, 20020129, 115131, 78337, 783337, 2%, 0%, 62%Additional References
The following sections provide references related to Periodic MIB Data Collection and Transfer Mechanism.
Related Documents
SNMP configuration tasks
"Configuring SNMP Support" section in the Cisco IOS Network Management Configuration Guide, Release 12.4
SNMP commands: complete command syntax, command mode, command history, defaults, usage guidelines, and examples
•
•
•
MIBs
RFCs
Technical Assistance
Command Reference
This section documents only commands that are new or modified.
•
•
•
add (bulkstat object)
To add a MIB object to a bulk statistics object list, use the add command in Bulk Statistics Object List configuration mode. To remove a MIB object from an SNMP bulk statistics object list, use the no form of this command.
add {object-name | oid}
no add {object-name | oid}
Syntax Description
Command Default
No MIB objects are listed in the bulk statistics object list.
Command Modes
Bulk Statistics Object List configuration (config-bulk-objects)
Command History
Usage Guidelines
All the objects in an object -list have to be indexed by the same MIB index, but the objects need not belong to the same MIB table. For example, it is possible to group ifInoctets and an Ether MIB object in the same schema because the containing tables are indexed by the ifIndex (in the IF-MIB).
Object names are available in the relevant MIB modules. For example, the input byte count of an interface is defined in the Interfaces Group MIB (IF-MIB.my) as ifInoctets. Complete MIB modules can be downloaded from Cisco.com at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
Examples
In the following example, two bulk statistics object lists are configured: one for IF-MIB objects and one for CISCO-CAR-MIB objects. Because the IF-MIB objects and the CISCO-CAR-MIB objects do not have the same index, they must be defined in separate object lists.
Router(config)# snmp mib bulkstat object-list if-ObjectsRouter(config-bulk-objects)# add ifInoctetsRouter(config-bulk-objects)# add ifOutoctetsRouter(config-bulk-objects)# add ifInUcastPktsRouter(config-bulk-objects)# add ifInDiscardsRouter(config-bulk-objects)# exitRouter(config)# snmp mib bulkstat object-list CAR-ObjectsRouter(config-bulk-objects)# add CcarStatSwitchedPktsRouter(config-bulk-objects)# add ccarStatSwitchedBytesRouter(config-bulk-objects)# add CcarStatFilteredBytesRouter(config-bulk-objects)# exitRouter(config)#Related Commands
snmp mib bulkstat object-list
Names a bulk statistics object list and enters Bulk Statistics Object List configuration mode.
buffer-size (bulkstat)
To configure a maximum buffer size for the transfer of bulk statistics files, use the buffer-size command in Bulk Statistics Transfer configuration mode. To remove a previously configured buffer size from the configuration, use the no form of this command.
buffer-size bytes
no buffer-size bytes
Syntax Description
bytes
Size of the bulk statistics transfer buffer, in bytes. The valid range is from 1024 to 2147483647. The default is 2048.
Command Default
The default bulk statistics transfer buffer is 2048 bytes.
Command Modes
Bulk Statistics Transfer configuration (config-bulk-tr)
Command History
Usage Guidelines
A configured buffer size limit is available primarily as a safety feature. Normal bulk statistics files should not generally meet or exceed the default value while being transferred.
Examples
In the following example, the bulk statistics transfer buffer size is set to 3072 bytes:
Router(config)# snmp mib bulkstat transfer bulkstat1Router(config-bulk-tr)# schema ATM2/0-IFMIBRouter(config-bulk-tr)# url primary ftp://user:pswrd@host/folder/bulkstat1Router(config-bulk-tr)# buffer-size 3072Router(config-bulk-tr)# enableRouter(config-bulk-tr)# exitRouter(config)#Related Commands
snmp mib bulkstat transfer
Identifies the transfer configuration with a name and enters Bulk Statistics Transfer configuration mode.
debug snmp bulkstat
To enable debugging messages for the SNMP Bulk Statistics feature, use the debug snmp bulkstat command in privileged EXEC mode. To disable debugging messages for this feature, use the no form of this command.
debug snmp bulkstat
no debug snmp bulkstat
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
This command is intended primarily for Cisco support personnel. Debugging output for the Periodic MIB Data Collection and Transfer Mechanism (Bulk Statistics feature) includes messages for data collection, local file generation, and transfer attempts.
Examples
In the following example, debugging command output is enabled for the Periodic MIB Data Collection and Transfer Mechanism (Bulk Statistics feature). Note that the references to a VFile indicate a local bulk statistics file, usually followed by the filename. The filename uses the format specified-filename_device-name_date_time-stamp.
Router# debug snmp bulkstat00:17:38:BULKSTAT-DC:Poll timer fired for ifmib00:17:38:BULKSTAT-DC:In pollDataGroup00:17:38:BULKSTAT-DC:creating new filevfile:IfMIB_objects_ios108_030307_10111973900:17:38:BULKSTAT-DC:Too small state buffer for ifmib10200:17:38:BULKSTAT-DC:Increased buffer state to 102400:17:38:BULKSTAT-DC:Interface type data group00:17:38:BULKSTAT-DC:polling done00:18:38:BULKSTAT-DC:Poll timer fired for ifmib00:18:38:BULKSTAT-DC:In pollDataGroup00:18:38:BULKSTAT-DC:Interface type data group00:18:38:BULKSTAT-DC:polling done00:19:26:BULKSTAT-DC:Collection timer fired for IfMIB_objects00:19:26:BULKSTAT-TP:Transfer request forvfile:IfMIB_objects_ios108_030307_10111973900:19:30:BULKSTAT-TP:written vfileIfMIB_objects_ios108_030307_10111973900:19:30:BULKSTAT-TP:retained vfilevfile:IfMIB_objects_ios108_030307_10111973900:19:38:BULKSTAT-DC:Poll timer fired for ifmib00:19:38:BULKSTAT-DC:In pollDataGroup00:19:38:BULKSTAT-DC:creating new filevfile:IfMIB_objects_ios108_030307_10131973900:19:38:BULKSTAT-DC:Interface type data group00:19:38:BULKSTAT-DC:polling done00:20:38:BULKSTAT-DC:Poll timer fired for ifmib00:20:38:BULKSTAT-DC:In pollDataGroup00:20:38:BULKSTAT-DC:Interface type data group00:20:38:BULKSTAT-DC:polling done00:21:38:BULKSTAT-DC:Poll timer fired for ifmib00:21:38:BULKSTAT-DC:In pollDataGroup00:21:38:BULKSTAT-DC:Interface type data group00:21:38:BULKSTAT-DC:polling done00:22:26:BULKSTAT-DC:Collection timer fired for IfMIB_objects00:22:26:BULKSTAT-TP:Transfer request forvfile:IfMIB_objects_ios108_030307_10131973900:22:26:BULKSTAT-TP:written vfileIfMIB_objects_ios108_030307_10131973900:22:26:BULKSTAT-TP:retained vfilevfile:IfMIB_objects_ios108_030307_10131973900:22:38:BULKSTAT-DC:Poll timer fired for ifmib00:22:38:BULKSTAT-DC:In pollDataGroup00:22:38:BULKSTAT-DC:creating new filevfile:IfMIB_objects_ios108_030307_10161973900:22:38:BULKSTAT-DC:Interface type data group00:22:38:BULKSTAT-DC:polling done00:23:38:BULKSTAT-DC:Poll timer fired for ifmib00:23:38:BULKSTAT-DC:In pollDataGroup00:23:38:BULKSTAT-DC:Interface type data group00:23:38:BULKSTAT-DC:polling done00:24:38:BULKSTAT-DC:Poll timer fired for ifmib00:24:38:BULKSTAT-DC:In pollDataGroup00:24:38:BULKSTAT-DC:Interface type data group00:24:38:BULKSTAT-DC:polling done00:25:26:BULKSTAT-DC:Collection timer fired for IfMIB_objects00:25:26:BULKSTAT-TP:Transfer request forvfile:IfMIB_objects_ios108_030307_10161973900:25:26:BULKSTAT-TP:written vfileIfMIB_objects_ios108_030307_10161973900:25:26:BULKSTAT-TP:retained vfilevfile:IfMIB_objects_ios108_030307_10161973900:25:38:BULKSTAT-DC:Poll timer fired for ifmib00:25:38:BULKSTAT-DC:In pollDataGroup00:25:38:BULKSTAT-DC:creating new filevfile:IfMIB_objects_ios108_030307_10191973900:25:38:BULKSTAT-DC:Interface type data group00:25:38:BULKSTAT-DC:polling done00:26:38:BULKSTAT-DC:Poll timer fired for ifmib00:26:38:BULKSTAT-DC:In pollDataGroup00:26:38:BULKSTAT-DC:Interface type data group00:26:38:BULKSTAT-DC:polling doneRelated Commands
enable (bulkstat)
To begin the bulk statistics data collection and transfer process for a specific bulk statistics configuration, use the enable command in Bulk Statistics Transfer configuration mode. To disable the bulk statistics data collection and transfer process for a specific bulk statistics configuration, use the no form of this command.
enable
no enable
Syntax Description
This command has no arguments or keywords.
Command Default
Bulk statistics transfer is disabled.
Command Modes
Bulk Statistics Transfer configuration (config-bulk-tr)
Command History
Usage Guidelines
Specific bulk statistics configurations are identified with a name, as specified in the snmp mib bulkstat transfer command. The enable command (in Bulk Statistics Transfer configuration mode) begins the periodic MIB data collection and transfer process.
Collection (and subsequent file transfer) will start only if this command is used. Conversely, the no enable command will stop the collection process. Subsequently, issuing the enable command will start the operations again.
Each time the collection process is started using the enable command, data is collected into a new bulk statistics file. When the no enable command is used, the transfer process for any collected data will immediately begin (in other words, the existing bulk statistics file will be transferred to the specified management station).
To successfully enable a bulk statistics configuration, at least one schema with a non-zero number of objects must be configured.
Examples
The following example shows the bulk statistics transfer configuration named bulkstat1 as enabled:
Router(config)# snmp mib bulkstat transfer bulkstat1Router(config-bulk-tr)# schema ATM2/0-IFMIBRouter(config-bulk-tr)# url primary ftp://user:pswrd@host/folder/bulkstat1Router(config-bulk-tr)# enableRouter(config-bulk-tr)# exitRelated Commands
snmp mib bulkstat transfer
Names a bulk statistics transfer configuration and enters Bulk Statistics Transfer configuration mode.
format (bulkstat)
To specify the format to be used for the bulk statistics data file, use the format command in Bulk Statistics Transfer configuration mode. To disable a previously configured format specification and return to the default, use the no form of this command.
format {bulkBinary | bulkASCII | schemaASCII}
no format {bulkBinary | bulkASCII | schemaASCII}
Syntax Description
bulkBinary
Binary format.
bulkASCII
ASCII (human-readable) format.
schemaASCII
ASCII format with additional bulk statistics schema tags. This is the default.
Command Default
The default bulk statistics transfer format is SchemaASCII.
Command Modes
Bulk Statistics Transfer configuration (config-bulk-tr)
Command History
Usage Guidelines
Note
The bulk statistics data file (VFile) contains two types of fields: tags and data. Tags are used to set off data to distinguish fields of the file. All other information is in data fields.
For the BulkASCII and BulkBinary formats, periodic polling enables data for a single data group (object list) to be collected more than once in the same VFile. Each such instance of a data group can be treated as a different "table" type.
Every object and table tag contains an additional sysUpTime field. Similarly each row tag contains the value of the sysUpTime when the data for that row was collected. The sysUpTime provides a time stamp for the data.
For additional information about the structures of the bulk statistics data file formats, see the definitions in the CISCO-DATA-COLLECTION-MIB.
Examples
In the following example, the bulk statistics data file is set to SchemaASCII:
Router(config)# snmp mib bulkstat transfer bulkstat1Router(config-bulk-tr)# schema ATM2/0-IFMIBRouter(config-bulk-tr)# url primary ftp://user:pswrd@host/folder/bulkstat1Router(config-bulk-tr)# format schemaASCIIRouter(config-bulk-tr)# exitRelated Commands
snmp mib bulkstat transfer
Names a bulk statistics transfer configuration and enters Bulk Statistics Transfer configuration mode.
instance (MIB)
To configure the MIB object instances to be used in a bulk statistics schema, use the instance command in Bulk Statistics Schema configuration mode. To remove a Simple Network Management Protocol (SNMP) bulk statistics object list, use the no form of this command.
instance {exact | wild} {interface interface-id [sub-if] | controller controller-id [sub-if] | oid oid}
no instance {exact | wild} {interface interface-id [sub-if] | controller controller-id [sub-if] | oid oid}
Syntax Description
Command Default
If the sub-if keyword is not used, the subinterfaces of the interface or controller will not be polled.
Command Modes
Bulk Statistics Schema configuration (config-bulk-sc)
Command History
Usage Guidelines
The instance command specifies the instance information for objects in the schema being configured. The specific instances of MIB objects for which data should be collected are determined by appending the value of the instance command to the objects specified in the associated object list. In other words, the schema object-list when combined with the schema instance specifies a complete MIB object identifier.
The instance exact command indicates that the specified instance, when appended to the object list, is the complete OID.
The instance wild command indicates that all subindices of the specified OID belong to this schema. In other words, the wild keyword allows you to specify a partial, wildcarded instance.
Instead of specifying an OID, you can specify a specific interface. The interface interface-id keyword and argument allow you to specify an interface name and number (for example, Ethernet 0) instead of specifying the ifIndex OID for the interface. Similarly, the controller controller-id syntax allows you to specify a controller interface.
The optional sub-if keyword, when added after specifying an interface or controller, includes the ifIndexes for all subinterfaces of the interface you specified.
Only one instance command can be configured per schema.
Examples
In the following example, the user configures the router to collect bulk statistics for the ifInOctets object (from the IF-MIB) for the Ethernet interface 3/0. In this example, 3 is the ifIndex instance for interface Ethernet3/0. The instance (3) when combined with the object list (ifIndex; 1.3.6.1.2.1.2.2.1.1) translates to the OID 1.3.6.1.2.1.2.2.1.1.3.
Router# configure terminalRouter(config)# snmp mib bulkstat object-list E0InOctets! The following command specifies the object 1.3.6.1.2.1.2.2.1.1.3 (ifIndex)Router(config-bulk-objects)# add ifIndexRouter(config-bulk-objects)# exitRouter(config)# snmp mib bulkstat schema E0Router(config-bulk-sc)# object-list EOInOctets! The following command is equivalent to "instance exact oid 3".Router(config-bulk-sc)# instance exact interface Ethernet 3/0Router(config-bulk-sc)# exitRouter(config)# snmp mib bulkstat transfer bulkstat1Router(config-bulk-tr)# schema E0Router(config-bulk-tr)# url primary ftp://user:password@host/ftp/user/bulkstat1Router(config-bulk-tr)# url secondary tftp://user@host/tftp/user/bulkstat1Router(config-bulk-tr)# format schemaASCIIRouter(config-bulk-tr)# transfer-interval 30Router(config-bulk-tr)# retry 5Router(config-bulk-tr)# enableRouter(config-bulk-tr)# exitRouter(config)# do copy running-config startup-configRelated Commands
object-list
To specify the bulk statistics object list to be used in the bulk statistics schema, use the object-list command in Bulk Statistics Schema configuration mode. To remove an object list from the schema, use the no form of this command.
object-list list-name
no object-list list-name
Syntax Description
Command Default
No bulk statistics object list is specified.
Command Modes
Bulk Statistics Schema configuration (config-bulk-sc)
Command History
Usage Guidelines
This command associates a bulk statistics object list with the schema being configured. The object list should contain a list of MIB objects to be monitored.
Only one object list can be specified for each schema.
Examples
In the following example, the object list named E0InOctets is associated with the schema named E0:
Router(config)# snmp mib bulkstat schema E0Router(config-bulk-sc)# object-list EOInOctetsRouter(config-bulk-sc)# instance exact interface Ethernet 3/0Router(config-bulk-sc)# exitRelated Commands
poll-interval
To configure the polling interval for a bulk statistics schema, use the poll-interval command in Bulk Statistics Schema configuration mode. To remove a previously configured polling interval, use the no form of this command.
poll-interval minutes
no poll-interval minutes
Syntax Description
minutes
Integer in the range from 1 to 20000 that specifies, in minutes, the polling interval of data for this schema. The default is 5.
Command Default
Object instances are polled once every five minutes.
Command Modes
Bulk Statistics Schema configuration (config-bulk-sc)
Command History
Usage Guidelines
The poll-interval command sets how often the MIB instances specified by the schema and associated object list are to be polled. Collected data is stored in the local bulk statistics file for later transfer.
Examples
In the following example the polling interval for bulk statistics collection is set to once every 3 minutes in the schema called Ethernet2/1-CAR:
Router(config)# snmp mib bulkstat schema Ethernet2/1-CARRouter(config-bulk-sc)# object-list CAR-mibRouter(config-bulk-sc)# poll-interval 3Router(config-bulk-sc)# instance wildcard oid 3.1Router(config-bulk-sc)# exitRelated Commands
snmp mib bulkstat schema
Names a bulk statistics schema and enters Bulk Statistics Schema configuration mode.
retain
To configure the retention interval for bulk statistics files, use the retain command in Bulk Statistics Transfer configuration mode. To remove a previously configured retention interval from the configuration, use the no form of this command.
retain minutes
no retain minutes
Syntax Description
minutes
Length of time, in minutes, that the local bulk statistics file should be kept in system memory (the retention interval). The valid range is 0 to 20000. The default is 0.
Command Default
The bulk statistics file retention interval is 0 minutes.
Command Modes
Bulk Statistics Transfer configuration (config-bulk-tr)
Command History
Usage Guidelines
This command specifies how long the bulk statistics file should be kept in system memory, in minutes, after the completion of the collection interval and a transmission attempt is made. The default value of zero (0) indicates that the file will be deleted immediately from local memory after a successful transfer.
If the retry command is used, you should configure a retention interval greater than 0. The interval between retries is the retention interval divided by the retry number. For example, if retain 10 and retry 2 are configured, retries will be attempted once every 5 minutes. Therefore, if the retain command is not configured (retain default is 0), no retries will be attempted.
Examples
In the following example, the bulk statistics transfer retention interval is set to 10 minutes:
Router(config)# snmp mib bulkstat transfer bulkstat1Router(config-bulk-tr)# schema ATM2/0-IFMIBRouter(config-bulk-tr)# url primary ftp://user:pswrd@host/folder/bulkstat1Router(config-bulk-tr)# retry 2Router(config-bulk-tr)# retain 10Router(config-bulk-tr)# exitRelated Commands
retry (bulkstat)
To configure the number of retries that should be attempted for a bulk statistics file transfer, use the retry command in Bulk Statistics Transfer configuration mode. To return the number of bulk statistics retries to the default, use the no form of this command.
retry number
no retry number
Syntax Description
Command Default
No retry attempts are made.
Command Modes
Bulk Statistics Transfer configuration (config-bulk-tr)
Command History
Usage Guidelines
If an attempt to send the bulk statistics file fails, the system can be configured to attempt to send the file again using the retry command. One retry includes an attempt first to the primary destination and then, if the transmission fails, to the secondary location; for example, if the retry value is 1, an attempt will be made first to the primary URL, then to the secondary URL, then to the primary URL again, and then to the secondary URL again.
If the retry command is used, you should also use the retain command to configure a retention interval greater than 0. The interval between retries is the retention interval divided by the retry number. For example, if retain 10 and retry 2 are configured, retries will be attempted once every 5 minutes. Therefore, if the retain command is not configured (or the retain 0 command is used) no retries will be attempted.
Examples
In the following example, the number of retries for the bulk statistics transfer is set to 2:
Router(config)# snmp mib bulkstat transfer bulkstat1Router(config-bulk-tr)# schema ATM2/0-IFMIBRouter(config-bulk-tr)# url primary ftp://user:pswrd@host/folder/bulkstat1Router(config-bulk-tr)# retry 2Router(config-bulk-tr)# retain 10Router(config-bulk-tr)# exitRelated Commands
schema
To specify the bulk statistics schema to be used in a specific bulk statistics transfer configuration, use the schema command in Bulk Statistics Transfer configuration mode. To remove a previously configured schema from a specific bulk statistics transfer configuration, use the no form of this command.
schema schema-name
no schema schema-name
Syntax Description
Command Default
No bulk statistics schema is specified.
Command Modes
Bulk Statistics Transfer configuration (config-bulk-tr)
Command History
Usage Guidelines
Repeat this command as desired for a specific bulk statistics transfer configuration. Multiple schemas can be associated with a single transfer configuration; all collected data will be in a single bulk statistics data file (VFile).
Examples
In the following example, the bulk statistics schemas ATM2/0-IFMIB and ATM2/0-CAR are associated with the bulk statistics transfer configuration called bulkstat1:
Router(config)# snmp mib bulkstat transfer bulkstat1Router(config-bulk-tr)# schema ATM2/0-IFMIBRouter(config-bulk-tr)# schema ATM2/0-CARRouter(config-bulk-tr)# url primary ftp://user:pswrd@host/folder/bulkstat1Router(config-bulk-tr)# retry 2Router(config-bulk-tr)# retain 10Router(config-bulk-tr)# exitRelated Commands
snmp mib bulkstat transfer
Names a bulk statistics transfer configuration and enters Bulk Statistics Transfer configuration mode.
show snmp mib bulkstat transfer
To display the transfer status of files generated by the Periodic MIB Data Collection and Transfer Mechanism (Bulk Statistics feature), use the show snmp mib bulkstat transfer command in privileged EXEC mode.
show snmp mib bulkstat transfer [transfer-id]
Syntax Description
transfer-id
(Optional) Name of a specific bulk statistics transfer configuration.
Use the transfer-id argument to display the status of a specific bulk statistics transfer configuration.
Command Default
If the optional transfer-id argument is not used, the status of all configured bulk statistics transfers is displayed.
Command Modes
Privileged EXEC (#)
Command History
Examples
In the following example, the initial transfer attempt and the first retry for the file IfMIB_objects_Router_030307_102519739 to the primary and secondary URL have failed, and four additional retry attempts will be made. The time stamp for this file indicates the file was created on March 7, 2003, at 10:25:19 a.m.
Router# show snmp mib bulkstat transferTransfer Name : IfMIB_objectsPrimary URL ftp://user:XXXXXXXX@192.168.1.229/Secondary ftp://user:XXXXXXXX@192.168.1.230/Retained filesFile Name :Time Left (in seconds) : STATE----------------------------------------------------------------------IfMIB_objects_Router_030307_102519739 : 1196 :Retry(5 Retry attempt(s) Left)IfMIB_objects_Router_030307_102219739 : 1016 :RetainedIfMIB_objects_Router_030307_101919739 : 836 :RetainedIfMIB_objects_Router_030307_101619739 : 656 :RetainedIfMIB_objects_Router_030307_101319739 : 475 :RetainedIfMIB_objects_Router_030307_101119739 : 295 :RetainedTable 1 describes the significant fields shown in the output.
Related Commands
snmp mib bulkstat transfer
Names a bulk statistics transfer configuration and enters Bulk Statistics Transfer configuration mode.
snmp mib bulkstat object-list
To configure a Simple Network Management Protocol (SNMP) bulk statistics object list, use the snmp mib bulkstat object-list command in global configuration mode. To remove an SNMP bulk statistics object list, use the no form of this command.
snmp mib bulkstat object-list name
no snmp mib bulkstat object-list name
Syntax Description
Command Default
No SNMP bulk statistics object list is configured.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
The snmp mib bulkstat object-list command allows you to name an object list. Bulk statistics object lists are used for the Periodic MIB Data Collection and Transfer Mechanism.
After you enter this command, the router enters Bulk Statistics Object List configuration mode, in which you can use the add command to add specific MIB objects to the list.
Bulk statistics object lists can be reused in multiple schemas.
Examples
In the following example, a bulk statistics object list called ifMib is configured to include the ifInoctets, ifOutoctets, ifInUcastPkts, and ifInDiscards objects from the Interfaces Group MIB (IF-MIB):
Router(config)# snmp mib bulkstat object-list ifmibRouter(config-bulk-objects)# add ifInoctetsRouter(config-bulk-objects)# add ifOutoctetsRouter(config-bulk-objects)# add ifInUcastPktsRouter(config-bulk-objects)# add ifInDiscardsRouter(config-bulk-objects)# endRelated Commands
snmp mib bulkstat schema
To define a bulk statistics schema, use the snmp mib bulkstat schema command in global configuration mode. To delete a previously configured bulk statistics schema, use the no form of this command.
snmp mib bulkstat schema schema-name
no snmp mib bulkstat schema schema-name
Syntax Description
Command Default
No schemas are defined.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
The snmp mib bulkstat schema command names the schema and enters Bulk Statistics Schema configuration mode. Bulk Statistics Schema configuration mode is used to configure the object list, instance, and polling interval to be used in the schema.
The specific instances of MIB objects for which data should be collected are determined by appending the value of the instance command to the objects specified in the object list.
Multiple schemas can be associated with a single bulk statistics file when configuring the bulk statistics transfer options.
Examples
The following example shows the configuration of a bulk statistics schema called ATM2/0-IFMIB:
Router(config)# snmp mib bulkstat schema ATM2/0-IFMIBRouter(config-bulk-sc)# object-list ifmibRouter(config-bulk-sc)# poll-interval 5Router(config-bulk-sc)# instance exact interface ATM2/0 subifRouter(config-bulk-sc)# exitRelated Commands
snmp mib bulkstat transfer
To identify the bulk statistics transfer configuration and enter Bulk Statistics Transfer configuration mode, use the snmp mib bulkstat transfer command in global configuration mode. To remove a previously configured transfer, use the no form of this command.
snmp mib bulkstat transfer transfer-id
no snmp mib bulkstat transfer transfer-id
Syntax Description
Command Default
No bulk statistics transfer configuration exists.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
The name (transfer-id) you specify for the bulk statistics transfer configuration is used in the filename of the bulk statistics file when it is generated and is used to identify the transfer configuration in the output of the show snmp mib bulkstat transfer command.
This command enters Bulk Statistics Transfer configuration mode, as indicated by the prompt (config-bulk-tr).
Examples
In the following example, the transfer configuration is given the name bulkstat1 and is configured to include the schemas ATM2/0-IFMIB and ATM2/0-CAR:
Router(config)# snmp mib bulkstat transfer bulkstat1Router(config-bulk-tr)# schema ATM2/0-IFMIBRouter(config-bulk-tr)# schema ATM2/0-CARRouter(config-bulk-tr)# url primary ftp://user1:pswrd@cbin2-host/users/user1/bulkstat1Router(config-bulk-tr)# url secondary tftp://user1@10.1.0.1/tftpboot/user1/bulkstat1Router(config-bulk-tr)# format schemaASCIIRouter(config-bulk-tr)# transfer-interval 30Router(config-bulk-tr)# retry 5Router(config-bulk-tr)# buffer-size 1024Router(config-bulk-tr)# retain 30Router(config-bulk-tr)# endRouter# copy running-config startup-configRelated Commands
show snmp mib bulkstat transfer
Displays the transfer status of files generated by the Periodic MIB Data Collection and Transfer Mechanism.
snmp-server enable traps bulkstat
To enable the sending of Simple Network Management Protocol (SNMP) bulk statistics collection and transfer SNMP notifications, use the snmp-server enable traps bulkstat command in global configuration mode. To disable bulk statistics SNMP notifications, use the no form of this command.
snmp-server enable traps bulkstat [collection | transfer]
no snmp-server enable traps bulkstat [collection | transfer]
Syntax Description
Command Default
SNMP notifications are disabled.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
SNMP notifications can be sent as traps or inform requests. The snmp-server enable traps bulkstat command enables both traps and inform requests for the specified notification types. Use this command with the snmp-server host [bulkstat] command.
The optional collection keyword controls bulk statistics collection notifications that are sent when data collection cannot be carried out successfully. One possible reason for this condition is insufficient memory on the device.
If the optional keywords are not used, all bulk statistics notification types are enabled (or disabled, if the no form of the command is used).
Examples
In the following example, bulk statistics collection and transfer notifications are configured to be sent to the host myhost.cisco.com using the community string public:
Router(config)# snmp-server enable traps bulkstatRouter(config)# snmp-server host myhost.cisco.com traps version 2c public bulkstatRelated Commands
transfer-interval
To configure how long bulk statistics should be collected before a bulk statistics transfer is initiated, use the transfer-interval command in Bulk Statistics Transfer configuration mode. To remove a previously configured interval from a bulk statistics configuration, use the no form of this command.
transfer-interval minutes
no transfer-interval minutes
Syntax Description
minutes
Length of time, in minutes, that the system should collect MIB data before attempting the transfer operation. The valid range is from 1 to 2147483647. The default is 30.
Command Default
Bulk statistics file transfer operations start 30 minutes after the enable (bulkstat) command is used.
Command Modes
Bulk Statistics Transfer configuration (config-bulk-tr)
Command History
Usage Guidelines
Bulk statistics data is collected into a new file when a transfer attempt begins, which means that this command also configures the collection interval.
If the maximum buffer size for a bulk statistics file is reached before the transfer interval time expires, the transfer operation will still be initiated, and bulk statistics MIB data will be collected into a new file in the system buffer.
Examples
The following example shows how to configure a transfer interval of 20 minutes for the bulk statistics configuration bulkstat1:
Router(config)# snmp mib bulkstat transfer bulkstat1Router(config-bulk-tr)# transfer-interval 20Related Commands
snmp mib bulkstat transfer
Names a bulk statistics transfer configuration and enters Bulk Statistics Transfer configuration mode.
url (bulkstat)
To specify the host to which bulk statistics files should be transferred, use the url command in Bulk Statistics Transfer configuration mode. To remove a previously configured destination host, use the no form of this command.
url {primary | secondary} url
no url {primary | secondary} url
Syntax Description
Command Default
No host is specified.
Command Modes
Bulk Statistics Transfer configuration (config-bulk-tr)
Command History
Usage Guidelines
For bulk statistics transfer retry attempts, a single retry consists of an attempt to send first to the primary URL, and then to the secondary URL.
Examples
In the following example, an FTP server is used as the primary destination for the bulk statistics file. If a transfer to that address fails, an attempt is made to send the file to the TFTP server at 192.168.10.5. No retry command is specified, which means that only one attempt to each destination will be made.
Router(config)# snmp mib bulkstat transfer ifMibTestingRouter(config-bulk-tr)# schema carMibTesting1Router(config-bulk-tr)# schema carMibTesting2Router(config-bulk-tr)# format bulkBinaryRouter(config-bulk-tr)# transfer-interval 60Router(config-bulk-tr)# buffer-size 10000Router(config-bulk-tr)# url primary ftp://user2:pswd@192.168.10.5/functionality/Router(config-bulk-tr)# url secondary tftp://user2@192.168.10.8/tftpboot/Router(config-bulk-tr)# buffer-size 2500000Router(config-bulk-tr)# enableRouter(config-bulk-tr)# exitRelated Commands
Appendix A: Object Names Supported for the add Command
Table 2 through Table 4 contain the object names that can be used with the add command when configuring an object list and their associated OIDs. These object names can be used instead of specifying the OID number.
CCVP, the Cisco logo, and the Cisco Square Bridge logo are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networking Academy, Network Registrar, Packet, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0705R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2003-2004, 2006-2007 Cisco Systems, Inc. All rights reserved.
