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

eSight V300R010C00 Operation Guide 07

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).
ONU Device Replacement

ONU Device Replacement

eSight provides function of replacing ONU while keeping original configuration data, and replace faulty ONUs or ONUs failed to meet new service requirement to new devices.

Replacing a Faulty ONT

This topic describes how to replace a faulty ONT or ONT failed to meet new service requirement and adds the replacement to eSight.

Prerequisites
  • eSight is running properly.
  • The original ONT has been added to eSight.
Procedure
  1. Choose Resource > PON from the main menu.
  2. Choose PON Resource > ONU from the navigation tree on the left.
  3. In the list, find the ONT to be replaced and click .
  4. In the Replace ONUs dialog box, enter the SN of the new ONT, or selecting the SN of device which is in automatically discovering status.
  5. Optional: If you need to upgrade the ONT, select the Version File text box and select the desired version file from the drop-down list. If there is no available version, click File Management to go to the File page. On the page, set the version information and upload the version file.

    NOTE:
    • If the Version file check box is selected, you can check and perform further operations in Upgrade Task after the replacement task is created. The upgrade task will start after the new ONT is powered on.
    • The ONT whose Type is not identified supports only SN replacement.

  6. Click Apply.

    • After the task is started, the WLAN settings will be automatically delivered to the new device.
    • Replacing ONTs may interrupt services and restart ONTs.
    • If the new ONT has already gone online, the replacement will fail.

Follow-up Procedure
  • Synchronize the new device manually after it goes online. The ONU list will be updated.
NOTE:
  • SN, Run Status, Operation Status, Configuration Status of device will be displayed as entered SN, Offline, Activated and Initial after replacement. After the new ONT is powered on, it is automatically registered to inherit service configurations of the original ONT.
  • If the SN on eSight is inconsistent with the actual SN of the new ONT, the run status of the ONT is offline after the new ONT is powered on.
  • Checks the execution result of the upgrade task.

    On the Upgrade Task page, click the name of the upgrade task to view detailed information of the task and the execution result.

    • You can view the upgrade status of each device in the Upgrade Status column. If the upgrade fails, view the failure causes in the Failure Reason column.
    • If you want to re-deliver an upgrade task to a device that fails to be upgraded, select the device and click . You can also click in the Operation column of the device that fails to be upgraded.
    • If ONT upgrade task is created while replacing ONT, after the ONT goes online and upgrade task starts, choose PON Deployment > Task Deployment from the navigation tree on the left to view the progress of the replacement task.

Replacing a Faulty MxU

This topic describes how to replace a faulty MxU or MxU failed to meet new service requirement and adds the replacement to eSight.

Prerequisites
  • eSight is running properly.
  • The original ONU has been added to eSight.
Procedure
  1. Choose Resource > PON from the main menu.
  2. Choose PON Resource > ONU from the navigation tree on the left.
  3. In the list, find the MxU to be replaced and click .
  4. In the Replace ONUs dialog box, enter the SN of the new MxU, or selecting the SN of device which is in automatically discovering status.
  5. Optional: Select the Configuration file check box and select the configuration file of the existing MxU so that the new MxU inherits the configurations of the existing MxU. If there is no available file, click Config Files to go to the Config Files page. On the page you can back up and manage configuration files.
  6. Optional: If you need to upgrade the MxU, select the Version file text box and select the desired version file from the drop-down list. If there is no available version, click File management to go to the File page. On the page, set the version information and upload the version file.

    NOTE:
    • If the Version file check box is selected, you can check and perform further operations in Upgrade Task after the replacement task is created. The upgrade task will start after the new MxU is powered on.
    • The MxU whose Type is not identified support only SN replacement.
    • When the MxU is not added to the eSight, Configuration file and Version file are unavailable.

  7. Click Apply.

    • Replacing MxUs may interrupt services and restart MxUs.
    • If the new MxU has already gone online, the replacement will fail.

Follow-up Procedure
  • Synchronize the new device manually after it goes online. The ONU list will be updated.
NOTE:
  • SN, Run Status, Operation Status, Configuration Status of device will be displayed as entered SN, Offline, Activated and Initial after replacement. After the new MxU is powered on, it is automatically registered to inherit service configurations of the original MxU.
  • If the SN on eSight is inconsistent with the actual SN of the new MxU, the run status of the MxU is offline after the new MxU is powered on.
  • Checks the execution result of the upgrade task.

    On the Upgrade Task page, click the name of the upgrade task to view detailed information of the task and the execution result.

    • You can view the upgrade status of each device in the Upgrade Status column. If the upgrade fails, view the failure causes in the Failure Reason column.
    • If you want to re-deliver an upgrade task to a device that fails to be upgraded, select the device and click . You can also click in the Operation column of the device that fails to be upgraded.
    • If MxU upgrade task or configuration file upgrade task is created while replacing MxU, after the MxU goes online and upgrade task starts, choose PON Deployment > Task Deployment from the navigation tree on the left to view the process of the replacement task.

