Module: check_mk
Branch: master
Commit: 7ec34bfafa123ba46a76b1545ef8627f143b03d9
URL:
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=7ec34bfafa123b…
Author: Florian Heigl <fh(a)mathias-kettner.de>
Date: Fri Aug 10 16:49:21 2012 +0200
add new bug entries
---
.bugs/717 | 135 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
.bugs/718 | 13 ++++++
.bugs/719 | 11 +++++
3 files changed, 159 insertions(+), 0 deletions(-)
diff --git a/.bugs/717 b/.bugs/717
new file mode 100644
index 0000000..478c3a4
--- /dev/null
+++ b/.bugs/717
@@ -0,0 +1,135 @@
+Title: MegaRaid BBU check should handle learning state
+Component: checks
+State: open
+Date: 2012-08-10 16:35:33
+Targetversion: 1.2.0
+Class: feature
+
+Most MegaRAID controllers come with a rechargable Li battery for the backup voltage.
+This voltage is used to sustain power to the cache ram should the power fail or the OS
crash.
+Once the system comes up, the outstanding writes are flushed to disk before OS boot
starts.
+
+The newest models use a flash memory bank instead that is fed using a supercap that lasts
+long enough to copy the ram onto flash.
+
+All non-flash models need to do maintenance on their batteries to avoid gas buildup and
+to test remaining capacity. This is called a learn cycle and occurs roughly once a month
+,but the controller does not support setting a schedule.
+
+During the learn cycle, the controller is set to write-through and then the battery is
+discharged a few times, and our check starts to look like a christmas tree.
+
+We need to handle the learn cycle which is detectable.
+If the agent reports "learn cycle requested: yes" then it will sstart at some
time,
+and if it says "learn cycle active: yes" then it is running already.
+
+
+Output 1:
+BBU status for Adapter: 0
+
+BatteryType: iBBU
+Voltage: 3251 mV
+Current: -375 mA
+Temperature: 30 C
+
+Battery State : Operational
+
+BBU Firmware Status:
+
+ Charging Status : Discharging
+ Voltage : Low
+ Temperature : OK
+ Learn Cycle Requested : Yes
+ Learn Cycle Active : Yes
+ Learn Cycle Status : OK
+ Learn Cycle Timeout : No
+ I2c Errors Detected : No
+ Battery Pack Missing : No
+ Battery Replacement required : No
+ Remaining Capacity Low : No
+ Periodic Learn Required : No
+ Transparent Learn : No
+ No space to cache offload : No
+ Pack is about to fail & should be replaced : No
+ Cache Offload premium feature required : No
+ Module microcode update required : No
+
+
+
+GasGuageStatus:
+ Fully Discharged : Yes
+ Fully Charged : No
+ Discharging : Yes
+ Initialized : Yes
+ Remaining Time Alarm : Yes
+ Remaining Capacity Alarm: Yes
+ Discharge Terminated : Yes
+ Over Temperature : No
+ Charging Terminated : No
+ Over Charged : No
+
+Relative State of Charge: 0 %
+Charger System State: 49169
+Charger System Ctrl: 0
+Charging current: 100 mA
+Absolute state of charge: 0 %
+Max Error: 8 %
+
+Exit Code: 0x00
+
+
+
+Output 2:
+
+
+BBU status for Adapter: 0
+
+BatteryType: iBBU
+Voltage: 4048 mV
+Current: 139 mA
+Temperature: 27 C
+
+Battery State : Operational
+
+BBU Firmware Status:
+
+ Charging Status : Charging
+ Voltage : OK
+ Temperature : OK
+ Learn Cycle Requested : Yes
+ Learn Cycle Active : No
+ Learn Cycle Status : OK
+ Learn Cycle Timeout : No
+ I2c Errors Detected : No
+ Battery Pack Missing : No
+ Battery Replacement required : No
+ Remaining Capacity Low : No
+ Periodic Learn Required : No
+ Transparent Learn : No
+ No space to cache offload : No
+ Pack is about to fail & should be replaced : No
+ Cache Offload premium feature required : No
+ Module microcode update required : No
+
+
+
+GasGuageStatus:
+ Fully Discharged : No
+ Fully Charged : No
+ Discharging : No
+ Initialized : Yes
+ Remaining Time Alarm : No
+ Remaining Capacity Alarm: No
+ Discharge Terminated : No
+ Over Temperature : No
+ Charging Terminated : No
+ Over Charged : No
+
+Relative State of Charge: 1 %
+Charger System State: 49168
+Charger System Ctrl: 0
+Charging current: 512 mA
+Absolute state of charge: 25 %
+Max Error: 8 %
+
+Exit Code: 0x00
diff --git a/.bugs/718 b/.bugs/718
new file mode 100644
index 0000000..c40b25d
--- /dev/null
+++ b/.bugs/718
@@ -0,0 +1,13 @@
+Title: WATO tags menue has issues when deleting tags
+Component: wato
+State: open
+Date: 2012-08-10 16:42:19
+Targetversion: future
+Class: bug
+
+If you create an empty tag (desc. and tag id) and then another one the empty tag will
+corrupt the tag id's.
+It seems this faulty state is also saved:
+If you delete another tag later on, all tags below the tag you're deleting are also
lost.
+
+It's already verified to be a bug ;)
diff --git a/.bugs/719 b/.bugs/719
new file mode 100644
index 0000000..765c771
--- /dev/null
+++ b/.bugs/719
@@ -0,0 +1,11 @@
+Title: if Check should track separate levels for in and out traffic bytes / levels
+Component: checks
+State: open
+Date: 2012-08-10 16:44:48
+Targetversion: future
+Class: feature
+
+Certain customers (ISP, or people with asymetric speeds on an inteface) put different
focus
+on interface monitoring - they don't need to detect the 1 out of 10000 clients that
has heavy
+traffic, but they need to detect bw excess in either of two directions.
+The check already tracks rx and tx but doesn't allow separate alerting like disk io
would.