aristaConfigCopyTimeout

The  maximum number of seconds a copy request could run.
              
If the copy request is not completed in such amount of
time, it will be terminated and marked as failed with a
failure cause of timeout.
              
The time taken by a copy request varies by the source and/
or destination file size, network condition, system load,
etc. A reasonable timeout should be chosen so that a stuck
or run-away copy request could be terminated, but a normal
copy request could complete.

MIB

ARISTA-CONFIG-COPY-MIB

OID

.1.3.6.1.4.1.30065.3.7.1.1.6

Type

column

Access

readwrite

Status

current

Parent

aristaConfigCopyCommandEntry