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 V300R010C00SPC200, 300, and 500 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).
Service Configuration

Service Configuration

Deploying an ONT in Zero Configuration Mode

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

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

NOTE:

Currently, only the GPON and 10GPON profile mode is supported.

Figure 18-5 Zero-touch ONT deployment flowchart

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

Demonstration

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 PON.

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. The command customization page is displayed.

    NOTE:
    • The autosave time command is used to enable auto-saving for device configuration data at the preset time or set the auto-saving time. By default, this function is enabled and the configuration data is automatically saved at 00:00:00 every day. You can configure this function and the auto-saving time as required. For more information, see Command Reference of the corresponding device.
    • If the autosave time command is issued to the OLT, ensure that the device time is accurate.

  5. (Optional) Enter the command to be added in the text box, or click to import user-defined command files to add a user-defined command.

    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.
    • The input content (text) will be checked based on the whitelist. Invalid commands irrelevant to the configurations are not allowed.
    • Do not include high-risk operations or host commands containing sensitive information in user-defined commands. Otherwise, the device may be abnormal or sensitive information may be disclosed.

  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.

(Optional) Verify OLT Global Configuration

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

Prerequisites

  • An OLT has been added to eSight.
  • An OLT global configuration has been created and the parameters exist.

Procedure

  1. Choose Resource > PON from the main menu.
  2. Choose PON Service > OLT Global Configuration from the navigation tree on the left.
  3. Click next to a configuration record in the global configuration record 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 OLT, the verify result displayed as Failed. Click Cover to apply the parameters to the OLT.

    NOTE:

    If the host packet switch is not in the default status, the verification result is displayed 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 OLT configuration file details.

(Optional) Configuring a 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, PON 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 the 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 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 > Type B Dual-Homing Protection 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 Port Config.
    5. Click in the lower part of the page and configure the port information.

    6. Click OK to complete port configuration.
    7. Click OK to complete creating the type B dual-homing protection group. Applying result on the OLT will be displayed in Result dialog box.
    8. (Optional) Click Verify to check whether resource items consist with protection group information on the OLT. Click Deliver to apply port configuration on the OLT.
  • Configuring type B dual-homing protection group with command
NOTE:

Users can configure type B dual-homing protection group on the OLT 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 on the OLT.

  • Command example for configuring the 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 the 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 18-18 Operations on the page for configuring a type-B dual-homing protection group

Related Operations

Purpose

To create a type B dual-homing protection group.

To synchronize device information of the working OLT and protection OLT to eSight to generate a type B dual-homing protection group record.

To modify the selected protection group.

NOTE:

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

To delete the selected protection group.

NOTE:

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

To verify whether port configuration information consists of information in the protection group on eSight.

(Optional) Configuring Traffic Profiles

A user can configure a traffic profile on eSight to limit the upstream and downstream traffic speed.

Prerequisites

eSight is running properly.

Procedure

  1. Choose Resource > PON from the main menu.
  2. Choose PON Service > Equipment Profile Management > Traffic Profile from the navigation tree on the left.
  3. Click to set Profile Name, Description, CIR (kbit/s)(0-10240000), CBS (byte)(0-1024000000), PIR (kbit/s)(64-10240000), PBS (byte)(2000-1024000000), Priority Strategy, Priority (0-7) and Priority Mapping template in Traffic Template Management.

    NOTE:
    • If you deselect Do not limit speed, speed limit parameters can be set.
    • The PIR value varies with the input CIR value. By default, the PIR value is twice the input CIR value.
    • A speed restriction parameter can be set only if Default before it is deselected.
    • If the value of CIR/PIR is not an integral multiple of 64, the system automatically adjusts the value.

  4. Click OK.

Related Operations

Table 18-19 Related operations of traffic template management

Related Operation

Purpose

Create a traffic profile.

Delete selected traffic profiles in batches.

NOTE:

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

Modify traffic profile parameters.

NOTE:

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.

Binds a traffic profile to an OLT or ONU device.

NOTE:

If an ONU device is offline, the traffic profile cannot be bound to it due to the communication failure.

Copies an existing record and creates a traffic profile accordingly.

Delete a traffic profile.

NOTE:

A traffic profile referenced by a zero touch policy cannot be deleted.

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

NOTE:

An offline device cannot be verified.

Follow-up Procedure

If a traffic profile is referenced by multiple service profiles and delivered to devices successfully during zero touch provisioning, the system automatically generates binding relationships. You can click a traffic profile record to view the list of devices to which the traffic profile is bound. You can click next to a device record to check whether the traffic profile on eSight is the same as that on the device. If no, click Cover to deliver parameters.

