Server Administrator

Version 8.5 Messages Reference Guide

Notes, cautions, and warnings

NOTE: A NOTE indicates important information that helps you make better use of your product.

CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem.

WARNING: A WARNING indicates a potential for property damage, personal injury, or death.

Copyright © 2017 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners.

2017 - 03

Rev. A00

Contents

1 Introduction....................................................................................................................16

New in this release ............................................................................................................................................................ 16

Alert Message Change History ..........................................................................................................................................16

Messages Not Described in This Guide ............................................................................................................................. 18

Understanding Event Messages ........................................................................................................................................18

Sample Event Message Text ....................................................................................................................................... 19

Viewing Alerts and Event Messages ..................................................................................................................................19

Logging Messages to a Unicode Text File ...................................................................................................................20

Viewing Events in Microsoft Windows Server 2008 ................................................................................................... 20

Viewing Events in Red Hat Enterprise Linux and SUSE Linux Enterprise Server .........................................................20

Viewing Events in VMware ESX/ESXi .........................................................................................................................21

Viewing the Event Information .................................................................................................................................... 21

Understanding the Event Description ..........................................................................................................................21

2 Server Management Messages..................................................................................... 25

Server Administrator General Messages ...........................................................................................................................25

Event ID — 0000 .......................................................................................................................................................25

Event ID — 0001 ........................................................................................................................................................25

Event ID — 1000 ........................................................................................................................................................25

Event ID — 1001 ........................................................................................................................................................ 25

Event ID — 1002 ........................................................................................................................................................25

Event ID – 1003 ..........................................................................................................................................................26

Event ID — 1004 ........................................................................................................................................................26

Event ID — 1005 ........................................................................................................................................................26

Event ID — 1006 ........................................................................................................................................................26

Event ID — 1007 ........................................................................................................................................................26

Event ID — 1008 ........................................................................................................................................................26

Event ID — 1009 ........................................................................................................................................................27

Event ID — 1011 ......................................................................................................................................................... 27

Event ID — 1012 .........................................................................................................................................................27

Event ID — 1013 .........................................................................................................................................................27

Event ID — 1014 .........................................................................................................................................................27

Event ID — 1019 .........................................................................................................................................................27

Event ID — 1016 ........................................................................................................................................................ 28

Temperature Sensor Messages ........................................................................................................................................ 28

Event ID — 1050 ........................................................................................................................................................28

Event ID — 1051 .........................................................................................................................................................28

Event ID — 1052 ........................................................................................................................................................29

Event ID — 1053 ........................................................................................................................................................29

Event ID — 1054 ........................................................................................................................................................29

Event ID — 1055 ........................................................................................................................................................30

3

4

Cooling Device Messages .................................................................................................................................................30

Event ID — 1100 ........................................................................................................................................................ 30

Event ID — 1101 .......................................................................................................................................................... 31

Event ID — 1102 ......................................................................................................................................................... 31

Event ID — 1103 ......................................................................................................................................................... 31

Event ID — 1104 ......................................................................................................................................................... 31

Event ID — 1105 ........................................................................................................................................................ 32

Voltage Sensor Messages ................................................................................................................................................ 32

Event ID — 1150 ........................................................................................................................................................ 32

Event ID — 1151 ......................................................................................................................................................... 32

Event ID — 1152 .........................................................................................................................................................33

Event ID — 1153 .........................................................................................................................................................33

Event ID — 1154 .........................................................................................................................................................33

Event ID — 1155 ........................................................................................................................................................ 34

Current Sensor Messages ................................................................................................................................................ 34

Event ID – 1200 ..........................................................................................................................................................34

Event ID — 1201 ........................................................................................................................................................ 35

Event ID — 1202 ........................................................................................................................................................35

Event ID — 1203 ........................................................................................................................................................36

Event ID — 1204 ........................................................................................................................................................36

Event ID — 1205 ........................................................................................................................................................36

Chassis Intrusion Messages ..............................................................................................................................................37

Event ID — 1251 ......................................................................................................................................................... 37

Event ID — 1252 ........................................................................................................................................................ 37

Event ID — 1254 ........................................................................................................................................................38

Redundancy Unit Messages ............................................................................................................................................. 38

Event ID — 1300 ........................................................................................................................................................38

Event ID — 1301 .........................................................................................................................................................38

Event ID — 1302 ........................................................................................................................................................39

Event ID — 1303 ........................................................................................................................................................39

Event ID — 1304 ........................................................................................................................................................39

Event ID — 1305 ........................................................................................................................................................39

Event ID — 1306 ........................................................................................................................................................40

Power Supply Messages .................................................................................................................................................. 40

Event ID — 1351 .........................................................................................................................................................40

Event ID — 1352 ........................................................................................................................................................40

Event ID — 1353 .........................................................................................................................................................41

Event ID — 1354 .........................................................................................................................................................41

Memory Device Messages ................................................................................................................................................ 41

Event ID — 1400 ........................................................................................................................................................42

Event ID — 1401 .........................................................................................................................................................42

Event ID — 1402 ........................................................................................................................................................42

Event ID — 1403 ........................................................................................................................................................42

Event ID — 1404 ........................................................................................................................................................43

Event ID — 1405 ........................................................................................................................................................43

Hardware Log Sensor Messages ...................................................................................................................................... 43

Event ID — 1550 ........................................................................................................................................................43

Event ID — 1551 .........................................................................................................................................................43

Event ID — 1552 ........................................................................................................................................................44

Event ID — 1553 ........................................................................................................................................................44

Event ID — 1554 ........................................................................................................................................................44

Event ID — 1555 ........................................................................................................................................................44

Processor Sensor Messages ............................................................................................................................................ 44

Event ID — 1601 ........................................................................................................................................................ 44

Event ID — 1602 ........................................................................................................................................................45

Event ID — 1603 ........................................................................................................................................................45

Event ID — 1604 ........................................................................................................................................................45

Pluggable Device Messages ............................................................................................................................................. 46

Event ID — 1650 ........................................................................................................................................................46

Event ID — 1651 .........................................................................................................................................................46

Event ID — 1652 ........................................................................................................................................................46

Event ID — 1653 ........................................................................................................................................................46

Battery Sensor Messages .................................................................................................................................................47

Event ID — 1700 ........................................................................................................................................................ 47

Event ID — 1701 .........................................................................................................................................................47

Event ID — 1702 ........................................................................................................................................................ 47

Event ID — 1703 ........................................................................................................................................................ 47

Event ID — 1704 ........................................................................................................................................................ 48

Event ID — 1705 ........................................................................................................................................................48

Secure Digital (SD) Card Device Messages ...................................................................................................................... 48

Event ID — 1750 ........................................................................................................................................................48

Event ID — 1751 .........................................................................................................................................................49

Event ID — 1752 ........................................................................................................................................................ 49

Event ID — 1753 ........................................................................................................................................................49

Event ID — 1754 ........................................................................................................................................................50

Event ID — 1755 ........................................................................................................................................................50

3 Storage Management Message Reference.....................................................................51

Alert Monitoring and Logging ............................................................................................................................................ 51

Alert Message Format with Substitution Variables ............................................................................................................ 51

Alert Descriptions and Corrective Actions ........................................................................................................................ 53

Event ID — 2048 ....................................................................................................................................................... 53

Event ID — 2049 ....................................................................................................................................................... 54

Event ID — 2050 .......................................................................................................................................................54

Event ID — 2051 ........................................................................................................................................................54

Event ID — 2052 .......................................................................................................................................................55

Event ID — 2053 .......................................................................................................................................................55

Event ID — 2054 .......................................................................................................................................................55

Event ID — 2055 .......................................................................................................................................................56

Event ID — 2056 .......................................................................................................................................................56

Event ID — 2057 ....................................................................................................................................................... 56

5

6

Event ID — 2058 ....................................................................................................................................................... 57

Event ID — 2059 ....................................................................................................................................................... 57

Event ID — 2060 .......................................................................................................................................................58

Event ID — 2061 ........................................................................................................................................................58

Event ID — 2062 ....................................................................................................................................................... 58

Event ID — 2063 ....................................................................................................................................................... 59

Event ID — 2064 ....................................................................................................................................................... 59

Event ID — 2065 .......................................................................................................................................................59

Event ID — 2067 ....................................................................................................................................................... 60

Event ID — 2070 ....................................................................................................................................................... 60

Event ID — 2074 ....................................................................................................................................................... 60

Event ID — 2075 ........................................................................................................................................................ 61

Event ID — 2076 ........................................................................................................................................................ 61

Event ID — 2077 ........................................................................................................................................................ 61

Event ID — 2079 ....................................................................................................................................................... 62

Event ID — 2080 ....................................................................................................................................................... 62

Event ID — 2081 ........................................................................................................................................................62

Event ID — 2082 ....................................................................................................................................................... 63

Event ID — 2083 ....................................................................................................................................................... 63

Event ID — 2085 ....................................................................................................................................................... 64

Event ID — 2086 ....................................................................................................................................................... 64

Event ID — 2087 ....................................................................................................................................................... 64

Event ID — 2088 ....................................................................................................................................................... 65

Event ID — 2089 .......................................................................................................................................................65

Event ID — 2090 .......................................................................................................................................................65

Event ID — 2091 ........................................................................................................................................................66

Event ID — 2092 ....................................................................................................................................................... 66

Event ID — 2094 ....................................................................................................................................................... 66

Event ID — 2095 ....................................................................................................................................................... 67

Event ID — 2098 ....................................................................................................................................................... 67

Event ID — 2099 ....................................................................................................................................................... 67

Event ID — 2100 ........................................................................................................................................................68

Event ID — 2101 ........................................................................................................................................................ 68

Event ID — 2102 ........................................................................................................................................................69

Event ID — 2103 ........................................................................................................................................................69

Event ID — 2104 ........................................................................................................................................................69

Event ID — 2105 ........................................................................................................................................................70

Event ID — 2106 ........................................................................................................................................................70

Event ID — 2107 ........................................................................................................................................................ 70

Event ID — 2108 .........................................................................................................................................................71

Event ID — 2109 .........................................................................................................................................................71

Event ID — 2110 .........................................................................................................................................................72

Event ID — 2111 ..........................................................................................................................................................72

Event ID — 2112 .........................................................................................................................................................72

Event ID — 2114 .........................................................................................................................................................73

Event ID — 2115 .........................................................................................................................................................73

Event ID — 2116 .........................................................................................................................................................73

Event ID — 2117 ......................................................................................................................................................... 74

Event ID — 2118 ......................................................................................................................................................... 74

Event ID — 2120 ........................................................................................................................................................ 75

Event ID — 2121 .........................................................................................................................................................75

Event ID — 2122 ........................................................................................................................................................ 75

Event ID — 2123 ........................................................................................................................................................ 76

Event ID — 2124 ........................................................................................................................................................ 76

Event ID — 2125 ........................................................................................................................................................ 77

Event ID — 2126 ........................................................................................................................................................ 77

Event ID — 2127 .........................................................................................................................................................77

Event ID — 2128 ........................................................................................................................................................ 78

Event ID — 2129 ........................................................................................................................................................ 78

Event ID — 2130 ........................................................................................................................................................ 78

Event ID — 2131 .........................................................................................................................................................79

Event ID — 2132 ........................................................................................................................................................ 79

Event ID — 2135 ........................................................................................................................................................ 79

Event ID — 2136 ........................................................................................................................................................80

Event ID — 2137 ........................................................................................................................................................ 80

Event ID — 2138 .........................................................................................................................................................81

Event ID — 2139 .........................................................................................................................................................81

Event ID — 2140 .........................................................................................................................................................81

Event ID — 2141 .........................................................................................................................................................82

Event ID — 2142 ........................................................................................................................................................ 82

Event ID — 2143 ........................................................................................................................................................ 82

Event ID — 2144 ........................................................................................................................................................83

Event ID — 2145 ........................................................................................................................................................83

Event ID — 2146 ........................................................................................................................................................83

Event ID — 2147 ........................................................................................................................................................ 84

Event ID — 2148 ........................................................................................................................................................84

Event ID — 2149 ........................................................................................................................................................84

Event ID — 2150 ........................................................................................................................................................85

Event ID — 2151 .........................................................................................................................................................85

Event ID — 2152 ........................................................................................................................................................85

Event ID — 2153 ........................................................................................................................................................86

Event ID — 2154 ........................................................................................................................................................86

Event ID — 2155 ........................................................................................................................................................86

Event ID — 2156 ........................................................................................................................................................ 87

Event ID — 2157 ........................................................................................................................................................ 87

Event ID — 2158 ........................................................................................................................................................ 87

Event ID — 2159 ........................................................................................................................................................88

Event ID — 2160 ........................................................................................................................................................88

Event ID — 2161 .........................................................................................................................................................88

Event ID — 2162 ........................................................................................................................................................89

7

8

Event ID — 2163 ........................................................................................................................................................89

Event ID — 2164 ........................................................................................................................................................89

Event ID — 2165 ........................................................................................................................................................90

Event ID — 2166 ........................................................................................................................................................90

Event ID — 2167 .........................................................................................................................................................91

Event ID — 2168 .........................................................................................................................................................91

Event ID — 2169 .........................................................................................................................................................91

Event ID — 2170 ........................................................................................................................................................ 92

Event ID — 2171 .........................................................................................................................................................92

Event ID — 2172 ........................................................................................................................................................ 92

Event ID — 2173 ........................................................................................................................................................ 93

Event ID — 2174 ........................................................................................................................................................ 93

Event ID — 2175 ........................................................................................................................................................ 93

Event ID — 2176 ........................................................................................................................................................ 94

Event ID — 2177 ........................................................................................................................................................ 94

Event ID — 2178 ........................................................................................................................................................ 94

Event ID — 2179 ........................................................................................................................................................95

Event ID — 2180 ........................................................................................................................................................95

Event ID — 2181 ........................................................................................................................................................ 95

Event ID — 2182 ........................................................................................................................................................96

Event ID — 2183 ........................................................................................................................................................96

Event ID — 2184 ........................................................................................................................................................96

Event ID — 2185 ........................................................................................................................................................ 97

Event ID — 2186 ........................................................................................................................................................ 97

Event ID — 2187 ........................................................................................................................................................ 97

Event ID — 2188 ........................................................................................................................................................98

Event ID — 2189 ........................................................................................................................................................98

Event ID — 2190 ........................................................................................................................................................98

Event ID — 2191 ........................................................................................................................................................ 99

Event ID — 2192 ........................................................................................................................................................99

Event ID — 2193 ........................................................................................................................................................99

Event ID — 2194 ...................................................................................................................................................... 100

Event ID — 2195 ...................................................................................................................................................... 100

Event ID — 2196 ...................................................................................................................................................... 100

Event ID — 2197 ....................................................................................................................................................... 101

Event ID — 2198 ....................................................................................................................................................... 101

Event ID — 2199 ....................................................................................................................................................... 101

Event ID — 2200 ......................................................................................................................................................102

Event ID — 2201 ...................................................................................................................................................... 102

Event ID — 2202 ......................................................................................................................................................102

Event ID — 2203 ......................................................................................................................................................103

Event ID — 2204 ......................................................................................................................................................103

Event ID — 2205 ......................................................................................................................................................103

Event ID — 2206 ......................................................................................................................................................104

Event ID — 2207 ......................................................................................................................................................104

Event ID — 2210 ...................................................................................................................................................... 104

Event ID — 2211 ....................................................................................................................................................... 105

Event ID — 2212 ...................................................................................................................................................... 105

Event ID — 2213 ...................................................................................................................................................... 105

Event ID — 2214 ...................................................................................................................................................... 106

Event ID — 2215 ...................................................................................................................................................... 106

Event ID — 2216 ...................................................................................................................................................... 106

Event ID — 2217 .......................................................................................................................................................107

Event ID — 2218 .......................................................................................................................................................107

Event ID — 2219 .......................................................................................................................................................107

Event ID — 2220 ......................................................................................................................................................108

Event ID — 2221 ...................................................................................................................................................... 108

Event ID — 2222 ......................................................................................................................................................108

Event ID — 2223 ......................................................................................................................................................109

Event ID — 2224 ......................................................................................................................................................109

Event ID — 2225 ......................................................................................................................................................109

Event ID — 2226 ...................................................................................................................................................... 110

Event ID — 2227 .......................................................................................................................................................110

Event ID — 2228 ...................................................................................................................................................... 110

Event ID — 2229 ....................................................................................................................................................... 111

Event ID — 2230 ....................................................................................................................................................... 111

Event ID — 2231 ........................................................................................................................................................ 111

Event ID — 2232 .......................................................................................................................................................112

Event ID — 2233 .......................................................................................................................................................112

Event ID — 2234 .......................................................................................................................................................112

Event ID — 2235 .......................................................................................................................................................113

Event ID — 2236 .......................................................................................................................................................113

Event ID — 2237 .......................................................................................................................................................113

Event ID — 2238 .......................................................................................................................................................114

Event ID — 2239 .......................................................................................................................................................114

Event ID — 2240 .......................................................................................................................................................114

Event ID — 2241 ....................................................................................................................................................... 115

Event ID — 2242 .......................................................................................................................................................115

Event ID — 2243 .......................................................................................................................................................115

Event ID — 2244 .......................................................................................................................................................116

Event ID — 2245 .......................................................................................................................................................116

Event ID — 2246 .......................................................................................................................................................116

Event ID — 2247 ....................................................................................................................................................... 117

Event ID — 2248 .......................................................................................................................................................117

Event ID — 2249 .......................................................................................................................................................117

Event ID — 2250 ...................................................................................................................................................... 118

Event ID — 2251 ....................................................................................................................................................... 118

Event ID — 2252 .......................................................................................................................................................118

Event ID — 2253 ...................................................................................................................................................... 119

Event ID — 2254 ...................................................................................................................................................... 119

9

10

Event ID — 2255 ...................................................................................................................................................... 119

Event ID — 2257 ......................................................................................................................................................120

Event ID — 2258 ......................................................................................................................................................120

Event ID — 2259 ......................................................................................................................................................120

Event ID — 2260 ...................................................................................................................................................... 121

Event ID — 2261 ....................................................................................................................................................... 121

Event ID — 2262 .......................................................................................................................................................121

Event ID — 2263 ......................................................................................................................................................122

Event ID — 2264 ......................................................................................................................................................122

Event ID — 2265 ......................................................................................................................................................122

Event ID — 2266 ......................................................................................................................................................123

Event ID — 2267 ...................................................................................................................................................... 123

Event ID — 2268 ......................................................................................................................................................123

Event ID — 2269 ......................................................................................................................................................124

Event ID — 2270 ...................................................................................................................................................... 124

Event ID — 2271 .......................................................................................................................................................124

Event ID — 2272 ...................................................................................................................................................... 125

Event ID — 2273 ...................................................................................................................................................... 125

Event ID — 2274 ...................................................................................................................................................... 125

Event ID — 2276 ...................................................................................................................................................... 126

Event ID — 2277 ...................................................................................................................................................... 126

Event ID — 2278 ...................................................................................................................................................... 126

Event ID — 2279 ...................................................................................................................................................... 127

Event ID — 2280 ...................................................................................................................................................... 127

Event ID — 2281 .......................................................................................................................................................128

Event ID — 2282 ......................................................................................................................................................128

Event ID — 2283 ......................................................................................................................................................128

Event ID — 2284 ......................................................................................................................................................129

Event ID — 2285 ......................................................................................................................................................129

Event ID — 2286 ......................................................................................................................................................129

Event ID — 2287 ...................................................................................................................................................... 130

Event ID — 2288 ......................................................................................................................................................130

Event ID — 2289 ......................................................................................................................................................130

Event ID — 2290 ...................................................................................................................................................... 131

Event ID — 2291 ....................................................................................................................................................... 131

Event ID — 2292 .......................................................................................................................................................131

Event ID — 2293 ......................................................................................................................................................132

Event ID — 2294 ......................................................................................................................................................132

Event ID — 2295 ......................................................................................................................................................132

Event ID — 2296 ......................................................................................................................................................133

Event ID — 2297 ...................................................................................................................................................... 133

Event ID — 2298 ......................................................................................................................................................133

Event ID — 2299 ......................................................................................................................................................134

Event ID — 2300 ......................................................................................................................................................134

Event ID — 2301 ...................................................................................................................................................... 134

Event ID — 2302 ......................................................................................................................................................135

Event ID — 2303 ......................................................................................................................................................135

Event ID — 2304 ......................................................................................................................................................135

Event ID — 2305 ......................................................................................................................................................136

Event ID — 2306 ......................................................................................................................................................136

Event ID — 2307 ......................................................................................................................................................136

Event ID — 2309 ...................................................................................................................................................... 137

Event ID — 2310 .......................................................................................................................................................137

Event ID — 2311 ....................................................................................................................................................... 138

Event ID — 2312 .......................................................................................................................................................138

Event Id — 2313 ....................................................................................................................................................... 138

Event ID — 2314 .......................................................................................................................................................139

Event Id — 2315 .......................................................................................................................................................139

Event ID — 2316 ...................................................................................................................................................... 139

Event ID — 2318 ...................................................................................................................................................... 140

Event ID — 2319 ...................................................................................................................................................... 140

Event Id — 2320 ...................................................................................................................................................... 140

Event ID — 2321 ....................................................................................................................................................... 141

Event ID — 2322 .......................................................................................................................................................141

Event ID — 2323 ......................................................................................................................................................142

Event ID — 2324 ...................................................................................................................................................... 142

Event ID — 2325 ......................................................................................................................................................142

Event ID — 2326 ......................................................................................................................................................143

Event ID — 2327 ...................................................................................................................................................... 143

Event ID — 2328 ......................................................................................................................................................143

Event ID — 2329 ......................................................................................................................................................144

Event ID — 2330 ......................................................................................................................................................144

Event ID — 2331 .......................................................................................................................................................144

Event ID — 2332 ......................................................................................................................................................145

Event ID — 2334 ......................................................................................................................................................145

Event ID — 2335 ......................................................................................................................................................145

Event ID — 2336 ......................................................................................................................................................146

Event ID — 2337 ...................................................................................................................................................... 146

Event ID — 2338 ...................................................................................................................................................... 147

Event ID — 2339 ...................................................................................................................................................... 147

Event ID — 2340 ...................................................................................................................................................... 147

Event ID — 2341 .......................................................................................................................................................148

Event ID — 2342 ......................................................................................................................................................148

Event ID — 2343 ......................................................................................................................................................148

Event ID — 2344 ......................................................................................................................................................149

Event ID — 2345 ......................................................................................................................................................149

Event ID — 2346 ......................................................................................................................................................149

Event ID — 2347 ......................................................................................................................................................150

Event ID — 2348 ......................................................................................................................................................150

Event ID — 2349 .......................................................................................................................................................151

11

12

Event ID — 2350 ...................................................................................................................................................... 151

Event ID — 2351 ....................................................................................................................................................... 151

Event ID — 2352 ......................................................................................................................................................152

Event ID — 2353 ......................................................................................................................................................152

Event ID — 2354 ......................................................................................................................................................152

Event ID — 2355 ......................................................................................................................................................153

Event ID — 2356 ......................................................................................................................................................153

Event ID — 2357 ......................................................................................................................................................153

Event ID — 2358 ......................................................................................................................................................154

Event ID — 2359 ......................................................................................................................................................154

Event ID — 2360 ......................................................................................................................................................154

Event ID — 2361 ...................................................................................................................................................... 155

Event ID — 2362 ......................................................................................................................................................155

Event ID — 2364 ......................................................................................................................................................155

Event ID — 2366 ......................................................................................................................................................156

Event ID — 2367 ......................................................................................................................................................156

Event ID — 2368 ......................................................................................................................................................156

Event ID — 2369 ......................................................................................................................................................157

Event ID — 2370 ...................................................................................................................................................... 157

Event ID — 2371 .......................................................................................................................................................157

Event ID — 2372 ...................................................................................................................................................... 158

Event ID — 2373 ...................................................................................................................................................... 158

Event ID — 2374 ...................................................................................................................................................... 158

Event ID — 2375 ......................................................................................................................................................159

Event ID — 2376 ......................................................................................................................................................159

Event ID — 2377 ...................................................................................................................................................... 159

Event ID — 2378 ......................................................................................................................................................160

Event ID — 2379 ......................................................................................................................................................160

Event ID — 2380 ......................................................................................................................................................160

Event ID — 2381 ....................................................................................................................................................... 161

Event ID — 2382 .......................................................................................................................................................161

Event ID — 2383 .......................................................................................................................................................161

Event ID — 2384 ......................................................................................................................................................162

Event Id — 2385 ...................................................................................................................................................... 162

Event ID — 2386 ......................................................................................................................................................162

Event ID — 2387 ...................................................................................................................................................... 163

Event ID — 2388 ......................................................................................................................................................163

Event ID — 2389 ......................................................................................................................................................163

Event ID — 2390 ......................................................................................................................................................164

Event ID — 2392 ......................................................................................................................................................164

Event ID — 2393 ......................................................................................................................................................164

Event ID — 2394 ......................................................................................................................................................165

Event ID — 2395 ......................................................................................................................................................165

Event ID — 2396 ......................................................................................................................................................165

Event ID — 2397 ......................................................................................................................................................166

Event ID — 2398 ......................................................................................................................................................166

Event ID — 2399 ......................................................................................................................................................166

Event ID — 2400 ......................................................................................................................................................167

Event ID — 2401 .......................................................................................................................................................167

Event ID — 2402 ...................................................................................................................................................... 167

Event ID — 2403 ......................................................................................................................................................168

Event ID — 2404 ......................................................................................................................................................168

Event ID — 2405 ......................................................................................................................................................168

Event ID — 2407 ......................................................................................................................................................169

Event ID — 2411 ....................................................................................................................................................... 169

Event ID — 2412 ...................................................................................................................................................... 169

Event ID — 2413 .......................................................................................................................................................170

Event ID — 2414 .......................................................................................................................................................170

Event ID — 2415 .......................................................................................................................................................170

Event ID — 2416 ....................................................................................................................................................... 171

Event ID — 2417 ........................................................................................................................................................171

Event ID — 2418 .......................................................................................................................................................172

Event ID — 2425 ...................................................................................................................................................... 172

Event ID — 2426 ...................................................................................................................................................... 172

Event ID — 2429 ...................................................................................................................................................... 173

Event ID — 2430 ...................................................................................................................................................... 173

Event ID — 2431 .......................................................................................................................................................173

Event ID — 2432 ...................................................................................................................................................... 174

Event ID — 2433 ...................................................................................................................................................... 174

Event ID — 2434 ...................................................................................................................................................... 174

Event ID — 2435 ......................................................................................................................................................175

Event ID — 2436 ......................................................................................................................................................175

Event ID — 2437 ...................................................................................................................................................... 175

Event ID — 2438 ...................................................................................................................................................... 176

Event ID — 2440 ......................................................................................................................................................176

Event ID — 2441 .......................................................................................................................................................176

Event ID — 2442 ...................................................................................................................................................... 177

Event ID — 2443 ...................................................................................................................................................... 177

Event ID — 2444 ...................................................................................................................................................... 177

Event ID — 2445 ...................................................................................................................................................... 178

Event ID — 2446 ...................................................................................................................................................... 178

Event ID — 2447 ...................................................................................................................................................... 178

Event ID — 2448 ...................................................................................................................................................... 179

Event ID — 2449 ......................................................................................................................................................179

Event ID — 2450 ......................................................................................................................................................179

Event ID — 2451 ...................................................................................................................................................... 180

Event ID — 2454 ......................................................................................................................................................180

Event ID — 2699 ......................................................................................................................................................180

Event ID — 2700 .......................................................................................................................................................181

Event ID — 2701 ....................................................................................................................................................... 181

13

Event ID — 2702 .......................................................................................................................................................181

Event ID — 2703 .......................................................................................................................................................181

Event ID — 2704 ...................................................................................................................................................... 182

Event ID — 2705 ......................................................................................................................................................182

Event ID — 2874 ...................................................................................................................................................... 182

Event ID — 2875 ...................................................................................................................................................... 183

Event ID — 2876 ...................................................................................................................................................... 183

Event ID — 2900 ......................................................................................................................................................183

Event ID — 2901 ...................................................................................................................................................... 183

Event ID — 2902 ......................................................................................................................................................184

Event ID — 2903 ......................................................................................................................................................184

Event ID — 2904 ......................................................................................................................................................184

Event ID — 2905 ..................................................................................................................................................... 185

Event ID — 2906 ..................................................................................................................................................... 185

Event ID — 2907 ......................................................................................................................................................185

Event ID — 2908 ..................................................................................................................................................... 185

Event ID — 2909 ..................................................................................................................................................... 186

Event ID — 2910 ...................................................................................................................................................... 186

Event ID — 2911 ....................................................................................................................................................... 186

Event ID — 2912 .......................................................................................................................................................187

Event ID — 2913 .......................................................................................................................................................187

Event ID — 2914 .......................................................................................................................................................187

Event ID — 2915 .......................................................................................................................................................187

Event ID — 2916 ...................................................................................................................................................... 188

Event ID — 2917 .......................................................................................................................................................188

Event ID — 2918 ...................................................................................................................................................... 188

Event ID — 2919 ...................................................................................................................................................... 189

Event ID — 2920 ......................................................................................................................................................189

Event ID — 2921 ...................................................................................................................................................... 189

Event ID — 2922 ......................................................................................................................................................189

Event ID — 2923 ......................................................................................................................................................190

Event ID — 2924 ......................................................................................................................................................190

Event ID — 2930 ......................................................................................................................................................190

Event ID — 2931 ....................................................................................................................................................... 191

Event ID — 2932 .......................................................................................................................................................191

Event ID — 2933 .......................................................................................................................................................191

4 System Event Log Messages for IPMI Systems........................................................... 192

Temperature Sensor Events ............................................................................................................................................ 192

Voltage Sensor Events ....................................................................................................................................................193

Fan Sensor Events ..........................................................................................................................................................194

Processor Status Events .................................................................................................................................................195

Power Supply Events ...................................................................................................................................................... 197

Memory ECC Events ..................................................................................................................................................... 200

BMC Watchdog Events ..................................................................................................................................................200

Memory Events .............................................................................................................................................................. 201

14

Hardware Log Sensor Events ......................................................................................................................................... 203

Drive Events ...................................................................................................................................................................203

Intrusion Events ............................................................................................................................................................. 204

BIOS Generated System Events .....................................................................................................................................205

POST Code Table ........................................................................................................................................................... 210

Operating System Generated System Events .................................................................................................................. 211

Cable Interconnect Events ..............................................................................................................................................212

Battery Events ................................................................................................................................................................ 212

Power And Performance Events ..................................................................................................................................... 213

Entity Presence Events ...................................................................................................................................................214

Miscellaneous Events ......................................................................................................................................................215

15

16

1

Introduction

OpenManage Server Administrator generates event messages stored primarily in the operating system or Server Administrator event logs and sometimes in Simple Network Management Protocol (SNMP) traps. This document describes the event messages that are created by Server Administrator version 8.5 and displayed in the Server Administrator alert log.

Server Administrator creates events in response to sensor status changes and other monitored parameters. The Server

Administrator event monitor uses these status change events to add descriptive messages to the operating system event log or the

Server Administrator alert log.

