3Ware 9500S-4LP CLI Guide - Page 51

/cx show alarms [reverse], force, reverse

Page 51 highlights

Controller Object Commands Given the above recommendation... Do you want to continue ? Y|N [N]: y Downloading the firmware from file /tmp/prom0006.img ... Done. The new image will take effect after reboot. force attribute is optional. If you include it, the compatibility checks are bypassed. /cx show alarms [reverse] Asynchronous events (also referred to as AENs or alarms) are originated by firmware and captured by their respective device drivers. These events reflect warning, debugging, and/or informative messages for the end user. These events are kept in a finite queue inside the kernel, awaiting extraction by user space programs such as CLI and/or 3DM. The /cx show alarms command displays all available alarms on a given controller. The default is to display the most recent alarm or AEN message first. The user can also use the [reverse] attribute to display the most recent alarm or AEN message last. Alarms generated on 7000/8000 controllers do not have dates, so you will see a '-' in the Date column. This means that it is not applicable. In addition, alarm messages on 7000/8000 controllers contain the severity in the message text, so the Severity column also shows a '-'. Typical output looks like: tw_cli> /c1 show alarms reverse Ctl Date Severity Message c1 [Fri Nov 28 04:26:31 2003] ERROR (0x04:0x0002): Degraded unit detected:unit=0, port=2 c1 [Fri Nov 28 06:13:54 2003] INFO (0x04:0x000B): Rebuild started: unit=0 c1 [Fri Nov 28 06:30:35 2003] INFO (0x04:0x003B): Background rebuild paused:unit=0 c1 [Fri Nov 28 06:33:00 2003] ERROR (0x04:0x0002): Degraded unit detected:unit=0, port=0 c1 [Fri Nov 28 06:33:04 2003] ERROR (0x04:0x0002): Degraded unit detected:unit=0, port=4 c1 [Fri Nov 28 06:33:46 2003] INFO (0x04:0x000B): Rebuild started: unit=0 c1 [Fri Nov 28 06:37:58 2003] INFO (0x04:0x000B): Rebuild started: unit=0 c1 [Fri Nov 28 07:51:34 2003] INFO (0x04:0x0005): Background rebuild done:unit=0 c1 [Fri Nov 28 07:59:43 2003] INFO (0x04:0x0005): Background rebuild done:unit=0 c1 [Mon Dec 1 02:26:12 2003] ERROR (0x04:0x0002): Degraded unit detected:unit=0, port=3 www.3ware.com 45

  • 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

Controller Object Commands
www.3ware.com
45
Given the above recommendation...
Do you want to continue ? Y|N [N]: y
Downloading the firmware from file /tmp/prom0006.img ... Done.
The new image will take effect after reboot.
force
attribute is optional. If you include it, the compatibility checks are
bypassed.
/c
x
show alarms [reverse]
Asynchronous events (also referred to as AENs or alarms) are originated by
firmware and captured by their respective device drivers. These events reflect
warning, debugging, and/or informative messages for the end user. These
events are kept in a finite queue inside the kernel, awaiting extraction by user
space programs such as CLI and/or 3DM.
The /cx show alarms command displays all available alarms on a given
controller. The default is to display the most recent alarm or AEN message
first. The user can also use the [
reverse
] attribute to display the most recent
alarm or AEN message last.
Alarms generated on 7000/8000 controllers do not have dates, so you will see
a '-'
in the Date column. This means that it is not applicable. In addition,
alarm messages on 7000/8000 controllers contain the severity in the message
text, so the Severity column also shows a '-'.
Typical output looks like:
tw_cli> /c1 show alarms reverse
Ctl Date
Severity Message
--------------------------------------------------------------------------------------------
c1
[Fri Nov 28 04:26:31 2003] ERROR
(0x04:0x0002): Degraded unit detected:unit=0, port=2
c1
[Fri Nov 28 06:13:54 2003] INFO
(0x04:0x000B): Rebuild started: unit=0
c1
[Fri Nov 28 06:30:35 2003] INFO
(0x04:0x003B): Background rebuild paused:unit=0
c1
[Fri Nov 28 06:33:00 2003] ERROR
(0x04:0x0002): Degraded unit detected:unit=0, port=0
c1
[Fri Nov 28 06:33:04 2003] ERROR
(0x04:0x0002): Degraded unit detected:unit=0, port=4
c1
[Fri Nov 28 06:33:46 2003] INFO
(0x04:0x000B): Rebuild started: unit=0
c1
[Fri Nov 28 06:37:58 2003] INFO
(0x04:0x000B): Rebuild started: unit=0
c1
[Fri Nov 28 07:51:34 2003] INFO
(0x04:0x0005): Background rebuild done:unit=0
c1
[Fri Nov 28 07:59:43 2003] INFO
(0x04:0x0005): Background rebuild done:unit=0
c1
[Mon Dec
1 02:26:12 2003] ERROR
(0x04:0x0002): Degraded unit detected:unit=0, port=3