MENU
You have been asked to troubleshoot failed connectivity between a local subnet in the HQ Office and a remote subnet in the Branch Office. PC1 is unable to ping PC2.
Use the provided topology and show command output to identify the reason for the failure:
Suggested Answer: D
Get Premium HPE6-A85 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
Using the provided topology and show command output, it can be determined that L3-SW-2 in the Branch Office does not have a route to reach the subnet where PC1 resides (192.168.1.0/24 in the HQ Office). L3-SW-1 in the HQ Office has a route to the Branch Office subnet (172.16.1.0/24), but without the reciprocal route on L3-SW-2, traffic from the Branch Office will not be able to reach the HQ Office subnet, hence PC1 cannot ping PC2.
17 comments · newest first
LY
Lynsey
10 months ago
HQ's switch missing a static route could also be the problem.
JE
Jesus
10 months ago
Totally agree, that's a common issue!
CH
Cherelle
11 months ago
Wait, how can there be no route to the Branch Office? That seems odd.
AS
Asuncion
11 months ago
Nah, I think the default route issue is a red herring here.
GA
Garry
11 months ago
Looks like there's no Layer 3 SVI on the Branch Office switch.
KR
Kris
11 months ago
I think option D makes sense too; if L3-SW-2 doesn’t have a route back to HQ, that could definitely block the ping.
JE
Jenise
12 months ago
I feel like option C is less likely since it mentions the internet, but I guess it could still affect local subnet communication somehow?
MI
Micaela
12 months ago
I’m not entirely sure, but I think option B about the route on L3-SW-1 could also be a possibility since routing issues often come up in practice questions.
AS
Ashleigh
12 months ago
I remember we discussed how missing SVIs can cause connectivity issues, so option A might be a strong candidate.
FI
Filiberto
1 year ago
This seems like a classic routing problem. I'll focus on checking the routing configuration on both the HQ Office and Branch Office switches to see if there are any missing or incorrect routes that could be causing the connectivity failure.
ME
Merlyn
1 year ago
Okay, let's see here. Based on the information provided, it seems like the issue could be either a missing Layer 3 SVI on the Branch Office switch or a missing route on the HQ Office switch. I'll need to analyze the details closely to determine the exact problem.
CO
Cordell
1 year ago
Hmm, I'm a bit unsure about this one. There are a lot of details to consider with the different switches and subnets. I'll need to carefully review the topology and command outputs to identify the root cause.
MI
Mila
1 year ago
This looks like a pretty straightforward connectivity issue. I'll start by checking the Layer 3 configuration on the switches to see if the subnets are properly configured and routed.
HE
Hector
1 year ago
Seriously, who designs a network with this many switches and no redundancy? I mean, come on, they're just asking for trouble. Whoever came up with this topology needs to go back to networking school.
EN
Enola
1 year ago
I think the issue might be with the Layer 3 SVI configuration on L3-SW-2 in the Branch Office.
HA
Hayley
1 year ago
Ah, this one's tricky. The connectivity issue seems to be on the Branch Office side, but which part is the real problem? I'm leaning towards D, but I'll have to double-check those command outputs to be sure.
AB
Abraham
1 year ago
User 1: I think the problem might be on the Branch Office side.