| cbfDefineMaxFiles |
.1.3.6.1.4.1.9.9.81.1.1.1 |
|
The maximum number of file definitions this system
can hold in cbfDefineFileTable. A value of 0 indicates no
configured limit.
This object may be read-only on some systems.
Changing this number does not disturb existing entries.
|
| cbfDefineFiles |
.1.3.6.1.4.1.9.9.81.1.1.2 |
|
The current number of file definitions in cbfDefineFileTable.
|
| cbfDefineHighFiles |
.1.3.6.1.4.1.9.9.81.1.1.3 |
|
The maximum value of cbfDefineFiles since system
initialization.
|
| cbfDefineFilesRefused |
.1.3.6.1.4.1.9.9.81.1.1.4 |
|
The number of attempts to create a file definition that
failed due to exceeding cbfDefineMaxFiles.
|
| cbfDefineMaxObjects |
.1.3.6.1.4.1.9.9.81.1.1.5 |
|
The maximum total number of object selections to go with
file definitions this system, that is, the total number
of objects this system can hold in cbfDefineObjectTable. A
value of 0 indicates no configured limit.
This object may be read-only on some systems.
Changing this number does not disturb existing entries.
|
| cbfDefineObjects |
.1.3.6.1.4.1.9.9.81.1.1.6 |
|
The current number of object selections in
cbfDefineObjectTable.
|
| cbfDefineHighObjects |
.1.3.6.1.4.1.9.9.81.1.1.7 |
|
The maximum value of cbfDefineObjects since system
initialization.
|
| cbfDefineObjectsRefused |
.1.3.6.1.4.1.9.9.81.1.1.8 |
|
The number of attempts to create an object selection that
failed due to exceeding cbfDefineMaxObjects.
|
| cbfDefineFileEntry |
.1.3.6.1.4.1.9.9.81.1.1.9.1 |
|
Information for creation of a bulk file.
To creat a bulk file an application creates an entry in this
table and corresponding entries in cbfDefineObjectTable.
When the entry in this table and the corresponding
entries in cbfDefineObjectTable are 'active' the
appliction uses cbfDefineFileNow to create the file
and a corresponding entry in cbfStatusFileTable.
Deleting an entry in cbfDefineFileTable deletes all
corresponding entries in cbfDefineObjectTable and
cbfStatusFileTable.
An entry may not be modified or deleted while its
cbfDefineFileNow has the value 'running'.
|
| cbfDefineObjectEntry |
.1.3.6.1.4.1.9.9.81.1.1.10.1 |
|
Information about one object for a particular file.
An application uses cbfDefineObjectEntryStatus to create entries
in this table in correspondence with entries in
cbfDefineFileTable, which must be created first.
Entries in this table may not be changed, created or deleted
while the corresponding value of cbfDefineFileNow is 'running'.
|
| cbfStatusMaxFiles |
.1.3.6.1.4.1.9.9.81.1.2.1 |
|
The maximum number of file statuses this system
can hold in cbfStatusFileTable. A value of 0 indicates no
configured limit.
This object may be read-only on some systems.
Changing this number deletes the oldest finished entries until
the new limit is satisfied.
|
| cbfStatusFiles |
.1.3.6.1.4.1.9.9.81.1.2.2 |
|
The current number of file statuses in cbfStatusFileTable.
|
| cbfStatusHighFiles |
.1.3.6.1.4.1.9.9.81.1.2.3 |
|
The maximum value of cbfStatusFiles since system
initialization.
|
| cbfStatusFilesBumped |
.1.3.6.1.4.1.9.9.81.1.2.4 |
|
The number times the oldest entry was deleted due to exceeding
cbfStatusMaxFiles.
|
| cbfStatusFileEntry |
.1.3.6.1.4.1.9.9.81.1.2.5.1 |
|
Status for a particular file.
An entry exists in this table for each time cbfDefineFileNow
has been set to 'create' and the corresponding entry here
has not been explicitly deleted by the application or bumped
to make room for a new entry.
Deleting an entry with cbfStatusFileState 'running' aborts
the file creation attempt.
It is implementation and file-system specific whether deleting
the entry also deletes the file.
|
| cbfDefineFileIndex |
.1.3.6.1.4.1.9.9.81.1.1.9.1.1 |
|
An arbitrary integer to uniquely identify this entry. To
create an entry a management application should pick a
random number.
|
| cbfDefineFileName |
.1.3.6.1.4.1.9.9.81.1.1.9.1.2 |
|
The file name which is to be created.
Explicit device or path choices in the value of this object
override cbfDefineFileStorage.
|
| cbfDefineFileStorage |
.1.3.6.1.4.1.9.9.81.1.1.9.1.3 |
|
The type of file storage to use:
ephemeral data exists in small amounts until read
volatile data exists in volatile memory
permanent data survives reboot
An ephemeral file is suitable to be read only one time.
Note that this value is taken as advisory and may be overridden
by explicit device or path choices in cbfDefineFile.
A given system may support any or all of these.
|
| cbfDefineFileFormat |
.1.3.6.1.4.1.9.9.81.1.1.9.1.4 |
|
The format of the data in the file:
StandardBER standard SNMP ASN.1 BER
bulkBinary a binary format specified with this MIB
bulkASCII a human-readable form of bulkBinary
variantBERWithCksum ASN.1 BER encoding with checksum
variantBinWithCksum a binary format with checksum
A given system may support any or all of these.
|
| cbfDefineFileNow |
.1.3.6.1.4.1.9.9.81.1.1.9.1.5 |
|
The control to cause file creation. The only values that can
be set are 'create' and 'forcedCreate'. These can be set only
when the value is 'ready'. Setting it to 'create' begins a
file creation and creates a corresponding entry in
cbfStatusFileTable. The system may choose to use an already
existing copy of the file instead of creating a new one. This
may happen if there has been no configuration change on the
system and a request to recreate the file is received.
Setting this object to 'forcedCreate' forces the system to
create a new copy of the file.
The value is 'notActve' as long as cbfDefineFileEntryStatus or
any corresponding cbfDefineObjectEntryStatus is not active.
When cbfDefineFileEntryStatus becomes active and all
corresponding cbfDefineObjectEntryStatuses are active this
object automatically goes to 'ready'.
|
| cbfDefineFileEntryStatus |
.1.3.6.1.4.1.9.9.81.1.1.9.1.6 |
|
The control that allows creation, modification, and deletion
of entries. For detailed rules see the DESCRIPTION for
cbfDefineFileEntry.
|
| cbfDefineFileNotifyOnCompletion |
.1.3.6.1.4.1.9.9.81.1.1.9.1.7 |
|
This controls the cbfDefineFileCompletion notification.
If true, cbfDefineFileCompletion notification
will be generated. It is the responsibility of the
management entity to ensure that the SNMP administrative
model is configured in such a way as to allow the
notification to be delivered.
|
| cbfDefineObjectIndex |
.1.3.6.1.4.1.9.9.81.1.1.10.1.1 |
|
An arbitrary integer to uniquely identify this entry.
The numeric order of the entries controls the order of
the objects in the file.
|
| cbfDefineObjectClass |
.1.3.6.1.4.1.9.9.81.1.1.10.1.2 |
|
The meaning of each object class is given below:
object a single MIB object is retrieved.
lexicalTable an entire table or partial table
is retrieved in lexical order of rows.
leastCpuTable an entire table is retrieved with
lowest CPU utilization.
Lexical ordering of rows may not be
maintained and is dependent upon
individual MIB implementation.
|
| cbfDefineObjectID |
.1.3.6.1.4.1.9.9.81.1.1.10.1.3 |
|
The object identifier of a MIB object to be included in
the file.
If cbfDefineObjectClass is 'object' this must be a full OID,
including all instance information.
If cbfDefineObjectClass is 'lexicalTable' or 'leastCpuTable'
this must be the OID of the table-defining SEQUENCE OF
registration point.
|
| cbfDefineObjectEntryStatus |
.1.3.6.1.4.1.9.9.81.1.1.10.1.4 |
|
The control that allows creation, modification, and deletion
of entries. For detailed rules see the DESCRIPTION for
cbfDefineObjectEntry.
|
| cbfDefineObjectTableInstance |
.1.3.6.1.4.1.9.9.81.1.1.10.1.5 |
|
If cbfDefineObjectClass is 'lexicalTable', then this object
represents the starting instance in the cbfDefineObjectID
table. The file created will have entries starting from
the lexicographically next instance of the OID represented
by this object.
For Eg:
-------
Let us assume we are polling ifTable and we
have information till the second row(ifIndex.2). Now
we may be interested in 10 rows lexically following
the second row.
So, we set cbfDefineObjectTableInstance as ifIndex.2
and cbfDefineObjectNumEntries as 10.
We will get information for the next 10 rows or
if there are less than 10 populated rows, we will
receive information till the end of the table is
reached.
The default value for this object is zeroDotZero.
If this object has the value of zeroDotZero and
cbfDefineObjectNumEntries has value 0, then the whole
table(represented by cbfDefineObjectID) is retrieved.
If this object has the value of zeroDotZero,
cbfDefineObjectNumEntries has value n (>0) and there are
m(>0) entries in the table(represented by cbfDefineObjectID)
then the first n entries in the table are retrieved if n < m.
If n >= m, then the whole table is retrieved.
When the value of cbfDefineObjectNumEntries is 0,
it means all the entries in the table(represented
by cbfDefineObjectID) which lexicographically follow
cbfDefineObjectTableInstance are retrieved.
This object is irrelevent if cbfDefineObjectClass is not
'lexicalTable'.
|
| cbfDefineObjectNumEntries |
.1.3.6.1.4.1.9.9.81.1.1.10.1.6 |
|
If cbfDefineObjectClass is 'lexicalTable', then this object
represents the maximum number of entries which will be
populated in the file starting from the lexicographically
next instance of the OID represented by
cbfDefineObjectTableInstance.
This object is irrelevent if cbfDefineObjectClass is not
'lexicalTable'.
Refer to the description of cbfDefineObjectTableInstance for
examples and different scenarios relating to this object.
|
| cbfDefineObjectLastPolledInst |
.1.3.6.1.4.1.9.9.81.1.1.10.1.7 |
|
This object represents the last polled instance in the
table.
The value represented by this object will be relevent only
if the corresponding cbfStatusFileState is emptied(3) for
ephemeral files or ready(2) for volatile or permanent files.
A value of zeroDotZero indicates an absence of last polled
object.
An NMS can use the value of this object and populate the
cbfDefineObjectTableInstance to retrieve a contiguous set
of rows in a table.
|
| cbfStatusFileIndex |
.1.3.6.1.4.1.9.9.81.1.2.5.1.1 |
|
An arbitrary integer to uniquely identify this file.
The numeric order of the entries implies the creation
order of the files.
|
| cbfStatusFileState |
.1.3.6.1.4.1.9.9.81.1.2.5.1.2 |
|
The file state:
running data is being written to the file
ready the file is ready to be read
emptied an ephemeral file was successfully consumed
noSpace no data due to insufficient file space
badName no data due to a name or path problem
writeErr no data due to fatal file write error
noMem no data due to insufficient dynamic memory
buffErr implementation buffer too small
aborted short terminated by operator command
Only the 'ready' state implies that the file is available
for transfer.
The disposition of files after an error is implementation
and file-syste specific.
|
| cbfStatusFileCompletionTime |
.1.3.6.1.4.1.9.9.81.1.2.5.1.3 |
|
The value of sysUpTime when the creation attempt completed.
A value of 0 indicates not complete. For ephemeral files this
is the time when cbfStatusFileState goes to 'emptied'. For
others this is the time when the state leaves 'running'.
|
| cbfStatusFileEntryStatus |
.1.3.6.1.4.1.9.9.81.1.2.5.1.4 |
|
The control that allows deletion of entries. For detailed rules
see the DESCRIPTION for cbfStatusFileEntry.
This object may not be set to any value other than 'destroy'.
|
