Dynamic Configuration Loading - HP 9304m Installation And Getting Started Manual

5. Enter the address of the TFTP server in the TFTP Server IP field.
6. Enter the configuration file name in the Configuration File Name field.
7. Click on one of the following buttons to start the file transfer:
• Copy from Server to Flash – downloads the configuration file from the TFTP server into the device's
flash. (The flash area holds only one configuration file, so you cannot specify a primary or secondary
save location for the file.)
• Save from Flash to Server – uploads the startup-config file (the configuration file) to the TFTP server
using the name you entered in the Configuration File Name field.
• Save from RAM to Server – uploads the running-config file to the TFTP server using the name you
entered in the Configuration File Name field. The running-config file contains the active system
configuration, which may not match the contents of the startup-config file if you have made configuration
changes but not saved them to flash. To synchronize the running-config and startup-config files, use the
procedure in "Replacing the Startup Configuration with the Running Configuration" on page 10-7.
NOTE: While TFTP transfers are in process, a red bar labeled "processing" is displayed on the screen. When
the TFTP transfer is actively transferring image or configuration data, a green bar labeled "loading" is displayed.
When a successful transfer is complete, the message "TFTP transfer complete" is displayed.
If a problem with the transfer occurs, one of the error codes listed in "Diagnostic Error Codes and Remedies for
TFTP Transfers" on page 10-14 is displayed.

Dynamic Configuration Loading

You can load dynamic configuration commands (commands that do not require a reload to take effect) from a file
on a TFTP server into an HP device's running-config. You can make configuration changes off-line, then load the
changes directly into the device's running-config, without reloading the software.
Usage Considerations
• Use this feature only to load configuration information that does not require a software reload to take effect.
For example, you cannot use this feature to change statically configured memory (system-max command) or
to enter trunk group configuration information into the running-config.
• Do not use this feature if you have deleted a trunk group but have not yet placed the changes into effect by
saving the configuration and then reloading. When you delete a trunk group, the command to configure the
trunk group is removed from the device's running-config, but the trunk group remains active. To finish deleting
a trunk group, save the configuration (to the startup-config file), then reload the software. After you reload the
software, then you can load the configuration from the file.
• Do not load port configuration information for secondary ports in a trunk group. Since all ports in a trunk
group use the port configuration settings of the primary port in the group, the software cannot implement the
changes to the secondary port.
Updating Software Images and Configuration Files
10 - 9