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 V800R010C00 Configuration Guide - Virtual Access 01

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).
Upgrading and Managing an AP

Upgrading and Managing an AP

This section describes how to upgrade and manage an AP.

Background

In the virtual access solution, the control and management planes are centralized on a master. You can upgrade and manage an AP on a master, including:

  • Upgrade using a software package

  • Patch installation

  • AP restart

  • LLDP configuration

  • NTP configuration

  • Configuring APs to Communicate with an NMS over SNMP

  • Configuring APs to Send Information to a Syslog Server

After you complete configurations, the master uses the NETCONF channel to deliver the configurations to the AP and the AP automatically performs the configurations.

NOTE:
  • During a software upgrade of the virtual access system, upgrade masters and then APs. The process for upgrading a master is the same as that for upgrading a common device.

  • You can also log in to an AP to upgrade and manage it.

Pre-configuration Tasks

Before upgrading and managing an AP on a master, complete the following tasks:

Configuration Procedures

Perform one or more of the following configurations as required.

Using a Software Package to Upgrade an AP

A software package optimizes an AP's original functions, adds functions, and resolves the issue that the running version cannot be promptly updated.

Procedure

  1. Upload a software package for an upgrade to an AP. The following table describes upload methods.

    Software Package Source

    AP Range

    Command

    Master

    APs in a specified range

    upgrade download-package packagename ap-id { startapid [ to endapid ] } &<1-10>

    All APs

    upgrade download-package packagename all-ap

    Specified server

    APs in a specified range

    upgrade download-package packagename server-ip ip-address server-port port-number ap-id { startapid [ to endapid ] } &<1-10>

    All APs

    upgrade download-package packagename server-ip ip-address server-port port-number all-ap

    NOTE:
    • After upgrade download-package is run, a user must enter an SFTP user name and password as prompted for SFTP authentication between an AP and master or between an AP and specified server.

    • If the software package source is a specified server, configure the virtual access system and server to import each other's network segment route to implement connectivity between the APs and server.

    • To free up the system storage space, run the upgrade delete-package type command on the Master to delete unnecessary AP software packages.

  2. Run the display patch-information ap-id ap-id command to check whether any running patch exists on the AP.
  3. (Optional) Run the patch delete all { all-ap | ap-id { startapid [ to endapid ] } &<1-10> } command to delete the running patches on the AP.

    Before using a software package to upgrade an AP, ensure that no patches are running on the AP. If any patch is running on the AP, system software cannot be upgraded. Perform this step if any patch is running on the AP. Otherwise, skip this step.

  4. Run the startup system-software system-file { all-ap | ap-id { startapid [ to endapid ] } &<1-10> } command to configure system software for the AP's next startup.

    Parameters are described as follows:

    • all-ap: configures system software for the next startup of all APs managed by the master.

    • ap-id { startapid [ to endapid ] } &<1-10>: configures system software for the next startup of the APs in the specified range.

Follow-up Procedure

Restart the AP for the software package to take effect immediately.

Installing a Patch

You can install a patch for an AP to optimize the AP's system functions or add small requirements.

Procedure

  1. Upload a patch file to an AP. The following table describes upload methods.

    Patch File Source

    AP Range

    Command

    Master

    APs in a specified range

    upgrade download-package packagename ap-id { startapid [ to endapid ] } &<1-10>

    All APs

    upgrade download-package packagename all-ap

    Specified server

    APs in a specified range

    upgrade download-package packagename server-ip ip-address server-port port-number ap-id { startapid [ to endapid ] } &<1-10>

    All APs

    upgrade download-package packagename server-ip ip-address server-port port-number all-ap

    NOTE:
    • After upgrade download-package is run, a user must enter an SFTP user name and password as prompted for SFTP authentication between an AP and master or between an AP and specified server.

    • If the software package source is a specified server, configure the virtual access system and server to import each other's network segment route to implement connectivity between the APs and server.

    • To free up the system storage space, run the upgrade delete-package type command on the Master to delete unnecessary AP patch packages.

  2. Install the patch for the AP.
    • Install the patch without interrupting services.

      1. Run the patch load file-name all run { all-ap | ap-id { startapid [ to endapid ] } &<1-10> } command to install the patch for the AP.

        Parameter

        Description

        run

        The patch is in the running state after being installed.

        all-ap

        The patch is installed for all APs managed by the master.

        ap-id { startapid [ to endapid ] } &<1-10>

        The patch is installed for the APs in a specified range.

    • Install the patch for the next startup.

      1. Run the startup patch packagename all { all-ap | ap-id { startapid [ to endapid ] } &<1-10> } command to configure the patch for the AP's next startup.

        After the AP restarts, the patch takes effect permanently.

Follow-up Procedure

  • When the patch is installed without interrupting services:

    • To delete the installed patch that results in an exception, run the patch delete all { all-ap | ap-id { startapid [ to endapid ] } &<1-10> } command.

  • When the patch is installed for the next startup:

    • To clear the patch configuration for the next startup, run the reset patch-configure next-startup { all-ap | ap-id { startapid [ to endapid ] } &<1-10> } command.

    • Restart the AP for the patch to take effect immediately.

Restarting an AP