(Optional) Configuring an ONT Dox1 Profile

You can configure an ONT Dot1x template on eSight.

Prerequisites

eSight is running properly.

Procedure

  1. Choose Resource > PON from the main menu.
  2. Choose PON Service > Device Profile Management > ONT Dot1x Profile from the navigation tree on the left.
  3. (Optional) Set Profile Name and Description and click Search to search for the required ONT Dot1x profile.
  4. Click and set basic settings such as Profile Name, Description, Radius Authentication Server IP, Radius Authentication Server, Authentication Server Shared Secret Key, Standby Radius Authentication Server IP, Standby Radius Authentication Server Port, Standby Authentication Server Shared Secret Key, and Username Format on the ONT Dot1x profile management page.

    NOTE:

    You can click and configure the key on the tab page that is displayed.

  5. After you set Ethernet Port Number or Obtain By Model, port number information is displayed on the ONT port list. Click next to a record and set Port Number, Authentication Switch, Authentication Method, MAC-Bypass, Guest VLAN, Restrict VLAN, Critical VLAN, Handshake Switch, Handshake Retransmission Time(s), and Frequency Of Handshake Retransmission.

  6. Click OK.

Related Operations

Table 18-20 Related operations on the ONT Dot1x profile management page

Related Operations

Purpose

To create an ONT Dot1x profile.

To delete selected ONT Dot1x profiles in batches.

NOTE:

ONT Dot1x profiles that are bound to devices or are referenced cannot be deleted.

To reuse the port information. The configuration of the first Ethernet port is reused for subsequent Ethernet ports.

To copy an existing record and create an ONT Dot1x profile accordingly.

To modify ONT Dot1x profile parameters.

To bind an ONT Dot1x profile to an OLT device.

NOTE:

If an ONU device is offline, the ONT Dot1x profile cannot be bound to it due to communication failure.

To delete an ONT Dot1x profile.

To verify the consistency between the profile on eSight and profile on the device.

NOTE:
  • When the device does not exist or is offline, the verification fails.
  • If the ONT Dot1x profile is referenced by an ONT, the OLT does not allow profile overwriting.

Follow-up Procedure

You can click next to a device record to check whether the ONT Dot1x profile on eSight is the same as that on the device. If no, click Cover to deliver parameters.

Configuring an ONT Multi-Service Profile

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

Prerequisites

eSight is running properly.

Procedure

  1. Choose Resource > PON from the main menu.

    
    

  2. Choose PON Service > Multiservice Profile Management.
  3. (Optional) Set Profile Name and click the search button to search for the required multi-service template.
  4. Click and set Profile Name, Description, ONU Type, Ethernet Ports, VLAN, WLAN VLAN, uplink traffic template, download traffic template, Voice VLAN, Voice Protocol, SIP Server IP, SIP Service Port, Domain Name, Multicast VLAN, VOD VLAN, 802.1x authentication, and ETH port configuration on the Multiservice Profile Management page.

    NOTE:
    • If Voice Protocol is set to H.248, the input parameters are MGC Server IP and MGC Service Port.
    • If 802.1x authentication is enabled, the 802.1x profile can be bound to the configured Dot1x profile. To ensure normal 802.1x authentication, you are advised to select a traffic profile with a higher priority.

  5. (Optional) Click and set Ring Check Switch, Ring Check Auto-Shutdown Switch, Ring Check Detect Frequency(pps), and Ring Check Resume Interval(s).

    NOTE:

    After the user enters values in the text boxes, the system performs automatic verification. The following describes the values of each text box:

    • Ring Check Switch: Enable/Disable
    • Ring Check Auto-Shutdown Switch: Enable/Disable
    • Ring Check Detect Frequency(pps): 1-20
    • Ring Check Resume Interval(s): 60-3600

  6. (Optional) After the number of Ethernet ports is configured, click in the ETH port list for configuration.

    NOTE:
    • The data, multicast, and VOD services are selected by default.
    • The L2 Isolation Switch parameter is set to Unconcern by default, which can be changed to Enable or Disable.
    • The Switch parameter is set to Unconcern by default, which can be changed to Enable or Disable.
    • The Mode parameter is set to Spare by default, which can be changed to Signal or Unconcern.
    • The Priority parameter is set to High by default, which can be changed to Critical or Low.
    • The Max Power Class parameter is set to Default by default, which can be changed to Class0 ~ Class4.
    • The Force Switch parameter is set to Disable by default, which can be changed to Enable or Unconcern.

  7. (Optional) Click at the bottom on the tab page to create an IP interface for management use, set VLAN and Get Type, and click OK.

    NOTE:
    • If Enable Voice Service is selected, the IP interface for the voice service is automatically generated based on the voice VLAN. Only Get Type can be modified. If Enable Voice Service is deselected, the added IP interface for the voice service will be deleted.
    • If Enable 802.1x Authentication is selected, the interface for the 802.1x service is automatically generated based on the VLAN. Only Get Type can be modified. If Enable 802.1x Authentication is deselected, the added 802.1x authentication parameters are cleared.

  8. Click OK.

