Reference Guide
Table Of Contents
- Server Administrator Version 8.4 Messages Reference Guide
- Introduction
- Server Management Messages
- Server Administrator General Messages
- Event ID — 0000
- Event ID — 0001
- Event ID — 1000
- Event ID — 1001
- Event ID — 1002
- Event ID – 1003
- Event ID — 1004
- Event ID — 1005
- Event ID — 1006
- Event ID — 1007
- Event ID — 1008
- Event ID — 1009
- Event ID — 1011
- Event ID — 1012
- Event ID — 1013
- Event ID — 1014
- Event ID — 1019
- Event ID — 1016
- Event ID — 1017
- Event ID — 1018
- Event ID — 1019
- Event ID — 1020
- Temperature Sensor Messages
- Cooling Device Messages
- Voltage Sensor Messages
- Current Sensor Messages
- Chassis Intrusion Messages
- Redundancy Unit Messages
- Power Supply Messages
- Memory Device Messages
- Hardware Log Sensor Messages
- Processor Sensor Messages
- Pluggable Device Messages
- Battery Sensor Messages
- Secure Digital (SD) Card Device Messages
- Server Administrator General Messages
- Storage Management Message Reference
- Alert Monitoring and Logging
- Alert Message Format with Substitution Variables
- Alert Descriptions and Corrective Actions
- Event ID — 2048
- Event ID — 2049
- Event ID — 2050
- Event ID — 2051
- Event ID — 2052
- Event ID — 2053
- Event ID — 2054
- Event ID — 2055
- Event ID — 2056
- Event ID — 2057
- Event ID — 2058
- Event ID — 2059
- Event ID — 2060
- Event ID — 2061
- Event ID — 2062
- Event ID — 2063
- Event ID — 2064
- Event ID — 2065
- Event ID — 2067
- Event ID — 2070
- Event ID — 2074
- Event ID — 2075
- Event ID — 2076
- Event ID — 2077
- Event ID — 2079
- Event ID — 2080
- Event ID — 2081
- Event ID — 2082
- Event ID — 2083
- Event ID — 2085
- Event ID — 2086
- Event ID — 2087
- Event ID — 2088
- Event ID — 2089
- Event ID — 2090
- Event ID — 2091
- Event ID — 2092
- Event ID — 2094
- Event ID — 2095
- Event ID — 2098
- Event ID — 2099
- Event ID — 2100
- Event ID — 2101
- Event ID — 2102
- Event ID — 2103
- Event ID — 2104
- Event ID — 2105
- Event ID — 2106
- Event ID — 2107
- Event ID — 2108
- Event ID — 2109
- Event ID — 2110
- Event ID — 2111
- Event ID — 2112
- Event ID — 2114
- Event ID — 2115
- Event ID — 2116
- Event ID — 2117
- Event ID — 2118
- Event ID — 2120
- Event ID — 2121
- Event ID — 2122
- Event ID — 2123
- Event ID — 2124
- Event ID — 2125
- Event ID — 2126
- Event ID — 2127
- Event ID — 2128
- Event ID — 2129
- Event ID — 2130
- Event ID — 2131
- Event ID — 2132
- Event ID — 2135
- Event ID — 2136
- Event ID — 2137
- Event ID — 2138
- Event ID — 2139
- Event ID — 2140
- Event ID — 2141
- Event ID — 2142
- Event ID — 2143
- Event ID — 2144
- Event ID — 2145
- Event ID — 2146
- Event ID — 2147
- Event ID — 2148
- Event ID — 2149
- Event ID — 2150
- Event ID — 2151
- Event ID — 2152
- Event ID — 2153
- Event ID — 2154
- Event ID — 2155
- Event ID — 2156
- Event ID — 2157
- Event ID — 2158
- Event ID — 2159
- Event ID — 2160
- Event ID — 2161
- Event ID — 2162
- Event ID — 2163
- Event ID — 2164
- Event ID — 2165
- Event ID — 2166
- Event ID — 2167
- Event ID — 2168
- Event ID — 2169
- Event ID — 2170
- Event ID — 2171
- Event ID — 2172
- Event ID — 2173
- Event ID — 2174
- Event ID — 2175
- Event ID — 2176
- Event ID — 2177
- Event ID — 2178
- Event ID — 2179
- Event ID — 2180
- Event ID — 2181
- Event ID — 2182
- Event ID — 2183
- Event ID — 2184
- Event ID — 2185
- Event ID — 2186
- Event ID — 2187
- Event ID — 2188
- Event ID — 2189
- Event ID — 2190
- Event ID — 2191
- Event ID — 2192
- Event ID — 2193
- Event ID — 2194
- Event ID — 2195
- Event ID — 2196
- Event ID — 2197
- Event ID — 2198
- Event ID — 2199
- Event ID — 2200
- Event ID — 2201
- Event ID — 2202
- Event ID — 2203
- Event ID — 2204
- Event ID — 2205
- Event ID — 2206
- Event ID — 2207
- Event ID — 2210
- Event ID — 2211
- Event ID — 2212
- Event ID — 2213
- Event ID — 2214
- Event ID — 2215
- Event ID — 2216
- Event ID — 2217
- Event ID — 2218
- Event ID — 2219
- Event ID — 2220
- Event ID — 2221
- Event ID — 2222
- Event ID — 2223
- Event ID — 2224
- Event ID — 2225
- Event ID — 2226
- Event ID — 2227
- Event ID — 2228
- Event ID — 2229
- Event ID — 2230
- Event ID — 2231
- Event ID — 2232
- Event ID — 2233
- Event ID — 2234
- Event ID — 2235
- Event ID — 2236
- Event ID — 2237
- Event ID — 2238
- Event ID — 2239
- Event ID — 2240
- Event ID — 2241
- Event ID — 2242
- Event ID — 2243
- Event ID — 2244
- Event ID — 2245
- Event ID — 2246
- Event ID — 2247
- Event ID — 2248
- Event ID — 2249
- Event ID — 2250
- Event ID — 2251
- Event ID — 2252
- Event ID — 2253
- Event ID — 2254
- Event ID — 2255
- Event ID — 2257
- Event ID — 2258
- Event ID — 2259
- Event ID — 2260
- Event ID — 2261
- Event ID — 2262
- Event ID — 2263
- Event ID — 2264
- Event ID — 2265
- Event ID — 2266
- Event ID — 2267
- Event ID — 2268
- Event ID — 2269
- Event ID — 2270
- Event ID — 2271
- Event ID — 2272
- Event ID — 2273
- Event ID — 2274
- Event ID — 2276
- Event ID — 2277
- Event ID — 2278
- Event ID — 2279
- Event ID — 2280
- Event ID — 2281
- Event ID — 2282
- Event ID — 2283
- Event ID — 2284
- Event ID — 2285
- Event ID — 2286
- Event ID — 2287
- Event ID — 2288
- Event ID — 2289
- Event ID — 2290
- Event ID — 2291
- Event ID — 2292
- Event ID — 2293
- Event ID — 2294
- Event ID — 2295
- Event ID — 2296
- Event ID — 2297
- Event ID — 2298
- Event ID — 2299
- Event ID — 2300
- Event ID — 2301
- Event ID — 2302
- Event ID — 2303
- Event ID — 2304
- Event ID — 2305
- Event ID — 2306
- Event ID — 2307
- Event ID — 2309
- Event ID — 2310
- Event ID — 2311
- Event ID — 2312
- Event Id — 2313
- Event ID — 2314
- Event Id — 2315
- Event ID — 2316
- Event ID — 2318
- Event ID — 2319
- Event Id — 2320
- Event ID — 2321
- Event ID — 2322
- Event ID — 2323
- Event ID — 2324
- Event ID — 2325
- Event ID — 2326
- Event ID — 2327
- Event ID — 2328
- Event ID — 2329
- Event ID — 2330
- Event ID — 2331
- Event ID — 2332
- Event ID — 2334
- Event ID — 2335
- Event ID — 2336
- Event ID — 2337
- Event ID — 2338
- Event ID — 2339
- Event ID — 2340
- Event ID — 2341
- Event ID — 2342
- Event ID — 2343
- Event ID — 2344
- Event ID — 2345
- Event ID — 2346
- Event ID — 2347
- Event ID — 2348
- Event ID — 2349
- Event ID — 2350
- Event ID — 2351
- Event ID — 2352
- Event ID — 2353
- Event ID — 2354
- Event ID — 2355
- Event ID — 2356
- Event ID — 2357
- Event ID — 2358
- Event ID — 2359
- Event ID — 2360
- Event ID — 2361
- Event ID — 2362
- Event ID — 2364
- Event ID — 2366
- Event ID — 2367
- Event ID — 2368
- Event ID — 2369
- Event ID — 2370
- Event ID — 2371
- Event ID — 2372
- Event ID — 2373
- Event ID — 2374
- Event ID — 2375
- Event ID — 2376
- Event ID — 2377
- Event ID — 2378
- Event ID — 2379
- Event ID — 2380
- Event ID — 2381
- Event ID — 2382
- Event ID — 2383
- Event ID — 2384
- Event Id — 2385
- Event ID — 2386
- Event ID — 2387
- Event ID — 2388
- Event ID — 2389
- Event ID — 2390
- Event ID — 2392
- Event ID — 2393
- Event ID — 2394
- Event ID — 2395
- Event ID — 2396
- Event ID — 2397
- Event ID — 2398
- Event ID — 2399
- Event ID — 2400
- Event ID — 2401
- Event ID — 2402
- Event ID — 2403
- Event ID — 2404
- Event ID — 2405
- Event ID — 2407
- Event ID — 2411
- Event ID — 2412
- Event ID — 2413
- Event ID — 2414
- Event ID — 2415
- Event ID — 2416
- Event ID — 2417
- Event ID — 2418
- Event ID — 2425
- Event ID — 2426
- Event ID — 2429
- Event ID — 2430
- Event ID — 2431
- Event ID — 2432
- Event ID — 2433
- Event ID — 2434
- Event ID — 2435
- Event ID — 2436
- Event ID — 2437
- Event ID — 2438
- Event ID — 2440
- Event ID — 2441
- Event ID — 2442
- Event ID — 2443
- Event ID — 2444
- Event ID — 2445
- Event ID — 2446
- Event ID — 2447
- Event ID — 2448
- Event ID — 2449
- Event ID — 2450
- Event ID — 2451
- Event ID — 2454
- Event ID — 2699
- Event ID — 2700
- Event ID — 2701
- Event ID — 2702
- Event ID — 2703
- Event ID — 2704
- Event ID — 2705
- Event ID — 2874
- Event ID — 2875
- Event ID — 2876
- Event ID — 2900
- Event ID — 2901
- Event ID — 2902
- Event ID — 2903
- Event ID — 2904
- Event ID — 2905
- Event ID — 2906
- Event ID — 2907
- Event ID — 2908
- Event ID — 2909
- Event ID — 2910
- Event ID — 2911
- Event ID — 2912
- Event ID — 2913
- Event ID — 2914
- Event ID — 2915
- Event ID — 2916
- Event ID — 2917
- Event ID — 2918
- Event ID — 2919
- Event ID — 2920
- Event ID — 2921
- Event ID — 2922
- Event ID — 2923
- Event ID — 2924
- Event ID — 2930
- Event ID — 2931
- Event ID — 2932
- Event ID — 2933
- System Event Log Messages for IPMI Systems
- Temperature Sensor Events
- Voltage Sensor Events
- Fan Sensor Events
- Processor Status Events
- Power Supply Events
- Memory ECC Events
- BMC Watchdog Events
- Memory Events
- Hardware Log Sensor Events
- Drive Events
- Intrusion Events
- BIOS Generated System Events
- POST Code Table
- Operating System Generated System Events
- Cable Interconnect Events
- Battery Events
- Power And Performance Events
- Entity Presence Events
- Miscellaneous Events

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/srvadmin-
deng/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