bb-prtdiag.sh - Sun SPARC Enterprise M9000 Server 🔗 link

From: Shaun Phillips [mailto:user-176e7038266c@xymon.invalid]
Sent: Saturday, 29 August 2009 12:15 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: [hobbit] bb-prtdiag.sh - Sun SPARC Enterprise M9000 Server

Hi everyone,

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?

Below is the output from it and I cant see anything wrong?

Any thoughts?


======================================================

Prtdiag Info

(/usr/platform/SUNW,SPARC-Enterprise/sbin/prtdiag -v) Memory Available Memory DIMM Number of System Configuration: Sun Microsystems sun4u Sun SPARC Enterprise M9000 Server System clock frequency: 960 MHz Memory size: 131072 Megabytes ==================================== CPUs ==================================== CPU CPU Run L2$ CPU CPU LSB Chip ID MHz MB Impl. Mask --- ---- -------------------- ---- --- ----- ---- 00 0 0, 1, 2, 3 2280 5.0 6 146 00 1 8, 9, 10, 11 2280 5.0 6 146 00 2 16, 17, 18, 19 2280 5.0 6 146 00 3 24, 25, 26, 27 2280 5.0 6 146 01 0 32, 33, 34, 35 2280 5.0 6 146 01 1 40, 41, 42, 43 2280 5.0 6 146 01 2 48, 49, 50, 51 2280 5.0 6 146 01 3 56, 57, 58, 59 2280 5.0 6 146 02 0 64, 65, 66, 67 2280 5.0 6 146 02 1 72, 73, 74, 75 2280 5.0 6 146 02 2 80, 81, 82, 83 2280 5.0 6 146 02 3 88, 89, 90, 91 2280 5.0 6 146 03 0 96, 97, 98, 99 2280 5.0 6 146 03 1 104, 105, 106, 107 2280 5.0 6 146 03 2 112, 113, 114, 115 2280 5.0 6 146 03 3 120, 121, 122, 123 2280 5.0 6 146 04 0 128, 129, 130, 131 2280 5.0 6 146 04 1 136, 137, 138, 139 2280 5.0 6 146 04 2 144, 145, 146, 147 2280 5.0 6 146 04 3 152, 153, 154, 155 2280 5.0 6 146 05 0 160, 161, 162, 163 2280 5.0 6 146 05 1 168, 169, 170, 171 2280 5.0 6 146 05 2 176, 177, 178, 179 2280 5.0 6 146 05 3 184, 185, 186, 187 2280 5.0 6 146 ====================== Memory Configuration ====================== Memory Available Memory DIMM Number of LSB Group Size Status Size DIMMs --- ------ ------------------ ------- ------ --------- 00 A 16384MB okay 1024MB 16 00 B 16384MB okay 1024MB 16 01 A 16384MB okay 1024MB 16 01 B 16384MB okay 1024MB 16 02 A 16384MB okay 1024MB 16 03 A 16384MB okay 1024MB 16 04 A 16384MB okay 1024MB 16 05 A 16384MB okay 1024MB 16 ========================= IO Devices ========================= IO Lane/Frq LSB Type LPID RvID,DvID,VnID BDF State Act, Max Name Model --- ----- ---- ------------------ --------- ----- ----------- ------------------------------ -------------------- Logical Path ------------ 00 PCIx 0 8, 125, 1033 2, 0, 0 okay 133, 133 pci-pciexclass,060400 N/A /pci at 0,600000/pci at 0 00 PCIx 0 8, 125, 1033 2, 0, 1 okay 133, 133 pci-pciexclass,060400 N/A /pci at 0,600000/pci at 0,1 00 PCI 0 2, 50, 1000 3, 1, 0 okay --, 133 scsi-pci1000,50 LSI,1064 /pci at 0,600000/pci at 0/scsi at 1 00 PCI 0 10, 1648, 14e4 4, 1, 0 okay --, 133 network-pci14e4,1648 N/A /pci at 0,600000/pci at 0,1/network at 1 00 PCI 0 10, 1648, 14e4 4, 1, 1 okay --, 133 network-pci14e4,1648 N/A /pci at 0,600000/pci at 0,1/network 00 PCIe 2 2, fe00, 10df 2, 0, 0 okay 4, 4 fibre-channel-pciex10df,fe00 LPe11002-E /pci at 2,600000/fibre-channel at 0 00 PCIe 2 2, fe00, 10df 2, 0, 1 okay 4, 4 fibre-channel-pciex10df,fe00 LPe11002-E /pci at 2,600000/fibre-channel at 0,1 00 PCIe 3 2, fe00, 10df 2, 0, 0 okay 4, 4 fibre-channel-pciex10df,fe00 LPe11002-E /pci at 3,700000/fibre-channel at 0 00 PCIe 3 2, fe00, 10df 2, 0, 1 okay 4, 4 fibre-channel-pciex10df,fe00 LPe11002-E /pci at 3,700000/fibre-channel at 0,1 00 PCIe 4 1, abcd, 108e 2, 0, 0 okay 8, 8 network-pciex108e,abcd SUNW,pcie-qgc /pci at 4,600000/network 00 PCIe 4 1, abcd, 108e 2, 0, 1 okay 8, 8 network-pciex108e,abcd SUNW,pcie-qgc /pci at 4,600000/network 00 PCIe 4 1, abcd, 108e 2, 0, 2 okay 8, 8 network-pciex108e,abcd SUNW,pcie-qgc /pci at 4,600000/network 00 PCIe 4 1, abcd, 108e 2, 0, 3 okay 8, 8 network-pciex108e,abcd SUNW,pcie-qgc /pci at 4,600000/network 01 PCIx 16 8, 125, 1033 2, 0, 0 okay 133, 133 pci-pciexclass,060400 N/A /pci at 10,600000/pci at 0 01 PCIx 16 8, 125, 1033 2, 0, 1 okay 133, 133 pci-pciexclass,060400 N/A /pci at 10,600000/pci at 0,1 01 PCI 16 2, 50, 1000 3, 1, 0 okay --, 133 scsi-pci1000,50 LSI,1064 /pci at 10,600000/pci at 0/scsi at 1 01 PCI 16 10, 1648, 14e4 4, 1, 0 okay --, 133 network-pci14e4,1648 N/A /pci at 10,600000/pci at 0,1/network at 1 01 PCI 16 10, 1648, 14e4 4, 1, 1 okay --, 133 network-pci14e4,1648 N/A /pci at 10,600000/pci at 0,1/network 01 PCIx 17 9, 340, 8086 2, 0, 0 okay 133, 133 pci-pciexclass,060400 N/A /pci at 11,700000/pci at 0 01 PCIx 17 9, 341, 8086 2, 0, 2 okay --, 133 pci-pciexclass,060400 N/A /pci at 11,700000/pci at 0,2 01 PCI 17 1, fa00, 10df 3, 4, 0 okay --, 133 fibre-channel-pci10df,fa00 N/A /pci at 11,700000/pci at 0/fibre-channel at 4 01 PCI 17 1, fa00, 10df 3, 4, 1 okay --, 133 fibre-channel-pci10df,fa00 N/A /pci at 11,700000/pci at 0/fibre-channel at 4,1 01 PCIe 18 2, fe00, 10df 2, 0, 0 okay 4, 4 fibre-channel-pciex10df,fe00 LPe11002-E /pci at 12,600000/fibre-channel at 0 01 PCIe 18 2, fe00, 10df 2, 0, 1 okay 4, 4 fibre-channel-pciex10df,fe00 LPe11002-E /pci at 12,600000/fibre-channel at 0,1 01 PCIe 20 1, abcd, 108e 2, 0, 0 okay 8, 8 network-pciex108e,abcd SUNW,pcie-qgc /pci at 14,600000/network at 0 01 PCIe 20 1, abcd, 108e 2, 0, 1 okay 8, 8 network-pciex108e,abcd SUNW,pcie-qgc /pci at 14,600000/network 01 PCIe 20 1, abcd, 108e 2, 0, 2 okay 8, 8 network-pciex108e,abcd SUNW,pcie-qgc /pci at 14,600000/network 01 PCIe 20 1, abcd, 108e 2, 0, 3 okay 8, 8 network-pciex108e,abcd SUNW,pcie-qgc /pci at 14,600000/network 01 PCIe 22 6, 105f, 8086 2, 0, 0 okay 4, 4 network-pciex8086,105f SUNW,pcie-northstar /pci at 16,600000/network 01 PCIe 22 6, 105f, 8086 2, 0, 1 okay 4, 4 network-pciex8086,105f SUNW,pcie-northstar /pci at 16,600000/network ==================== Hardware Revisions ==================== System PROM revisions: ---------------------- OBP 4.24.4 2007/10/12 12:19 =================== Environmental Status =================== Mode switch is in UNLOCK mode

-------Original Message-------
 
From: Craig Cook
Date: 8/31/2009 11:05:27 AM
To: user-ae9b8668bcde@xymon.invalid
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

 
-----Original Message-----
From: Craig Cook [mailto:user-850f03189cf7@xymon.invalid] Sent: Monday, 31 August 2009 9:14 PM
To: user-ae9b8668bcde@xymon.invalid
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


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.

user-9da1a1882f49@xymon.invalid> 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:user-850f03189cf7@xymon.invalid]
Sent: Monday, 31 August 2009 9:14 PM
To: user-ae9b8668bcde@xymon.invalid
 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


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.

user-176e7038266c@xymon.invalid> 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 <
user-9da1a1882f49@xymon.invalid> 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:user-850f03189cf7@xymon.invalid]
Sent: Monday, 31 August 2009 9:14 PM
To: user-ae9b8668bcde@xymon.invalid
  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


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.

On Wed, Sep 9, 2009 at 8:01 PM, Ralph Mitchell <user-00a5e44c48c0@xymon.invalid>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 <
user-176e7038266c@xymon.invalid> 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 <
user-9da1a1882f49@xymon.invalid> 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:user-850f03189cf7@xymon.invalid]
Sent: Monday, 31 August 2009 9:14 PM
To: user-ae9b8668bcde@xymon.invalid
 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


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.

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
<user-00a5e44c48c0@xymon.invalid>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 <
user-176e7038266c@xymon.invalid> 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 <
user-9da1a1882f49@xymon.invalid> 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:user-850f03189cf7@xymon.invalid]
Sent: Monday, 31 August 2009 9:14 PM
To: user-ae9b8668bcde@xymon.invalid
 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


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.

