atFilev2DeleteBegin
AT-FILEv2-MIB ·
allied-old variant
·
.1.3.6.1.4.1.207.8.4.4.4.600.3.9
Object
scalar r/w
OctetString
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.
Context
- MIB
- AT-FILEv2-MIB
- OID
.1.3.6.1.4.1.207.8.4.4.4.600.3.9- Type
- scalar
- Access
- readwrite
- Status
- current
- Parent
- atFilev2FileOperation
Net-SNMP examples
How SNMP and these commands workScalars have one instance, identified by the .0 suffix.
Read the scalar instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'AT-FILEv2-MIB' -M '/opt/observium/mibs/allied-old:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'AT-FILEv2-MIB::atFilev2DeleteBegin.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'AT-FILEv2-MIB' -M '/opt/observium/mibs/allied-old:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'AT-FILEv2-MIB::atFilev2DeleteBegin'
Syntax
OctetString
Values & Constraints
No enumerated values or constraints recorded.