As the information society continues to develop, people increasingly demand higher network speed and quality. Fiber to the home (FTTH) technology, an important means of meeting this requirement, is increasingly used in the construction of global broadband networks. Gigabit-capable Passive Optical Network (GPON), as an efficient FTTH technology, has become the mainstream choice for broadband access networks.

GPON is a point-to-multipoint optical network transmission technology. GPON uses optical fibers and passive optical splitters to enable a single optical network interface to connect multiple endpoints. This network structure significantly reduces the cost of network construction and operations and provides higher data transmission bandwidth (reaching Gbps levels).

Technical benefits of GPON

Compared with other broadband access technologies like asymmetric digital subscriber line (ADSL), very high-speed digital subscriber line (VDSL), and Ethernet Passive Optical Network (EPON), GPON technology has significant technical advantages. GPON supports higher data transmission rates, with a theoretical maximum of 10 Gbps for both upstream and downstream rates. GPON provides excellent quality of service (QoS), efficient bandwidth usage, and good security performance. Additionally, GPON network construction and maintenance costs are relatively low because GPON uses passive optical splitters, which do not require power, thus reducing energy consumption and failure rates.

GPON network model

As shown in Figure 1, GPON can simultaneously carry Internet, Voice over Internet Protocol (VoIP), and Internet Protocol Television (IPTV) services in the same network topology, achieving "triple play". The typical network model of GPON includes the following parts:

· Optical line terminal (OLT)—Core device of a GPON system, typically located at the central office. The OLT uniformly manages ONUs in the GPON system, and aggregates and transmits the access traffic to the IP network.

· Optical network unit (ONU)—Customer-side device in a GPON system. An ONU connects to user PCs, set-top boxes, and switches, and is typically deployed at a user home, corridor, or road side. An ONU responds to the management commands sent by an OLT, and forwards user data to the OLT.

· Optical distribution network (ODN)—An ODN contains optical fibers, one or more passive optical splitters (POSs), and other passive optical components. An ODN provides optical signal transmission paths between OLT and ONU. A POS aggregates upstream data into a single fiber and distributes downstream data to respective ONUs. An OLT uses POSs to provide upstream data access for multiple ONUs through one physical interface. In theory, a GPON network can achieve a maximum split ratio of 1:128. In this case, one physical interface on an OLT device can provide upstream data access for 128 ONUs.

Figure 1 Typical GPON network model

GPON terms

This document uses the following key GPON terms:

· Wavelength Division Multiplexing (WDM)—WDM multiplexes multiple optical signals onto a single optical fiber by using different wavelengths, significantly increasing transmission capacity.

· Time Division Multiple Access (TDMA)—TDMA divides time into multiple time slots and allocates each time slot to a user for communication. TDMA can improve the spectrum usage.

· Dynamic Bandwidth Assignment (DBA)—An OLT uses DBA to dynamically assign available upstream traffic bandwidth to different ONUs.

· GPON Encapsulation Method (GEM)—Connection-oriented data frame transmission scheme used in GPON systems. GEM supports fragmenting user data into multiple GEM frames.

· GPON Transmission Convergence (GTC)—GTC converges GEM frames into GTC frames, which are the basic data transmission units in the GPON protocol.

· Transmission container (T-CONT)—A T-CONT is a group of logical connections in the transmission process on the GPON network, and it is used to identify and differentiate data of different services.

How GPON works

GPON uses asymmetric transmission for upstream traffic and downstream traffic. Upstream traffic refers to traffic transmitted from ONU to OLT, and downstream traffic refers to traffic transmitted from OLT to ONU. In a GPON system, downstream traffic is broadcast by using WDM and upstream traffic is unicast by using TDMA. The following information describes the upstream and downstream communication principles of GPON, as well as the key technologies involved.

Downstream communication principles of GPON

Figure 2 Downstream traffic forwarding model

As shown in Figure 2, in the downstream direction, the OLT uses only GEM ports to distinguish GEM frames from different downstream logical connections and transmits these GEM frames to ONUs by using WDM in the optical network. An ONU receives all GEM frames broadcast by the OLT, but it filters the downstream GEM frames based on the GEM port IDs it uses. The ONU processes only the GEM frames containing the GEM ports used by the ONU, as shown in the following figure.

Figure 3 Downstream traffic forwarding process

The wavelength range for downstream traffic is 1480 to 1500 nm for the GPON technology, and that is 1575 to 1580 nm for the XG(S)-PON technology.

Upstream communication principles of GPON

Figure 4 Upstream traffic forwarding model

As shown in Figure 4, in the upstream direction, after the OLT grants an ONU the upstream transmission opportunity (as described in Key GPON technology: DBA), the ONU encapsulates and fragments the upstream data into multiple GEM frames based on GEM ports. Then, the OLT assigns data of different services to different logical links for transmission based on T-CONTs. The data in different T-CONTs are transmitted in time slots allocated by the OLT, achieving time division multiplexing (TDM). During the upstream traffic forwarding process, the GEM port IDs and Alloc-IDs serve as key identifiers to distinguish between GEM frames and T-CONTs, respectively.

The wavelength range for upstream traffic is 1290 to 1330 nm for the GPON technology, and that is 1260 to 1280 nm for the XG(S)-PON technology.

Key GPON technology: DBA

About DBA technology

The DBA mechanism primarily allocates upstream bandwidth for traffic from OLT to ONU. DBA ensures network resource efficiency, and guarantees QoS for users and fairness among different service types (such as voice, video, and data). In a GPON network, multiple ONUs share the upstream channel to the OLT, so you must use the DBA mechanism to allocate upstream bandwidth reasonably to avoid conflicts and improve bandwidth usage.

In the DBA mechanism, the OLT indicates the time when an ONU can transmit data (time slot) and the bandwidth for upstream data transmission through the BWmap field in the GTC frame header. Each T-CONT of an ONU has a specific time slot for upstream data transmission, avoiding upstream conflicts, as shown in Figure 5.

Figure 5 Schematic diagram for upstream data transmission in a GPON Network

In fact, the time slots allocated by the OLT to T-CONTs are related to the bandwidth allocated to them. For example, if the OLT allocates an upstream time slot of 250 microseconds and a bandwidth of 1.25 Gbps to a T-CONT of an ONU, the ONU can use the T-CONT to transmit the following data within the allocated time slot: (250 × 10^(-6))s × (1.25 × 10^9) bps ÷ 8 = 39062.5 bytes of data.

QoS mechanism for DBA: Bandwidth allocation modes and T-CONT types

