On 12/12/08, Corey Minyard <[email protected]> wrote: > I really don't know. The best I can say is to follow the spec. The > packet format should be the normal format sent by the driver, as it > follows the spec on that. The "Get Channel Authentication Capabilities" > should work without the session up. IMHO, your best bet would be to get > the info from the manufacturer. > > -corey > > Boban Petrovic wrote: >> Hey Corey, >> >> I really do think I need to properly establish a session. Do you >> have any advice where to continue looking? >> >> Boban >> >> On Thu, Dec 11, 2008 at 10:59 AM, Corey Minyard <[email protected]> wrote: >> >>> Boban Petrovic wrote: >>> >>>> Hey All, >>>> >>>> I currently work with Renesas H8 IPMC on Sun Monza board. It seems >>>> to me that anonymous access is disabled, so I would need to use "Get >>>> Channel Authentication Capabilities", "Get Session Challenge" and >>>> "Activate Session" commands in order to establish a session in Basic >>>> Mode for IPMI Serial interface (basically provide proper user and >>>> password in order to issue other commands to IPMC). This is quite >>>> possible according to spec, but it is not clear how to format packet >>>> which needs to be sent to the IPMC in case of these commands. I looked >>>> at IPMI spec v1.5, section 18.12 for Get Channel Auth Capabilities >>>> command. It states that I need to append session header to the regular >>>> IPMI request data but I am not sure how to do this. The session header >>>> is grayed out and ordering of the bytes within it is not clear. There >>>> is no example on how this should be done in case of Basic Mode (Direct >>>> codec). Any information regarding would be appreciated. >>>> >>>> >>> It would seem strange that you would channel authentication for this, no >>> other board I have seen uses that. Are you sure you need this? >>> >>> -corey >>> >>> >> Hey Corey,
I just wanted to close the loop. I was able to get to the bottom of my problem on Sun Monza boards (CP3260). As you suggested authentication is not needed for serial interface. The problem was in a way that Service Processor handles serial port on which hardware IPMC is attached. I needed to pad every IPMI message through Direct Codec with number of zero bytes. This number turned to be pretty high (close to 100 zero bytes), and I am still not sure if it depends on original message length. I am not sure if this change would be of any interest to you and wider community. I tested this change successfully on one more Sun board which used to work without this padding. Boban >> ------------------------------------------------------------------------------ >> SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, >> Nevada. >> The future of the web can't happen without you. Join us at MIX09 to help >> pave the way to the Next Web now. Learn more and register at >> http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ >> _______________________________________________ >> Openipmi-developer mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/openipmi-developer >> >> > > ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Openipmi-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openipmi-developer
