Module: check_mk
Branch: master
Commit: 5abf1bede894e1c06fec85270e23c59ebe682acb
URL:
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=5abf1bede894e1…
Author: Bernd Stroessenreuther <bs(a)mathias-kettner.de>
Date: Wed Jul 31 15:06:16 2013 +0200
initial release of check manpages for emc_storage
---
checkman/emc_storage.disks | 35 +++++++++++++++++++++++
checkman/emc_storage.hba | 28 +++++++++++++++++++
checkman/emc_storage.hw_status | 49 +++++++++++++++++++++++++++++++++
checkman/emc_storage.lun_usage | 30 ++++++++++++++++++++
checkman/emc_storage.raidgroup_status | 28 +++++++++++++++++++
checkman/emc_storage.sp_status | 26 +++++++++++++++++
6 files changed, 196 insertions(+)
diff --git a/checkman/emc_storage.disks b/checkman/emc_storage.disks
new file mode 100644
index 0000000..8e3041d
--- /dev/null
+++ b/checkman/emc_storage.disks
@@ -0,0 +1,35 @@
+title: EMC Storage: Status and I/O of Disks
+agents: emc
+catalog: hw/storage
+license: GPL
+distribution: check_mk
+description:
+ Reports the status and the I/O rate of a disk in an EMC storage system.
+
+ Returns {OK} if the number of Hard Read Errors is 0 and the number
+ of Hard Write Errors is 0. {CRIT} is returned otherwise.
+
+ Hint for implementation: Look for "Hard Read Errors:" and "Hard Write
Errors:"
+ lines in section "Bus x Enclosure y Disk z" lines found under
+ "All Disks Information"
+
+ I/O rates (in Bytes/sec) are just informational and do not trigger any state
+ other than {OK}
+
+ Hint for implementation: Look for "Kbytes Read:" and "Kbytes
Written:"
+ lines in section "Bus x Enclosure y Disk z" lines found under
+ "All Disks Information". Remember values of last check and devide by the
+ time since last check.
+
+item:
+ Consists of bus ID, enclosure ID and disk ID as returned by the agent.
+ E. g. "Bus 0 Enclosure 0 Disk 0"
+
+ Hint for implementation: Look for "Bus x Enclosure y Disk z" lines in section
+ "All Disks Information"
+
+perfdata:
+ Two values: Read-I/O and Write-I/O in Bytes/sec
+
+inventory:
+ Automatically configures one check for every disk listed in the agent output.
diff --git a/checkman/emc_storage.hba b/checkman/emc_storage.hba
new file mode 100644
index 0000000..58bd975
--- /dev/null
+++ b/checkman/emc_storage.hba
@@ -0,0 +1,28 @@
+title: EMC Storage: iSCSI traffic on HBAs
+agents: emc
+catalog: hw/storage
+license: GPL
+distribution: check_mk
+description:
+ Reports the traffic on iSCSI HBAs in an EMC storage system.
+
+ The values for Blocks Read/sec and Blocks Written/sec are just informational.
+ The check always returns {OK}
+
+ Hint for implementation: Look for "Blocks Read:" and "Blocks
Written:"
+ lines in section "SP Name: <my Name>" and "SP Port ID: <my
ID>" lines found under
+ "Information about each SPPORT:". Remember values of last check and devide by
the
+ time since last check.
+
+item:
+ Consists of the SP Name and the SP Port ID as returned by the agent.
+ E. g. "SP A Port 0"
+
+ Hint for implementation: Look for "SP Name:" and "SP Port ID:" lines
in section
+ "Information about each SPPORT:"
+
+perfdata:
+ Two values: Blocks Read/sec and Blocks Written/sec
+
+inventory:
+ Automatically configures one check for every HBA listed in the agent output.
diff --git a/checkman/emc_storage.hw_status b/checkman/emc_storage.hw_status
new file mode 100644
index 0000000..2305b02
--- /dev/null
+++ b/checkman/emc_storage.hw_status
@@ -0,0 +1,49 @@
+title: EMC Storage: Hardware Status
+agents: emc
+catalog: hw/storage
+license: GPL
+distribution: check_mk
+description:
+ Reports the status of Power Supplies, SPS, SPS Cabeling, LCC, CPU Modules,
+ SP I/O Modules and DIMM Modules on EMC storage systems.
+
+ Returns {OK} if the agent reports "Present" or "Valid" status and
{CRIT}
+ on every other status.
+
+ Hint for implementation: Look for lines matching
+ Bus x Enclosure y Power z State:
+ Bus x Enclosure y SPS z State:
+ Bus x Enclosure y SPS z Cabling State:
+ Bus x Enclosure y CPU Module z State:
+ Bus x Enclosure y SP z I/O Module w State:
+ Bus x Enclosure y DIMM Module z State:
+ Bus x Enclosure y LCC z State:
+ in section "Array Information"
+
+item:
+ The name of the storage processor as returned by the special agent.
+ E. g.
+ Bus 0 Enclosure 0 Power A
+ Bus 0 Enclosure 0 Power B
+ Bus 0 Enclosure 0 SPS A
+ Bus 0 Enclosure 0 SPS B
+ Bus 0 Enclosure 0 SPS A Cabling
+ Bus 0 Enclosure 0 SPS B Cabling
+ Bus 0 Enclosure 0 CPU Module A
+ Bus 0 Enclosure 0 CPU Module B
+ Bus 0 Enclosure 0 SP A I/O Module 0
+ Bus 0 Enclosure 0 SP A I/O Module 1
+ Bus 0 Enclosure 0 SP B I/O Module 0
+ Bus 0 Enclosure 0 SP B I/O Module 1
+ Bus 0 Enclosure 0 DIMM Module A
+ Bus 0 Enclosure 0 DIMM Module B
+ Bus 0 Enclosure 1 LCC A
+
+ Hint for implementation: see description
+
+perfdata:
+ None
+
+inventory:
+ Automatically configures one check for every hardware status entry listed
+ in the agent output.
diff --git a/checkman/emc_storage.lun_usage b/checkman/emc_storage.lun_usage
new file mode 100644
index 0000000..215a55f
--- /dev/null
+++ b/checkman/emc_storage.lun_usage
@@ -0,0 +1,30 @@
+title: EMC Storage: Usage of LUNs
+agents: emc
+catalog: hw/storage
+license: GPL
+distribution: check_mk
+description:
+ Reports the usage of LUNs on EMC storage systems.
+
+ You can set levels for minimum free space to result in {WARN} and {CRIT}
+ state. The levels can be given in absolute megabytes or percent of the
+ total space available in the LUN.
+
+ Hint for implementation: Look for "LUN Capacity(Megabytes):" line in
+ section "LOGICAL UNIT NUMBER <my ID>" under "All logical Units
Information"
+ But: Where can we get actual used space in the LUN from? To be defined!
+
+item:
+ The ID of the LUN as returned by the special agent.
+ E. g. "18"
+
+ Hint for implementation: Look for "LOGICAL UNIT NUMBER"
+ lines in section "All logical Units Information"
+
+perfdata:
+ One value: The used capacity in bytes, together with it's warn and crit
+ levels as well as the maximum (also in bytes)
+
+inventory:
+ Automatically configures one check for every LUN listed
+ in the agent output.
diff --git a/checkman/emc_storage.raidgroup_status
b/checkman/emc_storage.raidgroup_status
new file mode 100644
index 0000000..a4595a1
--- /dev/null
+++ b/checkman/emc_storage.raidgroup_status
@@ -0,0 +1,28 @@
+title: EMC Storage: Status of RAID groups
+agents: emc
+catalog: hw/storage
+license: GPL
+distribution: check_mk
+description:
+ Reports the status of RAID groups in EMC storage systems.
+
+ Returns {OK} if ... and {CRIT} on ...
+ (to be defined)
+
+ Hint for implementation: Look for "RaidGroup State:" line and following
+ in section "RaidGroup ID: <my ID>" under "All RAID Groups
Information"
+ Which states are good states and which are bad states is to be defined
+
+item:
+ The RAID group ID as returned by the special agent.
+ E. g. "4"
+
+ Hint for implementation: Look for "RaidGroup ID:" line in section
+ "All RAID Groups Information"
+
+perfdata:
+ None
+
+inventory:
+ Automatically configures one check for every RAID group listed
+ in the agent output.
diff --git a/checkman/emc_storage.sp_status b/checkman/emc_storage.sp_status
new file mode 100644
index 0000000..eeee52b
--- /dev/null
+++ b/checkman/emc_storage.sp_status
@@ -0,0 +1,26 @@
+title: EMC Storage: Status of StorageProcessors (sp)
+agents: emc
+catalog: hw/storage
+license: GPL
+distribution: check_mk
+description:
+ Reports the status of StorageProcessors (sp) on EMC storage systems.
+
+ Returns {OK} if the agent reports "Present" status and {CRIT} on every other
+ status.
+
+ Hint for implementation: Look for "SP * State:" line in section
+ "Array Information", Present -> OK, everything else -> CRIT
+
+item:
+ The name of the storage processor as returned by the special agent.
+ E. g. "A"
+
+ Hint for implementation: see at description
+
+perfdata:
+ None
+
+inventory:
+ Automatically configures one check for every storage processor listed
+ in the agent output.