In actual bandwidth allocation applications, the following bandwidth allocation modes are available for providing different QoS levels to different types of services:

· Fixed bandwidth (FB)—After the OLT allocates the fixed bandwidth to an Alloc-ID (T-CONT), only this Alloc-ID can always use this portion of bandwidth without being affected by the bandwidth requirements of the other Alloc-IDs. The fixed bandwidth can be considered as the private bandwidth allocated by the OLT to the Alloc-ID. The FB mode is suitable for services that require strict QoS but use relatively low bandwidth, such as voice or real-time video services.

· Assured bandwidth (AB)—Minimum bandwidth that the OLT assures for an Alloc-ID when the Alloc-ID requires bandwidth. The OLT must provide assured bandwidth as long as the Alloc-ID's bandwidth requirement is not met and exceeds the Alloc-ID's fixed bandwidth. The assured bandwidth can be considered as a "deposit" of bandwidth that the OLT allocates to an Alloc-ID, and it is available on demand. However, if the Alloc-ID has no requirement for the assured bandwidth, the assured bandwidth can be allocated to other Alloc-IDs. The assured bandwidth mode is suitable for services requiring certain QoS assurance but more flexibility than fixed bandwidth, such as regular data transmission services.

· Non-assured bandwidth (NAB)—Additional bandwidth that the OLT can allocate to an Alloc-ID beyond the fixed bandwidth and assured bandwidth. However, the system does not guarantee that the Alloc-ID can use this bandwidth. The non-assured bandwidth operates on a "first come, first served" basis.

· Best-effort bandwidth (BE)—Additional bandwidth that the OLT can allocate to an Alloc-ID from the remaining bandwidth resources beyond the fixed bandwidth, assured bandwidth, and non-assured bandwidth. The BE bandwidth is not guaranteed and has the lowest priority, and also operates on a "first come, first served" basis. The BE bandwidth is suitable for Internet browsing or email services that have almost no bandwidth requirements.

As shown in Figure 6, T-CONTs include the following types based on different combinations of bandwidth allocation modes.

· Type 1—This type of T-CONT can use the maximum bandwidth equal to its fixed bandwidth.

· Type 2—This type of T-CONT can use the maximum bandwidth equal to its assured bandwidth.

· Type 3—This type of T-CONT can use not only its assured bandwidth but also non-assured bandwidth.

· Type 4—This type of T-CONT can use only the best-effort bandwidth.

· Type 5—This type of T-CONT can use all types of bandwidth, including fixed bandwidth, assured bandwidth, non-assured bandwidth, and best-effort bandwidth.

Figure 6 Relationship between T-CONT types and bandwidth allocation modes

Key technology of GPON: Ranging

About ranging

In a GPON network, interface delay issues still exist even though the OLT use DBA to assign upstream time slots to T-CONTs and optical signals travel significantly faster in fibers than electrical signals. This is because multiple ONUs share the same upstream optical link. Due to the long physical distances between the OLT and ONUs, which are often in different states and located at varying distances, upstream data transmissions might not strictly adhere to their time slots. This can lead to collisions on the shared upstream optical fiber, as shown in Figure 7.

Figure 7 Schematic diagram for upstream data collisions

Therefore, the GPON network requires precise measurement of the physical distance between the OLT and each ONU. Based on these measurements, the system calibrates the upstream data transmission timing to ensure strict adherence to allocated time slots and prevent collisions. This process is called GPON ranging technology.

The ranging technology enables the OLT to allocate an equalization delay (EqD) to each ONU based on the ranging results. An ONU waits for the allocated EqD duration before transmitting upstream data to ensure the upstream signals arrive at the OLT in the correct time slot. The OLT allocates different EqDs to each ONU to compensate for their varying physical distances, ensuring a uniform logical distance during upstream data transmission. This mechanism guarantees strict adherence to allocated time slots, thereby preventing collisions, as shown in Figure 8.

Figure 8 How ranging works

Ranging process

Figure 9 Ranging process in a GPON network

As shown in Figure 9, the specific process of GPON ranging is as follows:

2. Upon powering up, a GPON ONU registers with the OLT for the first time.

3. The OLT sends a specific ranging message to the ONU.

4. Upon receiving the ranging message, the ONU replies immediately.

5. After receiving the reply, the OLT calculates the round-trip time of the ranging message. Also, the OLT calculates the physical distance between the ONU and OLT based on the propagation speed of optical signals in optical fibers. Then, the OLT sets an appropriate EqD for the ONU based on the calculated physical distance.

6. The OLT communicates the EqD set for the ONU by using the downstream control-plane GTC frames.

7. After receiving the EqD, the ONU uses the EqD for all subsequent upstream data transmission.

GPON protocol stack

About GPON protocol stack

A GPON network supports simultaneously carrying multiple services, such as Ethernet and TDM services, each with a unique data structure. Because the ODN cannot directly transmit these services over optical fiber links, GPON must standardize these services for transmission. Therefore, GPON uniquely defines a GPON transmission convergence (GTC) layer. The GTC layer is primarily used to adapt and map upper-layer data flows (typically, Ethernet frames and TDM frames) onto the physical layer of GPON. This ensures that all service traffic in the ODN is uniformly carried in GTC frames. The protocol stack of the GTC layer is shown in Figure 10.

Figure 10 GPON protocol stack

The GTC layer is divided into two sublayers: the GTC adaptation sublayer and the GTC framing sublayer.

· The GTC adaptation sublayer is responsible for adapting data and encapsulating data flows from different services into GEM frames. GEM is the encapsulation protocol used in GPON networks, and it supports various services and multiple QoS levels. On the GTC adaptation sublayer, data is allocated to different GEM ports, each of which can be associated with different service flows and QoS levels.

· The GTC framing sublayer is responsible for generating and resolving GTC frames. A GTC frame is the basic unit for data transmission on the GPON physical layer. GTC frames include upstream frames and downstream frames. The GTC framing sublayer combines GEM frames and other control information to form GTC frames. Then, these frames are transmitted to the physical layer for optical signal conversion and transmission. In the downstream direction, the GTC framing sublayer also provides DBA control information to inform each ONU of their upstream transmit time slots.

The preceding two sublayers work together to adapt and encapsulate upper-layer data flows for transmission over the GPON physical layer. The GTC adaptation sublayer first encapsulates the upper-layer data flows into GEM frames and processes them appropriately to meet the service requirements and QoS requirements of different service flows. Subsequently, the GTC framing sublayer further integrates GEM frames and necessary control informations into GTC frames and transmits these frames to the physical layer of GPON for transmission. Both layers ensure efficient and reliable transmission of data in GPON networks.

The protocol stack shown in xxx includes various types of traffic.

· Physical Layer Operations, Administrations and Maintenance (PLOAM)—Responsible for delivering control information for managing and maintaining the GPON physical layer, used for communication and network management and maintenance between OLT and ONU.

· ONU Management and Control Interface (OMCI)—Used to manage and control ONUs. OMCI defines a mechanism for the OLT to remotely configure ONU ports, services, performance, and state.

· GEM client—The GEM client mainly encapsulates different service data into GEM frames and meets QoS requirements.

GPON service traffic mapping

In the current software version, GPON mainly supports Ethernet and TDM services. They are mapped to the GTC layer in different ways, as shown in Figure 11 and Figure 12.

Figure 11 Ethernet frame mapping mode

Figure 12 TDM frame mapping mode

For the Ethernet service, the GPON system retains only the data portion of an Ethernet frame and maps the data portion to the GEM payload. The GTC layer encapsulates the GEM frame header and GTC frame header for transmission over the physical layer.

For the TDM service, the GPON system does not recognize the specific content of TDM frames and directly maps TDM data into the GEM payload. The GTC layer then encapsulates the GEM header and GTC header for transmission over the physical layer. Therefore, TDM service data is transparently transmitted.

GPON packet structure

Downstream packet structure

As shown in Figure 13, the downstream GTC frame of GPON is a fixed-length packet of 125 microseconds, including physical control block downstream (PCBd) and payload.

Figure 13 PCBd portion in the downstream GPON packet structure

Among them, PCBd carries the control information for downstream data transmission, and provides necessary control and management information for downstream communication. The PCB field contains the following fields:

· Psync—Physical synchronization field that begins every PCBd.

· Ident—Used to indicate larger framing structures.

· PLOAM—Carries control information for the OLT to manage, operate, and maintain ONUs. The field contains the following sections:

¡ ONU ID—Identifier allocated by the OLT to an ONU for ONU-based management.

¡ Message ID—PLOAM message type.

¡ Data—OAM control information.

¡ CRC—Checksum.

· BIP—Bit interleaved parity.

· PLend—Length of the GTC payload in bytes. PCBd might carry two instances of this field for error robustness.

· Upstream BWmap—Upstream bandwidth map that indicates the transmission time slots in the upstream direction for each Alloc-ID corresponding to a T-CONT. This field contains several allocation structures, each corresponding to a T-CONT. An allocation structure contains the following parts:

¡ Alloc-ID—Identifies a T-CONT.

¡ Flags—Controls certain functions of the associated upstream transmission.

¡ StartTime—Indicates the start time for the T-CONT to begin transmitting upstream data. This time is measured in bytes, starting with zero at the beginning of the upstream GTC frame.

¡ StopTime—Indicates the latest time allocated to the T-CONT for transmitting upstream data. This time is measured in bytes, starting with zero at the beginning of the upstream GTC frame.

¡ CRC—Checksum.

Figure 14 Payload section of the downstream GPON packet structure

As shown in Figure 14, the payload section of the downstream GTC frame contains multiple GEM frames for transmitting specific service data. Each GEM frame contains a GEM header and GEM payload. The GEM header includes the following fields:

· Payload Length Indicator (PLI)—Indicates the GEM payload length.

· Port-ID—Key information used to differentiate between GEM ports.

· Payload Type Indicator (PTI)—Indicates the type of GEM payload.

· Header Error Control (HEC)—Detects and corrects GEM frame header errors during data transmission.

Upstream packet structure

As shown in Figure 15, the length of an upstream GTC frame is the same as that of a downstream GTC frame, both fixed at 125 microseconds. However, the structure of an upstream GTC frame is different from that of a downstream GTC frame. An upstream GTC frame contains multiple upstream bursts, which might be transmitted by multiple ONUs within their respective time windows according to the transmission bandwidth and time slots allocated by the OLT. Because the bursts are transmitted sequentially and continuously, they are treated as a single GTC frame. Each burst transmitted in a GTC frame actually carries independent data or performs a separate function.

Figure 15 Comparison of upstream GTC frames and downstream GTC frames

As shown in Figure 16, each upstream burst contains an upstream physical layer overhead (PLOu) section and one or more bandwidth allocation intervals associated with Alloc-IDs. Each allocation interval represents the time interval allocated for transmitting upstream data for a T-CONT. Each burst corresponds to an ONU, and the PLOu section contains the ID of the ONU.

Figure 16 Upstream burst packet structure

An upstream burst packet includes the following fields:

· Guard time—Specifies the interval between upstream bursts to prevent collisions.

· Preamble—Used by the OLT to achieve receive synchronization.

· Delimiter—Indicates the start of a burst.

· BIP—Bit-interleaved parity.

· ONU-ID—Unique identifier for an ONU, allocated by the OLT. The ONU-ID field is 8 bits long, so the maximum value for an ONU-ID is 255.

· Ind—Provides real-time ONU status reports to the OLT.

· PLOAMu—Carries control information for managing, operating, and maintaining an ONU. This field has the same structure as the PLOAM field in a downstream GTC frame, as shown in Figure 17. Only the allocation interval for the default Alloc-ID of the ONU carries this field.

Figure 17 PLOAM field structure

· Dynamic Bandwidth Report Upstream (DBRu)—Contains information associated with a T-CONT, and allows the ONU to report its bandwidth requirements, QoS requirements, and authorized bandwidth usage to the OLT. This field helps the OLT adjust future bandwidth allocation.

· Payload—Payload in an upstream GTC frame. This field contains multiple GEM frames for carrying service data and has the same structure as a downstream GEM frames, as shown in Figure 18.

Figure 18 Payload field structure

ONU registration

In a GPON network, adding a new ONU to an existing GPON system follows a standardized process known as the ONU registration process. This process involves a series of message exchanges between ONU and OLT to ensure that the new ONU is correctly recognized, authenticated, and allocated the necessary communication resources.

When an ONU is registered, the following authentication modes are available:

· SN authentication—In this mode, an ONU only needs to provide its serial number (SN) to the OLT for registration.

· SN+password authentication—In this mode, the ONU needs to provide not only its SN but also its authentication password to the OLT for registration.

· Password authentication—In this mode, the ONU only needs to provide its password to the OLT for registration.

Figure 19 ONU registration process

As shown in Figure 19, a new ONU is registered as follows (all message exchanges occur at the GTC layer):

2. Upon powering on, the ONU initializes its software and hardware.

3. The OLT sends PLOAM messages to the ONU to notify the ONU of the physical layer transmission parameters.

4. (Required for SN/SN+password authentication.) The ONU announces its SN to the OLT.

5. (Required for SN+password/password authentication.) The OLT sends a password request to the ONU, asking the ONU to provide its password for authentication.

6. (Required for SN+password/password authentication.) The ONU responds to the OLT with the configured password.

7. (Required for SN+password/password authentication.) The OLT verifies the received password. If the password is wrong, the OLT might deny registration or take other actions as configured.

8. After the new ONU passes authentication, the OLT will allocate a unique ONU ID and several Alloc-IDs to the ONU.

9. The OLT performs ranging. For the specific process of ranging, see "Key technology of GPON: Ranging." This section will not repeat the details.

10. The OLT allocates upstream bandwidth and time slots to the ONU through the DBA mechanism. For more information about the DBA mechanism, see "Key GPON technology: DBA." This section will not repeat the details.

11. The OLT and ONU begin normal communication.

In addition, ONUs can also be added through autodiscovery or manually. The authentication procedure in the registration process varies by the addition method as follows:

· Autodiscovery—This method sets a policy to trust all new ONUs that meet the conditions. The OLT will automatically authenticate an ONU after receiving its SN and password. This method simplifies operations and is suitable for scenarios with large-scale ONU registration during GPON network deployment.

· Manual addition—In this method, you must pre-set specific SNs or SNs + passwords on the OLT. When an ONU performs registration, it can be registered only if the provided SN or SN + password matches the manual configuration. This method provides higher security and flexibility but increases configuration complexity.

Interface types and numbering conventions in a GPON system

As shown in Figure 20, a GPON system primarily provides the following interface types:

· OLT interface—Located on an OLT, each OLT interface can connect to a GPON network.

OLT interfaces use a three-tier numbering system: card slot number/subcard number/port number, for example, Olt1/0/1. (Distributed devices in standalone mode.)(Distributed devices in IRF mode.)

OLT interfaces use a three-tier numbering system: IRF member ID/subcard number/port number, for example, Olt1/0/1. (Centralized IRF devices.)

· ONU interface—A logical interface created on an OLT interface and used to connect to an ONU.

An ONU interface is numbered as follows: OLT interface number:ONU port number, for example, Onu1/ 0/1:1.

The settings configured in ONU interface view is applied to the ONU accessing the OLT. The settings configured in ONU interface view is applied to the ONU accessing the OLT.

You can create multiple subinterfaces on an ONU interface, with each subinterface corresponding to a T-CONT. Subinterfaces are used to differentiate various types of service data. An ONU subinterface is numbered as follows: ONU interface number.subinterface number, for example, Onu1/0/1:1.1.

· User Network Interface (UNI)—A port on an ONU. A UNI connects to a user.

After you enter the view of an ONU interface on an OLT, you can execute a command with a UNI number specified (for example, uni uni-number auto-negotiation) to remotely configure the UNI on the ONU.

Figure 20 Interface numbering conventions in a GPON system

ONU configuration deployment

In the actual configuration process of GPON, most ONU management parameters from the OLT are recorded in profiles. These parameters are bulk deployed through the following types of profiles:

· Line profile—Top-level profile for deploying configuration to ONUs. Most configuration deployed to ONUs must be first applied to a line profile. Then, you can apply the line profile to an ONU interface, and the OLT deploys configuration to the ONU based on the line profile applied to the ONU interface.

· DBA profile—Defines the bandwidth allocation policy and parameters for upstream traffic.

· Configuration profile—Defines the ONU UNI settings, GPON multicast settings, and some GPON QoS settings.

· Service profile—Defines VLAN-related service settings and some GPON QoS settings.

Configure these types of profiles in the following sequence:

1. Create a line profile and add subinterfaces in it.

2. Create a DBA profile and configure it.

3. Create a T-CONT in the line profile and associate it with a DBA profile.

4. Create a configuration profile and configure it.

5. Create a service profile and configure it.

6. Apply a T-CONT and a service profile to a line profile subinterface, and apply a configuration profile to a line profile.

7. Apply a line profile to an ONU interface. When the configuration for a subinterface exists, the ONU interface will automatically create a subinterface with the same number as the subinterface in the line profile. ONU subinterfaces are logical subinterfaces used to differentiate service configurations planned for different T-CONTs.

8. The OLT deploys configuration to the ONU connected to the ONU interface based on the line profile applied to that interface.

the relationship between various profiles is shown in Figure 21.

Figure 21 The relationship between various profiles when ONU configuration is deployed

Configuring GPON

Restrictions and guidelines: GPON configuration

All configuration tasks in this chapter are executed on the OLT. Configurations for an ONU will be automatically deployed to the ONU after the ONU is registered and comes online.

The GPON features are only supported on the default MDC. For more information about MDC, see MDC configuration in Virtual Technologies Configuration Guide.

GPON tasks at a glance

1. Configuring basic OLT settings

¡ Configuring the OLT operating mode

¡ Configuring the logical distances for ranging

2. Configuring ONU connections and authentication

¡ (Optional.) Configuring the ONU authentication mode on the OLT

¡ Creating an ONU interface

¡ Binding ONUs

¡ (Optional.) Configuring the ONU blacklist

3. Activating ONUs

4. Deploying configuration to ONUs

¡ Creating a DBA profile

¡ Creating a service profile

¡ Creating a configuration profile

¡ Configuring a line profile

¡ Applying a line profile

¡ (Optional.) Quickly configuring various profiles

¡ (Optional.) Directly deploying configuration to an ONU interface

5. (Optional.) Configuring the management VLAN of an ONU

6. (Optional.) Configuring extended GPON settings

¡ Configuring the DBA bandwidth allocation mode

¡ Configuring the AD-Campus server connection parameters for ONUs

Configuring basic OLT settings

Configuring the OLT operating mode

About this task

Perform this task to configure the OLT's split ratio, which determines the maximum number of ONUs that can be connected to each OLT interface or the maximum number of ONU interfaces that can be created on each OLT interface. The following operating modes are supported:

· 64-ONU mode—Each OLT interface supports creating a maximum of 64 ONU interfaces.

· 128-ONU mode—Each OLT interface supports creating a maximum of 128 ONU interfaces.

· 256-ONU mode—Each OLT interface supports creating a maximum of 256 ONU interfaces.

Restrictions and guidelines

After you change the OLT operating mode for a slot, you must reboot the slot or the whole device to make the OLT operating mode change take effect.

· If the slot is rebooted, all OLT interfaces in the slot are restored to the default settings, and the ONU interfaces created on the OLT interfaces are deleted.

· If the whole device is rebooted and the running configuration is saved, ONU interfaces numbered from 1 to 64 and OLT interfaces are not affected. Switching from a high split ratio mode to a low split ratio mode will delete ONU interfaces exceeding the upper limit for the low split ratio.

Procedure

1. Enter system view.

system-view

2. Enter FTTH view.

ftth

3. Configure the OLT operating mode for the specified slot.

Distributed devices in standalone mode: Centralized IRF devices:

olt-mode slot slot-number { 64-onu | 128-onu | 256-onu }

Distributed devices in IRF mode:

olt-mode chassis chassis-number slot slot-number { 64-onu | 128-onu | 256-onu }

By default, an OLT operates in 64-ONU mode.

Configuring the logical distances for ranging

About this task

During the ONU registration process, the OLT must perform ranging for ONUs. To quickly obtain the ranging results, you can pre-set the logical distances between OLT and ONU.

The maximum logical distance defines the greatest acceptable distance between the OLT and ONU. It also determines the longest time the OLT will wait to transmit a signal and receive a reply from the ONU. If the actual physical distance exceeds this distance, the OLT will consider the ONU unreachable and cannot establish a connection.

The minimum logical distance defines the shortest acceptable distance between the OLT and ONU. It also determines the shortest time the OLT will wait to transmit a signal and receive a reply from the ONU. If the actual physical distance is less than this distance, the OLT will consider the ONU too close, which might cause signal interference. As a result, the OLT cannot establish a connection.

The smaller the minimum logical distance, the faster the OLT can receive replies from the ONU. The larger the maximum logical distance, the farther the OLT can connect to an ONU. Adjusting these parameters enables fast, precise measurement of the distance between the OLT and ONU.

Restrictions and guidelines

Use this command to modify the logical distances for ranging only if you have a certain level of PON deployment knowledge. If you do not, use the default configuration to avoid longer ranging time due to incorrect parameter values.

Procedure

1. Enter system view.

system-view

2. Enter OLT interface view.

interface olt interface-number

3. Set the maximum and minimum logical distances between OLT and ONU during the OLT ranging process.

onu-distance { max distance | min distance } *

By default, the maximum logical distance between OLT and ONU is 20 kilometers, and the minimum logical distance is 0 kilometers.

Configuring ONU connections and authentication

Configuring the ONU authentication mode on the OLT

About this task

Perform this task to configure the ONU authentication mode on the OLT during registration. In the current software version, the following modes are supported:

· sn—Authenticates ONUs by SN.

· sn-password—Authenticates ONUs by SN and password.

· password—Authenticates using by password.

Restrictions and guidelines

When configured in OLT interface view, the ONU authentication mode only applies to that OLT interface. When configured in FTTH view, the ONU authentication mode applies to all OLT interfaces. An OLT interface preferentially uses the interface-specific ONU authentication mode. If no interface-specific ONU authentication mode is available, the OLT interface uses the ONU authentication mode configured in FTTH view.

You can configure multiple ONU authentication modes. However, the SN+password is mutually exclusive with any other modes.

Procedure

1. Enter system view.

system-view

2. Enter FTTH view or OLT interface view. Choose the options to configure as needed:

¡ Enter FTTH view.

ftth

¡ Enter OLT interface view.

interface olt interface-number

3. Configure the ONU authentication mode.

authentication-mode { sn | sn-password | password }*

By default, an OLT authenticates ONUs by SN.

Creating an ONU interface

About this task

Use ONU interfaces to remotely configure the ONUs connected to an OLT interface.

Restrictions and guidelines

When ONUs are bulk or automatically bound, this task is not required. The device can automatically create ONU interfaces based on the number of ONUs to be bound.

Procedure

1. Enter system view.

system-view

2. Enter OLT interface view.

interface olt interface-number

3. Create an ONU interface.

using onu onu-number-list

Binding ONUs

About this task

For an ONU to perform authentication and registration, first bind the ONU to an ONU interface. After the ONU completes registration, its ONU interface on the OLT will become up, indicating that the ONU is online.

Use the following methods to bind ONUs:

· Manually ONU binding—You can bind an ONU that meets the specified authentication conditions (SN/password) to the specified ONU interface on the OLT. This configuration method is flexible but requires individual configuration for each ONU interface. This method is suitable for initial binding for few ONUs or used as a supplementary binding method to the bulk binding method.

· Bulk ONU binding—The OLT automatically binds all the current unregistered ONUs that meet the authentication conditions to ONU interfaces, but will not bind any ONUs newly added after bulk binding.

Bulk ONU binding applies to a newly established GPON system that contains only legal ONUs. To prevent automatic registration of illegal ONUs, manually bind each new ONU separately.

· Automatic ONU binding—The OLT automatically binds all unregistered ONUs that meet the authentication conditions to ONU interfaces and also automatically binds any newly added ONUs.

Automatic ONU binding applies to a GPON system where ONUs attached to the OLT are completely trustworthy. To unbind a specific ONU, first use the undo onu bind auto command to disable automatic ONU binding. Then, manually unbind the ONU by using the undo bind onu-id command.

Restrictions and guidelines

When you manually bind an ONU, the authentication criterion used (SN/password/SN+password) is not restricted by the authentication mode configured by using the authentication-mode command on the OLT. For the other two binding modes, the authentication criterion must match the authentication mode on the OLT.

If you use the undo bind onu-id command to unbind the current interface from the ONU, the ONU will go offline.

You can bind only one ONU to an ONU interface.

Manually binding ONUs

1. Enter system view.

system-view

2. Enter ONU interface view.

interface onu interface-number

3. Bind the ONU interface to an ONU.

bind onu-id { sn serial-number | sn-password serial-number password | password password }

By default, an ONU interface is not bound to any ONU.

Bulk binding ONUs

1. Enter system view.

system-view

2. Enter FTTH view.

ftth

3. Configure bulk ONU binding.

Distributed devices in standalone mode: Centralized IRF devices:

onu bind batch [ slot slot-number ] [ bind-type { sn | sn-password | password } ]

Distributed devices in IRF mode:

onu bind batch [ chassis chassis-number slot slot-number ] [ bind-type { sn | sn-password | password } ]

By default, the device does not bulk bind ONUs.

