Troubleshooting OLT Uplink LACP: Configuration, Compatibility & Error Resolving

Overview & Thematic Scope

This FAQ addresses the most critical technical challenges network engineers face when configuring LACP (Link Aggregation Control Protocol) on OLT uplink ports. Focusing on turnkey deployment and troubleshooting, we cover compatibility matrices, common error states, timeout parameters, and load-balancing hash algorithms to ensure a stable, high-throughput PON aggregation layer.

Frequently Asked Questions

Q1: What are the mandatory configuration prerequisites before enabling LACP on an OLT uplink interface?

Ensure both the OLT and the upstream switch are set to the same LACP mode (Active or Passive) and that the system priority is correctly defined. You must also verify that the port channel is not already bound to another protocol (e.g., STP) and that all physical interfaces in the bundle share identical speed, duplex, and MTU settings (typically 1518 bytes or jumbo 9216).

Q2: Why does the LACP bundle fail to establish a ‘Distributed’ or ‘Collecting/Distributing’ state on my OLT?

An LACP bundle fails to enter the correct state primarily due to mismatched timeout timers (Short vs. Long) or incompatible port keys between the OLT and its peer. Additionally, verify that the peer device’s LACP protocol is not in ‘Passive’ mode while your OLT is also ‘Passive’; at least one side must be ‘Active’. Check the ‘lacp system-id’ on both sides; they must be globally unique.

Q3: How does the LACP load-balancing hash algorithm impact upstream traffic distribution and how do I configure it?

OLT LACP utilizes a hash algorithm on packet headers (typically Layer 2 MAC or Layer 3 IP) to assign flows to physical links within the trunk. Improper hash configuration leads to an unbalanced trunk where one member link saturates. For optimal distribution, configure ‘src-dst-ip’ or ‘src-dst-mac’ hashing on the OLT to ensure that diverse subscriber traffic is evenly distributed across your uplink fibers.

Q4: What is the procedure for adding a new physical fiber link to an existing LACP trunk without causing a service outage?

To perform a hitless expansion, first pre-configure the new physical port with the same VLAN and MTU settings as the existing bundle. Then, administratively enable the port (no shutdown) while ensuring the ‘lacp port-priority’ is set higher to prevent it from becoming the active aggregator prematurely. The LACP protocol will automatically negotiate the addition and begin load-sharing traffic after a few seconds of handshaking.

Q5: How do I troubleshoot ‘LACP timeout’ errors indicated by excessive ‘Event: LACP Rx Timeout’ messages in the OLT log?

An LACP Rx Timeout indicates the OLT has stopped receiving LACPDUs from its upstream neighbor. To resolve this, first set the LACP timeout to ‘Long’ (90 seconds) on both ends to make the link less sensitive to micro-bursts. Next, check the physical layer (SFP power/temperature) for errors, as intermittent fiber degradation often corrupts control PDUs before data traffic is affected.

Q6: What are the compatibility implications when connecting an OLT LACP trunk to a third-party (non-proprietary) core switch?

LACP is IEEE 802.3ad standard, so it is largely interoperable. However, critical discrepancies often arise in the default system priority values (32768) or the rate at which LACPDUs are exchanged. To ensure compatibility, manually set the same ‘lacp system-priority’ on the OLT and the third-party switch, and utilize the ‘Long’ timeout to accommodate varying hardware response latencies.

Q7: After a reboot, why is my OLT uplink LACP bundle selecting the wrong physical port as the ‘Aggregator’?

The OLT selects the Aggregator (active port) based on the lowest ‘lacp port-priority’ and system ID. To control this behavior predictably, explicitly assign a lower priority (e.g., 1) to the desired primary uplink port. This ensures that upon reboot or link flapping, the OLT consistently selects the designated primary fiber as the forwarding aggregator.

Q8: What is the proper sequence for isolating LACP mis-configuration from physical layer fiber issues during an outage?

First, check if the OLT’s physical uplink ports show ‘up/up’. If so, issue the ‘show lacp internal’ command; if the port state shows ‘DETACHED’ or ‘EXPIRED’, the issue is Layer 2 LACP negotiation. If the physical links are down, verify light levels and fiber connections. Always logically isolate the issue by disabling LACP on one end (forcing the port to ‘static trunk’) to confirm physical integrity.