How to better run the switch configuration file

To effectively manage the switch configuration file, you must run the copy command in a timely manner and in an appropriate location. By using the copy command, IOS software can move the configuration file from one component or device to another required component and device.

This command mainly has two parameters. The first parameter indicates the source location of the configuration file, that is, the file to be copied. The second parameter indicates the target location, that is, the location where the configuration file is to be copied. If you use the copy running-config tftp command, you can copy the running configuration file to the TFTP server on the network for configuration.

However, during replication, note that if the target location has the same configuration file, this command overwrites the configuration file with the same name in the target file. However, this sentence is easy, but it is difficult to do it. Specifically, you need to do the following.

First, after the switch configuration file in RAM is changed, you need to back up the latest running configuration file. This is mainly because the content in the RAM memory will be lost after power failure. If the network administrator wants to make changes to the vswitch during its operation, the change will remain valid at the next startup.

You need to save the changed content in the startup configuration file. To achieve this, run copy running-config startup-config. This command saves the running configuration file to the startup Switch configuration file. In this case, the latest update of the vswitch is saved.

Note that when copying the running configuration file in RAM to NVRAM, you must ensure the accuracy of the current configuration. That is to say, when we modify the parameters related to the running configuration file in RAM, we generally do not rush to copy the relevant content to NVRAM.

Instead, we need to test and track the new parameters to determine whether they meet our expected needs. That is, to determine whether the new parameter has taken effect and whether it meets the user's needs. This update can be saved to the startup configuration file only when the new configuration parameter runs normally.

Otherwise, if this parameter is set incorrectly, problems may occur during the next startup. For the sake of security, it is best to back up the content in NVRAM before copying the running configuration file to NVRAM.

This is mainly because when the copy running-config startup-config command is used, the command will automatically overwrite the startup configuration file at the target location. At this time, if the configuration file is running incorrectly, even the gods will be unable to go back to the sky. For this reason, the author sets up a network administrator. When managing configuration files, be careful and take another step.

For example, before saving the update, back up the original STARTUP configuration file on the tftp server. In this case, even if the latest configuration is incorrect and the network administrator saves it, you can use the backup configuration file to start the switch.

To complete this function, the network administrator can run the copy start tftp Command to save the startup configuration file to the TFTP server ). If there is a problem with the startup configuration file, you can also use the copy tftp start command to copy the backup configuration file to NVRAM so that the switch can use this configuration file for initialization.

Third, in addition to mutual replication between NVRAM and the tftp server, mutual replication can also be performed between RAM and the tftp server. For example, the network administrator updates a parameter in the switch configuration file, such as setting a virtual LAN.

In this case, it may be difficult to determine whether the current configuration is accurate in a short time. It may take a week or longer to make a decision. In this case, it is better not to update the content in the startup configuration file easily. The recommended method is to copy the running configuration file in RAM to the tftp server to implement a temporary transition.

After confirming that the configuration is correct, copy and replace the running configuration file to save the latest available updates. To achieve this, run the copy run tftp Command (copy the running configuration file to the tftp server) or run the copy tftp run Command to copy the configuration file on the tftp server to ram.

I 'd better emphasize that how to configure and run the configuration file or initial parameter file involves a lot of content, which is very difficult. However, if you manage the configuration file, the copy command is the core. The key to using this command is to back up the vswitch configuration file before making any changes. After ensuring that the update content is available, save it to the NVRAM that is not easy to lose after power failure or the tftp server on the network.