Hi Corey, > I don't really need the ability, was just curious. Spend your time on > the next release instead of back porting this. However having the > identify status is handy. How can I reproduce the status > functionality at the chassis level?
using ipmi-chassis the --chassis-identify allows you to turn on/off the LED. The LED status can be seen from --get-chassis-status assuming your motherboard supports this ability (some older motherboards don't). Al On Sun, 2012-07-29 at 09:48 -0700, Corey Osman wrote: > > > > > Thanks, > > > Corey Osman > [email protected] > > > Green IT and Data Center Automation Specialist > > > > > > > > > > > On Jul 29, 2012, at 7:41 AM, Al Chu <[email protected]> wrote: > > > Hi Corey, > > > > On Sat, 2012-07-28 at 17:52 -0700, Corey Osman wrote: > > > Its crucial that the return status actually return the correct > > > results. ipmipower should return 1 > > > version = ipmipower - 1.1.6 > > > > I noticed this issue a few months back and fixed it in the main > > branch, > > but elected not to backport the fixes to the 1.1.X branch. Is this > > something that you consider a reasonable importance to backport? Or > > can > > you wait for the newer release (hopefully 1-2 month range). > > > I can wait. I have already hacked around the issue in the mean time. > Are there other commands that report incorrect exit codes? > > > > > > Also, why does the ipmipower command allow me to use identify-on, > > > identify-off, identify-status from the command line. These options > > > are > > > supported under the interactive command console, why are they > > > missing > > > from the command line? > > > > They were only added to the interactive mode to aid with tools (most > > notably powerman) that interact solely with the ipmipower > > interactive > > mode. Similar options exist in ipmi-chassis. > > > > If it's easier for scripting, I could add command line options for > > those > > in ipmipower, are they something that would be really useful for > > you? > > > I don't really need the ability, was just curious. Spend your time on > the next release instead of back porting this. However having the > identify status is handy. How can I reproduce the status > functionality at the chassis level? > > > > > > > > > > > Al > > > > > > > > > > > > Incorrect result > > > ---------------------- > > > ipmipower --username=admin --hostname=192.168.1.22 > > > --password=password --on > > > 192.168.1.22: authentication type unavailable for attempted > > > privilege > > > level > > > [root@puppet2 lib]# echo $? > > > 0 > > > > > > > > > > > > > > > vs > > > correct result > > > ------------------ > > > bmc-info --username=admin --hostname=192.168.1.22 > > > --password=creative > > > bmc-info: authentication type unavailable for attempted privilege > > > level > > > [root@puppet2 lib]# echo $? > > > 1 > > > > > > > > > > > > > > > Also, why does the ipmipower command allow me to use identify-on, > > > identify-off, identify-status from the command line. These options > > > are > > > supported under the interactive command console, why are they > > > missing > > > from the command line? > > > > > > > > > > > > > > > > > > > > > > > > > > > Thanks, > > > > > > > > > Corey Osman > > > [email protected] > > > > > > > > > Green IT and Data Center Automation Specialist > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > Albert Chu > > [email protected] > > Computer Scientist > > High Performance Systems Division > > Lawrence Livermore National Laboratory > > > -- Albert Chu [email protected] Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory _______________________________________________ Freeipmi-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/freeipmi-devel
