{bb} More issues with bb-prtdiag.sh 4.5

["Richard.Hall" <Richard.Hall@ingenta.com>]

Craig,

Obviously today is a good day for raising problems with bb-prtdiag.sh. So
here are mine ...

1) Discovered when first testing bb-prtdiag.sh, prior to making the
appropriate changes to bbsys.local (so I was expecting the 'yellow's due
to unset variables) ...

The call to check_defaults_set occurs too late - it needs to be before
MACHINETYPE is set, as PLATFORM_SPEC needs to be defined by then.

2) I was trying to add an E3000 to the recognised systems. The changes
required appear to be minimal, as the prtdiag output is essentially
identical to that of an E3500. (Unfortunately I don't currently have a
'clean' prtdiag from the E3000 to add to your collection - I can send it
later if you so desire (ie once the machine is fixed!!))

3) I have problems with the 'Activity' light on an E450. bb-prtdiag.sh
expects it to be always ON. But (a) Sun officially describe it as
'blinking', and (b) prtdiag appears to report it as alternately 'ON' and
'OFF' (as opposed to eg an E3500, where it is indeed reported as
BLINKING).

Thus for example:-

$ /usr/platform/`uname -i`/sbin/prtdiag -v | head -1
System Configuration:  Sun Microsystems  sun4u Sun Enterprise 450 (4 X
UltraSPARC-II 400MHz)
$ while :; do /usr/platform/`uname -i`/sbin/prtdiag -v | \
> awk '/System LED Status./, /^$/ {print $0}' | head -2 ; sleep 1 ; done
System LED Status:    POWER     GENERAL ERROR      ACTIVITY
                      [ ON]         [OFF]           [ ON]
System LED Status:    POWER     GENERAL ERROR      ACTIVITY
                      [ ON]         [OFF]           [OFF]
System LED Status:    POWER     GENERAL ERROR      ACTIVITY
                      [ ON]         [OFF]           [ ON]
System LED Status:    POWER     GENERAL ERROR      ACTIVITY
                      [ ON]         [OFF]           [OFF]
System LED Status:    POWER     GENERAL ERROR      ACTIVITY
                      [ ON]         [OFF]           [ ON]
System LED Status:    POWER     GENERAL ERROR      ACTIVITY
                      [ ON]         [OFF]           [ ON]
System LED Status:    POWER     GENERAL ERROR      ACTIVITY
                      [ ON]         [OFF]           [OFF]

That's on Solaris 9; I get the same on 2.6 and 8. No, that's not totally
true - I do have one Solaris 8 system which always shows ON! I have no
idea why - maybe the light is actually permanently on - I'll need to take
a look some time ?!?

Anyway, the upshot is that I have had to comment out that particular test
for the E450.

4) I have _major_ problems with using bb-prtdiag.sh for E250's (on Solaris
2.6). My prtdiag has
  - no Memory section
  - no Environment Status section
    (ie no temps, LED status, fan status, power supply status)
so most of the E250-specific code just ROTFL !!!!

And yet
  - my OBP level is higher than in one of your examples
  - my prtdiag patch level is pretty good (though not perfect)

Can anyone suggest where the problem lies?



I have included a diff of all my changes below - feel free to use or
ignore them as you see fit.


*** bb-prtdiag.sh.orig  Thu Feb 24 18:57:27 2005
--- bb-prtdiag.sh       Thu Mar  3 17:57:41 2005
***************
*** 303,308 ****
--- 303,310 ----
    #####
    COLOR="green"

+   check_defaults_set
+
    #Get machine type
    MACHINETYPE=`echo $PLATFORM_SPEC | $SED 's/.*,//'`

***************
*** 309,316 ****
    #check to see if hardware supports temperature checks
    EXCLUDE=`echo $EXCLUDE_SYSTEMS | $EGREP "$MACHINETYPE"`

-   check_defaults_set
-
    #####
    #####  Diagnostic Information and more CPU/Memory Info.
    #####    looking for faults or failures here.
--- 311,316 ----
***************
*** 460,468 ****
            fi

            E_CLASS=`echo $PRT_FIRST_LINE |
!                    $EGREP "3500|4500" `
            if [ -n "$E_CLASS" ]; then
!             get_Ex500_data
            fi


--- 460,468 ----
            fi

            E_CLASS=`echo $PRT_FIRST_LINE |
!                    $EGREP "3000|3500|4500" `
            if [ -n "$E_CLASS" ]; then
!             get_Exx00_data
            fi


***************
*** 562,568 ****
  } #end check_defaults_set


! get_Ex500_data ()
  {

    BAD_LIGHTS=`$AWK '/.Environmental Status./, /^$/ {print $0}' $PRTFILE |
--- 562,568 ----
  } #end check_defaults_set


! get_Exx00_data ()
  {

    BAD_LIGHTS=`$AWK '/.Environmental Status./, /^$/ {print $0}' $PRTFILE |
***************
*** 577,583 ****
        echo "$BAD_LIGHTS"
    fi

! } #end Ex500_checks


  get_E450_data ()
--- 577,583 ----
        echo "$BAD_LIGHTS"
    fi

! } #end get_Exx00_data


  get_E450_data ()
***************
*** 605,612 ****
                              $CUT -c 24-26 `
    GEN_ERROR_LIGHT_STATUS=`$CAT $LEDFILE_FIRSTROW |
                            $CUT -c 38-40 `
!   ACT_ERROR_LIGHT_STATUS=`$CAT $LEDFILE_FIRSTROW |
!                           $CUT -c 54-56 `

    DISK_ERROR_LIGHT_STATUS=`$CAT $LEDFILE_LASTROW |
                             $CUT -c 24-26 `
--- 605,613 ----
                              $CUT -c 24-26 `
    GEN_ERROR_LIGHT_STATUS=`$CAT $LEDFILE_FIRSTROW |
                            $CUT -c 38-40 `
!   # The ACTIVITY LED actually blinks, so alternates ON/OFF !!
!   #ACT_ERROR_LIGHT_STATUS=`$CAT $LEDFILE_FIRSTROW |
!   #                        $CUT -c 54-56 `

    DISK_ERROR_LIGHT_STATUS=`$CAT $LEDFILE_LASTROW |
                             $CUT -c 24-26 `




HTH

Regards,
 Richard Hall

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.