7 replies
by jpru22 Accepted solution
by robo_dev Accepted solution
can you telnet to the switch?
Does the PC have a personal firewall or have Windows firewall enabled?
by jpru22 Accepted solution
by robo_dev Accepted solution
http://forums.techarena.in/networking-security/1129920.htm
from the above forum:
"You might have a problem with your default gateway command - the 'default gateway' command only sets the DGW for the console. It's the 'ip route' command that determines routes for the interfaces.
If you can ping the router, the 'ip route' is correct. If you can't telnet, you need to fix your 'default gateway'."
by jpru22 Accepted solution
by nwallette Accepted solution
This is prone to all sorts of confusion. There are a couple reasons why this could be.
First, a pretend network. Say you had two VLANS, 1 and 2, and they were assigned 10.0.1.1 and 10.0.2.1 on each, respectively, and ports 1 and 2 were assigned to VLANS 1 & 2 respectively.
The first problem is, if (for e.g.) port 1 is in access mode but there's no physical link (or it's admin shutdown), VLAN1 will not be "up" either. There *HAS* to be at least one port in that VLAN up before the VLAN itself will be up. (The switch will still forward packets over a trunk interface within VLAN1, but the management IP will not be accessible.)
So, Rule 1: Make sure you do at least this:
interface vlan1
ip address 10.0.1.1 255.255.255.0
no shutdown
interface fastethernet 0/1
switchport mode access
switchport access vlan 1
no shutdown
!
Next, if you tried to ping 10.0.1.3 from the switch, it may not work. Why? Because the switch may "source" the ping from the wrong place. Try this:
ping ip 10.0.1.3 source 10.0.1.1
This will ensure it comes from the VLAN1 management IP. You don't need any routing for this because it's in the same subnet. You only need routing enabled and a default gateway if you're going to jump subnets at some point in that packet's life.
If your switch has routing enabled, you might do well to use something like "ip default-network 10.0.1.0" to define your "main" or management subnet, but there are subtleties to that command which I haven't bothered to learn about. I'm trying to avoid Cisco in favor of stuff like Juniper these days.
If you want to telnet or SSH to the switch, you'll need to define these in the vty config:
username admin privilege 15 secret MyPassword
line vty 0 15
transport input telnet ssh
login default local
!
Once you're in the exec shell (either by telnet/ssh or serial console) you can try copying the config file to test your setup:
copy run tftp
[Follow prompts]
If that works, you can move on to copying the firmware image.
If all this fails, you may have more luck at the ROMmon.
Hope this helps some.
by cg it Accepted solution
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending