The current status of this file transfer. Is idle when
the row becomes valid. To start the file transfer set this
to go. InQueue signifies that the file transfer is waiting
for resources before it begins but it will begin
automatically. Busy signifies that the file transfer
could not begin due to a resource allocation problem. The
manager must try to restart the file transfer by setting
this entry to go.
Parsed from file fore-filexfr.mib.txt
Company: None
Module: Fore-FileXfr-MIB
The current status of this file transfer. Is idle when
the row becomes valid. To start the file transfer set this
to go. InQueue signifies that the file transfer is waiting
for resources before it begins but it will begin
automatically. Busy signifies that the file transfer
could not begin due to a resource allocation problem. The
manager must try to restart the file transfer by setting
this entry to go.
Parsed from file Fore-FileXfr-MIB.mib
Module: Fore-FileXfr-MIB
Vendor: Fore Systems, Inc.
Module: Fore-FileXfr-MIB
[Automatically extracted from oidview.com]
fXfrStatus OBJECT-TYPE SYNTAX INTEGER { idle(1), go(2), inQueue(3), inProgress(4), succeeded(5), failed(6), busy(7) } MAX-ACCESS read-create STATUS current DESCRIPTION "The current status of this file transfer. Is idle when the row becomes valid. To start the file transfer set this to go. InQueue signifies that the file transfer is waiting for resources before it begins but it will begin automatically. Busy signifies that the file transfer could not begin due to a resource allocation problem. The manager must try to restart the file transfer by setting this entry to go." ::= { fXfrEntry 6 }
fXfrStatus OBJECT-TYPE SYNTAX INTEGER { idle(1), go(2), inQueue(3), inProgress(4), succeeded(5), failed(6), busy(7) } MAX-ACCESS read-create STATUS current DESCRIPTION "The current status of this file transfer. Is idle when the row becomes valid. To start the file transfer set this to go. InQueue signifies that the file transfer is waiting for resources before it begins but it will begin automatically. Busy signifies that the file transfer could not begin due to a resource allocation problem. The manager must try to restart the file transfer by setting this entry to go." ::= { fXfrEntry 6 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.326.1.6.2.2.1.1 | fXfrIndex | 0 | 0 | The index of the file transfer. |
| 1.3.6.1.4.1.326.1.6.2.2.1.2 | fXfrRemoteFileUrl | 0 | 0 | This is the URL of the file to operate on. The URL is taken from the snmp agents point of view. The URL is in the form: |
| 1.3.6.1.4.1.326.1.6.2.2.1.3 | fXfrLocalFile | 0 | 0 | The name of the local file to use in the GET/PUT operations. This can either be a full pathname or a device specific description… |
| 1.3.6.1.4.1.326.1.6.2.2.1.4 | fXfrDirection | 0 | 0 | Indication of the file transfer operation. A 'get' will retrieve the file from the machine specified in fXfrRemoteFileUrl. A 'pu… |
| 1.3.6.1.4.1.326.1.6.2.2.1.5 | fXfrEntryStatus | 0 | 0 | The status of this table entry. |
| 1.3.6.1.4.1.326.1.6.2.2.1.7 | fXfrStatusText | 0 | 0 | A message describing the status of this file transfer. This must exists when the status is succeeded or failed. This can optional… |
| 1.3.6.1.4.1.326.1.6.2.2.1.8 | fXfrOwnerIpAddress | 0 | 0 | Ip address of the entity that requested this file transfer. |
| 1.3.6.1.4.1.326.1.6.2.2.1.9 | fXfrOwnerSignature | 0 | 0 | Signature of the owner of this file transfer. This is supplied by the management station. |
| 1.3.6.1.4.1.326.1.6.2.2.1.10 | fXfrTransferType | 0 | 0 | The type of transfer requested. A binary transfer will perform no translations while an ascii transfer will set the representati… |
| 1.3.6.1.4.1.326.1.6.2.2.1.11 | fXfrUserId | 0 | 0 | The login name on the remote host for FTP. |
| 1.3.6.1.4.1.326.1.6.2.2.1.12 | fXfrPassword | 0 | 0 | The password associated with the login name on the remote host for FTP. Note this object is write-only and reading it will result … |