Fore-FileXfr-MIB: View SNMP OID List / Download MIB
VENDOR: FORE SYSTEMS
Home | MIB: Fore-FileXfr-MIB | |||
---|---|---|---|---|
Download as: |
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).
|
|||
Object Name | OID | Type | Access | Info |
foreFileXfrModule | 1.3.6.1.4.1.326.1.6.1 |
This MIB module defines the FORE Systems generic file transfer information. It provides for a file transfer table. Each table entry contains the information necessary for a device to complete a file transfer. Each table entry also contains information as to the status of the file transfer. |
||
fXfrGroup | 1.3.6.1.4.1.326.1.6.2 | |||
fXfrNextIndex | 1.3.6.1.4.1.326.1.6.2.1 | testandincr | read-write |
The index of the next free row in the fXfrTable. |
fXfrTable | 1.3.6.1.4.1.326.1.6.2.2 | no-access |
A table of pending and completed file transfers. |
|
1.3.6.1.4.1.326.1.6.2.2.1 | no-access |
A table entry containing information on a pending or completed file transfer. |
||
fXfrIndex | 1.3.6.1.4.1.326.1.6.2.2.1.1 | integer32 | read-only |
The index of the file transfer. |
fXfrRemoteFileUrl | 1.3.6.1.4.1.326.1.6.2.2.1.2 | displaystring | read-only |
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: |
fXfrLocalFile | 1.3.6.1.4.1.326.1.6.2.2.1.3 | displaystring | read-only |
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 of the local file. Some examples of descriptions specific to an ASX are switchCDB, lecsConfig, and switchUpgrade. As of FT5.2 additionally supported are netmodUpgradeA, netmodUpgradeB,netmodUpgradeC,netmodUpgradeD |
fXfrDirection | 1.3.6.1.4.1.326.1.6.2.2.1.4 | integer | read-only |
Indication of the file transfer operation. A 'get' will retrieve the file from the machine specified in fXfrRemoteFileUrl. A 'put' will send the file to the machine specified in fXfrRemoteFileUrl. Enumeration: 'put': 2, 'get': 1. |
fXfrEntryStatus | 1.3.6.1.4.1.326.1.6.2.2.1.5 | entrystatus | read-only |
The status of this table entry. |
fXfrStatus | 1.3.6.1.4.1.326.1.6.2.2.1.6 | integer | read-only |
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. Enumeration: 'busy': 7, 'succeeded': 5, 'failed': 6, 'idle': 1, 'inQueue': 3, 'go': 2, 'inProgress': 4. |
fXfrStatusText | 1.3.6.1.4.1.326.1.6.2.2.1.7 | displaystring | read-only |
A message describing the status of this file transfer. This must exists when the status is succeeded or failed. This can optionally exists when the status is inQueue, inProgress, or busy. |
fXfrOwnerIpAddress | 1.3.6.1.4.1.326.1.6.2.2.1.8 | ipaddress | read-only |
Ip address of the entity that requested this file transfer. |
fXfrOwnerSignature | 1.3.6.1.4.1.326.1.6.2.2.1.9 | displaystring | read-only |
Signature of the owner of this file transfer. This is supplied by the management station. |
fXfrTransferType | 1.3.6.1.4.1.326.1.6.2.2.1.10 | integer | read-only |
The type of transfer requested. A binary transfer will perform no translations while an ascii transfer will set the representation type to network ASCII. Enumeration: 'binary': 1, 'ascii': 2. |
fXfrUserId | 1.3.6.1.4.1.326.1.6.2.2.1.11 | displaystring | read-only |
The login name on the remote host for FTP. |
fXfrPassword | 1.3.6.1.4.1.326.1.6.2.2.1.12 | displaystring | read-only |
The password associated with the login name on the remote host for FTP. Note this object is write-only and reading it will result in implementation-specific results. |