Observer 14, 5 Stars  
Got Observer 14?
If you're a customer under maintenance, the upgrade is free. Looking for more reasons to upgrade? Learn why Observer® earned ITPro Magazine's 5-star rating.
     
   
6 Steps to Troubleshooting Success   6 Steps to Troubleshooting Success
User complaints never come at an opportune time. You are already being pulled in 20 directions when a user complains of slow Internet or e-mail access. With few details and limited time to solve the problem, it's easy to overlook sound troubleshooting practices.

Not sure where to begin? The easiest place is to start at the bottom and work your way through the layers. Over the next few months, our EYE newsletter will feature some tips from NI University instructor Mike Motta – who helps educate countless individuals throughout the year on properly maintaining their network. In this article, we'll look at locating and diagnosing physical-layer issues in 6 steps.

Best Practice Note: Before troubleshooting, make sure you have a good network map showing how everything is connected through ports and switches. This allows you to know which switch and port interfaces to review for errors.

1. Ping the device
Ping the end device 5 times to verify connectivity between the console and device. If you're unable to successfully ping, it means the device is generating some type of error condition. If you can ping, everything is correctly connected to the network.

2. Verify switch connections
If you receive errors during pinging, the next step is to check the switch connections using the Show Interface command detailed in the Tech Spotlight section. Check switches and ports for errors and identify which side of the conversation is causing the problem. Verify the cable is correct for the network (Category 5 or higher for 10/100/1000 Gigabit) and doesn't exceed maximum distance requirements. Check the link status and be sure the port is enabled, operational, and configured appropriately.

3. Verify transceiver module
Before contacting the device manufacturer for support, be sure that you have the appropriate SFPs for the device.

4. Investigate errors
Within the Privileged Exec mode with Cisco switches, you can verify errors using the Show Interface command. Identify the port is enabled, duplex and speed settings are correct, and whether auto-negotiate is set. Although Show Interface is a Cisco command, other switches have similar commands to display status and configuration.

5. Switch checklist
If you are using multiple switches, make sure all are running the same IOS version. Verify interfaces are operational and configured properly. On Cisco switches, run the Show CDP Neighbor Details command to discover neighbor devices attached to the specific switch and verify connectivity between all other Cisco devices.

6. Attempt to ping device
Assuming everything is properly connected, you should be able to successfully ping all attached devices. With everything correctly connected at the physical layer, the next step will be to analyze communications and application performance using Observer's Expert Analysis.

Use the Network Application Performance white paper to walk through Observer's expert analysis capabilities for analyzing and troubleshooting application performance and transactions. In addition, to sharpen your network management and troubleshooting skills, sign up for one of our Network Instruments University classes.

 

     
   
WAN Acceleration   Tackling Switch Errors
One of the most common problems network managers face is troubleshooting network connections negotiating the wrong speed or duplex between devices. To identify switch speed and duplex settings and error conditions, use the following steps:


  1. Using Telnet log into the host. In this example, we're using PuTTY. Within Windows XP or older Windows operating systems, you'll find that you can telnet using command line.


  2. Once you have logged into the host, type show interface at the prompt. Show interface will either display all port interfaces or specific interfaces if you know the location of the issue.


  3. Check the speeds and duplex settings to make sure everything is in agreement. If you are having a negotiation problem, where one is at half-duplex and the other is operating at full-duplex, this should result in errors such as collisions. You can also look at packet counts to verify the switch if is sending and receiving packets appropriately. This can be done by checking input and output rates.

The following are common errors you'll encounter when troubleshooting switch issues:

Alignment Errors: commonly created by mismatched speed settings
CRC/FCS Errors: usually generated if there is a duplex mismatch
Late Collisions: indicates a duplex mismatch usually caused by auto-negotiation between connections



     
 
december 2009  


Last Month's Answer
A router that has eight ports will require 8 IP addresses.

Congrats to last month's winner, Stéphane Phillipe of Paris, France.

This month's question:
The Swiss Army Knife of sys admins is Perl. But how did it get the name?

Submit your answer and be entered to win a Network Instruments® polo shirt.

Application Delivery White Paper
Understand emerging challenges

New NIU Schedule (US & Canada)
Check out 2010 classes

NIU Kansas City
January 25-28