< Home

Upgrading an AS

Context

ASs in an SVF system can be manually upgraded on the parent.

  • The files used to upgrade an AS are often saved in the root directory unimng/ of the parent. These files can also be saved on an AS when the AS is upgraded or downgraded to the software version that is consistent with that of the parent.

  • To upgrade an AS, you must configure the FTP or SFTP server function on the parent so that the AS can download the related upgrade files from the parent.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run uni-mng

    The uni-mng view is displayed.

  3. Run upgrade { local-ftp-server | local-sftp-server } username username password password

    The local file server is configured.

    By default, no local file server is configured on the parent.

    • If the local file server is not configured, an AS cannot download upgrade files from the parent and so cannot be upgraded.

    • FTP has potential security risks, and so SFTP is recommended. If you want to use FTP, you are advised to configure ACLs to improve security. For details, see Configure the FTP ACL in "File Management" in the S2720, S5700, and S6700 V200R019C10 Configuration Guide - Basic Configuration.

    • When the file server is an FTP server, the FTP service is automatically enabled and an FTP user is created on the parent, removing the need to perform the FTP configuration.

    • When the file server type is set to SFTP, the SFTP service is not automatically enabled and no SFTP user is created on the parent. You need to manually pre-configure SFTP on the parent.

      For more details about the SFTP configuration, see File Management in the S2720, S5700, and S6700 V200R019C10 Configuration Guide - Basic Configuration.

    • After the upgrade { local-ftp-server | local-sftp-server } command is executed, the same user name and password configuration is also generated in the AAA view. If you modify the configured local user information (the user password for example) in AAA view, the version management function does not take effect.

    • If information about a user already exists in the AAA view, running this command to create the same user will change the user password in the AAA view to the configured password and change the user level to level 3. Changing the user password is allowed only when the user level of the user running this command is higher or equal to the user level configured in the AAA view. Otherwise, the command does not take effect.

    • Running this command multiple times to create new users will delete previous user information. Previous user information can be deleted only when the user level of the user running this command is higher or equal to the user level configured in the AAA view. Otherwise, the command does not take effect.

    • If a remote authentication server is used for AAA authentication, the user name and password configured using this command must also be configured on the remote authentication server.

    • If a remote authentication server is used for AAA authentication and the remote authentication server does not support FTP or SFTP, ASs will fail to be authenticated. In this case, run the authentication-scheme authentication-scheme-name command in the AAA view to create an authentication scheme and run the authentication-mode local command in the authentication scheme view to set the authentication mode to local authentication. Then, run the domain command in the AAA view to create a domain and run the authentication-scheme authentication-scheme-name command in the AAA domain view to apply the created authentication scheme to the domain. ASs can be authenticated when they use the newly created domain for local authentication.

  4. Run as type as-type { system-software system-software | patch patch } *

    Files to be loaded on an AS of the specified type are specified.

    You can run the as type command multiple times to specify different files for different types of ASs.

  5. Upgrade an AS.

    • Run upgrade as name as-name [ reload [ at time ] ]

      An AS with a specified name is upgraded.

    • Run upgrade as name-include string [ reload [ at time ] ]

      ASs of which the name contains a specified string are upgraded.

    • Run upgrade as type as-type [ reload [ at time ] ]

      An AS of a specified type is upgraded.

    • Run upgrade as all [ reload [ at time ] ]

      All ASs are upgraded.

    • The upgrade as command cannot upgrade an AS if the software file name or patch file name specified in the as type command is the same as the current or next startup software file name or patch file name of the AS.
    • The upgrade as command cannot upgrade an AS if the software file name specified in the as type command does not exist.
    • If reload is not specified during the upgrade of an AS:
      • If you specify patch patch but not system-software system-software in the as type command, the patch file is activated online immediately.
      • If you specify both patch patch and system-software system-software in the as type command and the specified system software file version is the version running on the AS, the patch file is activated online immediately.
      • If you specify both patchpatch and system-softwaresystem-software in the as type command and the specified system software file version is earlier or later than the version running on the AS, the specified system software file and patch file will be set as next startup files.

    • If reload is specified but at time is not specified during the upgrade of an AS, the AS restarts immediately after downloading upgrade files.

    • If reload and at time are specified during the upgrade of an AS, the AS restarts at the time specified by time.

Parent Topic: Maintaining an SVF System
Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >