PE 1750 and OMSA

Paul Shutleworth paul at aqualec.co.uk
Sat Mar 1 05:13:07 CST 2008


Hi Richard
 
Thanks for the pointer.
 
This was indeed the fix only slightly different.
 
On checking for ipmi or openipmi I found there were no init scripts for
either.
After a bit of digging I found that there was a 
 
/opt/dell/srvadmin/hapi/bin/dsm_sa_ipmi
and a config file for this.
 
So instead of 
 
service ipmi start
 
I did a /opt/dell/srvadmin/hapi/bin/dsm_sa_ipmi start
 
and the rest of it worked like a charm, 
 
Having run the ipmi script I now see an init script for dsm_sa_ipmi, so 
service dsm_sa_ipmi start | stop | restart will now work.
 
Now when I issue 
srvadmin-services.sh start
It starts the ipmi driver correctly.
 
I guess something must have fallen over during the install and it did not
complete.
 
 
thanks again for you help.
 
Cheers
 
Paul.
 

-----Original Message-----
From: Richard Garner [mailto:r.garner at computerservicecentre.com] On Behalf
Of Hostmaster
Sent: 28 February 2008 12:47
To: paul at aqualec.co.uk
Cc: linux-poweredge at lists.us.dell.com
Subject: RE: PE 1750 and OMSA



Ahh
 I think this is a problem I have seen (and advised on!) before in a
thread in January titled “RAID degraded on a PERC 4/im”.

 

>From that thread:

 

El 09/01/2008, a las 12:30, Richard Garner escribió:

 

> Run a srvadmin-services.sh stop. ps ax and make sure none of them are 

> running.

> Try service ipmi start, or failing that, service openipmi start.  

> One of those

> should start the IPMI kernel module and come back with success.  

> After that, then

> try srvadmin-services.sh start.

 

 

 

Dear Richard,

 

# srvadmin-services.sh stop

Shutting down DSM SA Shared Services:                      [  OK  ]

Shutting down DSM SA Connection Service:                   [  OK  ]

 

# /etc/init.d/ipmi start

Starting ipmi drivers:                                     [  OK  ]

 

# ps aux | grep -i ipmi

root     11688  0.2  0.0     0    0 ?        SN   13:19   0:00 [kipmi0]

 

# lsmod | grep -i ipmi

ipmi_devintf           13385  0

ipmi_si                37865  0

ipmi_msghandler        32041  2 ipmi_devintf,ipmi_si

 

No process related to OMSA are started.. so I start OMSA

 

 

# srvadmin-services.sh start

Starting mptctl:

Waiting for mptctl driver registration to complete:

                                                            [  OK  ]

DRAC4 probe: DRAC4 pci device not found                    [FAILED]

Starting Systems Management Device Drivers:

Starting dell_rbu:                                         [  OK  ]

Starting ipmi driver: Already started                      [  OK  ]

DRAC4 probe: DRAC4 pci device not found                    [FAILED]

Starting Systems Management Data Engine:

Starting dsm_sa_datamgr32d:                                [  OK  ]

Starting dsm_sa_eventmgr32d:                               [  OK  ]

Starting dsm_sa_snmp32d:                                   [  OK  ]

Starting DSM SA Shared Services:                           [  OK  ]

Starting DSM SA Connection Service:                        [  OK  ]

 

 

# omreport storage controller

  Controller  PERC 4/im (Embedded)

 

Controllers

ID                                : 0

Status                            : Ok

Name                              : PERC 4/im

Slot ID                           : Embedded

State                             : Ready

Firmware Version                  : 1032397

Minimum Required Firmware Version : Not Applicable

Driver Version                    : Not Applicable

Minimum Required Driver Version   : Not Applicable

Number of Connectors              : 1

Rebuild Rate                      : 100%

BGI Rate                          : Not Applicable

Check Consistency Rate            : Not Applicable

Reconstruct Rate                  : Not Applicable

Alarm State                       : Not Applicable

Cluster Mode                      : Not Applicable

SCSI Initiator ID                 : Not Applicable

Cache Memory Size                 : Not Applicable

Patrol Read Mode                  : Not Applicable

Patrol Read State                 : Not Applicable

Patrol Read Rate                  : Not Applicable

Patrol Read Iterations            : Not Applicable

 

Thanks! Now works without problems ;-)

 

Regards,

 

--

Santi Saez

Soporte Tecnico

HOSTALIA INTERNET S.L.

http://www.hostalia.com

 

 

 

 

 

Should hopefully be the key to your problem too!

Best Regards, 

Richard Garner (A+, N+, AMBCS, MOS-O) 
Hostmaster 

 

From: linux-poweredge-bounces at dell.com
[mailto:linux-poweredge-bounces at dell.com] On Behalf Of Paul Shutleworth
Posted At: 28 February 2008 12:20
Posted To: Hostmaster
Conversation: PE 1750 and OMSA
Subject: RE: PE 1750 and OMSA

 

Hi Richard

 

Thanks for the quick response.

 

