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 V300R009C00 Operation Guide 09

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).
Deploying an MxU in Zero Configuration Mode

Deploying an MxU in Zero Configuration Mode

This section describes how to deploy an MxU in zero configuration mode on the eSight.

A large number of MxUs need to be deployed on a GPON network. The deployment and commissioning are complex and labor-intensive, and costs are high. Zero-touch MxU deployment requires only the following procedure to deploy an MxU. Set a zero-touch MxU deployment policy, including the management VLAN, IP address pool, SNMP profile, and MxU configuration file, and bind the policy to the desired OLT. After the MxU goes online for the first time, the eSight automatically detects the MxU and matches it with the existing policy. If the match succeeds, the eSight automatically creates and deploys the MxU. Zero-touch MxU deployment improves the deployment efficiency effectively and lowers the network construction costs.

NOTE:

Currently, only the GPON and 10GPON profile modes are supported.

Figure 17-7 Zero-touch MxU deployment flowchart

The Configuration Guide of eSight combines the zero-touch deployment process, allowing you to fast deploy PON devices.

Creating OLT Global Configuration

This topic describes how to create the OLT global configuration including preconfiguration, VLAN and upstream ports of an OLT.

Prerequisites

An OLT has been added to eSight.

Context
  • When an OLT is preconfigured, the eSight will generate necessary configuration and global profiles.
  • Do not repeatedly preconfigure an OLT.
  • Do not preconfigure an OLT when additional configurations are being performed on it.
Procedure
  1. Choose Resource > PON from the main menu.
  2. Choose PON Service > OLT Global Configuration from the navigation tree on the left, and click .
  3. On the OLT Global Configuration tab, set Name and Description. Select the Preconfiguration, VLAN Settings, Upstream Port Settings or Multicast VLAN Config check box to create desired configuration items.

    1. Click VLAN Settings. On the VLAN Settings tab page, click to add the VLAN ID.
    2. Click Upstream Port Settings. On the Upstream Port Settings tab page, click to add the port and VLAN list.
    3. Click Multicast VLAN Config. On the Multicast VLAN tab page, click to add multicast VLANs.

  4. Click Next. Corresponding commands will be generated in the System Create Order window.
  5. (Optional) Enter the order to be added in the text box, or click to import user-defined order files to add user-defined order.

    NOTE:
    • The import file type must be TXT or CFG.
    • The file must not exceed 4 MB.
    • The text should be consistent with the format of the host command.

  6. Click OK.

Applying the OLT Global Configuration

This topic describes how to apply an OLT global configuration to an OLT.

Prerequisites
  • An OLT has been added to eSight.
  • An OLT global configuration has been created.
Context

If different OLT global configurations are applied to the same NE, a set of all the applied configurations is applied to the NE. If the same configuration command is run multiple times, the last value in the command takes effect.

Procedure
  1. Choose Resource > PON from the main menu.
  2. Choose PON Service > OLT Global Configuration from the navigation tree on the left.
  3. In the global configuration record list, select the desired configuration record, and click.
  4. In Available Resource list, select one or multiple NEs, and click OK.

    NOTE:

    NEs can be filtered by Name or IP when you select NEs.

Creating a MxU Configuration

This section describes how to create an MxU configuration by setting VLAN, Upstream Port, Subscriber Port, and User Define Order.

Prerequisites

An OLT has been added to eSight.

Context

MxU configuration of the same parameters but different names can be created.

Procedure
  1. Choose Resource > PON from the main menu.
  2. Choose PON Service > MxU Configuration from the navigation tree on the left.
  3. Click in the right area, and enter Name and Description.
  4. Click VLAN Settings. On the VLAN Settings tab page, click to add the VLAN ID.
  5. Click Upstream Port Settings. On the Upstream Port Settings tab page, click to add the port and VLAN list.
  6. Click Subscriber Port Settings. On the Subscriber Port Settings tab, enter the VLAN and default VLAN.

    NOTE:
    • At least one of VLAN and Default VLAN must be set.
    • VLANs to be added in Upstream Port Settings and those to be configured in Subscriber Port Settings must be first added in VLAN Settings. In addition, all the VLANs must have been provisioned in OLT Global Configuration or have existed on OLTs.

  7. (Optional) Click Command Settings to enter commands on the Command Settings tab.
  8. (Optional) Choose 802.1x configuration in the navigation tree on the left and select Enable 802.1x Authentication. The RADIUS server IP address and port number and the authentication server sharing key are mandatory.
  9. Click OK.
Related Operations

