Cisco WS-C2960S-24TS-S Hardware Installation Guide - Page 74

Verify Switch POST Results, Monitor Switch LEDs, Verify Switch Connections, Bad or Damaged Cable - review

Get Cisco WS-C2960S-24TS-S PDF manuals and user guides View all Cisco WS-C2960S-24TS-S manuals
Add to My Manuals
Save this manual to your list of manuals

Page 74 highlights

Diagnosing Problems Chapter 4 Troubleshooting Verify Switch POST Results As the switch powers on, it begins the POST, a series of tests that runs automatically to ensure that the switch functions properly. It might take several minutes for the switch to complete POST. When the switch begins POST, the system LED slowly blinks green. When POST completes, the system LED blinks amber. If POST fails, the system LED remains amber. If POST completes successfully, the system LED rapidly blinks green. Note POST failures are usually fatal. Contact your Cisco technical support representative if your switch does not pass POST. Monitor Switch LEDs Look at the port LEDs for troubleshooting information about the switch. See the "LEDs" section on page 1-14 for a description of the LED colors and their meanings. Verify Switch Connections Review these sections when troubleshooting switch connectivity problems: • Bad or Damaged Cable, page 4-2 • Ethernet and Fiber Cables, page 4-3 • Link Status, page 4-3 • Transceiver Module Port Issues, page 4-3 • Port and Interface Settings, page 4-4 • Ping the End Device, page 4-4 • Spanning Tree Loops, page 4-4 Bad or Damaged Cable Always look at the cable for marginal damage or failure. A cable might connect at the physical layer but then cause packet corruption because of subtle damage to its wiring or connectors. You can identify this situation because the port will have many packet errors, or the port constantly loses and regains link. In these situations: • Change the copper or fiber-optic cable with a known, good cable if necessary. • Look for broken or missing pins on cable connectors. • Rule out any insufficient patch panel connections or media convertors between the source and the destination. If possible, bypass the patch panel or eliminate faulty media convertors, such as fiber-optic-to-copper convertors. • Try using the cable in another port or interface to see if the problem also exists there. Catalyst 2960 Switch Hardware Installation Guide 4-2 OL-7075-09

  • 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
4-2
Catalyst 2960 Switch Hardware Installation Guide
OL-7075-09
Chapter 4
Troubleshooting
Diagnosing Problems
Verify Switch POST Results
As the switch powers on, it begins the POST, a series of tests that runs automatically to ensure that the
switch functions properly. It might take several minutes for the switch to complete POST.
When the switch begins POST, the system LED slowly blinks green. When POST completes, the system
LED blinks amber. If POST fails, the system LED remains amber. If POST completes successfully, the
system LED rapidly blinks green.
Note
POST failures are usually fatal. Contact your Cisco technical support representative if your switch does
not pass POST.
Monitor Switch LEDs
Look at the port LEDs for troubleshooting information about the switch. See the
“LEDs” section on
page 1-14
for a description of the LED colors and their meanings.
Verify Switch Connections
Review these sections when troubleshooting switch connectivity problems:
•
Bad or Damaged Cable, page 4-2
•
Ethernet and Fiber Cables, page 4-3
•
Link Status, page 4-3
•
Transceiver Module Port Issues, page 4-3
•
Port and Interface Settings, page 4-4
•
Ping the End Device, page 4-4
•
Spanning Tree Loops, page 4-4
Bad or Damaged Cable
Always look at the cable for marginal damage or failure. A cable might connect at the physical layer but
then cause packet corruption because of subtle damage to its wiring or connectors. You can identify this
situation because the port will have many packet errors, or the port constantly loses and regains link. In
these situations:
•
Change the copper or fiber-optic cable with a known, good cable if necessary.
•
Look for broken or missing pins on cable connectors.
•
Rule out any insufficient patch panel connections or media convertors between the source and the
destination. If possible, bypass the patch panel or eliminate faulty media convertors, such as
fiber-optic-to-copper convertors.
•
Try using the cable in another port or interface to see if the problem also exists there.