[hobbit] bb-prtdiag.sh - Sun SPARC Enterprise M9000 Server
Shaun Phillips
tainted.soul69 at googlemail.com
Mon Sep 14 14:10:00 CEST 2009
Mike,
No, the lom variables are set and when run manually it produces what I am
seeing. Exit status is 0 when I run it but I assume it's using awk/egrep
etc.. etc.. to get values?
LOM_COMMAND="/usr/sbin/lom"
LOM_OPT="-pfvt"
We do have SONWlom packages.
system SUNWlomm LOMlite manual pages
system SUNWlomr LOMlite driver (root)
system SUNWlomu LOMlite Utilities (usr)
Output from manual run.
# /usr/sbin/lom -pfvt
PSUs:
1 OK
Fans:
1 OK speed 84%
Supply voltages:
1 5V status=ok
2 3V3 status=ok
3 +12V status=ok
4 -12V status=ok
5 VDD core status=ok
System status flags (circuit breakers):
1 USB0 status=ok
2 USB1 status=ok
3 SCC status=ok
System Temperature Sensors:
1 Enclosure 32 degC : warning 67 degC : shutdown 72 degC
System Over-temperature Sensors:
1 ÿCPU status=ok
Painful, as these are the only servers let to solve?
Regards
Sean.
On Sat, Sep 12, 2009 at 8:22 PM, Mike Arnold <hobbit at razorsedge.org> wrote:
> My wild guess would be that you also need to run "/usr/sbin/lom -pfvt" on
> the v120 to get the temperature and voltage output? Do you have SUNWlom*
> installed on the v120?
>
> --
> -m
>
> ... so long as the people do not care to exercise their freedom, those
> who wish to tyrranize will do so; for tyrants are active and ardent,
> and will devote themselves in the name of any number of gods, religious
> and otherwise, to put shackles upon sleeping men.
> -- Voltarine de Cleyre
>
> Shaun Phillips wrote:
> > Ralph,
> >
> > Yes the bbcmd command was very useful. Ran that with the new bb-prtdiag
> > script from : http://xymonton.trantor.org/doku.php/monitors
> >
> > Now there is a compatability with the bb-prtdiag.sh script and v120
> > servers.
> >
> > if you run the script on one as follows.
> >
> > # /usr/platform/sun4u/sbin/prtdiag -v
> > System Configuration: Sun Microsystems sun4u Sun Fire V120
> > (UltraSPARC-IIe
> > 648MHz)
> > System clock frequency: 100 MHz
> > Memory size: 1024 Megabytes
> > ========================= CPUs =========================
> > Run Ecache CPU CPU
> > Brd CPU Module MHz MB Impl. Mask
> > --- --- ------- ----- ------ ------ ----
> > 0 0 0 648 0.5 13 3.3
> >
> > ========================= IO Cards =========================
> > Bus# Freq
> > Brd Type MHz Slot Name Model
> > --- ---- ---- ---- --------------------------------
> > ----------------------
> > 0 PCI-1 33 12 ebus
> > 0 PCI-1 33 3 pmu-pci10b9,7101
> > 0 PCI-1 33 3 lomp
> > 0 PCI-1 33 7 isa
> > 0 PCI-1 33 12 network-pci108e,1101 SUNW,pci-eri
> > 0 PCI-1 33 12 usb-pci108e,1103.1
> > 0 PCI-1 33 13 ide-pci10b9,5229
> > 0 PCI-1 33 5 network-pci108e,1101 SUNW,pci-eri
> > 0 PCI-1 33 5 usb-pci108e,1103.1
> > 0 PCI-2 33 8 scsi-glm Symbios,53C896
> > 0 PCI-2 33 8 scsi-glm Symbios,53C896
> >
> > No failures found in System
> > ===========================
> > ========================= HW Revisions =========================
> > ASIC Revisions:
> > ---------------
> > Cheerio: ebus Rev 1
> > System PROM revisions:
> > ----------------------
> > CORE 1.0.12 2002/01/08 13:00
> > dtcp-sbr001a:root#
> >
> > You get the above output. Which is not showing enough I would think.
> The
> > hobbit page shows the output as follows.
> >
> >
> > Fri Sep 11 13:34:40 GMT 2009 [image: red]prtdiag reports voltage
> problems
> > !!!
> >
> > prtdiag reports voltage problems !!!
> > 1 5V status=ok
> > 2 3V3 status=ok
> > 3 +12V status=ok
> > 4 -12V status=ok
> > 5 CPU core status=ok
> > 6 +3VSB status=ok PSUs:
> > 1 OK
> > Fans:
> > 1 OK speed 98%
> > 2 OK speed 100%
> > 3 OK speed 100%
> > 4 OK speed 100%
> > Supply voltages:
> > 1 5V status=ok
> > 2 3V3 status=ok
> > 3 +12V status=ok
> > 4 -12V status=ok
> > 5 CPU core status=ok
> > 6 +3VSB status=ok
> > System status flags (circuit breakers):
> > 1 SCSI-Term status=ok
> > 2 USB0 status=ok
> > 3 USB1 status=ok
> > 4 SCC status=ok
> > System Temperature Sensors:
> > 1 Enclosure 29 degC : warning 67 degC : shutdown 72 degC
> > System Over-temperature Sensors:
> > 1 ÿCPU status=ok
> >
> >
> > As you can see that's not the normal out that one would expect? Any
> > ideas?
> > Currently so far the new bb-prtdiag.sh has cleard up the majority of
> > errors
> > I was facing with some servers.
> >
> >
> > Regards
> > Shaun
> >
> >
> > On Wed, Sep 9, 2009 at 8:01 PM, Ralph Mitchell
> > <ralphmitchell at gmail.com>wrote:
> >
> >> Try using bbcmd to execute bb-prtdiag.sh
> >> server/bin/bbcmd /path/to/bb-prtdiag.sh
> >>
> >> bbcmd sets up the environment properly for the script. You need more
> >> than
> >> just BBHOME.
> >>
> >> Ralph Mitchell
> >>
> >>
> >> On Wed, Sep 9, 2009 at 1:52 PM, Shaun Phillips <
> >> tainted.soul69 at googlemail.com> wrote:
> >>
> >>> ok,
> >>>
> >>> So I edited the script and add -vvv to the interpreter line.
> >>>
> >>> And now see egrep and bb errors.
> >>>
> >>>
> >>> if [ -s "$REDLINE" ]; then
> >>> COLOR="red"
> >>> fi
> >>> # NOW USE THE BB COMMAND TO SEND THE DATA ACROSS
> >>> $BB $BBDISP "status $MACHINE.$TEST $COLOR `$DATE` `$CAT $REDLINE`
> >>> `$CAT
> >>> $YELLOWLINE` `$CAT $BBTMP/$MACHINE.$TEST` "
> >>> fi
> >>> *egrep: syntax error
> >>> ./bb-prtdiag.sh: /bin/bb: not found*
> >>> if [ "$DEBUG" != "Y" ]; then
> >>> clean_up_our_mess
> >>> fi
> >>>
> >>> I have logged in, su'd to hobbit on the clinet, set my BBHOME variable
> >>> and
> >>> then proceed to ( ./bb-prtdiag.sh ) run the script.
> >>>
> >>> Any thoughts?
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> On Tue, Sep 1, 2009 at 3:14 AM, Everett, Vernon <
> >>> Vernon.Everett at woodside.com.au> wrote:
> >>>
> >>>> You are right.
> >>>> I was thinking of sunhw.sh on deadcat.
> >>>> Apologies for muddying the water.
> >>>> Should have my coffee *before* I post to the list. :-)
> >>>>
> >>>> Cheers
> >>>> V
> >>>>
> >>>>
> >>>> -----Original Message-----
> >>>> From: Craig Cook [mailto:Craig.Cook at carquest.com]
> >>>> Sent: Monday, 31 August 2009 9:14 PM
> >>>> To: hobbit at hswn.dk
> >>>> Subject: RE: [hobbit] bb-prtdiag.sh - Sun SPARC Enterprise M9000
> >>>> Server
> >>>>
> >>>> >I am having truble with the bb-prtdiag script on "Sun SPARC
> >>>> Enterprise
> >>>> M9000 Server " and also "SUNW,UltraAX-i2" hardware. Always saying
> >>>> something is wrong when I cant see anything wrong?
> >>>>
> >>>> The M9000 has not explicitly been added for support.
> >>>>
> >>>> Check the readme with the bb-prtdiag tar file for how to run the built
> >>>> in
> >>>> debug.
> >>>> There is also information in the comment section at the top of the
> >>>> script.
> >>>>
> >>>> Support for UltraAX-i2 has been added, run debug to find out why/where
> >>>> it
> >>>> is complaining.
> >>>>
> >>>> >bb-prtdiag is a very simple test. It looks at the return code of the
> >>>> prtdiag command.
> >>>> No. bb-prtdiag does not look at the return code from running prtdiag.
> >>>> If you want a simple prtdiag check there is another one on deadcat.
> >>>>
> >>>> Craig
> >>>>
> >>>> To unsubscribe from the hobbit list, send an e-mail to
> >>>> hobbit-unsubscribe at hswn.dk
> >>>>
> >>>>
> >>>>
> >>>> NOTICE: This email and any attachments are confidential.
> >>>> They may contain legally privileged information or
> >>>> copyright material. You must not read, copy, use or
> >>>> disclose them without authorisation. If you are not an
> >>>> intended recipient, please contact us at once by return
> >>>> email and then delete both messages and all attachments.
> >>>>
> >>>>
> >>>> To unsubscribe from the hobbit list, send an e-mail to
> >>>> hobbit-unsubscribe at hswn.dk
> >>>>
> >>>>
> >>>>
> >>>
> >>
> >
>
>
> To unsubscribe from the hobbit list, send an e-mail to
> hobbit-unsubscribe at hswn.dk
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20090914/f6fe79ac/attachment.html>
More information about the Xymon
mailing list