Cisco 300 Series Managed Switches 11
Pinging 192.168.1.254 with 32 bytes of data:
Reply from 192.168.1.254: bytes=32 time<1ms TTL=128
If you cannot reach the switch, you should get a reply similar to the
following:
Pinging 192.168.1.254 with 32 bytes of data:
Request timed out.
Possible Causes and Resolutions
Bad Ethernet connection:
Check the LEDs for proper indications. Check the connectors of the
Ethernet cable to ensure they are firmly plugged into the switch and
your computer.
Bad Console port connection:
Check the console cable connectors to make sure they are firmly
plugged into the switch and your computer. Make sure the console
port utility is configured with the correct parameters.
Wrong IP address:
Make sure you are using the correct IP address for the switch. You can
determine the status of how the switch obtained the current IP address
by observing the system LED. You can determine the current IP
address of the switch through the console port interface by using the
CLI, or from your network administrator.
Make sure that no other device is using the same IP address as the
switch.
No IP route:
If the switch and your computer are in different IP subnets, you need
one or more routers to route the packets between the two subnets.
Unusually long access time:
Due to the standard spanning tree loop detection logic, adding new
connections may take 30 to 60 seconds for the affected interfaces
and/or LAN to become operational.
To Next Page
Loading...