It was installed with srvadmin-all option in YUM from the Dell Hardware Repo

 

 

OK Stopping srvadmin ....

 

 

[root at dell1750 ~]# srvadmin-services.sh stop
Shutting down DSM SA Shared Services:       OK             [  OK  ]

 

Shutting down DSM SA Connection Service:    OK             [  OK  ]

 

[root at dell1750 ~]#

 

 

Restart ....

 

 

[root at dell1750 ~]# srvadmin-services.sh start
Starting Systems Management Device Drivers:
Starting dell_rbu: Already started                         [  OK  ]
Starting ipmi driver:                                      [FAILED]
Starting Systems Management Device Drivers:
Starting dell_rbu: Already started                         [  OK  ]
Starting ipmi driver:                                      [FAILED]
Starting DSM SA Shared Services:            OK             [  OK  ]
Starting DSM SA Connection Service:         OK             [  OK  ]
Probe of RAC board: RAC pci device not found               [FAILED]
Starting racvnc (RAC) services:                            [  OK  ]
[root at dell1750 ~]#

 

Status ...

 

 

[root at dell1750 ~]# srvadmin-services.sh status
dell_rbu (module) is running
ipmi driver is stopped
dsm_sa_datamgr32d is stopped
dsm_sa_eventmgr32d is stopped
dsm_sa_snmp32d is stopped
dsm_om_shrsvc32d (pid 7283) is running...
dsm_om_connsvc32d (pid 7354 7353) is running...
Checking pppd (RAC) services: not running                  [FAILED]
racXvnc is stopped
[root at dell1750 ~]#

 

Looking at the above should the dsm_sa_datamgr32 and dsm_sa_eventmgr32 be
running ?

 

Thanks

 

Paul,

 

 

 

-----Original Message-----
From: Richard Garner [mailto:r.garner at computerservicecentre.com] On Behalf
Of Hostmaster
Sent: 28 February 2008 11:42
To: paul at aqualec.co.uk
Cc: linux-poweredge at lists.us.dell.com
Subject: RE: PE 1750 and OMSA

Hi Paul, and welcome to the list!

 

When you did your yum install, was it the srvadmin-all package? I am
wondering if something is missing.

 

If so, when your ran “srvadmin-services.sh start”, did everything start
correctly?

Best Regards, 

Richard Garner (A+, N+, AMBCS, MOS-O) 

From: linux-poweredge-bounces at dell.com
[mailto:linux-poweredge-bounces at dell.com] On Behalf Of Paul Shutleworth
Posted At: 28 February 2008 11:37
Posted To: Hostmaster
Conversation: PE 1750 and OMSA
Subject: PE 1750 and OMSA

 

Hi everyone, I am new here so please be gentle!

 

I have been setting up a PE 1750 to run as a web/mail server using CentOS.

 

I have got the server up and running and I have installed OMSA from the Dell
Hardware Repos through YUM.

When I log into the OMSA web interface (https:<my.ip.add.ress>:1311) up
comes the interface and I can Log in.

The problem that I have is that there is no information in there on the
system components like storeage and cputemp etc etc, the web page is just
empty.

 

Am I missing something that needs to be configured  ?.

 

>From the CLI then omreport for instance on temps

 

[root at dell1750 ~]# omreport chassis temps
Error! No temperature probes found on this system.

 

I am sure they are there !!

 

So what am I missing ?

 

Cheers

 

Paul.

 

All E-Mail communications are monitored in addition to being content checked
for malicious codes or viruses. The success of scanning products is not
guaranteed, therefore the recipient(s) should carry out any checks that they
believe to be appropriate in this respect.

This message (including any attachments and/or related materials) is
confidential to and is the property of Computer Service Centre, unless
otherwise noted. If you are not the intended recipient, you should delete
this message and are hereby notified that any disclosure, copying, or
distribution of this message, or the taking of any action based on it, is
strictly prohibited.

Any views or opinions presented are solely those of the author and do not
necessarily represent those of Computer Service Centre.

-- 
This message has been scanned for viruses and 
dangerous content by  <http://www.mailscanner.info/> MailScanner, and is 
believed to be clean. 

All E-Mail communications are monitored in addition to being content checked
for malicious codes or viruses. The success of scanning products is not
guaranteed, therefore the recipient(s) should carry out any checks that they
believe to be appropriate in this respect.




This message (including any attachments and/or related materials) is
confidential to and is the property of Computer Service Centre, unless
otherwise noted. If you are not the intended recipient, you should delete
this message and are hereby notified that any disclosure, copying, or
distribution of this message, or the taking of any action based on it, is
strictly prohibited.




Any views or opinions presented are solely those of the author and do not
necessarily represent those of Computer Service Centre.

-- 
This message has been scanned for viruses and 
dangerous content by  <http://www.mailscanner.info/> MailScanner, and is 
believed to be clean. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.us.dell.com/pipermail/linux-poweredge/attachments/20080301/23ab58df/attachment-0001.htm 


More information about the Linux-PowerEdge mailing list