| OID symbolic | OID numeric | Type | Access | Description |
|---|
| bulkDataMIB | 1.3.6.1.3.999 | | | The MIB module for defining Bulk Data objects along with
the Bulk Data file format, Upload Fileserver and Data Slice. |
| bulkDataAgentCapabilities | 1.3.6.1.3.999.1 | | | |
| INT acFileEncoding | 1.3.6.1.3.999.1.1 | INTEGER | read-only | This describes the agent's capability in term of which
file encoding styles it supports. |
| INT acFileCompression | 1.3.6.1.3.999.1.2 | INTEGER | read-only | This describes the agent's capability in term of which
file compression styles it supports. |
| INT acXferProtocol | 1.3.6.1.3.999.1.3 | INTEGER | read-only | This describes the agent's capability in term of which
file transfer protocols it supports. |
| bulkDataObjects | 1.3.6.1.3.999.2 | | | |
| sliceTable | 1.3.6.1.3.999.2.1 | | not-accessible | This table describes a bulk data slice that is a user-
defined subset of the current running agent's MIB data.
Virtual tables are built by specifying a sequence of
columnar Object Identifiers from real mib tables. |
| sliceEntry | 1.3.6.1.3.999.2.1.1 | | not-accessible | The data slice entry. |
| U32 sliceIndex | 1.3.6.1.3.999.2.1.1.1 | Unsigned32 | not-accessible | An arbitrary integer to uniquely identify this entry. To
create an entry a management application should pick a
random number. |
| U32 sliceSubId | 1.3.6.1.3.999.2.1.1.2 | Unsigned32 | not-accessible | A sequential sub-index to identify a component of a slice
entry. |
| OID sliceColumnOID | 1.3.6.1.3.999.2.1.1.3 | OBJECT IDENTIFIER | read-create | An Object Identifier, which must refer to a column of a
conceptual table. A slice is defined to be a series of
columns OIDs that exist in various tables which are
accessible via the local agent. |
| STR sliceSnmpContext | 1.3.6.1.3.999.2.1.1.4 | DisplayString | read-create | In mib groups that are not inherently instancable, an snmp
manager context is used to multiply access the separate
instances (eg, the bridge mib). |
| STR sliceColumnDisplayHint | 1.3.6.1.3.999.2.1.1.5 | DisplayString | read-create | This defines how the data file will render this OID's value
in the snapshot data file.
The following subset of the C printf-style formatting
macros is supported:
%s - ascii string field
%d - numeric field |
| STR sliceAdminString | 1.3.6.1.3.999.2.1.1.6 | DisplayString | read-create | Used for administrative purposes. Usually meaningful only
to the controlling NMS. |
| ROW sliceEntryStatus | 1.3.6.1.3.999.2.1.1.7 | RowStatus | read-create | The control variable that allows creation, modification,
and deletion of entries in this table. |
| xferTable | 1.3.6.1.3.999.2.2 | | not-accessible | This table describes a bulk data slice file transfer
information. It is referenced when a snapshot is being
requested. |
| xferEntry | 1.3.6.1.3.999.2.2.1 | | not-accessible | The snapshot file transfer request table entry. |
| U32 xferIndex | 1.3.6.1.3.999.2.2.1.1 | Unsigned32 | not-accessible | An integer to uniquely identify a transfer destination set. |
| U32 xferSubId | 1.3.6.1.3.999.2.2.1.2 | Unsigned32 | not-accessible | Sub index that allows several transfer entries to be
grouped together to form a transfer set. |
| IPt xferHostIpType | 1.3.6.1.3.999.2.2.1.3 | InetAddressType | read-create | Used along with xferHostIpAddr to define the IP address
version. |
| IP xferHostIpAddr | 1.3.6.1.3.999.2.2.1.4 | InetAddress | read-create | The IP address of the fileserver where the snapshot is to
be transferred. |
| INT xferProtocol | 1.3.6.1.3.999.2.2.1.5 | INTEGER | read-create | This defines the standard protocol that is used to upload
the snapshot to the fileserver. The agent is the client in
this transaction; ie, it initiates the upload to the
fileserver.
When the snapshot is being kept on the local system, cp(1)
is to be specified. For remote file transfers, ftp(2) or
scp(3) should be specified. |
| INT xferWriteControl | 1.3.6.1.3.999.2.2.1.6 | INTEGER | read-create | This defines the action to take when uploading bulk
data to a fileserver. If set to failIfExists(1) and
a file already exists on the fileserver, the upload will
fail and the existing file on the server will not be
overwritten. If set to overwrite(2), a file will be
uploaded and saved under the specified path and name
even if one by that composite name already exists;
if none exists by that composite name, a new file
will be created. |
| STR xferFilePath | 1.3.6.1.3.999.2.2.1.7 | DisplayString | read-create | The remote directory path where the file is to be saved on
the fileserver. |
| STR xferAuthUsername | 1.3.6.1.3.999.2.2.1.8 | DisplayString | read-create | The user name to use when authenticating with the remote
fileserver. |
| STR xferAuthPassword | 1.3.6.1.3.999.2.2.1.9 | DisplayString | read-create | The password to use when authenticating with the remote
fileserver. |
| STR xferAdminString | 1.3.6.1.3.999.2.2.1.10 | DisplayString | read-create | Used for administrative purposes. Usually meaningful only
to the controlling NMS. |
| ROW xferEntryStatus | 1.3.6.1.3.999.2.2.1.11 | RowStatus | read-create | The control that allows creation, modification, and deletion
of entries.
Setting this variable to createAndGo(4) or active(1) will
case a row creation to be performed in this table. Note
that no actual file transfer occurs until a snapshot table
entry is created.
Setting this variable to delete will delete this row entry. |
| snapshotTable | 1.3.6.1.3.999.2.3 | | not-accessible | This table describes a bulk data slice snapshot request.
The agent is expected to capture the values of the slice
(atomically, if possible) and save them in a file on the
local system when a row in this table is created and set to
createAndGo(4) or active(1). |
| snapshotEntry | 1.3.6.1.3.999.2.3.1 | | not-accessible | The snapshot request table entry. |
| U32 snapshotIndex | 1.3.6.1.3.999.2.3.1.1 | Unsigned32 | not-accessible | An integer to uniquely identify the data slice that is to
be transferred to the fileserver. This refers to an entry
in the SliceTable. |
| U32 snapshotSliceIndex | 1.3.6.1.3.999.2.3.1.2 | Unsigned32 | not-accessible | An integer to uniquely identify the data slice to saved on
the local system. |
| U32 snapshotXferId | 1.3.6.1.3.999.2.3.1.3 | Unsigned32 | not-accessible | An instance in the xfer table that describes where and how
to copy the bulk data snapshot to a fileserver. |
| STR snapshotSnapFileName | 1.3.6.1.3.999.2.3.1.4 | DisplayString | read-create | The bulk data snapshot is saved under this filename. |
| INT snapshotFileEncoding | 1.3.6.1.3.999.2.3.1.5 | INTEGER | read-create | If set to ascii(1), the format is human-readable ascii with
a lines in the form:
# timestampStart timestampCompletion col-1 col-2 ... col-n
instance-1 value-1 value-2 ...
instance-2 value-3 value-4 ...
...
where:
timestampStart and timestampCompletion are the values of
sysUptime on the agent when the snapshot of the data slice
was initiated and completed (with or without errors).
column-1 thru column-n are the human-readable MIB module
column names that are included in this data slice.
instance-1 (etc) are human-readable MIB module instance
names in usual dotted notation.
value-1 (etc) are human-readable ascii representations
of the actual values of the data cells. This is in
DisplayString format regardless of the native data type of
the column.
It is implementation-specific if the column name is stored
in dotted-OID format (.1.3.6...) or in symbolic format
(ifInOctets).
For example, an ifTable data slice file fragment might be:
# 28711187 28711190 ifDescr ifType ifInOctets ifOutOctets
1 lo0 softwareLoopback 54550782 54552115
2 eth0 ethernet-csmacd 372380346 2746062289
3 eth0.0 ethernet-csmacd 4002949 126167
If set to xml(2), the data will be saved in XML tagged
format. |
| INT snapshotFileCompression | 1.3.6.1.3.999.2.3.1.6 | INTEGER | read-create | If set to noCompression(1), no file compression will be
applied before the data slice is transferred to the
fileserver.
If set to bzip(2), the standard bzip compression algorithm
will be applied to the data slice before the file is
uploaded to the fileserver.
If set to gzip(3), the standard GNU gzip compression
algorithm will be applied to the data slice before the file
is uploaded to the fileserver. |
| TIM snapshotStartTime | 1.3.6.1.3.999.2.3.1.7 | TimeStamp | read-only | The value of sysUptime on the agent when the snapshot was
initiated. |
| TIM snapshotCompletionTime | 1.3.6.1.3.999.2.3.1.8 | TimeStamp | read-only | The value of sysUptime on the agent when the snapshot was
completed (with or without an error). |
| U32 snapshotFileSize | 1.3.6.1.3.999.2.3.1.9 | Unsigned32 | read-only | The actual size of the file (after optional file
compression was applied) at the completion of the snapshot.
The size is measured in bytes. This variable is only valid
upon the successful completion of a slice snapshot. |
| INT snapshotState | 1.3.6.1.3.999.2.3.1.10 | INTEGER | read-only | The file state:
running data is being written to the file
ready the file is ready to be sent or retrieved
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
aborted terminated by operator command
Only the 'ready' state implies that snapshot has successfully
completed. |
| STR snapshotAdminString | 1.3.6.1.3.999.2.3.1.11 | DisplayString | read-create | Used for administrative purposes. Usually meaningful only
to the controlling NMS. |
| ROW snapshotEntryStatus | 1.3.6.1.3.999.2.3.1.12 | RowStatus | read-create | The control that allows creation, modification, and deletion
of entries.
Setting this variable to createAndGo(4) or active(1) will
initiate a snapshot of a slice entry to the local system
and optionally initiate a remote file copy.
Setting this variable to delete() will delete this row entry
and delete the corresponding data file on the local system.
Note that in practice, this variable could be set by an
operator via the agent's craft interface, remotely via an
NMS using SNMP or locally within the agent via automatic
means, such as described in the DISMAN-SCHEDULE-MIB. |
| xferCtlTable | 1.3.6.1.3.999.2.4 | | not-accessible | This table contains individual (fileserver host) transfer
requests. There will be an entry in this table For each
filserver that is to receive a snapshot slice. The current
transfer status can be monitored as well as controlled
(aborted, retried). |
| xferCtlEntry | 1.3.6.1.3.999.2.4.1 | | not-accessible | The snapshot file transfer request table entry. |
| U32 xferCtlIndex | 1.3.6.1.3.999.2.4.1.1 | Unsigned32 | not-accessible | An integer to uniquely identify a transfer destination set. |
| TIM xferCtlStartTime | 1.3.6.1.3.999.2.4.1.2 | TimeStamp | read-only | The value of sysUptime on the agent when the file transfer
was initiated. |
| TIM xferCtlCompletionTime | 1.3.6.1.3.999.2.4.1.3 | TimeStamp | read-only | The value of sysUptime on the agent when the file transfer
was completed (with or without an error). |
| U32 xferCtlPercentXferred | 1.3.6.1.3.999.2.4.1.4 | Unsigned32 | read-only | The amount of the snapshot file that has been transferred
to the fileserver, in percent of completion (0..100). |
| INT xferCtlStatus | 1.3.6.1.3.999.2.4.1.5 | INTEGER | read-write | This allows individual file transfer requests to be
controlled.
inProgress(1) is returned if a file transfer is currently
being performed by the local system. This is a read-only
value.
complete(2) is returned upon successful file transfer.
This is a read-only value.
noSpace(3), badName(4), writeErr(5), badLogin(6) are error
status values that describe the error conditions of
insufficient fileserver space to create the file, invalid
filename, misc write error or authentication error on the
fileserver. These values are readable but not writable.
abortXfer(7), retryXfer(8) are writable values and allow
remote control of currently pending file transfer requests.
deleteRow(9) is a writable value that causes a row deletion
from this table. In addition, any pending operations on
this row are aborted. |
| bulkDataTraps | 1.3.6.1.3.999.3 | | | |
| NTF bulkDataXfer | 1.3.6.1.3.999.3.1 | | | Asynchronous events that are sent when a file transfer
request changes state. |
| bulkMIBConformance | 1.3.6.1.3.999.4 | | | |
| bulkMIBCompliances | 1.3.6.1.3.999.4.1 | | | |
| bulkMIBCompliance | 1.3.6.1.3.999.4.1.1 | | | The compliance statement for entities which implement
the Bulk Data MIB. Implementation of this MIB
is based on individual product needs. |
| bulkMIBGroups | 1.3.6.1.3.999.4.2 | | | |
| bulkCapabilitiesGroup | 1.3.6.1.3.999.4.2.1 | | | Bulk Data agent capabilities management. |
| bulkSliceGroup | 1.3.6.1.3.999.4.2.2 | | | Bulk Data slice management. |
| bulkFileTransferGroup | 1.3.6.1.3.999.4.2.3 | | | Bulk File transfer management. |
| bulkSnapshotGroup | 1.3.6.1.3.999.4.2.4 | | | Bulk data snapshot management. |
| bulkXferCtlGroup | 1.3.6.1.3.999.4.2.5 | | | Bulk Data transfer control management. |
| bulkTrapGroup | 1.3.6.1.3.999.4.2.6 | | | Bulk Data trap management. |
