HP P4000 9.0 HP StorageWorks P4000 SAN Solution User Guide - Page 128

Exporting event data, Setting up remote log destinations, Changing the event retention period, Events

Page 128 highlights

Exporting event data You can export all of the event data to a .csv or .txt file for use in a spreadsheet or database. To export event data: 1. In the navigation window, log in to the management group. 2. Select Events in the tree. 3. Click Event Tasks, and select Export Events. 4. In the Filename field, enter a path and file name. If you enter just a file name, the file is stored in the installation location of the CMC. To select a different location or .txt format, click Browse. 5. Click OK. Setting up remote log destinations Use remote log destinations to automatically write all events for the management group to a computer other than the storage system. For example, you can direct the event data to a single log server in a remote location. You must also configure the destination computer to receive the log files by configuring syslog on the destination computer. The syslog facility to use is local5, and the syslog levels are: LOG_INFO, LOG_WARNING, LOG_CRIT. See the syslog documentation for information about configuring syslog. To set up remote log destinations: 1. In the navigation window, log in to the management group. 2. Select Events in the tree. 3. Click Event Tasks, and select Edit Remote Log Destinations. 4. In the Destinations field, enter the IP address or host name of the computer that will receive the events. 5. Select the event severities you want to include. 6. If you want to set up a second remote destination, enter the appropriate information. 7. Click OK. Changing the event retention period By default, the system retains events for one month. You can change the event retention period. NOTE: Because of space constraints, retention periods longer than one month are not guaranteed. 1. In the navigation window, log in to the management group. 2. Select Events in the tree. 3. Click Event Tasks, and select Edit Event Log Policy. 4. Change the event retention period. 128 Monitoring and reporting

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350

Exporting event data
You can export all of the event data to a .csv or .txt file for use in a spreadsheet or database.
To export event data:
1.
In the navigation window, log in to the management group.
2.
Select
Events
in the tree.
3.
Click
Event Tasks
, and select
Export Events
.
4.
In the Filename field, enter a path and file name.
If you enter just a file name, the file is stored in the installation location of the CMC.
To select a different location or .txt format, click
Browse
.
5.
Click
OK
.
Setting up remote log destinations
Use remote log destinations to automatically write all events for the management group to a computer
other than the storage system. For example, you can direct the event data to a single log server in a
remote location.
You must also configure the destination computer to receive the log files by configuring syslog on the
destination computer. The syslog facility to use is local5, and the syslog levels are: LOG_INFO,
LOG_WARNING, LOG_CRIT. See the syslog documentation for information about configuring syslog.
To set up remote log destinations:
1.
In the navigation window, log in to the management group.
2.
Select
Events
in the tree.
3.
Click
Event Tasks
, and select
Edit Remote Log Destinations
.
4.
In the Destinations field, enter the IP address or host name of the computer that will receive the
events.
5.
Select the event severities you want to include.
6.
If you want to set up a second remote destination, enter the appropriate information.
7.
Click
OK
.
Changing the event retention period
By default, the system retains events for one month. You can change the event retention period.
NOTE:
Because of space constraints, retention periods longer than one month are not guaranteed.
1.
In the navigation window, log in to the management group.
2.
Select
Events
in the tree.
3.
Click
Event Tasks
, and select
Edit Event Log Policy
.
4.
Change the event retention period.
Monitoring and reporting
128