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