No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

S12700 V200R013C00 Configuration Guide - Basic Configuration

This document describes the configurations of Basic, including CLI Overview, EasyDeploy Configuration, USB-based Deployment Configuration, Logging In to a Device for the First Time, CLI Login Configuration, Web System Login Configuration, File Management, Configuring System Startup, ISSU Configuration, BootLoad Menu Operation.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuring System Startup Files

Configuring System Startup Files

Pre-configuration Tasks

Specify the system software and configuration file for system startup so that the device will start and initialize with the specified software and configuration file. Specify new patch files if the system needs to load new patches.

Before configuring the system startup files, complete the following tasks:
  • Start the device and log in to the device locally or remotely.
  • Save the system startup files to the root directory of the device.

Context

Before specifying the files for next startup, you can run the display startup command to view the specified files for next startup.
  • If no system software is specified for next startup, the device will start with current system software. To change the system software to be loaded for next startup (during an upgrade for example), upload the new system software to the device and specify it as the system file for next startup. The system software package must use .cc as the file name extension and be saved to the root directory of the storage device. If the device has double MPUs, save the system software in the master MPU. When the system software is specified for the slave MPU, the device automatically copies the system software to the slave MPU.
  • When the system software for next startup is configured, the system checks the system software integrity. If the digital signature of the system software is invalid, the configuration fails. Therefore, ensure the system software validity.
  • If no configuration file is specified for next startup, the device will start with the default configuration file (vrpcfg.zip for example). If no configuration file is stored in the default directory, the device uses the default parameters for initialization. The configuration file name extension must be .cfg or .zip. In addition, the configuration file must be saved to the root directory of the storage device.
  • The patch file name extension must be .pat. The specified patch file to be loaded for next startup must be saved to the root directory of the storage device. If the device has double MPUs, the patch file must be manually copied to the slave MPU using the copy source-filename destination-filename command after being uploaded to the master MPU. This ensures that the patch file is saved in both locations.
  • Do not change the configuration file manually and specify the configuration file for next startup. Otherwise, the device may not start normally.

Procedure

  • (Optional) Run check file-integrity filename signature-filename

    The system software validity is checked.

    NOTE:

    You need to upload the system software and corresponding signature file to the switch before using this command.

    You can also run this command to check a patch file.

  • Run startup system-software system-file

    The system software to be loaded for next startup is specified.

    If the device has dual MPUs, run the startup system-software system-file slave-board command to specify the system software for the slave MPU to load during the next startup.

    NOTE:

    Specify the same system software for the master and slave MPUs.

    If the specified system software is V200R005 or earlier (excluding V200R005C02), run the reset boot password command to restore the default BootLoad password and then specify the system software.

  • Run startup saved-configuration configuration-file

    The configuration file for next startup is specified.

    The device reads the configuration file from the root directory of the storage device for initialization when powered on.

  • (Optional) Run startup patch patch-name [ slave-board ]

    The patch file for next startup is specified.

    Run this command to make the patch file take effect after the device restarts.

Verifying the Configuration

After the configuration is complete, run the display startup command to view the system software, configuration file and patch file for next startup.

Translation
Download
Updated: 2019-04-08

Document ID: EDOC1100065643

Views: 10910

Downloads: 35

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next