All H35-211_V2.5 Test Inside Huawei Questions

In GPON Type C dual-attribution protection, the ONU has dual PON connections to two OLT PON ports (or two OLTs). When the protection group is configured to track the OLT’s uplink Ethernet port, a Down state on that uplink is an OLT-side trigger. The OLT initiates the protection action (forces the working/standby role swap via PON protection signaling).

A — Correct behavior: After the OLT triggers protection, the ONU’s working PON interface becomes standby, and the protect interface becomes working.

B — Correct behavior: The OLT monitors and updates the ONU uplink status as part of the protection group state machine.

C — Correct behavior: After inversion, services egress the ONU via the protect PON port toward the OLT, i.e., traffic follows the configured protect path.

D — Incorrect (answer): In this scenario the trigger is the OLT’s uplink Ethernet status, not an ONU-detected failure. Therefore the ONU does not detect the fault nor initiate the switchover; the OLT does.

(Reference: HCIP-Access V2.5 – GPON protection mechanisms; Huawei OLT protection group behavior, Type C dual-homing with uplink-tracking.)

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.

On Huawei VRP, Advanced IPv4 ACLs (which can match source IP, destination IP, and L4 port numbers) use the 3000–3999 numbering range.

2000–2999 = Basic IPv4 ACL (matches source IP only).

3000–3999 = Advanced IPv4 ACL (matches source/destination IP, protocol, ports).

4000–4999 = Layer 2 (MAC) ACL.

5000–5999 = User-defined/other ranges, not the standard advanced IPv4 range.

Therefore, to match IPs and ports, select 3000–3999.

In Huawei IPTV access, when the OLT’s IGMP audit/authorization debug shows a negative program-rights/authorization result, it indicates that the user lacks permission for the requested multicast program group. This is distinct from port multicast bandwidth alarms (insufficient multicast bandwidth), IGMP snooping state malfunctions, or subscriber traffic shaping/bandwidth checks. Authorization failures map directly to “no permission to watch the program.”