HP 2000sa HP StorageWorks 2000 G2 Modular Smart Array reference guide (500911- - Page 94

configuration the surviving controller will kill, automatically. In an active-active

Get HP 2000sa PDF manuals and user guides View all HP 2000sa manuals
Add to My Manuals
Save this manual to your list of manuals

Page 94 highlights

Table 14 Event code descriptions and recommended actions (continued) Event Event type Description code Recommended action 90 Informational The partner controller does not have a mirrored configuration image for the current controller, so the current controller's local flash configuration is being used. This event is expected if the other controller is new or its configuration has been cleared. 95 Critical Both controllers in an active-active configuration have the same serial number. Non-unique serial numbers can cause system problems; for example, vdisk ownership and WWNs are determined by serial number. A service technician must examine both controller serial numbers and change at least one of them. 96 Informational Pending configuration changes that take effect at startup were ignored because customer data might be present in cache. If the requested configuration changes did not occur, make the changes again and then use a user-interface command to shut down or restart the controller. 100 Informational During active-active operation, an event (potential error) occurred while communicating with the EMP, which reports SES data. 101 Informational An update of EMP data has been triggered. This event is for internal use only. 103 Informational Volume name change is complete. 104 Informational Volume size change is complete. 105 Informational Volume LUN change is complete. 106 Informational A volume has been added. 107 Critical The controller experienced the specified critical error. In a non-redundant configuration the controller will be restarted automatically. In an active-active configuration the surviving controller will kill the controller that experienced the critical error. A service technician can use the debug log to determine the problem. 108 Informational A volume has been deleted. 109 Informational The statistics for the specified vdisk have been reset. 110 Informational Ownership of the specified vdisk has been given to the other controller. 111 Informational The link for the specified host port is up. 112 Informational The link for the specified host port is down. or warning This event is logged as informational for expected link-down events that happen during controller startup. This event is logged as a warning for unexpected link-down events. 113 Informational The link for the specified disk channel port is up. 114 Informational The link for the specified disk channel port is down. 94 Event code reference

  • 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
94
Event code reference
90
Informational
The partner controller does not have a
mirrored configuration image for the current
controller, so the current controller’s local
flash configuration is being used. This event
is expected if the other controller is new or its
configuration has been cleared.
95
Critical
Both controllers in an active-active
configuration have the same serial number.
Non-unique serial numbers can cause system
problems; for example, vdisk ownership and
WWNs are determined by serial number.
A service technician must examine both
controller serial numbers and change at least
one of them.
96
Informational
Pending configuration changes that take
effect at startup were ignored because
customer data might be present in cache.
If the requested configuration changes did
not occur, make the changes again and then
use a user-interface command to shut down
or restart the controller.
100
Informational
During active-active operation, an event
(potential error) occurred while
communicating with the EMP, which reports
SES data.
101
Informational
An update of EMP data has been triggered.
This event is for internal use only.
103
Informational
Volume name change is complete.
104
Informational
Volume size change is complete.
105
Informational
Volume LUN change is complete.
106
Informational
A volume has been added.
107
Critical
The controller experienced the specified
critical error. In a non-redundant
configuration the controller will be restarted
automatically. In an active-active
configuration the surviving controller will kill
the controller that experienced the critical
error.
A service technician can use the debug log
to determine the problem.
108
Informational
A volume has been deleted.
109
Informational
The statistics for the specified vdisk have
been reset.
110
Informational
Ownership of the specified vdisk has been
given to the other controller.
111
Informational
The link for the specified host port is up.
112
Informational
or warning
The link for the specified host port is down.
This event is logged as informational for
expected link-down events that happen
during controller startup. This event is logged
as a warning for unexpected link-down
events.
113
Informational
The link for the specified disk channel port is
up.
114
Informational
The link for the specified disk channel port is
down.
Table 14
Event code descriptions and recommended actions (continued)
Event
code
Event type
Description
Recommended action