How to configure Optical Line Terminal (OLT) and Omada Switch with XM60A

Configuration Guide
Updated 06-29-2024 03:43:19 AM 3668
This Article Applies to: 

This Article Applies to All GPON OLT Products and all Omada Switches with optical ports.

1. Application Scenario

An apartment wants to use the XM60A to enable Omada equipment to access the OLT for networking and flexible deployment.

They have the following demands in this example.

1) The switches with XM60A are deployed in each region and connected to the GPON network. After registration, the switches should be able to communicate with the OLT via the GPON network.

2) There are multiple services for the user, including Internet service, VOIP service, and IPTV service. Different types of traffic should be managed separately in different VLANs.

2. Configuration scheme

2.1 Defining VLANs

VLAN 01 For Management

VLAN 10 For Internet

VLAN 20 For VOIP

VLAN 30 For IPTV

2.2 Configuration Ideas

To meet the demands, we have the following configuration ideas.

  1. Configure DBA Profile
  2. Configure Line Profile
  3. Register ONU
  4. Configure Service Ports for Service Flow
  5. Configure VLAN
  6. Configure the IGMP Snooping For IPTV

For demonstration purposes, we’ll take one ONU(XM60A), which is connected to the OLT’s PON Port 1, as a configuration example. Configuration steps for the other ONU should be similar.

3. OLT&Switch Configuration on Standalone mode

3.1 Configure DBA Profile

DBA (Dynamically Bandwidth Allocation) profile describes the GPON upstream traffic parameters.

A T-Cont is bound to a DBA profile for dynamic bandwidth allocation, improving the upstream bandwidth usage rate, which we’ll create in a line profile afterward. And more about T-Cont is covered in 3.2.

Below is a detailed description of the several types of DBA Profiles.

Type

Description

Fix

Indicates a DBA profile of the fixed bandwidth type. The fixed bandwidth is reserved for a specified ONU or certain services of the ONU. It cannot be used for other ONUs even when the upstream service stream is not transmitted on the ONU. This type of bandwidth is mainly used for services, such as TDM and VoIP, that have a high QoS requirement.

Assure

Indicates a DBA profile of the assured bandwidth type. The assured bandwidth is the available bandwidth of an ONU when the ONU requires the bandwidth. When the actual service stream does not reach the assured bandwidth, the DBA mechanism of the device is used to allocate the remaining bandwidth to the services of other ONUs. Because of the DBA mechanism that allocates the remaining bandwidth to services of other ONUs, the assured bandwidth has a poorer real-time performance than fixed bandwidth does.

Assure+Max

Indicates a DBA profile of the assured bandwidth + maximum bandwidth type. This type of bandwidth is the bandwidth of the combined type. When it is used, the user is allocated a certain bandwidth and at the same time occupies certain bandwidths. The total bandwidth, however, cannot exceed the maximum bandwidth configured for the user. This type of bandwidth is mainly used for VoIP and IPTV services.

Max

Indicates a DBA profile of the maximum bandwidth type. This type of bandwidth is the maximum bandwidth that can be used by an ONU to meet the ONU bandwidth requirement to the greatest extent. It is used for services such as Internet access service.

Fix+Assure+Max

Indicates a DBA profile of the fixed bandwidth + assured bandwidth + maximum bandwidth type. This type of bandwidth is the bandwidth of the combined type. When it is used, the user is allocated a fixed bandwidth that cannot be used by other users. In addition, the user can use the assured bandwidth when necessary and can occupy certain bandwidths. The total bandwidth, however, cannot exceed the maximum bandwidth configured for the user

Go to PON > Profile > DBA, and click +Add to configure DBA profiles according to the requirements of each service.

3.2 Configure Line Profile

In the Line Profile, we create T-CONTs, GEM ports, and GEM mapping rules.

T-Cont: T-CONT (Transmission Container), functions as a tunnel that contains several GEM ports.

It is mainly used as a unit for transmitting uplink data, and T-CONT is introduced mainly to solve the problem of dynamic allocation of uplink bandwidth to improve line utilization.

GEM Port: GEM (GPON Encapsulation Mode) ports are the smallest bearer units of the service.

