[Check_mk (english)] How to monitor XenServer

Archive checkmk-en
1

What is the best way to monitor xenserver?
with check_mk agent or snmp?

snmp is not showing much info.

agent is reporting many false/possessive.

###Sample messages:

few of:

Check_MK PROBLEM

(Service Check Timed Out)

too many of:

Vmalloc address space

CRIT - total 148.0 MB, used 11.7 MB, largest chunk 22.5 MB (critical at 32.0 MB!!)

tones of many different interface alerts:

Interface 17 PROBLEM

UNKNOWN - no such interface

Interface 12

WARN - [tap19.0] (up) MAC: fe:ff:ff:ff:ff:ff, 10MBit/s (wrong speed, expected: 0Bit/s)(!)

OK - [bond0.110] (up) MAC: zz:39:zz:02:zz:b0, speed unknown

Service description Interface 12

State

State OK → OK (FLAPPINGSTOP) since 0d 00:21:38

Output OK - [vif1zz0.0] (up) MAC: fe:ff:ff:ff:ff:ff, speed unknown, in: 4.25kB/s, out: 172.zzB/s

Service description Interface 12

State

State OK → WARNING (PROBLEM) since 0d 00:00:01

Output WARN - [tap19.0] (up) MAC: fe:ff:ff:ff:ff:ff, 10MBit/s (wrong speed, expected: 0Bit/s)(!)

Service description Interface 12

State

State OK → OK (FLAPPINGSTOP) since 0d 00:21:38

Output OK - [vif1zz0.0] (up) MAC: fe:ff:ff:ff:ff:ff, speed unknown, in: 4.25kB/s, out: 172.zzB/s

Service description Interface 12

State

State WARNING → OK (FLAPPINGSTART) since 0d 00:00:00

Output OK - [vif1zz0.0] (up) MAC: fe:ff:ff:ff:ff:ff, speed unknown, in: 4.00MB/s, out: 8.41MB/s

Service description Interface 14

State

State WARNING → OK (FLAPPINGSTART) since 0d 00:00:01

Output OK - [vif12.0] (up) MAC: fe:ff:ff:ff:ff:ff, speed unknown, in: 3.56kB/s, out: 201.43kB/s

Service description Interface 14

State

State OK → WARNING (PROBLEM) since 0d 00:00:01

Output WARN - [tap85.0] (up) MAC: fe:ff:ff:ff:ff:ff, 10MBit/s (wrong speed, expected: 0Bit/s)(!)

Service description Interface 08

State

State OK → CRITICAL (PROBLEM) since 0d 00:00:07

Output CRIT - [bond0] (up) MAC: zz:9d:zz:30:zz:zz speed unknown, in: 241.66kB/s, in-errors: 19.59%(!!) = 0.1, out: 2.65kB/s

Service description Interface 07

State

State OK → CRITICAL (PROBLEM) since 0d 00:00:01

Output CRIT - [eth5] (up) MAC: zz:9d:zz:30:zz:zz, 10.00GBit/s, in: 239.21kB/s, in-errors: 27.92%(!!) = 0.1, out: 2.65kB/s

Service description Interface 10

State

State OK → CRITICAL (PROBLEM) since 0d 00:00:01

Output CRIT - [bond0.110] (down)(!!) MAC: zz:39:zz:02:zz:zz, speed unknown

···

Regards,
Prashant Patel

2

It is best to use the agent. The output you gave are no false positive errors. You need to configure to ignore the virtual interfaces as these are not possible to monitor.
The Vmalloc check can be configured to not show this as error what you get.

Without good rules you will have many systems with “false positive” alerts.

Best regards

Andreas

···

Prashant Patel drsolaris8@gmail.com schrieb am Mi., 17. Juni 2015 um 21:18 Uhr:

What is the best way to monitor xenserver?
with check_mk agent or snmp?

snmp is not showing much info.

agent is reporting many false/possessive.

###Sample messages:

few of:

Check_MK PROBLEM

(Service Check Timed Out)

too many of:

Vmalloc address space

CRIT - total 148.0 MB, used 11.7 MB, largest chunk 22.5 MB (critical at 32.0 MB!!)

tones of many different interface alerts:

Interface 17 PROBLEM

UNKNOWN - no such interface

Interface 12

WARN - [tap19.0] (up) MAC: fe:ff:ff:ff:ff:ff, 10MBit/s (wrong speed, expected: 0Bit/s)(!)

OK - [bond0.110] (up) MAC: zz:39:zz:02:zz:b0, speed unknown

Service description Interface 12

State

State OK → OK (FLAPPINGSTOP) since 0d 00:21:38

Output OK - [vif1zz0.0] (up) MAC: fe:ff:ff:ff:ff:ff, speed unknown, in: 4.25kB/s, out: 172.zzB/s

Service description Interface 12

State

State OK → WARNING (PROBLEM) since 0d 00:00:01

Output WARN - [tap19.0] (up) MAC: fe:ff:ff:ff:ff:ff, 10MBit/s (wrong speed, expected: 0Bit/s)(!)

Service description Interface 12

State

State OK → OK (FLAPPINGSTOP) since 0d 00:21:38

Output OK - [vif1zz0.0] (up) MAC: fe:ff:ff:ff:ff:ff, speed unknown, in: 4.25kB/s, out: 172.zzB/s

Service description Interface 12

State

State WARNING → OK (FLAPPINGSTART) since 0d 00:00:00

Output OK - [vif1zz0.0] (up) MAC: fe:ff:ff:ff:ff:ff, speed unknown, in: 4.00MB/s, out: 8.41MB/s

Service description Interface 14

State

State WARNING → OK (FLAPPINGSTART) since 0d 00:00:01

Output OK - [vif12.0] (up) MAC: fe:ff:ff:ff:ff:ff, speed unknown, in: 3.56kB/s, out: 201.43kB/s

Service description Interface 14

State

State OK → WARNING (PROBLEM) since 0d 00:00:01

Output WARN - [tap85.0] (up) MAC: fe:ff:ff:ff:ff:ff, 10MBit/s (wrong speed, expected: 0Bit/s)(!)

Service description Interface 08

State

State OK → CRITICAL (PROBLEM) since 0d 00:00:07

Output CRIT - [bond0] (up) MAC: zz:9d:zz:30:zz:zz speed unknown, in: 241.66kB/s, in-errors: 19.59%(!!) = 0.1, out: 2.65kB/s

Service description Interface 07

State

State OK → CRITICAL (PROBLEM) since 0d 00:00:01

Output CRIT - [eth5] (up) MAC: zz:9d:zz:30:zz:zz, 10.00GBit/s, in: 239.21kB/s, in-errors: 27.92%(!!) = 0.1, out: 2.65kB/s

Service description Interface 10

State

State OK → CRITICAL (PROBLEM) since 0d 00:00:01

Output CRIT - [bond0.110] (down)(!!) MAC: zz:39:zz:02:zz:zz, speed unknown

–
Regards,
Prashant Patel

checkmk-en mailing list

checkmk-en@lists.mathias-kettner.de

http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

We’ll meet in Munich for the 2nd Check_MK Conference!

Book your place now and be part of it.

October 18th-20th, 2015

http://mathias-kettner.com/conference