fileCopyAction - file Copy Action - CISCO-STACK-MIB

MIBs list

With IPHost Network Monitor you can run simple snmp requests against a Cisco device in your network.

fileCopyAction

file Copy Action
1.3.6.1.4.1.52.4.12.30.1.24.1.8

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).

Back to CISCO-STACK-MIB MIB page.

IPHost Network monitor allows you to monitor fileCopyAction on Cisco device via the SNMP protocol. Download IPHost Network Monitor (500 monitors for 30 days, 50 monitors free forever) to start monitoring Cisco firewalls right now.

Easy monitoring of fileCopyAction with IPHost tools

MIBs list