Huawei OLTs support Eth-Trunk (link aggregation) with two standard modes: Static aggregation and Dynamic aggregation (LACP). These provide bandwidth expansion and redundancy on NNI uplinks. “Automatic” is not a defined mode; and “manual” is not used as a separate mode name in OLT Eth-Trunk configuration.

Right. The SIP Max-Forwards header limits how many SIP elements a request can traverse. Each proxy decrements the value by one; when it reaches zero, the message must not be forwarded, preventing infinite loops and yielding responses like 483 (Too Many Hops). RFC 3261 (Sections 8.1.1.6, 16.6, 20.22) defines this behavior; later work further discusses loop mitigation

According to IEEE 802.3av wavelength planning adopted by Huawei 10G-EPON, downstream uses 1577 nm and 10G upstream uses 1270 nm. In asymmetric coexistence, 1G-EPON upstream uses 1310 nm, but for 10G-EPON upstream specifically the wavelength is 1270 nm. Therefore the correct upstream wavelength for 10G-EPON is 1270 nm.

XG-PON (10G GPON) adopts XGEM framing. Compared with GPON’s 12-bit GEM Port-ID, XGEM expands the Port-ID field to 16 bits, increasing the number of logical data flows that can be identified per ONU/OLT and improving service granularity. Hence the correct length is 16 bits.

IPv4 multicast (historically “Class D”) occupies the address block 224.0.0.0 through 239.255.255.255. Any upper bound of 238.255.255.255 is incorrect because it excludes the full 239/8 administratively scoped range. This is standardized in the IANA IPv4 Multicast Address Space registry and reflected in foundational multicast specifications.

Huawei multicast guidance stresses IGMP version compatibility: devices running an earlier version must interoperate only with hosts using the same or earlier version, otherwise v3 messages may not be processed. In Huawei’s multicast feature guidance for access devices (OLT side vs. user side), the behavior documented is that when the device is operating in IGMPv2, IGMPv3 Report messages from terminals are not processed—interoperation is restored only after the terminal/device side is downgraded to v2 (often driven by periodic queries that induce hosts to respond in v2). This maps operationally to dropping unsolicited IGMPv3 Reports when the OLT is fixed to v2. Huawei also recommends ensuring the device runs an IGMP version the same as or later than member hosts to avoid such loss. Therefore, with OLT fixed at v2, an incoming v3 Join is discarded.

On Huawei OLTs, the service-port is a binding between the user-side access (ONT/port) and a VLAN/GEM channel, and it supports traffic policing (CAR/rate-limit) by referencing a traffic/queue profile. Traffic shaping (buffer-based smoothing, token bucket with queue drain) is provided on ports/queues or GEM/LLID directions, not on the service-port object itself. Therefore, shaping is not performed via the service-port; applying a traffic profile there enforces policing, not shaping.

Type B provides redundancy with two OLT PON ports on the same OLT and two feeder (backbone) fibers to the ODN. Therefore it protects the PON ports and the backbone/feeder path. It does not protect the OLT itself (still a single OLT) and does not protect the ONU branch fibers.

For Huawei uplink protection (STH-NNI port protection) with workmode timedelay, the mandatory steps are:

Create/define the protection group with the protect-target and workmode timedelay;

Add member ports with roles (work/protect);

Enable the protection group.

Interface-level timers like offline-tx-off-time under the physical interface are not required for standard timedelay protection operation and are therefore optional.

GPON traffic policing/shaping is commonly applied at multiple layers:

T-CONT rate control (T-CONT-CAR): controls upstream bandwidth per T-CONT.

GEM-port rate control (GEM-CAR): limits per GEM port.

Service flow rate control (Flow-CAR): enforces per-service policies.

GEM mapping is a forwarding association (service→GEM) and not itself a rate-control mechanism.