ARISTA-CONFIG-COPY-MIB

All MIBs › ARISTA-CONFIG-COPY-MIB

Organization: Arista Networks, Inc.

Last Updated: 2014-08-15

Category: Vendor: Arista

Description: Arista EOS configuration file copy and transfer operation management.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is ARISTA-CONFIG-COPY-MIB?

ARISTA-CONFIG-COPY-MIB is a vendor-specific MIB from Arista Networks (EOS) for managing configuration file copy/transfer operations between a source and destination URI, covering local files, flash, running-config, startup-config, and remote schemes such as ftp/http/https/tftp. It exposes a command table representing each requested copy operation along with its lifecycle status and outcome, rather than continuous performance counters. Its monitoring value is operational/software status: aristaConfigCopyState tracks whether a copy is in progress, succeeded, or failed, and aristaConfigCopyFailureCause/aristaConfigCopyFailureMessage reveal exactly why a configuration backup or restore operation failed. It relies on standard SNMP conformance conventions (its own compliance/group objects) but is otherwise a self-contained Arista-specific tool MIB. It is used on Arista EOS switches for automating and auditing configuration backups, restores, or firmware/config distribution via SNMP-driven tooling. Engineers can download the ARISTA-CONFIG-COPY-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in ARISTA-CONFIG-COPY-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Arista Networks EOS switch

Monitoring Examples

An administrator would create an entry in aristaConfigCopyCommandTable specifying aristaConfigCopySourceUri (e.g., the running-config) and aristaConfigCopyDestUri (e.g., an tftp:// backup server), then poll aristaConfigCopyState until it reports completion. If aristaConfigCopyState shows failure, aristaConfigCopyFailureCause and aristaConfigCopyFailureMessage identify the reason, such as an unreachable server or authentication failure. aristaConfigCopyTimeStarted and aristaConfigCopyTimeCompleted let an operator confirm the copy completed within an expected window, and aristaConfigCopyTimeout is checked when an operation appears to hang.

What Can Be Monitored

configuration copy operation state (in progress/success/failure)
failure cause and message
copy start and completion time
source/destination URI
operation timeout setting

Imported Objects

From ARISTA-SMI-MIB

aristaMibs	OBJECT-IDENTITY
aristaModules	OBJECT-IDENTITY
aristaProducts	OBJECT-IDENTITY

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

MODULE-IDENTITY
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

DateAndTime
DisplayString
RowStatus
TEXTUAL-CONVENTION

OIDs

OID symbolic	OID numeric	Type	Access	Description
aristaConfigCopyMIB	1.3.6.1.4.1.30065.3.7			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.
aristaConfigCopyCommandTable	1.3.6.1.4.1.30065.3.7.1		not-accessible	A 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.
aristaConfigCopyCommandEntry	1.3.6.1.4.1.30065.3.7.1.1		not-accessible	A 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.
STR aristaConfigCopyName	1.3.6.1.4.1.30065.3.7.1.1.1	DisplayString	not-accessible	The 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.
U32 aristaConfigCopyId	1.3.6.1.4.1.30065.3.7.1.1.2	Unsigned32	not-accessible	The 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).
STR aristaConfigCopySourceUri	1.3.6.1.4.1.30065.3.7.1.1.3	DisplayString	read-create	The 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-config
STR aristaConfigCopyDestUri	1.3.6.1.4.1.30065.3.7.1.1.4	DisplayString	read-create	The destination URI of a copy request. It has the same format as the source URI.
CON aristaConfigCopyState	1.3.6.1.4.1.30065.3.7.1.1.5	ConfigCopyState	read-only	The state of a copy request.
U32 aristaConfigCopyTimeout	1.3.6.1.4.1.30065.3.7.1.1.6	Unsigned32	read-create	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.
DAT aristaConfigCopyTimeStarted	1.3.6.1.4.1.30065.3.7.1.1.7	DateAndTime	read-only	The time when a copy request was started.
DAT aristaConfigCopyTimeCompleted	1.3.6.1.4.1.30065.3.7.1.1.8	DateAndTime	read-only	The time when a copy request was completed.
CON aristaConfigCopyFailureCause	1.3.6.1.4.1.30065.3.7.1.1.9	ConfigCopyFailureCause	read-only	The cause of a failed copy request.
STR aristaConfigCopyFailureMessage	1.3.6.1.4.1.30065.3.7.1.1.10	DisplayString	read-only	The details of a failed copy request.
ROW aristaConfigCopyRowStatus	1.3.6.1.4.1.30065.3.7.1.1.11	RowStatus	read-create	The 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.
aristaConfigCopyConformance	1.3.6.1.4.1.30065.3.7.2
aristaConfigCopyCompliances	1.3.6.1.4.1.30065.3.7.2.1
aristaConfigCopyCompliance	1.3.6.1.4.1.30065.3.7.2.1.1			The compliance statement for SNMP entities which implement the ARISTA-CONFIG-COPY-MIB.
aristaConfigCopyGroups	1.3.6.1.4.1.30065.3.7.2.2
aristaConfigCopyObjectsGroup	1.3.6.1.4.1.30065.3.7.2.2.1			The collection of objects in the ARISTA-CONFIG-COPY-MIB.

RFC description

Configuration copy operations between running-config, startup-config, and network locations on switches.

Start monitoring Arista Networks EOS switches with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download ARISTA-CONFIG-COPY-MIB

What Is ARISTA-CONFIG-COPY-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description