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

NE20E-S2 V800R010C10SPC500 Configuration Guide - System Management 01

This is NE20E-S2 V800R010C10SPC500 Configuration Guide - System Management
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).
Performing Software Upgrade that Takes Effect at the Next Startup

Performing Software Upgrade that Takes Effect at the Next Startup

Software upgrade can optimize device performance and add new features.

Applicable Environment

To add new features or optimize device performance as needed, you can upgrade the current system software.

Pre-configuration Tasks

Before performing software upgrade that takes effect at the next startup, complete the following task:

  • Logging in to a device to be upgraded

Configuration Procedures

Figure 22-1 Flowchart for performing software upgrade that takes effect at the next startup

Checking the System Before the Upgrade

The system must be checked against the checklist to ensure a smooth upgrade.

Prerequisites

  • Necessary hardware has been prepared.
  • Software required for the upgrade has been obtained. The new system software (.cc file) and relevant documents for the upgrade must be obtained from Huawei.

Procedure

  1. In the user view, run display version

    The version of the system software running on the device is checked.

  2. Run the following commands to check the device status:

    • In the user view, run display health

      Memory usage of the main board on the device is displayed.

      If the value will lead upgrading the system software failed, reduce the value.

    • In the user view, run display alarm information

      Alarm information on the device is displayed.

      If alarm information is displayed in the command output, contact technical support personnel whether the device can be upgraded.

    • In the user view, run display device

      The operating status of main boards and interface boards is displayed.

      If the value of the Register field is Unregistered, the board in the specified slot cannot register. If the value of the Status field is Abnormal, the board in the specified slot functions improperly.

    • In the user view, run display logfile path

      The log file information is recorded.

      If a fault failed to be located during the upgrade, contact technical support personnel for troubleshooting.

  3. Prepare the environment of upgrading the system software using FTP or TFTP. The current resource file can be backed up and the new resource file can be uploaded.

    When upgrading the system software using FTP, note the following points:

    • If the device to be upgraded functions as a client and the PC functions as a server, install FTP server software on the PC. The software needs to be purchased and installed separately.
    • If the device to be upgraded functions as a server and the PC functions as a client, you do not need to install FTP server software on the PC. The device to be upgraded can provide the FTP server function. By default, the FTP server function is disabled on the device to be upgraded. To enable it, run the ftp server enable command in the system view.

    When upgrading the system software using TFTP, you must install TFTP server software on the PC. This is because the device to be upgraded can only function as a client and does not provide the TFTP server function.

  4. In the user view, run copy source-filename destination-filename

    Back up key data in the storage medium of the device to be upgraded.

  5. In the user view, run dir [ /all ] [ filename ]

    Check the remaining space of the storage medium to ensure that there is sufficient space for saving the target system software and related documents.

Uploading the System Software

To add new features or optimize features on a device, upgrading the system software to the latest version is required. You need upload the system software before upgrading it.

Context

Before uploading the system software, ensure that there is sufficient space in the storage medium for saving the system software on the AMB and SMB.

NOTE:
  • Ensure that the system software on the AMB and SMB is identical. Otherwise, the upgrade fails.
  • Ensure that files to be uploaded are correct. Verify this by checking file size and date information.

Procedure

  1. Upload the system software to the storage medium of the AMB. For detailed procedures, see File System Management.
  2. In the user view, run copy source-filename destination-filename

    The system software is copied to the storage medium of the SMB.

Specifying the System Software to Be Used at the Next Startup

Specifying the system software to be used at the next startup ensures that the device runs the new system software after being restarted.

Context

Before specifying system software to be used at the next startup, make sure that there is no running patch in the system. Otherwise, the system software cannot be upgraded.

Before the version upgrade, you can run the upgrade rollback enable rollback-timer time-value command in the user view to enable the version rollback function and set a timeout period for version rollback during version upgrade. After the timeout period is set, the system will perform version rollback if no users log in to the device during the set timeout period.

The display upgrade rollback command displays whether the version rollback function is enabled on a device.

Before the startup, run the check system-software command to verify the digital signature and check whether the target software is secure and available. The execution of this command lasts for about 3 to 10 minutes.

Procedure

  1. Run display patch-information

    The patches in the running state are checked.

  2. (Optional) In the user view, run:

    patch delete all

    All running patches are deleted.

    NOTE:

    If there are running patches in the system, perform this step. Otherwise, go to the next step.

  3. In the user view, run startup system-software system-file

    The system software to be used on the AMB at the next startup is specified.

    system-file indicates the file name of the system software, which is in the format of *.cc.

  4. In the user view, run startup system-software system-file slave-board

    The system software to be used on the SMB at the next startup is specified.

    system-file indicates the file name of the system software, which is in the format of *.cc.

    NOTE:

    During the next restart, ensure that the master and slave OMUs use the same system software. Otherwise, the reboot operation fails to be performed.

    • Before you specify a next startup configuration file for the system without configurations, you must run the save command to save the current configurations.

    • When you need to specify a configuration file with new hardware information as the next startup configuration file, you must install the new hardware and activate it, and then run the save command to save the hardware configurations.

    • The current version does not allow you to transfer the hardware configuration file (device.sys) of one device to another device and then immediately restart that device. If you do so, the hardware on that device cannot be registered.

