HP StorageWorks 16-EL diagnostic and system error messages version 3.1.x refer - Page 13

Introduction to System Error Messages, Error Message Severity Levels

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

Page 13 highlights

Introduction to System Error Messages 1 This book supports Fabric OS version 3.1.x and contains diagnostic and system error messages, with recommended responses to the messages. Error messages are arranged alphabetically, first by module and then by individual message. A typical module contains multiple error messages. Each error message description consists of the following: ■ The message text ■ An explanation of the message or its probable cause ■ A recommended user response ■ The message's severity level. There may be more than one cause and more than one recommended course of action for any given message. This document provides the most probable cause and recommends the typically most beneficial response. This chapter provides an introduction to the error log system and consists of the following major topics: ■ Error Message Severity Levels on page 13 ■ Overview of System Logs on page 15 ■ View or Configure System Logs on page 17 ■ Reading a System Error Message on page 19 ■ Responding to a System Error Message on page 22 Error Message Severity Levels There are six levels of severity, ranging from 0 (panic) to 5 (debug). The definitions of the severity levels are quite general and should be used as guidelines for troubleshooting. In each case, you should thoroughly assess each error log description before taking a recovery action. Diagnostic and System Error Messages Version 3.1.x Reference Guide 13

  • 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
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
13
Diagnostic and System Error Messages Version 3.1.x Reference Guide
1
Introduction to System Error
Messages
This book supports Fabric OS version 3.1.x and contains diagnostic and system
error messages, with recommended responses to the messages. Error messages are
arranged alphabetically, first by module and then by individual message. A typical
module contains multiple error messages. Each error message description consists
of the following:
■
The message text
■
An explanation of the message or its probable cause
■
A recommended user response
■
The message’s severity level.
There may be more than one cause and more than one recommended course of
action for any given message. This document provides the most probable cause
and recommends the typically most beneficial response.
This chapter provides an introduction to the error log system and consists of the
following major topics:
■
Error Message Severity Levels
on page 13
■
Overview of System Logs
on page 15
■
View or Configure System Logs
on page 17
■
Reading a System Error Message
on page 19
■
Responding to a System Error Message
on page 22
Error Message Severity Levels
There are six levels of severity, ranging from 0 (panic) to 5 (debug). The
definitions of the severity levels are quite general and should be used as guidelines
for troubleshooting. In each case, you should thoroughly assess each error log
description before taking a recovery action.