ZHONE-COM-IP-FTP-CLIENT-MIB: View SNMP OID List / Download MIB

FTP Client Objects.

The next available index to be used for an FTP request. The manager performs a get on this variable to determine which index to utilize for its request. The agent controls this value and tracks which are in use and how many current requests are outstanding. An okay return is indicated by a value of 1-20 for which the manager can use for creating an ftp row/request. A value of 0 indicates there are no entries available (20 ftp requests are currently in progress. When this occurs, the ftpClientIndexFailures is incremented.

The highest number of requests that the agent has processed at one time. Because it is up to the manager to delete a ftp request, even after completion, this number may be artificially high as it only tracks the number of index values in use.

The number of times a manager tried to initiate an ftp request (get of ftpClientNextIndex), and there were not available indexes. In this case, the agent deletes the oldest completed ftp request and increments this object by 1.

The number of times a get was performed on the ftpClientNextIndex field and all indexes were in use (all had ftp requests in progress)

The table of ftp requests. An FTP request is initiated by a manager by setting the required values and setting the ftpClientRequestRowStatus to 'createAndGo'. An FTP request is stopped and deleted by setting the ftpClientRequestRowStatus to 'destroy'. The manager obtains the index to utilize by getting the next available index (get to ftpClientNextIndex).

Each row of this table represents an ftp request that may either be in progress or completed (see ftpClientRequestResult). The manager both creates and deletes entries utilizing the ftpClientRequestRowStatus field. Entries are not deleted by the agent unless a new request is made (get to ftpClientNextIndex) and all indexes are utilized. In this case, the oldest completed request is auto-deleted and then made available for the manager.

The index of this FTP request in this table. There is a maximum number of 20 outstanding requests in the system.

The operation requested by the manager with the default being a 'put' of a file in binary mode. These are the normal ftp operations allowed in being able to transfer a file in either binary or ASCII modes. Enumeration: 'putBinary': 1, 'getBinary': 3, 'putAscii': 2, 'getAscii': 4.

The local file name to be used in the ftp operation. No default value is specified and this field must be specified on a row creation.

The remote filename used in the ftp operation. This value must be specified when the row is created and there is no default value.

Either the ip address or name specifying the location of the FTP server. This value must be specified on the row create and there is no default value.

The user name to be used during the authentication process with the FTP server. This field must be specified on the row create and there is no default value.

The password associated with this user named which is used during the authentication process with the FTP server. This value must be present during the row create and there is no default value. When this variable is read (get), a null string is always returned.

The results of the FTP operation. The possible values are: inProgress - currently executing the request success - file has been transferred stoppedByUser - operation was aborted localFileNameError - File could not be read or written on the local system. remoteFileNameError - File could not be read or written on the remote system unreachableDestination - the ip address or server name could not be reached. invalidUserNamePassword - The user name/password combination could not be authenticated by the ftp server. tooManyOpenFiles - File could not be opened due to too many files already opened. readError - Transfer not completed due to a file read error. writeError - Transfer not completed due to a file write error. Enumeration: 'success': 2, 'unreachableDestination': 6, 'invalidUserNamePassword': 7, 'remoteFileNameError': 5, 'writeError': 10, 'localFileNameError': 4, 'stoppedByUser': 3, 'inProgress': 1, 'tooManyOpenFiles': 8, 'readError': 9.

The action requested by the user. The normal operation is for a 'start' to be specified and this is the default value. Specifying 'stop' aborts the current operation in the current state. Specifying 'stop' with 'createAndGo' rowStatus results in the creation of the row. But the ftp transfer does not start until the row is specified to 'start'. Specifying multiple successive mstops or starts has no impact on the current operation. When read, the value returned is the last action requested. Enumeration: 'start': 1, 'stop': 2.

The time when the operation completed. This includes if the operation was aborted. While the operation is in progress, a value of 0 is returned.

The rowstatus is used by the manager to create or destroy a ftp request. Required fields on a create_and_go are: - local and remote filenames - server address or name - user name - password A get on this field always return 'active'.

This MIB defines the fields use by a manager to create a ftp request. The mib equates those fields in the command line request to an equivalent table entry. The system allows for up to 20 FTP requests to be concurrently executing.