Automatically binding ONUs

1. Enter system view.

system-view

2. Enter FTTH view.

ftth

3. Enable automatic ONU binding.

Distributed devices in standalone mode: Centralized IRF devices:

onu bind auto [ slot slot-number ] [ bind-type { mac | sn | sn-password | password }* ]

undo onu bind auto [ slot slot-number ] [ bind-type { mac | sn | sn-password | password }* ]

Distributed devices in IRF mode:

onu bind auto [ chassis chassis-number slot slot-number ] [ bind-type { mac | sn | sn-password | password }* ]

undo onu bind auto [ chassis chassis-number slot slot-number ] [ bind-type { mac | sn | sn-password | password }* ]

By default, automatic ONU binding is disabled.

Configuring the ONU blacklist

About this task

Perform this task to add an ONU specified by its SN, password, or both to the ONU blacklist. An ONU added to the ONU blacklist cannot register with the OLT.

After you configure the ONU blacklist, the OLT will identify whether an ONU is on the blacklist each time it registers.

Restrictions and guidelines

You can add up to 256 ONUs to the blacklist.

Procedure

1. Enter system view.

system-view

2. Enter FTTH view.

ftth

3. Add an ONU to the blacklist.

blacklist onu-id { sn serial-number | sn-password serial-number password | password password }

By default, no ONU is added to the blacklist.

Activating ONUs

About this task

For a registered ONU to operate correctly, activate the ONU.

Procedure

1. Enter system view.

system-view

2. Enter ONU interface view.

interface onu interface-number

3. Activate the ONU.

activate onu

By default, an ONU is activated after coming online.

Deploying configuration to ONUs

Creating a DBA profile

About this task

In a DBA profile, you can configure only the bandwidth allocation type for T-CONTs.

Restrictions and guidelines

If you execute the dba type1, dba type2, dba type3, dba type4, and dba type5 commands multiple times in the same DBA profile, the most recent configuration takes effect.

To delete a DBA profile that has been applied to a T-CONT, you must first remove it from the T-CONT.

A maximum of 512 DBA profiles are supported.

Procedure

1. Enter system view.

system-view

2. Create a DBA profile and enter its view, or enter the view of an existing DBA profile.

onu dba-profile profile-name

By default, the default DBA profile named dba_profile_default exists.

3. Execute one of the following commands in the DBA profile.

¡ dba type1

¡ dba type2

¡ dba type3

¡ dba type4

¡ dba type5

By default, the dba type4 ratio max 1000 command is predefined in the default DBA profile named dba_profile_default, and no configuration exist in newly added DBA profiles.

Creating a service profile

Restrictions and guidelines

To delete a service profile that has been applied to a line profile subinterface, you must first remove the service profile from the subinterface.

A maximum of 1024 service profiles are supported.

Procedure

1. Enter system view.

system-view

2. Create a service profile and enter its view, or enter the view of an existing service profile.

onu service-profile profile-name

By default, the default service profile named service_profile_default exists.

3. In the service profile, execute the following commands as needed.

¡ port access vlan (Layer 2—LAN Switching Command Reference)

¡ port hybrid pvid (Layer 2—LAN Switching Command Reference)

¡ port hybrid vlan (Layer 2—LAN Switching Command Reference)

¡ port link-type (Layer 2—LAN Switching Command Reference)

¡ port trunk permit vlan (Layer 2—LAN Switching Command Reference)

¡ port trunk pvid (Layer 2—LAN Switching Command Reference)

¡ vlan mapping (Layer 2—LAN Switching Command Reference)

By default, all the preceding commands are predefined with their default settings in the default service profile named service_profile_default, and no configuration exists in the newly added service profiles.

Creating a configuration profile

Restrictions and guidelines

To delete a configuration profile that has been applied to a line profile, you must first remove the configuration profile from the line profile.

A maximum of 1024 configuration profiles are supported.

Procedure

1. Enter system view.

system-view

2. Create a configuration profile and enter its view, or enter the view of an existing configuration profile.

onu config-profile profile-name

By default, the default configuration profile named config_profile_default exists.

3. In the configuration profile, execute the following commands as needed.

¡ onu multicast fast-leave enable (GPON Command Reference)

¡ onu port-isolate enable

¡ onu protocol transparent-multicast (GPON Command Reference)

¡ onu statistics enable

¡ uni auto-negotiation

¡ uni description

¡ uni duplex

¡ uni flow-control

¡ uni igmp-snooping fast-leave (GPON Command Reference)

¡ uni multicast vlan (GPON Command Reference)

¡ uni multicast-group-number (GPON Command Reference)

¡ uni multicast-strip-tag enable (GPON Command Reference)

¡ uni multicast-translate-tag (GPON Command Reference)

¡ uni port-isolate

¡ uni speed

¡ uni statistics enable

¡ uni vlan-mode

By default, all the preceding commands are predefined with their default settings in the default configuration profile named config_profile_default, and no configuration exists in the newly added service profiles.

Configuring a line profile

About this task

In a line profile, you can configure the following features for traffic transmission between OLT and ONU.

· Downstream traffic encryption—With this feature enabled, the downstream traffic from OLT to ONU is encrypted by the OLT to ensure user data security.

· ONU FEC—Forward error correction (FEC) is an error control method for data transmission. FEC adds redundant data to the transmitted data, enabling the receiver to detect and correct a certain number of errors. With FEC enabled, an ONU detects and corrects errors in data received from the OLT based on the redundant information, ensuring the quality and stability of high speed data transmission.

· ONU traffic mapping mode—This feature determines the traffic mapping modes available for a line profile subinterface. On a line profile subinterface, the traffic mapping mode determines the criteria (such as UNI number, packet priority, and VLAN tag) that upstream traffic must meet to pass through the subinterface and be received by the OLT. If upstream traffic does not match the mapping rules of any subinterface, the OLT cannot receive it.

Restrictions and guidelines

To delete a line profile that has been applied to an ONU interface, you must first remove the line profile from the ONU interface.

To delete a T-CONT that has been applied to a line profile subinterface, you must first remove the T-CONT from the subinterface.

If you execute the apply onu-config-profile, apply onu-service-profile, or apply tcont command multiple times for a line profile or line profile subinterface, the most recent configuration takes effect.

A maximum of 1024 line profiles are supported.

Procedure

1. Enter system view.

system-view

2. Create a line profile and enter its view, or enter the view of an existing line profile.

onu line-profile profile-name

By default, the default line profile named line_profile_default exists.

3. Apply a configuration profile to the line profile.

