Troubleshoot Your Connection; Possible Causes And Resolutions; Bad Ethernet Connection; Bad Console Port Connection - Cisco 500 Series Quick Start Manual

Troubleshoot Your Connection

If you cannot access your switch from the web-based interface, the switch
might not be reachable from your computer. You can test network
connections by using ping on a computer running Windows:
Open the Terminal application.
S 1
TEP
Enter the ping command and the switch IP address. For
S 2
TEP
example ping 192. 1 68. 1 .254 (the default IP address of the switch).
If you can reach the switch, you should get a reply similar to the
following:
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 terminal
application 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.
20 500 Series Stackable Managed Switches