HP StorageWorks 2/32 SAN switch 2/32 version 4.0.2b release notes - Page 18

Error Log Enhancements

Page 18 highlights

Firmware Enhancements Error Log Enhancements The Error Log subsystem now retains a maximum of 1,536 messages in RAM, that is, a total of 256 messages for each error message level (Panic, Critical, Error, Warning, Info, and Debug). In addition, important messages are stored in a separate persistent error log to guarantee that they are not lost in case of power outage or system reboot. Note: The enhancement prevents messages of lesser severity from overwriting messages of greater severity. For example, Warning messages cannot overwrite Error, Critical or Panic messages. Error log updates include: ■ The error log subsystem supports persistent logging. Each switch integrates its own persistent log. ■ The persistent log is preserved across power cycles and system reboots. ■ The persistent log has a default capacity to store 1,024 error log entries. ■ The persistent log can be resized at run time without having to reboot the switch or the system. ■ The persistent log is configurable to a maximum of 2,048 entries. The persistent error log can be resized to between 1,024 and 2,048 entries. ■ The persistent log is implemented as a circular buffer. When more than maximum entries are added to the persistent log, new entries overwrite old entries. ■ All error messages of levels Panic and Critical are automatically saved in the persistent log as they are logged. This guarantees that critical or panic level messages are not lost in the event of unexpected system reboot or failover. ■ A new command to control/filter error log messages. For example, the user may specify that all log messages marked Warning remain in the persistent error log. ■ The commands errdump or errshow display a combination of the persistent log messages saved during previous system run time cycles, and the error log messages generated during the current run time cycle. 18 SAN switch 2/32 Version 4.0.2b Release Notes

  • 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

Firmware Enhancements
18
SAN switch 2/32 Version 4.0.2b Release Notes
Error Log Enhancements
The Error Log subsystem now retains a maximum of 1,536 messages in RAM,
that is, a total of 256 messages for each error message level (Panic, Critical, Error,
Warning, Info, and Debug). In addition, important messages are stored in a
separate persistent error log to guarantee that they are not lost in case of power
outage or system reboot.
Note:
The enhancement prevents messages of lesser severity from overwriting
messages of greater severity. For example,
Warning
messages cannot overwrite
Error
,
Critical
or
Panic
messages.
Error log updates include:
The error log subsystem supports persistent logging. Each switch integrates
its own persistent log.
The persistent log is preserved across power cycles and system reboots.
The persistent log has a default capacity to store 1,024 error log entries.
The persistent log can be resized at run time without having to reboot the
switch or the system.
The persistent log is configurable to a maximum of 2,048 entries. The
persistent error log can be resized to between 1,024 and 2,048 entries.
The persistent log is implemented as a circular buffer. When more than
maximum entries are added to the persistent log, new entries overwrite old
entries.
All error messages of levels Panic and Critical are automatically saved in the
persistent log as they are logged. This guarantees that critical or panic level
messages are not lost in the event of unexpected system reboot or failover.
A new command to control/filter error log messages. For example, the user
may specify that all log messages marked
Warning
remain in the persistent
error log.
The commands
errdump
or
errshow
display a combination of the
persistent log messages saved during previous system run time cycles, and the
error log messages generated during the current run time cycle.