BlackFriday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

HP Exam HPE7-A01 Topic 4 Question 20 Discussion

Actual exam question for HP's HPE7-A01 exam
Question #: 20
Topic #: 4
[All HPE7-A01 Questions]

A customer just upgraded aggregation layer switches and noticed traffic dropping for 120 seconds after the aggregation layer came online again. What is the best way to avoid having this traffic dropped given the topology below?

Show Suggested Answer Hide Answer
Suggested Answer: C

The reason is that the linkup delay timer is a feature that delays bringing downstream VSX links up, following a VSX device reboot or an ISL flap. The linkup delay timer has two phases: initial synchronization phase and link-up delay phase.

The initial synchronization phase is the download phase where the rebooted node learns all the LACP+MAC+ARP+STP database entries from its VSX peer through ISLP. The initial synchronization timer, which is not configurable, is the required time to download the database information from the peer.

The link-up delay phase is the duration for installing the downloaded entries to the ASIC, establishing router adjacencies with core nodes and learning upstream routes. The link-up delay timer default value is 180 seconds. Depending on the network size, ARP/routing tables size, you might be required to set the timer to a higher value (maximum 600 seconds).

When both VSX devices reboot, the link-up delay timer is not used.

Therefore, by configuring the linkup delay timer to include LAGs 101 and 102, which are part of the same VSX device as LAG 201, you can ensure that both devices have enough time to synchronize their databases and form routing adjacencies before bringing down their downstream links.


Contribute your Thoughts:

Ayesha
4 months ago
Wait, did they really ask us to configure the timer to 240 seconds? That's like asking for a nap break in the middle of a network outage!
upvoted 0 times
Cherilyn
3 months ago
Yeah, that way we can allow time for routing adjacencies to form and learn upstream routes.
upvoted 0 times
...
Mattie
4 months ago
I think we should configure the linkup delay timer to exclude LAGS 101 and 102.
upvoted 0 times
...
...
Queen
4 months ago
I think configuring the linkup delay timer to 120 seconds is the right choice, it allows the right amount of time for the initial phase to sync.
upvoted 0 times
...
Alverta
4 months ago
I agree with Kiera, excluding LAGs 101 and 102 will allow time for routing adjacencies to form and learn upstream routes.
upvoted 0 times
...
Kiera
4 months ago
I disagree, I believe configuring the linkup delay timer to exclude LAGs 101 and 102 is the better option.
upvoted 0 times
...
Winfred
4 months ago
Haha, imagine if they tried to include the LAGs - that would just be a recipe for more delays! C is definitely not the way to go.
upvoted 0 times
Delila
4 months ago
Agreed, C is definitely not the solution here.
upvoted 0 times
...
Shanice
4 months ago
Yeah, including the LAGs would just make things worse.
upvoted 0 times
...
...
Tanja
5 months ago
I think the best way to avoid traffic dropping is to configure the linkup delay timer to 240 seconds.
upvoted 0 times
...
Narcisa
5 months ago
I'm not sure about doubling the delay timer. Wouldn't that just make the issue worse? 120 seconds seems like a good middle ground.
upvoted 0 times
...
Marvel
5 months ago
Option B seems like the way to go. Excluding the LAGs that are already up will give the routing adjacencies time to form without delaying the whole process.
upvoted 0 times
Matt
4 months ago
I agree, excluding the LAGs that are already up will give enough time for routing adjacencies to form.
upvoted 0 times
...
Lonna
4 months ago
I think option B is the best choice here.
upvoted 0 times
...
...

Save Cancel