How do I limit the downstream and upstream traffic on GPON OLT P1201?

Note: This Article Applies to TP-Link GPON OLT P1201 Ver.1

As a service provider, one of the factors we care about much is the traffic limitation. So how can we limit the downstream and upstream traffic on the OLT? Here is the guide for the operation. It can be achieved based on Service (GEM port), T-cont and even the physical port.

A: CLI

I. Based on Physical Port.

If you want to limit the uplink GE port and downlink PON port stream. You can use the Rate Limit function which is based on the physical ports.

OLT(config)interface ge 0/0

OLT(config-interface-ge-0/0)#port-rate <port-list> {egress|ingress} <rate>

ONT(config)interface gpon 0/0 

OLT(config-interface-gpon-0/0)#port-rate <port-list> {egress|ingress} <rate>

For example:

OLT(config-interface-ge-0/0)#

OLT(config-interface-ge-0/0)#port-rate 1 egress 102400

Here the Egress and Ingress mean the Upstream and Downstream. By this command, you can limit the bandwidth of the ports from 64-10240000Kbps.

II. Based on T-cont.

Here we are talking about the traffic limitation based on T-cont is the DBA profile. The deployment and control of Uplink Bandwidth of ONT is realized through the Dynamic Bandwidth Allocation technology. DBA Profile defines the uplink bandwidth of ONU. Device adjusts the allocation of uplink bandwidth automatically according to the burst need of uplink services, which increases the uplink bandwidth service efficiency of PON system.

OLT(config)# dba-profile profile-id <profile-id > |profile-name <profile-name>

OLT(config-dba-profile-10)#type1 fix<fixed bandwidth>

OLT(config-dba-profile-10)#type2 assure<assure bandwidth>

OLT(config-dba-profile-10)#type3 assure<assure bandwidth>max<max bandwidth>

OLT(config-dba-profile-10)#type4 max<max bandwidth>

OLT(config-dba-profile-10)#type5 fix<fixed bandwidth> assure<assure bandwidth>max<max bandwidth>

For example:

OLT(config)# dba-profile profile-id 10

OLT(config-dba-profile-10)#type5 fix 5120 assure 10240 max 30720

As you can see, there are 5 types we can choose to define the DBA Profile.

<type1>: Fix bandwidth. It is reserved to specified ONU or the specific service of ONU, this bandwidth cannot be used by other ONU even if the ONU has not uplink service stream. It is mainly used in the service with hypersensitive QoS, such as TDM, VoIP and etc.

<type2>: Assure bandwidth. It assures that ONU can obtain a specified bandwidth when it is in need. Device’s dba mechanism could allocate the surplus bandwidth to other ONU’s service when the real time service stream of ONU cannot reach the assure bandwidth. Its real time performance is worse than fixed bandwidth for the reason that it needs to control the allocation of bandwidth according to dba mechanism.

<type3>: Type3 includes assure bandwidth and max bandwidth.Type3 is a combination bandwidth type which assures the user has a certain bandwidth and it commits that the user has a certain bandwidth to preempt. But the sum of assure bandwidth cannot exceed the max bandwidth. This kind of bandwidth is mainly used in VoIP and IPTV service.

<type4>: Max bandwidth. The upper limit of bandwidth that the ONU can obtain. It is mainly used in internet service.

<type5>: Type5 includes fixed bandwidth and assure bandwidth and max bandwidth. Type5 is a combination bandwidth type. The sum of fix bandwidth and assure bandwidth cannot exceed the max bandwidth.

Then we need to bind it to a T-cont to make the DBA profile work.

OLT(config)# ont-lineprofile profile-id 10

OLT(ont-lineprofile-10)# tcont 1 dba-profile-id 10

III. Based on Service.

For most cases, we want to limit the bandwidth based on each kind of services, not only the ports. For example, we provide 3 kinds of service to customers, internet access, VoIP and IPTV. All of them are bind into one Tcont, while in different GEM port. Here we can use the Traffic Profile to limit the bandwidth of each service apart.

OLT(config)# traffic-profile profile-id <Profile ID> profile-name <profile name> cir <committed-rate-value> pir < peek-rate-rate> cbs <committed-burst-size> pbs < peek-burst-size>

For example:

OLT(config)#traffic-profile profile-id 10 profile-name test1 cir 128 pir 256 cbs 2000 pbs 3000

Here the parameters meaning:

<CIR>: Committed Information Rate, range for 64-10240000, unit is kbps;

<PIR>: Peek Information Rate, range for 64-10240000, unit is kbps;

<CBS>: Committed Burst Size, range for 2000-10240000, unit is byte;

<PBS>: Peek Burst Size, range for 2000-10240000, unit is byte;

After that, we need to bind it to service port to make it work.

OLT(config)# service-port 3 vlan 100 gpon 0/0 port 4 ont 1 gemport 2 multi-service user-vlan 100 tag-action transparent inbound name test1 outbound name test1

B: EMS

I. Based on T-cont.

First of all, we need to create the DBA profile. Go to the Pon Card Management and choose DBA Profile Config. Click Add to create a new DBA profile.

Then go to Line Profile Config to bind it to the Tcont.

II. Based on Service.

First of all, we need to create the traffic profile. Go to Pon Card Management and choose Traffic Profile Config. Click Add to add a new traffic profile.

Then, bind the traffic profile to service port to make it work. Go to Service Port Config, click Config to set the traffic profile.