07-10-2023 11:04 PM - edited 07-10-2023 11:13 PM
Hi Cisco Geeks,
There are a Cisco ISR 4331 and Cisco 4507 (Core) and some Cisco 3650 (Access Switches's) in my Network,
I'm unable to take control of an Access switch via Telnet\SSH directly from putty, but able to access from Core to Access Switch (vice versa) and I can't PING the Access Switch from Windows CMD too, but Internet is working fine on all the switches.
Since I'm new to the Network, I can't express the issue in a better way, Kindly support to resolve this.
Pls find the attachment of my network.
Thanks in advance…!
Regards
Naveen
07-10-2023 11:18 PM
- Make sure the path to the ISR is not blocked from the laptop by routing constraints or traffic filtering (ACLs or firewalling) ; you can check this with tracert ISR-hostname or nmap --reason -p22 ISR-hostname , (e.g.)
M.
07-11-2023 02:08 AM
the issue in Access SW, it must have correct default gateway.
do you config default gateway point to Core SVI ?
07-12-2023 12:25 AM
The solution you referred isn't working, FYI.
Core IP – 172.16.5.254 and Access SW IP – 172.16.5.1
Access SW config I applied:
#ip default-gateway 172.16.5.254
#sh ip route
172.16.0.0/16 is variably subnetted, 2 subnets, 2 masks
C 172.16.5.0/24 is directly connected, Vlan5
L 172.16.5.1/32 is directly connected, Vlan5
07-12-2023 12:40 AM - edited 07-12-2023 12:41 AM
""able to access from Core to Access Switch""
PC-Core-Access
You can connect Access SW from Core because Core use VLAN5 SVI to connect to VLAN5 SVI of Access SW, there is L2
if you try using PC with IP within subnet of VLAN5 SVI (sure PC must connect to port assign to vlan5 in Core SW) you can connect to access SW.
OR
using in access switch
ip default gateway <VLAN5 SVI IP of Core SW>
this allow you to connect access SW if PC have any IP.
07-12-2023 05:33 AM
Able to access "Core-to-Access SW" via Putty SSH, I'm not even get ping response from the Access SW on Windows CMD.
09-04-2023 01:55 AM - edited 09-04-2023 01:57 AM
[Resolved]
The issue is resolved after adding a routing command on the Access SW.
#ip route 0.0.0.0 0.0.0.0 172.16.5.254
09-04-2023 10:56 AM
Thank you for the update letting us know that you resolved the issue. In our discussions we had been assuming that the access switch was operating as a layer 2 switch. For a layer 2 switch the command that you used "ip default-gateway 172.16.5.254" would be correct. The fact that the solution was to configure a static default route indicates that ip routing was enabled and the switch was operating as a layer 3 switch.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide