Allied Telesis AlliedWare Plus Operating System Version 5.4.4C (x310-26FT,x310-26FP,x310-50FT,x310-50FP) User Manual

Page 1848

SNMP MIBs

Software Reference for x310 Series Switches

69.36

AlliedWare Plus

Operating System - Version 5.4.4C

C613-50046-01 REV A

atFilev2DeleteBegin

{ atFilev2Operation 9 }

Represents the status of the delete file operation, in
the form of octet string.
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 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.

Following are possible values returned as Error
codes for file move:

■

1 - atFilev2SourceDevice has not been set

■

2 - atFilev2SourceFilename has not been set

■

3 - atFilev2SourceDevicehas not 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 move 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 move operation.

atFilev2Flash_1

{ atFilev2Operation 10 }

Represents the Flash operation device object

atFilev2Card_2

{ atFilev2Operation 11 }

Represents the Card operation device object

atFilev2Nvs_3

{ atFilev2Operation 12 }

Represents the NVS operation device object

atFilev2Tftp_4

{ atFilev2Operation 13 }

Represents the TFTP operation device object

Table 69-9: Objects defined in AT-FILEv2-MIB(cont.)

Object(cont.) Object

Identifier

Description