Configurating Files Management

eSight provides configuration files management function and able to set automatically regular automatic backup, which helps saving and managing ONU configuration data. Users can view configuration information, restore device configuration, and quickly configure batch devices using a configuration file. With service development, the configuration file of a device frequently changes. To ensure device security and reliability, eSight can back up, restore, and maintain configuration files, which improves the working efficiency of the administrator.

Operation Procedure

This topic describes the operation procedure of configuration file management of eSight, helping you quickly master configuration file management operations.

Table 18-15 Operation procedure of configuration file management

Step

Operation

Description

1

Set protocol parameters on the device: SNMP.

For details, see Setting Protocol Parameters on the Device.

When configuring SNMP parameters, create a MIB view containing ISO nodes and grant read-write permissions to the MIB view.

2

Add devices to eSight.

For details, see Adding OLTs and ONUs.

3

Check the FTP server status.

If SFTP is used to manage configuration files, run the following command on the device to enable first-time authentication on the SSH client:

ssh client first-time enable

4

Back up configuration files.

eSight can back up the running and startup configuration files in manual or automatic mode.

If a device is configured to save policies periodically, eSight automatically backs up the configuration files when any change occurs.

5

Restore configuration files.

If a fault occurs on a device, the backup configuration file can be uploaded to the device to quickly restore the device's configuration data.

6

Maintain configuration files.

You can compare and baseline the configuration files and view configuration changes.

Typical Configuration Examples: Example for Configuring eSight to Periodically Back Up Device Configuration Files

eSight provides functions that creates periodical backup tasks for device configuration, and also allows you to manage files and perform instant backup manually, which guarantees complete configuration data while replacing devices.

Configuration Roadmap
  1. Check whether FTP parameters are correctly configured on eSight.

    If the FTP service is disabled, enable it.

  2. Configure backup parameters.

    Set the maximum number of backup configuration files.

  3. Create a backup task.

    After a backup task is created, eSight backs up the configuration files of the specified devices at the specified time.

Prerequisites
  • eSight is running properly.
  • Devices have been added to eSight.
Procedure
  1. Check whether the FTP service status is normal on eSight referring to Configuring the eSight File Transfer Protocols in the Maintenance Guide.
  2. Choose Resource > PON from the main menu.
  3. Optional: Choose Configuration File Management > System Parameter Settings > Backup Parameters. You can set the maximum number of configuration files that can be stored on the eSight server for each device.
  4. Choose Configuration File Management > Device Configuration Management > Backup Tasks and click .
  5. Set Task Name, Task Description, Executed At and Apply To Device in Backup Tasks page.

    1. Click and select one or more devices to which the backup task is applied.
      NOTE:

      Set name, IP address, or device type in the text box to filter when selecting devices.

    2. (Optional) Select one or multiple devices and click to use FTP or SFTP to transfer the configuration file to eSight.
    NOTE:

    SFTP is recommended because its security level is higher than that of FTP.

  6. Click OK.
Related Operation
Table 18-16 Backup task related operation

Related Operations

Purpose

Create a backup task.

Deletes the selected tasks in batches.

Enable backup task.

Disable backup task.

Modify task information.

NOTE:

Backup task cannot be modified if it is in processing.

Instant back up the selected device manually.

NOTE:

The device can be instant backup only when it is enabled.

Set the parameters and search for devices.

Follow-up Procedure

Choose Configuration File Management > Device Configuration Management > Configuration File. You can view and manage the configuration files that already been backed up of devices.

Typical Configuration Examples: Example for Using eSight to Recover Services on Faulty Devices Through Backup Configuration Files

You can view the configuration files that have been backed up and restore the configurations for a device when necessary using eSight.

Prerequisites
  • eSight is running properly.
  • SNMP parameters of device are not lost, and device has gone online.
Procedure
  1. Choose Resource > PON from the main menu.
  2. Choose Configuration File Management > Manage Config Files > Config Files.
  3. Click in the Operation column to view the configuration file management page of a device.

  4. Click in the Operation column to restore the configuration file of the device.

    NOTE:
    • If the file is restored to the device, service transmission will be affected.
    • If Restore Configuration (Reboot Now) is selected, the device reboots and the restore operation takes effect immediately. If Restore Configuration (Manual Reboot) is selected, the restore operation takes effect after the device's reboot.

Config Files related operations
Table 18-17 Related operations on the configuration file page

Related Operation

Purpose

You can back up configuration file of a specified device.

Change the FTP operation types of selected devices.

NOTE:

SFTP is recommended because its security level is higher than that of FTP.

Export NE configuration files.

Manage configuration files of a specified device.

NOTE:

In the file management page, you can compare, delete, view, restore and download configuration files.

Download configuration file.

Import configuration file to device.

Set the parameters and search for devices.

Translation
Download
Updated: 2019-06-30

Document ID: EDOC1100044378

Views: 59793

Downloads: 272

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