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 Patch Installation that Takes Effect at the Next Startup

Performing Patch Installation that Takes Effect at the Next Startup

Performing patch installation that takes effect at the next startup can optimize device performance and add new features to the device.

Applicable Environment

To optimize device performance or add new features to a device, use either of the following methods to install a patch file:
  • Performing in-service patch installation: The patch files take effect after a command is run, without having to restart the device. For details, see Performing In-service Patch Installation.
  • Performing patch installation that takes effect at the next startup: The patch files take effect after the device has been restarted.
NOTE:

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

Pre-configuration Tasks

Before performing patch installation that takes effect at the next startup, complete the following task:
  • Logging in to a device where patch installation needs to be performed

Configuration Procedures

Figure 22-3 Flowchart for performing patch installation that takes effect at the next startup

Specifying the Patch to Be Loaded at the Next Startup

If the patch file uploaded to the storage medium does not need to take effect immediately, you can specify the uploaded patch file as the one to be used at the next startup. Then, the patch file will take effect after the device is restarted.

Procedure

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

    The patch file to be loaded at the next startup is specified for all main boards. file-name is suffixed with .pat.

Follow-up Procedure

To prevent the specified patch file from taking effect at the next startup, run the reset patch-configure command to reset the patch file to be used at the next startup.

Restarting a Device

The specified patch file 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 Patch Installation that Takes Effect at the Next Startup

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   NE20EV800R010C10.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   NE20EV800R010C10.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    : 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: 14640

Downloads: 26

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