Troubleshooting Switch Issues
Most issues that affect the switched network are encountered during the original implementation. Theoretically, after it is installed, a network will continue to operate without issues. However, that is only true in theory. Things change; cabling gets damaged, configurations change, and new devices are connected to the switch that require switch configuration changes. Ongoing maintenance is a fact of life.
Using a Layered Approach
Switches operate at multiple layers of the Open Systems Interconnection (OSI) model. At Layer 1 of the OSI model, switches provide an interface to the physical media. At Layer 2 of the OSI model, they provide switching of frames based on MAC addresses. Therefore, switch problems generally are seen as Layer 1 and Layer 2 issues. Some Layer 3 issues could also result, regarding IP connectivity to the switch for management purposes. The following sections describe using a layered approach to identify common switched network issues.
Identifying and Resolving Media Issues
Media issues are common. It is a fact of life that wiring gets damaged. These are some examples of everyday situations that can cause media issues:
- In an environment using Category 3 wiring, maintenance installs a new air conditioning system that introduces new electromagnetic interference (EMI) sources into the environment.
- In an environment using Category 5 wiring, cabling is run too close to an elevator motor.
- Poor cable management puts a strain on RJ-45 connectors, causing one or more wires to break.
- New applications change network traffic patterns.
- Something as simple as a user connecting a hub to the switch port to connect a second
PC can cause an increase in collisions.
Damaged wiring and EMI commonly show up as excessive collisions and noise. Changes in traffic patterns and the installation of a hub will show up as collisions and runt frames. These symptoms are best viewed using the show interface command, as shown in Example 2-13.
Example 2-13 Troubleshooting with the show interface Command
SwitchX# show interface fastethernet 0/0
Ethernet 0/0 is up, line protocol is up 
Hardware is MCI Ethernet, address is aa00.0400.0134 (via 0000.0c00.4369
Internet address is 184.108.40.206, subnet mask is 255.255.255.0
2295197 packets input, 305539992 bytes, 0 no buffer
Received 1925500 broadcasts, 0 runts, 0 giants
3 input errors, 3 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 
0 input packets with dribble condition detected
3594664 packets output, 436549843 bytes, 0 underruns
8 output errors, 
1790 collisions, 
10 interface resets,
0 restarts 
Table 2-9 Highlighted Fields for Troubleshooting
Identifying and Resolving Common Access Port Issues
Media-related issues can be reported as an access issue. (For example, the user might say, “I can’t access the network.”) Media issues should be isolated and resolved as indicated in the previous topic. Duplex-related issues result from a mismatch in duplex settings.
Speed-related issues result from a mismatch in speed settings.
Use the show interface command to verify the duplex settings.
Identifying and Resolving Common Configuration Issues
This topic describes methods of identifying and resolving common configuration issues. The watchword when it comes to configurations is better safe than sorry.
You should always know what you have before you start. When you have a working configuration, keep a copy. For example, keep both a hard copy and an electronic copy—a text file on a PC and/or a copy stored on a TFTP server.
When making changes, before saving the running configuration, verify that the changes accomplish what you wanted and do not cause unexpected issues. Changes made by an unauthorized person, whether malicious or not, can be disastrous. To ensure that you have secured the configuration, have both the console and VTY ports protected by a strong, complex password. Also, ensure that a strong, complex password has been enabled to enter privileged EXEC mode.