01-26-2020 04:15 AM
Hi All,
The Core Switch has been configured with VLANs and it's respective IPs as given in the picture and have been synchronized to the client switches through VTP. I wanted to configure the Client Switch Access1 with an IP to access it through Telnet. I configured Access1 Switch's VLAN1 with the IP 192.168.1.1 with Telnet enabled on it, but couldn't either ping to that IP from my PC named VLAN10, which in turn didn't allow me to access it via Telnet. IP Routing is enabled on the Core Switch. Any suggestions?
Solved! Go to Solution.
01-26-2020 03:20 PM
If we had more detail about your environment we might be able to give you better advice. Based on the little that we know so far I offer this suggestion:
- the drawing shows the core switch with IP addresses for vlans 10, 20, and 30. Are we correct in understanding that the core switch does not have any IP address configured on vlan 1? If so that explains the issue. The access switch is attempting to communicate using vlan 1 but the core switch does not have any IP configured for vlan 1. To solve this either configure interface vlan 1 on the core with an appropriate IP address, or change the configuration of the access switch and configure its IP address in either vlan 10 or 20 or 30.
If this does not resolve your issue please provide more detail (preferably including configuration of both switches).
HTH
Rick
01-26-2020 04:47 AM - edited 01-26-2020 04:50 AM
Hi,
Usually i don't recommend to use Vlan 1 but if you want to continue with it, do the following:
On the core, you need to also crease VLAN SVI interface for Vlan 1, assign the IP and make sure it is no shut. Once you do that, you will be able to ping vlan 1 ip defined on your access1 switch from Core. After that, log in to Access1 and add default Route pointing to Core Vlan 1 IP.
Make your you can ping from your PC to Access1 switch. if Telnet config is already defined on switch Access1, then you will be able to telnet to it also.
On Core:
!
vlan 1
!
interface vlan 1
ip address 192.168.1.254 255.255.255.0
no shut
!
on Access1
!
ip routing
!
username xyz password xyz
enable secret xyz
i
vlan 1
!
interface vlan 1
ip address 192.168.1.1
no shut
!
ip route 0.0.0.0 0.0.0.0 192.168.1.254
!
line vty 0 15
login local
!
01-26-2020 03:20 PM
If we had more detail about your environment we might be able to give you better advice. Based on the little that we know so far I offer this suggestion:
- the drawing shows the core switch with IP addresses for vlans 10, 20, and 30. Are we correct in understanding that the core switch does not have any IP address configured on vlan 1? If so that explains the issue. The access switch is attempting to communicate using vlan 1 but the core switch does not have any IP configured for vlan 1. To solve this either configure interface vlan 1 on the core with an appropriate IP address, or change the configuration of the access switch and configure its IP address in either vlan 10 or 20 or 30.
If this does not resolve your issue please provide more detail (preferably including configuration of both switches).
HTH
Rick
01-27-2020 05:48 AM
Hi,
My requirement is simple. I need to access the Core, Access Switches via Telnet from the Network.
Now I have configured all the VLANs on the Core and have synchronized it through VTP. I can access the Core through the SVI IPs that I have configured on the Core Switch. But I want to access the Access (VTP Client) Switches through Telnet.
01-27-2020 07:05 AM
Yes your requirement is simple. And the solution is simple. As I suggested in my previous response either configure interface vlan 1 on the core with an appropriate IP address, or change the configuration of the access switch and configure its IP address in either vlan 10 or 20 or 30. This would allow you to access the switch using telnet.
HTH
Rick
01-28-2020 06:13 AM
I am glad that our responses have been helpful. Thank you for marking this question as solved. This will help other participants in the community to identify discussions which have helpful information. This community is an excellent place to ask questions and to learn about networking. I hope to see you continue to be active in the community.
HTH
Rick
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