H35-211_V2.5 Sample Questions Answers

10G-EPON is designed for coexistence with EPON on the same ODN by using separate downstream wavelengths and dual-rate upstream mechanisms. Operators can realize a smooth upgrade at the OLT (local end) by inserting WDM mux/demux modules (or using dual-rate PON ports) while continuing to use the existing ODN fiber plant and splitters. This is a standard migration path emphasized in HCIP-Access materials for PON evolution.

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.

Standard OTDR operation allows you to configure multiple acquisition parameters:

Measurement range (distance range): sets the maximum span to be traced; best practice is typically 1.5–2× the fiber length under test.

Wavelength: select test wavelength(s), e.g., 1310/1550 nm for SM fiber, to observe different loss characteristics.

Mode: vendors provide real-time/average (or similar) acquisition modes to stabilize traces.

Pulse width: controls dynamic range vs. event resolution; longer pulses see farther but increase dead zones, while shorter pulses improve resolution at the cost of range.

These are documented in foundational OTDR references and application notes.

Huawei eSight supports multiple L3/L2 discovery mechanisms:

Network-segment (subnet) scanning;

ARP-based discovery in broadcast domains;

Routing-table discovery to traverse multi-segment networks.

Administrators can configure an exclusion list of subnets/IPs; during discovery, eSight skips any addresses listed there, preventing unwanted polling/Onboarding.

Huawei anti-DoS on access boards performs periodic detection. Ports with consecutive detections of abnormal traffic are placed into a blacklist/quarantine state. The system then applies a random back-off interval before re-detecting; if no further anomalies are found, the port can be automatically removed from the blacklist.

In eSight’s ONT Zero-Touch workflow, multi-service profiles define service parameters delivered to ONTs—primarily service VLANs such as Internet/Data VLAN, Voice VLAN, and IPTV/Multicast VLAN with related QoS. Hardware attributes like ONU type or Ethernet port count are part of the device/ONT profile, not the multi-service profile. A generic “Default VLAN” parameter is not used here; instead, explicit service VLANs are specified (for example, data VLAN and voice VLAN).

Huawei Anti-MAC-Spoofing binds the source MAC to the service flow/port to prevent address forgery. It is functionally exclusive with certain per-VLAN MAC check features (e.g., WMAC, SC, PPPoe-SMAC) to avoid conflicting validation logic. For IPoE users with fixed IP, operators typically configure static bindings/entries so that address and access policies remain consistent.

Option D is wrong: disabling Anti-MAC-Spoofing and removing fixed entries can affect service behavior; if forwarding is interrupted, that does impact user service—so the statement is self-contradictory and incorrect.

Type C GPON protection uses two different OLTs (dual-home). With uplink status linkage configured, a failure of the active OLT itself or its uplink interface triggers a protection switchover to the standby OLT to maintain service continuity for ONUs homed through the protected ODN.

GPON (per ITU-T G.984.x and Huawei OLT specifications) provides a downstream line rate of ~2.488 Gbit/s, commonly denoted as 2.5 Gbit/s, and an upstream rate of ~1.244 Gbit/s (1.25 Gbit/s). Therefore, the downstream effective bandwidth option that matches GPON is 2.5 Gbit/s.

In campus/access QoS planning on Huawei devices, queue scheduling commonly supports RR, WRR/DRR, and (optionally) strict-priority. WRR (Weighted Round Robin) assigns larger weights to high-priority queues so they receive more transmission opportunities and bandwidth than lower-priority queues while still serving all queues. Therefore, when ensuring better treatment for high-priority services under round-robin–type scheduling, WRR is the recommended choice.

In IP address discovery mode, eSight does not require L2 same-subnet adjacency; it only requires IP reachability/routing, proper SNMP credentials/alignment, and the operator’s Resource Access permission to poll and add devices. The “same network segment” prerequisite applies to ARP broadcast discovery mode, not to IP address discovery.

OLT-level (device-level) protection is achieved by dual-homing ONUs to two independent OLT interfaces so that services can switch to another OLT when one fails. In Huawei protection taxonomy, the dual-homing scheme (as contrasted with single-homing) provides device-side redundancy for the OLT. By comparison, Ethernet port protection groups and LACP protect uplink links and bandwidth at Layer 2, not the OLT device itself; single-homing does not protect against OLT failure.

For intercommunication across VLANs—especially for voice between ONUs—ARP Proxy is configured on the OLT so the OLT responds to ARP on behalf of endpoints and bridges traffic across VLAN boundaries without exposing the full L3 gateway to each segment.

A: “Saving IP addresses” is not the defining difference; ARP Proxy’s function is ARP mediation to enable L2/L3 reachability.

B: Both features target intercommunication, not isolation.

D: A VLAN service-profile is planned and applied from the OLT side to ONUs; it is not “configured on the ONU” directly for this purpose.

On Huawei OLTs (e.g., MA5600T/MA5680T), deploying IPTV/multicast commonly uses a program list (channel list) to map program numbers to multicast group addresses—this is configured with igmp program. When programs are statically configured under the multicast VLAN, the program definitions themselves are mandatory; without them, set-top boxes cannot select (zap to) channels by program number/address mapping and the OLT cannot correctly forward the requested multicast streams.

Drag & Drop Answer (NGN layers → devices):

Network control layer → Softswitch

Service management layer → OSS system

Edge access layer → MA5800

Core switching layer → Core router

Why:

Softswitch handles call/session control ⇒ control layer.

OSS provides O&M/service management ⇒ service management layer.

MA5800 is an OLT/access device ⇒ edge access layer.

Core router provides backbone forwarding ⇒ core switching layer.

