Hi,

 

We are observing a strange behavior with openhpi 2.8, when used on an AMC
SATA Storage Device (AM4500). Below are the details:

 

ISSUE:

The issue we are observing is that, when the chassis is switched on,
initially the BLUE LED on the AMC will be in OFF state, and when we run
openhpi 2.8 on the card, by the end of the discovery process, the BLUE LED
will be turned ON and it will remain ON forever.

 

Our Findings:

We used clia command on the chassis manager to find out the various states
that the BLUE LED is going through, and below are our observations:

1.      Normally when the chassis is rebooted, the LED State from the
getfruledstate command is:

 

 

82: FRU # 2, Led # 0 ("BLUE LED"):

     Override LED State (current state): LED OFF          

     Local Control LED State: LED ON, color: BLUE

 

      As shown in the above output, the Local control state of the LED is by
default ON. However it is overridden by the OFF state.

 

 

2.      After we run openhpi 2.8, the getfruledstate output is as below:

 

82: FRU # 2, Led # 0 ("BLUE LED"):                      

      Local Control LED State: LED ON, color: BLUE

 

      Note that, now the LED is gone back to Local Control State, and the
override state is removed, which makes it glow forever.

 

Our Analysis:

1.      We find that the “Local Control State” of this particular AMC SATA
Drive is ON by default, which is a deviation from any other LED status
(which are OFF by default)
2.      It looks like the control software on the Device has set the
override state of the LED to OFF, and that is the reason we see it OFF on
boot up.
3.      When we run openhpi discovery, during the LAMP test phase, it takes
the LED through various states, and finally gets it back to “LOCAL CONTROL
STATE”. In our case, since the local control state by default is ON, the LED
is turned on forever.

 

 

Queries:

1.      On this particular device (AM4500), the default LOCAL Control State
being ON, does it have any specific meaning?
2.      At the end of the LAMP test, openhpi moves the LED state back to
LOCAL Control State. I think this is based on the assumption that the
default state is OFF. But in this case, this assumption doesn’t hold good.
So is this an issue to be addressed in Openhpi?

 

 

Your clarifications on the above questions will be much appreciated.

 

Regards,

Shridhar


-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.446 / Virus Database: 268.18.25/743 - Release Date: 4/2/2007
4:24 PM
 
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Openhpi-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel

Reply via email to