Comments for IPMI touch - ipmitool for your iPhone http://www.yellowkompressor.com/ipmi-touch unKompressed Perspective Mon, 06 Sep 2010 04:28:12 +0000 http://wordpress.org/?v=2.9.2 hourly 1 Comment on IPMI touch by Jean-Francois Mezei http://www.yellowkompressor.com/ipmi-touch/ipmi-touch/comment-page-1/#comment-684 Jean-Francois Mezei Mon, 06 Sep 2010 04:28:12 +0000 http://macbookpro.local/yellowKompressor/wp/?page_id=2#comment-684 To Trey: IPMI uses UDP on port 623 Yesterday, i tried the "light" version. The synopsis icons at top show a red fan. But none of the fan readigs are red, they are all green. Today, I bought the "touch" version. Same issue. The Chassis status has a red fan icon. But none of the individual fans show a "red", they are all green. How should I go about investigating which fan may have a problem ? To Trey: IPMI uses UDP on port 623

Yesterday, i tried the “light” version. The synopsis icons at top show a red fan. But none of the fan readigs are red, they are all green.

Today, I bought the “touch” version. Same issue. The Chassis status has a red fan icon. But none of the individual fans show a “red”, they are all green.

How should I go about investigating which fan may have a problem ?

]]> Comment on IPMI touch by Trey http://www.yellowkompressor.com/ipmi-touch/ipmi-touch/comment-page-1/#comment-236 Trey Wed, 28 Jul 2010 21:21:34 +0000 http://macbookpro.local/yellowKompressor/wp/?page_id=2#comment-236 Would like to use this software but am unable to connect to my server. I need to use a PORT so that my router can FORWARD the connection request to the appropriate internal IP. (port forwarding) When I configure IPMI Lite with xxx.xxx.xxx.xxx:port it says "address lookup for (address) failed". I'm sure it's because it's not setup to use or understand the port request. Chance this could be updated? Is there another method you would suggest using if your trying to get around a firewall to connect to a server (very typical I would think) Thanks. Would like to use this software but am unable to connect to my server. I need to use a PORT so that my router can FORWARD the connection request to the appropriate internal IP. (port forwarding) When I configure IPMI Lite with xxx.xxx.xxx.xxx:port it says “address lookup for (address) failed”. I’m sure it’s because it’s not setup to use or understand the port request. Chance this could be updated? Is there another method you would suggest using if your trying to get around a firewall to connect to a server (very typical I would think) Thanks.

]]> Comment on IPMI touch by yellowKompressor http://www.yellowkompressor.com/ipmi-touch/ipmi-touch/comment-page-1/#comment-43 yellowKompressor Tue, 29 Jun 2010 14:29:09 +0000 http://macbookpro.local/yellowKompressor/wp/?page_id=2#comment-43 Aaron, Xserve LOM requires RMCP+ OEM extension of the IPMI-over-LAN protocol (-o intelplus option in ipmitool). This extension is enabled by default in Apple-compiled ipmitool. The protocol that implements intelplus in IPMI touch is listed as <strong>IPMI v2.0 Intel with RMCP+</strong> on the protocol selection page in the app. Aaron,
Xserve LOM requires RMCP+ OEM extension of the IPMI-over-LAN protocol (-o intelplus option in ipmitool). This extension is enabled by default in Apple-compiled ipmitool. The protocol that implements intelplus in IPMI touch is listed as IPMI v2.0 Intel with RMCP+ on the protocol selection page in the app.

]]> Comment on IPMI touch by Aaron Perez http://www.yellowkompressor.com/ipmi-touch/ipmi-touch/comment-page-1/#comment-42 Aaron Perez Tue, 29 Jun 2010 06:21:49 +0000 http://macbookpro.local/yellowKompressor/wp/?page_id=2#comment-42 Dear Yellow Kompressor, I manage a few Intel XServes and I am unable to connect to LOM on any of them using IPMI Lite. What settings should I be using? The farthest I have gotten is with the following settings: Protocol: IPMI v2.0 Cipher: SHA1 name: xxxx pass: xxxx role: ADMINISTRATOR But, I always get this error: "RAKP 4 message indicates an error: invalid integrity check value". I am currently using an iPhone 4. Thanks, Aaron Dear Yellow Kompressor,

I manage a few Intel XServes and I am unable to connect to LOM on any of them using IPMI Lite. What settings should I be using?

The farthest I have gotten is with the following settings:

Protocol: IPMI v2.0
Cipher: SHA1

name: xxxx
pass: xxxx
role: ADMINISTRATOR

But, I always get this error: “RAKP 4 message indicates an error: invalid integrity check value”. I am currently using an iPhone 4.

Thanks,