In Huawei GPON/EPON protection planning, Type B protection uses two PON ports on the same OLT with dual feeder (trunk) fibers into the same ODN. It protects the OLT PON port and the feeder/trunk optical path while branch/distribution fibers to ONUs are not protected. This exactly matches the requirement “protect trunk; do not protect branches.”

Huawei’s alarm reference for PON ports lists the common possible causes of LOS (the OLT does not receive the expected optical signal) as:

The port laser is shut down;

The backbone optical fiber connected to the port is faulty;

All the ONTs/ONUs connected to the port are powered off or faulty;

(and potentially) port hardware faults.

These map directly to options D, B, and C. A rogue ONU generates specific “rogue ONU” alarms and is characterized by continuous/abnormal upstream emission; it is not a typical root cause of an LOS condition, which indicates absence of expected optical signal.

When the number of access users approaches or exceeds the single-layer VLAN space and services must be distinguished per user, Huawei recommends hierarchical VLAN (QinQ) on the uplink: map a customer VLAN (C-VLAN) at the access side and add a service/provider VLAN (S-VLAN) toward the aggregation/core, i.e., C → S+C. This expands scalability beyond the ~4K single-VLAN limit while enabling precise user/service binding for large FTTH deployments (e.g., ~5K users under one OLT).

NCE supports on-demand (manual) and policy-driven (automatic) performance data dumps. In both modes, data filtered by configured criteria is exported to files stored locally on the NCE server for subsequent analysis or archiving.

For OLT uplink (NNI) protection groups (timedelay/weight, etc.), Huawei requires that each physical port belongs to one protection group only to avoid conflicting switchover control. A member port cannot be part of multiple protection groups simultaneously.

In Huawei QoS processing, traffic classification on access devices/OLTs can match Layer-3 and Layer-2 priority indicators and MPLS labels. Common match fields include IP DSCP (or IP precedence in the ToS byte), MPLS EXP, and IEEE 802.1p CoS carried in VLAN tags. These fields are used to place packets into scheduling/queuing behaviors and policing profiles.

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.

At Layer 2, Huawei switches use HGMP/IGMP-Snooping mechanisms to listen to IGMP reports and constrain multicast forwarding to interested ports, preventing broadcast-like flooding. PIM-SM/DM and IGMP-proxy are Layer-3 multicast control/relay functions, not L2 forwarding control.

In HCIP-Access teaching materials, 10G-EPON improves optical budget and FEC efficiency compared with 1G EPON, enabling very high split ratios. While commercial deployments commonly use 1:64 or 1:128 depending on optics class and reach, the maximum (laboratory) split ratio often cited for the technology is 1:256 under favorable conditions.

For ONT zero-touch on eSight/iMaster NCE-Campus, the prerequisite is that the OLT is onboarded and provisioned (communication parameters, northbound credentials, templates) so that discovered ONTs can inherit policies and be auto-activated. During incremental OLT configuration, eSight does push/update the OLT’s configuration (templates, profiles, authentication rules). Saying “do not provision OLT” is therefore false.

In IPTV/multicast access scenarios, channel zapping delay is heavily influenced by how fast the network stops forwarding the previous channel’s stream after a user switches. Huawei documents the IGMP Fast Leave/Prompt Leave feature, which enables the access device to immediately prune the old multicast group on receipt of a Leave (without waiting for group-specific queries and timers), thereby reducing the channel change delay and improving perceived switching speed. Option A explicitly disables a helpful pre-join optimization, which would worsen experience; Option C (preview) concerns showing brief previews and is not a primary mechanism for shortening zapping time; Option D is unrelated to performance. Thus, enabling Quick/Fast Leave is the correct action to shorten switching time.

Huawei GPON design recommends at most two splitting stages and a total split ratio within the optical power budget (commonly up to 1:64 for standard budgets).

A: 1:2 × 1:16 = 1:32 (valid).

C: 1:8 × 1:8 = 1:64 (valid under standard budgets).

D: 1:2 × 1:8 = 1:16 (valid).

B: 1:16 × 1:16 = 1:256, which exceeds typical GPON budgets and recommended engineering practice. Hence B is the incorrect networking.

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.

Huawei VLAN planning considers overall VLAN scale, user categories and volume, service types (HSI/IPTV/VoIP) and their isolation, uplink/aggregation mode (e.g., QinQ, VXLAN interwork), and device/topology constraints (e.g., OLT slot/board distribution). All listed factors affect VLAN count, tagging scheme, and scalability.

PITP (Port Identification Transparent Transmission) is used on access networks to carry a user’s physical access-location to the upper AAA/BRAS. It has two working forms: P-mode (PPPoE+)—injecting location identifiers into PPPoE discovery—and V-mode (Vendor-tag)—carrying vendor/location tags transparently upstream. The purpose is to let the upper server associate user credentials with access location and, by policy, restrict roaming. Options A, B, D, and E correctly describe these behaviors/terms. Option C is inaccurate as written: PITP itself does not “bind the authentication” or inherently “avoid theft/roaming”; it only delivers location info. Preventing credential theft/roaming is achieved by AAA/BRAS policy that uses the PITP-carried location, not by PITP alone.

In an H.248 (Megaco) control model, the MGC is the controller that issues provisioning/connection-control commands such as Add, Modify, Subtract, AuditValue, AuditCapabilities to the MG. The MG (Media Gateway) can initiate only specific messages toward the MGC to announce state changes or report detected events—namely ServiceChange (to indicate restart, failure, availability changes, etc.) and Notify (to report observed events collected per event descriptor). Therefore, among the listed options, the commands that the MG itself can send are ServiceChange and Notify.