ARISTA-CONFIG-COPY-MIB
AI MIB Summary
The ARISTA-CONFIG-COPY-MIB enables programmatic management of configuration and file transfers on Arista EOS devices by defining objects to copy resources between local storage, running-config, startup-config, and remote protocols including FTP, HTTP, HTTPS, and TFTP. It facilitates the automation of configuration backup, restoration, and synchronization tasks across supported URI schemes without requiring interactive CLI commands.
This MIB is for copying a source URI to a destination URI. A URI specifies the location of a local file, network file, running-config or startup-config. The resources specified by the URIs are copied from/to Arista devices. Currently supported URI schemes include: file, flash, extension, system, ftp, http, https and tftp.
Main OID:
aristaConfigCopyMIB.1.3.6.1.4.1.30065.3.7
19
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
19 total| Object Name |
|---|
aristaConfigCopyMIBThis MIB is for copying a source URI to a destination URI. A URI specifies the location of a local file, network file, running-config or startup-config. The resources specified by the URIs are copied from/to Arista devices. Currently supported URI schemes include: file, flash, extension, system, ftp, http, https and tftp. MODULE-IDENTITY .1.3.6.1.4.1.30065.3.7 |
aristaConfigCopyCommandTableA table of copy requests. Each row corresponds to a copy request. The completed rows are accessible for status retrival for a certain peroid of time and then will be gradually aged out by the agent. SEQUENCE OF AristaConfigCopyCommandEntry .1.3.6.1.4.1.30065.3.7.1 |
aristaConfigCopyCommandEntryA copy request. A management station should generate a unique ID and name (as the index) for each copy request. This prevents multiple management stations or applications from using same index and causing conflicts in same row. After an unique index is generated, the management station could create a row with that index and setup a copy request. Once a copy request is setup correctly with both source and destination URIs, it can be queued by setting the row status to active. The row creation, copy request setup and row activation can be done in one or multiple SET requests. The status of the copy request may change after the request is queued. It can be retrieved at any time before the request is aged out by the agent. AristaConfigCopyCommandEntry .1.3.6.1.4.1.30065.3.7.1.1 |
aristaConfigCopyNameThe name of a copy request. It is chosen by the management station and should be unique so that two management stations or applications do not cause conflicts in same row. DisplayString .1.3.6.1.4.1.30065.3.7.1.1.1 |
aristaConfigCopyIdThe ID of a copy request. It is chosen by the management station and should be unique. One way to generate such a unique intenger is through the TestAndIncr mechanism (in SNMPv2-TC). Unsigned32 .1.3.6.1.4.1.30065.3.7.1.1.2 |
aristaConfigCopySourceUriThe source URI of a copy request. The URI format is: scheme://[username:password@]host/path Supported URI schemes are: file, flash, extension, system, ftp, http, https and tftp. username and password may be required for a network URI scheme (e.g. ftp). For convenience, two aliases are supported: startup-config -> flash://startup-config running-config -> system://running-configrw DisplayString .1.3.6.1.4.1.30065.3.7.1.1.3 |
aristaConfigCopyDestUriThe destination URI of a copy request. It has the same format as the source URI.rw DisplayString .1.3.6.1.4.1.30065.3.7.1.1.4 |
aristaConfigCopyStateThe state of a copy request.ro ConfigCopyState .1.3.6.1.4.1.30065.3.7.1.1.5 |
aristaConfigCopyTimeoutThe 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.rw Unsigned32 .1.3.6.1.4.1.30065.3.7.1.1.6 |
aristaConfigCopyTimeStartedThe time when a copy request was started.ro DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.30065.3.7.1.1.7 |
aristaConfigCopyTimeCompletedThe time when a copy request was completed.ro DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.30065.3.7.1.1.8 |
aristaConfigCopyFailureCauseThe cause of a failed copy request.ro ConfigCopyFailureCause .1.3.6.1.4.1.30065.3.7.1.1.9 |
aristaConfigCopyFailureMessageThe details of a failed copy request.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.30065.3.7.1.1.10 |
aristaConfigCopyRowStatusThe row status of a copy request. A new copy request is instantiated by creating a new row. An existing copy request is queued by activating a row, or cancelled by destroying a row.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.30065.3.7.1.1.11 |
aristaConfigCopyConformance OBJECT IDENTIFIER .1.3.6.1.4.1.30065.3.7.2 |
aristaConfigCopyCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.30065.3.7.2.1 |
aristaConfigCopyComplianceThe compliance statement for SNMP entities which implement the ARISTA-CONFIG-COPY-MIB. Unknown .1.3.6.1.4.1.30065.3.7.2.1.1 |
aristaConfigCopyGroups OBJECT IDENTIFIER .1.3.6.1.4.1.30065.3.7.2.2 |
aristaConfigCopyObjectsGroupThe collection of objects in the ARISTA-CONFIG-COPY-MIB. Unknown .1.3.6.1.4.1.30065.3.7.2.2.1 |