GEM ports can be flexibly mapped to T-Cont, one GEM port can be mapped to one T-Cont, and multiple GEM ports can be mapped to the same T-Cont.

GEM mapping rule: Services are mapped to GEM ports according to the mapping rules, and then mapped to T-Cont for upstream transmission.

A line profile describes the binding between the T-Cont and the DBA profile, the QoS mode of the traffic stream, and the mapping between the GEM port and the ONU-side service.

3.2.1 Go to PON > Profile > Line and click edit to configure line profile 0. Then click +Add in T-Conts to create T-Conts and bind them to the corresponding DBA Profiles.

Bind T-Cont 1 to DBA profile 0, we will subsequently use T-Cont 1 for the Management VLAN.

Bind T-Cont 2 to DBA profile 1, we will subsequently use T-Cont 2 for the Internet VLAN.

Bind T-Cont 3 to DBA profile 2, we will subsequently use T-Cont 3 for the VOIP VLAN.

Bind T-Cont 4 to DBA profile 3, we will subsequently use T-Cont 4 for the IPTV VLAN.

This is the end of the configuration of the T-Conts.

3.2.2 Go to PON > Profile > Line > GEM Ports, and click +Add to create GEM ports and bind them to the corresponding T-Conts.

3.2.3 Go to PON > Profile > Line > Gem Mapping Rules, and click +Add to bind services to the corresponding GEM ports.

Bind the Internet VLAN with GEM port 2.

Bind the VOIP VLAN with GEM port 3.

Bind the IPTV VLAN with GEM port 4.

This is the end of the configuration of the GEM mapping rules.

3.3 Register ONU

After connecting the ONU to the GPON network, the ONU is auto-found by the OLT. Then you need to authenticate and register the ONU. You can also set auto authentication for ONUs.

After the ONU is registered, the ONU goes online and can communicate with the OLT via the GPON network.

We have the following three methods to authenticate and register ONUs:

• Authenticate and register the ONU manually after the ONU is found by the OLT

• Authenticate and register the ONU beforehand

• Auto-Authenticate and register the ONUs in batches beforehand

In this article we use Auto-Authentication. Go to PON > ONU Register > Auto Authentication, and enable Auto Authentication in Auto Authentication Config.

Then enable automatic authentication for the port where the ONU is located and set the authentication method to SN-Auth below.

After the authentication is successful, go to PON > ONU Register > Authentication Config, check the ONU ID for subsequent configuration, as you can see the ONU ID is 0 here.

3.4 Configure Service Ports for Service Flow

Service ports are used by OLT to map different types of traffic to different SVLANs according to PON ports, ONUs, GEM ports, and User VLANs, and then transmitted to the uplink network.

In this example, we want the internet traffic in User VLAN 10 of GEM Port 2 to be mapped to SLAN 10, the VOIP traffic in User VLAN 20 of GEM Port 3 to be mapped to SVLAN 20, the IPTV traffic in User VLAN 30 of GEM Port 4 to be mapped to SVLAN 30.

Simultaneously, we could apply the traffic profiles, which we have created previously, according to the types of traffic.

Go to PON > Service Ports > Service Ports, and click +Add to build the connection between the traffic of the user side (CVLAN) and the traffic of the upper-layer network (SVLAN). Just leave the traffic profile as default.

Note that we need to configure the TAG ACTION as Transparent here.

If keep the default configuration, due to the existence of both user VLANs and service VLANs, the default configuration will result in data emitted by the upstream port having a two-layer VLAN tag (QinQ), resulting in user-side data not reaching the server.

3.5 Configure VLAN

Switch 1:

Take SG3428X as an example.

Go to L2 FEATURES > VLAN > 802.1Q VLAN, and click +Add to create VLAN 10. Add the ports connected to the Router and OLT as tagged ports (Here are port 25 and port 26).

Create VLAN 20. Add the port connected to OLT as a tagged port (Here is port 26), and add the port connected to the SIP Server as an untagged port (Here is port 1).

Create VLAN 30. Add the port connected to OLT as a tagged port (Here is port 26), and add the port connected to the IPTV Server as an untagged port (Here is port 2).

Configure the corresponding PVIDs for the ports where the SIP Server and the IPTV Server are located respectively.

