CISCO-STACK-MIB :: fileCopyAction

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-STACK-MIBfileCopyAction

fileCopyAction

Module: CISCO-STACK-MIB

OID (symbolic): CISCO-STACK-MIB::fileCopyAction

OID (numeric): 1.3.6.1.4.1.9.5.1.25.7

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: Setting this object to one of the acceptable values will initiate the requested action using the information provided by fileCopyProtocol, fileCopyRemoteServer, fileCopySrcFileName, fileCopyDstFileName,fileCopyModuleNumber and fileCopyUserName.

copyConfigFromHostToRuntime(2): Copy the configuration file from host to runtime configuration over the network through tftp/rcp. This action will use fileCopyProtocol, fileCopyRemoteServer, fileCopySrcFileName, fileCopyModuleNumber, and fileCopyUserName (if applicable).

copyConfigFromRuntimeToHost(3): Copy the runtime configuration to host over the network through tftp/rcp. This action will use fileCopyProtocol, fileCopyRemoteServer, fileCopyModuleNumber, fileCopyDstFileName, fileCopyUserName (if applicable), and fileCopyRuntimeConfigPart.

copyImageFromHostToFlash(4): Copy the image from host to the flash over the network through tftp/rcp. It is up to the SNMP agent to reset and run the downloaded image after copying. This action will use fileCopyProtocol, fileCopyRemoteServer, fileCopySrcFileName, fileCopyModuleNumber, and fileCopyUserName (if applicable).

copyImageFromFlashToHost(5): Copy the image from flash to host over the switch through tftp/rcp. This action will use fileCopyProtocol, fileCopyRemoteServer, fileCopyDstFileName, fileCopyModuleNumber, and fileCopyUserName (if applicable).

copyConfigFromFlashToRuntime(8): Copy the configuration file to the runtime configuration locally. This action can perform only on the SUPG supervisor model and will use fileCopySrcFileName ('cfg1' or 'cfg2').

copyConfigFromRuntimeToFlash(9): Copy the runtime configuration to a configuration file on the flash locally. This action can perform only on the SUPG supervisor model and will use fileCopyDstFileName ('cfg1' or 'cfg2'), and fileCopyRuntimeConfigPart.

copyConfigFileFromHostToFlash(10): Copy the configuration file from host to the runtime configuration over the network through tftp/rcp. This action can perform only on the SUPG supervisor model and will use fileCopyProtocol, fileCopyRemoteServer, fileCopySrcFileName, fileCopyDstFileName, fileCopyModuleNumber and fileCopyUserName (if applicable).

copyConfigFileFromFlashToHost(11): Copy the configuration file on the flash to host over the network through tftp/rcp. This action can perform only on the SUPG supervisor model and will use fileCopyProtocol, fileCopyRemoteServer, fileCopySrcFileName, fileCopyDstFileName, fileCopyModuleNumber and fileCopyUserName (if applicable).

copyTechReportFromRuntimeToHost(12): Copy the technical report of the system to host over the network through tftp only. This action will use fileCopyProtocol, fileCopyRemoteServer, fileCopyModuleNumber, and fileCopyDstFileName.

Setting this object to any other value results in an error.

The value of this object can not be changed when the fileCopyResult object has the value of inProgress(1).

What is fileCopyAction?

Read-write control object that triggers a file-copy operation (such as downloading an image or configuration) using the protocol, server, and filename parameters set in related MIB objects.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.5.1.25.7
snmpwalk -v2c -c public <target> CISCO-STACK-MIB::fileCopyAction

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.5.1.25.7.1
snmpget -v2c -c public <target> CISCO-STACK-MIB::fileCopyAction.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.9.5.1.25.7.1 i <value>

Start monitoring Cisco Catalyst switch (legacy/mid-generation) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-STACK-MIB::fileCopyAction OID value, configure state conditions and alerts, and monitor any Cisco Catalyst switch (legacy/mid-generation) from a single console.

OID Breakdown

Upper-level ancestors (8 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.9ciscoCAT2600-MIB
1.3.6.1.4.1.9.5workgroupCISCO-ES-STACK-MIB
Numeric OIDNameModule
1.3.6.1.4.1.9.5.1ciscoStackMIBCISCO-STACK-MIB
1.3.6.1.4.1.9.5.1.25fileCopyGrpCISCO-STACK-MIB
1.3.6.1.4.1.9.5.1.25.7fileCopyActionCISCO-STACK-MIB