After setting the MxU configuration file, you can view all the current MxU configuration files on the MxU configuration management page, click to edit the configuration files again, and click to verify the configuration file and device configuration.

Configuring IP Address Pool

This section describes how to configure an IP address pool. To add an IP address segment to an ONU IP address pool, you can use an IP address from the IP address pool to automatically allocate an IP address to an MxU.

Prerequisites

An OLT has been added to eSight.

Context

OLT Name cannot be modified.

Procedure
  1. Choose Resource > PON from the main menu.
  2. Choose PON Deployment > IP Address Pool from the navigation tree on the left.
  3. Click and set OLT Name, Starting IP Address, Ending IP Address, ONU Mask, ONU Gateway, Management VLAN, Destination IP Address, Destination Mask, and Next Hop IP Address.

  4. Click OK.

(Optional)Configuring Type B Dual-homing Protection Group

You can create a type B dual-homing protection group by configuring a working OLT and a protection OLT. In this manner, services can fail over to the other OLT when the optical fiber connected to one OLT is faulty.

Prerequisites

An OLT has been added to eSight.

Context
  • After a type B dual-homing protection group is configured, GPON ports on two different OLTs protect each other. When one OLT is faulty, eSight automatically switches services on the faulty OLT to the other OLT and services are not interrupted. The type B dual-homing protection mechanism improves the disaster redundancy capabilities of OLT. Two OLTs in a protection group can locate in different regions. When the OLT connected to a working optical fiber is faulty, eSight automatically switches services on the faulty OLT to the OLT connected to a protection optical fiber.
  • In a protection group, the working OLT and the protection OLT must be different.
  • One port can be in only one protection group.
  • If an OLT is deleted from eSight, the protection group of the OLT is also deleted.
Procedure
  • Configuring type B dual-homing protection group on eSight
    1. Choose Resource > PON from the main menu.
    2. Choose PON Service > TypeB Dual-homing Protection Group from the navigation tree on the left.
    3. Click to create a type-B dual-homing protection group.
    4. Select Working OLT and Protection OLT and enter Data Synchronization Interface Config.
    5. Click at the lower part of the page to configure the port information.
    6. Click OK to complete port configuration.
    7. Click OK to complete creating type B dual-homing protection group. Applying result on OLT will be displayed in Result dialog box.
    8. Optional: Click Verify to check whether resource items consist with protection group information on OLT. Click Deliver to apply port configuration on OLT.
  • Configuring type B dual-homing protection group with command
NOTE:

Users can configure type B dual-homing protection group in OLT side with command as well as configuring it on eSight. If configuration of protection group is finished on eSight, it is not necessary to implement this operation in OLT side.

Command example for configuring working OLT:

Device_A(config)#dual-parenting local-node ip-address 192.168.68.1  
port 6076 key work_4234 // Configure the local-node IP address, TCP port ID, and key for a member in a dual-homing protection group.
Device_A(config)#dual-parenting peer-node standby ip-address  
192.168.68.8 port 6076 key protect_4234 // Configure the peer-node IP address, TCP port ID, and key for a member in a dual-homing protection group.
Device_A(config)#dual-parenting sync  
enable // Enable the dual-homing synchronization function.
Device_A(config)#protect-group  
1 protect-target gpon-uni-port workmode  
dual-parenting // Create a protection group and enter the protect-group mode of the protection group.
Device_A(protect-group-1)#protect-group member port  
0/2/1 role work // Add a member (active OLT) to the protection group.
Device_A(protect-group-1)#peer-group-member peer-node standby  
peer-port 0/2/1 // Configure the peer member information of the dual-homing protection group.
Device_A(protect-group-1)#uplink-monitor port  
0/9/1 // Bind the uplink interface associated with the dual-homing protection group.
Device_A(protect-group-1)#quit

Command example for configuring protecting OLT:

Device_B(config)#dual-parenting local-node ip-address 192.168.68.8  
port 6076 key protect_4234 // Configure the local-node IP address, TCP port ID, and key for a member in a dual-homing protection group.
Device_B(config)#dual-parenting peer-node active ip-address  
192.168.68.1 port 6076 key work_4234 // Query information about a protection group and all members in the protection group.
Device_B(config)#dual-parenting sync  
enable // Enable the dual-homing synchronization function.
Device_B(config)#protect-group  
1 protect-target gpon-uni-port workmode  
dual-parenting // Create a protection group and enter the protect-group mode of the protection group.
Device_B(protect-group-1)#protect-group member port  
0/2/1 role protect // Add a member (standby OLT) to the protection group.
Device_B(protect-group-1)#peer-group-member peer-node  
active peer-port 0/2/1 // Configure the peer member information of the dual-homing protection group.
Device_B(protect-group-1)#protect-group  
enable  // Enable the protection group.
Device_B(protect-group-1)#uplink-monitor port  
0/9/1 // Bind the uplink interface associated with the dual-homing protection group.
Device_B(protect-group-1)#quit
Example
Table 17-13 Operations on the page for configuring a type-B dual-homing protection group

