Managing Images and Files 369! Display information about direct connectionsshow serial! End of the script fileManaging Files on a StackImage files downloaded to the master unit of a stack are automaticallydownloaded to all stack members. If you activate the backup image on themaster, it is activated on all units as well so that when you reload the stack, allunits use the same image.The running-config, startup-config, and backup-config files, as well as all keysand certificates are synchronized across the stack when the running-configfile is saved to the startup-config file.Configuration scripts are not distributed across the stack and only exist onthe unit that is the master unit at the time of the file download.Uploading Configuration Files by Using SNMPWhen you use SNMP to upload a configuration file to a TFTP server, theagentTransferUploadFileName object must be set to the local filename,which is either startup-config or backup-config.How Is the Running Configuration Saved?Changes you make to the switch configuration while the switch is operatingare written to the running-config. These changes are not automaticallywritten to the startup-config. When you reload the switch, the startup-configfile is loaded. If you reload the switch (or if the switch resets unexpectedly),any settings in the running-config that were not explicitly saved to thestartup-config are lost. You must save the running-config to the startup-config to ensure that the settings you configure on the switch are saved acrossa switch reset.To save the running-config to the startup-config by using the web-basedinterface, click (the save icon), which is available at the top of each page.To save the running-config to the startup-config from the CLI, use the writecommand.
