Overview

Configuring line profiles and service profiles on a GPON Optical Line Terminal (OLT) is foundational for managing subscriber services and network performance. A line profile defines the physical and data link layer parameters, including the mapping between GEM (GPON Encapsulation Mode) ports, T-CONTs (Transmission Containers), and VLANs, while a service profile manages the ONT/ONU's available interfaces and features via OMCI . This FAQ provides expert technical answers to the most common pre-sales and post-sales configuration questions for network engineers and architects.

Frequently Asked Questions

Q1: What is the difference between a line profile and a service profile in GPON OLT configuration?

A line profile defines the physical layer and traffic mapping rules (binding T-CONTs to DBA profiles and GEM ports to VLANs), while a service profile defines the ONT's logical service capabilities (enabling Ethernet, POTS, or CATV ports) and is managed via OMCI . The line profile determines *how* traffic is forwarded, and the service profile determines *which* services the ONT can provide.

Q2: How do I create a basic line profile for internet access on a GPON OLT?

Creating a line profile involves creating a DBA profile, defining a T-CONT, adding a GEM port, and mapping it to a VLAN. For a standard internet service, you create a line profile, bind the T-CONT to the DBA profile, add a GEM port, and map the VLAN ID . The basic CLI steps are:

1. Create a DBA profile: dba-profile profile-id 10 type3 assure 8192 max 20480
2. Create the line profile: ont-lineprofile profile-id 10
3. Bind the T-CONT to the DBA: tcont 1 dba-profile-id 10
4. Add a GEM port: gem add 11 tcont 1
5. Map the GEM port to a VLAN: gem mapping 11 1 vlan-id 100

After configuration, you must commit the changes and exit the profile .

Q3: How do I map multiple services (Internet, VoIP, IPTV) to different VLANs using a single line profile?

You map multiple services by adding multiple GEM ports within the same line profile, each bound to the same T-CONT but mapped to a different VLAN. This is often done in the GEM Mapping Rules section, where you bind the specific VLAN to a GEM port index . For example, you bind GEM port 11 to VLAN 100 (Internet), GEM port 12 to VLAN 200 (VoIP), and GEM port 13 to VLAN 300 (IPTV) .

Q4: What is the typical console (CLI) configuration procedure for initial OLT access and troubleshooting?

The initial console access requires using the correct serial cable and settings. Unlike standard routers, the OLT console port often requires a specific baud rate and the manufacturer-provided console cable to display output . After logging in (default credentials are often admin/admin), you can use CLI commands to troubleshoot. For instance, if an ONU fails to auto-discover, check that the PON port's autofind function is enabled and the optical module is the correct type for the standard (GPON vs. EPON) .

Q5: What does the DBA profile do, and how does it affect throughput?

A DBA (Dynamic Bandwidth Allocation) profile defines the upstream bandwidth parameters (assured and maximum bandwidth) allocated to a T-CONT to improve uplink utilization . This directly impacts the maximum throughput a subscriber can achieve. The DBA profile type dictates the bandwidth allocation method; for example, 'Type3' provides an assured bandwidth plus a maximum burstable rate, enabling line-rate performance for bursty data traffic .

Q6: What steps are involved in troubleshooting an ONU auto-discovery failure on a GPON port?

Troubleshooting starts by checking the PON port's laser status and autofind configuration. The most common steps are:

• Ensure ont autofind is enabled on the PON port.
• Verify the ONU is within the configured ranging distance.
• Check the PON port's laser is on and the optical module is functioning.
• If the ONU is found but fails to provision, run display ont capability to check if the line and service profiles match the ONU's capabilities .

A mismatch in profiles will cause the ONU to display a 'mismatch' state .

Q7: Can I authenticate an ONU using SN and PLOAM password when integrating into the OLT?

Yes, GPON ONUs support multiple authentication methods that are defined in the line profile, including SN, SN+PLOAM password, and SN+LOID . The specific method is chosen during the ONU registration process, typically with the ont add command, which references the line profile configured to match the chosen authentication method.