Huawei H35-211_V2.5 Dumps

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 IPv4 multicast, the destination MAC is derived by mapping the lower 23 bits of the multicast IP address into the OUI 01-00-5E. The 4th MAC byte is the lower 7 bits of the IP’s second octet (so it ranges 00–7F), and the 5th and 6th MAC bytes are the third and fourth IP octets directly:

Multicast OUI: 01-00-5E

IP: 227.120.1.32

2nd octet = 120 (0x78). Its lower 7 bits are still 0x78 (since the MSB is 0).

3rd octet = 1 (0x01)

4th octet = 32 (0x20)

Therefore the MAC is 01-00-5E-78-01-20 → option C.

(This mapping aligns with standard IPv4 multicast-to-Ethernet rules described in Huawei’s multicast overview sections in HCIP-Access materials and Huawei OLT product guides.)

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.

Per RFC 3261 (SIP), “The CSeq header field of the response MUST equal the CSeq field of the request.” CSeq carries a sequence number and the method, thereby associating a response with the specific request it answers. While Call-ID ties together all messages within the same dialog, it does not identify the specific request/response pairing; CSeq does. Therefore, CSeq is the correct header for correlating a response to the exact request.

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.

SSH provides secure remote login and secure file transfer (SCP/SFTP) with encryption, integrity, and authentication. Clients validate the server/host and then perform user authentication (password, public key, etc.), often described as two layers of authentication. SSH runs over TCP (port 22) at the application layer, not at the network layer—therefore D is the incorrect statement.

For enterprise/private multicast, Huawei adopts the administratively scoped range 239.0.0.0/8 for internal multicast groups. 232/8 is typically used for SSM in public domains, 224/8 contains link-local and well-known groups, and 225/8 is not defined as the preferred private scope.

WRED (weighted early drop) uses lower and upper thresholds to determine a probabilistic drop curve; the drop probability scales with the average queue length between these thresholds—therefore D is correct.

A is incorrect because early dropping inevitably affects services to some extent; it’s designed to trade small, controlled loss for stability.

B is incorrect; devices use early drop before buffers fill, and when full, tail drop still applies—both mechanisms coexist.

C is imprecise in Huawei’s terminology; early drop begins when the average queue depth crosses the lower threshold and increases up to the upper threshold, not simply “before a preset threshold” without that two-threshold relationship.

Huawei devices support independent mapping/remarking for inner and outer VLAN priorities (802.1p CoS) when QinQ is used. Operators can define distinct mapping tables or remark rules per tag. Option A is incorrect (priorities can be derived or remarked, not “must be” tag-in-packet), option C is incorrect because mapping profiles are configurable, and option D confuses VLAN IDs with priorities; inner/outer CoS can be mapped independently for inbound/outbound directions.

On Huawei access devices/OLTs, VoIP/H.248 setup typically includes:

In voip view, configure media IP with gateway:

ip address media – e.g., ip address media 10.10.10.10 10.10.10.1.

Configure signaling IP without a gateway parameter:

ip address signaling – e.g., ip address signaling 10.10.10.10.

Add/enter the H.248 interface and apply properties with if-h248 attribute ….

It’s common to reset/enable the MG interface after attribute changes; many guides show reset coldstart (or reset) issued under the H.248 interface to activate the interface.

Authoritative configuration examples show media takes an IP and gateway, but signaling takes only the IP. Therefore, option D (attempting to configure signaling with a gateway parameter) is incorrect. Options A and C match documented syntax and workflow. Option B reflects the documented practice of issuing a reset (often written as reset coldstart) under the H.248 interface to apply/enable, as shown in Huawei-focused configuration guides.

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.

Huawei’s E2E pre-connection ODN (pre-connectorized ODN) adopts factory-pre-terminated cables, closures and splitter modules. Features highlighted in HCIP-Access V2.5 include: splicing-free quick installation (raising build efficiency and reducing skill/tool dependence), compact pre-connected splitter boxes, distributed splitting that shortens drop lengths and reduces ducts/cables, and easy O&M because modules are plug-and-play with no field splicing.

In 10G-EPON (IEEE 802.3av), the wavelength plan uses 1577 nm downstream and 1270 nm upstream. The 1270 nm upstream is used in both asymmetric and symmetric 10G-EPON profiles.

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.

XG-PON encapsulates user data into XGEM frames. The XGEM Port-ID field is 12 bits, allowing identification of logical connections (GEM ports) per ONU. This mirrors the 12-bit Port-ID used in GPON GEM.

In IEEE 802.1AX/802.3ad LACP operation, timeout detection relies on a multiplier of three consecutive LACP intervals. In short-timeout mode, the default period is ~1 s; if 3 intervals pass without receiving LACPDUs, the peer is considered expired and the member is removed (treated as Down for aggregation). Huawei implements this standard behavior for port-member validity in an Eth-Trunk.

(Reference: HCIP-Access V2.5 – Link Aggregation/LACP timers and member aging; IEEE LACP short-timeout 3× interval rule.)

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.

Huawei access security recommends limiting MAC learn counts per port/VLAN, and using anti-MAC-spoofing bindings: either automatic (dynamic) bindings generated by the system or manual static MAC bindings to the service/port. Simply replacing a terminal is not a network-side mitigation method and is not listed as a protection measure.

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.)

In AQM, high-priority queues are given more tolerant (larger) thresholds so they are less likely to be dropped early. Setting a smaller early-drop threshold for high priority would increase their loss probability, which contradicts QoS objectives—thus A is incorrect. Descriptions in B, C, and D align with Huawei’s treatment of congestion avoidance: RED/WRED proactively drops to stabilize queues and can reduce delay variation; tail drop at full buffer can lead to global TCP synchronization.