apply onu-config-profile profile-name

By default, the default configuration profile named config_profile_default is applied to a line profile.

4. (Optional.) Enable downstream traffic encryption for ONUs.

encryption enable

By default, downstream traffic encryption is enabled for ONUs.

5. (Optional.) Enable FEC for ONUs.

forward-error-correction enable

By default, FEC is enabled for ONUs.

6. Configure the traffic mapping mode for ONUs.

mapping-mode { priority | uni | vlan }

By default, an ONU maps traffic by UNI number.

7. Create a T-CONT and apply a DBA profile to it.

tcont tcont-name [ onu-dba-profile profile-name ]

By default, the default T-CONT named tcont_default exists in an ONU line profile, and the default DBA profile named dba_profile_default is applied to the T-CONT.

8. Create a line profile subinterface and enter its view, or enter the view of an existing line profile subinterface.

subinterface subnumber

By default, subinterface 1 exists.

9. Configure the traffic mapping rules for the ONU subinterface.

onu-mapping { [ uni [ all | { uni-number [ to uni-number ] }&<1-32> ] ] [vlan [ untag | { vlan-id [ to vlan-id ] }&<1-12> ] ] [ priority [ all | { priority [ to priority ] }&<1-8> ] ] }

By default, traffic from all UNIs is mapped to a subinterface.

10. Apply a service profile to the line profile subinterface.

apply onu-service-profile profile-name

By default, the default service profile named service_profile_default is applied to a line profile subinterface.

11. Apply a T-CONT to the line profile subinterface.

apply tcont tcont-name

By default, the default T-CONT named tcont_default is applied to a line profile subinterface.

Applying a line profile

About this task

The method of applying a line profile varies by ONU binding mode.

· Manual ONU binding—In this mode, use the bind onu-line-profile command to apply a line profile to an ONU interface. Then, when you manually bind an ONU to the ONU interface by using the bind onu-id command, the OLT automatically deploys the configuration in the applied line profile to the ONU.

· Bulk ONU binding & automatic ONU binding—In this mode, use the onu bind type command to bulk apply a line profile to multiple ONUs based on ONU type. The OLT will deploy the configuration in the specified line profile to ONUs of the type specified by using the onu bind type command, and deploy the configuration in the default line profile to the other ONUs.

Manually applying a line profile

1. Enter system view.

system-view

2. Enter ONU interface view.

interface onu interface-number

3. Apply a line profile to the ONU interface.

bind onu-line-profile profile-name

By default, no line profile is applied to an ONU interface.

Bulk applying a line profile

1. Enter system view.

system-view

2. Enter FTTH view.

ftth

3. Bulk apply a line profile based on ONU type.

onu bind type onu-type [ onu-line-profile profile-name ]

By default, the default line profile named line_profile_default is bulk applied.

Quickly configuring various profiles

About this task

GPON supports multiple profile types with complex configuration parameters. To simplify profile creation and application for users, GPON introduces the following enhancements.

· Displaying configuration differences between the specified profiles—Displays the configuration differences between different profiles of the same type on the OLT to help users decide which profiles to choose.

· Profile copying—Allows you to select a source profile and copy its configuration to a newly created destination profile on the OLT for quick creation of various profiles.

Procedure

1. Enter system view.

system-view

2. Display the configuration differences between the specified profiles.

gpon compare-profile { onu-config-profile | onu-dba-profile | onu-line-profile | onu-service-profile } source-profile-name profile-name destination-profile-name profile-name

3. Quickly add GPON profiles and copy settings from a source profile to these profiles.

gpon copy-profile { onu-config-profile | onu-dba-profile | onu-line-profile | onu-service-profile } source-profile-name profile-name { destination-profile-name profile-name } &<1-15>

Directly deploying configuration to an ONU interface

About this task

You can execute function commands directly in ONU interface view to deploy configuration to the ONU attached to the ONU interface, achieving the same effect as applying a profile. The differences between the two methods are as follows:

· Applying a profile allows for finer control over configuration deployment and a profile can be reapplied.

· Configuration in ONU interface view affects only the corresponding ONU. To deploy the same configuration to multiple ONU interfaces, you must repeatedly execute the configuration commands.

Procedure

1. Enter system view.

system-view

2. Enter ONU interface view.

interface onu interface-number

3. Configure the VLAN operation mode for a UNI: Choose one option as needed:

¡ Transparent mode:

uni uni-number vlan-mode transparent

¡ Tag mode:

uni uni-number vlan-mode tag pvid pvid [ priority priority ]

¡ Translation mode:

uni uni-number vlan-mode translation pvid pvid [ priority priority ] { original-vlan-id to translated-vlan-id } &<1-15>

¡ QinQ mode:

uni uni-number vlan-mode qinq pvid pvid [ priority priority ]

¡ Trunk mode:

uni uni-number vlan-mode trunk pvid pvid [ priority priority ] trunk-vlan-list

¡ N:1 aggregation mode:

uni uni-number vlan-mode aggregation pvid pvid [ priority priority ] { vlan-id1 to vlan-id2 aggregated-vlan aggregated-vlan }&<1-15>

By default, the VLAN operation mode for a UNI is transparent.

Forwarding multicast and broadcast packets from an ONU in multiple VLANs

About this task

Use this feature to flexibly forward packets across VLANs at Layer 2. When an OLT with this feature configured receives a packet with the specified destination MAC address/IP address and port number from the specified VLAN from an ONU, it forwards the packet directly to the specified target VLANs.

Procedure

1. Enter system view.

system-view

2. Forward multicast and broadcast packets from an ONU in multiple VLANs.

onu flow flow-id vlan vlan-id { destination-ip ipv4-address { mask-length | mask } | destination-mac mac-address } [ udp-port port-number ] forward-vlan vlan-list

By default, multicast and broadcast packets from an ONU are not configured to be forwarded in multiple VLANs.

If you execute this command multiple times with the same flow-id argument, the most recent configuration takes effect.

Configuring the management VLAN of an ONU

About this task

To manage an ONU through Telnet, you must assign an IP address to the management VLAN interface of the ONU. This task allows you to specify the management VLAN of an ONU.

The management VLAN interface of an ONU can obtain an IP address by using the following methods:

· Manual IP address configuration.

· DHCP (with the ONU as a DHCP client).

A new IP address overwrites the old IP address if both methods are used.

Restrictions and guidelines

For the IP address configured for the management VLAN interface of an ONU to take effect, first bind the ONU to a line profile.

