Hi, There is no change in OMSA default port. The default port is 1311.
Please run the following command and see the result. Which OS you are using? srvadmin-services.sh status Chandrasekhar R Dell | OpenManage office +91 80 41178649 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Thursday, August 05, 2010 5:48 PM To: linux-poweredge-Lists Subject: Linux-PowerEdge Digest, Vol 74, Issue 12 Send Linux-PowerEdge mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit https://lists.us.dell.com/mailman/listinfo/linux-poweredge or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of Linux-PowerEdge digest..." Today's Topics: 1. Re: IPMI (Alexander Dupuy) 2. Re: IPMI (James Bensley) 3. Re: IPMI (Jason Edgecombe) 4. PowerEdge 2800: megaraid/scsi errors (PERC 4e/di) (Marc Petitmermet) 5. Re: PowerEdge 2800: megaraid/scsi errors (PERC 4e/di) (Tim Small) 6. Re: PowerEdge 2800: megaraid/scsi errors (PERC 4e/di) (Stroller) 7. OMSA 6.3 from dell repo - no controller found (Rainer Traut) 8. OMSA6.3 webserver port (Nick Lunt) ---------------------------------------------------------------------- Message: 1 Date: Wed, 04 Aug 2010 15:33:48 -0400 From: Alexander Dupuy <[email protected]> Subject: Re: IPMI To: [email protected] Message-ID: <[email protected]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Rahul Nabar wrote: > I monitor temperatures via lm_sensors. Again in-band. I try to keep my > monitoring in-band unless there is a compelling reason to use ipmi. > Maybe some sensors are not available to lm_sensors. My experience with Dell server systems that have BMC or iDRAC cards standard (9th/10th/11th gen, at least) is that lm_sensors doesn't have any usable sensors to monitor, as Dell have wired them all up to the BMC instead (AMD CPU temperature sensors builtin to the CPU itself perhaps being one exception - but all my Dell servers are Intel). You can still do in-band management, but you end up running the monitoring via local IPMI anyhow, e.g. # ipmitool sdr type Temperature Temp | 01h | ok | 3.1 | -53 degrees C Temp | 02h | ok | 3.2 | -52 degrees C Temp | 05h | ok | 10.1 | 16 degrees C Ambient Temp | 07h | ok | 10.1 | 87 degrees C Temp | 06h | ok | 10.2 | 42 degrees C Ambient Temp | 08h | ok | 10.2 | 19 degrees C Ambient Temp | 0Eh | ok | 7.1 | 23 degrees C Planar Temp | 0Fh | ok | 7.1 | 40 degrees C IOH THERMTRIP | 5Dh | ns | 7.1 | Disabled CPU Temp Interf | 76h | ns | 7.1 | Disabled Temp | 0Ah | ok | 8.1 | 26 degrees C Temp | 0Bh | ok | 8.1 | 28 degrees C Temp | 0Ch | unc | 8.1 | 42 degrees C (those wacky -53 degree readings are relative to CPU melting point or something - not sure what the 87 degree ambient temperature is about - but basically I just look for ok/unc/ucr for nominal/warning/error state and ignore the specific temps anyhow). @alex -- mailto:[email protected] ------------------------------ Message: 2 Date: Wed, 4 Aug 2010 21:54:07 +0100 From: James Bensley <[email protected]> Subject: Re: IPMI To: [email protected] Message-ID: <[email protected]> Content-Type: text/plain; charset=ISO-8859-1 On 4 August 2010 20:33, Alexander Dupuy <[email protected]> wrote: > (those wacky -53 degree readings are relative to CPU melting point or > something Might be something like distance to TJmax or one of those? -- Regards, James. http://www.jamesbensley.co.cc/ There are 10 kinds of people in the world; Those who understand Vigesimal, and J others...? ------------------------------ Message: 3 Date: Wed, 04 Aug 2010 18:19:49 -0400 From: Jason Edgecombe <[email protected]> Subject: Re: IPMI To: [email protected] Message-ID: <[email protected]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed On 08/04/2010 02:12 PM, Eric Rostetter wrote: > > There are a number of great monitoring systems which are at their core > using nagios to monitor things. I would suggest one of these over just > a plain nagios install, since they layer a lot of stuff on top of nagios. > > Having said that, I do use nagios to monitor my Dell machines, but not > via IPMI (rather openmanage, etc). > > Would you please list a couple of these nagios-based systems? Preferably open-source. Thanks, Jason ------------------------------ Message: 4 Date: Thu, 5 Aug 2010 09:00:05 +0200 From: Marc Petitmermet <[email protected]> Subject: PowerEdge 2800: megaraid/scsi errors (PERC 4e/di) To: <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset="us-ascii" Dear all We have two identical PowerEdge 2800 (I know, 5 years old). Because it took the Dell Support people/ contractors so very long to set up everything (fibre channels switch, EMC CX300, custom drivers, etc.) to get it finally working, the system is more or less unchanged since the beginning. One of those PowerEdge 2800 is now acting up. I see messages like: megaraid: aborting-12854 cmd=2a <c=2 t=0 I=0> megaraid abort: [255:128], driver owner megaraid: resetting the host... megaraid: 2 outstanding commands. Max wait 180 sec etc. scsi0 (0:0): rejecting I/O to offline device etc. When I look at the RAID controller everything seems to be fine: - Logical Drive, RAID 1, Size 34680MB, Stripes 2, StrSz 64KB, Drive-State: optimal Battery: - Battery Backup Module: present - Battery Pack: present - Temperature: good - Voltage: good - fast charging: in progress - No of Cycles: 50 What do the above errors mean? Are the disks failing or is this an other hardware issue? I booted from a Redhat CD in linux rescue mode and I could fsck all partitions without any problems at all. Any advise would be greatly appreciated. Regards, Marc Some more details about the hardware/software: - Redhat Enterprise Linux 4.5 (2.6.9-22.0.2.ELsmp #1 SMP Thu Jan 5 17:11:56 EST 2006 x86_64 x86_64 x86_64 GNU/Linux) - PERC 4e/di standard FW 521S DRAM=256MB (SDRAM) - RAID 1; 2 x Seagate Cheetah 15K.4, Firmware D402 ------------------------------ Message: 5 Date: Thu, 05 Aug 2010 09:27:09 +0100 From: Tim Small <[email protected]> Subject: Re: PowerEdge 2800: megaraid/scsi errors (PERC 4e/di) To: Marc Petitmermet <[email protected]>, "[email protected]" <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed On 05/08/10 08:00, Marc Petitmermet wrote: > megaraid: aborting-12854 cmd=2a<c=2 t=0 I=0> > megaraid abort: [255:128], driver owner > megaraid: resetting the host... > > What do the above errors mean? Are the disks failing or is this an other hardware issue? > > Any advise would be greatly appreciated. > I'd want to take a closer look at the general health of the drives themselves (grown defect list, ECC correction count, uncorrectable error count and the like) using a tool like smartctl - recent smartmontools releases have support for looking at drives behind perc 4s - search for megaraid in: http://smartmontools.sourceforge.net/man/smartctl.8.html alternatively if getting smartctl onto this box is fiddly (and you can easily take the drives offline) it might be easier to plug the drives into a plain SCSI controller on a more modern box... HTH, Tim. -- South East Open Source Solutions Limited Registered in England and Wales with company number 06134732. Registered Office: 2 Powell Gardens, Redhill, Surrey, RH1 1TQ VAT number: 900 6633 53 http://seoss.co.uk/ +44-(0)1273-808309 ------------------------------ Message: 6 Date: Thu, 5 Aug 2010 12:51:23 +0100 From: Stroller <[email protected]> Subject: Re: PowerEdge 2800: megaraid/scsi errors (PERC 4e/di) To: linux-poweredge List <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes On 5 Aug 2010, at 08:00, Marc Petitmermet wrote: > ... > megaraid: aborting-12854 cmd=2a <c=2 t=0 I=0> > megaraid abort: [255:128], driver owner > megaraid: resetting the host... > megaraid: 2 outstanding commands. Max wait 180 sec > etc. > scsi0 (0:0): rejecting I/O to offline device > etc. > ... > > What do the above errors mean? Are the disks failing or is this an > other hardware issue? I would expect that at least one of the disks is failing. That would be the first thing I would look at. Stroller ------------------------------ Message: 7 Date: Thu, 05 Aug 2010 14:14:06 +0200 From: Rainer Traut <[email protected]> Subject: OMSA 6.3 from dell repo - no controller found To: [email protected] Message-ID: <[email protected]> Content-Type: text/plain; charset=UTF-8; format=flowed Hi all, it seems OMSA 6.3 has landed in the dell linux repo; My 2 findings so far: - OMSA 6.3 does not see the controller # omreport storage controller No controllers found - OMSA 6.2 was running while updating - after yum completed some services were not... # srvadmin-services.sh status Remote Access Controller (RAC4) is stopped [ OK ] dell_rbu (module) is running ipmi driver is running dsm_sa_datamgrd is stopped dsm_sa_eventmgrd is stopped dsm_sa_snmpd is stopped dsm_om_shrsvcd (pid 3402) is running dsm_om_connsvcd (pid 3445 3444) is running A srvadmin-services.sh restart fixed it. How can I fix the controller issue? Systems Specs: RHEL 5.5 x86_64 fully updated, PE2950 with Dell PERC 6/i Thx Rainer ------------------------------ Message: 8 Date: Thu, 5 Aug 2010 13:10:35 +0100 From: "Nick Lunt" <[email protected]> Subject: OMSA6.3 webserver port To: <[email protected]> Message-ID: <47073a5e92271a409f44d18958c1aaa6fb3...@server13.patechsolutions.local> Content-Type: text/plain; charset="us-ascii" Hi OMSA 6.3 install on R710. All services are running and omconfig system webserver action=start run for webserver. However I cannot connect to localhost:1311 . # omconfig system webserver action=start Error! DSM SA Connection Service is already started. # lsof -i tcp:1311 returns nothing. Has the default port changes in OMSA 6.3 ? Kind Regards Nick Lunt Managed Services and O/S Analyst Patech Solutions Limited Tel: 01543 444 710 Mob: 0755 400 3634 Fax: 01543 444 709 Tame House, Fradley Park, Lichfield, Staffordshire, WS13 8RZ www.patech-solutions.com <http://www.patech-solutions.com/home.htm> Please consider the environment before printing this e-mail. Thank you __________ Information from ESET NOD32 Antivirus, version of virus signature database 5342 (20100805) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.us.dell.com/pipermail/linux-poweredge/attachments/20100805/ 7d272db2/attachment.htm ------------------------------ _______________________________________________ Linux-PowerEdge mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq End of Linux-PowerEdge Digest, Vol 74, Issue 12 *********************************************** _______________________________________________ Linux-PowerEdge mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
