REDSTONE-FILE-XFER-MIB: View SNMP OID List / Download MIB

VENDOR: REDSTONE COMMUNICATIONS


 Home MIB: REDSTONE-FILE-XFER-MIB
Download as:   
SNMPv2-CONF, SNMPv2-SMI, REDSTONE-SMI, SNMPv2-TC

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 rsFileXferMIB 1.3.6.1.4.1.2773.2.23
The File Transfer MIB for Redstone Communications Inc. enterprise.
       rsFileXferObjects 1.3.6.1.4.1.2773.2.23.1
           rsFileXferTable 1.3.6.1.4.1.2773.2.23.1.1 no-access
A list of entries which describe file transfers.
               rsFileXferTableEntry 1.3.6.1.4.1.2773.2.23.1.1.1 no-access
A description of a particular file transfer entry.
                   rsFileXferIndex 1.3.6.1.4.1.2773.2.23.1.1.1.1 integer read-only
A unique index used to identify this entry.
                   rsFileXferDirection 1.3.6.1.4.1.2773.2.23.1.1.1.2 integer read-write
Specifies the direction of the file transfer. Enumeration: 'rsFileXferRemoteToLocal': 2, 'rsFileXferLocalToRemote': 1.
                   rsFileXferFileType 1.3.6.1.4.1.2773.2.23.1.1.1.3 integer read-write
Specifies the file type of the file transfer. Enumeration: 'rsFileXferRunningConfig': 3, 'rsFileXferBulkStatistics': 7, 'rsFileXferRebootHistory': 6, 'rsFileXferSystemConfig': 2, 'rsFileXferSoftwareRelease': 1, 'rsFileXferSystemLog': 4, 'rsFileXferScript': 5.
                   rsFileXferRemoteFileName 1.3.6.1.4.1.2773.2.23.1.1.1.4 displaystring read-write
The full path name of the source/destination file on the remote system.
                   rsFileXferRemoteUserName 1.3.6.1.4.1.2773.2.23.1.1.1.5 displaystring read-write
The user name to use when requesting the file transfer to/from the remote system.
                   rsFileXferRemoteUserPassword 1.3.6.1.4.1.2773.2.23.1.1.1.6 octet string read-write
The 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.
                   rsFileXferLocalFileName 1.3.6.1.4.1.2773.2.23.1.1.1.7 displaystring read-write
The local file name to transfer or to create as a result of an incoming transfer.
                   rsFileXferProtocol 1.3.6.1.4.1.2773.2.23.1.1.1.8 integer read-write
Specifies the file transfer protocol type. Enumeration: 'rsFileXferFtp': 1, 'rsFileXferTftp': 2.
                   rsFileXferStatus 1.3.6.1.4.1.2773.2.23.1.1.1.9 integer read-only
The status of the file transfer. Enumeration: 'rsFileXferInProgress': 2, 'rsFileXferUserAuthFailed': 4, 'rsFileXferFileTooBig': 6, 'rsFileXferPended': 8, 'rsFileXferFileNotFound': 5, 'rsFileXferRemoteUnreachable': 3, 'rsFileXferFileIncompatible': 7, 'rsFileXferSuccessfulCompletion': 1.
                   rsFileXferRowStatus 1.3.6.1.4.1.2773.2.23.1.1.1.10 rowstatus read-write
The 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.
                   rsFileXferTimeStamp 1.3.6.1.4.1.2773.2.23.1.1.1.11 timeticks read-only
The value of sysUpTime at the last status change for this entry.
           rsFileXferTrapEnabled 1.3.6.1.4.1.2773.2.23.1.2 integer read-write
An indication of whether the rsFileXferTrap trap is enabled. Enumeration: 'false': 2, 'true': 1.
       rsFileXferNotifications 1.3.6.1.4.1.2773.2.23.2
           rsFileXferNotifyPrefix 1.3.6.1.4.1.2773.2.23.2.0
               rsFileXferTrap 1.3.6.1.4.1.2773.2.23.2.0.1
An indication that the status associated with a particular file transfer entry has changed.