All MIBs › CXFileServer-MIB › cxFsTransferErrorCode
cxFsTransferErrorCode
Module: CXFileServer-MIB
OID (symbolic): CXFileServer-MIB::cxFsTransferErrorCode
OID (numeric): 1.3.6.1.4.1.495.2.1.5.3.14
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: Indicates whether any errors occurred during the last file transfer action initiated using the 'cxFsTransferAction' object. The cxFsTransferErrorCode object also indicates the nature of any errors that occur during file transfer.
Options: not-applicable (1): No action taken; therefore, no error generated.
ok (2): No errors. The last file transfer operation was successfully completed.
local-open-error (3): Could not open the local file for which a PUT or GET command was issued.
nfs-open-error (4): Could not open the remote file for which a PUT or GET command was issued.
local-reading-error (5): Either a local file for which a PUT command was issued could not be read, or a remote file obtained through a GET command could not be read locally.
nfs-reading-error (6): Either a remote file PUT to a destination slot could not be read at that location, or a remote file for which a GET command was issued could not be read in the remote slot.
local-writing-error (7): The 'cxFsTransferAction' object was unable to copy the specified file to the local directory.
nfs-writing-error (8): The 'cxFsTransferAction' object was unable to copy the specified file to the destination directory.
local-close-error (9): Could not close local file used in either a GET or PUT action.
nfs-close-error (10): Could not close a remote file used in either a GET or PUT action.
other-error (11): An unspecified error (other than those listed above) occurred.
Related Objects: cxFsTransferAction cxFsTransferFileName cxFsTransferDestSlot cxFsTransferStatus
What is cxFsTransferErrorCode?
This object reports the specific error, if any, that occurred during the last file transfer triggered via cxFsTransferAction, distinguishing failures such as local-open-error, nfs-open-error, reading/writing errors on either end, close errors, or an unspecified other-error, alongside not-applicable and ok. Admins check this after a transfer reports failed(4) in cxFsTransferStatus to pinpoint exactly what went wrong. For example, a failed transfer reporting nfs-writing-error(8) would tell the admin the problem was on the destination slot's side rather than the local file.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.495.2.1.5.3.14 snmpwalk -v2c -c public <target> CXFileServer-MIB::cxFsTransferErrorCode
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.495.2.1.5.3.14.1 snmpget -v2c -c public <target> CXFileServer-MIB::cxFsTransferErrorCode.1
Start monitoring CX Memotec network device (TFTP file management) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CXFileServer-MIB::cxFsTransferErrorCode OID value, configure state conditions and alerts, and monitor any CX Memotec network device (TFTP file management) from a single console.
OID Breakdown
Upper-level ancestors (11 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.495 | memotec | MEMOTEC-SMI |
| 1.3.6.1.4.1.495.2 | memotecProducts | MEMOTEC-SMI |
| 1.3.6.1.4.1.495.2.1 | cxProduct | MEMOTEC-SMI |
| 1.3.6.1.4.1.495.2.1.5 | cxSystem | CXProduct-SMI |
| 1.3.6.1.4.1.495.2.1.5.3 | cxFileServer | CXProduct-SMI |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.495.2.1.5.3.14 | cxFsTransferErrorCode | CXFileServer-MIB |