Aaron

]]> Comment on IPMI light by yellowKompressor http://www.yellowkompressor.com/ipmi-touch/ipmi-light/comment-page-1/#comment-38 yellowKompressor Sun, 13 Jun 2010 05:06:47 +0000 http://macbookpro.local/yellowKompressor/wp/?page_id=126#comment-38 Thank you for your comment! Making ipmitool work on iPhone was not exactly the easiest thing ever but it was pretty straightforward. There were four major areas of concern that I can think of. 1) Converting ipmitool into Xcode project Original ipmitool relies on autoconf's configure script to setup proper compilation variables. This needed to be replicated to get it to compile under xcode. We have looked at several options like calling configure from a custom xcode build step. In the end the simplest way was to execute the configure one time outside of xcode and include the generated config.h in the project. 2) Crypto functions IPMI protocol needs a variety of crypto functions (from MD5 to AES128 in V2.0). By default ipmitool uses OpenSSL which is not an ideal choice if your target is an iPhone like device. At first, we have got OpenSSL recompiled for ARM. However, vanilla OpenSLL happened to be too CPU intensive on iPhone (not to mention that getting an app approved with OpenSSL included is a big challenge). The solution was to redo the crypto support with Apple's CommonCrypto framework. As far as I know, many CommonCrypto functions are hardware accelerated on newer i-devices. After the change the app could do 16 simultaneous AES encrypted IPMI V2.0 sessions with no perceivable slowdown. 3) Multithreading+ A big unexpected discovery was that as a command line utility ipmitool was not designed to run 'clean' repeatedly without exiting. There are numerous places in the code that use uninitialized variables. A lot of down/close functions do not provide complete clean up. There is a concept of plugins but the implementation uses static variables all over the place so forget running on multiple threads. Time wise this was a big hit. Combing though code looking for statics was not fun at all :). 4) Race conditions The code had several obscure bugs that were only triggered on a slower platform or when operating on a slow network like GPRS (not a joke, the app is tested and is fully usable even on GPRS network :)). Not a lot of issues but definitely the hardest to deal with. I think we ended up fixing about five different bugs. Hopefully this can give you a good starting point… Best of luck with your iPhone development, it is a brave new world :)! Thank you for your comment! Making ipmitool work on iPhone was not exactly the easiest thing ever but it was pretty straightforward. There were four major areas of concern that I can think of.

1) Converting ipmitool into Xcode project
Original ipmitool relies on autoconf’s configure script to setup proper compilation variables. This needed to be replicated to get it to compile under xcode. We have looked at several options like calling configure from a custom xcode build step. In the end the simplest way was to execute the configure one time outside of xcode and include the generated config.h in the project.

2) Crypto functions
IPMI protocol needs a variety of crypto functions (from MD5 to AES128 in V2.0). By default ipmitool uses OpenSSL which is not an ideal choice if your target is an iPhone like device. At first, we have got OpenSSL recompiled for ARM. However, vanilla OpenSLL happened to be too CPU intensive on iPhone (not to mention that getting an app approved with OpenSSL included is a big challenge). The solution was to redo the crypto support with Apple’s CommonCrypto framework. As far as I know, many CommonCrypto functions are hardware accelerated on newer i-devices. After the change the app could do 16 simultaneous AES encrypted IPMI V2.0 sessions with no perceivable slowdown.

3) Multithreading+
A big unexpected discovery was that as a command line utility ipmitool was not designed to run ‘clean’ repeatedly without exiting. There are numerous places in the code that use uninitialized variables. A lot of down/close functions do not provide complete clean up. There is a concept of plugins but the implementation uses static variables all over the place so forget running on multiple threads. Time wise this was a big hit. Combing though code looking for statics was not fun at all :) .

4) Race conditions
The code had several obscure bugs that were only triggered on a slower platform or when operating on a slow network like GPRS (not a joke, the app is tested and is fully usable even on GPRS network :) ). Not a lot of issues but definitely the hardest to deal with. I think we ended up fixing about five different bugs.

Hopefully this can give you a good starting point… Best of luck with your iPhone development, it is a brave new world :) !

]]> Comment on IPMI light by Todd http://www.yellowkompressor.com/ipmi-touch/ipmi-light/comment-page-1/#comment-36 Todd Sat, 05 Jun 2010 01:42:33 +0000 http://macbookpro.local/yellowKompressor/wp/?page_id=126#comment-36 Hi there, I have downloaded and used your app. Well designed and easy to navigate; I like it. This is a great idea, to use IPMI 2.0, which will accommodate many vendors' servers and provide good security. As sort of a developer myself who is starting to dabble in iphone apps and xcode, I'm curious how difficult it was for you to get the ipmitool c code compiled and working in the xcode environment. I have tried to do this previously, but had a heck of a time with it. Any insight you would be willing to provide on that front would be appreciated. Thanks!! Hi there,

I have downloaded and used your app. Well designed and easy to navigate; I like it. This is a great idea, to use IPMI 2.0, which will accommodate many vendors’ servers and provide good security. As sort of a developer myself who is starting to dabble in iphone apps and xcode, I’m curious how difficult it was for you to get the ipmitool c code compiled and working in the xcode environment. I have tried to do this previously, but had a heck of a time with it. Any insight you would be willing to provide on that front would be appreciated. Thanks!!

]]>