Module: check_mk
Branch: master
Commit: 4f0cfa1d1b001258a71ba831698e76e87072ab13
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=4f0cfa1d1b0012…
Author: Lars Michelsen <lm(a)mathias-kettner.de>
Date: Thu Mar 1 12:36:14 2018 +0100
5873 IPMI Management board
The management board of hosts can now be configured to be monitored via IPMI
as alternative to the previous SNMP monitoring.
To configure the IPMI management board for a host, you need to edit the
host configuration. Set the addresss of the management board, choose IPMI
as management board protocol and specify the IPMI credentials.
After this, you should be able to find new services named "Management interface: ..."
using the service discovery.
To make your configuration a bit less explicit, you can specify the IPMI protocol
and credentials on folders instead of specifying it explicit for each host.
Another option is to use the ruleset "Management board config" to configure the
credentials. But you will have to set at least the protocol on host/folders and
the management board address for each host.
Change-Id: Ia6c69343b4319855dc2ae138be2852df4d9ce844
---
.werks/5873 | 23 +++++++++++++++++++++++
1 file changed, 23 insertions(+)
diff --git a/.werks/5873 b/.werks/5873
new file mode 100644
index 0000000..a183b7b
--- /dev/null
+++ b/.werks/5873
@@ -0,0 +1,23 @@
+Title: IPMI Management board
+Level: 2
+Component: core
+Compatible: compat
+Edition: cre
+Version: 1.5.0i4
+Date: 1519903894
+Class: feature
+
+The management board of hosts can now be configured to be monitored via IPMI
+as alternative to the previous SNMP monitoring.
+
+To configure the IPMI management board for a host, you need to edit the
+host configuration. Set the addresss of the management board, choose IPMI
+as management board protocol and specify the IPMI credentials.
+After this, you should be able to find new services named "Management interface: ..."
+using the service discovery.
+
+To make your configuration a bit less explicit, you can specify the IPMI protocol
+and credentials on folders instead of specifying it explicit for each host.
+Another option is to use the ruleset "Management board config" to configure the
+credentials. But you will have to set at least the protocol on host/folders and
+the management board address for each host.
Module: check_mk
Branch: master
Commit: 9fe9bc9de46a0ecf0d88b54519317212dd6ed05d
URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=9fe9bc9de46a0e…
Author: Jukka Aro <ja(a)mathias-kettner.de>
Date: Thu Mar 1 10:02:46 2018 +0100
Build Win-agent unit tests with common AM_CPPFLAGS
The common flags were accidentally forgotten when building unit tests.
Now it is possible to use, e. g., C++17 features also in unit tests.
---
agents/windows/Makefile.am | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/agents/windows/Makefile.am b/agents/windows/Makefile.am
index 0d01e6f..70c2d62 100644
--- a/agents/windows/Makefile.am
+++ b/agents/windows/Makefile.am
@@ -11,7 +11,7 @@ LD_COMMON = -lwsock32 -lws2_32 -lole32 -loleaut32 -lwbemuuid -lpsapi -lshlwapi -
check_mk_agent_LDADD = check_mk_agent.res libcheck_mk_agent.a $(LD_COMMON)
-WindowsAgentTest_CPPFLAGS = -I$(top_srcdir)/sections -I$(top_srcdir)/test
+WindowsAgentTest_CPPFLAGS = $(AM_CPPFLAGS) -I$(top_srcdir)/sections -I$(top_srcdir)/test
WindowsAgentTest_LDADD = libcheck_mk_agent.a -lgtest -lgmock $(LD_COMMON)
wmitest_LDADD = $(LD_COMMON)