If set to standardBER(1), the ASN.1/BER format is identical
to SNMP variable bindings, that is, each object has a full
OID and a fully tagged value. The file content is similar to
what would be obtained with a Get request.
If set to ascii(2), the format is human-readable ascii with a
lines in the form:
# table-name@timestamp column-1 column-2 ... column-n
instance-1 value-1 value-2 ...
instance-2 value-3 value-4 ...
...
where:
table-name is the ascii representation of the MIB module
table name in usual dotted notation.
timestamp is the value of sysUptime on the agent when the
snapshot of the data slice was taken.
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.
For example, an ifTable data slice file fragment might be:
# interfaces.ifTable@28711187 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(3), the data will be saved in XML tagged
format.
Parsed from file BULK-DATA-MIB-eos-00.txt
Company: ietf_drafts
Module: BULK-DATA-MIB
xferFileEncoding OBJECT-TYPE SYNTAX INTEGER { standardBER(1), ascii(2), xml(3) } MAX-ACCESS read-create STATUS current DESCRIPTION "If set to standardBER(1), the ASN.1/BER format is identical to SNMP variable bindings, that is, each object has a full OID and a fully tagged value. The file content is similar to what would be obtained with a Get request. If set to ascii(2), the format is human-readable ascii with a lines in the form: # table-name@timestamp column-1 column-2 ... column-n instance-1 value-1 value-2 ... instance-2 value-3 value-4 ... ... where: table-name is the ascii representation of the MIB module table name in usual dotted notation. timestamp is the value of sysUptime on the agent when the snapshot of the data slice was taken. 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. For example, an ifTable data slice file fragment might be: # interfaces.ifTable@28711187 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(3), the data will be saved in XML tagged format." ::= { xferEntry 4 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.3.999.2.1.1.1 | xferIndex | 0 | 0 | An integer to uniquely identify the data slice that is to be transferred to the fileserver. This refers to an entry in the Slice… |
| 1.3.6.1.3.999.2.1.1.2 | xferSliceIndex | 0 | 0 | An integer to uniquely identify the data slice to be transferred to the fileserver. |
| 1.3.6.1.3.999.2.1.1.3 | xferProtocol | 0 | 0 | This defines the standard protocol that is used to upload the data slice to the fileserver. The agent is the client in this tran… |
| 1.3.6.1.3.999.2.1.1.5 | xferFileCompression | 0 | 0 | If set to none(1), no file compression will be applied before the data slice is uploaded to the fileserver. If set to bzip(2), th… |
| 1.3.6.1.3.999.2.1.1.6 | xferFileServerManditory | 0 | 0 | The primary target upload hostname or address to send the bulk file. Successful upload to this host is required before the local… |
| 1.3.6.1.3.999.2.1.1.7 | xferFileServerOptional | 0 | 0 | The secondary upload hostname or address to send the bulk file. Successful upload to this host is optional; an attempt is made t… |
| 1.3.6.1.3.999.2.1.1.8 | xferFileWriteControl | 0 | 0 | This defines the action to take when uploading bulk data to a fileserver. If set to failIfExists(1) and a filename described by … |
| 1.3.6.1.3.999.2.1.1.9 | xferFilePath | 0 | 0 | The remote directory path where the file is to be saved on the fileserver. |
| 1.3.6.1.3.999.2.1.1.10 | xferFileName | 0 | 0 | The remote file name of the file that is to be saved on the fileserver. For fileservers that support versioning, the appropriate… |
| 1.3.6.1.3.999.2.1.1.11 | xferAuthUsername | 0 | 0 | The user name to use at the FTP server. |
| 1.3.6.1.3.999.2.1.1.12 | xferAuthPassword | 0 | 0 | The password to use at the FTP server. |
| 1.3.6.1.3.999.2.1.1.13 | xferState | 0 | 0 | The file state: running data is being written to the file ready the file is ready to be read emptied an ephemeral file … |
| 1.3.6.1.3.999.2.1.1.14 | xferStartTime | 0 | 0 | The value of sysUptime on the agent when the file transfer was initiated. This variable is only valid upon the successful complet… |
| 1.3.6.1.3.999.2.1.1.15 | xferCompletionTime | 0 | 0 | The value of sysUptime on the agent when the file transfer was completed. This variable is only valid upon the successful comple… |
| 1.3.6.1.3.999.2.1.1.16 | xferFileSize | 0 | 0 | The actual size of the file (after optional file compression was applied) that was uploaded to the fileserver. The size is measu… |
| 1.3.6.1.3.999.2.1.1.17 | xferEntryStatus | 0 | 0 | The control that allows creation, modification, and deletion of entries. Setting this variable to createAndGo or active will init… |