Related Operations

Function

Create a type B dual-homing protection group.

Synchronize device information about working OLT and protection OLT to eSight to create a new type B dual-homing protection group.

Modifies the selected protection group.

NOTE:

A protection group cannot be modified if it has been referenced by a zero-touch deployment policy and the zero-touch deployment policy has been bound to devices.

Deletes the selected protection group.

NOTE:

A protection group cannot be modified if it has been referenced by a zero-touch deployment policy and the zero-touch deployment policy has been bound to devices.

Verify whether port configuration information consists of information in protection group on eSight.

Traffic Profile Management

Configuring an MxU Multi-Service Profile

Users can configure multi-service profiles for MxU devices to set parameters and deliver the profile to devices through binding.

Prerequisites
  • eSight is running properly.
  • MxU configuration file is created.
Procedure
  1. Choose Resource > PON from the main menu.
  2. Choose PON Service > Multiservice Profile Management.
  3. Click and set Profile Name, Description, ONU Type, MxU Configuration File, Management VLAN(OLT), Management VLAN(MxU), uplink traffic profile, and downlink traffic profile on the Multiservice Profile Management page.

    NOTE:
    • The value of Management VLAN(OLT) must be consistent with that of Management VLAN in IP Address Pool.
    • The Management VLAN(OLT) and Management VLAN to be configured must have been provisioned in OLT Global Configuration or existed on OLTs. Otherwise, some subtasks will fail.

  4. Click OK.
Related Operations
Table 17-14 Related operations of Multiservice Profile Management page

Related Operations

Purpose

Creates a multi-service profile.

Deletes selected multi-service profiles in batches.

NOTE:

Profiles bound to devices or referenced by Zero Configuration Policy cannot be deleted.

Binds a multi-service profile to an ONU device.

Modifies multi-service profile parameters.

NOTE:
  • The profile name and ONU type cannot be modified.
  • If the profile to be modified has been bound to an ONU device, the modified content is not automatically delivered to devices. You need to manually deliver the modified content to the device.

Deletes a multi-service profile.

NOTE:

Profiles bound to devices or referenced by Zero Configuration Policy cannot be deleted.

Verifies the consistency between the profile on eSight and profile on the device.

Follow-up Procedure
  • Click to bind the profile to the device.
NOTE:
  • Services may be interrupted during binding.
  • A service profile can be associated to multiple devices.
  • Management VLAN (OLT) and Management VLAN (MxU) in profile must be consistent with parameters on devices, otherwise bounding would fail.
  • Click a profile. Information about ONU devices bound to the profile is displayed in the list at the bottom of the page.
  • Click next to a profile to check whether the profile on eSight is consistent with that on the bound ONU device.
  • Choose PON Service > ONU Service Configuration. If profile bounded successfully the result displayed in ONU list.

Configuring a Zero Configuration Policy for an MxU

This topic describes how to create a zero configuration policy for an MxU by configuring the ONU model, IP address pool, MxU Multiservice Profile and SNMP profile.

Prerequisites
  • An OLT has been added to eSight.
  • An MxU multiservice profile has been created.
  • An IP address pool has been configured.
  • SNMP parameters have been correctly set on NEs.
  • A trap destination host has been set.
Context
  • Zero configuration policy of the same parameters but different names can be created.
  • Policies of different ONU Model values can be bound to the same port of the same OLT. However, the policies of the same ONU Model value cannot be bound to the same port of the same OLT.
  • The values of Policy Name, ONU Type and ONU Model cannot be modified, and the modified policies take effect only on newly bound NEs.
Procedure
  1. Choose Resource > PON from the main menu.
  2. Choose PON Deployment > Zero Configuration Policies from the navigation tree on the left, and click .
  3. Set Policy Name, Description, ONU Type, ONU Model, IP Address Pool, Multiservice Profile, SNMP Profile, SNMP Trap IP Address, SNMP Trap Port, TypeB dual-homing protection and click OK.

    NOTE:

    Select TypeB dual-homing protection, typeB dual-homing protection will be applied to the zero-touch deployment policy. After the TypeB dual-homing protection text box is selected, the zero-touch deployment policy can only be bound to the working OLT and port in the protection group.

  4. Click to bind the zero-touch deployment policy to an NE or ports.

    NOTE:
    • A zero configuration policy can be bound to an OLT or specified ports of the OLT.
    • A zero configuration policy can be associated by multiple OLTs.

  5. Click OK.
