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.

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
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
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
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

View Answer

Answer: C

Explanation:

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.

References: https://www.arubanetworks.com/techdocs/AOS-CX_10_04/CLI/GUID-8F0E7E8B-0F4B-4A3C-AE