17.1.3 Update Precautions

(1) Notes on file transfer

Transfer the update file to /usr/var/update directory on the Switch using the file name k.img. If the file already exists, it overwrites the existing file. Depending on the access privileges of the file, it may not be possible to overwrite k.img file created by another user*. If this happens, use the operation-command rm to delete k.img file. Then, transfer the file. If the transfer destination and file name are incorrect, delete the incorrect file and transfer it again.

#: If the file was created by a user who has already been deleted by an operation command rmuser, the file owner is displayed as a number when detailed information is displayed in the operation command ls.

(2) Notes on Copying Files from MC

• Use our product for MC.

• Store the update file in MC using a PC in advance.

(3) Notes on executing the update command

• If the update command terminates abnormally, execute the following command to check for the presence of ppupdate.exec filename:

  ls /tmp/ppupdate.exec

  If the file exists, use the operation command rm to remove the file.

  For a stacked configuration, use the operation-command remote command to check and remove files. This is not the master switch.

• The update command cannot be executed concurrently by multiple users. When this command is executed, the message "another user is executing now" is displayed and the command terminates abnormally.

• The update command cannot be executed in the configuration command mode.

• Do not remove k.img filename. You will not be able to recover the file when it terminates abnormally.

• Do not turn OFF the power while the update is in progress. If the power is turned OFF, reboot and run the update again from the beginning.

• The configuration saved in the internal flash memory will be inherited by the updated version. If an update is performed with a large number of saved configurations, it may take a long time to take over the configuration.

  When downgrading, delete the unsupported configuration in advance. If you perform a version down without deleting an unsupported configuration, the stack configuration does not match between the member switches in the stack configuration, and the member switch cannot be configured. On a stand-alone device, an unintended network may be built because unsupported configurations are deleted and used.