HP 6400/8400 HP StorageWorks 6400/8400 Enterprise Virtual Array User Guide - Page 105

Interpreting fault management information, The XCS version

Get HP 6400/8400 PDF manuals and user guides View all HP 6400/8400 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 105 highlights

1. When the Fault Management display is active (flashing), press menu. The LTEA selection menu is active (LTEA 0 is displayed). 2. Press or to increment to a specific error. 3. Press to observe data about the selected error. to select the Detail View Interpreting fault management information Each version of HP P6000 Command View includes an ASCII text file that defines all the codes that the authorized service representative can view either on the GUI or on the OCP. IMPORTANT: This information is for the exclusive use of the authorized service representative. The file name identifies the controller model, file type, XCS baselevel id, and XCS version. For example, the file name hsv210_event_cr08d3_5020.txt provides the following information: • hsv210_-The EVA controller model number • event_-The type of information in the file • w010605_-The base level build string (the file creation date). ◦ 01-The creation year ◦ 06-The creation month ◦ 05-The creation date • 5020-The XCS version Table 21 (page 105) describes types of information available in this file. Table 22 Controller event text description file Information type Event Code Termination Code (TC) Coupled Crash Control Codes Dump/Restart Control Codes Corrective Action Codes (CAC) Software Component ID Codes (SWCID) Event Information Packets (EIP) Description This hexadecimal code identifies the reported event type. This hexadecimal code specifies the condition that generated the termination code. It might also define either a system or user initiated corrective action. This single digit, decimal character defines the requirement for the other controller to initiate a coupled crash control.0. Other controller SHOULD NOT complete a coupled crash.1. Other controller SHOULD complete a coupled crash. This single decimal character (0, 1, 3) defines the requirement to:0. Perform a crash dump and then restart the controller.1. DO NOT perform a crash dump; just restart the controller.3. DO NOT perform a crash dump; DO NOT restart the controller. These hexadecimal codes supplement the Termination Code information to identify the faulty element and the recommended corrective action. These decimal codes identify software associated with the event. These codes specify the packet organization for specific type events. GUI termination event display 105

  • 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
  • 143
  • 144
  • 145
  • 146
1.
When the Fault Management display is active (flashing), press
to select the Detail View
menu.
The LTEA selection menu is active (LTEA 0 is displayed).
2.
Press
or
to increment to a specific error.
3.
Press
to observe data about the selected error.
Interpreting fault management information
Each version of HP P6000 Command View includes an ASCII text file that defines all the codes
that the authorized service representative can view either on the GUI or on the OCP.
IMPORTANT:
This information is for the exclusive use of the authorized service representative.
The file name identifies the controller model, file type, XCS baselevel id, and XCS version. For
example, the file name
hsv210_event_cr08d3_5020.txt
provides the following information:
•
hsv210_
—The EVA controller model number
•
event_
—The type of information in the file
•
w010605_
—The base level build string (the file creation date).
01
—The creation year
◦
◦
06
—The creation month
◦
05
—The creation date
•
5020
—The XCS version
Table 21 (page 105)
describes types of information available in this file.
Table 22 Controller event text description file
Description
Information type
This hexadecimal code identifies the reported event type.
Event Code
This hexadecimal code specifies the condition that generated the termination
code. It might also define either a system or user initiated corrective action.
Termination Code (TC)
This single digit, decimal character defines the requirement for the other controller
to initiate a coupled crash control.0. Other controller SHOULD NOT complete
a coupled crash.1. Other controller SHOULD complete a coupled crash.
Coupled Crash Control Codes
This single decimal character (0, 1, 3) defines the requirement to:0. Perform a
crash dump and then restart the controller.1. DO NOT perform a crash dump;
Dump/Restart Control Codes
just restart the controller.3. DO NOT perform a crash dump; DO NOT restart
the controller.
These hexadecimal codes supplement the Termination Code information to
identify the faulty element and the recommended corrective action.
Corrective Action Codes (CAC)
These decimal codes identify software associated with the event.
Software Component ID Codes
(SWCID)
These codes specify the packet organization for specific type events.
Event Information Packets (EIP)
GUI termination event display
105