Huawei H12-891_V1.0 Exam With Confidence Using Practice Dumps

When Spanning Tree Protocol (STP) is not enabled on a network, loops can occur in Layer 2 Ethernet networks, leading to various network issues. STP is designed to prevent loops by blocking redundant paths, and its absence can cause broadcast storms, MAC address table instability, and resource exhaustion. Let’s analyze each option in the context of Huawei HCIE Datacom documentation and network behavior:

A. A loop alarm is generated on the LAN switch.

This option is incorrect. Huawei switches, as per HCIE Datacom standards, do not automatically generate a specific "loop alarm" unless configured with loop detection features (e.g., Huawei’s Loop Detection Protocol or similar mechanisms). Without STP or loop detection enabled, the switch may not explicitly generate an alarm for a loop; instead, it will exhibit symptoms like broadcast storms or flapping MAC entries. Therefore, this is not a direct symptom of an STP-less loop. Reference: Huawei HCIE Datacom V3.0 Training Materials, Section 4.2 – Spanning Tree Protocol and Loop Prevention.

B. CPU usage is too high.

This option is correct. When a loop occurs without STP, broadcast packets (and sometimes multicast or unknown unicast packets) circulate endlessly in the network. This leads to excessive processing by switches as they handle these packets, resulting in high CPU usage. Huawei switches, as described in HCIE Datacom documentation, can experience CPU overload due to continuous packet forwarding and processing in a looped environment. Reference: Huawei HCIE Datacom V3.0, Chapter 5 – Switch Performance and Loop Management.

C. MAC entries flap.

This option is correct. In a loop without STP, switches continuously receive frames from multiple ports, causing MAC address tables to update repeatedly as the same MAC address appears on different ports. This "flapping" of MAC entries destabilizes the network and can lead to incorrect frame forwarding. Huawei HCIE Datacom emphasizes MAC address table stability as a critical aspect affected by loops, as outlined in Section 4.3 – Ethernet Switching and Loop Mitigation. Reference: Huawei HCIE Datacom V3.0, Section 4.3.

D. Host receives a large number of broadcast packets.

This option is correct. A loop without STP causes broadcast packets to circulate indefinitely, creating a broadcast storm. Hosts connected to the network will receive an overwhelming number of these packets, potentially leading to performance degradation or even network timeouts. This is a well-documented symptom in Huawei HCIE Datacom training, specifically in discussions about loop prevention mechanisms. Reference: Huawei HCIE Datacom V3.0, Chapter 4 – Layer 2 Loop Prevention.

Thus, the correct symptoms of a loop occurring due to the absence of STP include high CPU usage, flapping MAC entries, and hosts receiving a large number of broadcast packets. Option A is incorrect as it requires specific loop detection configuration, which is not implied in the question.

To analyze this question, let's break down the key concepts and the given LSDB (Link State Database) information from the figure:

Understanding the LSDB Output:

The output shows the OSPF LSDB on R2 with Router ID 10.1.123.2.

Area 0.0.0.0 (Area 0) is displayed along with several Link State Advertisements (LSAs) including Router LSAs, Network LSAs, and Summary LSAs.

Area 0.0.0.1 (Area 1) also displays Router LSAs and a Type 7 LSA (NSSA LSA) with Link-State ID 0.0.0.0.

An External LSA (Type 5) with Link-State ID 0.0.0.0 and AdvRouter 10.1.123.2 is also present.

Analysis of Each Option:

Option A: Area 1 is an NSSA.

Correct.

The presence of a Type 7 LSA (NSSA LSA) in the database indicates that Area 1 is configured as an NSSA (Not-So-Stubby Area).

NSSA allows the injection of Type 7 LSAs for external routes while blocking Type 5 LSAs from entering the area.

Option B: R2 translates Type 7 default route into Type 5 default route.

Correct.

In an NSSA, if an ABR (like R2) has the NSSA ASBR capability, it will convert Type 7 LSAs to Type 5 LSAs before injecting them into the backbone area (Area 0).

In the LSDB, we see both a Type 7 LSA (NSSA) and a corresponding Type 5 External LSA, confirming that R2 performs this translation.

Option C: R2 advertises the default route in the OSPF process.

Incorrect.

There is no indication that R2 itself is originating the default route.

The Type 7 LSA in Area 1 and the Type 5 LSA in Area 0 only indicate translation from another source, not R2 advertising it directly.

Option D: Area 1 does not have Type 3 LSAs. The possible cause is that R2 filters Type 3 LSAs in the outbound direction of Area 1.

Incorrect.

In an NSSA area, Type 3 LSAs (Inter-Area Prefix LSAs) are typically not generated for external routes.

The absence of Type 3 LSAs in Area 1 is due to the nature of NSSA itself rather than any filtering configured on R2.