Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

HPE6-A85 Exam - Topic 7 Question 51 Discussion

After having configured the edge switch uplink as requested your colleague says that they have failed to ping the core You ask your colleague to verify the connection is plugged in and the switch is powered on They confirm that both are correct You attempt to ping the core switch and confirm that the ping is failing.Knowing the nature of this deployment, what commands might you use to troubleshoot this issued
C) Ping 10.1.1.1 - ping the core to attempt to verify connectivity show lacp agg - to verify which link aggregations are currently configured using which physical ports show lacp int - to verify the LACP status and whether any links are blocking in your topology show lldp neighors - to verify whether you are able to see the Core as an L2 neighbor to verify if the correct links are plugged in to the correct ports show run interface 1/1/51.1/1/52-to ensure the physical interfaces are no-shut and members of the lag show run interface lag 1 - to ensure the correct vlan trunking configuration is applied to the logical interface show run int vlan 20 - to ensure you have the L3 SVI no shut and configured in the correct subnet
A) Ping 10.11 1 - ping the core to attempt to verify connectivity Show trunk - to verify if the LAG interface was correctly added to the switch Show spanning tree - to check for spanning-tree blocked states Show port-access clients interface all - to view any port-access blocking states or failed authentication attempts on all interfaces Show run interface vlan20 - to double check the layer 3 svi configuration is correct for l_3 connectivity Show lldp neighors - to verify whether you are able to see the Core as an L2 neighbor to verify if the correct links are plugged in to the correct ports
B) diagnostic diag cable-diag 1/1/51 diag cable-diag 1/1/52 - to view diagnostic information for the physical link to get a status on any interruptions to Layer 1 connectivity, show ip route - to verify that the default gateway is present in the routing table show ip ospf - to check whether there is a layer 3 routing protocol enabled show ip dns - to view whether there is a valid dns source
D) Show run - to view the running configuration of the switch Show run | begin 20 'vlan 20' - to ensure VLAN 20 was correctly added to the database show run | begin 20 'interface vlan 20' - to view the L3 SVI configuration Show run interface 1/1/51.1/1/52 - to ensure the physical interfaces are no shut and were added as members of LAG 1 Show run int lag 1 - to verify LACP mode active was configured to eliminate LACP blocking states

HPE6-A85 Exam - Topic 7 Question 51 Discussion

Actual exam question for HP's HPE6-A85 exam
Question #: 51
Topic #: 7
[All HPE6-A85 Questions]

After having configured the edge switch uplink as requested your colleague says that they have failed to ping the core You ask your colleague to verify the connection is plugged in and the switch is powered on They confirm that both are correct You attempt to ping the core switch and confirm that the ping is failing.

Knowing the nature of this deployment, what commands might you use to troubleshoot this issued

Show Suggested Answer Hide Answer
Suggested Answer: C

These commands might help troubleshoot this issue as they check various aspects of the connectivity between the edge switch and the core switch, such as Layer 3 reachability, Layer 2 adjacency, LACP configuration and status, VLAN trunking configuration, and interface status. Reference: https://www.arubanetworks.com/techdocs/AOS-CX_10_04/CLI/GUID-8F0E7E8B-0F4B-4A3C-AE7F-0F1B5A7F9C5D.html


by Gerri at Jan 05, 2026, 05:16 AM

Limited Time Offer

25%

Off

Get Premium HPE6-A85 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Honey
1 month ago
D is my pick. Verifying VLAN and interface configurations is key to troubleshooting.
upvoted 0 times
...
Annelle
1 month ago
C looks good too. It includes LACP checks which are important for our setup.
upvoted 0 times
...
Beth
2 months ago
I prefer B. Checking the physical link first seems crucial.
upvoted 0 times
...
Taryn
2 months ago
I think option A is solid. It covers all bases for connectivity checks.
upvoted 0 times
...
Kandis
2 months ago
Surprised no one mentioned checking the physical connections first!
upvoted 0 times
...
Ozell
2 months ago
I think you should also run a cable diagnostic just to be safe.
upvoted 0 times
...
Solange
2 months ago
Wait, why would you check DNS? That seems off.
upvoted 0 times
...
Mitsue
3 months ago
Definitely agree, show spanning tree is a must too!
upvoted 0 times
...
Edelmira
3 months ago
I’d start with pinging the core and checking the trunk.
upvoted 0 times
...
Lenita
3 months ago
Show lldp neighbors is a great way to confirm the correct connections. Gotta love those Layer 2 visibility tools!
upvoted 0 times
...
Stevie
4 months ago
Looks like a good list of troubleshooting steps. I'd probably start with the physical layer and work my way up the OSI stack.
upvoted 0 times
...
Tomas
4 months ago
Haha, I bet the core switch is just unplugged and the guy is too embarrassed to admit it. Always start with the basics!
upvoted 0 times
...
Sabrina
4 months ago
Definitely need to verify the LACP status and LAG configuration. Sounds like a potential issue with the uplink ports.
upvoted 0 times
...
Teri
4 months ago
The ping issue could be due to a misconfigured VLAN or SVI. I'd start with checking the L3 configuration on the SVI.
upvoted 0 times
...
Annamae
4 months ago
I think we should definitely verify the VLAN configuration with "show run interface vlan 20," but I also wonder if we need to check the LACP status right after that.
upvoted 0 times
...
Matilda
4 months ago
I feel like checking the LLDP neighbors is crucial here to confirm the physical connections, but I'm a bit uncertain about the order of commands we should use.
upvoted 0 times
...
Fidelia
5 months ago
I remember practicing with the "show spanning tree" command in a similar scenario, but I can't recall if it was really necessary for this issue.
upvoted 0 times
...
Richelle
5 months ago
I think we should start with the basic ping command to check connectivity, but I'm not sure if we should also look at the LAG configuration right away.
upvoted 0 times
...
Micah
5 months ago
Alright, let's see here. I think the key is to start with the basics and work my way up. I'll begin by pinging the core switch to verify connectivity. If that doesn't work, I'll check the trunk and spanning-tree configurations to make sure there aren't any blocking states. Then I'll look into the port-access and LLDP settings to see if there are any issues there.
upvoted 0 times
...
Rosendo
5 months ago
Hmm, this is a tricky one. I think I'll try to tackle it systematically. First, I'll confirm the basic connectivity by pinging the core. If that fails, I'll check the LACP and LAG configurations to make sure the uplink is set up correctly. Then I'll dive into the VLAN and L3 SVI settings to ensure the routing is configured properly.
upvoted 0 times
...
Gianna
5 months ago
Okay, this looks like a pretty complex issue. I think I'll start by checking the physical layer first - running the cable diagnostics to see if there are any issues with the physical links. Then I'll move on to verifying the routing and protocol configurations, like checking the IP routing table and OSPF status.
upvoted 0 times
...
Jamal
5 months ago
I'm a bit confused here. There are a lot of different commands to try, and I'm not sure which ones are the most important. I think I'll start with the basic ping to the core switch and see if that works. If not, I'll try to check the trunk and spanning-tree configurations.
upvoted 0 times
Serina
29 days ago
Definitely check the trunk settings after that.
upvoted 0 times
...
Yuonne
1 month ago
I agree, starting with the ping is a good idea.
upvoted 0 times
...
...

Save Cancel