Follow-up Procedure
  • Choose PON Deployment > Task Deployment from the navigation tree on the left to view the task application progress of binding the zero configuration policies.
NOTE:

Deployment tasks whose Task Status is Executing cannot be deleted.

  • Choose PON Deployment > Zero Configuration Policies from the navigation tree on the left. Click to modify a zero-touch deployment policy. Only Description, Multiservice Profile and SNMP Configuration could be modified.
  • Choose PON Deployment > Zero Configuration Policies from the navigation tree on the left. Click one record in the policies list, and the devices been bounded by this policy will be displayed in Associated Devices in the lower pane.
NOTE:
  • If the policy has been bounded to working OLT in the protection group or its port, Protection OLT Name and Protection OLT IP will be displayed in the Associated Devices.
  • Click to check whether VLAN, DBA profile, IP traffic profile, SNMP profile, GPON service profile and GPON line profile exist on the OLT. Check result displayed as Successful indicates that profiles exist on working OLT and protection OLT, and are ready for normal configuration and deployment on device.
  • Select one or more associated devices and click to unbind the zero-touch deployment policy from the devices.
  • When a working OLT or protection OLT is removed from eSight, associated device will be automatically unbounded.

(Optional)Verify MxU Configuration

This topic describes how to verify whether parameters of MxU configuration file exist on OLT and apply parameters that MxU lack of.

Prerequisites
  • An MxU has been added to eSight.
  • A MxU Configuration File has been created and the parameters exist.
Procedure
  1. Choose Resource > PON from the main menu.
  2. Choose PON Service > MxU Configuration from the navigation tree on the left.
  3. Click in the row of a configuration record from the available configuration list.
  4. In Available NEs list, select one NE and click OK.

    NOTE:

    NEs can be filtered by Name, Device Type or IP when you select NEs.

  5. Click Verify in the Verify dialog box.
  6. (Optional) If the parameters do not exist in MxU, the verify result displayed as Failed. Click Cover to apply the parameters to MxU.

    NOTE:

    If the status of switch on NE is not default, verify result displays as Failed. Click Cover and the status will be switched.

Follow-up Procedure

Choose PON Deployment > Task Deployment from the navigation tree on the left to view the task application progress of the MxU configuration file details.

(Optional)MxU Service Configuration Management

After multi-service profiles are bound to MxUs, you can update multi-service profiles and deliver the profiles to devices in batches on the ONU service configuration page.

Prerequisites
  • eSight is running properly.
  • The ONUs have been added to eSight.
  • The multiservice profile has been added to eSight.
Procedure
  1. Choose Resource > PON from the main menu.
  2. Choose PON Service > ONU Service Configuration.
  3. Click .
  4. Click , download template.
  5. Open the template, enter information and then save the file.

    NOTE:

    To import MxUs into a table, you can enter only mandatory information, and parameters be consistent with those in the multi-service profile created on eSight. Otherwise, import fails.

  6. In Import tab, click and select the saved Excel file.
  7. Click Import. The import result of ONU parameters is displayed in the list at the bottom of the tab page if imported successfully.

    NOTE:

    This operation will download profiles to device and all be bounding profiles on this ONU will be updated. Once it failed may cause service interruption.

  8. Click OK.
  9. In ONU Service Configuration tab, imported profile record of ONU will be added in ONU list.
Related Operations
Table 17-15 Related operations of ONU Service Configuration page

Related Operations

Purpose

Import multiservice profile to device.

NOTE:

If imported successfully, parameters automatically downloaded to ONU once it goes online.

Configuring multiservice profile of ONU.

Delivering multiservice profile to ONU.

Verifies the consistency between the profile on eSight and profile on the device.

Follow-up Procedure
  • Click button behind one record to update multiservice profile of this ONU. Management VLAN (OLT) and Management VLAN (MxU) in profile must be consistent with parameters on devices, otherwise bounding would fail. When profile configuration is done, click to delivery it to devices.
  • Click to verify the consistency between the profile on eSight and profile on the device. Click Deliver to update parameters on eSight to device.
Download
Updated: 2019-05-17

Document ID: EDOC1100011877

Views: 283499

Downloads: 542

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