The inability of an access switch to ping the core switch is usually caused by missing default gateway settings, VLAN misconfigurations, or routing issues.Key Causes1. Missing Default Gateway on Acces...
1. Missing Default Gateway on Access Switch If the access switch does not have a default gateway configured, it cannot route traffic to devices outside its local VLAN. Ensure the access switch has a default gateway pointing to the core switch's SVI IP for that VLAN:
ip default-gateway <core_switch_SVI_IP>
Without this, pings to the core switch from the access switch will fail even if the VLAN is active . 2. VLAN and Trunk Configuration Issues
switchport trunk allowed vlan 103
show ip route on both switches to verify that the routes exist and are correct . 4. Source IP Considerations When pinging from the access switch, the source IP may default to the management VLAN interface. If the core switch does not have a route back to that subnet, the ping will fail. Use extended ping commands to specify the source VLAN IP:ping <core_IP> source <access_switch_VLAN_IP>
This ensures the ping uses the correct interface .
show vlan brief on both switches to confirm VLAN presence.show interfaces trunk to ensure VLANs are allowed.show running-config | include default-gateway on the access switch.show ip route to confirm routes exist for the core switch subnet.show arp to ensure the access switch can resolve the core switch IP. By systematically verifying VLANs, trunking, default gateway, and routing, you can identify why the access switch cannot ping the core switch and correct the configuration .
Cost price When the switch trunk port is configured to have vlan 100 as the native vlan, all traffic on vlan100 is untagged, which looks like vlan1
Cost price I have a very strange but simple problem. I have a 4500X core with a 3850 stack connected. int vlan is configured on
Cost price Hello All! I have several 48 port Edge Switches that were on a flat network which I am now segmenting into VLANs.
Cost price I''m currently training for my CCNA and am using Packet Tracer to build simple networks. I ran into an issue where I was unable to
Cost price 3. However, when I test from a laptop connected to an access switch (set to access mode for VLAN 10), the laptop can
Cost price Hey, We just installed some new switches at a remote site. A 3750X as the core switch and around 12 access layer
Cost price Hi all, so, i configure my core switch (stack of 2 X670V) with different vlan interf ip adresses. all my configuration is on
Cost price 172.16.32.1 is the gateway for your subnet but probably isn''t the ip address your core is attempting to ping from. I''m guessing your
Cost price So in my network I have a setup where all the switches are on a /26 management network, on a management vlan. I
Cost price Is there something I''m missing? Port 27 goes to the main comms room where the server is that I''m trying to ping from and I can ping
Cost price I installed a new cisco cbs-250 that cannot be pinged or accessed remotely or when on the wireless network. When
Cost price I have a 4500X core with a 3850 stack connected. int vlan is configured on the core with 192.168.1.1 int vlan is
Cost price Hello, I am a beginner in packet tracer. In here, I''m using access, distrib (has trunking), core switches shown in my
Cost price Hi Friends, My task was to add new switches to the existing environment. So, the Setup is as below. So, i have these
Cost price Ideally, try pinging it from its LAN. If you can reach it from there then it''s probably a firewall/access control issue. If you
Cost price Hi all, Here is my network diagram: From the core switch, I can only ping to vlan 1 (10.65.0.0/24). I can''t ping to other
Cost price I cannot ssh or ping the right side / lower numbers (6.2,.3 .4) from core or left side. When I''m in the right side, I can
Cost price In a nut shell, why can I ping a device at a school on the core switch but not on the switch the device is plugged into
Cost price HI, we had a network management machine which we removed long time ago and now i have added another machine
Cost price I can ping both x440 from the core and the core from them. I also can ping switch 4 from switch 11 but not the other
Cost price Note: On a virtual standard switch, virtual machines cannot be placed on a vmkernel port group. Standard switches
Cost price Router has internet but Core Switch not picking, what i''m i missing? Router and Switch can ping each other Router
Cost price There is no communication with the device until you ping it from the core switch. My theory is that the core switch is not
Cost price Once all the changes had been saved, the switch & pc ip addresses were now able to be pinged. However, back in
Cost price Is the server you are trying to ping the switch from on the same VLAN? If it''s not, then unless the switch has a way to route inter
Cost price Ping from our access stack to the server - no replies Ping from the core switch to the server - there are replies We
Cost price VLAN routing seems to be working on the core switch when I test communication between VLANs by using the
Cost price I am able to ping from the attached device (MacBook via ethernet adaptor) to the switch without issue however when I
Contact us today for product inquiries, custom kits, or calibration support