Supply voltages:
 1               5V status=ok
 2              3V3 status=ok
 3             +12V status=ok
 4             -12V status=ok

On Sat, Sep 12, 2009 at 8:22 PM, Mike Arnold <user-95d566fbb20b@xymon.invalid> 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:

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
<user-00a5e44c48c0@xymon.invalid>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 <
user-176e7038266c@xymon.invalid> 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 <
user-9da1a1882f49@xymon.invalid> 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:user-850f03189cf7@xymon.invalid]
Sent: Monday, 31 August 2009 9:14 PM
To: user-ae9b8668bcde@xymon.invalid
 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


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.

On Mon, Sep 14, 2009 at 4:33 PM, Craig Cook <user-850f03189cf7@xymon.invalid> wrote:

 Did you review the instructions in the top of the script?  Including the
tip you may need to run nawk?


I thought these were in the readme.txt but it is missing.  They have been
in the script since version 4.11.

I thought hobbitmon/xymon debug instructions were also included.  I’ll add
them in the next release.


# INSTALLATION - Hobbitmon

#

# Step 1 - Copy this script to $HOBBITCLIENT/ext/bb-prtdiag.sh

#          Ensure your hobbit user owns the script and is executable
(chown)

#

# Step 2 - Add the lines mentioned in the bbsys.local section to

#             $HOBBITCLIENT/etc/hobbitclient.cfg

#           Note: You may have to hard code the

#                 PLATFORM_SPEC & PRTDIAG_COMMAND variables, or

#                 do not enter it in hobbitclient.cfg

#                 You may also need to use /usr/xpg4/bin/awk or
/usr/bin/nawk

#

# Step 3 - Add this:

#

#          [prtdiag]

#                  ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg

#                  CMD $HOBBITCLIENTHOME/ext/bb-prtdiag.sh

#                  LOGFILE $HOBBITCLIENTHOME/logs/bb-prtdiag.log

#                  INTERVAL 5

#

#          to $HOBBITCLIENT/etc/clientlaunch.cfg

#

# You do not need to restart hobbit to activate


Craig

I have seen the link referencing the awk or nawk but not sure how it's using
either?

AIs the only reference in the file to awk is the following?

cat bb-prtdiag.sh  | grep awk
#                 You may also need to use /usr/xpg4/bin/awk or
/usr/bin/nawk

Am I being stupid here?

# Step 2 - Add the lines mentioned in the bbsys.local section to
#             $HOBBITCLIENT/etc/hobbitclient.cfg
#           Note: You may have to hard code the
#                 PLATFORM_SPEC & PRTDIAG_COMMAND variables, or
#                 do not enter it in hobbitclient.cfg
#
#                 You may also need to use /usr/xpg4/bin/awk or /usr/bin/nawk

# Step 3 - Add this:
#
#          [prtdiag]
#                  ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg
#                  CMD $HOBBITCLIENTHOME/ext/bb-prtdiag.sh
#                  LOGFILE $HOBBITCLIENTHOME/logs/bb-prtdiag.log
#                  INTERVAL 5

On Tue, Sep 15, 2009 at 3:01 PM, Craig Cook <user-850f03189cf7@xymon.invalid> wrote:

 Oh, you will want to correct this as well.


# Step 3 - Add this:

#

#          [prtdiag]

#                  ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg

#                  CMD $HOBBITCLIENTHOME/ext/bb-prtdiag.sh

#                  LOGFILE $HOBBITCLIENTHOME/logs/bb-prtdiag.log

#                  INTERVAL 5


Should be:

#                  INTERVAL 5m


The previous “  INTERVAL 5 “ actually means run the script every 5 seconds,
not 5 minutes like I wanted.


Craig

user-176e7038266c@xymon.invalid> wrote:

Craig,

I've set them to 5m already.

 [prtdiag]
        ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg
        CMD $HOBBITCLIENTHOME/ext/bb-prtdiag.sh
        LOGFILE $HOBBITCLIENTHOME/logs/hobbitclient.log
        INTERVAL 5m

Thanks for the AWK/NAWK update I'll update the script myside.

Regards
Shaun

  On Tue, Sep 15, 2009 at 3:01 PM, Craig Cook <user-850f03189cf7@xymon.invalid>wrote:

 Oh, you will want to correct this as well.


# Step 3 - Add this:

#

#          [prtdiag]

#                  ENVFILE $HOBBITCLIENTHOME/etc/hobbitclient.cfg

#                  CMD $HOBBITCLIENTHOME/ext/bb-prtdiag.sh

#                  LOGFILE $HOBBITCLIENTHOME/logs/bb-prtdiag.log

#                  INTERVAL 5


Should be:

#                  INTERVAL 5m


The previous “  INTERVAL 5 “ actually means run the script every 5
seconds, not 5 minutes like I wanted.


Craig