REDSTONE-FILE-XFER-MIB
The File Transfer MIB for Redstone Communications Inc. enterprise.
Main OID:
rsFileXferMIB.1.3.6.1.4.1.2773.2.23
19
Objects
Active
Status
3
Dependencies
Imported Objects
Objects
19 total| Object Name |
|---|
rsFileXferMIBThe File Transfer MIB for Redstone Communications Inc. enterprise. MODULE-IDENTITY .1.3.6.1.4.1.2773.2.23 |
rsFileXferObjects OBJECT IDENTIFIER .1.3.6.1.4.1.2773.2.23.1 |
rsFileXferTableA list of entries which describe file transfers. SEQUENCE OF RsFileXferTableEntry .1.3.6.1.4.1.2773.2.23.1.1 |
rsFileXferTableEntryA description of a particular file transfer entry. RsFileXferTableEntry .1.3.6.1.4.1.2773.2.23.1.1.1 |
rsFileXferIndexA unique index used to identify this entry.ro INTEGER .1.3.6.1.4.1.2773.2.23.1.1.1.1 |
rsFileXferDirectionSpecifies the direction of the file transfer.rw Enumeration .1.3.6.1.4.1.2773.2.23.1.1.1.2 |
rsFileXferFileTypeSpecifies the file type of the file transfer.rw Enumeration .1.3.6.1.4.1.2773.2.23.1.1.1.3 |
rsFileXferRemoteFileNameThe full path name of the source/destination file on the remote system.rw DisplayString .1.3.6.1.4.1.2773.2.23.1.1.1.4 |
rsFileXferRemoteUserNameThe user name to use when requesting the file transfer to/from the remote system.rw DisplayString .1.3.6.1.4.1.2773.2.23.1.1.1.5 |
rsFileXferRemoteUserPasswordThe password to use when requesting the file transfer to/from the remote system. When read, this object returns a zero string. Note that, for security reasons, some ftp servers may insist on a non-zero length user password.rw OCTET STRING .1.3.6.1.4.1.2773.2.23.1.1.1.6 |
rsFileXferLocalFileNameThe local file name to transfer or to create as a result of an incoming transfer.rw DisplayString .1.3.6.1.4.1.2773.2.23.1.1.1.7 |
rsFileXferProtocolSpecifies the file transfer protocol type.rw Enumeration .1.3.6.1.4.1.2773.2.23.1.1.1.8 |
rsFileXferStatusThe status of the file transfer.ro Enumeration .1.3.6.1.4.1.2773.2.23.1.1.1.9 |
rsFileXferRowStatusThe row status object controls the creation/deletion of rows in this table. Its semantics are the same as those for the RowStatus textual convention specified for SNMPv2. Setting this object to createAndGo(4) is allowed. If required objects are missing, the agent will create the row and set its status to notReady(3). If all of the required objects are present and valid, the agent will create the row, set it to active and commence the file xfer. Upon completion of the file xfer, the agent will set the rowStatus to notInService(2), indicating that the row is valid and useable by a management client. To commence another transfer, a management client should set the rowStatus to active(1). Setting this object to createAndWait(5) causes an entry to be created with rsFileXferRowStatus value of notInService(2) if all of the required objects are present and valid. Or, if some of the required objects are missing or invalid, the agent will create the row and sets its status to notReady(3). Setting this object to active(1) causes the transfer to start for the given row. Objects within the row cannot be modified once a row has been set to active(1), Setting this object to destroy(6) causes the corresponding row to be deleted. Note that only a single instance of a row can be active at at any given moment, although several rows can exist in the table.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.2773.2.23.1.1.1.10 |
rsFileXferTimeStampThe value of sysUpTime at the last status change for this entry.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.2773.2.23.1.1.1.11 |
rsFileXferTrapEnabledAn indication of whether the rsFileXferTrap trap is enabled.rw Enumeration .1.3.6.1.4.1.2773.2.23.1.2 |
rsFileXferNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.2773.2.23.2 |
rsFileXferNotifyPrefix OBJECT IDENTIFIER .1.3.6.1.4.1.2773.2.23.2.0 |
rsFileXferTrapAn indication that the status associated with a particular file transfer entry has changed. NOTIFICATION-TYPE .1.3.6.1.4.1.2773.2.23.2.0.1 |