Related Operations

Table 18-21 Related operations of Multiservice Profile Management page

Related Operations

Purpose

To create a multi-service profile.

To delete selected multi-service profiles in batches.

NOTE:

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

To bind a multi-service profile to an ONU device.

To modify multi-service profile parameters.

NOTE:
  • The profile name and ONU type cannot be modified. In addition, the service enabling and disabling status 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.

To delete a multi-service profile.

NOTE:

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

To verify the consistency between the profile on eSight and profile on the device.

To reuse the port information. The configuration of the first Ethernet port is reused for subsequent Ethernet ports.

To unbind a multi-service profile from a 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.
  • 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. After being successfully bounded, the device is displayed in the ONU list.

(Optional)Import personalized parameters of ONT

After multi-service profile is created on eSight, you can set personalized parameters and supplement the pre-configuration data for ONT service configuration through ONU Service Predeployment if the services are enabled such as voice service.

Prerequisites

  • eSight is running properly.
  • The multiservice profile has been added to eSight.

Procedure

  1. Choose Resource > PON from the main menu.
  2. Choose PON Deployment > ONU Service Predeployment.
  3. Click .
  4. Click , download template and configure related information, and then save the profile.
  5. On Service Predeployment Import tab page, click and select the saved Excel file.
  6. Click Import. The import result of ONU parameters is displayed in the list at the bottom of the tab page.

    NOTE:
    • If voice service is enabled in multiservice profile, voice parameters such as Voice VLAN, Voice Protocol is required in the Excel file. If voice service is not enabled in multiservice profile, after ONU goes online, the voice parameters configured in Excel file will not be delivered to devices.
    • The values of the manage VLAN, voice VLAN, and 802.1x VLAN parameters on the page must be consistent with those in the multiservice profile. If the values of other parameters are different from those in the multiservice profile, the values on the page will overwrite those in the multi-service profile.
    • If IP Interface is not configured in multiservice profile, after ONU goes online, the parameters configured in Excel file will not be delivered to devices.

  7. Click OK. If Excel file imported successfully, SN, Result and Detail will display in ONT list in Import tab.
  8. On the ONU Service Predeployment tab page, imported personalized parameters record of ONT will be added in the SN list.

Related Operation

Table 18-22 Related operations of Configuration Import Management page

Related Operation

Function

Import multiservice personalized parameters of ONT.

Refresh personalized parameters list after new Excel file imported.

Delete personalized parameters imported for an ONT.

Follow-up Procedure

Before ONU initially get online, editing personalized parameters needs to update Excel file and import it again. After the ONU goes online, you can alter the parameters through ONU Service Configuration function. For details, see (Optional) ONT Service Configuration Management.

Configuring a Zero Configuration Policy for an ONT

This topic describes how to create a zero configuration policy for an ONT by configuring the ONU model, Ethernet Ports and VLAN.

Prerequisites

  • An OLT has been added to eSight.
  • 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, Multiservice Profile, Type B dual-homing protection and click OK.

    NOTE:
    • ONU Type can be customized. Ensure that the user-defined ONU model is the same as the actual ONU model. Otherwise, the ONU cannot go online.
    • If TypeB Dual-Homing Protection is selected, typeB dual-homing protection will be applied to the zero-touch deployment policy. After this check 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 provisioning policy to a device or some ports of the device.

    NOTE:
    • A zero configuration policy can be bound to an OLT or specified ports of the OLT.
    • A zero-touch provisioning 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-touch provisioning policy.
NOTE:
  • Deployment tasks whose Task Status is Pending or Executing cannot be deleted.
  • If the task fails to be deployed, the device status may be abnormal. Check the ONU service configurations and bind the ONU again.
  • Choose PON Deployment > Zero Configuration Policies from the navigation tree on the left. Click to modify a zero-touch provisioning policy. Only Description and Mulitservice Profile can 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 provisioning policy from the devices.
  • When a working OLT or protection OLT is removed from eSight, associated device will be automatically unbounded.