In campus/access networks, IGMP (Internet Group Management Protocol) operates between hosts and the first-hop multicast router/querier on the local subnet. It controls host group membership (Join/Leave/Query/Report), allowing the device to learn which receivers are interested in specific multicast groups and to populate/maintain the local multicast forwarding state.

Live TV uses multicast, while VOD uses unicast. If VOD works but live TV is a black screen, typical causes are multicast service-path/config mismatches or priority starvation for multicast control/traffic:

C: If the ONU uses different VLANs for VOD and live but the OLT has only one video service flow, multicast frames will not match the correct service-port, causing black screen.

D: A low-priority traffic profile for multicast join/report or stream on the OLT uplink may drop IGMP joins or multicast packets under load, resulting in black screen while unicast VOD still passes.

Queue scheduling choices such as PQ or DWRR (A/B) are generic congestion schemes; by themselves they are not direct root causes of a live-only black screen unless mis-classified, whereas C and D are recognized multicast-specific fault points.

Huawei OLTs support ONT replacement without deleting the original service profile by using ONT replace/auto-find mechanisms. The OLT can bind the new ONT (new SN) to the existing ONT configuration template (service-port, VLAN, QoS, multicast profile, etc.), achieving a smooth replacement without manually removing and re-creating the ONT and services. The statement that you must remove the ONT and re-register from scratch is therefore wrong.

Type C dual-homing provides device-level protection with two OLTs; when one OLT/uplink fails, services switch to the peer OLT. In single-homing, ONUs are associated with only one OLT; therefore an OLT failure interrupts services (C). Single-homing has simpler networking and management than dual-homing (D). It does not offer switchover to another OLT (so B is incorrect), and the “important-service” positioning in A is typically applied to dual-homing scenarios that require the highest availability.

IGMP Snooping is a Layer-2 function that listens to IGMP control packets between hosts and the multicast querier. Upon receiving a host’s Membership Report (Join) for group G, the switch learns that the ingress port is a member port for G and adds that port to the group’s forwarding entry, so multicast traffic for G is forwarded only to those learned member ports (saving bandwidth and avoiding flooding). Huawei’s official documentation describes IGMP Snooping exactly in this way.

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.

A persistently high CPU on the OLT main control board is typically driven by excessive control-plane load or abnormal traffic patterns. Common causes include:

Illegal login attempts generating authentication and logging overhead (A)

Layer-2 loops leading to storms and protocol churn (B)

DoS/scan/attack traffic stressing control/management processing (C)

Rogue/misbehaving ONUs causing frequent state changes, registration flaps, or abnormal report traffic (D)

All listed factors are recognized contributors to elevated CPU on access OLTs.

In Huawei’s QoS theory (aligned with IETF), the recognized service models are Best Effort, Integrated Services (IntServ), and Differentiated Services (DiffServ). FIFO is a queueing discipline (scheduling method) rather than a service model. FIFO simply forwards packets in arrival order without classification or guarantees, and while it can be used within Best Effort, it is not itself a service model.

An Ethernet port protection group is a 1:1 protection mechanism that improves reliability through active/standby switching. It does not aggregate bandwidth—the standby port does not forward traffic unless a switchover occurs. If increased bandwidth is required, technologies such as LACP are used instead.

Huawei GPON implements hierarchical traffic control. CAR (Committed Access Rate) can be applied at multiple layers: GEM-port level (GEM-CAR), per-flow (Flow-CAR), and T-CONT level (T-CONT-CAR) for upstream bandwidth policing/shaping and guaranteeing QoS. GEM mapping is a classification/association mechanism (service → GEM/T-CONT) rather than a traffic-control action, so it is not a CAR measure.

Huawei GPON service provisioning supports mapping upstream/downstream service flows to GEM Ports using multiple classifiers, including MAC address, physical port (PORT), VLAN ID, and 802.1p (priority). These classifiers are configured in line/service templates (and pushed via U2000) to ensure precise flow-to-GEM binding.

With ONT Zero-Touch Provisioning (ZTP) enabled on eSight, newly discovered ONTs can be automatically identified and provisioned by pushing service templates from eSight. This removes the need for advance (preset) service configuration on the OLT during incremental onboarding; the OLT simply accepts the provisioning delivered by eSight.

For IPv4 multicast, the MAC mapping uses 01-00-5E followed by the low-order 23 bits of the multicast IP address. Because an IPv4 multicast address has 28 variable bits (224/4), 5 bits are not mapped to the MAC. Therefore, 2⁵ = 32 distinct multicast IP addresses can map to the same multicast MAC address.

A (True): Huawei multicast configuration defaults commonly allow a user to watch up to 8 programs simultaneously unless overridden (e.g., max-program-num default 8 in multicast/VLAN views and controllable multicast profile).

B (True): On Huawei access devices, IGMP Reports from users are processed by the line card (board) logic/CPU as part of IGMP Snooping/controllable multicast handling to build forwarding entries. (See Huawei IGMP Snooping/Proxy architecture descriptions.)

C (Incorrect): IGMP Snooping is a Layer 2 function, but IGMP Proxy is a Layer 3 function (runs on a gateway to originate Queries and proxy membership upstream). Grouping them together as “Layer 2 global parameters” is incorrect. Huawei documentation distinguishes IGMP Snooping (L2) from IGMP Proxy (L3).

D (True in practice): When automatic matching is not used, multicast program groups/channels must be configured so that user joins map to provisioned program entries (consistent with Huawei controllable multicast/BTV configuration workflows).

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.