OID reference

atFilev2DeleteBegin

1.3.6.1.4.1.207.8.4.4.4.600.3.9

Description

A read on this object can return several possible values, depending on the current status of the system and the various file operation objects: idle There is no file operation in progress and all required objects have been set correctly. Setting a '1' to this object will begin the file deletion. Error codes: [1-3] A d…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.207.8.4.4.4.600.3 (atFilev2FileOperation)
Node code
9
Node name
atFilev2DeleteBegin
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.207.8.4.4.4.600.3.9
URN notation
urn:oid:1.3.6.1.4.1.207.8.4.4.4.600.3.9
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 207 8 4 4 4 600 3 9}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedtelesyn(207) mibObject(8) brouterMib(4) atRouter(4) modules(4) atFilev2(600) atFilev2FileOperation(3) atFilev2DeleteBegin(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedtelesyn(207) mibObjects(8) brouterMib(4) atRouter(4) modules(4) atFilev2(600) atFilev2FileOperation(3) atFilev2DeleteBegin(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedtelesyn(207) mibobjs(8) brouterMib(4) atRouter(4) modules(4) atFilev2(600) atFilev2FileOperation(3) atFilev2DeleteBegin(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) ati(207) mibObject(8) brouterMib(4) atRouter(4) modules(4) atFilev2(600) atFilev2FileOperation(3) atFilev2DeleteBegin(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) ati(207) mibObjects(8) brouterMib(4) atRouter(4) modules(4) atFilev2(600) atFilev2FileOperation(3) atFilev2DeleteBegin(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) ati(207) mibobjs(8) brouterMib(4) atRouter(4) modules(4) atFilev2(600) atFilev2FileOperation(3) atFilev2DeleteBegin(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedTelesis(207) mibObject(8) brouterMib(4) atRouter(4) modules(4) atFilev2(600) atFilev2FileOperation(3) atFilev2DeleteBegin(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedTelesis(207) mibObjects(8) brouterMib(4) atRouter(4) modules(4) atFilev2(600) atFilev2FileOperation(3) atFilev2DeleteBegin(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedTelesis(207) mibobjs(8) brouterMib(4) atRouter(4) modules(4) atFilev2(600) atFilev2FileOperation(3) atFilev2DeleteBegin(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedTelesyn(207) mibObject(8) brouterMib(4) atRouter(4) modules(4) atFilev2(600) atFilev2FileOperation(3) atFilev2DeleteBegin(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedTelesyn(207) mibObjects(8) brouterMib(4) atRouter(4) modules(4) atFilev2(600) atFilev2FileOperation(3) atFilev2DeleteBegin(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedTelesyn(207) mibobjs(8) brouterMib(4) atRouter(4) modules(4) atFilev2(600) atFilev2FileOperation(3) atFilev2DeleteBegin(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) alliedtelesyn(207) mibObject(8) brouterMib(4) atRouter(4) modules(4) atFilev2(600) atFilev2FileOperation(3) atFilev2DeleteBegin(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) alliedtelesyn(207) mibObjects(8) brouterMib(4) atRouter(4) modules(4) atFilev2(600) atFilev2FileOperation(3) atFilev2DeleteBegin(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) alliedtelesyn(207) mibobjs(8) brouterMib(4) atRouter(4) modules(4) atFilev2(600) atFilev2FileOperation(3) atFilev2DeleteBegin(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) ati(207) mibObject(8) brouterMib(4) atRouter(4) modules(4) atFilev2(600) atFilev2FileOperation(3) atFilev2DeleteBegin(9)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/207/8/4/4/4/600/3/9
  • /ISO/Identified-Organization/6/1/4/1/207/8/4/4/4/600/3/9
  • /ISO/3/6/1/4/1/207/8/4/4/4/600/3/9
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/alliedtelesyn/mibObject/brouterMib/atRouter/modules/atFilev2/atFilev2FileOperation/atFilev2DeleteBegin
  • /iso/identified-organization/dod/internet/private/enterprise/alliedtelesyn/mibObjects/brouterMib/atRouter/modules/atFilev2/atFilev2FileOperation/atFilev2DeleteBegin
  • /iso/identified-organization/dod/internet/private/enterprise/alliedtelesyn/mibobjs/brouterMib/atRouter/modules/atFilev2/atFilev2FileOperation/atFilev2DeleteBegin
  • /iso/identified-organization/dod/internet/private/enterprise/ati/mibObject/brouterMib/atRouter/modules/atFilev2/atFilev2FileOperation/atFilev2DeleteBegin
  • /iso/identified-organization/dod/internet/private/enterprise/ati/mibObjects/brouterMib/atRouter/modules/atFilev2/atFilev2FileOperation/atFilev2DeleteBegin
  • /iso/identified-organization/dod/internet/private/enterprise/ati/mibobjs/brouterMib/atRouter/modules/atFilev2/atFilev2FileOperation/atFilev2DeleteBegin
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesis/mibObject/brouterMib/atRouter/modules/atFilev2/atFilev2FileOperation/atFilev2DeleteBegin
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesis/mibObjects/brouterMib/atRouter/modules/atFilev2/atFilev2FileOperation/atFilev2DeleteBegin
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesis/mibobjs/brouterMib/atRouter/modules/atFilev2/atFilev2FileOperation/atFilev2DeleteBegin
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesyn/mibObject/brouterMib/atRouter/modules/atFilev2/atFilev2FileOperation/atFilev2DeleteBegin
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesyn/mibObjects/brouterMib/atRouter/modules/atFilev2/atFilev2FileOperation/atFilev2DeleteBegin
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesyn/mibobjs/brouterMib/atRouter/modules/atFilev2/atFilev2FileOperation/atFilev2DeleteBegin
  • /iso/identified-organization/dod/internet/private/enterprises/alliedtelesyn/mibObject/brouterMib/atRouter/modules/atFilev2/atFilev2FileOperation/atFilev2DeleteBegin
  • /iso/identified-organization/dod/internet/private/enterprises/alliedtelesyn/mibObjects/brouterMib/atRouter/modules/atFilev2/atFilev2FileOperation/atFilev2DeleteBegin
  • /iso/identified-organization/dod/internet/private/enterprises/alliedtelesyn/mibobjs/brouterMib/atRouter/modules/atFilev2/atFilev2FileOperation/atFilev2DeleteBegin
  • /iso/identified-organization/dod/internet/private/enterprises/ati/mibObject/brouterMib/atRouter/modules/atFilev2/atFilev2FileOperation/atFilev2DeleteBegin
  • Additional combinations skipped.

SNMP properties

Value type
OCTET STRING
Maximum access defined by MIB
read-write
Status in MIB
current

Using this OID with SNMP

At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.

snmpget [connection options] DEVICE .1.3.6.1.4.1.207.8.4.4.4.600.3.9.0

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

atFilev2DeleteBegin · current

atFilev2DeleteBegin OBJECT-TYPE
            SYNTAX OCTET STRING
            MAX-ACCESS read-write
            STATUS current
            DESCRIPTION
                "A read on this object can return several possible values,
                depending on the current status of the system and the various
                file operation objects:

                idle                               There is no file operation
                                                   in progress and all required
                                                   objects have been set
                                                   correctly. Setting a '1' to
                                                   this object will begin the
                                                   file deletion.

                Error codes: [1-3]                 A delete operation cannot be
                                                   started until these errors
                                                   are resolved. See below for
                                                   key.

                [action]ing x [--> y]              A file operation is
                                                   currently in progress. You
                                                   cannot start another
                                                   operation while the object
                                                   is returning this value.

                [action] x [--> y] success         The last copy, move or
                                                   delete operation was
                                                   successfully completed.

                [action] x [--> y] failure: [err]  The last copy, move or
                                                   delete operation failed,
                                                   with the error message
                                                   attached. Common failures
                                                   include lack of space on the
                                                   destination file system,
                                                   incorrect source file names
                                                   or communication errors with
                                                   remote services.

                Upon reading a success or failure message, the message will be
                cleared and the next read will result in either an 'idle'
                message or an 'Error codes' message if not all required objects
                have been correctly set. If a read returns 'idle', a new file
                operation can be started.

                File deletion operations ignore the values set in the
                atFilev2DestinationStackID, atFilev2DestinationDevice and
                atFilev2DestinationFilename objects.

                Error codes for file deletion:

                1 - atFilev2SourceDevice has not been set
                2 - atFilev2SourceFilename has not been set
                3 - atFilev2SourceDevice has been set to TFTP

                Note that if the above requirements are met and the operation
                would result in a system file being deleted, then an SNMP set
                to this object will be disallowed.
                
                For valid operations, immediately upon executing the SNMP set
                operation on this object, the file deletion will begin and will
                continue on the device until either it has completed, or a
                failure occurs. For large files, operations can take several
                minutes to complete.

                Subsequent reads of the object will return one of the messages
                shown above, to track the progress of the deletion operation."
            ::= { atFilev2FileOperation 9 }

atFilev2DeleteBegin · current

atFilev2DeleteBegin OBJECT-TYPE
			SYNTAX OCTET STRING
			MAX-ACCESS read-write
			STATUS current
			DESCRIPTION
				"A read on this object can return several possible values,
				depending on the current status of the system and the various
				file operation objects:
				
				idle                               There is no file operation
				                                   in progress and all required
				                                   objects have been set
				                                   correctly. Setting a '1' to
				                                   this object will begin the
				                                   file deletion.
				
				Error codes: [1-3]                 A delete operation cannot be
				                                   started until these errors
				                                   are resolved. See below for
				                                   key.
				
				[action]ing x [--> y]              A file operation is
				                                   currently in progress. You
				                                   cannot start another
				                                   operation while the object
				                                   is returning this value.
				
				[action] x [--> y] success         The last copy, move or
				                                   delete operation was 
				                                   successfully completed.
				
				[action] x [--> y] failure: [err]  The last copy, move or
				                                   delete operation failed,
				                                   with the error message
				                                   attached. Common failures 
				                                   include lack of space on the
				                                   destination file system,
				                                   incorrect source file names
				                                   or communication errors with
				                                   remote services.
				
				Upon reading a success or failure message, the message will be
				cleared and the next read will result in either an 'idle'
				message or an 'Error codes' message if not all required objects
				have been correctly set. If the read returned 'idle', a new
				file operation can now be started.
				
				File deletion operations ignore the values set in the
				atFilev2DestinationStackID, atFilev2DestinationDevice and
				atFilev2DestinationFilename objects.
				
				The file deletion operation is equivalent to the CLI 'delete
				force [file]' command, so it is possible to delete any
				normally-protected system files, such as the currently
				configured boot release.
				
				
				Error codes for file deletion:
				
				1 - atFilev2SourceDevice has not been set
				2 - atFilev2SourceFilename has not been set
				3 - atFilev2SourceDevice has been set to TFTP
				
				Provided all above requirements are met, immediately upon
				executing the SNMP set, the device will indicate that it was a
				success. The actual file deletion itself will be started and
				continue on the device until it has completed. For large files,
				operations can take several minutes to complete.
				
				Subsequent reads of the object will return one of messages
				shown in the first table, to allow for tracking of the progress
				of the delete operation."
			::= { atFilev2FileOperation 9 }

Meaning

Descriptions

2 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

Description 1

A read on this object can return several possible values, depending on the current status of the system and the various file operation objects: idle There is no file operation in progress and all required objects have been set correctly. Setting a '1' to this object will begin the file deletion. Error codes: [1-3] A delete operation cannot be started until these errors are resolved. See below for key. [action]ing x [--> y] A file operation is currently in progress. You cannot start another operation while the object is returning this value. [action] x [--> y] success The last copy, move or delete operation was successfully completed. [action] x [--> y] failure: [err] The last copy, move or delete operation failed, with the error message attached. Common failures include lack of space on the destination file system, incorrect source file names or communication errors with remote services. Upon reading a success or failure message, the message will be cleared and the next read will result in either an 'idle' message or an 'Error codes' message if not all required objects have been correctly set. If a read returns 'idle', a new file operation can be started. File deletion operations ignore the values set in the atFilev2DestinationStackID, atFilev2DestinationDevice and atFilev2DestinationFilename objects. Error codes for file deletion: 1 - atFilev2SourceDevice has not been set 2 - atFilev2SourceFilename has not been set 3 - atFilev2SourceDevice has been set to TFTP Note that if the above requirements are met and the operation would result in a system file being deleted, then an SNMP set to this object will be disallowed. For valid operations, immediately upon executing the SNMP set operation on this object, the file deletion will begin and will continue on the device until either it has completed, or a failure occurs. For large files, operations can take several minutes to complete. Subsequent reads of the object will return one of the messages shown above, to track the progress of the deletion operation.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)Netdisco MIB archive copies

See 1 matching source record

Description 2

A read on this object can return several possible values, depending on the current status of the system and the various file operation objects: idle There is no file operation in progress and all required objects have been set correctly. Setting a '1' to this object will begin the file deletion. Error codes: [1-3] A delete operation cannot be started until these errors are resolved. See below for key. [action]ing x [--> y] A file operation is currently in progress. You cannot start another operation while the object is returning this value. [action] x [--> y] success The last copy, move or delete operation was successfully completed. [action] x [--> y] failure: [err] The last copy, move or delete operation failed, with the error message attached. Common failures include lack of space on the destination file system, incorrect source file names or communication errors with remote services. Upon reading a success or failure message, the message will be cleared and the next read will result in either an 'idle' message or an 'Error codes' message if not all required objects have been correctly set. If the read returned 'idle', a new file operation can now be started. File deletion operations ignore the values set in the atFilev2DestinationStackID, atFilev2DestinationDevice and atFilev2DestinationFilename objects. The file deletion operation is equivalent to the CLI 'delete force [file]' command, so it is possible to delete any normally-protected system files, such as the currently configured boot release. Error codes for file deletion: 1 - atFilev2SourceDevice has not been set 2 - atFilev2SourceFilename has not been set 3 - atFilev2SourceDevice has been set to TFTP Provided all above requirements are met, immediately upon executing the SNMP set, the device will indicate that it was a success. The actual file deletion itself will be started and continue on the device until it has completed. For large files, operations can take several minutes to complete. Subsequent reads of the object will return one of messages shown in the first table, to allow for tracking of the progress of the delete operation.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

2 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies1 record · 2 sources

Description 1

atFilev2DeleteBegin · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies2 sources

Status in source: current.

Names: atFilev2DeleteBegin

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "atFilev2DeleteBegin",
    "OBJECT-TYPE",
    "SYNTAX",
    "OCTET",
    "STRING",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"A read on this object can return several possible values, depending on the current status of the system and the various file operation objects: idle There is no file operation in progress and all required objects have been set correctly. Setting a '1' to this object will begin the file deletion. Error codes: [1-3] A delete operation cannot be started until these errors are resolved. See below for key. [action]ing x [--> y] A file operation is currently in progress. You cannot start another operation while the object is returning this value. [action] x [--> y] success The last copy, move or delete operation was successfully completed. [action] x [--> y] failure: [err] The last copy, move or delete operation failed, with the error message attached. Common failures include lack of space on the destination file system, incorrect source file names or communication errors with remote services. Upon reading a success or failure message, the message will be cleared and the next read will result in either an 'idle' message or an 'Error codes' message if not all required objects have been correctly set. If a read returns 'idle', a new file operation can be started. File deletion operations ignore the values set in the atFilev2DestinationStackID, atFilev2DestinationDevice and atFilev2DestinationFilename objects. Error codes for file deletion: 1 - atFilev2SourceDevice has not been set 2 - atFilev2SourceFilename has not been set 3 - atFilev2SourceDevice has been set to TFTP Note that if the above requirements are met and the operation would result in a system file being deleted, then an SNMP set to this object will be disallowed. For valid operations, immediately upon executing the SNMP set operation on this object, the file deletion will begin and will continue on the device until either it has completed, or a failure occurs. For large files, operations can take several minutes to complete. Subsequent reads of the object will return one of the messages shown above, to track the progress of the deletion operation.\"",
    "::=",
    "{",
    "atFilev2FileOperation",
    "9",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "OCTET STRING"
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "A read on this object can return several possible values, depending on the current status of the system and the various file operation objects: idle There is no file operation in progress and all required objects have been set correctly. Setting a '1' to this object will begin the file deletion. Error codes: [1-3] A delete operation cannot be started until these errors are resolved. See below for key. [action]ing x [--> y] A file operation is currently in progress. You cannot start another operation while the object is returning this value. [action] x [--> y] success The last copy, move or delete operation was successfully completed. [action] x [--> y] failure: [err] The last copy, move or delete operation failed, with the error message attached. Common failures include lack of space on the destination file system, incorrect source file names or communication errors with remote services. Upon reading a success or failure message, the message will be cleared and the next read will result in either an 'idle' message or an 'Error codes' message if not all required objects have been correctly set. If a read returns 'idle', a new file operation can be started. File deletion operations ignore the values set in the atFilev2DestinationStackID, atFilev2DestinationDevice and atFilev2DestinationFilename objects. Error codes for file deletion: 1 - atFilev2SourceDevice has not been set 2 - atFilev2SourceFilename has not been set 3 - atFilev2SourceDevice has been set to TFTP Note that if the above requirements are met and the operation would result in a system file being deleted, then an SNMP set to this object will be disallowed. For valid operations, immediately upon executing the SNMP set operation on this object, the file deletion will begin and will continue on the device until either it has completed, or a failure occurs. For large files, operations can take several minutes to complete. Subsequent reads of the object will return one of the messages shown above, to track the progress of the deletion operation."
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 2Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 2

atFilev2DeleteBegin · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: atFilev2DeleteBegin

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "atFilev2DeleteBegin",
    "OBJECT-TYPE",
    "SYNTAX",
    "OCTET",
    "STRING",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"A read on this object can return several possible values, depending on the current status of the system and the various file operation objects: idle There is no file operation in progress and all required objects have been set correctly. Setting a '1' to this object will begin the file deletion. Error codes: [1-3] A delete operation cannot be started until these errors are resolved. See below for key. [action]ing x [--> y] A file operation is currently in progress. You cannot start another operation while the object is returning this value. [action] x [--> y] success The last copy, move or delete operation was successfully completed. [action] x [--> y] failure: [err] The last copy, move or delete operation failed, with the error message attached. Common failures include lack of space on the destination file system, incorrect source file names or communication errors with remote services. Upon reading a success or failure message, the message will be cleared and the next read will result in either an 'idle' message or an 'Error codes' message if not all required objects have been correctly set. If the read returned 'idle', a new file operation can now be started. File deletion operations ignore the values set in the atFilev2DestinationStackID, atFilev2DestinationDevice and atFilev2DestinationFilename objects. The file deletion operation is equivalent to the CLI 'delete force [file]' command, so it is possible to delete any normally-protected system files, such as the currently configured boot release. Error codes for file deletion: 1 - atFilev2SourceDevice has not been set 2 - atFilev2SourceFilename has not been set 3 - atFilev2SourceDevice has been set to TFTP Provided all above requirements are met, immediately upon executing the SNMP set, the device will indicate that it was a success. The actual file deletion itself will be started and continue on the device until it has completed. For large files, operations can take several minutes to complete. Subsequent reads of the object will return one of messages shown in the first table, to allow for tracking of the progress of the delete operation.\"",
    "::=",
    "{",
    "atFilev2FileOperation",
    "9",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "OCTET STRING"
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "A read on this object can return several possible values, depending on the current status of the system and the various file operation objects: idle There is no file operation in progress and all required objects have been set correctly. Setting a '1' to this object will begin the file deletion. Error codes: [1-3] A delete operation cannot be started until these errors are resolved. See below for key. [action]ing x [--> y] A file operation is currently in progress. You cannot start another operation while the object is returning this value. [action] x [--> y] success The last copy, move or delete operation was successfully completed. [action] x [--> y] failure: [err] The last copy, move or delete operation failed, with the error message attached. Common failures include lack of space on the destination file system, incorrect source file names or communication errors with remote services. Upon reading a success or failure message, the message will be cleared and the next read will result in either an 'idle' message or an 'Error codes' message if not all required objects have been correctly set. If the read returned 'idle', a new file operation can now be started. File deletion operations ignore the values set in the atFilev2DestinationStackID, atFilev2DestinationDevice and atFilev2DestinationFilename objects. The file deletion operation is equivalent to the CLI 'delete force [file]' command, so it is possible to delete any normally-protected system files, such as the currently configured boot release. Error codes for file deletion: 1 - atFilev2SourceDevice has not been set 2 - atFilev2SourceFilename has not been set 3 - atFilev2SourceDevice has been set to TFTP Provided all above requirements are met, immediately upon executing the SNMP set, the device will indicate that it was a success. The actual file deletion itself will be started and continue on the device until it has completed. For large files, operations can take several minutes to complete. Subsequent reads of the object will return one of messages shown in the first table, to allow for tracking of the progress of the delete operation."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.207)

Scott Holley

Siblings (14)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.207.8.4.4.4.600.3.1 atFilev2SourceStackID00
1.3.6.1.4.1.207.8.4.4.4.600.3.2 atFilev2SourceDevice00
1.3.6.1.4.1.207.8.4.4.4.600.3.3 atFilev2SourceFilename00
1.3.6.1.4.1.207.8.4.4.4.600.3.4 atFilev2DestinationStackID00
1.3.6.1.4.1.207.8.4.4.4.600.3.5 atFilev2DestinationDevice00
1.3.6.1.4.1.207.8.4.4.4.600.3.6 atFilev2DestinationFilename00
1.3.6.1.4.1.207.8.4.4.4.600.3.7 atFilev2CopyBegin00
1.3.6.1.4.1.207.8.4.4.4.600.3.8 atFilev2MoveBegin00
1.3.6.1.4.1.207.8.4.4.4.600.3.10 atFilev2Flash100
1.3.6.1.4.1.207.8.4.4.4.600.3.11 atFilev2Card200
1.3.6.1.4.1.207.8.4.4.4.600.3.12 atFilev2Nvs300
1.3.6.1.4.1.207.8.4.4.4.600.3.13 atFilev2Tftp411
1.3.6.1.4.1.207.8.4.4.4.600.3.14 atFilev2DirOperation77
1.3.6.1.4.1.207.8.4.4.4.600.3.15 atFilev2Usb500