Cisco WS-C3560X-48PF-L Hardware Installation Guide - Page 84

Interface Settings, Ping End Device, Spanning Tree Loops, Switch Performance, Speed, Duplex

Page 84 highlights

Diagnosing Problems Chapter 4 Troubleshooting Note When ordering or using CX1 cables, ensure that the version identifier is 2 or higher. • For long wave SFP+ modules, a mode conditioning patch might improve performance over maximum link distances with MMF connections. Interface Settings Verify that the port or interface is not disabled or powered off. If a port or interface is manually shut down on either side of the link, it does not come up until you re-enable the interface. Use the show interfaces privileged EXEC command to see if the interface is error-disabled, disabled, or shut down on either side of the connection. If needed, re-enable the interface. Ping End Device Ping from the directly connected switch first, and then work your way back port by port, interface by interface, trunk by trunk, until you find the source of the connectivity issue. Make sure that each switch can identify the end device MAC address in its Content-Addressable Memory (CAM) table. Spanning Tree Loops STP loops can cause serious performance issues that look like port or interface problems. A unidirectional link can cause loops. It occurs when the traffic sent by the switch is received by the neighbor, but the traffic from the neighbor is not received by the switch. A broken cable, other cabling problems, or a port issue could cause this one-way communication. You can enable UniDirectional Link Detection (UDLD) on the switch to help identify unidirectional link problems. For information about enabling UDLD on the switch, see the "Understanding UDLD" section in the software configuration guide on Cisco.com. Switch Performance Speed, Duplex, and Autonegotiation Port statistics that show a large amount of alignment errors, frame check sequence (FCS), or late-collisions errors, might mean a speed or duplex mismatch. A common issue occurs when duplex and speed settings are mismatched between two switches, between a switch and a router, or between the switch and a workstation or server. Mismatches can happen when manually setting the speed and duplex or from autonegotiation issues between the two devices. To maximize switch performance and to ensure a link, follow one of these guidelines when changing the duplex or the speed settings: • Let both ports autonegotiate both speed and duplex. • Manually set the speed and duplex parameters for the interfaces on both ends of the connection. • If a remote device does not autonegotiate, use the same duplex settings on the two ports. The speed parameter adjusts itself even if the connected port does not autonegotiate. Catalyst 3750-X and 3560-X Switch Hardware Installation Guide 4-4 OL-19593-02

  • 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

4-4
Catalyst 3750-X and 3560-X Switch Hardware Installation Guide
OL-19593-02
Chapter 4
Troubleshooting
Diagnosing Problems
Note
When ordering or using CX1 cables, ensure that the version identifier is 2 or higher.
For long wave SFP+ modules, a mode conditioning patch might improve performance over
maximum link distances with MMF connections.
Interface Settings
Verify that the port or interface is not disabled or powered off. If a port or interface is manually shut
down on either side of the link, it does not come up until you re-enable the interface. Use the
show
interfaces
privileged EXEC command to see if the interface is error-disabled, disabled, or shut down on
either side of the connection. If needed, re-enable the interface.
Ping End Device
Ping from the directly connected switch first, and then work your way back port by port, interface by
interface, trunk by trunk, until you find the source of the connectivity issue. Make sure that each switch
can identify the end device MAC address in its Content-Addressable Memory (CAM) table.
Spanning Tree Loops
STP loops can cause serious performance issues that look like port or interface problems.
A unidirectional link can cause loops. It occurs when the traffic sent by the switch is received by the
neighbor, but the traffic from the neighbor is not received by the switch. A broken cable, other cabling
problems, or a port issue could cause this one-way communication.
You can enable UniDirectional Link Detection (UDLD) on the switch to help identify unidirectional link
problems. For information about enabling UDLD on the switch, see the “Understanding UDLD” section
in the software configuration guide on Cisco.com.
Switch Performance
Speed, Duplex, and Autonegotiation
Port statistics that show a large amount of alignment errors, frame check sequence (FCS), or
late-collisions errors, might mean a speed or duplex mismatch.
A common issue occurs when duplex and speed settings are mismatched between two switches, between
a switch and a router, or between the switch and a workstation or server. Mismatches can happen when
manually setting the speed and duplex or from autonegotiation issues between the two devices.
To maximize switch performance and to ensure a link, follow one of these guidelines when changing the
duplex or the speed settings:
Let both ports autonegotiate both speed and duplex.
Manually set the speed and duplex parameters for the interfaces on both ends of the connection.
If a remote device does not autonegotiate, use the same duplex settings on the two ports. The speed
parameter adjusts itself even if the connected port does not autonegotiate.