Each event message that Server Administrator adds to the alert log consists of a unique identifier called the event ID for a specific event source category and a descriptive message. The event message includes the severity, cause of the event, and other relevant information, such as the event location and the previous state of the monitored item.

The tables in this guide list all Server Administrator event IDs in numeric order. Each entry includes the description, severity level, and cause of the event ID. The message text in angle brackets (for example, (for example, <State>) describes the event-specific information provided by the Server Administrator.

New in this release

Message reference guide does not have any updates for this release.

Alert Message Change History

The following table describes the changes made to the Storage Management alerts from the previous release of Storage

Management to the current release.

Table 1. Alert Message Change History

Storage Management 4.4

Product Versions to which changes apply Storage Management 4.4.0

Server Administrator 7.4.0

1015, 1016 New Alerts

Deleted Alerts 1250, 1253, 1255, 1350, 1355, 1450, 1451, 1452, 1453, 1454, 1455, 1500, 1501,

1502, 1503, 1504, 1505, 1600, 1605

Modified Alerts

Storage Management 4.3

Product Versions to which changes apply

None

Storage Management 4.3.0

Server Administrator 7.3.0

New Alerts

Deleted Alerts

Modified Alerts

Storage Management 4.2

Product Versions to which changes apply

New Alerts

Deleted Alerts

Modified Alerts

Storage Management 4.1

Product Versions to which changes apply

New Alerts

Deleted Alerts

Modified Alerts

Storage Management 4.0

Product Versions to which changes apply

New Alerts

Deleted Alerts

Modified Alerts

Storage Management 3.5

Product Versions to which changes apply

New Alerts

Deleted Alerts

Modified Alerts

Storage Management 3.4

Product Versions to which changes apply

New Alerts

Deleted Alerts

2699, 2700, 2701, 2702, 2703, 2704, 2705, 2874, 2875, 2876, 2900, 2901,

2902, 2903, 2904, 2905, 2906, 2907, 2908, 2909, 2910, 2911, 2912, 2913,

2914, 2915, 2916, 2917, 2918, 2919, 2920, 2921, 2922, 2923, 2924, 2930,

2931, 2932, 2933

None

None

Storage Management 4.2.0

Server Administrator 7.2.0

2433, 2434, 2435, 2436, 2437, 2438

None

2359

Storage Management 4.1.0

Server Administrator 7.1.0

2432

None

None

Storage Management 4.0.0

Server Administrator 7.0.0

2425, 2426, 2429, 2430, 2431

None

None

Storage Management 3.5.0

Server Administrator 6.5.0

None

None

2388, 2347, 2081

Storage Management 3.4.0

Server Administrator 6.4.0

2405, 2406, 2407, 2408, 2409, 2410, 2411, 2412, 2413, 2414, 2415, 2416, 2417,

2418

NOTE: The CacheCade feature is available from calendar year 2011.

None

17

Modified Alerts

Storage Management 3.3

Product Versions to which changes apply

None

New Alerts

Deleted Alerts

Modified Alerts

Storage Management 3.2

Product Versions to which changes apply

Storage Management 3.3.0

Server Administrator 6.3.0

2394, 2395, 2396, 2397, 2398, 2399, 2400, 2401, 2402, 2403, 2404

None

Alert severity changed for 1151 and 1351

New Alerts

Deleted Alerts

Modified Alerts

Storage Management 3.2.0

Server Administrator 6.2.0

2387, 2388, 2389, 2390, 2392, 2393

None

None

Messages Not Described in This Guide

This guide describes only event messages logged by Server Administrator and Storage Management that are displayed in the Server

Administrator alert log. For information on other messages generated by your system, see one of the following sources:

• The Installation and Troubleshooting Guide or Hardware Owner's Manual shipped with your system

• Operating system documentation

• Application program documentation

Understanding Event Messages

Add your section content here.This section describes the various types of event messages generated by the Server Administrator.

When an event occurs on your system, Server Administrator sends information about one of the following event types to the systems management console:

Table 2. Understanding Event Messages

Icon Alert Severity

OK /Normal /

Informational

Component Status

An event that describes the successful operation of a unit.

The alert is provided for informational purposes and does not indicate an error condition. For example, the alert may indicate the normal start or stop of an operation, such as power supply or a sensor reading returning to normal.

Warning / Non-critical An event that is not necessarily significant, but may indicate a possible future problem. For example, a Warning/Noncritical alert may indicate that a component (such as a temperature probe in an enclosure) has crossed a warning threshold.

Critical / Failure / Error A significant event that indicates actual or imminent loss of data or loss of function. For example, crossing a failure threshold or a hardware failure such as an array disk.

Server Administrator generates events based on status changes in the following sensors:

18

• Temperature Sensor — Helps protect critical components by alerting the systems management console when temperatures become too high inside a chassis; also monitors the temperature in a variety of locations in the chassis and in attached system(s).

• Fan Sensor — Monitors fans in various locations in the chassis and in attached system(s).

• Voltage Sensor — Monitors voltages across critical components in various chassis locations and in attached system(s).

• Current Sensor — Monitors the current (or amperage) output from the power supply (or supplies) in the chassis and in attached system(s).

• Chassis Intrusion Sensor — Monitors intrusion into the chassis and attached system(s).

• Redundancy Unit Sensor — Monitors redundant units (critical units such as fans, AC power cords, or power supplies) within the chassis; also monitors the chassis and attached system(s). For example, redundancy allows a second or nth fan to keep the chassis components at a safe temperature when another fan has failed. Redundancy is normal when the intended number of critical components are operating. Redundancy is degraded when a component fails, but others are still operating. Redundancy is lost when there is one less critical redundancy device than required.

• Power Supply Sensor — Monitors power supplies in the chassis and in attached system(s).

• Memory Prefailure Sensor — Monitors memory modules by counting the number of Error Correction Code (ECC) memory corrections.

• Fan Enclosure Sensor — Monitors protective fan enclosures by detecting their removal from and insertion into the system, and by measuring how long a fan enclosure is absent from the chassis. This sensor monitors the chassis and in attached system(s).

• AC Power Cord Sensor — Monitors the presence of AC power for an AC power cord.

• Hardware Log Sensor — Monitors the size of a hardware log.

• Processor Sensor — Monitors the processor status in the system.

• Pluggable Device Sensor — Monitors the addition, removal, or configuration errors for some pluggable devices, such as memory cards.

• Battery Sensor — Monitors the status of one or more batteries in the system.

• SD Card Device Sensor — Monitors instrumented Secure Digital (SD) card devices in the system.

Sample Event Message Text

The following example shows the format of the event messages logged by Server Administrator.

EventID: 1000

Source: Server Administrator

Category: Instrumentation Service

Type: Information

Date and Time: Mon Oct 21 10:38:00 2002

Computer: <computer name>

Description: Server Administrator starting

Data: Bytes in Hex

Viewing Alerts and Event Messages

An event log is used to record information about important events.

Server Administrator generates alerts that are added to the operating system event log and to the Server Administrator alert log. To view these alerts in Server Administrator:

1.

Select the System object in the tree view.

2.

Select the Logs tab.

3.

Select the Alert tab.

19

You can also view the event log using your operating system’s event viewer. Each operating system’s event viewer accesses the applicable operating system event log.

The location of the event log file depends on the operating system you are using.

• On systems running the Microsoft Windows operating systems, event messages are logged in the operating system event log and the Server Administrator event log.

NOTE: The Server Administrator event log file is named dcsys32.xml and is located in the <install_path>\omsa\log directory. The default install_path is C:\Program Files\Dell\SysMgt.

• On systems running the Red Hat Enterprise Linux, SUSE Linux Enterprise Server, Citrix XenServer, VMware ESX, and VMware

ESXi operating systems, the event messages are logged in the operating system log file and the Server Administrator event log.

NOTE: The default name of the operating system log file is /var/log/messages, and you can view the operating system log file using a text editor such as vi or emacs. The Server Administrator event log file is named dcsys<xx>.xml,where xx is either 32 or 64 bit depending on the operating system. In the Red Hat Enterprise Linux,

SUSE Linux Enterprise Server, Citrix XenServer and VMware ESX operating systems, the Server Administrator event log file is located in the /opt/dell/srvadmin/var/log/openmanage directory. In the VMware ESXi operating system, the

Server Administrator event log file is located in the /etc/cim/dell/srvadmin/log/openmanage directory.

Logging Messages to a Unicode Text File

Logging messages to a Unicode text file is optional. By default, the feature is disabled in the Server Administrator. To enable this feature, modify the Event Manager section of the dcemdy <xx>.ini configuration file where xx is 32 or 64 bit depending on the operating system, as follows:

• On systems running Microsoft Windows operating systems, you can locate the configuration file in the <install_path> \dataeng

\ini directory and set the property UnitextLog.enabled=true. The default install_path is C:\Program Files\Dell\SysMgt.

Restart the DSM SA Event Manager service to enable the setting. The Server Administrator Unicode text event log file is named dcsys32.log and is located in the <install_path>\omsa\log directory.

• On systems running the Red Hat Enterprise Linux, SUSE Linux Enterprise Server, Citrix XenServer and VMware ESX operating systems, you can locate the configuration file in the /opt/dell/srvadmin/etc/ srvadmin-deng/ini directory and set the property

UnitextLog.enabled=true. Run the /etc/init.d/dataeng restart command to restart the Server Administrator Event Manager service and enable the setting. This also restarts the Server Administrator Data Manager and SNMP services. The Server

Administrator Unicode text event log file is named dcsys <xx>.log where xx is 32 or 64 bit depending on the operating system and is located in the /opt/dell/srvadmin/var/log/ openmanage directory.

• On systems running the in ESXi operating system the dcemdy32.ini file is located under /etc/cim/dell/srvadmin/srvadmindeng/ini/ and the dcsys <xx>.log where xx is 32 or 64 bit depending on the operating system and is located under /etc/cim/ dell/srvadmin/log/openmanage/

The following sub-sections explain how to launch the Windows Server 2008, Red Hat Enterprise Linux, SUSE Linux Enterprise

Server, VMware ESX, and VMware ESXi event viewers.

Viewing Events in Microsoft Windows Server 2008

1.

Click the Start button, point to Settings, and click Control Panel.

2.

Double-click Administrative Tools, and then double-click Event Viewer.

3.

In the Event Viewer window, click the Tree tab and then click System Log.

The System Log window displays a list of recently logged events.

4.

To view the details of an event, double-click one of the event items.

NOTE: You can also look up the dcsys <xx>.xml file, in the <install_path> \omsa\log directory, to view the separate event log file, where the default install_path is C:\Program Files\Dell\SysMgt and xx is 32 or 64 depending on the operating system that is installed.

Viewing Events in Red Hat Enterprise Linux and SUSE Linux Enterprise Server

1.

Log in as root.

2.

Use a text editor such as vi or emacs to view the file named /var/log/messages.

20

The following example shows the Red Hat Enterprise Linux and SUSE Linux Enterprise Server message log, /var/log/messages. The text in boldface type indicates the message text.

NOTE: These messages are typically displayed as one long line. In the following example, the message is displayed using line breaks to help you see the message text more clearly.

Feb 6 14:20:51 server01 Server Administrator: Instrumentation Service EventID: 1000

Server Administrator starting

Feb 6 14:20:51 server01 Server Administrator: Instrumentation Service EventID: 1001

Server Administrator startup complete

Feb 6 14:21:21 server01 Server Administrator: Instrumentation Service EventID: 1254Chassis intrusion detected Sensor location: Main chassis intrusion Chassis location: Main System

Chassis Previous state was: OK (Normal) Chassis intrusion state: Open

Feb 6 14:21:51 server01 Server Administrator: Instrumentation Service EventID: 1252Chassis intrusion returned to normal Sensor location: Main chassis intrusion Chassis location: Main

System Chassis Previous state was: Critical (Failed) Chassis intrusion state: Closed

Viewing Events in VMware ESX/ESXi

1.

Log in to the system running VMware ESX/ESXi with VMware vSphere Client.

2.

Click View → Administration → System Logs.

3.

Select Server Log → /var/log/messages entry from the drop-down list.

Viewing the Event Information

The event log for each operating system contains some or all of the following information:

• Date — The date the event occurred.

• Time — The local time the event occurred.

• Type — A classification of the event severity: Information, Warning, or Error.

• User — The name of the user on whose behalf the event occurred.

• Computer — The name of the system where the event occurred.

• Source — The software that logged the event.

• Category — The classification of the event by the event source.

• Event ID — The number identifying the particular event type.

• Description — A description of the event. The format and contents of the event description vary, depending on the event type.

Understanding the Event Description

Table below lists in alphabetical order each line item that may appear in the event description.

Description Line

Item

Explanation

Description Line

Item

Explanation

Action performed was: <Action>

Specifies the action that was performed, for example: Action performed was: Power cycle

Action requested was: <Action>

Specifies the action that was requested, for example: Action requested was: Reboot, shutdown OS first

21

Description Line

Item

Explanation

Description Line

Item

Explanation

Description Line

Item

Explanation

Description Line

Item

Explanation

Description Line

Item

Explanation

Description Line

Item

Explanation

Description Line

Item

Explanation

Description Line

Item

Explanation

Description Line

Item

Explanation

Description Line

Item

Explanation

Additional Details: <Additional details for the event>

Specifies additional details available for the hot plug event, for example: Memory device: DIMM1_A

Serial number: FFFF30B1

<Additional power supply status information>

Specifies information pertaining to the event, for example: Power supply input AC is off,

Power supply POK (power OK) signal is not normal, Power supply is turned off

Chassis intrusion state: <Intrusion state>

Specifies whether the chassis intrusion state is Open or Closed. For example: Chassis intrusion state: Open

Chassis location: <Name of chassis>

Specifies name of the chassis that generated the message, for example: Chassis location: Main

System Chassis

Configuration error type: <type of configuration error>

Specifies the type of configuration error that occurred, for example: Configuration error type:

Revision mismatch

Current sensor value (in Amps): <Reading>

Specifies the current sensor value in amps, for example: Current sensor value (in Amps):

7.853

Date and time of action: <Date and time>

Specifies the date and time the action was performed, for example: Date and time of action: Sat

Jun 12 16:20:33 2004

Device location: <Location in chassis>

Specifies the location of the device in the specified chassis, for example: Device location: Memory

Card A

Discrete current state: <State>

Specifies the state of the current sensor, for example: Discrete current state: Good

Discrete temperature state: <State>

Specifies the state of the temperature sensor, for example: Discrete temperature state: Good

22

Description Line

Item

Explanation

Description Line

Item

Explanation

Description Line

Item

Explanation

Description Line

Item

Explanation

Description Line

Item

Explanation

Description Line

Item

Explanation

Description Line

Item

Explanation

Description Line

Item

Explanation

Description Line

Item

Explanation

Description Line

Item

Explanation

Discrete voltage state: <State>

Specifies the state of the voltage sensor, for example: Discrete voltage state: Good

Fan sensor value: <Reading>

Specifies the fan speed in revolutions per minute (RPM) or On/Off, for example: Fan sensor value

(in RPM): 2600

Fan sensor value: Off

Log type: <Log type>

Specifies the type of hardware log, for example: Log type: ESM

Memory device bank location: <Bank name in chassis>

Specifies the name of the memory bank in the system that generated the message, for example: Memory device bank location: Bank_1

Memory device location: <Device name in chassis>

Specifies the location of the memory module in the chassis, for example: Memory device location:

DIMM_A

Number of devices required for full redundancy: <Number>

Specifies the number of power supply or cooling devices required to achieve full redundancy, for example:

Number of devices required for full redundancy: 4

Peak value (in Watts):<Reading>

Specifies the peak value in Watts, for example: Peak value (in Watts): 1.693

Possible memory module event cause: <list of causes>

Specifies a list of possible causes for the memory module event, for example: Possible memory module event cause:

Single bit warning error rate exceeded

Single bit error logging disabled

Power Supply type: <type of power supply>

Specifies the type of power supply, for example: Power Supply type: VRM

Previous redundancy state was: <State>

Specifies the status of the previous redundancy message, for example: Previous redundancy state was: Lost

23

Description Line

Item

Explanation

Description Line

Item

Explanation

Description Line

Item

Explanation

Description Line

Item

Explanation

Description Line

Item

Explanation

Description Line

Item

Explanation

Description Line

Item

Explanation

Description Line

Item

Explanation

Previous state was:<State>

Specifies the previous state of the sensor, for example: Previous state was: OK (Normal)

Processor sensor status: <status>

Specifies the status of the processor sensor, for example: Processor sensor status:

Configuration error

Redundancy unit: <Redundancy location in chassis>

Specifies the location of the redundant power supply or cooling unit in the chassis, for example:

Redundancy unit: Fan Enclosure

SD card device type: <Type of SD card device>

Specifies the type of SD card device, for example: SD card device type: Hypervisor

SD card state: <State of SD card>

Specifies the state of the SD card, for example: SD card state: Present, Active

Sensor location: <Location in chassis>

Specifies the location of the sensor in the specified chassis, for example: Sensor location: CPU1

Temperature sensor value: <Reading>

Specifies the temperature in degrees Celsius, for example: Temperature sensor value (in degrees Celsius): 30

Voltage sensor value (in Volts):<Reading>

Specifies the voltage sensor value in volts, for example: Voltage sensor value (in Volts):

1.693

24

Server Management Messages

The following tables lists in numerical order each event ID and its corresponding description, along with its severity and cause.

NOTE: For corrective actions, see the appropriate documentation.

2

Server Administrator General Messages

The messages below indicate that certain alert systems are up and working.

Event ID — 0000

Description

Severity

Cause

Log was cleared

Information

User cleared the log from Server Administrator.

This operation does not clear the operating system event log. Therefore, this event is not logged in the operating system event log. This is logged in the System Administrator alert log.

Event ID — 0001

Description

Severity

Cause

Log backup created

Information

The log was full, copied to backup, and cleared.

Event ID — 1000

Description

Severity

Cause

Server Administrator starting

Information

Server Administrator is beginning to initialize.

Event ID — 1001

Description

Severity

Cause

Server Administrator startup complete

Information

Server Administrator completed initialization.

Event ID — 1002

Description

Severity

A system BIOS update has been scheduled for the next reboot

Information

25

Cause The user has chosen to update the flash basic input/output system (BIOS).

Event ID – 1003

Description

Severity

Cause

A previously scheduled system BIOS update has been canceled

Information

The user decides to cancel the flash BIOS update, or an error occurs during the flash.

Event ID — 1004

Description

Severity

Cause

Thermal shutdown protection has been initiated

Error

This message is generated when a system is configured for thermal shutdown due to an error event. If a temperature sensor reading exceeds the error threshold for which the system is configured, the operating system shuts down and the system powers off. This event may also be initiated on certain systems when a fan enclosure is removed from the system for an extended period of time.

Event ID — 1005

Description

Severity

Cause

SMBIOS data is absent

Error

The system does not contain the required systems management BIOS version 2.2 or higher, or the BIOS is corrupted.

Event ID — 1006

Description Automatic System Recovery (ASR) action was performed Action performed was:

<Action>

Date and time of action:<Date and time>

Severity

Cause

Error

This message is generated when an automatic system recovery action is performed due to a hung operating system. The action performed and the time of action is provided.

Event ID — 1007

Description

Severity

Cause

User initiated host system control action Action requested was: <Action>

Information

User requested a host system control action to reboot, power off, or power cycle the system. Alternatively, the user had indicated protective measures to be initiated in the event of a thermal shutdown.

Event ID — 1008

Description

Severity

Cause

Systems Management Data Manager Started

Information

Systems Management Data Manager services were started.

26

Event ID — 1009

Description

Severity

Cause

Systems Management Data Manager Stopped

Information

Systems Management Data Manager services were stopped.

Event ID — 1011

Description

Severity

Cause

RCI table is corrupt

Error

This message is generated when the BIOS Remote Configuration Interface (RCI) table is corrupted or cannot be read by the systems management software.

Event ID — 1012

Description

Severity

Cause

IPMI Status Interface: <the IPMI interface being used>, <additional information if available and applicable >

Information

This message is generated to indicate the Intelligent Platform Management Interface (IPMI) status of the system.

Additional information, when available, includes Baseboard Management Controller (BMC) not present, BMC not responding, System Event Log (SEL) not present, and SEL Data Record (SDR) not present.

Event ID — 1013

Description

Severity

Cause

System Peak Power detected new peak value Peak value (in Watts): <Reading>

Information

The system peak power sensor detected a new peak value in power consumption. The new peak value in

Watts is provided.

Event ID — 1014

Description System software event: <Description>

Date and time of action: <Date and time>

Severity

Cause

Warning

This event is generated when the systems management agent detects a critical system software generated event in the system event log which could have been resolved.

Event ID — 1019

Description Alert generated from unmonitored sensors

Severity Warning

27

Event ID — 1016

Description

Severity

Cause

Server Based Management Mode is disabled

Information

This event is generated when the server-based management mode is disabled.

Temperature Sensor Messages

The temperature sensors listed help protect critical components by alerting the systems management console when temperatures become too high inside a chassis. The temperature sensor messages use more variables: sensor location, chassis location, previous state, and temperature sensor value or state.

Event ID — 1050

Description Temperature sensor has failed Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

If sensor type is not discrete:

Temperature sensor value (in degrees Celsius): <Reading>

If sensor type is discrete:

Discrete temperature state: <State>

Severity

Cause

Error

A temperature sensor on the backplane board, system board, or the carrier in the specified system failed.

The sensor location, chassis location, previous state, and temperature sensor value are provided.

Event ID — 1051

Description Temperature sensor value unknown Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

If sensor type is not discrete:

Temperature sensor value (in degrees Celsius): <Reading>

If sensor type is discrete:

Discrete temperature state: <State>

Severity

Cause

Warning

A temperature sensor on the backplane board, system board, or drive carrier in the specified system could not obtain a reading. The sensor location, chassis location, previous state, and a nominal temperature sensor value information is provided.

28

Event ID — 1052

Description Temperature sensor returned to a normal value Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

If sensor type is not discrete:

Temperature sensor value (in degrees Celsius): <Reading>

If sensor type is discrete:

Discrete temperature state: <State>

Severity

Cause

Information

A temperature sensor on the backplane board, system board, or drive carrier in the specified system returned to a valid range after crossing a failure threshold. The sensor location, chassis location, previous state, and temperature sensor value are provided.

Event ID — 1053

Description Temperature sensor detected a warning value Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

If sensor type is not discrete:

Temperature sensor value (in degrees Celsius): <Reading>

If sensor type is discrete:

Discrete temperature state: <State>

Severity

Cause

Warning

A temperature sensor on the backplane board, system board, CPU, or drive carrier in the specified system exceeded its warning threshold. The sensor location, chassis location, previous state, and temperature sensor value are provided.

Event ID — 1054

Description Temperature sensor detected a failure value Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

If sensor type is not discrete:

29

Temperature sensor value (in degrees Celsius): <Reading>

If sensor type is discrete:

Discrete temperature state: <State>

Severity

Cause

Error

A temperature sensor on the backplane board, system board, or drive carrier in the specified system exceeded its failure threshold. The sensor location, chassis location, previous state, and temperature sensor value are provided.

Event ID — 1055

Description Temperature sensor detected a non-recoverable value Sensor location:

<Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

If sensor type is not discrete:

Temperature sensor value (in degrees Celsius): <Reading>

If sensor type is discrete:

Discrete temperature state: <State>

Severity

Cause

Error

A temperature sensor on the backplane board, system board, or drive carrier in the specified system detected an error from which it cannot recover. The sensor location, chassis location, previous state, and temperature sensor value information is provided.

Cooling Device Messages

The cooling device sensors listed monitor how well a fan is functioning. Cooling device messages provide status and warning information for fans in a particular chassis.

Event ID — 1100

Description Fan sensor has failed Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

Fan sensor value: <Reading>

Severity

Cause

Error

A fan sensor in the specified system is not functioning. The sensor location, chassis location, previous state, and fan sensor value information is provided.

30

Event ID — 1101

Description Fan sensor value unknown Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

Fan sensor value: <Reading>

Severity

Cause

Error

A fan sensor in the specified system could not obtain a reading. The sensor location, chassis location, previous state, and a nominal fan sensor value information is provided.

Event ID — 1102

Description Fan sensor returned to a normal value Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

Fan sensor value: <Reading>

Severity

Cause

Information

A fan sensor reading on the specified system returned to a valid range after crossing a warning threshold.

The sensor location, chassis location, previous state, and fan sensor value information is provided.

Event ID — 1103

Description Fan sensor detected a warning value Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

Fan sensor value: <Reading>

Severity

Cause

Warning

A fan sensor reading in the specified system exceeded a warning threshold. The sensor location, chassis location, previous state, and fan sensor value information is provided.

Event ID — 1104

Description Fan sensor detected a failure value Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

Fan sensor value: <Reading>

Severity Error

31

Cause A fan sensor in the specified system detected the failure of one or more fans. The sensor location, chassis location, previous state, and fan sensor value information is provided.

Event ID — 1105

Description Fan sensor detected a non-recoverable value Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

Fan sensor value: <Reading>

Severity

Cause

Error

A fan sensor detected an error from which it cannot recover. The sensor location, chassis location, previous state, and fan sensor value information is provided.

Voltage Sensor Messages

The voltage sensors listed monitor the number of volts across critical components. Voltage sensor messages provide status and warning information for voltage sensors in a particular chassis.

Event ID — 1150

Description

Voltage sensor has failed Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

If sensor type is not discrete:

Voltage sensor value (in Volts): <Reading>

If sensor type is discrete:

Discrete voltage state: <State>

Severity

Cause

Error

A voltage sensor in the specified system failed. The sensor location, chassis location, previous state, and voltage sensor value information is provided.

Event ID — 1151

Description Voltage sensor value unknown Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

If sensor type is not discrete:

Voltage sensor value (in Volts): <Reading>

32

If sensor type is discrete:

Discrete voltage state: <State>

Severity

Cause

Warning

A voltage sensor in the specified system could not obtain a reading. The sensor location, chassis location, previous state, and a nominal voltage sensor value are provided.

Event ID — 1152

Description Voltage sensor returned to a normal value Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

If sensor type is not discrete:

Voltage sensor value (in Volts): <Reading>

If sensor type is discrete:

Discrete voltage state: <State>

Severity

Cause

Information

A voltage sensor in the specified system returned to a valid range after crossing a failure threshold. The sensor location, chassis location, previous state, and voltage sensor value information is provided.

Event ID — 1153

Description Voltage sensor detected a warning value Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

If sensor type is not discrete:

Voltage sensor value (in Volts): <Reading>

If sensor type is discrete:

Discrete voltage state: <State>

Severity

Cause

Warning

A voltage sensor in the specified system exceeded its warning threshold. The sensor location, chassis location, previous state, and voltage sensor value information is provided.

Event ID — 1154

Description

Voltage sensor detected a failure value Sensor location: <Location in chassis>

33

Chassis location: <Name of chassis>

Previous state was: <State>

If sensor type is not discrete:

Voltage sensor value (in Volts): <Reading>

If sensor type is discrete:

Discrete voltage state: <State>

Severity

Cause

Error

A voltage sensor in the specified system exceeded its failure threshold. The sensor location, chassis location, previous state, and voltage sensor value information is provided.

Event ID — 1155

Description Voltage sensor detected a non-recoverable value Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

If sensor type is not discrete:

Voltage sensor value (in Volts): <Reading>

If sensor type is discrete:

Discrete voltage state: <State>

Severity

Cause

Error

A voltage sensor in the specified system detected an error from which it cannot recover. The sensor location, chassis location, previous state, and voltage sensor value information is provided.

Current Sensor Messages

The current sensors listed measure the amount of current (in amperes) that is traversing critical components. Current sensor messages provide status and warning information for current sensors in a particular chassis.

Event ID – 1200

Description

Current sensor has failed Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

If sensor type is not discrete:

Current sensor value (in Amps): <Reading> OR

34

Current sensor value (in Watts): <Reading>

If sensor type is discrete:

Discrete voltage state: <State>

Severity

Cause

Error

A current sensor in the specified system failed. The sensor location, chassis location, previous state, and current sensor value are provided.

Event ID — 1201

Description Current sensor value unknown Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

If sensor type is not discrete:

Current sensor value (in Amps): <Reading> OR

Current sensor value (in Watts): <Reading>

If sensor type is discrete:

Discrete voltage state: <State>

Severity

Cause

Warning

A current sensor in the specified system could not obtain a reading. The sensor location, chassis location, previous state, and a nominal current sensor value information is provided.

Event ID — 1202

Description

Current sensor returned to a normal value Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

If sensor type is not discrete:

Current sensor value (in Amps): <Reading> OR

Current sensor value (in Watts): <Reading>

If sensor type is discrete:

Discrete voltage state: <State>

Severity

Cause

Information

A current sensor in the specified system returned to a valid range after crossing a failure threshold. The sensor location, chassis location, previous state, and current sensor value information is provided.

35

Event ID — 1203

Description

Current sensor detected a warning value Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

If sensor type is not discrete:

Current sensor value (in Amps): <Reading> OR

Current sensor value (in Watts): <Reading>

If sensor type is discrete:

Discrete voltage state: <State>

Severity

Cause

Warning

A current sensor in the specified system exceeded its warning threshold. The sensor location, chassis location, previous state, and current sensor value are provided.

Event ID — 1204

Description

Current sensor detected a failure value Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

If sensor type is not discrete:

Current sensor value (in Amps): <Reading> OR

Current sensor value (in Watts): <Reading>

If sensor type is discrete:

Discrete voltage state: <State>

Severity

Cause

Error

A current sensor in the specified system exceeded its failure threshold. The sensor location, chassis location, previous state, and current sensor value are provided.

Event ID — 1205

Description Current sensor detected a non-recoverable value Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

36

Severity

Cause

Previous state was: <State>

If sensor type is not discrete:

Current sensor value (in Amps): <Reading> OR

Current sensor value (in Watts): <Reading>

If sensor type is discrete:

Discrete voltage state: <State>

Error

A current sensor in the specified system detected an error from which it cannot recover. The sensor location, chassis location, previous state, and current sensor value are provided.

Chassis Intrusion Messages

The chassis intrusion messages listed are a security measure. Chassis intrusion means that someone is opening the cover to a system’s chassis. Alerts are sent to prevent unauthorized removal of parts from a chassis.

Event ID — 1251

Description Chassis intrusion sensor value unknown Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

Chassis intrusion state: <Intrusion state>

Severity

Cause

Warning

A chassis intrusion sensor in the specified system could not obtain a reading. The sensor location, chassis location, previous state, and chassis intrusion state are provided.

Event ID — 1252

Description

Chassis intrusion returned to normal Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

Chassis intrusion state: <Intrusion state>

Severity

Cause

Information

A chassis intrusion sensor in the specified system detected that a cover was opened while the system was operating but has since been replaced. The sensor location, chassis location, previous state, and chassis intrusion state information is provided.

37

Event ID — 1254

Description

Chassis intrusion detected Sensor location: <Location in chassis>

Chassis location: <Name of chassis>

Previous state was: <State>

Chassis intrusion state: <Intrusion state>

Severity

Cause

Critical

A chassis intrusion sensor in the specified system detected that the system cover was opened while the system was operating. The sensor location, chassis location, previous state, and chassis intrusion state information is provided.

Redundancy Unit Messages

Redundancy means that a system chassis has more than one of certain critical components. Fans and power supplies, for example, are so important for preventing damage or disruption of a computer system that a chassis may have “extra” fans or power supplies installed. Redundancy allows a second or nth fan to keep the chassis components at a safe temperature when the primary fan has failed. Redundancy is normal when the intended number of critical components are operating. Redundancy is degraded when a component fails but others are still operating. Redundancy is lost when the number of components functioning falls below the redundancy threshold. Lists the redundancy unit messages.

The number of devices required for full redundancy is provided as part of the message, when applicable, for the redundancy unit and the platform. For details on redundancy computation, see the respective platform documentation.

Event ID — 1300

Description Redundancy sensor has failed Redundancy unit: <Redundancy Location in chassis>

Chassis location: <Name of chassis>

Previous redundancy state was: <State>

Severity

Cause

Error

A redundancy sensor in the specified system failed. The redundancy unit location, chassis location, previous redundancy state, and the number of devices required for full redundancy are provided.

Event ID — 1301

Description Redundancy sensor value unknown Redundancy unit: <Redundancy Location in chassis>

Chassis location: <Name of chassis>

Previous redundancy state was: <State>

Severity Warning

38

Cause A redundancy sensor in the specified system could not obtain a reading. The redundancy unit location, chassis location, previous redundancy state, and the number of devices required for full redundancy are provided.

Event ID — 1302

Description Redundancy not applicable Redundancy unit: <Redundancy Location in chassis>

Chassis location: <Name of chassis>

Previous redundancy state was: <State>

Severity

Cause

Information

A redundancy sensor in the specified system detected that a unit was not redundant. The redundancy location, chassis location, previous redundancy state, and the number of devices required for full redundancy information is provided.

Event ID — 1303

Description Redundancy is offline Redundancy unit: <Redundancy Location in chassis>

Chassis location: <Name of chassis>

Previous redundancy state was: <State>

Severity

Cause

Information

A redundancy sensor in the specified system detected that a redundant unit is offline. The redundancy unit location, chassis location, previous redundancy state, and the number of devices required for full redundancy information is provided.

Event ID — 1304

Description Redundancy regained Redundancy unit: <Redundancy Location in chassis>

Chassis location: <Name of chassis>

Previous redundancy state was: <State>

Severity

Cause

Information

A redundancy sensor in the specified system detected that a “lost” redundancy device has been reconnected or replaced; full redundancy is in effect. The redundancy unit location, chassis location, previous redundancy state, and the number of devices required for full redundancy information is provided.

Event ID — 1305

Description Redundancy degraded Redundancy unit: <Redundancy Location in chassis>

Chassis location: <Name of chassis>

Previous redundancy state was: <State>

Severity Warning

39

Cause A redundancy sensor in the specified system detected that one of the components of the redundancy unit has failed but the unit is still redundant. The redundancy unit location, chassis location, previous redundancy state, and the number of devices required for full redundancy information is provided.

Event ID — 1306

Description Redundancy lost Redundancy unit: <Redundancy Location in chassis>

Chassis location: <Name of chassis>

Previous redundancy state was: <State>

Severity

Cause

Error

A redundancy sensor in the specified system detected that one of the components in the redundant unit has been disconnected, has failed, or is not present. The redundancy unit location, chassis location, previous redundancy state, and the number of devices required for full redundancy are provided.

Power Supply Messages

The power supply sensors monitor how well a power supply is functioning. The power supply messages listed provides status and warning information for power supplies present in a particular chassis.

Event ID — 1351

Description Power supply sensor value unknown Sensor Location: <Location in chassis>

Chassis location: <Name of chassis>

Previous redundancy state was: <State>

Power Supply type: <type of power supply>

<Additional power supply status information>

If in configuration error state:

Configuration error type:<type of configuration error>

Severity

Cause

Warning

A power supply sensor in the specified system could not obtain a reading. The sensor location, chassis location, previous state, power supply type, additional power supply status, and configuration error type information are provided.

Event ID — 1352

Description Power supply returned to normal Sensor Location: <Location in chassis>

Chassis location: <Name of chassis>

Previous redundancy state was: <State>

Power Supply type: <type of power supply>

<Additional power supply status information>

40

If in configuration error state:

Configuration error type:<type of configuration error>

Severity

Cause

Information

A power supply has been reconnected or replaced. The sensor location, chassis location, previous state, power supply type, additional power supply status, and configuration error type information are provided.

Event ID — 1353

Description Power supply detected a warning Sensor Location: <Location in chassis>

Chassis location: <Name of chassis>

Previous redundancy state was: <State>

Power Supply type: <type of power supply>

<Additional power supply status information>

If in configuration error state:

Configuration error type:<type of configuration error>

Severity

Cause

Warning

A power supply sensor reading in the specified system exceeded a user-definable warning threshold. The sensor location, chassis location, previous state, power supply type, additional power supply status, and configuration error type information are provided.

Event ID — 1354

Description Power supply detected a failure Sensor Location: <Location in chassis>

Chassis location: <Name of chassis>

Previous redundancy state was: <State>

Power Supply type: <type of power supply>

<Additional power supply status information>

If in configuration error state:

Configuration error type:<type of configuration error>

Severity

Cause

Error

A power supply has been disconnected or has failed. The sensor location, chassis location, previous state, power supply type, additional power supply status, and configuration error type information are provided.

Memory Device Messages

The memory device messages listed provides status and warning information for memory modules present in a particular system.

Memory devices determine health status by monitoring the ECC memory correction rate and the type of memory events that have occurred.

41

NOTE: A critical status does not always indicate a system failure or loss of data. In some instances, the system has exceeded the ECC correction rate. Although the system continues to function, you should perform system maintenance as described.

NOTE: The <status> can be either critical or non-critical.

Event ID — 1400

Description Memory device status is <status>

Memory device location: <location in chassis>

Possible memory module event cause: <list of causes>

Severity

Cause

Informational

Memory device monitoring has been disabled. The memory module may not be correctly seated, wrongly configured, or has failed.

Event ID — 1401

Description Memory device status is <status>

Memory device location: <location in chassis>

Possible memory module event cause: <list of causes>

Severity

Cause

Informational

Memory device status is unknown. The memory module may not be correctly seated, wrongly configured, or has failed.

Event ID — 1402

Description Memory device status is <status>

Memory device location: <location in chassis>

Possible memory module event cause: <list of causes>

Severity

Cause

Informational

Memory device status is normal. The memory device identified in the message has returned to a normal state.

Event ID — 1403

Description Memory device status is <status>

Memory device location: <location in chassis>

Possible memory module event cause: <list of causes>

Severity

Cause

Warning

A memory device correction rate exceeded an acceptable value. The memory device status and possible memory module event cause information is provided.

42

Event ID — 1404

Description Memory device status is <status>

Memory device location: <location in chassis>

Possible memory module event cause: <list of causes>

Severity

Cause

Error

A memory device correction rate exceeded an acceptable value, a memory spare bank was activated, or a multi-bit ECC error occurred. The system continues to function normally (except for a multi-bit error).

Replace the memory module identified in the message during the system’s next scheduled maintenance.

Clear the memory error on multi-bit ECC error. The memory device status and possible memory module event cause information is provided.

Event ID — 1405

Description Memory device status is <status>

Memory device location: <location in chassis>

Possible memory module event cause: <list of causes>

Severity

Cause

Informational

Memory device status is nonrecoverable. The memory module failed because of an irrecoverable error.

Hardware Log Sensor Messages

The hardware logs provide hardware status messages to systems management software. On certain systems, the hardware log is implemented as a circular queue. When the log becomes full, the oldest status messages are overwritten when new status messages are logged. On some systems, the log is not circular. On these systems, when the log becomes full, subsequent hardware status messages are lost. Hardware log sensor messages listed provides status and warning information about the noncircular logs that may fill up, resulting in lost status messages.

Event ID — 1550

Description Log monitoring has been disabled

Log type: <Log type>

Severity

Cause

Warning

A hardware log sensor in the specified system is disabled. The log type information is provided.

Event ID — 1551

Description Log status is unknown

Log type: <Log type>

Severity

Cause

Information

A hardware log sensor in the specified system could not obtain a reading. The log type information is provided.

43

Event ID — 1552

Description Log size is no longer near or at capacity

Log type: <Log type>

Severity

Cause

Information

The hardware log on the specified system is no longer near or at its capacity, usually as the result of clearing the log. The log type information is provided.

Event ID — 1553

Description Log size is near capacity

Log type: <Log type>

Severity

Cause

Warning

The size of a hardware log on the specified system is near or at the capacity of the hardware log. The log type information is provided.

Event ID — 1554

Description Log status is full

Log type: <Log type>

Severity

Cause

Error

The size of a hardware log on the specified system is full. The log type information is provided.

Event ID — 1555

Description Log sensor has failed

Log type: <Log type>

Severity

Cause

Error

A hardware log sensor in the specified system failed. The hardware log status cannot be monitored. The log type information is provided.

Processor Sensor Messages

The processor sensors monitor how well a processor is functioning. Processor messages listed provides status and warning information for processors in a particular chassis.

Event ID — 1601

Description Processor sensor value unknown Sensor Location: <Location in chassis>

Chassis Location: <Name of chassis>

Previous state was: <State>

44

Processor sensor status: <status>

Severity

Cause

Warning

A processor sensor in the specified system could not obtain a reading. The sensor location, chassis location, previous state and processor sensor status information is provided.

Event ID — 1602

Description Processor sensor returned to a normal value Sensor Location: <Location in chassis>

Chassis Location: <Name of chassis>

Previous state was: <State>

Processor sensor status: <status>

Severity

Cause

Information

A processor sensor in the specified system transitioned back to a normal state. The sensor location, chassis location, previous state and processor sensor status are provided.

Event ID — 1603

Description Processor sensor detected a warning value Sensor Location: <Location in chassis>

Chassis Location: <Name of chassis>

Previous state was: <State>

Processor sensor status: <status>

Severity

Cause

Warning

A processor sensor in the specified system is in a throttled state. The sensor location, chassis location, previous state and processor sensor status information is provided.

Event ID — 1604

Description Processor sensor detected a failure value Sensor Location: <Location in chassis>

Chassis Location: <Name of chassis>

Previous state was: <State>

Processor sensor status: <status>

Severity

Cause

Error

A processor sensor in the specified system is disabled, has a configuration error, or experienced a thermal trip. The sensor location, chassis location, previous state and processor sensor status are provided.

45

Pluggable Device Messages

The pluggable device messages listed provides status and error information when some devices, such as memory cards, are added or removed.

Event ID — 1650

Description Device plug event type unknown Device location: <Location in chassis, if available>

Chassis Location: <Name of chassis, if available>

Additional details: <Additional details for the events, if available>

Severity

Cause

Information

A pluggable device event message of unknown type was received. The device location, chassis location, and additional event details, if available, are provided.

Event ID — 1651

Description Device added to system Device location: <Location in chassis>

Chassis Location: <Name of chassis>

Additional details: <Additional details for the events>

Severity

Cause

Information

A device was added in the specified system. The device location, chassis location, and additional event details, if available, are provided.

Event ID — 1652

Description Device removed from system Device location: <Location in chassis>

Chassis Location: <Name of chassis>

Additional details: <Additional details for the events>

Severity

Cause

Information

A device was removed from the specified system. The device location, chassis location, and additional event details, if available, are provided.

Event ID — 1653

Description Device configuration error detected Device location: <Location in chassis>

Chassis Location: <Name of chassis>

Additional details: <Additional details for the events>

Severity

Cause

Error

A configuration error was detected for a pluggable device in the specified system. The device may have been added to the system incorrectly.

46

Battery Sensor Messages

The battery sensors monitor how well a battery is functioning. The battery messages listed provides status and warning information for batteries in a particular chassis.

Event ID — 1700

Description Battery sensor has failed Sensor location: <Location in chassis>

Chassis Location: <Name of chassis>

Previous state was: <State>

Battery sensor status: <status>

Severity

Cause

Critical/ Failure/Error

A battery sensor in the specified system is not functioning. The sensor location, chassis location, previous state, and battery sensor status information is provided.

Event ID — 1701

Description Battery sensor value unknown Sensor location: <Location in chassis>

Chassis Location: <Name of chassis>

Previous state was: <State>

Battery sensor status: <status>

Severity

Cause

Warning

A battery sensor in the specified system could not retrieve a reading. The sensor location, chassis location, previous state, and battery sensor status information is provided.

Event ID — 1702

Description Battery sensor returned to a normal value Sensor location: <Location in chassis>

Chassis Location: <Name of chassis>

Previous state was: <State>

Battery sensor status: <status>

Severity

Cause

Information

A battery sensor in the specified system detected that a battery transitioned back to a normal state. The sensor location, chassis location, previous state, and battery sensor status information is provided.

Event ID — 1703

Description Battery sensor detected a warning value Sensor location: <Location in chassis>

47

Chassis Location: <Name of chassis>

Previous state was: <State>

Battery sensor status: <status>

Severity

Cause

Warning

A battery sensor in the specified system detected that a battery is in a predictive failure state. The sensor location, chassis location, previous state, and battery sensor status information is provided.

Event ID — 1704

Description Battery sensor detected a failure value Sensor location: <Location in chassis>

Chassis Location: <Name of chassis>

Previous state was: <State>

Battery sensor status: <status>

Severity

Cause

Error

A battery sensor in the specified system detected that a battery has failed. The sensor location, chassis location, previous state, and battery sensor status information is provided.

Event ID — 1705

Description Battery sensor detected a non-recoverable value Sensor location: <Location in chassis>

Chassis Location: <Name of chassis>

Previous state was: <State>

Battery sensor status: <status>

Severity

Cause

Error

A battery sensor in the specified system could not retrieve a value. The sensor location, chassis location, previous state, and battery sensor status information is provided.

Secure Digital (SD) Card Device Messages

The SD card device sensors monitor instrumented SD card devices in the system. The messages provide the status and error information for SD card devices present in a chassis.

Event ID — 1750

Description SD card device sensor has failed Sensor location: <Location in chassis>

Chassis Location: <Name of chassis>

Previous state was: <State>

SD card device type: <Type of SD card device>

48

SD card state: <State of SD card>

Severity

Cause

Error

An SD card device sensor in the specified system failed. The sensor location, chassis location, previous state, and SD card device type information is provided. The SD card state is provided if an SD card is present in the SD card device.

Event ID — 1751

Description SD card device sensor value unknown Sensor location: <Location in chassis>

Chassis Location: <Name of chassis>

Previous state was: <State>

SD card device type: <Type of SD card device>

SD card state: <State of SD card>

Severity

Cause

Information

An SD card device sensor in the specified system could not obtain a reading. The sensor location, chassis location, previous state, and SD card device type information is provided. The SD card state is provided if an

SD card is present in the SD card device.

Event ID — 1752

Description SD card device returned to normal Sensor location: <Location in chassis>

Chassis Location: <Name of chassis>

Previous state was: <State>

SD card device type: <Type of SD card device>

SD card state: <State of SD card>

Severity

Cause

Information

An SD card device sensor in the specified system detected that an SD card transitioned back to a normal state. The sensor location, chassis location, previous state, and SD card device type information is provided.

The SD card state is provided if an SD card is present in the SD card device.

Event ID — 1753

Description SD card device detected a warning Sensor location: <Location in chassis>

Chassis Location: <Name of chassis>

Previous state was: <State>

SD card device type: <Type of SD card device>

SD card state: <State of SD card>

Severity Warning

49

Cause An SD card device sensor in the specified system detected a warning condition. The sensor location, chassis location, previous state, and SD card device type information is provided. The SD card state is provided if an

SD card is present in the SD card device.

Event ID — 1754

Description SD card device detected a failure Sensor location: <Location in chassis>

Chassis Location: <Name of chassis>

Previous state was: <State>

SD card device type: <Type of SD card device>

SD card state: <State of SD card>

Severity

Cause

Error

An SD card device sensor in the specified system detected an error. The sensor location, chassis location, previous state, and SD card device type information is provided. The SD card state is provided if an SD card is present in the SD card device.

Event ID — 1755

Description SD card device sensor detected a non-recoverable value Sensor location:

<Location in chassis>

Chassis Location: <Name of chassis>

Previous state was: <State>

SD card device type: <Type of SD card device>

SD card state: <State of SD card>

Severity

Cause

Error

An SD card device sensor in the specified system detected an error from which it cannot recover. The sensor location, chassis location, previous state, and SD card device type information is provided. The SD card state is provided if an SD card is present in the SD card device.

50

3

Storage Management Message Reference

The Server Administrator Storage Management’s alert or event management features let you monitor the health of storage resources such as controllers, enclosures, physical disks, and virtual disks.

Alert Monitoring and Logging

The Storage Management Service performs alert monitoring and logging. By default, the Storage Management service starts when the managed system starts up. If you stop the Storage Management Service, then alert monitoring and logging stops. Alert monitoring does the following:

• Updates the status of the storage object that generated the alert.

• Propagates the storage object’s status to all the related higher objects in the storage hierarchy. For example, the status of a lower-level object is propagated up to the status displayed on the Health tab for the top-level Storage object.

• Logs an alert in the alert log and the operating system application log.

• Sends an SNMP trap if the operating system’s SNMP service is installed and enabled.

NOTE: Server Administrator Storage Management does not log alerts regarding the data I/O path. These alerts are logged by the respective RAID drivers in the system alert log.

See the Server Administrator Storage Management Online Help for updated information.

Alert Message Format with Substitution Variables

When you view an alert in the Server Administrator alert log, the alert identifies the specific components such as the controller name or the virtual disk name to which the alert applies. In an actual operating environment, a storage system can have many combinations of controllers and disks as well as user-defined names for virtual disks and other components. Each environment is unique in its storage configuration and user-defined names. To receive an accurate alert message, that the Storage Management service must be able to insert the environment-specific names of storage components into an alert message.

This environment-specific information is inserted after the alert message text as shown for alert 2127.

For other alerts, the alert message text is constructed from information passed directly from the controller (or another storage component) to the alert log. In these cases, the variable information is represented with a percent symbol in the Storage

Management documentation. An example of such an alert is shown for alert 2334.

Table 3. Alert Message Format

Alert ID

2127

Message Text Displayed in the Storage

Management Service Documentation

Background Initialization started

2334 Controller event log %

Message Text Displayed in the Alert Log with Variable

Information Supplied

Background Initialization started: Virtual Disk 3 (Virtual

Disk 3) Controller 1 (PERC 5/E Adapter)

Controller event log: Current capacity of the battery is above threshold : Controller 1 (PERC 5/E Adapter)

The variables required to complete the message vary depending on the type of storage object and whether the storage object is in a

SCSI or SAS configuration. The following table identifies the possible variables used to identify each storage object.

51

NOTE: Some alert messages relating to an enclosure or an enclosure component, such as a fan or EMM, are generated by the controller when the enclosure or enclosure component ID cannot be determined.

NOTE: A, B, C and X, Y, Z in the following examples are variables representing the storage object name or number.

Table 4. Message Format with Variables for Each Storage Object

Storage Object

Controller

Message Variables

Message Format: Controller A (Name)

Message Format: Controller A

For example, 2326 A foreign configuration has been detected: Controller 1 (PERC 5/E Adapter)

NOTE: The controller name is not always displayed.

Battery

SCSI Physical Disk

Message Format: Battery X Controller A

For example, 2174 The controller battery has been removed: Battery 0 Controller 1

Message Format: Physical Disk X:Y Controller A, Connector B

For example, 2049 Physical disk removed: Physical Disk 0:14 Controller 1, Connector 0

SAS Physical Disk

Virtual Disk

Message Format: Physical Disk X:Y:Z Controller A, Connector B

For example, 2049 Physical disk removed: Physical Disk 0:0:14 Controller 1, Connector 0

Message Format: Virtual Disk X (Name) Controller A (Name)

Message Format: Virtual Disk X Controller A

For example, 2057 Virtual disk degraded: Virtual Disk 11 (Virtual Disk 11) Controller 1 (PERC 5/E

Adapter)

NOTE: The virtual disk and controller names are not always displayed.

Enclosure

SCSI Power Supply

SAS Power Supply

SCSI Temperature Probe

SAS Temperature Probe

Message Format: Enclosure X:Y Controller A, Connector B

For example, 2112 Enclosure shutdown: Enclosure 0:2 Controller 1, Connector 0

Message Format: Power Supply X Controller A, Connector B, Target ID C where "C" is the SCSI ID number of the enclosure management module (EMM) managing the power supply.

For example, 2122 Redundancy degraded: Power Supply 1, Controller 1, Connector 0, Target ID 6

Message Format: Power Supply X Controller A, Connector B, Enclosure C

For example, 2312 A power supply in the enclosure has an AC failure: Power Supply 1, Controller 1,

Connector 0, Enclosure 2

Message Format: Temperature Probe X Controller A, Connector B, Target ID C where C is the SCSI ID number of the EMM managing the temperature probe.

For example, 2101 Temperature dropped below the minimum warning threshold: Temperature

Probe 1, Controller 1, Connector 0, Target ID 6

Message Format: Temperature Probe X Controller A, Connector B, Enclosure C

52

Storage Object

SCSI Fan

SAS Fan

SCSI EMM

SAS EMM

Message Variables

For example, 2101 Temperature dropped below the minimum warning threshold: Temperature

Probe 1, Controller 1, Connector 0, Enclosure 2

Message Format: Fan X Controller A, Connector B, Target ID C where C is the SCSI ID number of the EMM managing the fan.

For example, 2121 Device returned to normal: Fan 1, Controller 1, Connector 0, Target ID 6

Message Format: Fan X Controller A, Connector B, Enclosure C

For example, 2121 Device returned to normal: Fan 1, Controller 1, Connector 0, Enclosure 2

Message Format: EMM X Controller A, Connector B, Target ID C where C is the SCSI ID number of the EMM.

For example, 2121 Device returned to normal: EMM 1, Controller 1, Connector 0, Target ID 6

Message Format: EMM X Controller A, Connector B, Enclosure C

For example, 2121 Device returned to normal: EMM 1, Controller 1, Connector 0, Enclosure 2

Alert Descriptions and Corrective Actions

The following sections describe alerts generated by the RAID or SCSI controllers supported by Storage Management. The alerts are displayed in the Server Administrator Alert tab or through Windows Event Viewer. These alerts can also be forwarded as SNMP traps to other applications.

SNMP traps are generated for the alerts listed in the following sections. These traps are included in the Server Administrator Storage

Management, management information base (MIB). The SNMP traps for these alerts use all of the SNMP trap variables. For more information on SNMP support and the MIB, see the SNMP Reference Guide.

To locate an alert, scroll through the following table to find the alert number displayed on the Server Administrator Alert tab or search

this file for the alert message text or number. See Understanding Event Messages

for more information on severity levels.

For more information regarding alert descriptions and the appropriate corrective actions, see the online help.

Event ID — 2048

Description

Severity

Cause and Action

Device failed.

Critical / Failure / Error

Cause: A storage component such as a physical disk or an enclosure has failed. The failed component may have been identified by the controller while performing a task such as a rescan or a check consistency.

Action: Replace the failed component. You can identify which disk has failed by locating the disk that has a red “X” for its status. Perform a rescan after replacing the failed component.

Related Alert

Information

Clear Alert Number: 2121

Related Alert Number: 2095, 2201, 2203

Local Response Agent (LRA) Number: 2051, 2061, 2071, 2081, 2091, 2101

53

SNMP Trap

Numbers

754, 804, 854, 904, 954, 1004, 1054, 1104, 1154, 1204

Event ID — 2049

Description

Severity

Cause and Action

Physical disk removed.

Warning / Non-critical

Cause: A physical disk has been removed from the disk group. This alert can also be caused by loose or defective cables or by problems with the enclosure.

Action: If a physical disk was removed from the disk group, either replace the disk or restore the original disk. On some controllers, a removed disk has a red X for its status. On other controllers, a removed disk may have an Offline status or is not displayed on the user interface. Perform a rescan after replacing or restoring the disk. If a disk has not been removed from the disk group, then check for problems with the cables. See the online help for more information on checking the cables. Ensure that the enclosure is powered on. If the problem persists, check the enclosure documentation for further diagnostic information.

Related Alert

Information

Clear Alert Number: 2052

Related Alert Number: 2054, 2057, 2056, 2076, 2079, 2081, 2083, 2129, 2202, 2204, 2270, 2292, 2299,

2369

Local Response Agent (LRA) Number: 2070

SNMP Trap

Numbers

903

Event ID — 2050

Description

Severity

Cause and Action

Physical disk offline.

Warning / Non-critical

Cause: A physical disk in the disk group is offline. The user may have manually put the physical disk offline.

Action: Perform a rescan. You can also select the offline disk and perform a Make Online operation.

Related Alert

Information

Clear Alert Number: 2158

Related Alert Number: 2099, 2196

Local Response Agent (LRA) Number: 2070

SNMP Trap

Numbers

903

Event ID — 2051

Description

Severity

Cause and Action

Physical disk degraded.

Warning / Non-critical

Cause: A physical disk has reported an error condition and may be degraded. The physical disk may have reported the error condition in response to a SMART Trip (Predictive Failure).

54

Related Alert

Information

Action: Replace the degraded physical disk. You can identify which disk is degraded by locating the disk that has a Yellow Triangle for its status. Perform a rescan after replacing the disk.

Clear Alert Number: None

Related Alert Number: 2094

Local Response Agent (LRA) Number: 2070

SNMP Trap

Numbers

903

Event ID — 2052

Description

Severity

Cause and Action

Physical disk inserted.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: 2065, 2305, 2367

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2053

Description

Severity

Cause and Action

Virtual disk created.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2054

Description

Severity

Cause and Action

Virtual disk deleted.

Informational

Cause: A virtual disk has been deleted. Performing a Reset Configuration may detect that a virtual disk has been deleted.

55

Related Alert

Information

Action: None

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2080

SNMP Trap

Numbers

1201

Event ID — 2055

Description

Severity

Cause and Action

Virtual disk configuration changed.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2056

Description

Severity

Cause and Action

Virtual disk failed.

Critical / Failure / Error

Cause: One or more physical disks included in the virtual disk have failed. If the virtual disk is non-redundant

(does not use mirrored or parity data), then the failure of a single physical disk can cause the virtual disk to fail. If the virtual disk is redundant, then more physical disks have failed than can be rebuilt using mirrored or parity information.

Action: Create a new virtual disk and restore from a backup.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: 2048, 2049, 2050, 2076, 2079, 2081, 2129, 2346

Local Response Agent (LRA) Number: 2081

SNMP Trap

Numbers

1204

Event ID — 2057

Description

Severity

Virtual disk degraded.

Warning / Non-critical

56

Cause and Action

Related Alert

Information

Cause 1: This alert message occurs when a physical disk included in a redundant virtual disk fails. Because the virtual disk is redundant (uses mirrored or parity information) and only one physical disk has failed, the virtual disk can be rebuilt.

Action 1: Replace the failed drive. Rebuild of the virtual disk starts automatically.

NOTE: If you put the drive in a different slot, you need to assign it as a hot spare for the rebuild to start automatically.

If you put the drive in a different slot, you need to assign it as a hot spare for the rebuild to start automatically.

Cause 2: A physical disk in the disk group has been removed.

Action 2: If a physical disk was removed from the disk group, either replace the disk or restore the original disk. You can identify which disk has been removed by locating the disk that has a red “X” for its status.

Perform a rescan after replacing the disk.

Clear Alert Number: None

Related Alert Number: 2048, 2049, 2050, 2076, 2079, 2081, 2123, 2129, 2346

Local Response Agent (LRA) Number: 2080

SNMP Trap

Numbers

1203

Event ID — 2058

Description

Severity

Cause and Action

Virtual disk check consistency started.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2059

Description

Severity

Cause and Action

Virtual disk format started.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: 2086

Related Alert Number: None

57

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2060

Description

Severity

Cause and Action

Copy of data started from physical disk % 2 to physical disk % 1.

OK / Normal /Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: 2075

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2061

Description

Severity

Cause and Action

Virtual disk initialization started.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: 2088

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2062

Description

Severity

Cause and Action

Physical disk initialization started.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: 2089

Related Alert Number: None

Local Response Agent (LRA) Number: None

58

SNMP Trap

Numbers

901

Event ID — 2063

Description

Severity

Cause and Action

Virtual disk reconfiguration started.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

SNMP Trap

Numbers

1201

Event ID — 2064

Description

Severity

Cause and Action

Virtual disk rebuild started.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: 2090

Related Alert Number: None

Local Response Agent (LRA) Number: None

Clear Alert Number: 2091

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2065

Description

Severity

Cause and Action

Physical disk rebuild started.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Number: 2092

Related Alert Number: 2099, 2121, 2196

Local Response Agent (LRA) Number: None

901

59

Event ID — 2067

Description

Severity

Cause and Action

Virtual disk check consistency cancelled.

OK / Normal / Informational

Cause: The check consistency operation was cancelled because a physical disk in the array has failed or because a user cancelled the check consistency operation.

Action: If the physical disk failed, then replace the physical disk. You can identify which disk failed by locating the disk that has a red “X” for its status. Perform a rescan after replacing the disk. The consistency check can take a long time. The time it takes depends on the size of the physical disk or the virtual disk.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2070

Description

Severity

Cause and Action

Virtual disk initialization cancelled.

OK / Normal / Informational

Cause: The virtual disk initialization cancelled because a physical disk included in the virtual disk has failed or because a user cancelled the virtual disk initialization.

Action: If a physical disk failed, then replace the physical disk. You can identify which disk has failed by locating the disk that has a red “X” for its status. Perform a rescan after replacing the disk. Restart the format physical disk operation. Restart the virtual disk initialization.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2074

Description

Severity

Cause and Action

Physical disk rebuild cancelled.

OK / Normal / Informational

Cause: The user has cancelled the rebuild operation.

Action: Restart the rebuild operation.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

60

SNMP Trap

Numbers

901

Event ID — 2075

Description

Severity

Cause and Action

Copy of data completed from physical disk % 2 to physical disk % 1.

OK / Normal / Informational

Cause: This alert is provided for informational purposes.

Action: None

Related Alert

Information

SNMP Trap

Numbers

1201

Event ID — 2076

Description

Severity

Cause and Action

Virtual disk Check Consistency failed.

Critical / Failure / Error

Cause: AA physical disk included in the virtual disk failed or there is an error in the parity information. A failed physical disk can cause errors in parity information.

Action: Replace the failed physical disk. You can identify which disk has failed by locating the disk that has a red “X” for its status. Rebuild the physical disk. When finished, restart the check consistency operation.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: 2060

Local Response Agent (LRA) Number: None

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2081

SNMP Trap

Numbers

1204

Event ID — 2077

Description

Severity

Cause and Action

Virtual disk format failed.

Critical / Failure / Error

Cause: A physical disk included in the virtual disk failed.

Action: Replace the failed physical disk. You can identify which physical disk has failed by locating the disk that has a red X for its status. Rebuild the physical disk. When finished, restart the virtual disk format operation.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

61

Local Response Agent (LRA) Number: 2081

SNMP Trap

Numbers

1204

Event ID — 2079

Description

Severity

Cause and Action

Virtual disk initialization failed.

Critical / Failure / Error

Cause: A physical disk included in the virtual disk has failed or a user has cancelled the initialization.

Action: If a physical disk has failed, then replace the physical disk

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2081

SNMP Trap

Numbers

1204

Event ID — 2080

Description

Severity

Cause and Action

Physical disk initialization failed.

Critical / Failure / Error

Cause: The physical disk has failed or is not functioning.

Action: Replace the failed or non-functional disk. You can identify a disk that has failed by locating the disk that has a red “X” for its status. Restart the initialization.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2071

SNMP Trap

Numbers

904

Event ID — 2081

Description

Severity

Cause and Action

Virtual disk reconfiguration failed.

Critical / Failure / Error

Hardware RAID:

Cause: A physical disk included in the virtual disk has failed or is not functioning. A user may also have cancelled the reconfiguration.

Action: Replace the failed or non-functional disk. You can identify a disk that has failed by locating the disk that displays a red X in the status field.

62

Related Alert

Information

If the physical disk is part of a redundant array, then rebuild the physical disk. When finished, restart the reconfiguration.

Software RAID:

• Perform a backup with the Verify option.

• If the file backup fails, try to restore the failed file from a previous backup.

• When the backup with the Verify option is complete without any errors, delete the Virtual Disk.

• Recreate a new Virtual Disk with new drives.

• Restore the data from backup.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2081

SNMP Trap

Numbers

1204

Event ID — 2082

Description

Severity

Cause and Action

Virtual disk rebuild failed.

Critical / Failure / Error

Cause: A physical disk included in the virtual disk has failed or is not functioning. A user may also have cancelled the rebuild.

Action: Replace the failed or non-functional disk. You can identify a disk that has failed by locating the disk that has a red X for its status. Restart the virtual disk rebuild.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: 2048

Local Response Agent (LRA) Number: 2081

SNMP Trap

Numbers

1204

Event ID — 2083

Description

Severity

Cause and Action

Physical disk rebuild failed.

Critical / Failure / Error

Cause: A physical disk included in the virtual disk has failed or is not functioning. A user may also have cancelled the rebuild.

Action: Replace the failed or non-functional disk. You can identify a disk that has failed by locating the disk that has a red X for its status. Rebuild the virtual disk rebuild.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2071

63

SNMP Trap

Numbers

904

Event ID — 2085

Description

Severity

Cause and Action

Virtual disk check consistency completed.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

SNMP Trap

Numbers

1201

Event ID — 2086

Description

Severity

Cause and Action

Virtual disk format completed.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: Alert 2085 is a clear alert for alert 2058.

Related Alert Number: None

Local Response Agent (LRA) Number: None

Clear Alert Number: Alert 2086 is a clear alert for alert 2059.

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2087

Description

Severity

Cause and Action

Copy of data resumed from physical disk % 2 to physical disk % 1.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Number: None

Related Alert Number: 2060

Local Response Agent (LRA) Number: None

901

64

Event ID — 2088

Description

Severity

Cause and Action

Virtual disk initialization completed.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: Alert 2088 is a clear alert for alerts 2061 and 2136.

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2089

Description

Severity

Cause and Action

Physical disk initialization completed.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: Alert 2089 is a clear alert for alert 2062.

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2090

Description

Severity

Cause and Action

Virtual disk reconfiguration completed

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Number: Alert 2090 is a clear alert for alert 2063.

Related Alert Number: None

Local Response Agent (LRA) Number: None

1201

65

Event ID — 2091

Description

Severity

Cause and Action

Virtual disk rebuild completed.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: Alert 2091 is a clear alert for alert 2064.

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2092

Description

Severity

Cause and Action

Physical disk rebuild completed.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: Alert 2092 is a clear alert for alert 2065.

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2094

Description

Severity

Cause and Action

Predictive Failure reported.

Warning / Non-critical

Cause: The physical disk is predicted to fail. Many physical disks contain Self Monitoring Analysis and

Reporting Technology (SMART). When enabled, SMART monitors the health of the disk based on indications such as the number of write operations that have been performed on the disk.

Action: Replace the physical disk. Even though the disk may not have failed yet, it is strongly recommended that you replace the disk.

If this disk is part of a redundant virtual disk, perform the Offline task on the disk; replace the disk; the rebuild starts automatically.

NOTE: If you put the drive in a different slot, you need to assign it as a hot spare for the rebuild to start automatically.

If this disk is a hot spare, then unassign the hot spare; perform the Prepare to Remove task on the disk; replace the disk; and assign the new disk as a hot spare.

66

Related Alert

Information

CAUTION: If this disk is part of a non-redundant disk, back up your data immediately. If the disk fails, you cannot recover the data.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2070

SNMP Trap

Numbers

903

Event ID — 2095

Description

Severity

Cause and Action

SCSI sense data %1.

OK / Normal / Informational

Cause: A SCSI device experienced an error, but may have recovered.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: 2273

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751, 851, 901

Event ID — 2098

Description

Severity

Cause and Action

Global hot spare assigned.

OK / Normal / Informational

Cause: A user has assigned a physical disk as a global hot spare. This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: 2277

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2099

Description

Severity

Cause and Action

Global hot spare unassigned.

OK / Normal / Informational

Cause: A physical disk that was assigned as a hot spare has been unassigned and is no longer functioning as a hot spare. The physical disk may have been unassigned by a user or automatically unassigned by Storage

Management. Storage Management unassigns hot spares that have been used to rebuild data. Once data is

67

Related Alert

Information rebuilt, the hot spare becomes a member of the virtual disk and is no longer assigned as a hot spare. You need to assign a new hot spare to maintain data protection in this situation. On the CERC SATA1.5/6 ch, and

CERC SATA1.5/2s controllers, if you use another application such as the BIOS to include a hot spare in a virtual disk, then Storage Management unassigns the physical disk as a hot spare.

Action: Although this alert is provided for informational purposes, you may need to assign a new hot spare to the virtual disk.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2100

Description

Severity

Cause and Action

Temperature exceeded the maximum warning threshold.

Warning / Non-critical

Cause: The physical disk enclosure is too hot. A variety of factors can cause the excessive temperature. For example, a fan may have failed, the thermostat may be set too high, or the room temperature may be too hot.

Action: Check for factors that may cause overheating. For example, verify that the enclosure fan is working.

You should also check the thermostat settings and examine whether the enclosure is located near a heat source. Make sure the enclosure has enough ventilation and that the room temperature is not too hot. See the physical disk enclosure documentation for more diagnostic information.

Related Alert

Information

SNMP Trap

Numbers

1053

Event ID — 2101

Description

Severity

Cause and Action

Temperature exceeded the maximum warning threshold.

Warning / Non-critical

Cause: The physical disk enclosure is too cool.

Action: Check if the thermostat setting is too low and if the room temperature is too cool.

Related Alert

Information

Clear Alert Number: 2353

Related Alert Number: 2112

Local Response Agent (LRA) Number: 2090

SNMP Trap

Numbers

Clear Alert Number: 2353

Related Alert Number: None

Local Response Agent (LRA) Number: 2090

1053

68

Event ID — 2102

Description

Severity

Cause and Action

Temperature exceeded the maximum failure threshold.

Critical / Failure / Error

Cause: The physical disk enclosure is too hot. A variety of factors can cause the excessive temperature. For example, a fan may have failed, the thermostat may be set too high, or the room temperature may be too hot.

Action: Check for factors that may cause overheating. For example, verify that the enclosure fan is working.

You should also check the thermostat settings and examine whether the enclosure is located near a heat source. Make sure the enclosure has enough ventilation and that the room temperature is not too hot. See the physical disk enclosure documentation for more diagnostic information.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2091

SNMP Trap

Numbers

1054

Event ID — 2103

Description

Severity

Cause and Action

Temperature dropped below the minimum failure threshold.

Critical / Failure / Error

Cause: The physical disk enclosure is too cool.

Action: Check if the thermostat setting is too low and if the room temperature is too cool.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: 2112

Local Response Agent (LRA) Number: 2091

SNMP Trap

Numbers

1054

Event ID — 2104

Description

Severity

Cause and Action

Controller battery is reconditioning.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: 2105

Related Alert Number: None

Local Response Agent (LRA) Number: None

69

SNMP Trap

Numbers

1151

Event ID — 2105

Description

Severity

Cause and Action

Controller battery recondition is completed.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: Alert 2105 is a clear alert for alert 2104.

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1151

Event ID — 2106

Description

Severity

Cause and Action

SMART FPT exceeded.

Warning / Non-critical

Cause: A disk on the specified controller has received a SMART alert (predictive failure) indicating that the disk is likely to fail in the near future.

Action: Replace the disk that has received the SMART alert. If the physical disk is a member of a nonredundant virtual disk, then back up the data before replacing the disk.

CAUTION: Removing a physical disk that is included in a non-redundant virtual disk causes the virtual disk to fail and may cause data loss.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2070

SNMP Trap

Numbers

903

Event ID — 2107

Description

Severity

Cause and Action

SMART configuration change.

Critical / Failure / Error

Cause: A disk has received a SMART alert (predictive failure) after a configuration change. The disk is likely to fail in the near future.

Action: Replace the disk that has received the SMART alert. If the physical disk is a member of a nonredundant virtual disk, then back up the data before replacing the disk.

CAUTION: Removing a physical disk that is included in a non-redundant virtual disk causes the virtual disk to fail and may cause data loss.

70

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2071

SNMP Trap

Numbers

904

Event ID — 2108

Description

Severity

Cause and Action

SMART warning.

Warning / Non-critical

Cause: A disk has received a SMART alert (predictive failure). The disk is likely to fail in the near future.

Action: Replace the disk that has received the SMART alert. If the physical disk is a member of a nonredundant virtual disk, then back up the data before replacing the disk.

CAUTION: Removing a physical disk that is included in a non-redundant virtual disk causes the virtual disk to fail and may cause data loss.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2070

SNMP Trap

Numbers

903

Event ID — 2109

Description

Severity

Cause and Action

SMART warning temperature.

Warning / Non-critical

Cause: A disk has reached an unacceptable temperature and received a SMART alert (predictive failure).

The disk is likely to fail in the near future.

Action 1: Determine why the physical disk has reached an unacceptable temperature. A variety of factors can cause the excessive temperature. For example, a fan may have failed, the thermostat may be set too high, or the room temperature may be too hot or cold. Verify that the fans in the server or enclosure are working. If the physical disk is in an enclosure, you should check the thermostat settings and examine whether the enclosure is located near a heat source.

Make sure the enclosure has enough ventilation and that the room temperature is not too hot. See the physical disk enclosure documentation for more diagnostic information.

Action 2 : If you cannot identify why the disk has reached an unacceptable temperature, then replace the disk. If the physical disk is a member of a non-redundant virtual disk, then back up the data before replacing the disk.

CAUTION: Removing a physical disk that is included in a non-redundant virtual disk causes the virtual disk to fail and may cause data loss.

Related Alert

Information

Clear Alert Number: None

71

Related Alert Number: None

Local Response Agent (LRA) Number: 2070

SNMP Trap

Numbers

903

Event ID — 2110

Description

Severity

Cause and Action

SMART warning degraded.

Warning / Non-critical

Cause: A disk is degraded and has received a SMART alert (predictive failure). The disk is likely to fail in the near future.

Action: Replace the disk that has received the SMART alert. If the physical disk is a member of a nonredundant virtual disk, then back up the data before replacing the disk.

CAUTION: Removing a physical disk that is included in a non-redundant virtual disk causes the virtual disk to fail and may cause data loss.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2070

SNMP Trap

Numbers

903

Event ID — 2111

Description

Severity

Cause and Action

Failure prediction threshold exceeded due to test.

Warning / Non-critical

Cause: A disk has received a SMART alert (predictive failure) due to test conditions.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2070

SNMP Trap

Numbers

903

Event ID — 2112

Description

Severity

Cause and Action

Enclosure was shut down.

Critical / Failure / Error

Cause: The physical disk enclosure is either hotter or cooler than the maximum or minimum allowable temperature range.

72

Related Alert

Information

Action: Check for factors that may cause overheating or excessive cooling. For example, verify that the enclosure fan is working. You should also check the thermostat settings and examine whether the enclosure is located near a heat source. Make sure the enclosure has enough ventilation and that the room temperature is not too hot or too cold. See the enclosure documentation for more diagnostic information.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2091

SNMP Trap

Numbers

854

Event ID — 2114

Description

Severity

Cause and Action

A consistency check on a virtual disk has been paused (suspended).

OK / Normal / Informational

Cause: The check consistency operation on a virtual disk was paused by a user.

Action: To resume the check consistency operation, right-click the virtual disk in the tree view and select

Resume Check Consistency.

Related Alert

Information

Clear Alert Number: 2115

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2115

Description

Severity

Cause and Action

A consistency check on a virtual disk has been resumed.

OK / Normal / Informational

Cause: The check consistency operation on a virtual disk has resumed processing after being paused by a user. This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: Alert 2115 is a clear alert for alert 2114.

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2116

Description

Severity

A virtual disk and its mirror have been split.

OK / Normal / Informational

73

Cause and Action

Related Alert

Information

Cause: A user has caused a mirrored virtual disk to be split. When a virtual disk is mirrored, its data is copied to another virtual disk in order to maintain redundancy. After being split, both virtual disks retain a copy of the data although the mirror is no longer intact. The updates to the data are no longer copied to the mirror.

This alert is for informational purposes.

Action: None

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2117

Description

Severity

Cause and Action

A mirrored virtual disk has been unmirrored.

OK / Normal / Informational

Cause: A user has caused a mirrored virtual disk to be unmirrored. When a virtual disk is mirrored, its data is copied to another virtual disk in order to maintain redundancy. After being unmirrored, the disk formerly used as the mirror returns to being a physical disk and becomes available for inclusion in another virtual disk. This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2118

Description

Severity

Cause and Action

Change write policy.

OK / Normal / Informational

Cause: A user has changed the write policy for a virtual disk. This alert is for informational purposes.

Action: None

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

1201

74

Event ID — 2120

Description

Severity

Cause and Action

Enclosure firmware mismatch.

Warning / Non-critical

Cause: The firmware on the EMM is not the same version. It is required that both modules have the same version of the firmware. This alert may be caused when a user attempts to insert an EMM module that has a different firmware version than an existing module.

Action: Download the same version of the firmware to both EMM modules.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2090

SNMP Trap

Numbers

853

Event ID — 2121

Description

Severity

Cause and Action

Device returned to normal.

OK / Normal / Informational

Cause: A device that was previously in an error state has returned to a normal state. For example, if an enclosure became too hot and subsequently cooled down, you may receive this alert. This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: Alert 2121 is a clear alert for alert 2048.

Related Alert Number: 2050, 2065, 2158

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

752,802, 852, 902, 952, 1002,1052, 1102, 1152, 1202

Event ID — 2122

Description

Severity

Cause and Action

Redundancy degraded.

Warning / Non-critical

Cause: One or more of the enclosure components has failed.

For example, a fan or power supply may have failed. Although the enclosure is currently operational, the failure of additional components could cause the enclosure to fail.

Action: Identify and replace the failed component. To identify the failed component, select the enclosure in the tree view and click the Health subtab. Any failed component is identified with a red X on the enclosure’s

Health subtab. Alternatively, you can select the Storage object and click the Health subtab.

The controller status displayed on the Health subtab indicates whether a controller has a Failed or

Degraded component.

75

Related Alert

Information

See the enclosure documentation for information on replacing enclosure components and for other diagnostic information.

Clear Alert Number: 2124

Related Alert Number: 2048

Local Response Agent (LRA) Number: 2090

SNMP Trap

Numbers

1305

Event ID — 2123

Description

Severity

Cause and Action

Redundancy lost.

Warning / Non-critical

Cause: A virtual disk or an enclosure has lost data redundancy. In the case of a virtual disk, one or more physical disks included in the virtual disk have failed. Due to the failed physical disk or disks, the virtual disk is no longer maintaining redundant (mirrored or parity) data. The failure of an additional physical disk results in lost data. In the case of an enclosure, more than one enclosure component has failed. For example, the enclosure may have suffered the loss of all fans or all power supplies.

Action: Identify and replace the failed components. To identify the failed component, select the Storage object and click the Health subtab. The controller status displayed on the Health subtab indicates whether a controller has a Failed or Degraded component.

Click the controller that displays a Warning or Failed status. This action displays the controller Health subtab which displays the status of the individual controller components. Continue clicking the components with a

Warning or Health status until you identify the failed component.

See the online help for more information. See the enclosure documentation for information on replacing enclosure components and for other diagnostic information.

Related Alert

Information

Clear Alert Number: 2353

Related Alert Number: 2112

Local Response Agent (LRA) Number: 2090

SNMP Trap

Numbers

1053

Event ID — 2124

Description

Severity

Cause and Action

Redundancy normal.

OK / Normal / Informational

Cause: Data redundancy has been restored to a virtual disk or an enclosure that previously suffered a loss of redundancy. This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: Alert 2124 is a clear alert for alerts 2122 and 2123.

Related Alert Number: None

76

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1304

Event ID — 2125

Description

Severity

Cause and Action

Controller cache preserved for missing or offline virtual disk.

Warning / Non-critical

Cause: Virtual disk controller was disconnected, during I/O operation.

Action: Import foreign disks, if any. Check if the enclosure containing the virtual disk is disconnected from the controller.

Related Alert

Information

Clear Alert Number: 2186, 2240

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1203

Event ID — 2126

Description

Severity

Cause and Action

SCSI sense sector reassign.

Warning / Non-critical

Cause: A sector of the physical disk is corrupted and data cannot be maintained on this portion of the disk.

This alert is for informational purposes.

CAUTION: Any data residing on the corrupt portion of the disk may be lost and you may need to restore your data from backup.

Action: If the physical disk is part of a non-redundant virtual disk, then back up the data and replace the physical disk.

CAUTION: Removing a physical disk that is included in a non-redundant virtual disk causes the virtual disk to fail and may cause data loss.

If the disk is part of a redundant virtual disk, then any data residing on the corrupt portion of the disk is reallocated elsewhere in the virtual disk.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

903

Event ID — 2127

Description Background initialization (BGI) started.

77

Severity

Cause and Action

Related Alert

Information

OK / Normal / Informational

Cause: BGI of a virtual disk has started. This alert is for informational purposes.

Action: None

Clear Alert Number: 2130

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2128

Description

Severity

Cause and Action

BGI cancelled.

OK / Normal / Informational

Cause: BGI of a virtual disk has been cancelled. A user or the firmware may have stopped BGI.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2129

Description

Severity

Cause and Action

BGI failed.

Critical / Failure / Error

Cause: BGI of a virtual disk has failed.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: 2340

Local Response Agent (LRA) Number: 2081

SNMP Trap

Numbers

1204

Event ID — 2130

Description

Severity

Cause and Action

BGI completed.

OK / Normal / Informational

Cause: BGI of a virtual disk has completed. This alert is for informational purposes.

78

Related Alert

Information

Action: None

Clear Alert Number: Alert 2130 is a clear alert for alert 2127.

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2131

Description

Severity

Cause and Action

Firmware version mismatch.

Warning / Non-critical

Cause: The firmware on the controller is not a supported version.

Action: Install a supported version of the firmware. If you do not have a supported version of the firmware available, check with your support provider for information on how to obtain the most current firmware.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2060

SNMP Trap

Numbers

753

Event ID — 2132

Description

Severity

Cause and Action

Driver version mismatch.

Warning / Non-critical

Cause: The controller driver is not a supported version.

Action: Install a supported version of the driver. If you do not have a supported driver version available, you can check with your support provider for information on how to obtain the most current driver.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2060

SNMP Trap

Numbers

753

Event ID — 2135

Description Array Manager is installed on the system.

NOTE: This is not supported on Server Administrator version 6.0.1.

Severity Warning / Non-critical

79

Cause and Action

Related Alert

Information

Cause: Storage Management has been installed on a system that has an Array Manager installation.

Action: Installing Storage Management and Array Manager on the same system is not a supported configuration. Uninstall either Storage Management or Array Manager.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2050

SNMP Trap

Numbers

103

Event ID — 2136

Description

Severity

Cause and Action

Virtual disk initialization.

OK / Normal / Informational

Cause: Virtual disk initialization is in progress. This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: 2088

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2137

Description

Severity

Cause and Action

Communication time-out.

Warning / Non-critical

Cause: The controller is unable to communicate with an enclosure. There are several reasons why communication may be lost. For example, there may be a bad or loose cable. An unusual amount of I/O may also interrupt communication with the enclosure. In addition, communication loss may be caused by software, hardware, or firmware problems, bad or failed power supplies, and enclosure shutdown.

When viewed in the alert log, the description for this event displays several variables. These variables are: controller and enclosure names, type of communication problem, return code, and SCSI status.

Action: Check for problems with the cables. See the online help for more information on checking the cables. You should also check to see if the enclosure has degraded or failed components. To do so, select the enclosure object in the tree view and click the Health subtab. The Health subtab displays the status of the enclosure components. Verify that the controller has supported driver and firmware versions installed and that the EMMs are each running the same version of supported firmware.

Related Alert

Information

Clear Alert Number: 2162

Related Alert Number: None

Local Response Agent (LRA) Number: 2090

80

SNMP Trap

Numbers

853

Event ID — 2138

Description

Severity

Cause and Action

Enclosure alarm enabled.

OK / Normal / Informational

Cause: A user has enabled the enclosure alarm. This alert is for informational purposes.

Action: None

Related Alert

Information

SNMP Trap

Numbers

851

Event ID — 2139

Description

Severity

Cause and Action

Enclosure alarm disabled.

OK / Normal / Informational

Cause: A user has disabled the enclosure alarm.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

851

Event ID — 2140

Description

Severity

Cause and Action

Dead disk segments restored.

OK / Normal / Informational

Cause: Disk space that was formerly “dead” or inaccessible to a redundant virtual disk has been restored.

This alert is for informational purposes.

Action: None

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

1201

81

Event ID — 2141

Description

Severity

Cause and Action

Physical disk dead segments removed.

OK / Normal / Informational

Cause: Portions of the physical disk were formerly inaccessible. The disk space from these dead segments has been recovered and is now usable. Any data residing on these dead segments has been lost. This alert is for informational purposes.

Action: Check for factors that may cause overheating. For example, verify that the enclosure fan is working.

You should also check the thermostat settings and examine whether the enclosure is located near a heat source. Make sure the enclosure has enough ventilation and that the room temperature is not too hot. See the physical disk enclosure documentation for more diagnostic information.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2142

Description

Severity

Cause and Action

Controller rebuild rate has changed.

OK / Normal / Informational

Cause: A user has changed the controller rebuild rate. This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2143

Description

Severity

Cause and Action

Controller alarm enabled.

OK / Normal / Informational

Cause: A user has enabled the controller alarm. This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

82

SNMP Trap

Numbers

751

Event ID — 2144

Description

Severity

Cause and Action

Controller alarm disabled.

OK / Normal / Informational

Cause: A user has disabled the controller alarm. This alert is for informational purposes.

Action: None

Related Alert

Information

SNMP Trap

Numbers

751

Event ID — 2145

Description

Severity

Cause and Action

Controller battery low.

Warning / Non-critical

Cause: The controller battery charge is low.

Action: Recondition the battery. See the online help for more information.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2100

SNMP Trap

Numbers

1153

Event ID — 2146

Description

Severity

Cause and Action

Bad block replacement error.

Warning / Non-critical

Cause: A portion of a physical disk is damaged.

Action: See the Server Administrator Storage Management online help for more information.

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2060

753

83

Event ID — 2147

Description

Severity

Cause and Action

Bad block sense error.

Warning / Non-critical

Cause: A portion of a physical disk is damaged.

Action: See the Server Administrator Storage Management online help for more information.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2060

SNMP Trap

Numbers

753

Event ID — 2148

Description

Severity

Cause and Action

Bad block medium error.

Warning / Non-critical

Cause: A portion of a physical disk is damaged.

Action: See the Server Administrator Storage Management online help for more information.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2060

SNMP Trap

Numbers

753

Event ID — 2149

Description

Severity

Cause and Action

Bad block extended sense error.

Warning / Non-critical

Cause: A portion of a physical disk is damaged.

Action: See the Server Administrator Storage Management online help for more information.

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2060

753

84

Event ID — 2150

Description

Severity

Cause and Action

Bad block extended medium error.

Warning / Non-critical

Cause: A portion of a physical disk is damaged.

Action: See the Server Administrator Storage Management online help for more information.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2060

SNMP Trap

Numbers

753

Event ID — 2151

Description Enclosure asset tag changed

Severity

Cause and Action

OK / Normal / Informational

Cause: A user has changed the enclosure asset tag. This alert is for informational purposes.

Action: None

Related Alert

Information

SNMP Trap

Numbers

851

Event ID — 2152

Description

Severity

Cause and Action

Enclosure asset name changed.

OK / Normal / Informational

Cause: A user has changed the enclosure asset name. This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

851

85

Event ID — 2153

Description

Severity

Cause and Action

Enclosure service tag changed.

OK / Normal / Informational

Cause: An enclosure service tag was changed. In most circumstances, this service tag should only be changed by your service provider.

Action: Ensure that the tag was changed under authorized circumstances.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

851

Event ID — 2154

Description

Severity

Cause and Action

Maximum temperature probe warning threshold value changed.

OK / Normal / Informational

Cause: A user has changed the value for the maximum temperature probe warning threshold. This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1051

Event ID — 2155

Description

Severity

Cause and Action

Minimum temperature probe warning threshold value changed.

OK / Normal / Informational

Cause: A user has changed the value for the minimum temperature probe warning threshold. This alert is for informational purposes.

Action: None

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

1051

86

Event ID — 2156

Description

Severity

Cause and Action

Controller alarm has been tested.

OK / Normal / Informational

Cause: The controller alarm test has run successfully. This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2157

Description

Severity

Cause and Action

Controller configuration has been reset.

OK / Normal / Informational

Cause: A user has reset the controller configuration. See the online help for more information. This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2158

Description

Severity

Cause and Action

Physical disk online.

OK / Normal / Informational

Cause: An offline physical disk has been made online. This alert is for informational purposes.

Action: None

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Number: Alert 2158 is a clear alert for alert 2050.

Related Alert Number: 2048, 2050, 2065, 2099, 2121, 2196, 2201, 2203

Local Response Agent (LRA) Number: None

901

87

Event ID — 2159

Description

Severity

Cause and Action

Virtual disk renamed.

OK / Normal / Informational

Cause: A user has renamed a virtual disk.

When renaming a virtual disk on a PERC 4/SC, 4/DC, 4e/DC, 4/Di, CERC ATA100/4ch, PERC 5/E, PERC

5/i or SAS 5/iR controller, this alert displays the new virtual disk name.

On the PERC 4/SC, 4/DC, 4e/DC, 4/Di, 4/IM, 4e/Si, 4e/Di, and CERC ATA 100/4ch controllers, this alert displays the original virtual disk name. This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2160

Description

Severity

Cause and Action

Dedicated hot spare assigned.

OK / Normal / Informational

Cause: A user has assigned a physical disk as a dedicated hot spare to a virtual disk. This alert is provided for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: 2161

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2161

Description

Severity

Cause and Action

Dedicated hot spare unassigned.

OK / Normal / Informational

Cause: A physical disk that was assigned as a hot spare has been unassigned and is no longer functioning as a hot spare. The physical disk may have been unassigned by a user or automatically unassigned by Storage

Management. Storage Management unassigns hot spares that have been used to rebuild data. Once data is rebuilt onto the hot spare, the hot spare becomes a member of the virtual disk and is no longer assigned as a hot spare. You need to assign a new hot spare to maintain data protection in this situation. On the CERC

SATA1.5/6ch, and CERC SATA1.5/2s controllers, if you use another application such as the BIOS to include a hot spare in a virtual disk, then Storage Management unassigns the physical disk as a hot spare.

88

Related Alert

Information

Action: Although this alert is provided for informational purposes, you may need to assign a new hot spare to the virtual disk.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2162

Description

Severity

Cause and Action

Communication regained.

OK / Normal / Informational

Cause: Communication with an enclosure has been restored. This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: Alert 2162 is a clear alert for alerts 2137 and 2292.

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

851

Event ID — 2163

Description

Severity

Cause and Action

Rebuild completed with errors.

OK / Normal / Informational

Cause: During a rebuild one or more blocks of data was not recoverable due to missing parity information.

Some data loss may have occurred.

Action: Perform a check to verify the built array. Any files that are impacted should be restored from a backup. See the Storage Management online help for more information.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2071

SNMP Trap

Numbers

904

Event ID — 2164

Description

Severity

See the Readme file for a list of validated controller driver versions.

OK / Normal / Informational

89

Cause and Action

Related Alert

Information

Cause: Storage Management is unable to determine whether the system has the minimum required versions of the RAID controller drivers. This alert is for informational purposes.

Action: See the Readme file for driver and firmware requirements. In particular, if Storage Management experiences performance problems, you should verify that you have the minimum supported versions of the drivers and firmware installed.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

101

Event ID — 2165

Description

Severity

Cause and Action

The RAID controller firmware and driver validation was not performed. The configuration file cannot be opened.

Warning / Non-critical

Cause: Storage Management is unable to determine whether the system has the minimum required versions of the RAID controller firmware and drivers. This situation may occur for a variety of reasons. For example, the installation directory path to the configuration file may not be correct. The configuration file may also have been removed or renamed.

Action: Reinstall Storage Management

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2060

SNMP Trap

Numbers

753

Event ID — 2166

Description

Severity

Cause and Action

The RAID controller firmware and driver validation was not performed. The configuration file is out of date, missing the required information, or not properly formatted to complete the comparison.

Warning / Non-critical

Cause: Storage Management is unable to determine whether the system has the minimum required versions of the RAID controller firmware and drivers. This situation has occurred because a configuration file is out of date, missing the required information, or not properly formatted to complete the comparison.

Action: Reinstall Storage Management.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2060

90

SNMP Trap

Numbers

753

Event ID — 2167

Description

Severity

Cause and Action

The current kernel version and the non-RAID SCSI driver version are older than the minimum required levels.

See readme.txt for a list of validated kernel and driver versions.

Warning / Non-critical

Cause: The version of the kernel and the driver do not meet the minimum requirements. Storage

Management may not be able to display the storage or perform storage management functions until you have updated the system to meet the minimum requirements.

Action: See the Readme file for a list of validated kernel and driver versions. Update the system to meet the minimum requirements and then reinstall Storage Management.

Related Alert

Information

SNMP Trap

Numbers

103

Event ID — 2168

Description

Severity

Cause and Action

The non-RAID SCSI driver version is older than the minimum required level. See readme.txt for the validated driver version.

Warning / Non-critical

Cause: The version of the driver does not meet the minimum requirements. Storage Management may not be able to display the storage or perform storage management functions until you have updated the system to meet the minimum requirements.

Action: See the Readme file for the validated driver version. Update the system to meet the minimum requirements and then reinstall Storage Management.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2050

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2050

SNMP Trap

Numbers

103

Event ID — 2169

Description

Severity

Cause and Action

The controller battery needs to be replaced.

Critical / Failure / Error

Cause: The controller battery cannot be recharged. The battery may be old or it may have been already recharged the maximum number of times. In addition, the battery charger may not be working.

Action: Replace the battery pack.

91

Related Alert

Information

Clear Alert Number: None

Related Alert Number: 2118

Local Response Agent (LRA) Number: 2101

SNMP Trap

Numbers

1154

Event ID — 2170

Description

Severity

Cause and Action

The controller battery charge level is normal.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1151

Event ID — 2171

Description

Severity

Cause and Action

The controller battery temperature is above normal.

Warning / Non-critical

Cause: The battery may be recharging, the room temperature may be too hot, or the fan in the system may be degraded or failed.

Action: If this alert was generated due to a battery recharge, the situation is corrected when the recharge is complete. You should also check if the room temperature is normal and that the system components are functioning properly.

Related Alert

Information

Clear Alert Number: 2172

Related Alert Number: None

Local Response Agent (LRA) Number: 2100

SNMP Trap

Numbers

1153

Event ID — 2172

Description

Severity

Cause and Action

The controller battery temperature is normal.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

92

Related Alert

Information

Clear Alert Number: Alert 2172 is a clear alert for alert 2171.

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1151

Event ID — 2173

Description

Severity

Cause and Action

Unsupported configuration detected. The SCSI rates of the enclosure management modules (EMMs) are not the same. EMM 0 % 1 EMM 1 % 2

Warning / Non-critical

Cause: An unsupported configuration was detected.

Action: Replace one of the EMMs with the matching SCSI rate EMM.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2090

SNMP Trap

Numbers

853

Event ID — 2174

Description

Severity

Cause and Action

The controller battery has been removed.

Warning / Non-critical

Cause: The controller cannot communicate with the battery. The battery may be removed, or the contact point between the controller and the battery may be burnt or corroded.

Action: Replace the battery if it has been removed. If the contact point between the battery and the controller is burnt or corroded, you must replace either the battery or the controller, or both. See the hardware documentation for information on how to safely access, remove, and replace the battery.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: 2188, 2318

Local Response Agent (LRA) Number: 2100

SNMP Trap

Numbers

1153

Event ID — 2175

Description

Severity

Cause and Action

The controller battery has been replaced.

OK / Normal / Informational

Cause: This alert is for informational purposes.

93

Related Alert

Information

Action: None

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1151

Event ID — 2176

Description

Severity

Cause and Action

The controller battery Learn cycle has started.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: 2177

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1151

Event ID — 2177

Description

Severity

Cause and Action

The controller battery Learn cycle has completed.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: Alert 2177 is a clear alert for alert 2176.

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1151

Event ID — 2178

Description

Severity

Cause and Action

The controller battery Learn cycle has timed out.

Warning / Non-critical

Cause: The controller battery must be fully charged before the Learn cycle can begin. The battery may be unable to maintain a full charge causing the Learn cycle to timeout. Additionally, the battery must be able to maintain cached data for a specified period of time in the event of a power loss. For example, some batteries

94

Related Alert

Information maintain cached data for 24 hours. If the battery is unable to maintain cached data for the required period of time, then the Learn cycle timeout occurs.

Action: Replace the battery pack as the battery is unable to maintain a full charge.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2100

SNMP Trap

Numbers

1153

Event ID — 2179

Description

Severity

Cause and Action

The controller battery Learn cycle has been postponed.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1151

Event ID — 2180

Description

Severity

Cause and Action

The controller battery Learn cycle starts in % 1 days.

OK / Normal / Informational

Cause: This alert is for informational purposes. The %1 indicates a substitution variable. The text for this substitution variable is displayed with the alert in the alert log and can vary depending on the situation.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1151

Event ID — 2181

Description

Severity

The controller battery learn cycle starts in % 1 hours.

OK / Normal / Informational

95

Cause and Action

Related Alert

Information

Cause: The % 1 indicates a substitution variable. The text for this substitution variable is displayed with the alert in the alert log and can vary depending on the situation. This alert is for informational purposes.

Action: None

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1151

Event ID — 2182

Description

Severity

Cause and Action

An invalid SAS configuration has been detected.

Critical / Failure / Error

Cause: The controller and attached enclosures are not cabled correctly.

Action: See the hardware documentation for information on correct cabling configurations.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2061

SNMP Trap

Numbers

754

Event ID — 2183

Description

Severity

Cause and Action

Replace Member Operation failed on physical disk % 1 from physical disk % 2.

Critical / Failure / Error

Cause: The physical disk participating in the Replace Member Operation, operation has failed.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: 2060

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

904

Event ID — 2184

Description

Severity

Cause and Action

Physical disk Replace Member Operation cancelled.

OK / Normal / Informational

Cause: User cancelled the Replace Member Operation.

96

Related Alert

Information

Action: None

Clear Alert Number: None

Related Alert Number: 2060

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2185

Description

Severity

Cause and Action

Physical disk Replace Member Operation stopped for spare.

Warning / Non-critical

Cause: This alert is provided for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: 2060

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

903

Event ID — 2186

Description

Severity

Cause and Action

The controller cache has been discarded.

Warning / Non-critical

Cause: The controller has flushed the cache and any data in the cache has been lost. This may happen if the system has memory or battery problems that cause the controller to distrust the cache. Although user data may have been lost, this alert does not always indicate that relevant or user data has been lost.

Action: Verify that the battery and memory are functioning properly.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2060

SNMP Trap

Numbers

753

Event ID — 2187

Description

Severity

Cause and Action

Single-bit ECC error limit exceeded on the controller DIMM.

Warning / Non-critical

Cause: The system memory is malfunctioning.

97

Related Alert

Information

Action: Contact technical support to replace the controller memory.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2060

SNMP Trap

Numbers

753

Event ID — 2188

Description

Severity

Cause and Action

The controller write policy has been changed to Write Through.

Warning

Cause: The controller battery is unable to maintain cached data for the required period of time. For example, if the required period of time is 24 hours, the battery is unable to maintain cached data for 24 hours. It is normal to receive this alert during the battery Learn cycle as the Learn cycle discharges the battery before recharging it. When discharged, the battery cannot maintain cached data.

Action: Check the health of the battery. If the battery is weak, replace the battery pack.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1153

Event ID — 2189

Description

Severity

Cause and Action

The controller write policy has been changed to Write Back.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1151

Event ID — 2190

Description

Severity

Cause and Action

The controller has detected a hot-add of an enclosure.

OK / Normal / Informational

Cause: This alert is for informational purposes.

98

Related Alert

Information

Action: None

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2191

Description

Severity

Cause and Action

Multiple enclosures are attached to the controller. This is an unsupported configuration.

Critical / Failure / Error

Cause: There are too many enclosures attached to the controller port. When the enclosure limit is exceeded, the controller loses contact with all enclosures attached to the port.

Action: Remove the last enclosure. You must remove the enclosure that has been added last and is causing the enclosure limit to exceed.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: 2211

Local Response Agent (LRA) Number: 2091

SNMP Trap

Numbers

854

Event ID — 2192

Description

Severity

Cause and Action

The virtual disk Check Consistency has made corrections and completed.

Informational

Cause: The virtual disk Check Consistency has identified errors and made corrections. For example, the

Check Consistency may have encountered a bad disk block and remapped the disk block to restore data consistency. This alert is for informational purposes.

Action: None. As a precaution, monitor the alert log for other errors related to this virtual disk. If problems persist, contact Technical Support.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1203

Event ID — 2193

Description

Severity

The virtual disk reconfiguration has resumed.

OK / Normal / Informational

99

Cause and Action

Related Alert

Information

Cause: This alert is for informational purposes.

Action: None

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2194

Description

Severity

Cause and Action

The virtual disk Read policy has changed.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2195

Description

Severity

Cause and Action

Dedicated hot spare assigned. Physical disk % 1

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: 2196

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2196

Description

Severity

Cause and Action

Dedicated hot spare unassigned. Physical disk % 1

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

100

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2197

Description

Severity

Cause and Action

Physical disk Replace Member Operation stopped for rebuild.

Warning

Cause: This alert is provided for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: 2060

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

903

Event ID — 2198

Description

Severity

Cause and Action

The physical disk is too small to be used for Replace member operation.

Warning

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

903

Event ID — 2199

Description

Severity

Cause and Action

The virtual disk cache policy has changed.

Informational

Cause: User has provided invalid input for the chosen operation.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

101

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2200

Description

Severity

Cause and Action

Replace Member Operation not possible as SAS/SATA is not supported in the same virtual disk.

Warning/ Non-critical

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

903

Event ID — 2201

Description

Severity

Cause and Action

A global hot spare failed.

Warning/ Non-critical

Cause: The controller is not able to communicate with a disk that is assigned as a dedicated hot spare. The disk may have been removed. There may also be a bad or loose cable.

Action: Check if the disk is healthy and that it has not been removed. Check the cables. If necessary, replace the disk and reassign the hot spare.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: 2048

Local Response Agent (LRA) Number: 2070

SNMP Trap

Numbers

903

Event ID — 2202

Description

Severity

Cause and Action

A global hot spare has been removed.

OK / Normal / Informational

Cause: The controller is unable to communicate with a disk that is assigned as a global hot spare. The disk may have been removed. There may also be a bad or loose cable.

Action: Check if the disk is healthy and that it has not been removed. Check the cables. If necessary, replace the disk and reassign the hot spare.

Related Alert

Information

Clear Alert Number: None

102

SNMP Trap

Numbers

901

Event ID — 2203

Description

Severity

Cause and Action

A dedicated hot spare failed.

Warning/ Non-critical

Cause: The controller is unable to communicate with a disk that is assigned as a dedicated hot spare. The disk may have failed or been removed. There may also be a bad or loose cable.

Action: Check if the disk is healthy and that it has not been removed. Check the cables. If necessary, replace the disk and reassign the hot spare.

Related Alert

Information

Related Alert Number: None

Local Response Agent (LRA) Number: None

Clear Alert Number: None

Related Alert Number: 2048

Local Response Agent (LRA) Number: 2070

SNMP Trap

Numbers

903

Event ID — 2204

Description

Severity

Cause and Action

A dedicated hot spare has been removed.

OK / Normal / Informational

Cause: The controller is unable to communicate with a disk that is assigned as a dedicated hot spare. The disk may have been removed. There may also be a bad or loose cable.

Action: Check if the disk is healthy and that it has not been removed. Check the cables. If necessary, replace the disk and reassign the hot spare.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2205

Description

Severity

Cause and Action

A dedicated hot spare has been automatically unassigned.

OK / Normal / Informational

Cause: The hot spare is no longer required because the virtual disk it was assigned to has been deleted.

Action: None

103

Related Alert

Information

Clear Alert Number: None

Related Alert Number: 2098, 2161, 2196

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2206

Description

Severity

Cause and Action

The only hot spare available is a SATA disk. SATA disks cannot replace SAS disks.

Warning / Non-critical

Cause: The only physical disk available to be assigned as a hot spare is using SATA technology. The physical disks in the virtual disk are using SAS technology. Because of this difference in technology, the hot spare cannot rebuild data if one of the physical disks in the virtual disk fails.

Action: Add a SAS disk that is large enough to be used as the hot spare and assign it as a hot spare.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2070

SNMP Trap

Numbers

903

Event ID — 2207

Description

Severity

Cause and Action

The only hot spare available is a SAS disk. SAS disks cannot replace SATA disks.

Warning / Non-critical

Cause: The only physical disk available to be assigned as a hot spare is using SAS technology. The physical disks in the virtual disk are using SATA technology. Because of this difference in technology, the hot spare cannot rebuild data if one of the physical disks in the virtual disk fails.

Action: Add a SATA disk that is large enough to be used as the hot spare and assign the new disk as a hot spare.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2070

SNMP Trap

Numbers

903

Event ID — 2210

Description

Severity

Cause and Action

Battery requires reconditioning. Initiate the battery learn cycle.

Warning / Non-critical

Cause: Battery is in warn only mode and requires reconditioning.

104

Related Alert

Information

Action: Initiate the battery learn cycle.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1153

Event ID — 2211

Description

Severity

Cause and Action

The physical disk is not supported.

Warning / Non-critical

Cause: The physical disk may not have a supported version of the firmware or the disk may not be supported by your service provider.

Action: If the disk is supported, update the firmware to a supported version. If the disk is not supported by your service provider, replace the disk with one that is supported.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2070

SNMP Trap

Numbers

903

Event ID — 2212

Description

Severity

Cause and Action

The controller battery temperature is above normal.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1151

Event ID — 2213

Description

Severity

Cause and Action

Recharge count maximum exceeded.

Warning / Non-critical

Cause: The battery has been recharged more times than the battery recharge limit allows.

105

Related Alert

Information

Action: Replace the battery pack.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2100

SNMP Trap

Numbers

1153

Event ID — 2214

Description

Severity

Cause and Action

Battery charge in progress.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1151

Event ID — 2215

Description

Severity

Cause and Action

Battery charge process interrupted.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1151

Event ID — 2216

Description

Severity

Cause and Action

The battery learn mode has changed to auto.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

106

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1151

Event ID — 2217

Description

Severity

Cause and Action

The battery learn mode has changed to warn.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1151

Event ID — 2218

Description

Severity

Cause and Action

None of the Controller Property are set.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: You should change at least one controller property and run the command again.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2219

Description

Severity

Cause and Action

Abort Check Consistency on Error, Replace Member Operation, Auto Replace Member Operation on

Predictive Failure and Loadbalance changed.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: Change at least one controller property and run the command again.

Related Alert

Information

Clear Alert Number: None

107

SNMP Trap

Numbers

751

Event ID — 2220

Description

Severity

Cause and Action

Replace Member Operation, Auto Replace Member Operation on Predictive Failure and Loadbalance changed.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: Change at least one controller property and run the command again.

Related Alert

Information

Related Alert Number: None

Local Response Agent (LRA) Number: None

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2221

Description

Severity

Cause and Action

Auto Replace Member Operation on Predictive Failure, Abort CC on Error and Loadbalance changed.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: Change at least one controller property and run the command again.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2222

Description

Severity

Cause and Action

Loadbalance and Auto Replace Member Operation on Predictive Failure changed.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: Change at least one controller property and run the command again.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

108

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2223

Description

Severity

Cause and Action

Abort Check Consistency on Error, Replace Member Operation and Loadbalance changed.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: Change at least one controller property and run the command again.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2224

Description

Severity

Cause and Action

Replace Member Operation and Loadbalance changed.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: Change at least one controller property and run the command again.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2225

Description

Severity

Cause and Action

Abort Check Consistency on Error and Load balance changed.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: Change at least one controller property and run the command again.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

109

SNMP Trap

Numbers

751

Event ID — 2226

Description

Severity

Cause and Action

Load balance changed.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: Change at least one controller property and run the command again.

Related Alert

Information

SNMP Trap

Numbers

751

Event ID — 2227

Description

Severity

Cause and Action

Abort Check Consistency on Error, Replace Member Operation and Auto Replace Member Operation on

Predictive Failure changed.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: Change at least one controller property and run the command again.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2228

Description

Severity

Cause and Action

Replace Member Operation and Auto Replace Member Operation on Predictive Failure changed.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: Change at least one controller property and run the command again.

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

751

110

Event ID — 2229

Description

Severity

Cause and Action

Abort Check Consistency on Error and Auto Replace Member Operation on Predictive Failure changed.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: Change at least one controller property and run the command again.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2230

Description

Severity

Cause and Action

Auto Replace Member Operation on Predictive Failure changed.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: Change at least one controller property and run the command again.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2231

Description

Severity

Cause and Action

Replace Member Operation and Abort Check Consistency on Error changed.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: Change at least one controller property and run the command again.

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

751

111

Event ID — 2232

Description

Severity

Cause and Action

The controller alarm is silenced.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2233

Description

Severity

Cause and Action

The Background initialization (BGI) rate has changed.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2234

Description

Severity

Cause and Action

The Patrol Read rate has changed.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

751

112

Event ID — 2235

Description

Severity

Cause and Action

The Check Consistency rate has changed.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2236

Description

Severity

Cause and Action

Replace Member Operation modified.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: Change at least one controller property and run the command again.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2237

Description

Severity

Cause and Action

Abort Check Consistency on Error modified.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: Change at least one controller property and run the command again.

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

751

113

Event ID — 2238

Description

Severity

Cause and Action

The controller debug log file has been exported.

OK / Normal / Informational

Cause: The user has attempted to export the controller debug log. This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2239

Description

Severity

Cause and Action

A foreign configuration has been cleared.

OK / Normal / Informational

Cause: The user has attempted to clear a foreign configuration. This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2240

Description

Severity

Cause and Action

A foreign configuration has been imported.

OK / Normal / Informational

Cause: The user has attempted to import a foreign configuration. This alert is for informational purposes.

Action: None

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

751

114

Event ID — 2241

Description

Severity

Cause and Action

The Patrol Read mode has changed.

OK / Normal / Informational

Cause: The controller has changed the patrol read mode. This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2242

Description

Severity

Cause and Action

The Patrol Read operation has started.

OK / Normal / Informational

Cause: The controller has started the Patrol Read operation. This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: 2243

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2243

Description

Severity

Cause and Action

The Patrol Read operation has stopped.

OK / Normal / Informational

Cause: The controller has stopped the Patrol Read operation. This alert is for informational purposes.

Action: None

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Number: Alert 2243 is a clear alert for alert 2242.

Related Alert Number: None

Local Response Agent (LRA) Number: None

751

115

Event ID — 2244

Description

Severity

Cause and Action

A virtual disk blink has been initiated.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2245

Description

Severity

Cause and Action

A virtual disk blink has ceased.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2246

Description

Severity

Cause and Action

Warning / Non-critical

OK / Normal / Informational

Cause: The temperature of the battery is high. This maybe due to the battery being charged.

Action: As the charge weakens, the charger should automatically recharge the battery. If the battery has reached its recharge limit, replace the battery pack. Monitor the battery to make sure that it recharges successfully.

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2100

1153

116

Event ID — 2247

Description

Severity

Cause and Action

The controller battery is charging.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: 2358

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1151

Event ID — 2248

Description

Severity

Cause and Action

The controller battery is executing a Learn cycle.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1151

Event ID — 2249

Description

Severity

Cause and Action

The physical disk Clear operation has started.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

901

117

Event ID — 2250

Description

Severity

Cause and Action

Redundant Path is broken.

Warning /Non-critical

Cause: The redundant path is broken.

Action: Check the connection to the enclosure, which is degraded.

Related Alert

Information

Clear Alert Number: 2370

Related Alert Number: 2370

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

753

Event ID — 2251

Description

Severity

Cause and Action

The physical disk blink has initiated.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2252

Description

Severity

Cause and Action

The physical disk blink has ceased.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

901

118

Event ID — 2253

Description

Severity

Cause and Action

Redundant path restored.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2254

Description

Severity

Cause and Action

The Clear operation has cancelled.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2255

Description

Severity

Cause and Action

The physical disk has been started.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Number: None

Related Alert Number: 2048, 2050, 2065, 2099, 2121, 2196, 2201, 2203

Local Response Agent (LRA) Number: None

901

119

Event ID — 2257

Description

Severity

Cause and Action

Controller preserved cache is discarded.

Warning /Non-critical

Cause: The controller cache is discarded by the user. This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

753

Event ID — 2258

Description

Severity

Cause and Action

Controller has preserved cache.

Warning /Non-critical

Cause: I/O interrupted for a virtual disk which is connected to the controller.

Action: Check for foreign configuration and import if any. Check for cable fault. Recover any virtual disk lost by the controller.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

753

Event ID — 2259

Description

Severity

Cause and Action

An enclosure blink operation has initiated.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Number: 2260

Related Alert Number: None

Local Response Agent (LRA) Number: None

851

120

Event ID — 2260

Description

Severity

Cause and Action

An enclosure blink has ceased.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

851

Event ID — 2261

Description

Severity

Cause and Action

A global rescan has initiated.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2262

Description

Severity

Cause and Action

SMART thermal shutdown is enabled.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

101

121

Event ID — 2263

Description

Severity

Cause and Action

SMART thermal shutdown is disabled.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

101

Event ID — 2264

Description

Severity

Cause and Action

A device is missing.

Warning / Non-critical

Cause: The controller cannot communicate with a device. The device may be removed. There may also be a bad or loose cable.

Action: Check if the device is in and not removed. If it is in, check the cables. Also check the connection to the controller battery and the battery health. A battery with a weak or depleted charge may cause this alert.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2050, 2060, 2070, 2080, 2090, 2100

SNMP Trap

Numbers

753, 803, 853, 903, 953, 1003, 1053, 1103, 1153, 1203

Event ID — 2265

Description

Severity

Cause and Action

A device is in an unknown state.

Warning / Non-critical

Cause: The controller cannot communicate with a device. The state of the device cannot be determined.

There may be a bad or loose cable. The system may also be experiencing problems with the application programming interface (API). There could also be a problem with the driver or firmware.

Action: Check the cables. Check if the controller has a supported version of the driver and firmware. You can download the current version of the driver and firmware from the support site. Rebooting the system may also resolve this problem.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: 2048, 2050

Local Response Agent (LRA) Number: 2050, 2060, 2070, 2080, 2090, 2100

122

SNMP Trap

Numbers

753, 803, 853, 903, 953, 1003, 1053, 1103, 1153, 1203

Event ID — 2266

Description

Severity

Cause and Action

Controller log file entry: %1

OK / Normal / Informational

Cause: The %1 indicates a substitution variable. The text for this substitution variable is generated by the controller and is displayed with the alert in the alert log. This text can vary depending on the situation. This alert is for informational purposes.

Action: None

Related Alert

Information

SNMP Trap

Numbers

751, 801, 851, 901, 951, 1001, 1051, 1101, 1151, 1201

Event ID — 2267

Description

Severity

Cause and Action

The controller reconstruct rate has changed.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2268

Description

Severity

Cause and Action

%1, Storage Management has lost communication with the controller. An immediate reboot is strongly recommended to avoid further problems. If the reboot does not restore communication, then contact technical support for more information.

Critical / Failure / Error

Cause: Storage Management has lost communication with a controller. This may occur if the controller driver or firmware is experiencing a problem. The %1 indicates a substitution variable. The text for this substitution variable is displayed with the alert in the alert log and can vary depending on the situation.

Action: Reboot the system. If the problem is not resolved, contact technical support. See your system documentation for information about contacting technical support by using telephone, fax, and Internet services.

123

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2051

SNMP Trap

Numbers

104

Event ID — 2269

Description

Severity

Cause and Action

The physical disk Clear operation has completed.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2270

Description

Severity

Cause and Action

The physical disk Clear operation failed.

Critical / Failure / Error

Cause: A Clear task was being performed on a physical disk but the task was interrupted and did not complete successfully. The controller may have lost communication with the disk. The disk may have been removed or the cables may be loose or defective.

Action: Verify that the disk is present and not in a Failed state. Make sure the cables are attached securely.

See the online help for more information on checking the cables. Restart the Clear task.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2071

SNMP Trap

Numbers

904

Event ID — 2271

Description

Severity

Cause and Action

The Patrol Read encountered a media error.

OK / Normal / Informational

Cause: The Patrol Read task has encountered an error such as a bad disk block that cannot be remapped.

This alert is for informational purposes.

124

Related Alert

Information

Action: None

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2272

Description

Severity

Cause and Action

Patrol Read found an uncorrectable media error.

Critical / Failure / Error

Cause: The Patrol Read task has encountered an error that cannot be corrected. There may be a bad disk block that cannot be remapped.

Action: Back up your data. If you are able to back up the data successfully, then fully initialize the disk and then restore from back up.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2071

SNMP Trap

Numbers

904

Event ID — 2273

Description

Severity

Cause and Action

A block on the physical disk has been punctured by the controller.

Critical / Failure / Error

Cause: The controller encountered an unrecoverable medium error when attempting to read a block on the physical disk and marked that block as invalid. If the error was encountered on a source physical disk during a rebuild or reconfigure operation, it also punctures the corresponding block on the target physical disk. The invalid block is cleared during a write operation.

Action: Back up your data. If you are able to back up the data successfully, initialize the disk and restore from the back up.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: 2095, 2350

Local Response Agent (LRA) Number: 2071

SNMP Trap

Numbers

904

Event ID — 2274

Description The physical disk rebuild has resumed.

125

Severity

Cause and Action

Related Alert

Information

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2276

Description

Severity

Cause and Action

The dedicated hot spare is too small.

Warning / Non-critical

Cause: The dedicated hot spare is not large enough to protect all virtual disks that reside on the disk group.

Action: Assign a larger disk as the dedicated hot spare.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2070

SNMP Trap

Numbers

903

Event ID — 2277

Description

Severity

Cause and Action

The global hot spare is too small.

Warning / Non-critical

Cause: The global hot spare is not large enough to protect all virtual disks that reside on the controller.

Action: Assign a larger disk as the global hot spare.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2070

SNMP Trap

Numbers

903

Event ID — 2278

Description

Severity

The controller battery charge level is below a normal threshold.

Warning

126

Cause and Action

Related Alert

Information

Cause: The battery is discharging. A battery discharge is a normal activity during the battery Learn cycle.

The battery Learn cycle recharges the battery. You should receive alert 2179 when the recharge occurs.

Action 1: Check if the battery Learn cycle is in progress. The battery also displays the Learn state while the

Learn cycle is in progress.

Action 2: If a Learn cycle is not in progress, replace the battery pack.

Clear Alert Number: None

Related Alert Number: 2199

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1153

Event ID — 2279

Description

Severity

Cause and Action

The controller battery charge level is operating within normal limits.

OK / Normal / Informational

Cause: This alert indicates that the battery is recharging during the battery Learn cycle. This alert is provided for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1151

Event ID — 2280

Description

Severity

Cause and Action

A disk media error has been corrected.

OK / Normal / Informational

Cause: A disk media error was detected while the controller was completing a background task. A bad disk block was identified. The disk block has been remapped.

Action: Consider replacing the disk. If you receive this alert frequently, be sure to replace the disk. You should also routinely back up your data.

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

1201

127

Event ID — 2281

Description

Severity

Cause and Action

Virtual disk has inconsistent data.

OK / Normal / Informational

Cause: The virtual disk has inconsistent data. This may be caused when a power loss or system shutdown occurs while data is being written to the virtual disk. This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: 2127

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2282

Description

Severity

Cause and Action

Hot spare SMART polling failed.

Critical / Failure / Error

Cause: The controller firmware attempted a SMART polling on the hot spare but was unable to complete it.

The controller has lost communication with the hot spare.

Action: Check the health of the disk assigned as a hot spare. You may need to replace the disk and reassign the hot spare. Make sure the cables are attached securely. See the Server Administrator Storage

Management User’s Guide, for more information on checking the cables.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2071

SNMP Trap

Numbers

904

Event ID — 2283

Description

Severity

Cause and Action

A redundant path is broken.

Warning / Non-critical

Cause: The controller has two connectors that are connected to the same enclosure. The communication path on one connector has lost connection with the enclosure. The communication path on the other connector is reporting this loss.

Action: Make sure the cables are attached securely and both enclosure management modules (EMMs) are healthy. See the Cables Attached Correctly section for more information on checking the cables.

Related Alert

Information

Clear Alert Number: 2284

Related Alert Number: None

128

Local Response Agent (LRA) Number: 2070

SNMP Trap

Numbers

903

Event ID — 2284

Description

Severity

Cause and Action

A redundant path has been restored.

OK / Normal / Informational

Cause: This alert is provided for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: Alert 2284 is a clear alert for alert 2283.

Related Alert Number: None

Local Response Agent (LRA) Number: 2071

SNMP Trap

Numbers

901

Event ID — 2285

Description

Severity

Cause and Action

A disk media error was corrected during recovery.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2286

Description

Severity

Cause and Action

A Learn cycle start is pending while the battery charges.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

129

SNMP Trap

Numbers

1151

Event ID — 2287

Description

Severity

Cause and Action

Protection policy has been changed.

OK / Normal / Informational

Cause: A new protection policy has been created / existing protection policy has been modified.

Action: None

Related Alert

Information

SNMP Trap

Numbers

101

Event ID — 2288

Description

Severity

Cause and Action

The patrol read has resumed.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: 2384

Local Response Agent (LRA) Number: None

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2289

Description

Severity

Cause and Action

Multi-bit ECC error on controller DIMM.

Critical / Failure / Error

Cause: An error involving multiple bits has been encountered during a read or write operation. The error correction algorithm recalculates parity data during read and write operations. If an error involves only a single bit, it may be possible for the error correction algorithm to correct the error and maintain parity data.

An error involving multiple bits, however, usually indicates data loss. In some cases, if the multi-bit error occurs during a read operation, the data on the disk may be OK. If the multi-bit error occurs during a write operation, data loss has occurred.

Action: Replace the dual in-line memory module (DIMM). The DIMM is a part of the controller battery pack.

See your hardware documentation for information on replacing the DIMM. You may need to restore data from backup.

130

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2061

SNMP Trap

Numbers

754

Event ID — 2290

Description

Severity

Cause and Action

Single-bit ECC error on controller DIMM.

Warning / Non-critical

Cause: An error involving a single bit has been encountered during a read or write operation. The error correction algorithm has corrected this error.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2060

SNMP Trap

Numbers

753

Event ID — 2291

Description

Severity

Cause and Action

An enclosure management module (EMM) has been discovered.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

851

Event ID — 2292

Description

Severity

Cause and Action

Communication with the enclosure has been lost.

Critical / Failure / Error

Cause: The controller has lost communication with an EMM. The cables may be loose or defective.

Action: Make sure the cables are attached securely. Reboot the system.

Related Alert

Information

Clear Alert Number: 2162

131

SNMP Trap

Numbers

854

Event ID — 2293

Description

Severity

Cause and Action

The EMM has failed.

Critical / Failure / Error

Cause: The failure may be caused by a loss of power to the EMM. The EMM self test may also have identified a failure. There could also be a firmware problem or a multi-bit error.

Action: Replace the EMM. See the hardware documentation for information on replacing the EMM.

Related Alert

Information

Related Alert Number: None

Local Response Agent (LRA) Number: 2091

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2091

SNMP Trap

Numbers

854

Event ID — 2294

Description

Severity

Cause and Action

A device has been inserted.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

851

Event ID — 2295

Description

Severity

Cause and Action

A device has been removed.

Critical / Failure / Error

Cause: A device has been removed and the system is no longer functioning in optimal condition.

Action: Replace the device.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

132

Related Alert

Information

Local Response Agent (LRA) Number: 2091

SNMP Trap

Numbers

854

Event ID — 2296

Description

Severity

Cause and Action

An EMM has been inserted.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751, 851, 951

Event ID — 2297

Description

Severity

Cause and Action

An EMM has been removed.

Critical / Failure / Error

Cause: An EMM has been removed.

Action: Reinsert the EMM. See the hardware documentation for information on replacing the EMM.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2091

SNMP Trap

Numbers

854, 954

Event ID — 2298

Description

Severity

Cause and Action

The enclosure has a bad sensor %1.

Warning / Non-critical

Cause: The enclosure has a bad sensor. The enclosure sensors monitor the fan speeds, temperature probes, and so on. The % indicates a substitution variable. The text for this substitution variable is displayed with the alerts in the alert log and can vary depending on the situation.

Action: See the hardware documentation for more information.

Related Alert

Information

Clear Alert Number: None

133

SNMP Trap

Numbers

853

Event ID — 2299

Description

Severity

Cause and Action

Bad PHY %1

Critical / Failure / Error

Cause: There is a problem with a physical connection or PHY. The %1 indicates a substitution variable. The text for this substitution variable is displayed with the alert in the alert log and can vary depending on the situation.

Action: Contact your technical support.

Related Alert

Information

Related Alert Number: None

Local Response Agent (LRA) Number: 2090

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2091

SNMP Trap

Numbers

854

Event ID — 2300

Description

Severity

Cause and Action

The enclosure is unstable.

Critical / Failure / Error

Cause: The controller is not receiving a consistent response from the enclosure. There could be a firmware problem or an invalid cabling configuration. If the cables are too long, they degrade the signal.

Action: Power down all enclosures attached to the system and reboot the system. If the problem persists, upgrade the firmware to the latest supported version. You can download the most current version of the driver and firmware from the support site. Make sure the cable configuration is valid. See the hardware documentation for valid cabling configurations.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2091

SNMP Trap

Numbers

854

Event ID — 2301

Description

Severity

Cause and Action

The enclosure has a hardware error.

Critical / Failure / Error

Cause: The enclosure or an enclosure component is in a Failed or Degraded state.

134

Related Alert

Information

Action: Check the health of the enclosure and its components. Replace any hardware that is in a Failed state. See the hardware documentation for more information.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2091

SNMP Trap

Numbers

854

Event ID — 2302

Description

Severity

Cause and Action

The enclosure is not responding.

Critical / Failure / Error

Cause: The enclosure or an enclosure component is in a Failed or Degraded state.

Action: Check the health of the enclosure and its components. Replace any hardware that is in a Failed state. See the hardware documentation for more information.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2091

SNMP Trap

Numbers

854

Event ID — 2303

Description

Severity

Cause and Action

The enclosure cannot support both SAS and SATA physical disks. Physical disks may be disabled.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

851

Event ID — 2304

Description

Severity

Cause and Action

An attempt to hot plug an EMM has been detected. This type of hot plug is not supported.

OK / Normal / Informational

Cause: This alert is for informational purposes.

135

Related Alert

Information

Action: None

Clear Alert Number: None

Related Alert Number: 2211

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2305

Description

Severity

Cause and Action

The physical disk is too small to be used for a rebuild.

Warning / Non-critical

Cause: The physical disk is too small to rebuild the data.

Action: Remove the physical disk and insert a new physical disk that is the same size or larger than the disk that is being rebuilt. The new physical disk must also use the same technology (for example, SAS or SATA) as the disk being rebuilt. If the rebuild does not start automatically after you have inserted a suitable physical disk, then run the Rebuild task. See the Server Administrator Storage Management User’s Guide for more information.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: 2326

Local Response Agent (LRA) Number: 2070

SNMP Trap

Numbers

903

Event ID — 2306

Description

Severity

Cause and Action

Bad block table is 80% full.

Warning / Non-critical

Cause: The bad block table is used for remapping bad disk blocks. This table fills, as bad disk blocks are remapped. When the table is full, bad disk blocks can no longer be remapped, and disk errors can no longer be corrected. At this point, data loss can occur. The bad block table is now 80% full.

Action: Back up your data. Replace the disk generating this alert and restore from back up.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: 2307

Local Response Agent (LRA) Number: 2070

SNMP Trap

Numbers

903

Event ID — 2307

Description Bad block table is full. Unable to log block %1.

136

Severity

Cause and Action

Related Alert

Information

Critical / Failure / Error

Cause: The bad block table is used for remapping bad disk blocks. This table fills, as bad disk blocks are remapped. When the table is full, bad disk blocks can no longer be remapped and disk errors can no longer be corrected. At this point, data loss can occur. The %1 indicates a substitution variable. The text for this substitution variable is displayed with the alert in the alert log and can vary depending on the situation.

Action: Replace the disk generating this alert. If necessary, restore your data from backup.

Clear Alert Number: None

Related Alert Number: 2048

Local Response Agent (LRA) Number: 2071

SNMP Trap

Numbers

904

Event ID — 2309

Description

Severity

Cause and Action

A physical disk is incompatible.

Warning / Non-critical

Cause: You have attempted to replace a disk with another disk that is using an incompatible technology. For example, you may have replaced one side of a mirror with a SAS disk when the other side of the mirror is using SATA technology.

Action: See the hardware documentation for information on replacing disks.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2070

SNMP Trap

Numbers

903

Event ID — 2310

Description

Severity

Cause and Action

A virtual disk is permanently degraded.

Critical / Failure / Error

Cause: A redundant virtual disk has lost redundancy. This may occur when the virtual disk suffers the failure of multiple physical disks. In this case, both the source physical disk and the target disk with redundant data have failed. A rebuild is not possible because there is no redundancy.

Action: Replace the failed disks and restore from backup.

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Number: 1204

Related Alert Number: None

Local Response Agent (LRA) Number: 2081

1204

137

Event ID — 2311

Description

Severity

Cause and Action

The firmware on the EMMs is not the same version. EMM0 %1 EMM1 %2.

Warning / Non-critical

Cause: The firmware on the EMM modules is not the same version. It is required that both modules have the same version of the firmware. This alert may be caused if you attempt to insert an EMM module that has a different firmware version than an existing module. The %1 and %2 indicate a substitution variable. The text for these substitution variables is displayed with the alert in the alert log and can vary depending on the situation.

Action: Upgrade to the same version of the firmware on both EMM modules.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2090

SNMP Trap

Numbers

853

Event ID — 2312

Description

Severity

Cause and Action

A power supply in the enclosure has an AC failure.

Warning / Non-critical

Cause: The power supply has an AC failure.

Action: Replace the power supply.

Related Alert

Information

Clear Alert Number: 1003

Related Alert Number: 2122, 2324

Local Response Agent (LRA) Number: 2090

SNMP Trap

Numbers

1003

Event Id — 2313

Description

Severity

Cause and Action

A power supply in the enclosure has a DC failure.

Warning / Non-critical

Cause: The power supply has a DC failure.

Action: Replace the power supply.

Related Alert

Information

Clear Alert Number: 2323

Related Alert Number: 2122, 2333

Local Response Agent (LRA) Number: 2090

138

SNMP Trap

Numbers

1003

Event ID — 2314

Description

Severity

Cause and Action

The initialization sequence of SAS components failed during system startup. SAS management and monitoring is not possible.

Critical / Failure / Error

Cause: Storage Management is unable to monitor or manage SAS devices.

Action: Reboot the system. If problem persists, make sure you have supported versions of the drivers and firmware. Also, you may need to reinstall Storage Management or Server Administrator because of some missing installation components.

Related Alert

Information

SNMP Trap

Numbers

104

Event Id — 2315

Description

Severity

Cause and Action

Diagnostic message %1

OK / Normal / Informational

Cause: The %1 indicates a substitution variable. The text for this substitution variable is generated by the utility that ran the diagnostics and is displayed with the alert in the alert log. This text can vary depending on the situation. This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2051

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2316

Description

Severity

Cause and Action

Diagnostic message %1

Critical / Failure / Error

Cause: A diagnostics test failed. The %1 indicates a substitution variable. The text for this substitution variable is generated by the utility that ran the diagnostics and is displayed with the alert in the alert log. This text can vary depending on the situation.

Action: See the documentation for the utility that ran the diagnostics for more information

139

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2061

SNMP Trap

Numbers

754

Event ID — 2318

Description

Severity

Cause and Action

Problems with the battery or the battery charger have been detected. The battery health is poor.

Warning / Non-critical

Cause: The battery or the battery charger is not functioning properly.

Action: Replace the battery pack.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: 2188

Local Response Agent (LRA) Number: 2100

SNMP Trap

Numbers

1153

Event ID — 2319

Description

Severity

Cause and Action

Single-bit ECC error. The DIMM is degrading.

Warning / Non-critical

Cause: The DIMM is beginning to malfunction.

Action: Replace the DIMM to avoid data loss or data corruption. The DIMM is a part of the controller battery pack. See your hardware documentation for information on replacing the DIMM or contact technical support.

Related Alert

Information

Clear Alert Number: 753

Related Alert Number: 2320

Local Response Agent (LRA) Number: 2060

SNMP Trap

Numbers

753

Event Id — 2320

Description

Severity

Cause and Action

Single-bit ECC error. The DIMM is critically degraded.

Critical / Failure / Error

Cause: The DIMM is malfunctioning. Data loss or data corruption may be imminent.

140

Related Alert

Information

Action: Replace the DIMM immediately to avoid data loss or data corruption. The DIMM is a part of the controller battery pack. See your hardware documentation for information on replacing the DIMM or contact technical support.

Clear Alert Number: None

Related Alert Number: 2321

Local Response Agent (LRA) Number: 2061

SNMP Trap

Numbers

754

Event ID — 2321

Description

Severity

Cause and Action

Single-bit ECC error. The DIMM is critically nonfunctional. There is no further reporting.

Critical / Failure / Error

Cause: The DIMM is malfunctioning. Data loss or data corruption is imminent. No further alerts are generated.

Action: Replace the DIMM immediately. The DIMM is a part of the controller battery pack. See your hardware documentation for information on replacing the DIMM.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2061

SNMP Trap

Numbers

754

Event ID — 2322

Description

Severity

Cause and Action

The DC power supply is switched off.

Informational

Cause: The power supply unit is switched off. Either a user switched off the power supply unit or it is defective.

Action: Check if the power switch is turned off. If it is turned off, turn it on. If the problem persists, check if the power cord is attached and functional. If the problem is still not corrected or if the power switch is already turned on, replace the power supply unit.

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Number: 2323

Related Alert Number: None

Local Response Agent (LRA) Number: 2091

1001

141

Event ID — 2323

Description

Severity

Cause and Action

The power supply is switched on.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Status: Alert 2323 is a clear alert for alerts 2313 and 2322.

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1001

Event ID — 2324

Description

Severity

Cause and Action

The AC power supply cable has been removed.

Critical / Failure / Error

Cause: The power cable may be pulled out or removed. The power cable may also have overheated and become warped and nonfunctional.

Action: Replace the power cable.

Related Alert

Information

Clear Alert Number: 2325

Related Alert Number: None

Local Response Agent (LRA) Number: 2091

SNMP Trap

Numbers

1004

Event ID — 2325

Description

Severity

Cause and Action

The power supply cable has been inserted.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Status: Alert 2325 is a clear alert for alerts 2324 and 2312.

Related Alert Number: None

Local Response Agent (LRA) Number: None

1001

142

Event ID — 2326

Description

Severity

Cause and Action

A foreign configuration has been detected.

OK / Normal / Informational

Cause: This alert is for informational purposes. The controller has physical disks that were moved from another controller. These physical disks contain virtual disks that were created on the other controller. See the Import Foreign Configuration and Clear Foreign Configuration section in the Server Administrator

Storage Management User’s Guide for more information.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2327

Description

Severity

Cause and Action

The NVRAM has corrupted data. The controller is reinitializing the NVRAM.

Warning / Non-critical

Cause: The nonvolatile random access memory (NVRAM) is corrupt. This may occur after a power surge, a battery failure, or for other reasons. The controller is reinitializing the NVRAM. The controller properties reset to the default settings after the reinitialization is complete.

NOTE: The controller is taking the required corrective action. If this alert is generated often (such as during each reboot), replace the controller.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: 2266

Local Response Agent (LRA) Number: 2060

SNMP Trap

Numbers

753

Event ID — 2328

Description

Severity

Cause and Action

The NVRAM has corrupt data.

Warning / Non-critical

Cause: The NVRAM has corrupt data. The controller is unable to correct the situation.

Action: Replace the controller.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 20601

143

SNMP Trap

Numbers

753

Event ID — 2329

Description

Severity

Cause and Action

SAS port report: %1

Warning / Non-critical

Cause: The text for this alert is generated by the controller and can vary depending on the situation. The %1 indicates a substitution variable. The text for this substitution variable is generated by the controller and is displayed with the alert in the alert log. This text can vary depending on the situation.

Action: Run the PHY integrity test diagnostic. Make sure the cables are attached securely. If the problem persists, replace the cable with a valid cable according to SAS specifications. If the problem still persists, you may need to replace some devices such as the controller or EMM. See the hardware documentation for more information.

Related Alert

Information

SNMP Trap

Numbers

753

Event ID — 2330

Description

Severity

Cause and Action

SAS port report: %1

OK / Normal / Informational

Cause: The %1 indicates a substitution variable. The text for this substitution variable is generated by the controller and is displayed with the alert in the alert log. This text can vary depending on the situation. This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2060

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2331

Description

Severity

Cause and Action

A bad disk block has been reassigned.

OK / Normal / Informational

Cause: The disk has a bad block. Data has been readdressed to another disk block and no data loss has occurred.

Action: Monitor the disk for other alerts or indications of poor health. For example, you may receive alert

2306. Replace the disk if you suspect there is a problem.

144

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2332

Description

Severity

Cause and Action

A controller hot plug has been detected.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2334

Description

Severity

Cause and Action

Controller event log: %1

OK / Normal / Informational

Cause: The %1 indicates a substitution variable. The text for this substitution variable is generated by the controller and is displayed with the alert in the alert log. This text is from events in the controller event log that were generated while Storage Management was not running. This text can vary depending on the situation. This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751, 801, 851, 901, 951, 1001, 1051, 1101, 1151, 1201

Event ID — 2335

Description

Severity

Cause and Action

Controller event log: %1.

Warning / Non-critical

Cause: The %1 indicates a substitution variable. The text for this substitution variable is generated by the controller and is displayed with the alert in the alert log. This text is from events in the controller event log

145

Related Alert

Information that were generated while Storage Management was not running. This text can vary depending on the situation.

Action: If there is a problem, review the controller event log and the Server Administrator alert log for significant events or alerts that may assist in diagnosing the problem. Check the health of the storage components. See the hardware documentation for more information.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2060

SNMP Trap

Numbers

753

Event ID — 2336

Description

Severity

Cause and Action

Controller event log: %1.

Critical / Failure / Error

Cause: The %1 indicates a substitution variable. The text for this substitution variable is generated by the controller and is displayed with the alert in the alert log. This text is from events in the controller event log that were generated while Storage Management was not running. This text can vary depending on the situation.

Action: See the hardware documentation for more information.

Related Alert

Information

SNMP Trap

Numbers

754

Event ID — 2337

Description

Severity

Cause and Action

The controller is unable to recover cached data from the battery backup unit (BBU).

Critical / Failure / Error

Cause: The controller was unable to recover data from the cache. This may occur when the system is without power for an extended period when the battery is discharged.

Action: Check if the battery is charged and in good health. When the battery charge is unacceptably low, it cannot maintain cached data. Check if the battery has reached its recharge limit. The battery may need to be recharged or replaced.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2061

SNMP Trap

Numbers

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2101

1154

146

Event ID — 2338

Description

Severity

Cause and Action

The controller has recovered cached data from the BBU.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1151

Event ID — 2339

Description

Severity

Cause and Action

The factory default settings have been restored.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2340

Description

Severity

Cause and Action

The BGI completed with uncorrectable errors.

Critical / Failure / Error

Cause: The BGI task encountered errors that cannot be corrected. The virtual disk contains physical disks that have unusable disk space or disk errors that cannot be corrected.

Action: Replace the physical disk that contains the disk errors. Review other alert messages to identify the physical disk that has errors. If the virtual disk is redundant, you can replace the physical disk and continue using the virtual disk. If the virtual disk is non-redundant, you may need to recreate the virtual disk after replacing the physical disk. After replacing the physical disk, run Check Consistency to check the data.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2081

147

SNMP Trap

Numbers

1204

Event ID — 2341

Description

Severity

Cause and Action

The Check Consistency made corrections and completed.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

SNMP Trap

Numbers

1201

Event ID — 2342

Description

Severity

Cause and Action

The Check Consistency found inconsistent parity data. Data redundancy may be lost.

Warning / Non-critical

Cause: The data on a source disk and the redundant data on a target disk is inconsistent.

Action: Restart the Check Consistency task. If you receive this alert again, check the health of the physical disks included in the virtual disk. Review the alert messages for significant alerts related to the physical disks. If you suspect that a physical disk has a problem, replace it and restore from backup.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

Clear Alert Number: None

Related Alert Number: 2341, 2343

Local Response Agent (LRA) Number: 2080

SNMP Trap

Numbers

1203

Event ID — 2343

Description

Severity

Cause and Action

The Check Consistency logging of inconsistent parity data is disabled.

Warning / Non-critical

Cause: The Check Consistency can no longer report errors in the parity data.

Action: See the hardware documentation for more information.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2080

148

SNMP Trap

Numbers

1203

Event ID — 2344

Description

Severity

Cause and Action

The virtual disk initialization terminated.

Warning / Non-critical

Cause: A user has cancelled the virtual disk initialization.

Action: Restart the initialization.

Related Alert

Information

SNMP Trap

Numbers

1203

Event ID — 2345

Description

Severity

Cause and Action

The virtual disk initialization failed.

Critical / Failure / Error

Cause: The controller cannot communicate with attached devices. A disk may be removed or contain errors.

Cables may also be loose or defective.

Action: Verify the health of attached devices. Review the Alert Log for significant events. Make sure the cables are attached securely. See the Cables Attached Correctly section for more information on checking the cables.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2080

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2081

SNMP Trap

Numbers

1204

Event ID — 2346

Description

Severity

Cause and Action

Error occurred: %1.

Warning / Non-critical

Cause: A physical device may have an error. The %1 indicates a substitution variable. The text for this substitution variable is generated by the firmware and is displayed with the alert in the alert log. This text can vary depending on the situation.

Action: Verify the health of attached devices. Review the alert log for significant events. Run the PHY integrity diagnostic tests. You may need to replace faulty hardware. Make sure that the cables are attached securely. See the hardware documentation for more information.

149

Related Alert

Information

Clear Alert Number: None

Related Alert Number: 2048, 2050, 2056, 2057, 2076, 2079, 2081, 2083, 2095, 2129, 2201, 2203, 2270,

2282, 2369

Local Response Agent (LRA) Number: 2070

SNMP Trap

Numbers

903

Event ID — 2347

Description

Severity

Cause and Action

The rebuild failed due to errors on the source physical disk.

Critical / Failure / Error

Hardware RAID: Cause and Action

Cause: You are attempting to rebuild data that resides on a defective disk.

Action: Replace the source disk and restore from backup.

Software RAID:

• Perform a backup with the Verify option.

• If the file backup fails, try to restore the failed file from a previous backup.

• When the backup with the Verify option is complete without any errors, delete the Virtual Disk.

• Recreate a new Virtual Disk with new drives.

• Restore the data from backup.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: 2195, 2346

Local Response Agent (LRA) Number: 2071

SNMP Trap

Numbers

904

Event ID — 2348

Description

Severity

Cause and Action

The rebuild failed due to errors on the target physical disk.

Critical / Failure / Error

Cause:You are attempting to rebuild data on a disk that is defective.

Action: Replace the target disk. If a rebuild does not automatically start after replacing the disk, initiate the

Rebuild task. You may need to assign the new disk as a hot spare to initiate the rebuild.

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Number: None

Related Alert Number: 2195, 2346

Local Response Agent (LRA) Number: 2071

904

150

Event ID — 2349

Description

Severity

Cause and Action

A bad disk block could not be reassigned during a write operation.

Critical / Failure / Error

Cause: A write operation could not complete because the disk contains bad disk blocks that could not be reassigned. Data loss may have occurred and data redundancy may also be lost.

Action: Replace the disk.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: 2346

Local Response Agent (LRA) Number: 2071

SNMP Trap

Numbers

904

Event ID — 2350

Description

Severity

Cause and Action

There was an unrecoverable disk media error during the rebuild or recovery operation.

Critical / Failure / Error

Cause: The rebuild or recovery operation encountered an unrecoverable disk media error.

Action: Replace the disk.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: 2095, 2273

Local Response Agent (LRA) Number: 2071

SNMP Trap

Numbers

904

Event ID — 2351

Description

Severity

Cause and Action

A physical disk is marked as missing.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None.

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Number: 2352

Related Alert Number: None

Local Response Agent (LRA) Number: None

901

151

Event ID — 2352

Description

Severity

Cause and Action

A physical disk that was marked as missing has been replaced.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Status: Alert 2352 is a clear alert for alert 2351.

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2353

Description

Severity

Cause and Action

The enclosure temperature has returned to normal.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Status: Alert 2353 is a clear alert for alerts 2100 and 2101.

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1051

Event ID — 2354

Description

Severity

Cause and Action

Enclosure firmware download in progress.

OK / Normal / Informational

Cause: This alert is provided for informational purposes.

Action: None

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

851

152

Event ID — 2355

Description

Severity

Cause and Action

Enclosure firmware download failed.

Warning / Non-critical

Cause: The system was unable to download firmware to the enclosure. The controller may have lost communication with the enclosure. There may have been problems with the data transfer or the download media may be corrupt.

Action: Attempt to download the enclosure firmware again. If problems continue, verify that the controller can communicate with the enclosure. Make sure that the enclosure is powered on. Check the cables. See the Cables Attached Correctly section for more information on checking the cables. Verify the health of the enclosure and its components. To verify the health of the enclosure, select the enclosure object in the tree view. The Health subtab displays a red X or yellow exclamation point for enclosure components that are failed or degraded.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2090

SNMP Trap

Numbers

853

Event ID — 2356

Description

Severity

Cause and Action

SAS SMP Communications error %1.

Critical / Failure / Error

Cause: The text for this alert is generated by the firmware and can vary depending on the situation. The reference to SMP in this text refers to SAS Management Protocol.

Action: There may be a SAS topology error. See the hardware documentation for information on correct

SAS topology configurations. There may be problems with the cables such as a loose connection or an invalid cabling configuration. See the Cables Attached Correctly section for more information on checking the cables. See the hardware documentation for information on correct cabling configurations. Verify that the firmware is a supported version.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2061

SNMP Trap

Numbers

754

Event ID — 2357

Description

Severity

Cause and Action

SAS expander error: %1.

Critical / Failure / Error

Cause: The %1 indicates a substitution variable. The text for this substitution variable is generated by the firmware and is displayed with the alert in the alert log. This text can vary depending on the situation.

153

Related Alert

Information

Action: There may be a problem with the enclosure. Check the health of the enclosure and its components by selecting the enclosure object in the tree view. The Health subtab displays a red X or yellow exclamation point for enclosure components that are Failed or Degraded. See the enclosure documentation for more information.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2061

SNMP Trap

Numbers

754

Event ID — 2358

Description

Severity

Cause and Action

The battery charge cycle is complete.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1151

Event ID — 2359

Description

Severity

Cause and Action

Disk found is not supplied by an authorized hardware provider.

Warning / Non-critical

Cause: The physical disk does not comply with the standards set and is not supported.

Action: Replace the physical disk with a physical disk that is supported.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2070

SNMP Trap

Numbers

903

Event ID — 2360

Description

Severity

Cause and Action

A user has discarded data from the controller cache.

OK / Normal / Informational

Cause: This alert is for informational purposes.

154

Related Alert

Information

Action: None.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2361

Description

Severity

Cause and Action

Physical disk(s) that are part of a virtual disk have been removed while the system was shut down. This removal was discovered during system start-up.

Warning

Cause: This alert is for informational purposes.

Action: None.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

753

Event ID — 2362

Description

Severity

Cause and Action

Physical disk(s) have been removed from a virtual disk. The virtual disk is in Failed state during the next system reboot.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2364

Description

Severity

Cause and Action

All virtual disks are missing from the controller. This situation was discovered during system start-up.

Warning

Cause: This alert is for informational purposes.

155

Related Alert

Information

Action: None

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

753

Event ID — 2366

Description

Severity

Cause and Action

Dedicated spare imported as global due to missing arrays.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2367

Description

Severity

Cause and Action

Rebuild is not possible because mixing of different media type (SSD/HDD) and bus protocols (SATA/SAS) is not supported on the same virtual disk.

Warning / Non-critical

Cause: The physical disk is using an incompatible technology.

Action: All physical disks in the virtual disk must use the same technology. You cannot use both SAS and

SATA physical disks in the same virtual disk. Remove the physical disk and insert a new physical disk that uses the correct technology. If the rebuild does not start automatically after you have inserted a suitable physical disk, then run the Rebuild task.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: 2326

Local Response Agent (LRA) Number: 2070

SNMP Trap

Numbers

903

Event ID — 2368

Description

Severity

The SCSI Enclosure Processor (SEP) has been rebooted as part of the firmware download operation and is unavailable until the operation completes.

OK / Normal / Informational

156

Cause and Action

Related Alert

Information

Cause: This alert is for informational purposes.

Action: None

Clear Alert Number: None

Related Alert Number: 2049, 2052, 2162, 2292

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

851

Event ID — 2369

Description

Severity

Cause and Action

Virtual Disk Redundancy has been degraded.

OK / Normal / Informational

Cause: A physical disk in a RAID 6 virtual disk has either failed or been removed.

Action: Replace the missing or failed physical disk.

Related Alert

Information

Clear Alert Number: 2121

Related Alert Number: 2048, 2049, 2050, 2076, 2346

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2370

Description

Severity

Cause and Action

Redundant Path View cleared.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2371

Description

Severity

Cause and Action

Attempted import of Unsupported Virtual Disk type RAID%1.

OK / Normal / Informational

Cause: This alert is for informational purposes.

Action: None.

157

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2372

Description

Severity

Cause and Action

Attempted import of Virtual Disk exceeding the limit supported on the controller.

OK / Normal / Informational

Cause: This alert is provided for informational purposes.

Action: None.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2373

Description

Severity

Cause and Action

Attempted import of unsupported Virtual Disk type RAID %1.

OK / Normal / Informational

Cause: This alert is provided for informational purposes. User is attempting to import a foreign virtual disk with unsupported RAID level on the controller.

Action: None.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2374

Description

Severity

Cause and Action

Attempted import of Virtual Disk with missing span.

OK / Normal / Informational

Cause: This alert is provided for informational purposes and is displayed when you attempt to import a foreign virtual disk with a missing span.

Action: None.

158

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2375

Description

Severity

Cause and Action

Attempted import of Virtual Disk with missing physical disk.

OK / Normal / Informational

Cause: User is attempting to import a foreign virtual disk with a missing physical disk. This alert is provided for informational purposes.

Action: None.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2376

Description

Severity

Cause and Action

Attempted import of Virtual Disk with stale physical disk.

OK / Normal / Informational

Cause: User is attempting to import a foreign virtual disk with a stale physical disk. This alert is provided for informational purposes.

Action: None.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2377

Description

Severity

Cause and Action

Attempted import of an orphan drive.

OK / Normal / Informational

Cause: User is attempting to import an orphan drive. This alert is provided for informational purposes.

Action: None.

159

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2378

Description

Severity

Cause and Action

Attempted import of an incompatible physical drive.

OK / Normal / Informational

Cause: User is attempting to import an incompatible physical drive. This alert is provided for informational purposes.

Action: None.

Related Alert

Information

SNMP Trap

Numbers

751

Event ID — 2379

Description

Severity

Cause and Action

An overflow of the foreign configuration has occurred. You can import the foreign configuration in multiple attempts.

Warning

Cause: This alert is provided for informational purposes.

Action: None.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

753

Event ID — 2380

Description

Severity

Cause and Action

Foreign configuration has been partially imported. Some configuration failed to import.

OK / Normal / Informational

Cause: This alert is provided for informational purposes.

Action: None.

160

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2381

Description

Severity

Cause and Action

Controller preserved cache is recovered.

OK / Normal / Informational

Cause: This alert is provided for informational purposes.

Action: None.

Related Alert

Information

SNMP Trap

Numbers

751

Event ID — 2382

Description

Severity

Cause and Action

An unsupported configuration was detected. The controller does not support physical disks of type SSD:

<Physical DiskID>, <controller- ID>, <connector- ID>

Warning / Non-critical

Cause: A physical disk of media type SSD is attached to a controller that does not support SSD disks.

Action: Replace the unsupported physical disk with a physical disk of media type HDD.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

903

Event ID — 2383

Description

Severity

Cause and Action

The Information level set for the hot spare protection policy is violated for the Virtual Disk.

OK / Normal / Informational

Cause: The number of physical disks you specified for the hot spare protection policy is violated.

Action: Reassign the number of hot spares as specified in the protection policy for that RAID level.

Related Alert

Information

Clear Alert Number: 2195

161

SNMP Trap

Numbers

1201

Event ID — 2384

Description

Severity

Cause and Action

The Warning level set for the hot spare protection policy is violated for the Virtual Disk.

Warning / Non-critical

Cause: The number of physical disks you specified for the hot spare protection policy is violated.

Action: Reassign the number of hot spares as specified in the protection policy for that RAID level.

Related Alert

Information

Related Alert Number: None

Local Response Agent (LRA) Number: None

Clear Alert Number: 2195

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1203

Event Id — 2385

Description

Severity

Cause and Action

The Critical level set for the hot spare protection policy is violated for the Virtual Disk.

Critical / Failure / Error

Cause: The number of physical disks you specified for the hot spare protection policy is violated.

Action: Reassign the number of hot spares as specified in the protection policy for that RAID level.

Related Alert

Information

Clear Alert Number: 2195

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1204

Event ID — 2386

Description

Severity

Cause and Action

Drive could not be assigned as Dedicated Hot Spare.

Informational

Cause: The assignment of a Dedicated Hot Spare fails as the disk is invalid.

Action: None.

Related Alert

Information

Clear Alert Number: 2195

Related Alert Number: None

162

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2387

Description

Severity

Cause and Action

A virtual disk bad block medium error is detected.

Critical / Failure / Error

Cause: Virtual disk bad blocks are due to presence of unrecoverable bad blocks on one or more member physical disks.

Action:

1.

Perform a backup of the virtual disk with the Verify option selected. One of the following can occur:

• Backup operation fails. In this case, restore the file from a previous backup. After restoring the file, run Patrol Read and check for bad blocks. If more bad blocks exist, proceed to step 2.

• Backup operation completes without error. This indicates that there are no bad blocks on your virtual disk.

• Backup operation displays bad blocks. This indicates that the bad blocks are located in a nondata area. Proceed to step 2.

2.

To clear these bad blocks, execute the Clear Virtual Disk Bad Blocks task.

3.

Run Patrol Read to ensure no new bad blocks are found.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2081

SNMP Trap

Numbers

1204

Event ID — 2388

Description

Severity

Cause and Action

The Controller Encryption Key is destroyed.

OK / Normal / Informational

Cause: The Controller Encryption Key is destroyed.

Action: None.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2389

Description The virtual disk bad block medium error is cleared.

163

Severity

Cause and Action

Related Alert

Information

OK / Normal / Informational

Cause: Virtual disk bad blocks are cleared.

Action: None.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2390

Description

Severity

Cause and Action

The Cryptographic Erase operation is performed on the physical disk.

OK / Normal / Informational

Cause: Instant Encrypt Erase operation is successful on Self Encryption Disks (SEDs.)

Action: None.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2392

Description

Severity

Cause and Action

The drive Encryption Key is invalid.

Warning / Non-critical

Cause: The controller failed to verify the specified Passphrase.

Action: Enter a correct Passphrase.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: 2060

SNMP Trap

Numbers

753

Event ID — 2393

Description

Severity

The virtual disk is encrypted.

OK / Normal / Informational

164

Cause and Action

Related Alert

Information

Cause: The Encrypted virtual disk operation on normal virtual disk (created using Self encrypting disks only) is successful.

Action: None.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2394

Description

Severity

Cause and Action

Persistent Hot Spare is enabled.

OK / Normal / Informational

Cause: The Persistent Hot Spare option is enabled.

Action: None.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2395

Description

Severity

Cause and Action

Persistent Hot Spare is disabled.

OK / Normal / Informational

Cause: The Persistent Hot Spare option is disabled.

Action: None.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2396

Description

Severity

Cause and Action

The Check Consistency detected uncorrectable multiple medium errors.

Critical / Failure / Error

Cause: The Check Consistency task detects uncorrectable multiple errors.

165

Related Alert

Information

Action: Replace the failed physical disk. You can identify the failed disk by locating the disk that has a red

“X” for its status. Rebuild the physical disk. When finished, restart the check consistency operation.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1204

Event ID — 2397

Description

Severity

Cause and Action

The Check Consistency completed with uncorrectable errors.

Critical / Failure / Error

Cause: The Check Consistency task detected uncorrectable multiple errors.

Action: Replace the failed physical disk. You can identify the failed disk by locating the disk that has a red

“X” for its status. Rebuild the physical disk. When finished, restart the check consistency operation.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1204

Event ID — 2398

Description

Severity

Cause and Action

The Manage Physical Disk Power property(s) changed.

OK / Normal / Informational

Cause: The Manage Physical Disk Power properties are changed.

Action: None.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2399

Description

Severity

Cause and Action

The Physical Disk Power status changed from 1% to 2%.

OK / Normal / Informational

Cause: The physical disk power status is changed from one state to another. A physical disk can have the following power statuses: spun down, transition, and spun up.

166

Related Alert

Information

Action: None.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2400

Description

Severity

Cause and Action

Physical disk configuration data updated as it was stale.

Informational

Cause: The physical disk configuration data is updated because it was outdated.

Action: None.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2401

Description

Severity

Cause and Action

Configuration command could not be committed to disk. Configuration has to be re applied.

Failure / Error

Cause: The virtual disk configuration command did not succeed.

Action: Check for the recent configuration that has not taken effect. Re-apply the configuration.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

754

Event ID — 2402

Description

Severity

Cause and Action

Changing the Physical Disk Power status from 1% to 2% failed.

Failure / Error

Cause: When changing the Physical Disk Power status fails.

Action: Replace the physical disk.

167

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

904

Event ID — 2403

Description

Severity

Cause and Action

Virtual Disk is available.

OK / Normal / Informational

Cause: The operating system detects the newly created virtual disk.

Action: None.

NOTE: This alert also appears when a CacheCade is created but is not available for the operating system (as it is a CacheCade and not a Virtual Disk).

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2404

Description

Severity

Cause and Action

Virtual Disk is not available.

OK / Normal / Informational

Cause: The operating system does not detect the newly created virtual disk.

Action: Wait for some time.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2405

Description

Severity

Cause and Action

Command timeout on physical disk.

Warning

Cause: The spundown physical disks take more time than the timeout period and the configuration commands are timed out.

Action: None.

168

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

903

Event ID — 2407

Description

Severity

Cause and Action

Controller Encryption mode is enabled in LKM.

Informational

Cause: The Local Key Management (LKM) encryption mode is enabled.

Action: None.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2411

Description

Severity

Cause and Action

Controller LKM Encryption key is changed.

Informational

Cause: Using Manage Encryption Key operations, encryption key is changed.

Action: None.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2412

Description

Severity

Cause and Action

Controller CacheCade is resized.

Informational

Cause: This alert is provided for informational purposes.

Action: None.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

169

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2413

Description

Severity

Cause and Action

Controller CacheCade is created.

Informational

Cause: This alert is provided for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2414

Description

Severity

Cause and Action

Controller CacheCade is deleted.

Informational

Cause: This alert is provided for informational purposes.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2415

Description

Severity

Cause and Action

Controller battery is discharging.

Informational

Cause: The battery learn cycle has started.

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

170

SNMP Trap

Numbers

1151

Event ID — 2416

Description

Severity

Cause and Action

Disk medium error detected.

Warning / Non-critical

Cause: A part of the physical disk is damaged.

Action: None.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

903

Event ID — 2417

Description

Severity

Cause and Action

There is an unrecoverable medium error detected on virtual disk.

Critical / Failure / Error

Cause: Unrecoverable medium error found on one or more member physical disks of a virtual disk.

Action: Perform a backup of the virtual disk with the Verify option selected. If the Backup operation is successful, it indicates that the un-recoverable medium did not affect user data.

If the Backup operation fails, restore the file from a previous backup. After restoring the file, run check consistency operation:

• If the consistency check is successful, no further action is required.

• If the consistency check finds and unrecoverable medium error, it means that the medium error is located in non-user data. No further action is required as, writing data to the location of the medium error fixes the problem.

NOTE: If the unrecoverable medium error has not been corrected, it may be reported again by the system. This error can be fixed by writing data on the affected area or deleting and recreating the

Virtual Disk as demonstrated in the following procedure.

1.

Back up the data.

2.

Delete the Virtual Disk.

3.

Recreate the Virtual Disk using the same parameters like size, RAID level, disks, etc.

4.

Restore data.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1204

171

Event ID — 2418

Description

Severity

Cause and Action

Disk medium error on virtual disk has been corrected

Informational

Cause: This alert is for informational purposes.

Action: None.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201

Event ID — 2425

Description

Severity

Cause and Action

State change on Physical disk from READY to Non-RAID.

Informational

Cause: User triggered action.

Action: Configure the drive to be non-raid using CLI/GUI.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2426

Description

Severity

Cause and Action

State change on Physical disk from Non- RAID to READY.

Informational

Cause: User triggered action.

Action: Configure the drive to be ready using CLI/GUI.

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

901

172

Event ID — 2429

Description

Severity

Cause and Action

Drive Prepared for Removal.

Informational

Cause: User triggered action.

Action: Execute "Prepare to Remove" task from UI in a PCIeSSD setup

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2430

Description

Severity

Cause and Action

Physical Device Log Exported.

Informational

Cause: User triggered action.

Action: Execute export log for physical device.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2431

Description

Severity

Cause and Action

Physical Device Full Initialization completed.

Informational

Cause: User triggered task.

Action: None.

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

901

173

Event ID — 2432

Description

Severity

Cause and Action

The PCIeSSD device was found to be in security locked state. Full initialization has to be done on the security locked drive to recover the drive in usable state.

Warning

Cause: Last full initialization was stopped for some reason and hence the device is in security locked state.

Action: Run full initialization to recover the device.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

902

Event ID — 2433

Description

Severity

Cause and Action

Physical Device is at %1% of warranted device wear-out limit.

Informational

Cause: User triggered task.

Action: None.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2434

Description

Severity

Cause and Action

Physical Device has reached or exceeded its warranted device wear-out limit.

Warning

Cause: User triggered task.

Action: None.

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

903

174

Event ID — 2435

Description

Severity

Cause and Action

Physical Device is approaching read-only mode.

Informational

Cause: User triggered task.

Action: None.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2436

Description

Severity

Cause and Action

Physical Device is in read-only mode.

Critical

Cause: User triggered task.

Action: None.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

904

Event ID — 2437

Description

Severity

Cause and Action

The physical device blink has initiated.

Informational

Cause: User triggered task.

Action: None.

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

901

175

Event ID — 2438

Description

Severity

Cause and Action

The physical device blink has ceased.

Informational

Cause: User triggered task.

Action: None.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2440

Description

Severity

Cause and Action

The physical device available space is below threshold.

Warning

Cause: None

Action: None

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

904

Event ID — 2441

Description

Severity

Cause and Action

The PCIe solid state device identified in the message has turned off because the critical temperature threshold of the device was exceeded.

Error

Cause: None

Action: Contact your service provider.

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

904

176

Event ID — 2442

Description

Severity

Cause and Action

The reliability of the PCIe solid state device identified in the message degraded. Data loss is possible.

Error

Cause: None

Action: Back up the data on the device, and contact your service provider for further instructions.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

904

Event ID — 2443

Description

Severity

Cause and Action

The volatile memory backup device on the PCIe solid state device identified in the message is no longer functional. Data loss is possible.

Error

Cause: None

Action: Back up the data on the device, and contact your service provider for further instructions.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

904

Event ID — 2444

Description

Severity

Cause and Action

The Patrol Read operation was manually stopped before completion.

Informational

Cause: User Triggered Task

Action: If desired, restart the Patrol Read operation at a later time.

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

901

177

Event ID — 2445

Description

Severity

Cause and Action

Cryptographic Erase operation is successfully completed on the physical disk drive identified in the message.

Informational

Cause: User Triggered Task

Action: No response action is required.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2446

Description

Severity

Cause and Action

The controller identified in the message has been changed to a new personality mode (HBA or RAID).

Informational

Cause: User Triggered Task

Action: No response action is required.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

751

Event ID — 2447

Description

Severity

Cause and Action

The Auto Configure operation is successfully completed on the controller identified in the message.

Informational

Cause: User Triggered Task

Action: No response action is required.

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

751

178

Event ID — 2448

Description

Severity

Cause and Action

The Remaining Rated Write Endurance (RRWE) Threshold for SAS and SATA SSD is set to <value>.

Informational

Cause: The Remaining Rated Write Endurance (RRWE) Threshold for SAS and SATA solid-state drives has been modified.

Action: No response action is required.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

101

Event ID — 2449

Description

Severity

Cause and Action

The Remaining Rated Write Endurance (RRWE) Threshold for PCIe SSDs is set to <value>.

Informational

Cause: The Remaining Rated Write Endurance (RRWE) Threshold for PCIe solid-state drives has been modified.

Action: No response action is required.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

101

Event ID — 2450

Description

Severity

Cause and Action

The disk write cache policy is changed for Non-RAID disks.

Informational

Cause: The disk write cache policy of non-RAID physical disk drives on the <controller name> is changed.

Action: No response action is required.

Related Alert

Information

SNMP Trap

Numbers

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

751

179

Event ID — 2451

Description

Severity

Cause and Action

The disk write cache policy is changed.

Informational

Cause: The disk write cache policy of physical disk drive <drive name> is changed..

Action: No response action is required.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2454

Description

Severity

Cause and Action

Unable to complete the Cryptographic erase operation on the physical disk drive <drive name>.

Warning

Cause: The cryptographic erase operation cannot be completed on the physical disk drive identified in the message.

Action: No response action is required.

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2699

Description

Severity

Cause and Action

Related Alert

Information

Connection to CFM lost! : FluidCache

Error

No action required.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

.

SNMP Trap

Numbers

1604

180

Event ID — 2700

Description

Severity

Cause and Action

Related Alert

Information

The following journal mirror is available. %1

Information

No action required.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1601

Event ID — 2701

Description

Severity

Cause and Action

Related Alert

Information

The following journal mirror is being replaced.(wwn ) %1 : FluidCache.

Information

No action required.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1601

Event ID — 2702

Description

Severity

Cause and Action

Related Alert

Information

The following journal mirror has failed. (wwn) %1 : FluidCache.

Warning

No action required.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1603

Event ID — 2703

Description

Severity

Cause and Action

There are not enough journal mirrors available to operate. : FluidCache.

Error

To resolve the issue, you must ensure that there are at least two journal mirrors that are accessible. You must activate either one or more failed cache devices or use the fldc_restore utility to rebuild the node.

181

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1604

Event ID — 2704

Description

Severity

Cause and Action

Related Alert

Information

The cluster ID in the journal does not match the cluster ID in the configuration file. : FluidCache.

Error

Service is required. Contact Technical Support.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1604

Event ID — 2705

Description

Severity

Cause and Action

Related Alert

Information

The journal could not be read/written. : FluidCache.

Error

Service is required. Contact Technical Support.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1604

Event ID — 2874

Description

Severity

Cause and Action

Related Alert

Information

The following Cache Device has no associated server in the configuration: %1 : FluidCache.

Warning

There is a cache device specified in the configuration with no associated cache server configured.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

903

182

Event ID — 2875

Description

Severity

Cause and Action

Related Alert

Information

The following Disk is beginning flushing.(wwn) %1 (path) %2 : FluidCache.

Information

No action required.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2876

Description

Severity

Cause and Action

Related Alert

Information

The following Disk has finished flushing. (wwn) %1 (path) %2 : FluidCache.

Information

No action required.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2900

Description

Severity

Cause and Action

Related Alert

Information

The following cache device has failed. (wwn) %1 (path) %2 : FluidCache.

Error

Replace the failed device.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

904

Event ID — 2901

Description

Severity

Cause and Action

The following storage device is either inaccessible or failed. (wwn) %1 (path) %2 : FluidCache.

Error

If the device is inaccessible, restore connectivity. If the device has failed, replace it.

183

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1204, 1504

Event ID — 2902

Description

Severity

Cause and Action

Related Alert

Information

The following storage device has had transient failures. (wwn) %1 (path) %2 : FluidCache.

Information

No action required.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201, 1501

Event ID — 2903

Description

Severity

Cause and Action

Related Alert

Information

The following cache device has been registered. (ww n) %1 (path) %2 : FluidCache.

Information

No action required.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2904

Description

Severity

Cause and Action

Related Alert

Information

The following cache device has been removed. (wwn ) %1 (path) %2 : FluidCache.

Information

No action required.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

184

Event ID — 2905

Description

Severity

Cause and Action

Related Alert

Information

The following cache device is being removed. (wwn ) %1 (path) %2 : FluidCache.

Information

No action required.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2906

Description

Severity

Cause and Action

Related Alert

Information

Caching is being removed for the following storage device. (wwn) %1 (path) %2 : FluidCache.

Information

No action required.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201, 1501, 1601

Event ID — 2907

Description

Severity

Cause and Action

Related Alert

Information

Caching has been enabled on the following storage device. (wwn) %1 (path) %2 : FluidCache.

Information

No action required.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201, 1501

Event ID — 2908

Description

Severity

Cause and Action

The following cache device has been disconnected. (wwn) %1 (path) %2 : FluidCache.

Information

No action required.

185

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2909

Description

Severity

Cause and Action

Related Alert

Information

The following journal mirror is available. %1The following storage device is in an unknown state.(wwn) %1

(path) %2 : FluidCache.

Warning

Service is required. Contact Technical Support.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1203, 1503

Event ID — 2910

Description

Severity

Cause and Action

Related Alert

Information

Caching has been disabled for the following storage device. (wwn) %1 (path) %2 : FluidCache.

Information

No action required.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1201, 1501, 1601

Event ID — 2911

Description

Severity

Cause and Action

Related Alert

Information

The following cached LUN has had a failure. (wwn) %1 (path) %2 : FluidCache.

Error

Service is required. Contact Technical Support.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1404

186

Event ID — 2912

Description

Severity

Cause and Action

Related Alert

Information

Resilvering for the following cache device is complete .(wwn) %1 (path) %2 : FluidCache.

Information

No action required.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2913

Description

Severity

Cause and Action

Related Alert

Information

The following failed cache device has completed recovery. (wwn) %1 (path) %2 : FluidCache.

Information

No action required.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

901

Event ID — 2914

Description

Severity

Cause and Action

Related Alert

Information

A valid permanent license is installed.: FluidCache.

Information

No action required.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1601

Event ID — 2915

Description

Severity

Cause and Action

No valid license is installed.: FluidCache.

Error

A valid license must be installed.

187

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1604

Event ID — 2916

Description

Severity

Cause and Action

Related Alert

Information

Running on an evaluation license. Days remaining %1 (days): FluidCache.

Information

A permanent license should be purchased.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1601

Event ID — 2917

Description

Severity

Cause and Action

Related Alert

Information

Running on an expired evaluation license. No configuration changes will be allowed. Expired days: % 1:

FluidCache.

Error

A permanent license must be installed.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1604

Event ID — 2918

Description

Severity

Cause and Action

Related Alert

Information

Running on an expired evaluation license. Caching functionality is disabled. Expired days: % 1: FluidCache

Error

A permanent license must be installed.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1604

188

Event ID — 2919

Description

Severity

Cause and Action

Related Alert

Information

Running on an expired/invalid license. Configuration changes are disabled.: FluidCache.

Error

A valid permanent license must be installed.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1604

Event ID — 2920

Description

Severity

Cause and Action

Related Alert

Information

A license has been installed.: FluidCache.

Information

No action required.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1601

Event ID — 2921

Description

Severity

Cause and Action

Related Alert

Information

A license has been removed.: FluidCache.

Information

A license should be installed.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1601

Event ID — 2922

Description

Severity

Cause and Action

Not enough memory to run necessary services.: FluidCache.

Error

You must run on a system with adequate memory.

189

Related Alert

Information

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1604

Event ID — 2923

Description

Severity

Cause and Action

Related Alert

Information

One or more cache devices are missing. Cache is hung.: FluidCache.

Error

To resolve the issue, insert the missing cache device. If the cache device was unplugged, reactivate it.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

.

SNMP Trap

Numbers

1604

Event ID — 2924

Description

Severity

Cause and Action

Related Alert

Information

All cache devices have been found and registered.: FluidCache.

Information

No action required.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1601

Event ID — 2930

Description

Severity

Cause and Action

Related Alert

Information

Even though caching was enabled in write-back mode, it is currently operating in write-through mode.:

FluidCache.

Warning

To resolve the issue, add a PCIe SSD to the cache pool.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

190

SNMP Trap

Numbers

1203, 1503, 1603

Event ID — 2931

Description

Severity

Cause and Action

Related Alert

Information

Even though caching was enabled in write-back or write-through mode, it is currently operating in passthrough mode.: FluidCache.

Warning

To resolve the issue, add one or more PCIe SSDs to the cache pool.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1203, 1503, 1603

Event ID — 2932

Description

Severity

Cause and Action

Related Alert

Information

Caching is no longer degraded to write-through mode and is now operating in write-back mode.: FluidCache.

Warning

No action required.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1203, 1503, 1603

Event ID — 2933

Description

Severity

Cause and Action

Related Alert

Information

Caching is no longer degraded to pass-through mode and is now operating in its configured mode.:

FluidCache.

Warning

No action required.

Clear Alert Number: None

Related Alert Number: None

Local Response Agent (LRA) Number: None

SNMP Trap

Numbers

1203, 1503, 1603

191

System Event Log Messages for IPMI Systems

The tables in this chapter list the system event log (SEL) messages, their severity, and cause.

NOTE: For corrective actions, see the appropriate documentation.

Temperature Sensor Events

The temperature sensor event messages help protect critical components by alerting the systems management console when the temperature rises inside the chassis. These event messages use additional variables, such as sensor location, chassis location, previous state, and temperature sensor value or state.

Table 5. Temperature Sensor Events

Event Message

<Sensor Name/Location> temperature sensor detected a warning <Reading>.

Severity

<Sensor Name/Location> temperature sensor detected a failure <Reading> where <Sensor Name/Location> is the entity that this sensor is monitoring.

For example, "PROC Temp" or "Planar

Temp." Reading is specified in degree

Celsius. For example 100 C.

Critical

Warning

Cause

Temperature of the backplane board, system board, or the carrier in the specified system <Sensor Name/

Location> exceeded the critical threshold.

<Sensor Name/Location> temperature sensor returned to warning state

<Reading>.

<Sensor Name/Location> temperature sensor returned to normal state <Reading>.

The <Sensor Name/ Location> temperature is less than the lower warning threshold.

The <Sensor Name/ Location> temperature is less than the lower critical threshold.

Warning

Information

Warning

Critical

The <Sensor Name/ Location> temperature is greater than the upper warning threshold.

Warning

The <Sensor Name/ Location> temperature is greater than the upper critical threshold.

Critical

Temperature of the backplane board, system board, or the carrier in the specified system <Sensor Name/

Location> exceeded the non-critical threshold.

Temperature of the backplane board, system board, or the carrier in the specified system <Sensor Name/

Location> returned from critical state to non-critical state.

Temperature of the backplane board, system board, or the carrier in the specified system <Sensor Name/

Location> returned to normal operating range.

Temperature of the backplane, system board, system inlet, or the carrier in the specified system <Sensor

Name/Location> entered into non-critical state.

Temperature of the backplane, system board, system inlet, or the carrier in the specified system <Sensor

Name/Location> entered into critical state.

Temperature of the backplane, system board, system inlet, or the carrier in the specified system <Sensor

Name/Location> entered into non-critical state.

Temperature of the backplane, system board, system inlet, or the carrier in the specified system <Sensor

Name/Location> entered into critical state.

4

192

Event Message

The <Sensor Name/ Location> temperature is outside of range.

Severity

Critical

The <Sensor Name/ Location> temperature is within range.

Information

Cause

Temperature of the backplane, system board, system inlet, or the carrier in the specified system <Sensor

Name/Location> is outside of normal operating range.

Temperature of the backplane, system board, system inlet, or the carrier in the specified system <Sensor

Name/Location> returned to a normal operating range.

Voltage Sensor Events

The voltage sensor event messages monitor the number of volts across critical components. These messages provide status and warning information for voltage sensors for a particular chassis.

Table 6. Voltage Sensor Events

Event Message Severity

<Sensor Name/Location> voltage sensor detected a failure <Reading> where

<Sensor Name/Location> is the entity that this sensor is monitoring. Reading is specified in volts. For example, 3.860 V.

Critical

Cause

The voltage of the monitored device has exceeded the critical threshold.

Critical The voltage specified by <Sensor Name/

Location> is in critical state.

<Sensor Name/Location> voltage sensor state asserted.

<Sensor Name/Location> voltage sensor state deasserted.

<Sensor Name/Location> voltage sensor detected a warning <Reading>.

<Sensor Name/Location> voltage sensor returned to normal <Reading>.

Information

Warning

Information

The voltage of a previously reported

<Sensor Name/Location> is returned to normal state.

Voltage of the monitored entity <Sensor

Name/Location> exceeded the warning threshold.

The voltage of a previously reported

<Sensor Name/Location> is returned to normal state.

The <Sensor Name/Location> voltage is less than the lower warning threshold.

The <Sensor Name/Location> voltage is less than the lower critical threshold.

The <Sensor Name/Location> voltage is greater than the upper warning threshold.

The <Sensor Name/Location> voltage is greater than the upper critical threshold.

Warning

Critical

Warning

Critical

Voltage of the monitored Entity <Sensor

Name/ Location> exceeded the warning threshold.

Voltage of the monitored Entity <Sensor

Name/ Location> exceeded the critical threshold.

Voltage of the monitored Entity <Sensor

Name/ Location> exceeded the warning threshold.

Voltage of the monitored Entity <Sensor

Name/ Location> exceeded the critical threshold.

193

Event Message

The <Sensor Name/Location> voltage is outside of range.

Severity

Critical

The <Sensor Name/Location> voltage is within range.

Information

Cause

Voltage of the monitored Entity <Sensor

Name/ Location> is outside of normal operating range.

Voltage of the monitored Entity <Sensor

Name/ Location> returned to a normal operating range.

Fan Sensor Events

The cooling device sensors monitor how well a fan is functioning. These messages provide status warning and failure messages for fans for a particular chassis.

Table 7. Fan Sensor Events

Event Message

<Sensor Name/Location> Fan sensor detected a failure

<Reading> where <Sensor Name/

Location> is the entity that this sensor is monitoring.

For example "BMC Back Fan" or

"BMC Front Fan." Reading is specified in RPM. For example, 100 RPM.

<Sensor Name/Location> Fan sensor returned to normal state <Reading>.

Severity

Critical

Information

Cause

The speed of the specified <Sensor

Name/Location> fan is not sufficient to provide enough cooling to the system.

The fan specified by <Sensor Name/

Location> has returned to its normal operating speed.

<Sensor Name/Location> Fan sensor detected a warning

<Reading>.

Warning

<Sensor Name/Location> Fan

Redundancy sensor redundancy degraded.

<Sensor Name/Location> Fan

Redundancy sensor redundancy lost.

<Sensor Name/Location> Fan

Redundancy sensor redundancy regained

Information

Critical

Information

The speed of the specified <Sensor

Name/Location> fan may not be sufficient to provide enough cooling to the system.

The fan specified by <Sensor Name/

Location> may have failed and hence, the redundancy has been degraded.

The fan specified by <Sensor Name/

Location> may have failed and hence, the redundancy that was degraded previously has been lost.

The fan specified by <Sensor Name/

Location> may have started functioning again and hence, the redundancy has been regained.

Fan <number> RPM is less than the lower warning threshold.

Warning

Fan <number> RPM is less than the lower critical threshold.

Critical

The speed of the specified fan might not provide enough cooling to the system.

The speed of the specified fan is not sufficient to provide enough cooling to the system.

194

Event Message

Fan <number> RPM is greater than the upper warning threshold.

Fan <number> RPM is greater than the upper critical threshold.

Fan <number> RPM is outside of range.

Fan <number> RPM is within range.

Fan <number> is removed.

Fan <number> was inserted.

Fan <number> is present.

Fan <number> is absent.

The fans are redundant.

Severity

Warning

Critical

Critical

Information

Critical

Information

Information

Critical

Information

Fan redundancy is lost.

Fan redundancy is degraded.

Critical

Warning

Cause

The speed of the specified fan exceeded the warning threshold.

The speed of the specified fan exceeded the critical threshold.

The speed of the specified fan might not provide enough cooling to the system.

The speed of the specified fan is operating in a normal range.

A required fan was removed.

A fan was added.

The total number of fans present.

A required fan is missing.

One or more fans may have started functioning or installed and the redundancy has been regained.

One or more required fans may have failed or removed and hence, the redundancy was lost.

One or more fans may have failed or removed and hence, the redundancy has been degraded.

Processor Status Events

The processor status messages monitor the functionality of the processors in a system. These messages provide processor health and warning information of a system.

Table 8. Processor Status Events

Event Message

<Processor Entity> status processor sensor IERR, where

<Processor Entity> is the processor that generated the event. For example, PROC for a single processor system and

PROC # for multiprocessor system.

Severity

Critical

Cause

IERR internal error generated by the

<Processor Entity>. This event is generated due to processor internal error.

<Processor Entity> status processor sensor Thermal

Trip.

Critical The processor generates this event before it shuts down because of excessive heat caused by lack of cooling or heat synchronization.

195

Event Message

<Processor Entity> status processor sensor recovered from IERR.

<Processor Entity> status processor sensor disabled.

<Processor Entity> status processor sensor terminator not present.

<Processor Entity> presence was deasserted.

<Processor Entity> presence was asserted.

<Processor Entity> thermal tripped was deasserted.

Severity

Information

Warning

Information

Critical

Information

Information

<Processor Entity> configuration error was asserted.

<Processor Entity> configuration error was deasserted.

Critical

Information

<Processor Entity> throttled was asserted.

Warning

<Processor Entity> throttled was deasserted.

Information

CPU <number> has an internal error (IERR).

CPU <number> has a thermal trip (over-temperature) event.

Critical

Critical

CPU <number> configuration is unsupported.

Warning

CPU <number> is present.

Information

Information CPU <number> terminator is present.

CPU <number> terminator is absent.

CPU <number> is throttled.

Warning

Warning

196

Cause

This event is generated when a processor recovers from the internal error.

This event is generated for all processors that are disabled.

This event is generated if the terminator is missing on an empty processor slot.

This event is generated when the system could not detect the processor.

This event is generated when the earlier processor detection error was corrected.

This event is generated when the processor has recovered from an earlier thermal condition.

This event is generated when the processor configuration is incorrect.

This event is generated when the earlier processor configuration error was corrected.

This event is generated when the processor slows down to prevent overheating.

This event is generated when the earlier processor throttled event was corrected.

The specified CPU generated an internal error.

The CPU generates this event before it shuts down because of excessive heat caused by lack of cooling or heat synchronization.

The specified CPU is not support for this system.

The specified CPU is present.

This event is generated if the terminator is present on a processor slot.

This event is generated if the terminator is missing on an empty processor slot.

This event is generated when the processor slows down to prevent overheating.

Event Message

CPU <number> is absent.

CPU <number> is operating correctly.

CPU <number> is configured correctly.

Severity

Critical

Information

Information

Cause

This event is generated when the system could not detect the processor.

This event is generated when the processor recovered from an error.

The specified CPU is configured correctly.

Power Supply Events

The power supply sensors monitor the functionality of the power supplies. These messages provide status and warning information for power supplies for a particular system.

Table 9. Power Supply Events

Event Message

<Power Supply Sensor Name> power supply sensor removed.

Severity

Critical

Cause

This event is generated when the power supply sensor is removed.

This event is generated when the power supply has been replaced.

<Power Supply Sensor Name> power supply sensor AC recovered.

<Power Supply Sensor Name> power supply sensor returned to normal state.

Information

Information

<Entity Name> PS Redundancy sensor redundancy degraded.

<Entity Name> PS Redundancy sensor redundancy lost.

<Entity Name> PS Redundancy sensor redundancy regained.

<Power Supply Sensor Name> predictive failure was asserted.

Information

Critical

Information

Critical

This event is generated when the power supply that failed or removed was replaced and the state has returned to normal.

Power supply redundancy is degraded if one of the power supply sources is removed or failed.

Power supply redundancy is lost if only one power supply is functional.

This event is generated if the power supply has been reconnected or replaced.

This event is generated when the power supply is about to fail.

<Power Supply Sensor Name> input lost was asserted.

<Power Supply Sensor Name> predictive failure was deasserted.

Critical

Information

<Power Supply Sensor Name> input lost was deasserted.

Information

PS 1 Status: Power supply sensor for PS 1, presence was asserted.

Information

This event is generated when the power supply is unplugged.

This event is generated when the power supply has recovered from an earlier predictive failure event.

This event is generated when the power supply is plugged in.

This event is generated when the power supply is plugged in.

197

Event Message Severity

PS 1 Status: Power supply sensor for PS 1, presence was deasserted.

Critical

PS 1 Status: Power supply sensor for PS 1, failure was asserted.

Critical

PS 1 Status: Power supply sensor for PS 1, failure was deasserted.

PS 1 Status: Power supply sensor for PS 1, predictive failure was asserted.

Information

Warning

Information PS 1 Status: Power supply sensor for PS 1, predictive failure was deasserted.

PS 1 Status: Power supply sensor for PS 1, input lost was asserted.

PS 1 Status: Power supply sensor for PS 1, input lost was deasserted.

PS 1 Status: Power supply sensor for PS 1, configuration error was asserted.

Critical

Information

Warning/Critical

PS 1 Status: Power supply sensor for PS 1, configuration error was deasserted.

Power supply <number> is present.

Information

Information

Power supply <number> is absent.

Critical

Power supply <number> failed. Critical

A predictive failure detected on power supply <number>.

Warning

The power input for power supply <number> is lost.

Critical

The input power for power supply <number> has been restored.

Power supply <number> is incorrectly configured.

Information

Critical/Warning

198

Cause

This event is generated when the power supply is removed.

This event is generated when the power supply has failed.

This event is generated when the power supply has recovered from an earlier failure event.

This event is generated when the power supply is about to fail.

This event is generated when the power supply has recovered from an earlier predictive failure event.

This event is generated when AC power is removed from the power supply.

This event is generated when the power supply is plugged in.

This event is generated when an invalid power supply configuration is detected.

This event is generated when the power supply has recovered from an earlier invalid configuration.

This event is generated when the power supply is plugged in.

This event is generated when the power supply is removed.

This event is generated when the power supply has failed.

This event is generated when the power supply is about to fail.

This event is generated when input power is removed from the power supply.

This event is generated if the power supply has been reconnected or replaced.

This event is generated when an invalid power supply configuration is detected.

Event Message

Power supply <number> is correctly configured.

Power supply <number> is operating normally.

Severity

Information

Information

Cannot communicate with power supply <number>.

Critical

The temperature for power supply <number> is in a warning range.

Warning

The temperature for power supply <number> is outside of range.

Critical

An under voltage fault detected on power supply

<number>.

Critical

An over voltage fault detected on power supply

<number>.

An over current fault detected on power supply

<number>.

Critical

Crotoca;

Fan failure detected on power supply <number>.

Critical

Communication has been restored to power supply

<number>.

Information

A power supply wattage mismatch is detected; power supply <number> is rated for

<value> watts.

Critical

Power supply <number> wattage mismatch corrected.

Information

Power supply redundancy is lost.

Power supply redundancy is degraded.

Critical

Warning

The power supplies are redundant.

Information

Cause

This event is generated when the power supply has recovered from an earlier invalid configuration.

This event is generated when the power supply has recovered from an earlier failure event.

The power supply may operate, however power supply monitoring is degraded.

Temperature of specified power supply entered into non-critical state.

Temperature of specified power supply entered into critical state.

The specified power supply detected inefficient voltage.

The specified power supply detected an over voltage condition.

The specified power supply detected an over current condition.

The specified power supply fan has failed.

This event is generated when the power supply has recovered from an earlier communication problem.

This event is generated when there is more than one power supplies in the system and the power supply wattage do not match.

This event is generated when the power supply has recovered from an earlier power supply wattage mismatch.

Power supply redundancy is lost if only one power supply is functional.

Power supply redundancy is degraded if one of the power supply sources is removed or failed.

This event is generated if the power supply has been reconnected or replaced.

199

Memory ECC Events

The memory ECC event messages monitor the memory modules in a system. These messages monitor the ECC memory correction rate and the type of memory events that occurred.

Table 10. Memory ECC Events

Event Message Severity

ECC error correction detected on Bank # DIMM [A/B].

Information

ECC uncorrectable error detected on Bank # [DIMM].

Critical

Cause

This event is generated when there is a memory error correction on a particular

Dual Inline Memory Module (DIMM).

This event is generated when the chipset is unable to correct the memory errors.

Usually, a bank number is provided and

DIMM may or may not be identifiable, depending on the error.

Correctable memory error logging disabled.

Persistent correctable memory errors detected on a memory device at location(s) <DIMM number>.

Multi-bit memory errors detected on a memory device at location(s) <location>.

Correctable memory error logging disabled for a memory device at location

<location>.

Critical

Warning

Critical

Critical

This event is generated when the chipset in the ECC error correction rate exceeds a predefined limit.

This event is generated when there is a memory error correction on a particular

Dual Inline Memory Module (DIMM).

This event is generated when the chipset is unable to correct the memory errors.

Usually, more than on DIMM is listed because a single DIMM may or may not be identifiable, depending on the error.

This event is generated when the chipset in the ECC error correction rate exceeds a predefined limit.

BMC Watchdog Events

Enter a short description for your reference topic. This should be one or two sentences that describes the topic content.

Table 11. BMC Watchdog Events

Event Message

BMC OS Watchdog timer expired.

BMC OS Watchdog performed system reboot.

Severity

Information

Critical

Cause

This event is generated when the BMC watchdog timer expires and no action is set.

This event is generated when the BMC watchdog detects that the system has crashed (timer expired because no response was received from Host) and the action is set to reboot.

BMC OS Watchdog performed system power off.

Critical This event is generated when the BMC watchdog detects that the system has

200

Event Message

BMC OS Watchdog performed system power cycle.

The OS watchdog timer reset the system.

Critical

The OS watchdog timer powered cycle the system.

Critical

The OS watchdog timer powered off the system.

Critical

The OS watchdog timer expired.

Severity

Critical

Critical

Cause crashed (timer expired because no response was received from Host) and the action is set to power off.

This event is generated when the BMC watchdog detects that the system has crashed (timer expired because no response was received from Host) and the action is set to power cycle.

This event is generated when the BMC watchdog detects that the system has crashed (timer expired because no response was received from Host) and the action is set to reboot.

This event is generated when the BMC watchdog detects that the system has crashed (timer expired because no response was received from Host) and the action is set to power cycle.

This event is generated when the BMC watchdog detects that the system has crashed (timer expired because no response was received from Host) and the action is set to power off.

This event is generated when the BMC watchdog timer expires and no action is set.

Memory Events

The memory modules can be configured in different ways in particular systems. These messages monitor the status, warning, and configuration information about the memory modules in the system.

Table 12. Memory Events

Event Message

Memory RAID redundancy degraded.

Memory RAID redundancy lost.

Severity

Warning

Critical

Cause

This event is generated when there is a memory failure in a RAID-configured memory configuration.

This event is generated when redundancy is lost in a RAID-configured memory configuration.

Memory RAID redundancy regained.

Memory Mirrored redundancy degraded.

Information

Warning

This event is generated when the redundancy lost or degraded earlier is regained in a RAID-configured memory configuration.

This event is generated when there is a memory failure in a mirrored memory configuration.

201

Event Message

Memory Mirrored redundancy lost.

Memory Mirrored redundancy regained.

Severity

Critical

Information

Memory Spared redundancy degraded.

Memory Spared redundancy lost.

Memory Spared redundancy regained.

Warning

Critical

Information

Memory RAID is redundant.

Information

Memory RAID redundancy is lost. Check memory device at location(s) <DIMM number>.

Critical

Memory RAID redundancy is degraded. Check memory device at location(s) <DIMM number

>.

Warning

Memory is not redundant.

Information

Memory mirror is redundant.

Information

Memory mirror redundancy is lost. Check memory device at location(s) <DIMM number>.

Critical

Memory mirror redundancy is degraded. Check memory device at location <DIMM number >.

Warning

Memory spare is redundant.

Information

Memory spare redundancy is lost. Check memory device at location <DIMM number>.

Critical

202

Cause

This event is generated when redundancy is lost in a mirrored memory configuration.

This event is generated when the redundancy lost or degraded earlier is regained in a mirrored memory configuration.

This event is generated when there is a memory failure in a spared memory configuration.

This event is generated when redundancy is lost in a spared memory configuration.

This event is generated when the redundancy lost or degraded earlier is regained in a spared memory configuration.

This event is generated when the memory redundancy mode has change to RAID redundant.

This event is generated when redundancy is lost in a RAID-configured memory configuration.

This event is generated when there is a memory failure in a RAID-configured memory configuration.

This event is generated when the memory redundancy mode has change to nonredundant.

This event is generated when the memory redundancy mode has change to mirror redundant.

This event is generated when redundancy is lost in a mirror-configured memory configuration.

This event is generated when there is a memory failure in a mirror-configured memory configuration.

This event is generated when the memory redundancy mode has change to spare redundant.

This event is generated when redundancy is lost in a sparer-configured memory configuration.

Event Message Severity

Memory spare redundancy is degraded. Check memory device at location <DIMM number>.

Warning

Cause

This event is generated when there is a memory failure in a spare-configured memory configuration.

Hardware Log Sensor Events

The hardware logs provide hardware status messages to the system management software. On particular systems, the subsequent hardware messages are not displayed when the log is full. These messages provide status and warning messages when the logs are full.

Table 13. Hardware Log Sensor Events

Event Message

Log full detected.

Log cleared.

Severity

Critical

Information

Cause

This event is generated when the SEL device detects that only one entry can be added to the SEL before it is full.

This event is generated when the SEL is cleared.

Drive Events

The drive event messages monitor the health of the drives in a system. These events are generated when there is a fault in the drives indicated.

Table 14. Drive Events

Event Message

Drive <Drive #> asserted fault state.

Drive <Drive #> de-asserted fault state.

Severity

Critical

Information

Cause

This event is generated when the specified drive in the array is faulty.

This event is generated when the specified drive recovers from a faulty condition.

Drive <Drive #> drive presence was asserted.

Drive <Drive #> predictive failure was asserted.

Information

Warning

Drive <Drive #> predictive failure was deasserted.

Information

Drive <Drive #> hot spare was asserted.

Warning

Drive <Drive #> hot spare was deasserted.

Drive <Drive #> consistency check in progress was asserted.

Drive <Drive #> consistency check in progress was deasserted.

Information

Warning

Information

This event is generated when the drive is installed.

This event is generated when the drive is about to fail.

This event is generated when the drive from earlier predictive failure is corrected.

This event is generated when the drive is placed in a hot spare.

This event is generated when the drive is taken out of hot spare.

This event is generated when the drive is placed in consistency check.

This event is generated when the consistency check of the drive is completed.

203

Event Message

Drive <Drive #> in critical array was asserted.

Drive <Drive #> in critical array was deasserted.

Severity

Critical

Information

Drive <Drive #> in failed array was asserted.

Drive <Drive #> in failed array was deasserted.

Drive <Drive #> rebuild in progress was asserted.

Drive <Drive #> rebuild aborted was asserted.

Critical

Information

Information

Warning

Drive <Drive #> is installed. Information

Drive <Drive #> is removed.

Fault detected on drive

<Drive #>.

Critical

Critical

Cause

This event is generated when the drive is placed in critical array.

This event is generated when the drive is removed from critical array.

This event is generated when the drive is placed in the fail array.

This event is generated when the drive is removed from the fail array.

This event is generated when the drive is rebuilding.

This event is generated when the drive rebuilding process is aborted.

This event is generated when the drive is installed.

This event is generated when the drive is removed.

This event is generated when the specified drive in the array is faulty.

Intrusion Events

The chassis intrusion messages are a security measure. Chassis intrusion alerts are generated when the system's chassis is opened.

Alerts are sent to prevent unauthorized removal of parts from the chassis.

Table 15. Intrusion Events

Event Message

<Intrusion sensor Name> sensor detected an intrusion.

Severity

Critical

Cause

This event is generated when the intrusion sensor detects an intrusion.

This event is generated when the earlier intrusion has been corrected.

<Intrusion sensor Name> sensor returned to normal state.

Information

<Intrusion sensor Name> sensor intrusion was asserted while system was ON.

Critical

<Intrusion sensor Name> sensor intrusion was asserted while system was OFF.

Critical

The chassis is open.

Critical

This event is generated when the intrusion sensor detects an intrusion while the system is on.

This event is generated when the intrusion sensor detects an intrusion while the system is off.

This event is generated when the intrusion sensor detects an intrusion.

The chassis is closed.

The chassis is open while the power is on.

Information

Critical

This event is generated when the earlier intrusion has been corrected.

This event is generated when the intrusion sensor detects an intrusion while the system is on.

204

Event Message

The chassis is closed while the power is on.

Severity

Information

The chassis is open while the power is off.

Critical

The chassis is closed while the power is off.

Information

Cause

This event is generated when the earlier intrusion has been corrected while the power is on.

This event is generated when the intrusion sensor detects an intrusion while the system is off.

This event is generated when the earlier intrusion has been corrected while the power is off.

BIOS Generated System Events

The BIOS-generated messages monitor the health and functionality of the chipsets, I/O channels, and other BIOS-related functions.

Table 16. BIOS Generated System Events

Event Message Severity

System Event I/O channel chk. Critical

Cause

This event is generated when a critical interrupt is generated in the I/O Channel.

System Event PCI Parity Err.

Critical

System Event Chipset Err.

System Event PCI System Err.

System Event PCI Fatal Err.

Critical

Information

Critical

This event is generated when a parity error is detected on the PCI bus.

This event is generated when a chip error is detected.

This event indicates historical data, and is generated when the system has crashed and recovered.

This error is generated when a fatal error is detected on the PCI bus.

System Event PCIE Fatal Err.

Critical

POST Err.

POST fatal error #<number> or

<error description>.

Memory Spared redundancy lost.

Critical

Critical

Critical

Memory Mirrored redundancy lost.

Critical

Memory RAID redundancy lost.

Critical

This error is generated when a fatal error is detected on the PCIE bus.

This event is generated when an error occurs during system boot. See the system documentation for more information on the error code.

This event is generated when a fatal error occurs during system boot. For more information, see

POST Code Errors .

This event is generated when memory spare is no longer redundant.

This event is generated when memory mirroring is no longer redundant.

This event is generated when memory

RAID is no longer redundant.

205

Event Message

Err Reg Pointer OEM

Diagnostic data event was asserted.

Severity

Information

System Board PFault Fail Safe state asserted.

Critical

System Board PFault Fail Safe state deasserted

Information

Memory Add (BANK# DIMM#) presence was asserted.

Memory Removed (BANK# DIMM#) presence was asserted.

Memory Cfg Err configuration error (BANK# DIMM#) was asserted.

Information

Information

Critical

Mem Redun Gain redundancy regained.

Information

Mem ECC Warning transition to non-critical from OK.

Warning

Mem ECC Warning transition to critical from less severe.

Critical

Mem CRC Err transition to non-recoverable.

Critical

Critical Mem Fatal SB CRC uncorrectable ECC was asserted.

Mem Fatal NB CRC uncorrectable ECC was asserted.

Mem Overtemp critical over temperature was asserted.

USB Over-current transition to non-recoverable

Critical

Critical

Critical

Hdwr version err hardware incompatibility (BMC/iDRAC

Firmware and CPU mismatch) was asserted.

Hdwr version err hardware incompatibility (BMC/iDRAC

Firmware and CPU mismatch) was deasserted.

Critical

Information

206

Cause

This event is generated when an OEM event occurs. OEM events can be used by the service team to better understand the cause of the failure.

This event is generated when the system board voltages are not at normal levels.

This event is generated when earlier

PFault Fail Safe system voltages return to a normal level.

This event is generated when memory is added to the system.

This event is generated when memory is removed from the system.

This event is generated when memory configuration is incorrect for the system.

This event is generated when memory redundancy is regained.

This event is generated when correctable

ECC errors have increased from a normal rate.

This event is generated when correctable

ECC errors reach a critical rate.

This event is generated when CRC errors enter a non-recoverable state.

This event is generated while storing CRC errors to memory.

This event is generated while removing

CRC errors from memory.

This event is generated when system memory reaches critical temperature.

This event is generated when the USB exceeds a predefined current level.

This event is generated when there is a mismatch between the BMC and iDRAC firmware and the processor in use or vice versa.

This event is generated when an earlier mismatch between the BMC and iDRAC firmware and the processor is corrected.

Event Message Severity

SBE Log Disabled correctable memory error logging disabled was asserted.

Critical

CPU Protocol Err transition to non-recoverable.

Critical

CPU Bus PERR transition to non-recoverable.

Critical

CPU Init Err transition to non-recoverable.

Critical

CPU Machine Chk transition to non-recoverable.

Critical

Logging Disabled all event logging disabled was asserted.

Critical

LinkT/FlexAddr: Link Tuning sensor, device option ROM failed to support link tuning or flex address (Mezz XX) was asserted

Critical

LinkT/FlexAddr: Link Tuning sensor, failed to program virtual MAC address

(<location>) was asserted.

Critical

PCIE NonFatal Er: Non Fatal

IO Group sensor, PCIe error(<location>)

Warning

I/O Fatal Err: Fatal IO Group sensor, fatal IO error

(<location>)

Critical

Unknown system event sensor unknown system hardware failure was asserted.

An I/O channel check error was detected.

A PCI parity error was detected on a component at bus <number> device <number> function <number>.

A PCI parity error was detected on a component at slot <number>.

Critical

Critical

Critical

Critical

Cause

This event is generated when the ECC single bit error rate is exceeded.

This event is generated when the processor protocol enters a nonrecoverable state.

This event is generated when the processor bus PERR enters a nonrecoverable state.

This event is generated when the processor initialization enters a nonrecoverable state.

This event is generated when the processor machine check enters a nonrecoverable state.

This event is generated when all event logging is disabled.

This event is generated when the PCI device option ROM for a NIC does not support link tuning or the Flex addressing feature.

This event is generated when BIOS fails to program virtual MAC address on the given

NIC device.

This event is generated in association with a CPU IERR.

This event is generated in association with a CPU IERR and indicates the PCI/PCIe device that caused the CPU IERR.

This event is generated when an unknown hardware failure is detected.

This event is generated when a critical interrupt is generated in the I/O Channel.

This event is generated when a parity error is detected on the PCI bus.

This event is generated when a parity error is detected on the PCI bus.

207

Event Message

A PCI system error was detected on a component at bus <number> device <number> function <number>.

A PCI system error was detected on a component at slot <number>.

Severity

Critical

Critical

A bus correctable error was detected on a component at bus <number> device <number> function <number>.

A bus correctable error was detected on a component at slot <number>.

Critical

Critical

A bus uncorrectable error was detected on a component at bus <number> device <number> function <>number>.

Critical

A bus uncorrectable error was detected on a component at slot <number>.

Critical

A fatal error was detected on a component at bus <number> device <number> function

<number>.

Critical

A fatal error was detected on a component at slot <number>.

Critical

A fatal IO error detected on a component at bus <number> device <number> function

<number>.

A fatal IO error detected on a component at slot <number>.

Critical

Critical

A non-fatal PCIe error detected on a component at bus <number> device <number> function <number>.

A non-fatal PCIe error detected on a component at slot <number>.

Warning

Warning

A non-fatal IO error detected on a component at bus

<number> device <number> function <number>.

Warning

208

Cause

This is generated when the system has crashed and recovered.

This is generated when the system has crashed and recovered.

This is generated when the system has detected bus correctable errors.

This is generated when the system has detected bus correctable errors.

This is generated when the system has detected bus uncorrectable errors.

This is generated when the system has detected bus uncorrectable errors.

This error is generated when a fatal error is detected on the PCI bus.

This error is generated when a fatal error is detected on the PCI bus.

This error is generated when a fatal IO error is detected.

This error is generated when a fatal IO error is detected.

This event is generated in association with a CPU IERR.

This event is generated in association with a CPU IERR.

This event is generated in association with a CPU IERR and indicates the PCI/PCIe device that caused the CPU IERR.

Event Message

Memory device was added at location <location>.

Severity

Information

Memory device is removed from location <location>.

Information

Unsupported memory configuration; check memory device at location

<location>.

Critical

Correctable memory error rate exceeded for <location>.

Warning

Correctable memory error rate exceeded for <location>.

Critical

Memory device at location

<location> is overheating.

Critical

An OEM diagnostic event occurred.

Information

CPU <number> protocol error detected.

Critical

CPU bus parity error detected.

Critical

CPU <number> initialization error detected.

Critical

CPU <number> machine check error detected.

Critical

All event logging is disabled.

Logging is disabled.

Critical

Critical

The system board fail-safe voltage is outside of range.

The system board fail-safe voltage is within range.

Critical

Information

A hardware incompatibility detected between BMC/iDRAC firmware and CPU.

Critical

Cause

This event is generated when memory is added to the system.

This event is generated when memory is removed from the system.

This event is generated when memory configuration is incorrect for the system.

This event is generated when correctable

ECC errors have increased from a normal rate.

This event is generated when correctable

ECC errors reach a critical rate.

This event is generated when system memory reaches critical temperature.

This event is generated when an OEM event occurs. OEM events can be used by the service team to better understand the cause of the failure.

This event is generated when the processor protocol enters a nonrecoverable state.

This event is generated when the processor bus PERR enters a nonrecoverable state.

This event is generated when the processor initialization enters a nonrecoverable state.

This event is generated when the processor machine check enters a nonrecoverable state.

This event is generated when all event logging is disabled.

This event is generated when the ECC single bit error rate is exceeded.

This event is generated when the system board voltages are not at normal levels.

This event is generated when earlier Fail-

Safe system voltages return to a normal level.

This event is generated when there is a mismatch between the BMC and iDRAC firmware and the processor in use or vice versa.

209

Event Message

A hardware incompatibility was corrected between BMC/ iDRAC firmware and CPU.

Severity

Information

Device option ROM on embedded

NIC failed to support Link

Tuning or FlexAddress.

Critical

Device option ROM on mezzanine card <number> failed to support Link Tuning or FlexAddress.

Critical

Failed to program virtual MAC address on a component at bus

<bus> device <device> function <function>.

Critical

Failed to get Link Tuning or

FlexAddress data from iDRAC.

Critical

Cause

This event is generated when an earlier mismatch between the BMC and iDRAC firmware and the processor is corrected.

This event is generated when the PCI device option ROM for a NIC does not support link tuning or the Flex addressing feature.

This event is generated when the PCI device option ROM for a NIC does not support link tuning or the Flex addressing feature.

This event is generated when BIOS fails to program virtual MAC address on the given

NIC device.

An unknown system hardware failure detected.

POST fatal error <error description>

Critical

Critical

This event is generated when BIOS could not obtain virtual MAC address or Link

Tuning data from iDRAC.

This event is generated when an unknown hardware failure is detected.

This event is generated when a fatal error occurs during system boot. For more information, see

POST Code Errors .

POST Code Table

The following table lists the POST Code errors that are generated when a fatal error occurs during system boot.

Table 17. POST Code Table

Fatal Error Code

80

Description

No memory detected.

Cause

This error code implies that no memory is installed.

81

82

83

84

85

Memory detected but is not configurable.

This error code indicates memory configuration error that could be a result of bad memory, mismatched memory or bad socket.

Memory configured but not usable.

This error code indicates memory subsystem failure.

System BIOS shadow failure.

CMOS failure.

DMA controller failure.

This error code indicates system BIOS shadow failure.

This error code indicates that CMOS

RAM is not working.

This error code indicates DMA controller failure.

210

C1

C2

8C

C0

C3

C4

FE

88

89

8A

8B

Fatal Error Code

86

87

Description

Interrupt controller failure.

Timer refresh failure.

Programmable interval timer error.

Parity error.

SIO failure.

Keyboard controller failure.

SMI initialization failure.

Shutdown test failure.

POST Memory test failure.

RAC configuration failure.

CPU configuration failure.

Incorrect memory configuration.

General failure after video.

Cause

This error code indicates interrupt controller failure.

This error code indicates timer refresh failure.

This error code indicates a programmable interval timer error.

This error code indicates a parity error.

This error code indicates SIO failure.

This error code indicates keyboard controller failure.

This error code indicates SMI initialization failure.

This error code indicates a shutdown test failure.

This error code indicates bad memory detection.

Check screen for the actual error message.

Check screen for the actual error message.

Memory population order not correct.

Check screen for the actual error message.

Operating System Generated System Events

Table 18. Operating System Generated System Events

Description

System Event: OS stop event

OS graceful shutdown detected

OEM Event data record (after

OS graceful shutdown/restart event)

Severity

Information

Information

System Event: OS stop event runtime critical stop

OEM Event data record (after

OS bugcheck event)

A critical stop occurred during OS load.

Critical

Information

Critical

Cause

The operating system was shutdown/ restarted normally.

Comment string accompanying an operating system shutdown/ restart.

The operating system encountered a critical error and was stopped abnormally.

Operating system bugcheck code and parameters.

The operating system encountered a critical error and was stopped abnormally while loading.

211

Description

A runtime critical stop occurred.

Severity

Critical

An OS graceful stop occurred. Information

An OS graceful shut-down occurred.

Information

Cause

The operating system encountered a critical error and was stopped abnormally.

The operating system was stopped.

The operating system was shut down normally.

Cable Interconnect Events

The cable interconnect messages in the table are used for detecting errors in the hardware cabling.

Table 19. Cable Interconnect Events

Description

Cable sensor <Name/

Location>Configuration error was asserted.

Severity

Critical

Cause

This event is generated when the cable is not connected or is incorrectly connected.

This event is generated when the earlier cable connection error was corrected.

Cable sensor <Name/

Location>Connection was asserted.

Information

The <name> cable or interconnect is not connected or is improperly connected.

Critical

The <name> cable or interconnect is connected.

Information

This event is generated when the named cable or interconnect is not connected or is incorrectly connected.

This event is generated when named cable or interconnect earlier cable or interconnect connection error was corrected.

Battery Events

Table 20. Battery Events

Description

<Battery sensor Name/

Location>Failed was asserted

<Battery sensor Name/

Location>Failed was deasserted

<Battery sensor Name/

Location>is low was asserted

<Battery sensor Name/

Location>is low was deasserted

The <Battery sensor Name/

Location> battery is low.

Severity

Critical

Information

Warning

Information

Warning

Cause

This event is generated when the sensor detects a failed or missing battery.

This event is generated when the earlier failed battery was corrected.

This event is generated when the sensor detects a low battery condition.

This event is generated when the earlier low battery condition was corrected.

This event is generated when the sensor detects a low battery condition.

212

Description

The <Battery sensor Name/

Location> battery is operating normally.

The <Battery sensor Name/

Location> battery has failed.

Severity

Information

Critical

Cause

This event is generated when an earlier battery condition was corrected.

This event is generated when the sensor detects a failed or missing battery.

Power And Performance Events

The power and performance events are used to detect degradation in system performance with change in power supply.

Table 21. Power And Performance Events

Description

System Board Power Optimized:

Performance status sensor for

System Board, degraded,

<description of why> was deasserted

Severity

Normal

System Board Power Optimized:

Performance status sensor for

System Board, degraded,

<description of why> was asserted

Warning

Cause

This event is generated when system performance was restored.

This event is generated when change in power supply degrades system performance.

This event is generated when change in power supply degrades system performance.

System Board Power Optimized:

Performance status sensor for

System Board, degraded, power capacity changed was asserted

Warning

System Board Power Optimized:

Performance status sensor for

System Board, degraded, power capacity changed was deasserted

Normal

System Board Power Optimized:

Performance status sensor for

System Board, degraded, user defined power capacity was asserted

Warning

System Board Power Optimized:

Performance status sensor for

System Board, degraded, user defined power capacity was deasserted

Normal

System Board Power Optimized:

Performance status sensor for

System Board, Halted, system power exceeds capacity was asserted

Critical

This event is generated when the system performance is restored.

This event is generated when a change in power supply degrades system performance.

This event is generated when the system performance is restored.

This event is generated when a change in power supply degrades system performance.

213

Description Severity

System Board Power Optimized:

Performance status sensor for

System Board, Halted, system power exceeds capacity was deasserted

Normal

The system performance degraded.

Warning

Warning The system performance degraded because of thermal protection.

The system performance degraded because cooling capacity has changed.

The system performance degraded because power capacity has changed.

The system performance degraded because of userdefined power capacity has changed.

Warning

Warning

Warning

The system halted because system power exceeds capacity.

The system performance degraded because power exceeds capacity.

The system performance degraded because power draw exceeds the power threshold.

The system performance restored

Critical

Warning

Critical

Information

Entity Presence Events

The entity presence messages are used for detecting different hardware devices.

Table 22. Entity Presence Events

Description

<Device Name> presence was asserted

<Device Name> absent was asserted

Severity

Information

Critical

The <Device Name> is present. Information

Cause

This event is generated when system performance was restored.

This event is generated when a change degrades system performance.

This event is generated when a change in thermal protection degrades system performance.

This event is generated when a change in cooling degrades system performance.

This event is generated when change in power supply degrades system performance.

This event is generated when change in power supply degrades system performance.

This event is generated when there is inefficient power for the system.

This event is generated when system power is inefficient causing system performance to degrade.

This event is generated when system power is inefficient causing system performance to degrade.

This event is generated when system performance was restored.

Cause

This event is generated when the device was detected.

This event is generated when the device was not detected.

This event is generated when the device was detected.

214

Description Severity

The <Device Name> is absent.

Critical

Cause

This event is generated when the device was not detected.

Miscellaneous Events

The following table provides events related to hardware and software components like mezzanine cards, sensors, firmware etc. and compatibility issues.

Table 23. Miscellaneous Events

Description

System Board Video Riser:

Module sensor for System

Board, device removed was asserted

Severity

Critical

Cause

This event is generated when the required module is removed.

This event is generated when an incorrect

Mezzanine card is installed for I/O fabric.

Mezz B<slot number> Status:

Add-in Card sensor for Mezz

B<slot number>, install error was asserted

Critical

Mezz C<slot number> Status:

Add-in Card sensor for Mezz

C<slot number>, install error was asserted

Critical

Hdwar version err: Version

Change sensor, hardware incompatibility was asserted

Hdwar version err: Version

Change sensor, hardware incompatibility (BMC firmware) was asserted

Critical

Critical

This event is generated when an incorrect

Mezzanine card is installed for I/O fabric.

This event is generated when an incompatible hardware is detected.

This event is generated when a hardware is incompatible with the firmware.

Hdwar version err: Version

Change sensor, hardware incompatibility (BMC firmware and CPU mismatch) was asserted

Critical

Link Tuning: Version Change sensor, successful software or F/W change was deasserted

Warning

Link Tuning: Version Change sensor, successful hardware change <device slot number> was deasserted

LinkT/FlexAddr: Link Tuning sensor, failed to program virtual MAC address (Bus #

Device # Function #) was asserted

Warning

Critical

This event is generated when the CPU and firmware are not compatible.

This event is generated when the link tuning setting for proper NIC operation fails to update.

This event is generated when the link tuning setting for proper NIC operation fails to update.

This event is generated when Flex address can be programmed for this device.

215

Description Severity

LinkT/FlexAddr: Link Tuning sensor, device option ROM failed to support link tuning or flex address (Mezz

<location>) was asserted

Critical

LinkT/FlexAddr: Link Tuning sensor, failed to get link tuning or flex address data from BMC/iDRAC was asserted

Critical

The <name> is removed.

Critical

The <name> is inserted.

Information

A fabric mismatch detected between IOM and mezzanine card <number>.

Hardware incompatibility detected with mezzanine card

<number>.

The QuickPath Interconnect

(QPI) width degraded.

The QuickPath Interconnect

(QPI) width regained.

Critical

Critical

Warning

Information

BIOS detected an error configuring the Intel Trusted

Execution Technology (TXT).

Critical

Processor detected an error while performing an Intel

Trusted Execution Technology

(TXT) operation.

Critical

BIOS Authenticated Code

Module detected an Intel

Trusted Execution Technology

(TXT) error during POST.

SINIT Authenticated Code

Module detected an Intel

Trusted Execution Technology

(TXT) error at boot.

Critical

Critical

Intel Trusted Execution

Technology (TXT) is operating correctly.

Information

Failure detected on Removable

Flash Media <name>.

Critical

216

Cause

This event is generated when ROM does not support Flex address or link tuning.

This event is generated when link tuning or Flex address information is not obtained from BMC/iDRAC.

This event is generated when the device was removed.

This event is generated when the device was inserted or installed.

This event is generated when an incorrect

Mezzanine card is installed for I/O fabric.

This event is generated when an incorrect

Mezzanine card is installed in the system.

This event is generated when the bus is not operating at maximum speed or width.

This event is generated when the bus is operating at maximum speed or width.

This event is generated when TXT initialization failed.

This event is generated when TXT CPU microcode boot failed.

This event is generated when TXT Post failed.

This event is generated when the

Authenticated Code Module detected a

TXT initialization failure.

This event is generated when the TXT returned from a previous failure.

This event is generated when the SD card module is installed but improperly configured or failed to initialize.

Description

Removable Flash Media <name> is write protected.

Severity

Warning

Internal Dual SD Module is redundant.

Internal Dual SD Module redundancy is lost.

Information

Critical

Cause

This event is generated when the module is write-protected. Changes may not be written to the media.

This event is generated when both SD cards are functioning properly.

This event is generated when either one of the SD cards or both the SD cards are not functioning properly.

217