The MIB module allows a management application to
select a set of MIB object instances whose values need
to be collected on a periodic basis. The term 'data' in
the context of this MIB is used to generically refer to
the values of the selected set of object instances.
Once the required setup is done, the MIB implementation
carries out the following periodic tasks:
- collects the required object values into local
file-like entities called VFiles (virtual files).
- transfers the VFiles to specified locations.
- carries out VFile management operations.
Some of the key features of this MIB are:
a) Allows grouping of MIB objects into groups called
data groups. The constraint is that the MIB objects
grouped into a data group, need to have the same
semantic MIB index. So it is possible to group MIB
objects belonging to different MIB tables into a
single data group as long as the above constraint is
met.
For e.g. it is possible to group ifInOctets from
ifTable, ifHCInOctets from ifXTable,
dot3StatsExcessiveCollisions from dot3StatsTable
into a single data group.
b) Allows the application to specify a set of instances
(of the MIB objects in a data group) whose values
need to be collected.
c) The required data can be collected for each such
data group on a periodic basis into a virtual file
(VFile). A VFile is an abstraction of a file.
d) The format of the contents of the VFile, can be
specified by the application.
e) An application can also specify a collection period.
A collection period is an interval of time during
which data is collected into a VFile. After the
collection period ends, the VFile is frozen, and a
new VFile is created for storing data. The frozen
VFile is then transferred to a specified destination.
An application can choose to retain such frozen
VFiles on the device for a certain period of time,
called the retention period.
Data Collection MIB vs Bulkfile MIB
***********************************
The data collection MIB can pretty much do what the
CISCO-BULK-FILE-MIB (Bulkfile MIB) can do. The 'manual'
mode of the Data collection MIB is similar to the way
in which the Bulkfile MIB operates.
However the data collection MIB is mainly targetted
for medium to high-end platforms which have sufficient
local storage (volatile or permanent) to store VFiles.
Locally storing VFiles, helps minimize loss of data
during temporary network outages. If the local store
is permament, then the collected data is also available
across agent restarts.
The data collection MIB has more powerful data
selection features than the Bulkfile MIB. It allows
grouping of MIB objects from different tables into
data groups. It also incorporates a more flexible
instance selection mechanism, where the application
is not restricted to fetching an entire MIB table.
Definitions:
************
Base objects:
*************
MIB objects whose values an application needs to
collect.
Data group:
***********
A group of base objects. Can be of 2 types: 'object'
and 'table'. An 'object' type data group can consist
of only one fully instantiated base object. A 'table'
type data group can consist of more than one base
objects, each a columnar object in a conceptual
table. In addition a 'table' type data group can
specify the instances of the base objects whose
values need to be collected. In the context of this
MIB, collecting data for a data group means fetching
the values of the associated base object instances
and storing them into VFiles.
Virtual File (VFile):
*********************
A VFile is a file like entity used to collect data.
An agent might choose to implement a VFile as a
simple in-memory buffer, or it might choose to
use a file in it's filesystem. An application does
not really need to know the location of a VFile
- the MIB provides mechanisms to transfer the
VFile to application specified locations. However
if the implementation supports it, the application
can specify the location of the VFiles.
Current VFile:
**************
The VFile into which data is currently being
collected.
Frozen VFile:
*************
A VFile which is no longer used for collecting
data. Only frozen VFiles can be transferred to
specified destinations.
Collection interval:
********************
A collection interval is associated with a VFile.
It is the interval of time over which a VFile
is used to collect data.
This interval of time can be specified by the
application. However there are conditions under
which a collection interval can be shorter than
the specified time. For e.g. a collection
interval is prematurely terminated when the
maximum size of a VFile is exceeded, or when
there is an error condition.
Polling period:
***************
A polling period is associated with a data
group. It determines the frequency at which
the base objects of a data group should
be fetched and stored into a VFile.
Data collection operations:
**************************
A generic term used to refer to operations
that are carried out while collecting data.
These include:
- Periodically creating new VFiles for
collecting data.
- Transferring frozen VFiles either
automatically or on demand.
- Fetching base object values and storing
them into current VFiles, either periodically
or on demand.
- Deleting frozen VFiles, either periodically
or on demand.
Parsed from file CISCO-DATA-COLLECTION-MIB.mib
Module: CISCO-DATA-COLLECTION-MIB
The MIB module allows a management application to
select a set of MIB object instances whose values need
to be collected on a periodic basis. The term 'data' in
the context of this MIB is used to generically refer to
the values of the selected set of object instances.
Once the required setup is done, the MIB implementation
carries out the following periodic tasks:
- collects the required object values into local
file-like entities called VFiles (virtual files).
- transfers the VFiles to specified locations.
- carries out VFile management operations.
Some of the key features of this MIB are:
a) Allows grouping of MIB objects into groups called
data groups. The constraint is that the MIB objects
grouped into a data group, need to have the same
semantic MIB index. So it is possible to group MIB
objects belonging to different MIB tables into a
single data group as long as the above constraint is
met.
For e.g. it is possible to group ifInOctets from
ifTable, ifHCInOctets from ifXTable,
dot3StatsExcessiveCollisions from dot3StatsTable
into a single data group.
b) Allows the application to specify a set of instances
(of the MIB objects in a data group) whose values
need to be collected.
c) The required data can be collected for each such
data group on a periodic basis into a virtual file
(VFile). A VFile is an abstraction of a file.
d) The format of the contents of the VFile, can be
specified by the application.
e) An application can also specify a collection period.
A collection period is an interval of time during
which data is collected into a VFile. After the
collection period ends, the VFile is frozen, and a
new VFile is created for storing data. The frozen
VFile is then transferred to a specified destination.
An application can choose to retain such frozen
VFiles on the device for a certain period of time,
called the retention period.
Data Collection MIB vs Bulkfile MIB
***********************************
The data collection MIB can pretty much do what the
CISCO-BULK-FILE-MIB (Bulkfile MIB) can do. The 'manual'
mode of the Data collection MIB is similar to the way
in which the Bulkfile MIB operates.
However the data collection MIB is mainly targetted
for medium to high-end platforms which have sufficient
local storage (volatile or permanent) to store VFiles.
Locally storing VFiles, helps minimize loss of data
during temporary network outages. If the local store
is permament, then the collected data is also available
across agent restarts.
The data collection MIB has more powerful data
selection features than the Bulkfile MIB. It allows
grouping of MIB objects from different tables into
data groups. It also incorporates a more flexible
instance selection mechanism, where the application
is not restricted to fetching an entire MIB table.
Definitions:
************
Base objects:
*************
MIB objects whose values an application needs to
collect.
Data group:
***********
A group of base objects. Can be of 2 types: 'object'
and 'table'. An 'object' type data group can consist
of only one fully instantiated base object. A 'table'
type data group can consist of more than one base
objects, each a columnar object in a conceptual
table. In addition a 'table' type data group can
specify the instances of the base objects whose
values need to be collected. In the context of this
MIB, collecting data for a data group means fetching
the values of the associated base object instances
and storing them into VFiles.
Virtual File (VFile):
*********************
A VFile is a file like entity used to collect data.
An agent might choose to implement a VFile as a
simple in-memory buffer, or it might choose to
use a file in it's filesystem. An application does
not really need to know the location of a VFile
- the MIB provides mechanisms to transfer the
VFile to application specified locations. However
if the implementation supports it, the application
can specify the location of the VFiles.
Current VFile:
**************
The VFile into which data is currently being
collected.
Frozen VFile:
*************
A VFile which is no longer used for collecting
data. Only frozen VFiles can be transferred to
specified destinations.
Collection interval:
********************
A collection interval is associated with a VFile.
It is the interval of time over which a VFile
is used to collect data.
This interval of time can be specified by the
application. However there are conditions under
which a collection interval can be shorter than
the specified time. For e.g. a collection
interval is prematurely terminated when the
maximum size of a VFile is exceeded, or when
there is an error condition.
Polling period:
***************
A polling period is associated with a data
group. It determines the frequency at which
the base objects of a data group should
be fetched and stored into a VFile.
Data collection operations:
**************************
A generic term used to refer to operations
that are carried out while collecting data.
These include:
- Periodically creating new VFiles for
collecting data.
- Transferring frozen VFiles either
automatically or on demand.
- Fetching base object values and storing
them into current VFiles, either periodically
or on demand.
- Deleting frozen VFiles, either periodically
or on demand.
Parsed from file CISCO-DATA-COLLECTION-MIB.my.txt
Company: None
Module: CISCO-DATA-COLLECTION-MIB
The MIB module allows a management application to
select a set of MIB object instances whose values need
to be collected on a periodic basis. The term 'data' in
the context of this MIB is used to generically refer to
the values of the selected set of object instances.
Once the required setup is done, the MIB implementation
carries out the following periodic tasks:
- collects the required object values into local
file-like entities called VFiles (virtual files).
- transfers the VFiles to specified locations.
- carries out VFile management operations.
Some of the key features of this MIB are:
a) Allows grouping of MIB objects into groups called
data groups. The constraint is that the MIB objects
grouped into a data group, need to have the same
semantic MIB index. So it is possible to group MIB
objects belonging to different MIB tables into a
single data group as long as the above constraint is
met.
For e.g. it is possible to group ifInOctets from
ifTable, ifHCInOctets from ifXTable,
dot3StatsExcessiveCollisions from dot3StatsTable
into a single data group.
b) Allows the application to specify a set of instances
(of the MIB objects in a data group) whose values
need to be collected.
c) The required data can be collected for each such
data group on a periodic basis into a virtual file
(VFile). A VFile is an abstraction of a file.
d) The format of the contents of the VFile, can be
specified by the application.
e) An application can also specify a collection period.
A collection period is an interval of time during
which data is collected into a VFile. After the
collection period ends, the VFile is frozen, and a
new VFile is created for storing data. The frozen
VFile is then transferred to a specified destination.
An application can choose to retain such frozen
VFiles on the device for a certain period of time,
called the retention period.
Data Collection MIB vs Bulkfile MIB
***********************************
The data collection MIB can pretty much do what the
CISCO-BULK-FILE-MIB (Bulkfile MIB) can do. The 'manual'
mode of the Data collection MIB is similar to the way
in which the Bulkfile MIB operates.
However the data collection MIB is mainly targetted
for medium to high-end platforms which have sufficient
local storage (volatile or permanent) to store VFiles.
Locally storing VFiles, helps minimize loss of data
during temporary network outages. If the local store
is permament, then the collected data is also available
across agent restarts.
The data collection MIB has more powerful data
selection features than the Bulkfile MIB. It allows
grouping of MIB objects from different tables into
data groups. It also incorporates a more flexible
instance selection mechanism, where the application
is not restricted to fetching an entire MIB table.
Definitions:
************
Base objects:
*************
MIB objects whose values an application needs to
collect.
Data group:
***********
A group of base objects. Can be of 2 types: 'object'
and 'table'. An 'object' type data group can consist
of only one fully instantiated base object. A 'table'
type data group can consist of more than one base
objects, each a columnar object in a conceptual
table. In addition a 'table' type data group can
specify the instances of the base objects whose
values need to be collected. In the context of this
MIB, collecting data for a data group means fetching
the values of the associated base object instances
and storing them into VFiles.
Virtual File (VFile):
*********************
A VFile is a file like entity used to collect data.
An agent might choose to implement a VFile as a
simple in-memory buffer, or it might choose to
use a file in it's filesystem. An application does
not really need to know the location of a VFile
- the MIB provides mechanisms to transfer the
VFile to application specified locations. However
if the implementation supports it, the application
can specify the location of the VFiles.
Current VFile:
**************
The VFile into which data is currently being
collected.
Frozen VFile:
*************
A VFile which is no longer used for collecting
data. Only frozen VFiles can be transferred to
specified destinations.
Collection interval:
********************
A collection interval is associated with a VFile.
It is the interval of time over which a VFile
is used to collect data.
This interval of time can be specified by the
application. However there are conditions under
which a collection interval can be shorter than
the specified time. For e.g. a collection
interval is prematurely terminated when the
maximum size of a VFile is exceeded, or when
there is an error condition.
Polling period:
***************
A polling period is associated with a data
group. It determines the frequency at which
the base objects of a data group should
be fetched and stored into a VFile.
Data collection operations:
**************************
A generic term used to refer to operations
that are carried out while collecting data.
These include:
- Periodically creating new VFiles for
collecting data.
- Transferring frozen VFiles either
automatically or on demand.
- Fetching base object values and storing
them into current VFiles, either periodically
or on demand.
- Deleting frozen VFiles, either periodically
or on demand.
ciscoDataCollectionMIB MODULE-IDENTITY LAST-UPDATED "200210300530Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "The MIB module allows a management application to select a set of MIB object instances whose values need to be collected on a periodic basis. The term 'data' in the context of this MIB is used to generically refer to the values of the selected set of object instances. Once the required setup is done, the MIB implementation carries out the following periodic tasks: - collects the required object values into local file-like entities called VFiles (virtual files). - transfers the VFiles to specified locations. - carries out VFile management operations. Some of the key features of this MIB are: a) Allows grouping of MIB objects into groups called data groups. The constraint is that the MIB objects grouped into a data group, need to have the same semantic MIB index. So it is possible to group MIB objects belonging to different MIB tables into a single data group as long as the above constraint is met. For e.g. it is possible to group ifInOctets from ifTable, ifHCInOctets from ifXTable, dot3StatsExcessiveCollisions from dot3StatsTable into a single data group. b) Allows the application to specify a set of instances (of the MIB objects in a data group) whose values need to be collected. c) The required data can be collected for each such data group on a periodic basis into a virtual file (VFile). A VFile is an abstraction of a file. d) The format of the contents of the VFile, can be specified by the application. e) An application can also specify a collection period. A collection period is an interval of time during which data is collected into a VFile. After the collection period ends, the VFile is frozen, and a new VFile is created for storing data. The frozen VFile is then transferred to a specified destination. An application can choose to retain such frozen VFiles on the device for a certain period of time, called the retention period. Data Collection MIB vs Bulkfile MIB *********************************** The data collection MIB can pretty much do what the CISCO-BULK-FILE-MIB (Bulkfile MIB) can do. The 'manual' mode of the Data collection MIB is similar to the way in which the Bulkfile MIB operates. However the data collection MIB is mainly targetted for medium to high-end platforms which have sufficient local storage (volatile or permanent) to store VFiles. Locally storing VFiles, helps minimize loss of data during temporary network outages. If the local store is permament, then the collected data is also available across agent restarts. The data collection MIB has more powerful data selection features than the Bulkfile MIB. It allows grouping of MIB objects from different tables into data groups. It also incorporates a more flexible instance selection mechanism, where the application is not restricted to fetching an entire MIB table. Definitions: ************ Base objects: ************* MIB objects whose values an application needs to collect. Data group: *********** A group of base objects. Can be of 2 types: 'object' and 'table'. An 'object' type data group can consist of only one fully instantiated base object. A 'table' type data group can consist of more than one base objects, each a columnar object in a conceptual table. In addition a 'table' type data group can specify the instances of the base objects whose values need to be collected. In the context of this MIB, collecting data for a data group means fetching the values of the associated base object instances and storing them into VFiles. Virtual File (VFile): ********************* A VFile is a file like entity used to collect data. An agent might choose to implement a VFile as a simple in-memory buffer, or it might choose to use a file in it's filesystem. An application does not really need to know the location of a VFile - the MIB provides mechanisms to transfer the VFile to application specified locations. However if the implementation supports it, the application can specify the location of the VFiles. Current VFile: ************** The VFile into which data is currently being collected. Frozen VFile: ************* A VFile which is no longer used for collecting data. Only frozen VFiles can be transferred to specified destinations. Collection interval: ******************** A collection interval is associated with a VFile. It is the interval of time over which a VFile is used to collect data. This interval of time can be specified by the application. However there are conditions under which a collection interval can be shorter than the specified time. For e.g. a collection interval is prematurely terminated when the maximum size of a VFile is exceeded, or when there is an error condition. Polling period: *************** A polling period is associated with a data group. It determines the frequency at which the base objects of a data group should be fetched and stored into a VFile. Data collection operations: ************************** A generic term used to refer to operations that are carried out while collecting data. These include: - Periodically creating new VFiles for collecting data. - Transferring frozen VFiles either automatically or on demand. - Fetching base object values and storing them into current VFiles, either periodically or on demand. - Deleting frozen VFiles, either periodically or on demand." REVISION "200210300530Z" DESCRIPTION "Initial Version." ::= { ciscoMgmt 312}
ciscoDataCollectionMIB OBJECT IDENTIFIER ::= { ciscoMgmt 312 }
Vendor: Cisco
Module: CISCO-DATA-COLLECTION-MIB
[Automatically extracted from oidview.com]
ciscoDataCollectionMIB MODULE-IDENTITY LAST-UPDATED "200210300530Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "The MIB module allows a management application to select a set of MIB object instances whose values need to be collected on a periodic basis. The term 'data' in the context of this MIB is used to generically refer to the values of the selected set of object instances. Once the required setup is done, the MIB implementation carries out the following periodic tasks: - collects the required object values into local file-like entities called VFiles (virtual files). - transfers the VFiles to specified locations. - carries out VFile management operations. Some of the key features of this MIB are: a) Allows grouping of MIB objects into groups called data groups. The constraint is that the MIB objects grouped into a data group, need to have the same semantic MIB index. So it is possible to group MIB objects belonging to different MIB tables into a single data group as long as the above constraint is met. For e.g. it is possible to group ifInOctets from ifTable, ifHCInOctets from ifXTable, dot3StatsExcessiveCollisions from dot3StatsTable into a single data group. b) Allows the application to specify a set of instances (of the MIB objects in a data group) whose values need to be collected. c) The required data can be collected for each such data group on a periodic basis into a virtual file (VFile). A VFile is an abstraction of a file. d) The format of the contents of the VFile, can be specified by the application. e) An application can also specify a collection period. A collection period is an interval of time during which data is collected into a VFile. After the collection period ends, the VFile is frozen, and a new VFile is created for storing data. The frozen VFile is then transferred to a specified destination. An application can choose to retain such frozen VFiles on the device for a certain period of time, called the retention period. Data Collection MIB vs Bulkfile MIB *********************************** The data collection MIB can pretty much do what the CISCO-BULK-FILE-MIB (Bulkfile MIB) can do. The 'manual' mode of the Data collection MIB is similar to the way in which the Bulkfile MIB operates. However the data collection MIB is mainly targetted for medium to high-end platforms which have sufficient local storage (volatile or permanent) to store VFiles. Locally storing VFiles, helps minimize loss of data during temporary network outages. If the local store is permament, then the collected data is also available across agent restarts. The data collection MIB has more powerful data selection features than the Bulkfile MIB. It allows grouping of MIB objects from different tables into data groups. It also incorporates a more flexible instance selection mechanism, where the application is not restricted to fetching an entire MIB table. Definitions: ************ Base objects: ************* MIB objects whose values an application needs to collect. Data group: *********** A group of base objects. Can be of 2 types: 'object' and 'table'. An 'object' type data group can consist of only one fully instantiated base object. A 'table' type data group can consist of more than one base objects, each a columnar object in a conceptual table. In addition a 'table' type data group can specify the instances of the base objects whose values need to be collected. In the context of this MIB, collecting data for a data group means fetching the values of the associated base object instances and storing them into VFiles. Virtual File (VFile): ********************* A VFile is a file like entity used to collect data. An agent might choose to implement a VFile as a simple in-memory buffer, or it might choose to use a file in it's filesystem. An application does not really need to know the location of a VFile - the MIB provides mechanisms to transfer the VFile to application specified locations. However if the implementation supports it, the application can specify the location of the VFiles. Current VFile: ************** The VFile into which data is currently being collected. Frozen VFile: ************* A VFile which is no longer used for collecting data. Only frozen VFiles can be transferred to specified destinations. Collection interval: ******************** A collection interval is associated with a VFile. It is the interval of time over which a VFile is used to collect data. This interval of time can be specified by the application. However there are conditions under which a collection interval can be shorter than the specified time. For e.g. a collection interval is prematurely terminated when the maximum size of a VFile is exceeded, or when there is an error condition. Polling period: *************** A polling period is associated with a data group. It determines the frequency at which the base objects of a data group should be fetched and stored into a VFile. Data collection operations: ************************** A generic term used to refer to operations that are carried out while collecting data. These include: - Periodically creating new VFiles for collecting data. - Transferring frozen VFiles either automatically or on demand. - Fetching base object values and storing them into current VFiles, either periodically or on demand. - Deleting frozen VFiles, either periodically or on demand." REVISION "200210300530Z" DESCRIPTION "Initial Version." ::= { ciscoMgmt 312}
ciscoDataCollectionMIB MODULE-IDENTITY LAST-UPDATED "200210300530Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "The MIB module allows a management application to select a set of MIB object instances whose values need to be collected on a periodic basis. The term 'data' in the context of this MIB is used to generically refer to the values of the selected set of object instances. Once the required setup is done, the MIB implementation carries out the following periodic tasks: - collects the required object values into local file-like entities called VFiles (virtual files). - transfers the VFiles to specified locations. - carries out VFile management operations. Some of the key features of this MIB are: a) Allows grouping of MIB objects into groups called data groups. The constraint is that the MIB objects grouped into a data group, need to have the same semantic MIB index. So it is possible to group MIB objects belonging to different MIB tables into a single data group as long as the above constraint is met. For e.g. it is possible to group ifInOctets from ifTable, ifHCInOctets from ifXTable, dot3StatsExcessiveCollisions from dot3StatsTable into a single data group. b) Allows the application to specify a set of instances (of the MIB objects in a data group) whose values need to be collected. c) The required data can be collected for each such data group on a periodic basis into a virtual file (VFile). A VFile is an abstraction of a file. d) The format of the contents of the VFile, can be specified by the application. e) An application can also specify a collection period. A collection period is an interval of time during which data is collected into a VFile. After the collection period ends, the VFile is frozen, and a new VFile is created for storing data. The frozen VFile is then transferred to a specified destination. An application can choose to retain such frozen VFiles on the device for a certain period of time, called the retention period. Data Collection MIB vs Bulkfile MIB *********************************** The data collection MIB can pretty much do what the CISCO-BULK-FILE-MIB (Bulkfile MIB) can do. The 'manual' mode of the Data collection MIB is similar to the way in which the Bulkfile MIB operates. However the data collection MIB is mainly targetted for medium to high-end platforms which have sufficient local storage (volatile or permanent) to store VFiles. Locally storing VFiles, helps minimize loss of data during temporary network outages. If the local store is permament, then the collected data is also available across agent restarts. The data collection MIB has more powerful data selection features than the Bulkfile MIB. It allows grouping of MIB objects from different tables into data groups. It also incorporates a more flexible instance selection mechanism, where the application is not restricted to fetching an entire MIB table. Definitions: ************ Base objects: ************* MIB objects whose values an application needs to collect. Data group: *********** A group of base objects. Can be of 2 types: 'object' and 'table'. An 'object' type data group can consist of only one fully instantiated base object. A 'table' type data group can consist of more than one base objects, each a columnar object in a conceptual table. In addition a 'table' type data group can specify the instances of the base objects whose values need to be collected. In the context of this MIB, collecting data for a data group means fetching the values of the associated base object instances and storing them into VFiles. Virtual File (VFile): ********************* A VFile is a file like entity used to collect data. An agent might choose to implement a VFile as a simple in-memory buffer, or it might choose to use a file in it's filesystem. An application does not really need to know the location of a VFile - the MIB provides mechanisms to transfer the VFile to application specified locations. However if the implementation supports it, the application can specify the location of the VFiles. Current VFile: ************** The VFile into which data is currently being collected. Frozen VFile: ************* A VFile which is no longer used for collecting data. Only frozen VFiles can be transferred to specified destinations. Collection interval: ******************** A collection interval is associated with a VFile. It is the interval of time over which a VFile is used to collect data. This interval of time can be specified by the application. However there are conditions under which a collection interval can be shorter than the specified time. For e.g. a collection interval is prematurely terminated when the maximum size of a VFile is exceeded, or when there is an error condition. Polling period: *************** A polling period is associated with a data group. It determines the frequency at which the base objects of a data group should be fetched and stored into a VFile. Data collection operations: ************************** A generic term used to refer to operations that are carried out while collecting data. These include: - Periodically creating new VFiles for collecting data. - Transferring frozen VFiles either automatically or on demand. - Fetching base object values and storing them into current VFiles, either periodically or on demand. - Deleting frozen VFiles, either periodically or on demand." REVISION "200210300530Z" DESCRIPTION "Initial Version." ::= { ciscoMgmt 312}
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.312.0 | ciscoDataCollMIBNotifs | 2 | 2 | None |
| 1.3.6.1.4.1.9.9.312.1 | ciscoDataCollMIBObjects | 3 | 72 | None |
| 1.3.6.1.4.1.9.9.312.2 | ciscoDataCollMIBConformance | 2 | 7 | None |
To many brothers! Only 100 nearest brothers are shown.
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| ... | ||||
| 1.3.6.1.4.1.9.9.262 | ciscoVoaMIB | 2 | 14 | This MIB module defines objects to configure and manage the Variable Optical Attenuator (VOA) modules. VOA modules are typically … |
| 1.3.6.1.4.1.9.9.263 | ciscoIgmpSnoopingMIB | 3 | 286 | The MIB module for IGMP Snooping feature. Internet Group Management Protocol (IGMP) is the protocol used by IPv4 end hosts to ind… |
| 1.3.6.1.4.1.9.9.264 | ciscoOpticalMonitorMIB | 3 | 72 | This MIB module defines objects to monitor optical characteristics and set corresponding thresholds on the optical interfaces in … |
| 1.3.6.1.4.1.9.9.265 | ciscoEntityPfeMib | 3 | 58 | The Packet Forwarding Engine technology are Cisco developed Network Processors, which accelerates certain features in order to pr… |
| 1.3.6.1.4.1.9.9.268 | ciscoWlanVlanMIB | 3 | 41 | This MIB module provides network management support for device VLAN configuration on IEEE 802.11 wireless LAN. ACRONYMS AES Advanced… |
| 1.3.6.1.4.1.9.9.269 | ciscoTBridgeDevIfMIB | 2 | 20 | This MIB module provides network management support for configuration and status information of devices supporting transparent br… |
| 1.3.6.1.4.1.9.9.270 | ciscoSyslogEventExtMIB | 2 | 21 | This MIB module extends the Cisco Syslog MIB and provides network management support to handle and process Syslog messages as devi… |
| 1.3.6.1.4.1.9.9.271 | ciscoL2DevMonMIB | 3 | 24 | This MIB module is for monitoring of active layer 2 devices by hot standby layer 2 devices and the configuration of hot standby s… |
| 1.3.6.1.4.1.9.9.272 | ciscoDot11IfMIB | 3 | 212 | This MIB module provides network management support for Cisco IEEE 802.11 Wireless LAN type device (Access Point) radio interface… |
| 1.3.6.1.4.1.9.9.273 | ciscoDot11AssociationMIB | 2 | 91 | This MIB module provides network management information on IEEE 802.11 wireless device association management and data packet for… |
| 1.3.6.1.4.1.9.9.275 | ciscoBcpMIB | 2 | 25 | This MIB module describes the Managed Objects for of Bridge Control Protocol (RFC2878). This MIB is influenced by RFC1474. |
| 1.3.6.1.4.1.9.9.276 | ciscoIfExtensionMIB | 3 | 143 | A MIB module for extending the IF-MIB (RFC2863) to add objects which provide additional information about interfaces not availabl… |
| 1.3.6.1.4.1.9.9.277 | ciscoDdpIappMIB | 3 | 22 | This MIB module describes the management support for the Inter-Access Point Protocol (IAPP). IAPP is a Cisco propriety Data Deli… |
| 1.3.6.1.4.1.9.9.278 | ciscoIpProtocolMIB | 3 | 63 | The MIB module is for management of information to support packet filtering on IP protocols. The cippfIpProfileTable allows users… |
| 1.3.6.1.4.1.9.9.279 | ciscoAtmQosMIB | 3 | 67 | The MIB is created to provide ATM QoS information in these areas: 1. Traffic shaping on a per-VC basis 2. Traffic shaping on a pe… |
| 1.3.6.1.4.1.9.9.280 | ciscoOutageMIB | 3 | 75 | This MIB module describes, stores, and reports outage related information generated by individual hardware and software component… |
| 1.3.6.1.4.1.9.9.281 | ciscoFabricC12kMIB | 3 | 135 | Cisco Fabric MIB module for c12000 series of routers. This MIB module is used for managing/tracking the c12000 fabric entities an… |
| 1.3.6.1.4.1.9.9.282 | ciscoVsanMIB | 2 | 104 | The MIB module for the management of the Virtual Storage Networks (VSANs) within the frame work of Cisco's VSAN Architecture. T… |
| 1.3.6.1.4.1.9.9.284 | ciscoFcRouteMIB | 2 | 55 | The MIB module for configuring and displaying FC (Fibre Channel) Route Information. |
| 1.3.6.1.4.1.9.9.285 | ciscoPortChannelMIB | 2 | 40 | The MIB module for management of Port Channel ports. In addition to this MIB, CISCO-FC-FE-MIB and interface mib (rfc2863) will al… |
| 1.3.6.1.4.1.9.9.286 | ciscoWwnmgrMIB | 2 | 38 | The World Wide Name (WWN) in the fibre channel networking technology is equivalent to the MAC address in Ethernet. There are six … |
| 1.3.6.1.4.1.9.9.287 | ciscoFspfMIB | 4 | 95 | Fabric Shortest Path First (FSPF) MIB. |
| 1.3.6.1.4.1.9.9.288 | ciscoRadiusMIB | 3 | 91 | MIB module for monitoring and configuring authentication and logging services using RADIUS (Remote Authentication Dial In User Se… |
| 1.3.6.1.4.1.9.9.289 | ciscoFcFeMIB | 2 | 315 | This is the Cisco fibre element management MIB module. It covers: - Cisco extension to the interface MIB ( IF-MIB ) - Contains all… |
| 1.3.6.1.4.1.9.9.290 | ciscoVirtualNwIfMIB | 2 | 22 | The MIB module for management of virtual network interfaces to VSAN and VLAN. |
| 1.3.6.1.4.1.9.9.292 | ciscoRscnMIB | 2 | 67 | The MIB module for the management of the Fibre Channel's Registered State Change Notification (RSCN) functionality, which is spec… |
| 1.3.6.1.4.1.9.9.293 | ciscoNsMIB | 2 | 67 | The MIB module for the management of the Cisco Name Server which realizes the FC-GS3 requirements for Name Server (NS). |
| 1.3.6.1.4.1.9.9.294 | ciscoZsMIB | 2 | 254 | The MIB module for the management of zoning within the framework of Cisco's Zoning Server (ZS) Archi- tecture which realizes the … |
| 1.3.6.1.4.1.9.9.295 | ciscoFcPingMIB | 2 | 37 | The MIB module for the management of the Fibre Channel Ping functionality. |
| 1.3.6.1.4.1.9.9.296 | ciscoFcTraceRouteMIB | 2 | 31 | The MIB module for the management of the Fibre Channel Trace Route functionality. |
| 1.3.6.1.4.1.9.9.297 | ciscoFcsMIB | 2 | 122 | The MIB module for the management of a Fabric Configuration Server (FCS). An FCS is defined by the FC-GS3 standard. This MIB ena… |
| 1.3.6.1.4.1.9.9.299 | ciscoExtScsiMIB | 2 | 68 | The Cisco extension to CISCO-SCSI-MIB which is a copy of the Internet draft, the SCSI-MIB, from the IETF. Glossary of terms used i… |
| 1.3.6.1.4.1.9.9.300 | ciscoCallHomeMIB | 3 | 324 | The MIB module for the management of Call Home feature within the framework of Cisco's Call Home architecture. Customers deployin… |
| 1.3.6.1.4.1.9.9.301 | ciscoSyslogExtMIB | 2 | 44 | MIB module for configuring and monitoring System Log related management parameters as defined by RFC 3164. |
| 1.3.6.1.4.1.9.9.302 | ciscoDmMIB | 2 | 85 | The MIB module for the domain management functionality defined by the Fibre Channel standards (FC-SW2). For the purposes of this … |
| 1.3.6.1.4.1.9.9.305 | ciscoSystemExtMIB | 3 | 112 | MIB module for monitoring High Availability, SNMP SET errors and bandwidths. This mib module also provides the information on co… |
| 1.3.6.1.4.1.9.9.309 | ciscoIPIfMIB | 3 | 40 | The MIB module for configuring IP characteristics of the interfaces of a device. |
| 1.3.6.1.4.1.9.9.311 | ciscoEpmNotificationMIB | 3 | 48 | Notifications directly from hardware and software and processed notifications from various management applications can be furthe… |
| 1.3.6.1.4.1.9.9.313 | ciscoL2ControlMIB | 3 | 113 | The CISCO-L2-CONTROL-MIB is used to control some layer 2 functions, including MAC limit function and unicast flooding. This devi… |
| 1.3.6.1.4.1.9.9.314 | ciscoCasIfExtMIB | 3 | 225 | The MIB module is an extension of CISCO-CAS-IF-MIB. It defines the attributes of a voice interface. |
| 1.3.6.1.4.1.9.9.315 | ciscoPortSecurityMIB | 3 | 89 | The MIB module for managing Cisco Port Security. |
| 1.3.6.1.4.1.9.9.317 | ciscoIscsiGwMIB | 3 | 145 | MIB module for monitoring and configuring iSCSI gateway functions. An iSCSI gateway represents FC (Fibre Channel) targets/initiat… |
| 1.3.6.1.4.1.9.9.318 | ciscoXgcpMIB | 3 | 120 | This MIB is an enhancement for existing XGCP-MIB. xGCP is a set of protocols, for example SGCP (Simple Gateway Control Protocol) … |
| 1.3.6.1.4.1.9.9.319 | ciscoPropAtmIfMIB | 3 | 57 | This MIB is designed for Propietary ATM (propAtm) interfaces. The propAtm interfaces are identified in the ifTable entries with if… |
| 1.3.6.1.4.1.9.9.321 | ciscoMgcMIB | 3 | 43 | This MIB is used to support MGC(call agent) and MGC Group configuration. The MGC or MGC group configuration is performed under a s… |
| 1.3.6.1.4.1.9.9.322 | ccacSysMIB | 2 | 60 | This MIB module provides provisioning and monitoring Call Admission Control (CAC). |
| 1.3.6.1.4.1.9.9.323 | ciscoVoiceAalxProfileMIB | 3 | 87 | This MIB defines the objects specific to voice over ATM or voice over IP. Those objects are related to the following areas: 1. COD… |
| 1.3.6.1.4.1.9.9.324 | ciscoMediaGatewayMIB | 3 | 107 | The MIB module for managing Trunk Media Gateway. A Media Gateway is a network element that provides conversion between the audio … |
| 1.3.6.1.4.1.9.9.325 | ciscoXgcpExtMIB | 2 | 65 | This MIB module is an extension to CISCO-XGCP-MIB. It defines the parameters related to the following aspects in xGCP protocols: *… |
| 1.3.6.1.4.1.9.9.326 | ciscoIpLocalPoolMIB | 3 | 57 | This MIB defines the configuration and monitoring capabilities relating to local IP pools. Local IP pools have the following char… |
| 1.3.6.1.4.1.9.9.329 | ciscoFcipMgmtExtMIB | 3 | 75 | A MIB module for extending the CISCO-FCIP-MGMT-MIB to add objects which provide additional information about FCIP interfaces not … |
| 1.3.6.1.4.1.9.9.330 | ciscoSysInfoLogMIB | 3 | 44 | This MIB provides the configuration of System Information Logging feature, which allows a certain number of commands to be execut… |
| 1.3.6.1.4.1.9.9.331 | ciscoCsgMIB | 3 | 86 | This MIB supports the Cisco Content Services Gateway (CSG) product. It includes five traps and four tables that enable querying C… |
| 1.3.6.1.4.1.9.9.332 | ciscoGsp2MIB | 3 | 91 | The MIB for providing information specified in ITU Q752 Monitoring and Measurements for signalling System No. 7(SS7) Network. This… |
| 1.3.6.1.4.1.9.9.333 | ciscoGactMIB | 3 | 40 | The MIB for providing information specified in ITU Q752 Monitoring and Measurements for Signalling System No. 7(SS7) Network. This… |
| 1.3.6.1.4.1.9.9.334 | ciscoGrtMIB | 3 | 150 | This MIB is for managing information required to route messages transported over Signalling System No. 7 (SS7) Network via Cisco … |
| 1.3.6.1.4.1.9.9.335 | ciscoGsccpMIB | 3 | 293 | The MIB for signalling Connection Control Part(SCCP) messages transported over Signalling System No. 7 (SS7) Network via Cisco IP… |
| 1.3.6.1.4.1.9.9.336 | ciscoGspMIB | 3 | 273 | The MIB for managing Signalling Points and its associated messages transported over Signalling System No. 7 (SS7) Network via Ci… |
| 1.3.6.1.4.1.9.9.339 | ciscoSecureShellMIB | 2 | 40 | MIB module for displaying and configuring accounting and Secure Shell (SSH) related features in a device. SSH is a program to log … |
| 1.3.6.1.4.1.9.9.340 | ciscoLreCpeMIB | 3 | 21 | The MIB module for the Cisco Long Reach Ethernet Customer Premise Equipment device information. *** ABBREVIATIONS, ACRONYMS, AND … |
| 1.3.6.1.4.1.9.9.341 | ciscoCableQosMonitorMIB | 3 | 57 | This is the MIB module for subscriber QoS monitoring for DOCSIS-compliant Cable Modem Termination Systems (CMTS). Several subscrib… |
| 1.3.6.1.4.1.9.9.343 | ciscoAuthorizationStatsMibModule | 2 | 25 | The Cisco User Authorization Statistics MIB models counters and objects that are of management interest. |
| 1.3.6.1.4.1.9.9.344 | ciscoEntityDisplayMIB | 2 | 21 | This MIB module provides information about the status of display devices such as Light Emitting Diodes (LEDs) and alphanumeric di… |
| 1.3.6.1.4.1.9.9.350 | ciscoEntityDiagMIB | 3 | 139 | This MIB module defines the managed objects that describe the online diagnostics capabilities supported by the physical entities … |
| 1.3.6.1.4.1.9.9.351 | ciscoAtmTrunkMIB | 3 | 102 | The MIB for voice and Nx64 over ATM Trunking applications. The following lists the abbreviations used in this MIB: AAL ATM … |
| 1.3.6.1.4.1.9.9.356 | ciscoVoiceToneCadenceMIB | 3 | 30 | The MIB defines the attributes of the programmable tones specified in ITU-T E.180 Supplement 2. Each country has its own regulati… |
| 1.3.6.1.4.1.9.9.358 | ciscoBbsmMIB | 3 | 20 | This mib is designed to send BBSM specific notifications. There are variables that contain detail data that are bind to a notifi… |
| 1.3.6.1.4.1.9.9.359 | ciscoLicenseMIB | 3 | 52 | This MIB module provides objects to view the features and services that are licensed to run on a system (usually a network entity… |
| 1.3.6.1.4.1.9.9.360 | ciscoImageUpgradeMIB | 3 | 101 | This mib provides, objects to upgrade images on modules in the system, objects showing the status of the upgrade operation, and o… |
| 1.3.6.1.4.1.9.9.361 | ciscoCommonRolesMIB | 3 | 40 | MIB module for managing the common roles between access methods like Command Line Interface (CLI), SNMP and XML interfaces. Every … |
| 1.3.6.1.4.1.9.9.362 | ciscoPortStormControlMIB | 3 | 41 | The MIB module for managing Cisco Port Storm Control. |
| ... | ||||