After configuring a software package for an AP's upgrade or a patch for an AP's next startup, restart the AP to immediately validate the software package or patch and check whether the configuration is successful.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    ap-id ap-id

    The AP view is displayed.

  3. Run:

    reboot

    The AP is restarted.

  4. Run:

    commit

    The configuration is committed.

Configuring LLDP

After LLDP is configured for APs, an NMS can obtain their topology information, capabilities, management addresses, device IDs, and interface IDs.

Context

LLDP is used to obtain neighbor information and discover network topology. To enable an NMS to collect an AP's topology information, enable LLDP for the AP on a master. After LLDP is enabled, APs send status information to one another and an NMS can obtain topology information.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    virtual-access

    The virtual access view is displayed.

  3. Run:

    lldp enable

    LLDP is enabled.

  4. Run:

    commit

    The configuration is committed.

Configuring NTP

In the virtual access system, you can configure NTP so that an AP automatically synchronizes clock information with a master.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    virtual-access

    The virtual access view is displayed.

  3. Run:

    ntp-service enable authentication-keyid key-id authentication-mode hmac-sha256 password

    NTP is enabled.

  4. Run:

    commit

    The configuration is committed.

Configuring APs to Communicate with an NMS over SNMP

To use a network management system (NMS) to manage APs, configure the APs to communicate with the NMS over SNMP on a master.

Context

In a virtual access scenario, to use an NMS to manage APs, configure SNMP in the virtual access view of a master. After the configuration, when the IP route between the NMS and an AP is reachable:

  • The AP uses a trap message to report a fault alarm to the NMS.

  • The AP records active alarms, and the NMS can use the MIB to query or synchronize the active alarms on the AP.

NOTE:
  • In a virtual access system, a master manages services on an AP. If a service on the AP fails, the master reports an alarm. If an AP fails, it independently reports a fault alarm.

  • A master communicates with an NMS over SNMP. The configuration procedure is the same as that in a common scenario.

Perform the following steps on a master.

Prerequisites

Before configuring APs to communicate with an NMS over SNMP, establish a virtual access system.

When establishing a virtual access system, configure route import between the virtual access system and external network so that the routes between the NMS and APs are reachable.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    virtual-access

    The virtual access view is displayed.

  3. Run:

    snmp-agent

    The SNMP agent service is started.

  4. Run:

    snmp-agent sys-info version { v1 | v2c } *

    An SNMP version is configured.

  5. Run:

    snmp-agent community { read | write } cipher community-name [ mib-view view-name ]

    A read/write community name is configured.

    A community is a collection of an NMS and SNMP agent and is identified using a community name. The community name acts like a password to regulate access to a managed device. An NMS can access a managed device only if the community name carried in an SNMP request sent by the NMS is the same as the community name configured on the managed device. Perform this step to configure an SNMP community name so that the NMS communicates with APs. You can also run the snmp-agent community command to set a MIB view that a community name can access.

  6. Run:

    snmp-agent target-host host-name host-name trap address udp-domain ip-address params securityname cipher cipher-name  [ [ v1 | v2c ] | private-netmanager | ext-vb ] *

    A destination is set for trap messages.

    Perform this step to set a destination NMS address for trap messages sent by APs. If a target host that receives trap messages is a Huawei NMS, specify private-netmanager. To enable trap messages to carry extended bound variables, specify ext-vb.

  7. (Optional) Run:

    snmp-agent extend error-code enable

    The extended error code function is enabled.

    The extended error code function can be configured to extend standard error codes only when an NMS is a Huawei NMS and managed devices are Huawei devices. Extended error codes facilitate fault locating.

  8. (Optional) Run:

    snmp-agent mib-view { excluded | included } view-name oid-tree

    A MIB view is created, and MIB objects monitored and managed by an NMS are specified.

    • If there are only a few MIB objects that do not need to be managed by an NMS when you create a MIB view or you want to remove some MIB objects from an existing MIB view, specify excluded in the command.

    • If there are only a few MIB objects that need to be managed by an NMS when you create a MIB view or you want to add some MIB objects to an existing MIB view, specify included in the command.

  9. Run:

    commit

    The configuration is committed.

Configuring APs to Send Information to a Syslog Server

To view AP running information on a syslog server, configure the APs managed by the master to send information to the syslog server on a master.

Context

When an AP is running, the system records the AP's running status in real time and generates related information. After the information management function is enabled, configure the APs managed by the master to send information to a syslog server for storage and query on a master. A network administrator can use the information to monitor the running status of the APs and diagnose network faults.

Perform the following steps on a master.

Pre-configuration Tasks

Before configuring APs to send information to a syslog server, establish a virtual access system.

When establishing a virtual access system, configure route import between the virtual access system and external network so that the routes between the syslog server and APs are reachable.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    virtual-access

    The virtual access view is displayed.

  3. Run:

    info-center loghost ipv4-address [ { local-time | utc } | facility local-number | port port-number | level log-level | transport { udp | tcp } ] *

    All the APs managed by the master are configured to send information to a specified syslog server.

    Repeat this step to configure APs to send information to multiple syslog servers, implementing information backup between the syslog servers. You can configure APs to send information to a maximum of eight syslog servers.

  4. Run:

    commit

    The configuration is committed.

Download
Updated: 2018-07-12

Document ID: EDOC1100028541

Views: 7391

Downloads: 92

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