Overview

Multicast IPTV delivery on a ZTE OLT platform depends on precise alignment between the ONU service profile, the OLT multicast VLAN (MVLAN) configuration, and the upstream IGMP snooping parameters. When an ONU fails to pass multicast traffic while unicast browsing remains functional, the issue almost always traces to one of four root causes: a missing igmp span-vlan enable command, an untagged SVLAN on the uplink, an incomplete MVLAN receive-port binding, or a mismatched IGMP version between the ONU and OLT. This FAQ addresses the most frequent technical questions network architects and field engineers raise when diagnosing and resolving multicast IPTV failures on ZTE OLT platforms, from forwarding capacity specifications to exact CLI remediation steps.

Frequently Asked Questions

Q1: What is the maximum multicast forwarding throughput and backplane capacity of the ZTE OLT for IPTV services?

The ZTE ZXA10 C600 platform supports a backplane switching capacity of 14 Tbit/s and a system switching capacity of 7.2 Tbit/s, with the main control switching capacity reaching 3.68 Tbit/s. This line-rate capability enables hardware-based multicast replication across all line cards, ensuring that 4K/8K IPTV streams maintain consistent bandwidth without bottlenecks under high-density subscriber loads.

Q2: Why does my ONU receive unicast traffic but fail to pass multicast IPTV streams on the ZTE OLT?

The most common cause is that the multicast VLAN (MVLAN) is not properly enabled on the OLT, or the ONU user port is not bound as a multicast receive-port. On ZTE OLT platforms, you must globally enable IGMP snooping, create the MVLAN, define the source-port on the uplink, and bind the ONU UNI as a receive-port. If any of these steps is missing, the ONU will forward unicast traffic normally while silently dropping IGMP Join messages, resulting in a black screen for IPTV live channels.

Q3: What is the exact CLI configuration sequence to enable multicast IPTV on a ZTE OLT?

The standard configuration sequence on a ZTE ZXA10 OLT is as follows: first run igmp enable globally, then configure the MVLAN with igmp mvlan <vlan-id>, set the working mode to proxy or snooping, define the source-port on the uplink interface, and add the ONU interface as a receive-port. For example: igmp mvlan 200 work-mode proxy followed by igmp mvlan 200 source-port gei_1/21/1 and igmp mvlan 200 receive-port gpon-onu_1/5/1:1 vport 1. Always verify with show igmp mvlan 200 to confirm the bindings are active.

Q4: Why is the igmp span-vlan enable command critical for multicast IPTV when each PON port uses a different SVLAN?

When each PON port is assigned a unique outer SVLAN, the OLT must be able to extract IGMP messages from traffic arriving on different SVLANs and map them to a single MVLAN. Without the igmp span-vlan enable command, the OLT treats each SVLAN independently and fails to forward multicast streams across VLAN boundaries. A documented ZTE C600 troubleshooting case found that affected users all shared the same SVLAN that had not been extracted for cross-VLAN multicast processing; adding the span-vlan configuration for that specific SVLAN immediately restored multicast stream delivery.

Q5: What are the optical module specifications required for multicast IPTV on ZTE OLT uplinks?

The ZTE OLT requires SFP+ modules operating at 10 Gbps with DDM (Digital Diagnostic Monitoring) support for multicast IPTV uplinks. For 100G backbone integration, QSFP28 modules compliant with IEEE 802.3bm are mandatory. Optical power degradation below the DDM thresholds can cause intermittent packet loss that specifically affects multicast streams because multicast replication amplifies the impact of any single corrupted packet across multiple subscriber ports. Always verify that the received optical power falls within the module's specified sensitivity range before escalating software-level configuration issues.

Q6: How do I troubleshoot an ONU that switches from multicast to unicast during IPTV playback?

When an ONU falls back to unicast, the symptom typically indicates that the IGMP Join message is not reaching the OLT correctly. Check three items in sequence: verify that the MVLAN is properly tagged on the uplink port, confirm that the ONU service profile includes the multicast service entry (service igmp type iptv gemport 2 vlan 200), and ensure the STB is sending IGMP v2 or v3 messages that match the OLT's accepted version mode. If the OLT is configured for IGMP v3 but the STB sends v2 and the OLT is set to drop v2 packets, the Join will be rejected and the stream will fail.

Q7: What is the difference between IGMP Snooping and IGMP Proxy modes on a ZTE OLT for IPTV?

IGMP Snooping mode makes the OLT listen to IGMP messages between the STB and the upstream router, forwarding multicast streams based on learned group membership without actively participating in the protocol. IGMP Proxy mode makes the OLT terminate IGMP signaling from subscribers and generate its own upstream queries, which reduces upstream multicast state and is preferred in high-density IPTV deployments. For large-scale carrier IPTV, ZTE recommends Proxy mode with IGMPv3 support to enable source-specific multicast and reduce unnecessary flooding.

Q8: What power supply failover behavior should I expect during a multicast IPTV broadcast peak?

The ZTE OLT switches to the redundant power supply within 10 milliseconds of detecting an active PSU failure, which is fast enough to prevent interruption of multicast video streams. To verify failover readiness, monitor DC voltage with show power status and ensure both AC/DC modules are connected to separate grid sources. If failover fails during peak IPTV load, check the PSU alarm thresholds via show alarm current and confirm that the power management firmware supports load-sharing mode under high-demand video traffic.