! Display information about direct connections
! End of the script file
Managing Files on a Stack
Image files downloaded to the master unit of a stack are automatically
downloaded to all stack members. If you activate the backup image on the
master, it is activated on all units as well so that when you reload the stack, all
units use the same image.
The running-config, startup-config, and backup-config files, as well as all keys
and certificates are synchronized across the stack when the running-config
file is saved to the startup-config file.
Configuration scripts are not distributed across the stack and only exist on
the unit that is the master unit at the time of the file download.
Uploading Configuration Files by Using SNMP
When you use SNMP to upload a configuration file to a TFTP server, the
agentTransferUploadFileName 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 operating
are written to the running-config. These changes are not automatically
written to the startup-config. When you reload the switch, the startup-config
file 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 the
startup-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 across
a switch reset.
To save the running-config to the startup-config by using the web-based
(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 write
Managing Images and Files