Monitoring MD3000 using OMSA?
libor.klepac at bcom.cz
Tue Feb 23 06:20:19 CST 2010
i have installer OMSA from sara.nl (running debian here).
I hoped, that i'll be able to monitor/manage md3000 with it.
I have had to rebuild mptlinux drivers (some patching of mptlan.c and mptlan.h
was needed http://groups.google.com/group/android-
kernel/browse_thread/thread/ab511cde228d7c77) , so omsa doesn't report that
they are too old.
But i'm not able to manage it, omreport only shows those two sas5/e adapters
(web interface is now dead, it only segfaults on start with this error
when i stop openvpn links to server, it works - as i found somewhere its
problem with non eth* interfaces)
We need to monitor md3000 before we start to use it for customer data. It's
now in some strange state, i can use virtual disk from it, but it says
"Individual Physical Disk - Degraded Path" and "Degraded Physical Disk
Channel" (it started on friday when i removed some test-only disk and created
one vdisk for customer data)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.us.dell.com/pipermail/linux-poweredge/attachments/20100223/4c0353c8/attachment.sig
More information about the Linux-PowerEdge