All MIBs › AT-FILEv2-MIB › atFilev2DeleteBegin
atFilev2DeleteBegin
Module: AT-FILEv2-MIB
OID (symbolic): AT-FILEv2-MIB::atFilev2DeleteBegin
OID (numeric): 1.3.6.1.4.1.207.8.4.4.4.600.3.9
Node type: OBJECT-TYPE
Type: OCTET STRING
Access: read-write
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.
What is atFilev2DeleteBegin?
This read-write object initiates or monitors file deletion. Reading returns status; setting to '1' deletes the source file after confirming all parameters are set.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.207.8.4.4.4.600.3.9 snmpwalk -v2c -c public <target> AT-FILEv2-MIB::atFilev2DeleteBegin
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.207.8.4.4.4.600.3.9.1 snmpget -v2c -c public <target> AT-FILEv2-MIB::atFilev2DeleteBegin.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.207.8.4.4.4.600.3.9.1 s <value>
Start monitoring Allied Telesis managed switches and routers with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the AT-FILEv2-MIB::atFilev2DeleteBegin OID value, configure state conditions and alerts, and monitor any Allied Telesis managed switches and routers 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.207 | alliedTelesyn | AT-RG600-MIB |
| 1.3.6.1.4.1.207.8 | mibObject | AT-RG600-MIB |
| 1.3.6.1.4.1.207.8.4 | brouterMib | AT-SMI-MIB |
| 1.3.6.1.4.1.207.8.4.4 | atRouter | AT-SMI-MIB |
| 1.3.6.1.4.1.207.8.4.4.4 | modules | AT-SMI-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.207.8.4.4.4.600 | atFilev2 | AT-FILEv2-MIB |
| 1.3.6.1.4.1.207.8.4.4.4.600.3 | atFilev2FileOperation | AT-FILEv2-MIB |
| 1.3.6.1.4.1.207.8.4.4.4.600.3.9 | atFilev2DeleteBegin | AT-FILEv2-MIB |