Follow-up Procedure

If you want a PAF file to be loaded and run after the system restarts, you can run the startup paf { default | file-name } command to specify the PAF file to be used at the next startup.

Restarting a Device

The specified system software to be used at the next startup will take effect only after the device is restarted.

Procedure

  1. In the user view, run reboot

    The device is restarted.

Verifying the Configuration of Software Upgrade that Takes Effect at the Next Startup

After specifying the system software to be used at the next startup, you can check whether the upgrade is successful.

Prerequisites

The configuration of specifying the system software to be used at the next startup is complete.

Procedure

  • In the user view, run the dir file-name command to check whether the file name (*.cc) of the system software saved on the AMB and SMB is the same as that of the uploaded system software.
  • Run the display startup command to check whether the file name in the "Startup system software" field is the same as that of the specified system software.

Example

Run the dir file-name command, and you can view information about files in the storage medium on the AMB and SMB.

# Display information about files in the storage medium on the AMB. For example:
<HUAWEI> dir cfcard:
Directory of cfcard:/

  Idx  Attr     Size(Byte)  Date        Time(LMT)  FileName
    0  -rw-      1,010,368 Aug 30 2010  20:34:40   vrpcfg.db
    1  -rw-          2,602 Aug 31 2010  11:14:09   aa.cfg
    2  -rw-    245,552,377 Aug 30 2010  10:38:34   NE20EV800R010C10.cc
    3  -rw-        105,761 Aug 30 2010  11:43:12   paf.txt
    4  -rw-         14,894 Aug 30 2010  11:43:24   license.txt
    5  -rw-            972 Aug 30 2010  06:39:14   vrpcfg-223.cfg
    6  -rw-          2,028 Aug 30 2010  11:52:22   all.dat
    7  -rw-        330,661 Aug 30 2010  20:12:33   V800R010C10SPH001.pat

26,201,748 KB total (20,628,940 KB free)
# Display information about files in the storage medium on the SMB. For example:
<HUAWEI> dir slave#cfcard:
Directory of slave#cfcard:/

  Idx  Attr     Size(Byte)  Date        Time(LMT)  FileName
    0  -rw-      1,010,368 Aug 30 2010  20:34:40   vrpcfg.db
    1  -rw-          2,602 Aug 31 2010  11:14:09   aa.cfg
    2  -rw-    245,552,377 Aug 30 2010  10:38:34   NE20EV800R010C10.cc
    3  -rw-        105,761 Aug 30 2010  11:43:12   paf.txt
    4  -rw-         14,894 Aug 30 2010  11:43:24   license.txt
    5  -rw-            972 Aug 30 2010  06:39:14   vrpcfg-223.cfg
    6  -rw-          2,028 Aug 30 2010  11:52:22   all.dat
    7  -rw-        330,661 Aug 30 2010  20:12:33   V800R010C10SPH001.pat

26,201,748 KB total (20,628,940 KB free)

Run the display startup command, and you can view the system software to be loaded at the next startup. For example:

<HUAWEI> display startup
MainBoard                               :
  Configured startup system software    : NE20EV800R010C10.cc
  Startup system software             : NE20EV800R010C10.cc
  Next startup system software          : NE20EV800R010C10.cc
  Startup saved-configuration file      : cfcard:/aa.cfg
  Next startup saved-configuration file : cfcard:/aa.cfg
  Startup paf file                      : default 
  Next startup paf file                 : PAF_400k.bin 
  Startup patch package                 : cfcard:/V800R010C10SPH001.pat
  Next startup patch package            : cfcard:/V800R010C10SPH001.pat
SlaveBoard                              :
  Configured startup system software    : NE20EV800R010C10.cc
  Startup system software             : NE20EV800R010C10.cc
  Next startup system software          : NE20EV800R010C10.cc
  Startup saved-configuration file      : cfcard:/aa.cfg
  Next startup saved-configuration file : cfcard:/aa.cfg
  Startup paf file                      : default 
  Next startup paf file                 : PAF_400k.bin 
  Startup patch package                 : cfcard:/V800R010C10SPH001.pat
  Next startup patch package            : cfcard:/V800R010C10SPH001.pat
Translation
Download
Updated: 2019-01-02

Document ID: EDOC1100055400

Views: 14538

Downloads: 26

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