HPE7-A08 Exam Dumps : HPE Aruba Networking Certified Professional - Switching

The term " Active " in BGP is one of the most misunderstood states. It sounds positive, but it actually indicates that the switch is " actively " trying to establish a TCP connection and failing.

eBGP Default Behavior: By default, External BGP (eBGP) expects neighbors to be directly connected. Because of this, eBGP packets are sent with a Time to Live (TTL) of 1 .

The Loopback Problem: In the exhibit, the switches are peering using their Loopback 0 addresses (update-source loopback 0). Even if the switches are physically connected, the Loopback interface is considered a " hop " away from the physical interface.

TTL Expiry: When Agg-1 sends a BGP packet to Agg-2 ' s loopback, the TTL of 1 expires before the packet can reach the logical loopback interface. This causes the TCP connection to fail, keeping the session in the Active state.

The Solution (eBGP Multihop): To fix this, you must configure ebgp-multihop (usually with a value of 2 or more). This increases the TTL, allowing the BGP packets to reach the loopback address.

Side Note on the Exhibit: If you look closely at Agg-1 ' s configuration, there is a typo: the neighbor is defined as 10.3.0.3 but the address-family activation is for 10.3.0.2. While this would also cause a failure, the core architectural concept being tested here regarding " Active " state and loopbacks is the TTL/Multihop requirement.

The exhibit shows a configuration for a standard Stub Area (area 1 stub). To meet the customer requirement of having only a default route, we must understand how OSPF area types filter Link State Advertisements (LSAs).

Stub Area (Current Config): Blocks Type 5 (External) LSAs. The Area Border Router (ABR) injects a Type 3 LSA default route. However, Type 3 LSAs (Inter-Area routes from other parts of the OSPF network) are still allowed in. This explains why the user still sees other OSPF routes in the table.

Totally Stubby Area (The Solution): This area type is a Cisco/Aruba enhancement to the OSPF standard. It blocks both Type 5 (External) and Type 3 (Inter-Area) LSAs. The ABR replaces all of these with a single Type 3 default route . This is the most efficient configuration for a small branch switch with limited memory and a single exit point.

AOS-CX Configuration: To convert the current " Stub " to a " Totally Stubby " area, you would add the no-summary keyword on the ABR:

Bash

router ospf 1

area 1 stub no-summary

Why other options are incorrect:

Option A and D: NSSA (Not-So-Stubby Areas) are used when you need to redistribute external routes from the branch into the rest of the OSPF network. The prompt doesn ' t mention a local external source.

Option B: This is what is currently configured and is explicitly described as not meeting the requirement.

LACP (Link Aggregation Control Protocol) modes can be active or passive. When two switches are both configured in passive mode, no LACP packets are initiated, causing the link aggregation to fail or go into a block state.

Changing one side from passive to active causes that switch to initiate LACP negotiation, resolving the block state.

Changing to static mode disables LACP negotiation, which is not recommended unless both sides are static.

Changing timeout does not solve LACP block issues caused by mode mismatches.

Therefore, changing one switch’s LACP mode from passive to active is necessary to resolve the block.