HP Cluster Platform Interconnects v2010 Gigabit Ethernet Interconnect Guide - Page 73

Troubleshooting, 12.1 Basic Ethernet Troubleshooting Tips, Management and Configuration Guide

Page 73 highlights

12 Troubleshooting This chapter provides basic Ethernet troubleshooting tips (Section 12.1). 12.1 Basic Ethernet Troubleshooting Tips Most Ethernet problems are caused by the following situations. Check for these items first when starting your troubleshooting: • Faulty or loose cables. Look for loose or obviously faulty connections. If they appear to be undamaged, make sure the connections are snug. If that does not correct the problem, try a different cable. • Nonstandard cables. Nonstandard and incorrectly wired cables may cause network collisions and other network problems, and can seriously impair network performance. A category 5 cable tester is recommended for every 100Base-TX and 1000Base-T network installation. • Improper network topologies. It is important to make sure you have a valid network topology. Common topology faults include excessive cable length and excessive repeater delays between end nodes. If you have network problems after recent changes to the network, change back to the previous topology. If you no longer experience the problems, the new topology is probably at fault. In addition, you should make sure that your network topology contains no data path loops. Between any two end nodes, there should be only one active cabling path at any time. Data path loops will cause broadcast storms that will severely impact your network performance. • Port configuration. Check the port configurations. A port on your HP ProCurve switch may not be operating as you expect because it has been put into a "blocking" state, or the port may have been configured as disabled through software. Use the switch console to determine the port's configuration and verify that there is not an improper or undesired configuration of any of the switch features that may be affecting the port. For more information, refer to the Management and Configuration Guide, which is on the HP ProCurve switch documentation CD. • Duplex configuration. Make sure that all devices connected to the HP ProCurve switch are configured either to auto-negotiate or to connect at half duplex. If a device connected to the switch has a fixed configuration at full duplex, the device will not connect correctly to the switch. The result will be high error rates and inefficient communications between the switch and the device. For more information on possible network problems and their solutions, see the technical note Troubleshooting LAN Performance and Intermittent Connectivity Problems, which can be found on the HP ProCurve Web site, http://www.hp.com/go/hpProCurve/, in the Information Library section. 12.1 Basic Ethernet Troubleshooting Tips 73

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76

12 Troubleshooting
This chapter provides basic Ethernet troubleshooting tips (
Section 12.1
).
12.1 Basic Ethernet Troubleshooting Tips
Most Ethernet problems are caused by the following situations. Check for these items first when
starting your troubleshooting:
Faulty or loose cables. Look for loose or obviously faulty connections. If they appear to be
undamaged, make sure the connections are snug. If that does not correct the problem, try
a different cable.
Nonstandard cables. Nonstandard and incorrectly wired cables may cause network collisions
and other network problems, and can seriously impair network performance. A category 5
cable tester is recommended for every 100Base-TX and 1000Base-T network installation.
Improper network topologies. It is important to make sure you have a valid network topology.
Common topology faults include excessive cable length and excessive repeater delays
between end nodes. If you have network problems after recent changes to the network,
change back to the previous topology. If you no longer experience the problems, the new
topology is probably at fault. In addition, you should make sure that your network topology
contains no data path loops. Between any two end nodes, there should be only one active
cabling path at any time. Data path loops will cause broadcast storms that will severely
impact your network performance.
Port configuration. Check the port configurations. A port on your HP ProCurve switch may
not be operating as you expect because it has been put into a “blocking” state, or the port
may have been configured as disabled through software. Use the switch console to determine
the port's configuration and verify that there is not an improper or undesired configuration
of any of the switch features that may be affecting the port. For more information, refer to
the
Management and Configuration Guide
, which is on the HP ProCurve switch documentation
CD.
Duplex configuration. Make sure that all devices connected to the HP ProCurve switch are
configured either to auto-negotiate or to connect at half duplex. If a device connected to the
switch has a fixed configuration at full duplex, the device will not connect correctly to the
switch. The result will be high error rates and inefficient communications between the switch
and the device.
For more information on possible network problems and their solutions, see the technical note
Troubleshooting LAN Performance and Intermittent Connectivity Problems
, which can be found on
the HP ProCurve Web site,
http://www
.hp.com/go/hpProCurv
e/
, in the Information Library
section.
12.1 Basic Ethernet Troubleshooting Tips
73