Dot Hill Systems SANnet II 200 Service Manual Page 163
- Page / 210
- Table of contents
- TROUBLESHOOTING
- BOOKMARKS
Rated. / 5. Based on customer reviews
C-1
APPENDIX
C
Failed Component Alarm Codes
This appendix describes failed component alarm codes.
Failed component alarm codes use Morse code dot and dash characters. The dot “.” is
a short tone sounding for one unit of time. The dash “-” is a long tone sounding for
three units of time.
Alarms, also referred to as beep codes, are presented in a sequence, starting with the
critical component failure alarm, which alerts you to a component problem or failure
or a firmware mismatch. This alarm is then followed by alarms for whichever
components or assemblies have failed. Once the beep code sequence is complete, it
repeats. To understand the beep codes, listen to the sequence of codes until you can
break down the sequence into its separate alarms. You can also check your software or
firmware for alarms, error messages, or logs to isolate and understand the cause. For
example, in the case of a fan failure in a power supply, you might first hear the critical
component failure alarm, followed by a power supply failure alarm from power supply
0 or power supply 1, followed by a fan failure event alarm. This sequence continues to
repeat.
Table C-1 Failed Component Alarm Codes
Failure Morse Code Letter
Morse Code Sound
Pattern
Critical component
failure or mismatch
8 dashes --------
Power supply 0 failure P0 . -- . -----
Power supply 1 failure P1 . -- . . ----
Event alarm E .
Fan failure F . . - .
Voltage failure V . . . -
Temperature failure T -
SES/PLD firmware
mismatch
R. - .
- II 200 FC, SATA, and SATA SE 1
- Service Manual 1
- Copyright 2
- Trademarks 2
- Contents 3
- Contents v 5
- Contents vii 7
- Contents ix 9
- Figures xiii 13
- How This Book Is Organized 17
- Typographic Conventions 18
- Related Documentation 18
- Technical Support 19
- SANnet II 200 SATA Arrays 24
- Configurations 26
- 1.2 Field-Replaceable Units 28
- 1.2.2 I/O Expansion Modules 29
- 1.2.3 Disk Drives 29
- 1.2.4 Battery Module 30
- 1.3 Interoperability 31
- 1.4.1 FC Protocols 32
- 1.4.2 FC Topologies 32
- 1.4.3 Fibre Hubs and Switches 32
- 1.4.4 Data Availability 33
- 1.4.5 Scalability 33
- 1.5.1.1 Host Bus Adapters 34
- 1.6 Additional Software Tools 35
- Site Planning 37
- 2.2 Safety Precautions 38
- Operating Nonoperating 39
- 2.5 Physical Specifications 40
- 2.6 Layout Map 40
- 2.6.2 Tabletop Placement 41
- Chapter 2 Site Planning 2-7 43
- Unpacking Your Array 45
- 3.2.1 Standard Array Packages 46
- 3.3 Field-Replaceable Units 47
- 3.4 Customer-Provided Cables 47
- Connecting Your Array 49
- Cannot Be Removed 50
- 4.2 RAID Array Connections 52
- II 200 SATA array 53
- SATA Array 54
- Servers and consoles 55
- Management 55
- FC device connections 55
- Pin Number Voltage Color 58
- Bezel locks 62
- LEDs Displayed 64
- Two drive ports on channel 2 66
- Two ports on channel 3 66
- Data Transfer 67
- Two drive ports on channel 3 67
- Host channel 0 68
- Host channel 1 68
- Host channel 4 68
- Host channel 5 68
- 4.8.3 Default SFP Placement 69
- Default SFP Placement 72
- RAID Array 74
- Change/Set IP Address ? 75
- Ethernet 76
- # telnet IP-address 77
- 4.16 Power-On Sequence 80
- 4.17 Powering Off the Array 81
- Configuration Overview 83
- host IDs to 87
- Switches 89
- Two Switches 90
- Server 1 93
- Server 2 93
- Server 3 93
- Server 4 93
- 5.2 Larger Configurations 96
- Checking LEDs 99
- 6.2 Front-Panel LEDs 100
- LED LED Color Description 101
- 6.2.1 Drive LED Status 102
- 6.3 Back-Panel LEDs 103
- Chapter 6 Checking LEDs 6-7 105
- Chapter 6 Checking LEDs 6-9 107
- Maintaining Your Array 109
- 7.1.1 Out-of-Band Connections 110
- 7.1.2 In-Band Connections 110
- 7.1.4 Enabling VERITAS DMP 111
- 7.2 Battery Operation 112
- 7.4 Upgrading Firmware 115
- Troubleshooting Your Array 119
- 8.1.1 Cooling Element Sensors 120
- 8.1.2 Temperature Sensors 121
- 8.1.3 Voltage Sensors 122
- 8.2 Silencing Audible Alarms 123
- 8.4 Controller Failover 125
- ■ Tests that LEDs work 128
- ■ Resets the array 128
- ■ “Drive LEDs” on page 8-13 129
- Power supply or fan problem 130
- 8.7.2 Drive LEDs 131
- Drive LEDs problem (FC) 133
- 8.7.3 Front-Panel LEDs 134
- 3A 135
- 3B 136
- 3C 137
- 3D 138
- 8.7.4 I/O Controller Module 139
- Specifications 141
- Highlights 142
- A.2.1 Hardware Loop ID 143
- Product Safety Standard 144
- Electromagnetic Interference 145
- Test Standard 145
- 200 FC Array Only) 147
- Methods (JBOD Arrays) 148
- JBOD Arrays 148
- B.5.1 SANscape 149
- JBOD Array 150
- Press to change the ID number 151
- Host computer 154
- JBOD array 154
- Host Computer 155
- ■ For Linux, var/log/messages 159
- ■ SANscape event log 159
- ■ SANscape CLI event log 160
- Failed Component Alarm Codes 163
- Cable Pinouts 165
- D.2 DB9 COM Port 166
- Solaris Operating System 167
- Workstation 168
- # tip -38400 /dev/ttyn 168
- # tip -38400 /dev/ttyb 168
- 1. Reboot the computer 169
- APPENDIX 171
- ■ 38,400 baud 172
- ■ 8 data bits 172
- ■ 1 stop bit 173
- ■ No parity 173
- Microsoft Windows Server 174
- Windows Servers 178
- Configuring a Linux Server 179
- Linux Server 181
- G.3 Checking the Adapter BIOS 182
- G.6 Creating a File System 184
- System Manually 185
- Operating System 187
- IBM Server Running AIX 188
- COM port 189
- Create a Logical Volume 190
- Recognize New LUNs 190
- H.5 Creating a Volume Group 191
- H.6 Creating a Logical Volume 192
- H.7 Creating a File System 192
- Servers Running AIX 194
- HP-UX Operating System 195
- HP Server Running HP-UX 196
- I.3 Attaching the Disk Array 198
- I.4 Logical Volume Manager 198
- # ioscan -fnC disk 199
- I.7 Creating a Volume Group 200
- I.8 Creating a Logical Volume 201
- 2. Type: 204
Related products and manuals for Networking Dot Hill Systems SANnet II 200
(35 pages)© 2020, manymanuals.com. All rights reserved. | 0.703 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comments to this Manuals