This post is more than 5 years old
17 Posts
0
43394
May 13th, 2009 17:00
Managing MD3000 inband with CentOS host
Hi,
With a Windows 2003 host, i was able to manage an MD3000 inband. But now that it has CentOS 5.3 installed, i'm unable to manage it inband. What's the necessary drivers/utils i need on there?
I have already installed Openmanage, dkms. mptlinux drivers.
Thanks.
No Events found!
daunce
17 Posts
1
May 15th, 2009 06:00
Well I think i've solved it.
For in-band management (even remotely), MDSM software has to be installed on the host. Then SMagent is available.
The only problem is we do a minimal linux install, but MDSM requires Xwindows to be installed. But now that it is installed, i might be able to grab /opt/dell/mdstoragemanager/*.rpm which includes SMagent.rpm and copy them to our real server.
Thanks all.
Dev Mgr
6 Operator
•
9.3K Posts
0
May 14th, 2009 08:00
First off; CentOS isn't on the support matrix, but you inband management should work I think.
Do you have the iSCSI connections established? These are needed for inband management.
dining_philosop
60 Posts
0
May 14th, 2009 11:00
Make sure that the software load that you added from the MD Storage resource CD was supported on the kernel version for Cent OS 5.3. There has been significant changes in the Linux storage stack between Cent OS 4.0 and Cent OS 5.3. You may beed to get the new bits for the MD agent support code from the MD resource CD and install them.
http://support.dell.com/support/downloads/download.aspx?c=us&l=en&s=gen&releaseid=R214061&SystemID=PWV_MD3000I&servicetag=&os=WNET&osl=en&deviceid=12882&devlib=0&typecnt=0&vercnt=6&catid=-1&impid=-1&formatcnt=1&libid=52&fileid=303159
daunce
17 Posts
0
May 14th, 2009 22:00
I used the new software from the website rather than what came with the MD3000. (note: it's not the iSCSI version.. )
The manuals mentions restartign SMagent, but i dont have that.. and have no idea where to get it.. I am guessing that i need this running to be able to manage the MD3000 through tthe host. Any ideas where it comes from?
I mounted the MD3000 CD, and ran through the install.sh
During the install of the SAS 5/E adapter, it says:
============================================================
Loading kernel module source and prebuilt module binaries (if any)
Installing prebuilt kernel module binaries (if any)
Module build for the currently running kernel was skipped since the
kernel source for this kernel does not seem to be installed.
Your DKMS tree now includes:
sg, 3.5.34dell, 2.6.18-8.el5, x86_64: built
This option requires the following package(s) to be installed:
kernel-sources or kernel-devel
gcc
Press any key to return to the main menu.
============================================================
And for the multipath driver:
linuxrdac-09.03.0C06.0030-1dkms
Uninstall of linuxrdac module (version 09.03.0C06.0030) beginning:
-------- Uninstall Beginning --------
Module: linuxrdac
Version: 09.03.0C06.0030
Kernel: 2.6.18-92.el5 (i686)
-------------------------------------
Status: This module version was INACTIVE for this kernel.
Running the post_remove script:
depmod.....
DKMS: uninstall Completed.
------------------------------
Deleting module version: 09.03.0C06.0030
completely from the DKMS tree.
------------------------------
Done.
============================================================
dmesg says:
Vendor: DELL Model: MD3000 Rev: 0735
Type: Direct-Access ANSI SCSI revision: 05
Vendor: DELL Model: Universal Xport Rev: 0735
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sdb: 40960 512-byte hdwr sectors (21 MB)
sdb: Write Protect is off
sdb: Mode Sense: 77 00 10 08
SCSI device sdb: drive cache: write through w/ FUA
SCSI device sdb: 40960 512-byte hdwr sectors (21 MB)
sdb: Write Protect is off
sdb: Mode Sense: 77 00 10 08
SCSI device sdb: drive cache: write through w/ FUA
sdb:
sd 2:0:0:31: Attached scsi disk sdb