HP J8698A User Manual - Page 70

Non-standard cables., Improper Network Topologies., Spanning Tree Protocol, Trunking

Get HP J8698A PDF manuals and user guides View all HP J8698A manuals
Add to My Manuals
Save this manual to your list of manuals

Page 70 highlights

Troubleshooting Troubleshooting Basic Troubleshooting Tips ■ Non-standard cables. Non-standard and miswired cables may cause network collisions and other network problems, and can seriously impair network performance. Use a new correctly-wired cable or compare your cable to the cable in appendix B, "Switch Ports and Network Cables" for pinouts and correct cable wiring. A category 5 cable tester is a recommended tool 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. With your Series 5400zl Switches, if you wish to build redundant paths between important nodes in your network to provide some fault tolerance, you should enable Spanning Tree Protocol support on the switch. This ensures that only one of the redundant paths is active at any time, thus avoiding data path loops. Spanning Tree can be enabled through the switch console, the web browser interface, or ProCurve Manager. The Series 5400zl Switches also support Trunking, which allows multiple network cables to be used for a single network connection without causing a data path loop. See the Management and Configuration Guide for more information on Spanning Tree and on Trunking, which is on the ProCurve Web site. See page 5-1 for details. ■ Connecting to devices that have a fixed full-duplex configuration. The RJ-45 ports on the Series 5400zl Switches are all configured as "Auto". That is, when connecting to attached devices, the switch will operate in one of two ways to determine the link speed and the communication mode (half duplex or full duplex): • if the connected device is also configured to Auto, the switch will automatically negotiate both link speed and communication mode • if the connected device has a fixed configuration, for example 100 Mbps, at half or full duplex, the switch will automatically sense the link speed, but will default to a communication of half duplex 5-2

  • 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
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
5-2
Troubleshooting
Basic Troubleshooting Tips
Troubleshooting
■
Non-standard cables.
Non-standard and miswired cables may cause
network collisions and other network problems, and can seriously impair
network performance. Use a new correctly-wired cable or compare your
cable to the cable in appendix B, “Switch Ports and Network Cables” for
pinouts and correct cable wiring. A category 5 cable tester is a recom-
mended tool 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.
With your Series 5400zl Switches, if you wish to build redundant paths
between important nodes in your network to provide some fault toler-
ance, you should enable
Spanning Tree Protocol
support on the switch.
This ensures that only one of the redundant paths is active at any time,
thus avoiding data path loops. Spanning Tree can be enabled through the
switch console, the web browser interface, or ProCurve Manager.
The Series 5400zl Switches also support
Trunking
, which allows multiple
network cables to be used for a single network connection without
causing a data path loop. See the
Management and Configuration Guide
for more information on Spanning Tree and on Trunking, which is on the
ProCurve Web site. See
page 5-1
for details.
■
Connecting to devices that have a fixed full-duplex configuration.
The RJ-45 ports on the Series 5400zl Switches are all configured as “Auto”.
That is, when connecting to attached devices, the switch will operate in
one of two ways to determine the link speed and the communication mode
(half duplex or full duplex):
•
if the connected device is also configured to Auto, the switch will
automatically negotiate both link speed and communication mode
•
if the connected device has a fixed configuration, for example 100
Mbps, at half or full duplex, the switch will automatically sense the
link speed, but will default to a communication of
half
duplex