Allied Telesis AlliedWare Plus Operating System Version 5.4.4C (x310-26FT,x310-26FP,x310-50FT,x310-50FP) User Manual
Page 1847
SNMP MIBs
Software Reference for x310 Series Switches
C613-50046-01 REV A
AlliedWare Plus
TM
Operating System - Version 5.4.4C
69.35
atFilev2MoveBegin
{ atFilev2Operation 8 }
Represents the status of the move 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 move.
■
Error codes: [1-6] - A move 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.
Following are possible values returned as Error
codes for file move:
■
1 - atFilev2SourceDevice has not been set
■
2 - atFilev2SourceFilename has not been set
■
3 - atFilev2DestinationDevice has not been set
■
4 - atFilev2DestinationFilename has not been set
■
5 - either atFilev2SourceDevice or
atFilev2DestinationDevice are set to TFTP
■
6 - the combination of source device, stackID and
filename is the same as the destination device,
stackID and filename (i.e. it is not valid to move a
file onto itself.
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.
Table 69-9: Objects defined in AT-FILEv2-MIB(cont.)
Object(cont.) Object
Identifier
Description