When you configure an IP address for the management VLAN interface of an ONU interface, the device does not prompt whether the IP address conflicts with that of any other interface. If multiple interfaces are configured with the same IP address, only the first configuration takes effect.

Procedure

1. Enter system view.

system-view

2. Enter ONU interface view.

interface onu interface-number

3. Configure the management VLAN of the ONU.

management-vlan vlan-id

By default, the management VLAN of an ONU is VLAN 1.

If the management VLAN is changed, the IP address of the original management VLAN interface is deleted.

4. Bring up the management VLAN interface.

undo shutdown management-vlan-interface

By default, a management VLAN interface is down.

5. Assign an IP address to the management VLAN interface.

¡ IPv4 network:

ip address { dhcp-alloc | ip-address { mask-length | mask } gateway gateway }

By default, no IPv4 address is assigned to the management VLAN interface.

¡ IPv6 network:

ipv6 address { dhcp-alloc | { ipv6-address prefix-length | ipv6-address/prefix-length } gateway gateway }

By default, no IPv6 address is assigned to the management VLAN interface.

Configuring extended GPON settings

Configuring the DBA bandwidth allocation mode

About this task

In the DBA mechanism, the amount of bandwidth allocated to an ONU is influenced by the bandwidth allocation mode. The DBA bandwidth allocation mode involves the concept of a DBA calculation period, which is the interval at which the OLT recalculates and allocates bandwidth to each ONU. This period is the foundation for executing the DBA algorithm, and it determines the flexibility and response speed of bandwidth allocation. Based on the different DBA calculation periods, the following DBA bandwidth allocation modes are available:

· Minimum delay mode—This mode aims to minimize the data transmission delay. In this mode, the OLT preferentially allocates bandwidth resources to delay-sensitive services, such as VoIP or real-time video conferencing.

· Maximum bandwidth mode—This mode aims to provide an ONU with as much bandwidth as possible. In this mode, an ONU can transmit more data.

· Manual mode—The DBA calculation periods for the preceding two modes are dynamically allocated by the OLT. For greater control, you can manually set a fixed DBA calculation period to achieve more precise bandwidth allocation. A shorter DBA calculation period enables the OLT to respond faster to network changes but increases its processing load. Conversely, a longer period reduces the OLT’s workload but might delay bandwidth allocation adjustments during dynamic network conditions, which will degrade QoS. In manual mode, set an appropriate DBA calculation period based on the actual network conditions and service requirements.

Procedure

1. Enter system view.

system-view

2. Enter FTTH view.

ftth

3. Configure the DBA bandwidth allocation mode.

Distributed devices in standalone mode: Centralized IRF devices:

dba bandwidth-assignment-mode slot slot-number { min-delay | max-bandwidth | manual period }

undo dba bandwidth-assignment-mode slot slot-number

Distributed devices in IRF mode:

dba bandwidth-assignment-mode chassis chassis-number slot slot-number { min-delay | max-bandwidth | manual period }

undo dba bandwidth-assignment-mode chassis chassis-number slot slot-number

By default, the DBA bandwidth allocation mode is minimum delay.

Configuring the AD-Campus server connection parameters for ONUs

About this task

Use this feature specifically for an Application-Driven Campus (AD-Campus) network. This feature remotely configures the AD-Campus server connection parameters on the OLT, facilitating the connection between ONU and server.

Procedure

1. Enter system view.

system-view

2. Enter FTTH view.

ftth

3. Configure the AD-Campus server connection parameters for ONUs.

management server source-ip ip-address [ port port-number ] [ keepalive interval ] password { cipher | simple } string

By default, the AD-Campus server connection parameters are not configured for ONUs.

Display and maintenance commands for GPON

Execute display commands in any view.

Table 1 Display and maintenance commands for OLTs

Task	Command
Display IP address assignment information for an ONU that acts as a DHCPv4 client.	display dhcp-client
Display information about the OLT interfaces and ONU interfaces.	display interface [ interface-type [ interface-number ] ] [ brief [ description \| down ] ]
Display ONU information.	In standalone mode:‌ display onu [ silent [ sn ] \| status [ keep-time keep-time ] ] { interface interface-type interface-number \| slot slot-number } In IRF mode: display onu [ silent [ sn ] \| status [ keep-time keep-time ] ] { interface interface-type interface-number \| chassis chassis-number slot slot-number }
Display information about a UNI of an ONU.	display uni uni-number
Display detailed ONU information.	display vendor-specific information
Display information about the legal ONU with the specified SN.	display onu sn serial-number
Display the OLT authentication mode.	display pon authentication-mode [ interface interface-type interface-number ]
Display GPON DBA diagnostic information.	In standalone mode:‌ display pon diagnostic dba slot slot-number In IRF mode: display pon diagnostic dba chassis chassis-number slot slot-number
Display the profile state information of an ONU subinterface.	display pon diagnostic config interface interface-type interface-number
Display GPON configuration deployment failure information.	In standalone mode:‌ display pon diagnostic config-error { slot slot-number \| interface interface-type interface-number } In IRF mode: display pon diagnostic config-error { chassis chassis-number slot slot-number \| interface interface-type interface-number }
Display the link state of an ONU subinterface.	display pon diagnostic status interface interface-type interface-number
Display the registration and deregistration records of an ONU.	display pon onu-event interface interface-type interface-number
Display loop information of UNIs of ONUs.	In standalone mode: display pon onu-loop-status { interface interface-type interface-number \| slot slot-number } In IRF mode: display pon onu-loop-status { interface interface-type interface-number \| chassis chassis-number slot slot-number }
Display ONU update information.	In standalone mode:‌ display pon onu-update { interface interface-type interface-number \| slot slot-number } In IRF mode: display pon onu-update { interface interface-type interface-number \| chassis chassis-number slot slot-number }
Display optical parameters for an OLT interface.	display pon optics-parameters interface interface-type interface-number
Display version information of an OLT or ONU.	display pon version interface interface-type interface-number
Display information about an ONU configuration profile.	display onu-config-profile [ profile-name profile-name ]
Display information about an ONU DBA profile.	display onu-dba-profile [ profile-name profile-name ]
Display information about an ONU line profile.	display onu-line-profile [ profile-name profile-name ]
Display information about an ONU subinterface service profile.	display onu-service-profile [ profile-name profile-name ]

20-GPON

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Procedure

About this task

Restrictions and guidelines

Procedure

Restrictions and guidelines

Procedure

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Procedure

About this task

Procedure

About this task

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Procedure

About this task

Procedure

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us