PE2900 omsa 5.2 Debian etch
L.P.H. van Belle
belle at bazuin.nl
Tue Aug 14 01:48:26 CDT 2007
Hi everybody,
I'm new here on the list and here is some info.
Im running a PE2900 with debian etch.
i had some problem with the install and here is my experiance, hope it helps
someone.
my hardware specs of the PE2900
2 x Quad 2,33Ghz 8 Gb Ram, SAS Perc 5I Raid with 3 x "Raid 1 72Gb" +
Ultrium LTO2
And Drac 5 card.
When you install debian Etch on a server with a drac controller, in de
install mode
de harddrives are detected as "SDB + SDC + SDD" Everything installs cleanly
and
is corrected detected. ( kernel 2.6.18-4 )
You eth0 is atm, NIC2 and eth1 = NIC1
Upgrade your kernel to 2.6.20 or higer and this is fixed.
simple get the custom iso from : http://kmuto.jp/debian/d-i/
and select kernel 2.6.21 at the end. and you nic1 = eth0 and nic2 = eth1
When you reboot after the debian install, your loader stops at "Waiting for
root fs"
this is because of the DRAC5 controller.
explanation: The debian installer detects a USB Virtual CD Player, and sets
it to SDA !
when you reboot, de megaraid_sas is loaded now before the usb-storage driver
and
sets the HDD: SDA (was SDB ) SDB ( was SDC) and SDC ( was SDD ). ( And
Virtual Storage SDD )
To very simple fix this. Just remove the cables from the DRAC5 controller
and reinstall.
Other solution, fix grub fix fstab, make drivers load in correct order in
initrd.img
Just before the reboot when installing, change to TTY2 , type chroot
/target/ , and fix your os.
I tried both options, and the first is te most easy one. and beleave me it
saves time.. ;-)
reboot, check is your server loads normaly, shut it down, !! UNPLUG
POWERCORD !!
and reconnect your DRAC Card.
For the apt/sources.list u uses the following.
#
# /etc/apt/sources.list
#
#########################################
#### Stable sources
#
# etch
#
deb http://ftp.nl.debian.org/debian/ etch main contrib non-free
deb-src http://ftp.nl.debian.org/debian/ etch main contrib non-free
#
# Security updates
#
deb http://security.debian.org/ etch/updates main contrib non-free
deb-src http://security.debian.org/ etch/updates main contrib non-free
#########################################
### volatile updates ( get some newer packages )
### http://volatile.debian.net/debian-volatile/
deb http://volatile.debian.org/debian-volatile etch/volatile main
contrib non-free
deb-src http://volatile.debian.org/debian-volatile etch/volatile main
contrib non-free
#########################################
### Etch Debian-unofficial
### www.debian-unofficial.org
deb http://ftp.debian-unofficial.org/debian etch main contrib non-free
restricted
deb-src http://ftp.debian-unofficial.org/debian etch main contrib non-free
restricted
### Etch backports
### www.backports.org
deb http://www.backports.org/debian etch-backports main contrib non-free
deb-src http://www.backports.org/debian etch-backports main contrib non-free
### Dell Monitoring
### OMSA
deb ftp://ftp.sara.nl/pub/sara-omsa dell sara
Next was OMSA5, i have read lots from the mailing list, and the most simple
is.
add "deb ftp://ftp.sara.nl/pub/sara-omsa dell sara" to the /etc/apt/sources
install JAVA ( apt-cache search sun | grep java )
apt-get install sun-java6-jre Java is needed by OMSA
and apt-get install snmp snmpd dellomsa libopenipmi openipmi lsb-base
enable snmp in OMSA /etc/init.d/dataeng enablesnmp
restart OMSA /etc/init.d/dataeng restart
and you see usleep messages ( command not found )
get the source here, there is no debian packages atm.
http://www.rz.uni-karlsruhe.de/~andy/source/Local/usleep-1.0/
and build usleep ( you need gcc and kernel-headers to build )
( i'll make a deb, but other things have to go first atm. )
and copy usleep in /bin
It works also without usleep, but i like clean log files ;-)
check if you can get info from snmpd
snmpwalk -v 1 -OS -c public localhost .1.3.6.1.4.1.674.10892.1
When you get lost of output it works.
if not check /etc/snmp/snmpd.conf
In the section Access Controll;
com2sec .... etc.. etc.
i disabled the first and enabled the 2e and the 3e
( and for security i changed the 3e's community.
Next i saw this on the mailing list.
omconfig system shutdown action=reboot osfirst=true
and the system came back with the following error message
Error! Reboot unsupported on this system.
You can fix this by simply editing : /etc/default/dsm_sa_ipmi
set the POWER.. to yes and restart OMSA /etc/init.d/dataeng restart
And now my question ;-)
Setting up the Web Management (OMSA)
I googled a bit around and found this.
ln -s /opt/dell/srvadmin/iws/bin/linux/omawsd.src /etc/sysconfig/omawsd.src
Edit the iws.ini file (must change username/password):
/opt/dell/srvadmin/iws/config/iws.ini
so i changed the username and password
and tried to logon the website.
wel off-course this didnt work.
so i tried my "root" with "MyOwnpassword" and i could login.
A cleaner nicer config for the webinterface would be nice..
the start/stop script is not working fine.
i does not remove the lock file and the stop command does not stop
the webservices. just kill it and remove te lockfile before starting
it up again.
The End,
I hope someone likes it.
And now the question.. ;-)
why do we have to change the username/password in the iws.ini
if root is used ?
Greetz,
Louis
More information about the Linux-PowerEdge
mailing list