For port 3, where the PC for management is located, we don't need to do any special configuration, just keep the default configuration so that it is in VLAN 1.

This is the end of the configuration of the VLANs on Switch 1.

OLT:

Take DS-P7001-04 as an example.

Go to L2 FEATURES > VLAN > 802.1Q VLAN.

The VLAN here is equal to the Service VLAN, we need to create as many VLANs as existing Service VLANs.

Click +Add to create VLAN 10 and add the uplink port as a tagged port (Here is port XGE 1).

Configure VLAN 20 and add the uplink port as a tagged port (Here is port XGE 1).

Configure VLAN 30 and add the uplink port as a tagged port (Here is port XGE 1).

This is the end of the configuration of the VLANs on OLT.

Switch 2:

Take SG2210MP as an example.

For EAP directly connected to the switch, we configure the port where it is located as VLAN tagged and keep the corresponding PVID default.

For clients(VOIP/IPTV/PC/…) directly connected to the switch, we configure the port where it is located as VLAN untagged and configure the corresponding PVID for the port.

Go to L2 FEATURES > VLAN > 802.1Q VLAN, and click +Add to create VLAN 10.

Add the ports connected to the EAP and OLT as tagged ports (Here are port 1 and port 9), and add the port connected to the PC as an untagged port (Here is port 2).

Create VLAN 20. Add the port connected to OLT as a tagged port (Here is port 9), and add the port connected to the VOIP as an untagged port (Here is port 3).

Create VLAN 30. Add the port connected to OLT as a tagged port (Here is port 9), and add the port connected to the IPTV as an untagged port(Here is port 4).

Configure the corresponding PVIDs for the ports where the EAP, the PC, the VOIP, and the IPTV are located respectively.

This is the end of the configuration of the VLANs on Switch 2

3.6 Configure the IGMP Snooping For IPTV

Go to Multicast > IGMP Snooping > Global Config, and enable IGMP Snooping in Global Config.

Enable IGMP Snooping for IPTV VLAN in IGMP VLAN Config and disable both Fast Leave and Report Suppression.

Add the uplink port as a static router port (Here is port XGE 1).

For more configuration guidance about IGMP Snooping on Omada Router and Switch, please refer to the following documents:

How to configure IGMP Snooping on Omada switches for hotel IPTV scenario | TP-Link

4. OLT Configuration on Omada SDN Controller

Support for some OLT devices has been added in Omada SDN Controller version 5.14.20 and above, for example, DS-P7001-04 V1, DS-P7001-08 V1.10.

Note: Omada SDN Controller will not lose the OLT configuration after adopting an OLT device but we are no longer able to configure the OLT device using the OLT GUI.

First, decide which site you want to add the devices to. On the controller configuration page, select the site from the drop-down list of Organization.

Go to Device, and devices that have been discovered by the controller are displayed.

Click the Adopt button in the ACTION column of the devices that you want to add to the site. Wait until the STATUS turns into Connected. Then the devices are adopted by the controller and added to the current site.

Then in the Properties window, we can click Settings to configure the OLT features in Config.

For more configuration guidance about Omada SDN Controller, please refer to the following documents:

static.tp-link.com/upload/manual/2023/202311/20231122/1910013481_Omada SDN Controller_ User Guide_REV5.12.pdf

5. OLT Configuration on DeltaStream PON Management System (DPMS)

Note: DPMS will not lose the OLT configuration after adopting the OLT device and we are still able to configure the OLT device using the OLT GUI, and the configuration data on both sides will be synchronized automatically.

Go to Device, and devices that have been discovered by the controller are displayed.

Click the Adopt button in the ACTION column of the devices that you want to add to the site. Wait until the STATUS turns into Online. Then the devices are adopted by the DPMS.

Then in the Properties window, we can click the device name to configure the OLT.

For more configuration guidance about DPMS, please refer to the following documents:

1910013088-DPMS User Guide.pdf (tp-link.com)

For more configuration guidance about OLT, please refer to the following documents:

static.tp-link.com/upload/manual/2024/202402/20240206/1910013370-OLT User Guide.pdf

Questa faq è utile?

Your feedback helps improve this site.

Recommend Products

From United States?

Get products, events and services for your region.