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

NE40E-M2 V800R010C10SPC500 Configuration Guide - System Management 01

This is NE40E-M2 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 In-Service Patch Installation

Performing In-Service Patch Installation

Performing in-service patch installation on a device allows the current system software on the device to be upgraded without service interruption.

Applicable Environment

You can use either of the following methods to install patches:
  • Performing in-service patch installation: The patch files take effect after a command is run, without having to restart the device.
  • Performing patch installation that takes effect at the next startup: The installed patch files take effect after the device is restarted. For details, see Performing Patch Installation that Takes Effect at the Next Startup.
NOTE:

This feature is supported only on the Admin-VS but takes effect on all VSs.

Pre-configuration Tasks

Before performing in-service patch installation, complete the following task:
  • Logging in to a device to be upgraded

Configuration Procedures

Figure 22-2 Flowchart for performing in-service patch installation

Installing a Patch File

After a patch file has been uploaded to the storage medium of a device, the patch file needs to be installed to the patch area in the memory.

Context

The system that is just started successfully needs to perform internal restoration. Installing or uninstalling a patch during the restoration process may fail. In this situation, run the display current-configuration command to check whether the internal restoration has completed. If the command output contains current configurations, the internal restoration has completed, and you can install or uninstall a patch as needed.

Before installing the patch, you can run the set patch cpu-usage threshold command to configure a CPU usage overload threshold so that CPU resources are released if the CPU usage on a board exceeds the threshold during patch installation.

Procedure

  1. In the user view, run patch load file-name all run

    The patch file is loaded.

    NOTE:

    When a patch file is loaded, the system checks whether the patch version is the same as the system software version. If the patch file version is different from the system software version, the system prompts that the patch file loading fails.

    If there are running patch files in the system during non-incremental patching, the system displays a patch file installation failure. The patch delete all command needs to be run to delete the running patch files.

Follow-up Procedure

If a patch file needs to be deleted after having been installed, run the patch delete all command.

Running the patch delete all command will delete all patch files.

Verifying the Configuration of In-Service Patch Installation

This section describes how to check whether a patch file has been installed onto a device.

Procedure

  • Run the dir file-name command in the user view to check whether the uploaded patch file (*.PAT) is included in the information displayed on the AMB and SMB.
  • Run the display patch-information command to check whether the installed patch file is in the running state.
  • Run the display startup command to check whether the next startup patch file is the file that you have configured.

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 2016  20:34:40   vrpcfg.db
    1  -rw-          2,602 Aug 31 2016  11:14:09   aa.cfg
    2  -rw-    245,552,377 Aug 30 2016  10:38:34   NE40EV800R010C10.cc
    3  -rw-        105,761 Aug 30 2016  11:43:12   paf.txt
    4  -rw-         14,894 Aug 30 2016  11:43:24   license.txt
    5  -rw-            972 Aug 30 2016  06:39:14   vrpcfg-223.cfg
    6  -rw-          2,028 Aug 30 2016  11:52:22   all.dat
    7  -rw-        330,661 Aug 30 2016  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 2016  20:34:40   vrpcfg.db
    1  -rw-          2,602 Aug 31 2016  11:14:09   aa.cfg
    2  -rw-    245,552,377 Aug 30 2016  10:38:34   NE40EV800R010C10.cc
    3  -rw-        105,761 Aug 30 2016  11:43:12   paf.txt
    4  -rw-         14,894 Aug 30 2016  11:43:24   license.txt
    5  -rw-            972 Aug 30 2016  06:39:14   vrpcfg-223.cfg
    6  -rw-          2,028 Aug 30 2016  11:52:22   all.dat
    7  -rw-        330,661 Aug 30 2016  20:12:33   V800R010C10SPH001.PAT

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

Run the display patch-information command, and you can view whether the installed patch file is in the running state. For example:

<HUAWEI> display patch-information
Patch Package Name    :cfcard:/V800R010C10SPH001.PAT
Patch Package Version :V800R010C10SPH001
Patch Package State   :Running   
Patch Package Run Time:2011-11-07 11:55:01

Run the display startup command, and you can view whether the next startup patch file is the patch you have configured. For example:

<HUAWEI> display startup
MainBoard                               :
  Configured startup system software    : NE40EV800R010C10.cc
  Startup system software               : NE40EV800R010C10.cc
  Next startup system software          : NE40EV800R010C10.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    : NE40EV800R010C10.cc
  Startup system software               : NE40EV800R010C10.cc
  Next startup system software          : NE40EV800R010C10.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
Download
Updated: 2019-01-02

Document ID: EDOC1100058392

Views: 18369

Downloads: 31

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