HP StorageWorks 8/80 Brocade Troubleshooting and Diagnostics Guide v6.1.0 (53- - Page 15

Introduction to Troubleshooting, In this About troubleshooting, Network time protocol

Get HP StorageWorks 8/80 - SAN Switch PDF manuals and user guides View all HP StorageWorks 8/80 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 15 highlights

Chapter Introduction to Troubleshooting 1 This chapter provides information on troubleshooting and the most common procedures to use to diagnose and recover from problems. This book is a companion guide to be used in conjunction with the Fabric OS Administrator's Guide. Although it provides a lot of common troubleshooting tips and techniques it does not teach troubleshooting methodology. In this chapter •About troubleshooting 1 •Most common problem areas 2 •Questions for common symptoms 2 •Gathering information for your switch support provider 5 •Building a case for your switch support provider 7 About troubleshooting Troubleshooting should begin at the center of the SAN - the fabric. Because switches are located between the hosts and storage devices and have visibility into both sides of the storage network, starting with them can help narrow the search path. After eliminating the possibility of a fault within the fabric, see if the problem is on the storage side or the host side, and continue a more detailed diagnosis from there. Using this approach can quickly pinpoint and isolate problems. For example, if a host cannot detect a storage device, run a switch command, for example switchShow to determine if the storage device is logically connected to the switch. If not, focus first on the switch directly connecting to storage. Use your vendor-supplied storage diagnostic tools to better understand why it is not visible to the switch. If the storage can be detected by the switch, and the host still cannot detect the storage device, then there is still a problem between the host and switch. Network time protocol One of the most frustrating parts of troubleshooting is trying to synchronize switch's message logs and portlogs with other switches in the fabric. If you do not have NTP set up on your switches, then trying to synchronize log files to track a problem is practically impossible. Fabric OS Troubleshooting and Diagnostics Guide 1 53-1000853-01

  • 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
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
Fabric OS Troubleshooting and Diagnostics Guide
1
53-1000853-01
Chapter
1
Introduction to Troubleshooting
This chapter provides information on troubleshooting and the most common procedures to use to
diagnose and recover from problems.
This book is a companion guide to be used in conjunction with the
Fabric OS Administrator’s Guide
.
Although it provides a lot of common troubleshooting tips and techniques it does not teach
troubleshooting methodology.
In this chapter
•
About troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1
•
Most common problem areas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2
•
Questions for common symptoms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2
•
Gathering information for your switch support provider. . . . . . . . . . . . . . . . .
5
•
Building a case for your switch support provider . . . . . . . . . . . . . . . . . . . . . .
7
About troubleshooting
Troubleshooting should begin at the center of the SAN — the fabric. Because switches are located
between the hosts and storage devices and have visibility into both sides of the storage network,
starting with them can help narrow the search path. After eliminating the possibility of a fault within
the fabric, see if the problem is on the storage side or the host side, and continue a more detailed
diagnosis from there. Using this approach can quickly pinpoint and isolate problems.
For example, if a host cannot detect a storage device, run a switch command, for example
switchShow
to determine if the storage device is logically connected to the switch. If not, focus first
on the switch directly connecting to storage. Use your vendor-supplied storage diagnostic tools to
better understand why it is not visible to the switch. If the storage can be detected by the switch,
and the host still cannot detect the storage device, then there is still a problem between the host
and switch.
Network time protocol
One of the most frustrating parts of troubleshooting is trying to synchronize switch’s message logs
and portlogs with other switches in the fabric. If you do not have NTP set up on your switches, then
trying to synchronize log files to track a problem is practically impossible.