(Optional) ONT Service Configuration Management

After multi-service profiles are bound to ONTs, you can set personalized parameters of the multi-service profiles and deliver the settings 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 profile, enter information, and save the file.

    NOTE:
    • Mandatory parameters in the table must be consistent with those in the multi-service profile created on eSight. Otherwise, import fails.
    • The following parameters can be set in batches in the file: SN Number, ONU Type, Template Name, ONU Name, Voice Protocol, SIP/MGC Server IP Address, SIP/MGC Server Port, Home domain, MGR VLAN, MGR IP Get Type, MGR IP Address, MGR IP Subnet Mask, MGR IP GATEWAY, VOICE VLAN, VOICE IP Get Type, VOICE IP Address, VOICE IP Subnet Mask, VOICE IP GATEWAY, Telephone Number, Terminal Flag, username, password, RADIUS VLAN, RADIUS IP Get the Type, RADIUS IP Address, RADIUS Subnet Mask, RADIUS IP GATEWAY.
    • The ONU menu on the PON resource management page can be used to export ONU SNs, which can be used for reference when setting the ONU SN field in the table. For details, see the export description in Managing ONUs.

  6. In Import tab, click and select the saved profile.
  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. (Optional) Click next to a record to set personalized parameters on the ONU Service Configuration page.

    NOTE:

    You can click under the voice user configuration to configure the phone number, authentication user name, and authentication password.

  9. Click OK.
  10. In ONU Service Configuration tab, imported profile record of ONU will be added in ONU list.

Related Operations

Table 18-23 Related operations of ONU Service Configuration page

Related Operations

Purpose

Import user-defined parameters of multiservice profile.

NOTE:

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

Configuring user-defined parameters of multiservice profile of ONU.

Delivering user-defined parameters of multiservice profile to ONU.

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

Follow-up Procedure

  • Click next to an ONU record to modify the multi-service profile for the ONU. If a created multi-service profile already has an IP interface whose Get Type is Static, you can set IP Address, Subnet Mask, and Default Gateway of the IP interface after clicked behind IP interface.
  • If the device has a voice interface and the profile voice protocol is SIP, you can set Phone Number. If the voice protocol is H.248, you can set Terminal Flag.
  • After the profile is modified, you need to click to deliver the update to the device.
  • Click next to a profile to check whether the profile parameters on eSight are consistent with those on the ONU. Click Send to the Device to overwrite data on the device with that on eSight.

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 18-6 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 PON.

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. The command customization page is displayed.

    NOTE:
    • The autosave time command is used to enable auto-saving for device configuration data at the preset time or set the auto-saving time. By default, this function is enabled and the configuration data is automatically saved at 00:00:00 every day. You can configure this function and the auto-saving time as required. For more information, see Command Reference of the corresponding device.
    • If the autosave time command is issued to the OLT, ensure that the device time is accurate.

  5. (Optional) Enter the command to be added in the text box, or click to import user-defined command files to add a user-defined command.

    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.
    • The input content (text) will be checked based on the whitelist. Invalid commands irrelevant to the configurations are not allowed.
    • Do not include high-risk operations or host commands containing sensitive information in user-defined commands. Otherwise, the device may be abnormal or sensitive information may be disclosed.

  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 a 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, PON 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 the 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 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 > Type B Dual-Homing Protection 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 Port Config.
    5. Click in the lower part of the page and configure the port information.
    6. Click OK to complete port configuration.
    7. Click OK to complete creating the type B dual-homing protection group. Applying result on the OLT will be displayed in Result dialog box.
    8. (Optional) Click Verify to check whether resource items consist with protection group information on the OLT. Click Deliver to apply port configuration on the OLT.
  • Configuring type B dual-homing protection group with command
NOTE:

Users can configure type B dual-homing protection group on the OLT 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 on the OLT.

  • Command example for configuring the 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 the 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 18-24 Operations on the page for configuring a type-B dual-homing protection group

Related Operations

Purpose

To create a type B dual-homing protection group.

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

To modify the selected protection group.

NOTE:

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

To delete the selected protection group.

NOTE:

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

To verify whether port configuration information consists of information in the protection group on eSight.

(Optional) Configuring Traffic Profiles

A user can configure a traffic profile on eSight to limit the upstream and downstream traffic speed.

Prerequisites

eSight is running properly.

Procedure

  1. Choose Resource > PON from the main menu.
  2. Choose PON Service > Equipment Profile Management > Traffic Profile from the navigation tree on the left.
  3. Click to set Profile Name, Description, CIR (kbit/s)(0-10240000), CBS (byte)(0-1024000000), PIR (kbit/s)(64-10240000), PBS (byte)(2000-1024000000), Priority Strategy, Priority (0-7) and Priority Mapping template in Traffic Template Management.

    NOTE:
    • If you deselect Do not limit speed, speed limit parameters can be set.
    • The PIR value varies with the input CIR value. By default, the PIR value is twice the input CIR value.
    • A speed restriction parameter can be set only if Default before it is deselected.
    • If the value of CIR/PIR is not an integral multiple of 64, the system automatically adjusts the value.

  4. Click OK.

Related Operations

Table 18-25 Related operations of traffic template management

Related Operation

Purpose

Create a traffic profile.

Delete selected traffic profiles in batches.

NOTE:

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

Modify traffic profile parameters.

NOTE:

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.

Binds a traffic profile to an OLT or ONU device.

NOTE:

If an ONU device is offline, the traffic profile cannot be bound to it due to the communication failure.

Copies an existing record and creates a traffic profile accordingly.

Delete a traffic profile.

NOTE:

A traffic profile referenced by a zero touch policy cannot be deleted.

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

NOTE:

An offline device cannot be verified.

Follow-up Procedure

If a traffic profile is referenced by multiple service profiles and delivered to devices successfully during zero touch provisioning, the system automatically generates binding relationships. You can click a traffic profile record to view the list of devices to which the traffic profile is bound. You can click next to a device record to check whether the traffic profile on eSight is the same as that on the device. If no, click Cover to deliver parameters.

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 18-26 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 provisioning policy to a device or some ports of the device.

    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 Pending or Executing cannot be deleted.
  • If the task fails to be deployed, the device status may be abnormal. Check the ONU service configurations and bind the ONU again.
  • After MxU zero configuration goes online, click Predeploy MxU to view the execution status of the Save configurations subtask.
  • Choose PON Deployment > Zero Configuration Policies from the navigation tree on the left. Click to modify a zero-touch provisioning 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 provisioning 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 section describes how to verify whether parameters of MxU configuration file exist on OLT and apply parameters that MxU lack of.

Prerequisites

  • An OLT 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 next to a configuration record in the configuration record 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 the MxU.

    NOTE:

    If the host packet switch is not in the default status, the verification result is displayed 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 18-27 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.

WLAN Service Configuration Management

You can configure the WLAN service for ONU devices that have been deployed and gone online in eSight.

Prerequisites

  • eSight is running properly.
  • An ONU has been added to eSight.

Procedure

  1. Choose Resource > PON from the main menu.
  2. Choose PON Service > ONU Service Configuration from the navigation tree on the left.
  3. Click .
  4. Click to download the WLAN template.
  5. Open the profile, enter information, and save the file.

    NOTE:

    VLANs in the table must be the same as the planned WLAN VLANs. Otherwise, services will be abnormal.

  6. On the Import tab page, click to select the saved profile.

    NOTE:

  7. Click Import. The import result of WLAN parameters is displayed in the list at the bottom of the tab page if imported successfully.

    NOTE:

    A maximum of 4 WLAN service records can be saved for an ONU device. If there are more than 4 records on the device after the new profile is delivered, old records are overwritten.

  8. Click OK.
  9. In ONU Service Configuration tab, imported profile record of ONU will be added in ONU list.

Related Operations

Table 18-28 Related operations of ONU Service Configuration page

Related Operations

Purpose

Imports the WLAN parameter setting profile.

NOTE:

After the profile is imported successfully, a deployment task is automatically generated and executed to deliver parameters to the devices.

Sets WLAN service parameters on the ONU.

Delivers the WLAN service parameters to the ONU.

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

Deployment Task Management

This function provides capabilities of managing tasks during PON device deployment, monitoring task execution status, and viewing failure information. In addition, the retry capability is provided.

Prerequisites

The device deployment task is successfully created and executed.

Procedure

  1. Choose Resource > PON from the main menu.
  2. Choose PON Deployment > Task Deployment from the navigation tree on the left.
  3. View the task progress, status, and execution result during device deployment.

    • Click to view task details.
    • If Last Execution Result of a task is Failed, click to re-deliver the task.

Translation
Download
Updated: 2019-09-12

Document ID: EDOC1100044378

Views: 72625

Downloads: 378

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