Re: [Freeipmi-users] ipmi support with HP iLO2 servers initial success!

2012-08-13 Thread Al Chu 
Hi Christian,

On Sun, 2012-08-12 at 05:07 -0700, Christian Ruppert wrote:
 # ipmimonitoring -h 10.0.0.177 --config-file /etc/icinga/ipmi.cfg 
 --quiet-cache --sdr-cache-recreate --interpret-oem-data --output-sensor-state 
 --ignore-not-available-sensors --debug
 10.0.0.177: =
 10.0.0.177: IPMI 1.5 Get Channel Authentication Capabilities Request
 10.0.0.177: =
 10.0.0.177: RMCP Header:
 10.0.0.177: 
 10.0.0.177: [   6h] = version[ 8b]
 10.0.0.177: [   0h] = reserved[ 8b]
 10.0.0.177: [  FFh] = sequence_number[ 8b]
 10.0.0.177: [   7h] = message_class.class[ 5b]
 10.0.0.177: [   0h] = message_class.reserved[ 2b]
 10.0.0.177: [   0h] = message_class.ack[ 1b]
 10.0.0.177: IPMI Session Header:
 10.0.0.177: 
 10.0.0.177: [   0h] = authentication_type[ 8b]
 10.0.0.177: [   0h] = session_sequence_number[32b]
 10.0.0.177: [   0h] = session_id[32b]
 10.0.0.177: [   9h] = ipmi_msg_len[ 8b]
 10.0.0.177: IPMI Message Header:
 10.0.0.177: 
 10.0.0.177: [  20h] = rs_addr[ 8b]
 10.0.0.177: [   0h] = rs_lun[ 2b]
 10.0.0.177: [   6h] = net_fn[ 6b]
 10.0.0.177: [  C8h] = checksum1[ 8b]
 10.0.0.177: [  81h] = rq_addr[ 8b]
 10.0.0.177: [   0h] = rq_lun[ 2b]
 10.0.0.177: [  1Ch] = rq_seq[ 6b]
 10.0.0.177: IPMI Command Data:
 10.0.0.177: --
 10.0.0.177: [  38h] = cmd[ 8b]
 10.0.0.177: [   Eh] = channel_number[ 4b]
 10.0.0.177: [   0h] = reserved1[ 3b]
 10.0.0.177: [   0h] = get_ipmi_v2.0_extended_data[ 1b]
 10.0.0.177: [   2h] = maximum_privilege_level[ 4b]
 10.0.0.177: [   0h] = reserved2[ 4b]
 10.0.0.177: IPMI Trailer:
 10.0.0.177: --
 10.0.0.177: [  C7h] = checksum2[ 8b]
 10.0.0.177: =
 10.0.0.177: IPMI 1.5 Get Channel Authentication Capabilities Request
 10.0.0.177: =
 10.0.0.177: RMCP Header:
 10.0.0.177: 
 10.0.0.177: [   6h] = version[ 8b]
 10.0.0.177: [   0h] = reserved[ 8b]
 10.0.0.177: [  FFh] = sequence_number[ 8b]
 10.0.0.177: [   7h] = message_class.class[ 5b]
 10.0.0.177: [   0h] = message_class.reserved[ 2b]
 10.0.0.177: [   0h] = message_class.ack[ 1b]
 10.0.0.177: IPMI Session Header:
 10.0.0.177: 
 10.0.0.177: [   0h] = authentication_type[ 8b]
 10.0.0.177: [   0h] = session_sequence_number[32b]
 10.0.0.177: [   0h] = session_id[32b]
 10.0.0.177: [   9h] = ipmi_msg_len[ 8b]
 10.0.0.177: IPMI Message Header:
 10.0.0.177: 
 10.0.0.177: [  20h] = rs_addr[ 8b]
 10.0.0.177: [   0h] = rs_lun[ 2b]
 10.0.0.177: [   6h] = net_fn[ 6b]
 10.0.0.177: [  C8h] = checksum1[ 8b]
 10.0.0.177: [  81h] = rq_addr[ 8b]
 10.0.0.177: [   0h] = rq_lun[ 2b]
 10.0.0.177: [  1Dh] = rq_seq[ 6b]
 10.0.0.177: IPMI Command Data:
 10.0.0.177: --
 10.0.0.177: [  38h] = cmd[ 8b]
 10.0.0.177: [   Eh] = channel_number[ 4b]
 10.0.0.177: [   0h] = reserved1[ 3b]
 10.0.0.177: [   0h] = get_ipmi_v2.0_extended_data[ 1b]
 10.0.0.177: [   2h] = maximum_privilege_level[ 4b]
 10.0.0.177: [   0h] = reserved2[ 4b]
 10.0.0.177: IPMI Trailer:
 10.0.0.177: --
 10.0.0.177: [  C3h] = checksum2[ 8b]
 10.0.0.177: =
 10.0.0.177: IPMI 1.5 Get Channel Authentication Capabilities Request
 10.0.0.177: =
 10.0.0.177: RMCP Header:
 10.0.0.177: 
 10.0.0.177: [   6h] = version[ 8b]
 10.0.0.177: [   0h] = reserved[ 8b]
 10.0.0.177: [  FFh] = sequence_number[ 8b]
 10.0.0.177: [   7h] = message_class.class[ 5b]
 10.0.0.177: [   0h] = message_class.reserved[ 2b]
 10.0.0.177: [   0h] = message_class.ack[ 1b]
 10.0.0.177: IPMI Session Header:
 10.0.0.177: 
 10.0.0.177: [   0h] = authentication_type[ 8b]
 10.0.0.177: [   0h] = session_sequence_number[32b]
 10.0.0.177: [   0h] = session_id[32b]
 10.0.0.177: [   9h] = ipmi_msg_len[ 8b]
 10.0.0.177: IPMI Message Header:
 10.0.0.177: 
 10.0.0.177: [  20h] = rs_addr[ 8b]
 10.0.0.177: [   0h] = rs_lun[ 2b]
 10.0.0.177: [   6h] = net_fn[ 6b]
 10.0.0.177: [  C8h] = checksum1[ 8b]
 10.0.0.177:

Re: [Freeipmi-users] ipmi support with HP iLO2 servers initial success!

2012-08-13 Thread Albert Chu 
Hi Christian,

I'm really questioning if that system has IPMI.  It's always possible,
but it's current configuration is certainly not allowing it.  You'd have
to ping HP on that kind of setup.  Sorry, but I don't think much more
can be done from the FreeIPMI side.

Al

On Mon, 2012-08-13 at 11:41 -0700, Christian Ruppert wrote:
 Hi Albert,
 
 On 08/12/12 at 11:40PM -0700, Al Chu wrote:
  Hi Christian,
  
  On Sun, 2012-08-12 at 05:07 -0700, Christian Ruppert wrote:
   # ipmimonitoring -h 10.0.0.177 --config-file /etc/icinga/ipmi.cfg 
   --quiet-cache --sdr-cache-recreate --interpret-oem-data 
   --output-sensor-state --ignore-not-available-sensors --debug
   10.0.0.177: =
   10.0.0.177: IPMI 1.5 Get Channel Authentication Capabilities Request
   10.0.0.177: =
   10.0.0.177: RMCP Header:
   10.0.0.177: 
   10.0.0.177: [   6h] = version[ 8b]
   10.0.0.177: [   0h] = reserved[ 8b]
   10.0.0.177: [  FFh] = sequence_number[ 8b]
   10.0.0.177: [   7h] = message_class.class[ 5b]
   10.0.0.177: [   0h] = message_class.reserved[ 2b]
   10.0.0.177: [   0h] = message_class.ack[ 1b]
   10.0.0.177: IPMI Session Header:
   10.0.0.177: 
   10.0.0.177: [   0h] = authentication_type[ 8b]
   10.0.0.177: [   0h] = session_sequence_number[32b]
   10.0.0.177: [   0h] = session_id[32b]
   10.0.0.177: [   9h] = ipmi_msg_len[ 8b]
   10.0.0.177: IPMI Message Header:
   10.0.0.177: 
   10.0.0.177: [  20h] = rs_addr[ 8b]
   10.0.0.177: [   0h] = rs_lun[ 2b]
   10.0.0.177: [   6h] = net_fn[ 6b]
   10.0.0.177: [  C8h] = checksum1[ 8b]
   10.0.0.177: [  81h] = rq_addr[ 8b]
   10.0.0.177: [   0h] = rq_lun[ 2b]
   10.0.0.177: [  1Ch] = rq_seq[ 6b]
   10.0.0.177: IPMI Command Data:
   10.0.0.177: --
   10.0.0.177: [  38h] = cmd[ 8b]
   10.0.0.177: [   Eh] = channel_number[ 4b]
   10.0.0.177: [   0h] = reserved1[ 3b]
   10.0.0.177: [   0h] = get_ipmi_v2.0_extended_data[ 1b]
   10.0.0.177: [   2h] = maximum_privilege_level[ 4b]
   10.0.0.177: [   0h] = reserved2[ 4b]
   10.0.0.177: IPMI Trailer:
   10.0.0.177: --
   10.0.0.177: [  C7h] = checksum2[ 8b]
   10.0.0.177: =
   10.0.0.177: IPMI 1.5 Get Channel Authentication Capabilities Request
   10.0.0.177: =
   10.0.0.177: RMCP Header:
   10.0.0.177: 
   10.0.0.177: [   6h] = version[ 8b]
   10.0.0.177: [   0h] = reserved[ 8b]
   10.0.0.177: [  FFh] = sequence_number[ 8b]
   10.0.0.177: [   7h] = message_class.class[ 5b]
   10.0.0.177: [   0h] = message_class.reserved[ 2b]
   10.0.0.177: [   0h] = message_class.ack[ 1b]
   10.0.0.177: IPMI Session Header:
   10.0.0.177: 
   10.0.0.177: [   0h] = authentication_type[ 8b]
   10.0.0.177: [   0h] = session_sequence_number[32b]
   10.0.0.177: [   0h] = session_id[32b]
   10.0.0.177: [   9h] = ipmi_msg_len[ 8b]
   10.0.0.177: IPMI Message Header:
   10.0.0.177: 
   10.0.0.177: [  20h] = rs_addr[ 8b]
   10.0.0.177: [   0h] = rs_lun[ 2b]
   10.0.0.177: [   6h] = net_fn[ 6b]
   10.0.0.177: [  C8h] = checksum1[ 8b]
   10.0.0.177: [  81h] = rq_addr[ 8b]
   10.0.0.177: [   0h] = rq_lun[ 2b]
   10.0.0.177: [  1Dh] = rq_seq[ 6b]
   10.0.0.177: IPMI Command Data:
   10.0.0.177: --
   10.0.0.177: [  38h] = cmd[ 8b]
   10.0.0.177: [   Eh] = channel_number[ 4b]
   10.0.0.177: [   0h] = reserved1[ 3b]
   10.0.0.177: [   0h] = get_ipmi_v2.0_extended_data[ 1b]
   10.0.0.177: [   2h] = maximum_privilege_level[ 4b]
   10.0.0.177: [   0h] = reserved2[ 4b]
   10.0.0.177: IPMI Trailer:
   10.0.0.177: --
   10.0.0.177: [  C3h] = checksum2[ 8b]
   10.0.0.177: =
   10.0.0.177: IPMI 1.5 Get Channel Authentication Capabilities Request
   10.0.0.177: =
   10.0.0.177: RMCP Header:
   10.0.0.177: 
   10.0.0.177: [   6h] = version[ 8b]
   10.0.0.177: [   0h] = reserved[ 8b]
   10.0.0.177: [  FFh] = sequence_number[ 8b]
   10.0.0.177: [   7h] = message_class.class[ 5b]
   10.0.0.177: [   0h] = message_class.reserved[ 2b]
   10.0.0.177: [   0h] = message_class.ack[

Re: [Freeipmi-users] ipmi support with HP iLO2 servers initial success!

2012-08-13 Thread Johnson, Bill 
Guys reading this email, I did a quick google and found this link:
http://old.nabble.com/ipmi-support-with-HP-iLO2-servers-initial-success!-td29527071.html

is the firmware on the ILO up to date?

Thanks,
Bill

On Aug 13, 2012, at 1:47 PM, Albert Chu ch...@llnl.gov wrote:

Hi Christian,

I'm really questioning if that system has IPMI.  It's always possible,
but it's current configuration is certainly not allowing it.  You'd have
to ping HP on that kind of setup.  Sorry, but I don't think much more
can be done from the FreeIPMI side.

Al

On Mon, 2012-08-13 at 11:41 -0700, Christian Ruppert wrote:
 Hi Albert,

 On 08/12/12 at 11:40PM -0700, Al Chu wrote:
 Hi Christian,

 On Sun, 2012-08-12 at 05:07 -0700, Christian Ruppert wrote:
 # ipmimonitoring -h 10.0.0.177 --config-file /etc/icinga/ipmi.cfg 
 --quiet-cache --sdr-cache-recreate --interpret-oem-data 
 --output-sensor-state --ignore-not-available-sensors --debug
 10.0.0.177: =
 10.0.0.177: IPMI 1.5 Get Channel Authentication Capabilities Request
 10.0.0.177: =
 10.0.0.177: RMCP Header:
 10.0.0.177: 
 10.0.0.177: [   6h] = version[ 8b]
 10.0.0.177: [   0h] = reserved[ 8b]
 10.0.0.177: [  FFh] = sequence_number[ 8b]
 10.0.0.177: [   7h] = message_class.class[ 5b]
 10.0.0.177: [   0h] = message_class.reserved[ 2b]
 10.0.0.177: [   0h] = message_class.ack[ 1b]
 10.0.0.177: IPMI Session Header:
 10.0.0.177: 
 10.0.0.177: [   0h] = authentication_type[ 8b]
 10.0.0.177: [   0h] = session_sequence_number[32b]
 10.0.0.177: [   0h] = session_id[32b]
 10.0.0.177: [   9h] = ipmi_msg_len[ 8b]
 10.0.0.177: IPMI Message Header:
 10.0.0.177: 
 10.0.0.177: [  20h] = rs_addr[ 8b]
 10.0.0.177: [   0h] = rs_lun[ 2b]
 10.0.0.177: [   6h] = net_fn[ 6b]
 10.0.0.177: [  C8h] = checksum1[ 8b]
 10.0.0.177: [  81h] = rq_addr[ 8b]
 10.0.0.177: [   0h] = rq_lun[ 2b]
 10.0.0.177: [  1Ch] = rq_seq[ 6b]
 10.0.0.177: IPMI Command Data:
 10.0.0.177: --
 10.0.0.177: [  38h] = cmd[ 8b]
 10.0.0.177: [   Eh] = channel_number[ 4b]
 10.0.0.177: [   0h] = reserved1[ 3b]
 10.0.0.177: [   0h] = get_ipmi_v2.0_extended_data[ 1b]
 10.0.0.177: [   2h] = maximum_privilege_level[ 4b]
 10.0.0.177: [   0h] = reserved2[ 4b]
 10.0.0.177: IPMI Trailer:
 10.0.0.177: --
 10.0.0.177: [  C7h] = checksum2[ 8b]
 10.0.0.177: =
 10.0.0.177: IPMI 1.5 Get Channel Authentication Capabilities Request
 10.0.0.177: =
 10.0.0.177: RMCP Header:
 10.0.0.177: 
 10.0.0.177: [   6h] = version[ 8b]
 10.0.0.177: [   0h] = reserved[ 8b]
 10.0.0.177: [  FFh] = sequence_number[ 8b]
 10.0.0.177: [   7h] = message_class.class[ 5b]
 10.0.0.177: [   0h] = message_class.reserved[ 2b]
 10.0.0.177: [   0h] = message_class.ack[ 1b]
 10.0.0.177: IPMI Session Header:
 10.0.0.177: 
 10.0.0.177: [   0h] = authentication_type[ 8b]
 10.0.0.177: [   0h] = session_sequence_number[32b]
 10.0.0.177: [   0h] = session_id[32b]
 10.0.0.177: [   9h] = ipmi_msg_len[ 8b]
 10.0.0.177: IPMI Message Header:
 10.0.0.177: 
 10.0.0.177: [  20h] = rs_addr[ 8b]
 10.0.0.177: [   0h] = rs_lun[ 2b]
 10.0.0.177: [   6h] = net_fn[ 6b]
 10.0.0.177: [  C8h] = checksum1[ 8b]
 10.0.0.177: [  81h] = rq_addr[ 8b]
 10.0.0.177: [   0h] = rq_lun[ 2b]
 10.0.0.177: [  1Dh] = rq_seq[ 6b]
 10.0.0.177: IPMI Command Data:
 10.0.0.177: --
 10.0.0.177: [  38h] = cmd[ 8b]
 10.0.0.177: [   Eh] = channel_number[ 4b]
 10.0.0.177: [   0h] = reserved1[ 3b]
 10.0.0.177: [   0h] = get_ipmi_v2.0_extended_data[ 1b]
 10.0.0.177: [   2h] = maximum_privilege_level[ 4b]
 10.0.0.177: [   0h] = reserved2[ 4b]
 10.0.0.177: IPMI Trailer:
 10.0.0.177: --
 10.0.0.177: [  C3h] = checksum2[ 8b]
 10.0.0.177: =
 10.0.0.177: IPMI 1.5 Get Channel Authentication Capabilities Request
 10.0.0.177: =
 10.0.0.177: RMCP Header:
 10.0.0.177: 
 10.0.0.177: [   6h] = version[ 8b]
 10.0.0.177: [   0h] = reserved[ 8b]
 10.0.0.177: [  FFh] = sequence_number[ 8b]
 10.0.0.177: [   7h] = message_class.class[ 5b]
 10.0.0.177: [

Re: [Freeipmi-users] ipmi support with HP iLO2 servers initial success!

2012-02-17 Thread john s. 


Hello Al Chu 


Here is the Debug file when the error says username invalid:



xxx.xxx.xxx.xxx: =
xxx.xxx.xxx.xxx: IPMI 1.5 Get Channel Authentication Capabilities Request
xxx.xxx.xxx.xxx: =
xxx.xxx.xxx.xxx: RMCP Header:
xxx.xxx.xxx.xxx: 
xxx.xxx.xxx.xxx: [   6h] = version[ 8b]
xxx.xxx.xxx.xxx: [   0h] = reserved[ 8b]
xxx.xxx.xxx.xxx: [  FFh] = sequence_number[ 8b]
xxx.xxx.xxx.xxx: [   7h] = message_class.class[ 5b]
xxx.xxx.xxx.xxx: [   0h] = message_class.reserved[ 2b]
xxx.xxx.xxx.xxx: [   0h] = message_class.ack[ 1b]
xxx.xxx.xxx.xxx: IPMI Session Header:
xxx.xxx.xxx.xxx: 
xxx.xxx.xxx.xxx: [   0h] = authentication_type[ 8b]
xxx.xxx.xxx.xxx: [   0h] = session_sequence_number[32b]
xxx.xxx.xxx.xxx: [   0h] = session_id[32b]
xxx.xxx.xxx.xxx: [   9h] = ipmi_msg_len[ 8b]
xxx.xxx.xxx.xxx: IPMI Message Header:
xxx.xxx.xxx.xxx: 
xxx.xxx.xxx.xxx: [  20h] = rs_addr[ 8b]
xxx.xxx.xxx.xxx: [   0h] = rs_lun[ 2b]
xxx.xxx.xxx.xxx: [   6h] = net_fn[ 6b]
xxx.xxx.xxx.xxx: [  C8h] = checksum1[ 8b]
xxx.xxx.xxx.xxx: [  81h] = rq_addr[ 8b]
xxx.xxx.xxx.xxx: [   0h] = rq_lun[ 2b]
xxx.xxx.xxx.xxx: [   5h] = rq_seq[ 6b]
xxx.xxx.xxx.xxx: IPMI Command Data:
xxx.xxx.xxx.xxx: --
xxx.xxx.xxx.xxx: [  38h] = cmd[ 8b]
xxx.xxx.xxx.xxx: [   Eh] = channel_number[ 4b]
xxx.xxx.xxx.xxx: [   0h] = reserved1[ 3b]
xxx.xxx.xxx.xxx: [   1h] = get_ipmi_v2.0_extended_data[ 1b]
xxx.xxx.xxx.xxx: [   2h] = maximum_privilege_level[ 4b]
xxx.xxx.xxx.xxx: [   0h] = reserved2[ 4b]
xxx.xxx.xxx.xxx: IPMI Trailer:
xxx.xxx.xxx.xxx: --
xxx.xxx.xxx.xxx: [  A3h] = checksum2[ 8b]
xxx.xxx.xxx.xxx: =
xxx.xxx.xxx.xxx: IPMI 1.5 Get Channel Authentication Capabilities Response
xxx.xxx.xxx.xxx: =
xxx.xxx.xxx.xxx: RMCP Header:
xxx.xxx.xxx.xxx: 
xxx.xxx.xxx.xxx: [   6h] = version[ 8b]
xxx.xxx.xxx.xxx: [   0h] = reserved[ 8b]
xxx.xxx.xxx.xxx: [  FFh] = sequence_number[ 8b]
xxx.xxx.xxx.xxx: [   7h] = message_class.class[ 5b]
xxx.xxx.xxx.xxx: [   0h] = message_class.reserved[ 2b]
xxx.xxx.xxx.xxx: [   0h] = message_class.ack[ 1b]
xxx.xxx.xxx.xxx: IPMI Session Header:
xxx.xxx.xxx.xxx: 
xxx.xxx.xxx.xxx: [   0h] = authentication_type[ 8b]
xxx.xxx.xxx.xxx: [   0h] = session_sequence_number[32b]
xxx.xxx.xxx.xxx: [   0h] = session_id[32b]
xxx.xxx.xxx.xxx: [  10h] = ipmi_msg_len[ 8b]
xxx.xxx.xxx.xxx: IPMI Message Header:
xxx.xxx.xxx.xxx: 
xxx.xxx.xxx.xxx: [  81h] = rq_addr[ 8b]
xxx.xxx.xxx.xxx: [   0h] = rq_lun[ 2b]
xxx.xxx.xxx.xxx: [   7h] = net_fn[ 6b]
xxx.xxx.xxx.xxx: [  63h] = checksum1[ 8b]
xxx.xxx.xxx.xxx: [  20h] = rs_addr[ 8b]
xxx.xxx.xxx.xxx: [   0h] = rs_lun[ 2b]
xxx.xxx.xxx.xxx: [   5h] = rq_seq[ 6b]
xxx.xxx.xxx.xxx: IPMI Command Data:
xxx.xxx.xxx.xxx: --
xxx.xxx.xxx.xxx: [  38h] = cmd[ 8b]
xxx.xxx.xxx.xxx: [   0h] = comp_code[ 8b]
xxx.xxx.xxx.xxx: [   2h] = channel_number[ 8b]
xxx.xxx.xxx.xxx: [   0h] = authentication_type.none[ 1b]
xxx.xxx.xxx.xxx: [   0h] = authentication_type.md2[ 1b]
xxx.xxx.xxx.xxx: [   0h] = authentication_type.md5[ 1b]
xxx.xxx.xxx.xxx: [   0h] = authentication_type.reserved1[ 1b]
xxx.xxx.xxx.xxx: [   0h] =
authentication_type.straight_password_key[ 1b]
xxx.xxx.xxx.xxx: [   0h] = authentication_type.oem_prop[ 1b]
xxx.xxx.xxx.xxx: [   0h] = authentication_type.reserved2[ 1b]
xxx.xxx.xxx.xxx: [   1h] =
authentication_type.ipmi_v2.0_extended_capabilities_available[ 1b]
xxx.xxx.xxx.xxx: [   0h] =
authentication_status.anonymous_login[ 1b]
xxx.xxx.xxx.xxx: [   0h] = authentication_status.null_username[
1b]
xxx.xxx.xxx.xxx: [   1h] =
authentication_status.non_null_username[ 1b]
xxx.xxx.xxx.xxx: [   0h] =
authentication_status.user_level_authentication[ 1b]
xxx.xxx.xxx.xxx: [   1h] =
authentication_status.per_message_authentication[ 1b]
xxx.xxx.xxx.xxx: [   0h] = authentication_status.k_g[ 1b]
xxx.xxx.xxx.xxx: [   0h] = authentication_status.reserved[ 2b]
xxx.xxx.xxx.xxx: [   0h] =
channel_supports_ipmi_v1.5_connections[ 1b]
xxx.xxx.xxx.xxx: [   1h] =

Re: [Freeipmi-users] ipmi support with HP iLO2 servers initial success!

2012-02-17 Thread Albert Chu 
Hi John,

I assume this username works when using IPMI 1.5 (-D lan) vs. IPMI 2.0
(-D lan_2_0)?

I wonder if some of the workarounds like -W opensesspriv would help.
Or perhaps some other options like a different privilege level (-l
admin).  If it works under IPMI 1.5 but not IPMI 2.0, I'm thinking
there's a subtle bug in HP's authentication mechanism.

Al


On Fri, 2012-02-17 at 00:28 -0800, john s. wrote:
 
 Hello Al Chu
 
 
 Here is the Debug file when the error says username invalid:
 
 
 
 xxx.xxx.xxx.xxx: =
 xxx.xxx.xxx.xxx: IPMI 1.5 Get Channel Authentication Capabilities Request
 xxx.xxx.xxx.xxx: =
 xxx.xxx.xxx.xxx: RMCP Header:
 xxx.xxx.xxx.xxx: 
 xxx.xxx.xxx.xxx: [   6h] = version[ 8b]
 xxx.xxx.xxx.xxx: [   0h] = reserved[ 8b]
 xxx.xxx.xxx.xxx: [  FFh] = sequence_number[ 8b]
 xxx.xxx.xxx.xxx: [   7h] = message_class.class[ 5b]
 xxx.xxx.xxx.xxx: [   0h] = message_class.reserved[ 2b]
 xxx.xxx.xxx.xxx: [   0h] = message_class.ack[ 1b]
 xxx.xxx.xxx.xxx: IPMI Session Header:
 xxx.xxx.xxx.xxx: 
 xxx.xxx.xxx.xxx: [   0h] = authentication_type[ 8b]
 xxx.xxx.xxx.xxx: [   0h] = session_sequence_number[32b]
 xxx.xxx.xxx.xxx: [   0h] = session_id[32b]
 xxx.xxx.xxx.xxx: [   9h] = ipmi_msg_len[ 8b]
 xxx.xxx.xxx.xxx: IPMI Message Header:
 xxx.xxx.xxx.xxx: 
 xxx.xxx.xxx.xxx: [  20h] = rs_addr[ 8b]
 xxx.xxx.xxx.xxx: [   0h] = rs_lun[ 2b]
 xxx.xxx.xxx.xxx: [   6h] = net_fn[ 6b]
 xxx.xxx.xxx.xxx: [  C8h] = checksum1[ 8b]
 xxx.xxx.xxx.xxx: [  81h] = rq_addr[ 8b]
 xxx.xxx.xxx.xxx: [   0h] = rq_lun[ 2b]
 xxx.xxx.xxx.xxx: [   5h] = rq_seq[ 6b]
 xxx.xxx.xxx.xxx: IPMI Command Data:
 xxx.xxx.xxx.xxx: --
 xxx.xxx.xxx.xxx: [  38h] = cmd[ 8b]
 xxx.xxx.xxx.xxx: [   Eh] = channel_number[ 4b]
 xxx.xxx.xxx.xxx: [   0h] = reserved1[ 3b]
 xxx.xxx.xxx.xxx: [   1h] = get_ipmi_v2.0_extended_data[ 1b]
 xxx.xxx.xxx.xxx: [   2h] = maximum_privilege_level[ 4b]
 xxx.xxx.xxx.xxx: [   0h] = reserved2[ 4b]
 xxx.xxx.xxx.xxx: IPMI Trailer:
 xxx.xxx.xxx.xxx: --
 xxx.xxx.xxx.xxx: [  A3h] = checksum2[ 8b]
 xxx.xxx.xxx.xxx: =
 xxx.xxx.xxx.xxx: IPMI 1.5 Get Channel Authentication Capabilities Response
 xxx.xxx.xxx.xxx: =
 xxx.xxx.xxx.xxx: RMCP Header:
 xxx.xxx.xxx.xxx: 
 xxx.xxx.xxx.xxx: [   6h] = version[ 8b]
 xxx.xxx.xxx.xxx: [   0h] = reserved[ 8b]
 xxx.xxx.xxx.xxx: [  FFh] = sequence_number[ 8b]
 xxx.xxx.xxx.xxx: [   7h] = message_class.class[ 5b]
 xxx.xxx.xxx.xxx: [   0h] = message_class.reserved[ 2b]
 xxx.xxx.xxx.xxx: [   0h] = message_class.ack[ 1b]
 xxx.xxx.xxx.xxx: IPMI Session Header:
 xxx.xxx.xxx.xxx: 
 xxx.xxx.xxx.xxx: [   0h] = authentication_type[ 8b]
 xxx.xxx.xxx.xxx: [   0h] = session_sequence_number[32b]
 xxx.xxx.xxx.xxx: [   0h] = session_id[32b]
 xxx.xxx.xxx.xxx: [  10h] = ipmi_msg_len[ 8b]
 xxx.xxx.xxx.xxx: IPMI Message Header:
 xxx.xxx.xxx.xxx: 
 xxx.xxx.xxx.xxx: [  81h] = rq_addr[ 8b]
 xxx.xxx.xxx.xxx: [   0h] = rq_lun[ 2b]
 xxx.xxx.xxx.xxx: [   7h] = net_fn[ 6b]
 xxx.xxx.xxx.xxx: [  63h] = checksum1[ 8b]
 xxx.xxx.xxx.xxx: [  20h] = rs_addr[ 8b]
 xxx.xxx.xxx.xxx: [   0h] = rs_lun[ 2b]
 xxx.xxx.xxx.xxx: [   5h] = rq_seq[ 6b]
 xxx.xxx.xxx.xxx: IPMI Command Data:
 xxx.xxx.xxx.xxx: --
 xxx.xxx.xxx.xxx: [  38h] = cmd[ 8b]
 xxx.xxx.xxx.xxx: [   0h] = comp_code[ 8b]
 xxx.xxx.xxx.xxx: [   2h] = channel_number[ 8b]
 xxx.xxx.xxx.xxx: [   0h] = authentication_type.none[ 1b]
 xxx.xxx.xxx.xxx: [   0h] = authentication_type.md2[ 1b]
 xxx.xxx.xxx.xxx: [   0h] = authentication_type.md5[ 1b]
 xxx.xxx.xxx.xxx: [   0h] = authentication_type.reserved1[ 1b]
 xxx.xxx.xxx.xxx: [   0h] =
 authentication_type.straight_password_key[ 1b]
 xxx.xxx.xxx.xxx: [   0h] = authentication_type.oem_prop[ 1b]
 xxx.xxx.xxx.xxx: [   0h] = authentication_type.reserved2[ 1b]
 xxx.xxx.xxx.xxx: [   1h] =
 authentication_type.ipmi_v2.0_extended_capabilities_available[ 1b]
 xxx.xxx.xxx.xxx: [   0h] =
 authentication_status.anonymous_login[ 1b]
 xxx.xxx.xxx.xxx: [   0h] = authentication_status.null_username[
 1b]
 xxx.xxx.xxx.xxx: [   1h] =

Re: [Freeipmi-users] ipmi support with HP iLO2 servers initial success!

2012-02-15 Thread john s. 


Hello Al Chu 

sorry but i haven't anytime to take care over my ilo problem


so here is the bmc config output: 


Section UserX Comments 
#
# In the following User sections, users should configure usernames,
passwords, 
# and access rights for IPMI over LAN communication. Usernames can be set to
any 
# string with the exception of User1, which is a fixed to the anonymous 
# username in IPMI. 
#
# For IPMI over LAN access for a username, set Enable_User to Yes, 
# Lan_Enable_IPMI_Msgs to Yes, and Lan_Privilege_Limit to a privilege 
# level. The privilege level is used to limit various IPMI operations for 
# individual usernames. It is recommened that atleast one username be
created 
# with a privilege limit Administrator, so all system functions are
available 
# to atleast one username via IPMI over LAN. For security reasons, we
recommend 
# not enabling the anonymous User1. For most users, Lan_Session_Limit
can be 
# set to 0 (or ignored) to support an unlimited number of simultaneous IPMI
over 
# LAN sessions. 
#
# If your system supports IPMI 2.0 and Serial-over-LAN (SOL), 
# aSOL_Payload_Access field may be listed below. Set the
SOL_Payload_Access 
# field to Yes or No to enable or disable this username's ability to
access 
# SOL. 
#
# Please do not forget to uncomment those fields, such as Password, that
may 
# be commented out during the checkout. 
#
# Some motherboards may require a Username to be configured prior to other 
# fields being read/written. If this is the case, those fields will be set
to 
# username-not-set-yet. 
#
Section User1
## Give Username
## Username   NULL
## Give password or blank to clear. MAX 16 chars (20 chars if IPMI 2.0
supported).
## Password   
## Possible values: Yes/No or blank to not set
Enable_User   Yes
## Possible values: Yes/No
Lan_Enable_IPMI_Msgs  Yes
## Possible values: Yes/No
Lan_Enable_Link_Auth  No
## Possible values: Yes/No
Lan_Enable_Restricted_to_Callback No
## Possible values:
Callback/User/Operator/Administrator/OEM_Proprietary/No_Access
Lan_Privilege_Limit   Administrator
## Possible values: 0-17, 0 is unlimited; May be reset to 0 if not
specified
## Lan_Session_Limit  
EndSection
Section User2
## Give Username
Username  ilox
## Give password or blank to clear. MAX 16 chars (20 chars if IPMI 2.0
supported).
## Password   
## Possible values: Yes/No or blank to not set
Enable_User   Yes
## Possible values: Yes/No
Lan_Enable_IPMI_Msgs  Yes
## Possible values: Yes/No
Lan_Enable_Link_Auth  No
## Possible values: Yes/No
Lan_Enable_Restricted_to_Callback No
## Possible values:
Callback/User/Operator/Administrator/OEM_Proprietary/No_Access
Lan_Privilege_Limit   Administrator
## Possible values: 0-17, 0 is unlimited; May be reset to 0 if not
specified
## Lan_Session_Limit  
EndSection
Section User3
## Give Username
Username  OAtmp1322558051
## Give password or blank to clear. MAX 16 chars (20 chars if IPMI 2.0
supported).
## Password   
## Possible values: Yes/No or blank to not set
Enable_User   Yes
## Possible values: Yes/No
Lan_Enable_IPMI_Msgs  Yes
## Possible values: Yes/No
Lan_Enable_Link_Auth  No
## Possible values: Yes/No
Lan_Enable_Restricted_to_Callback No
## Possible values:
Callback/User/Operator/Administrator/OEM_Proprietary/No_Access
Lan_Privilege_Limit   Administrator
## Possible values: 0-17, 0 is unlimited; May be reset to 0 if not
specified
## Lan_Session_Limit  
EndSection
Section User4
## Give Username
Username  OAtmp1322568826
## Give password or blank to clear. MAX 16 chars (20 chars if IPMI 2.0
supported).
## Password   
## Possible values: Yes/No or blank to not set
Enable_User   Yes
## Possible values: Yes/No
Lan_Enable_IPMI_Msgs  Yes
## Possible values: Yes/No
Lan_Enable_Link_Auth  No
## Possible values:

Re: [Freeipmi-users] ipmi support with HP iLO2 servers initial success!

2012-02-15 Thread Albert Chu 
Things look fine in general for what you provided.  It's possible some
of the authentication options below would cause issues too.

Can you provide the --debug output when you get a username error.

Al

On Wed, 2012-02-15 at 06:06 -0800, john s. wrote:
 
 Hello Al Chu
 
 sorry but i haven't anytime to take care over my ilo problem
 
 
 so here is the bmc config output:
 
 
 Section UserX Comments
 #
 # In the following User sections, users should configure usernames,
 passwords,
 # and access rights for IPMI over LAN communication. Usernames can be set to
 any
 # string with the exception of User1, which is a fixed to the anonymous
 # username in IPMI.
 #
 # For IPMI over LAN access for a username, set Enable_User to Yes,
 # Lan_Enable_IPMI_Msgs to Yes, and Lan_Privilege_Limit to a privilege
 # level. The privilege level is used to limit various IPMI operations for
 # individual usernames. It is recommened that atleast one username be
 created
 # with a privilege limit Administrator, so all system functions are
 available
 # to atleast one username via IPMI over LAN. For security reasons, we
 recommend
 # not enabling the anonymous User1. For most users, Lan_Session_Limit
 can be
 # set to 0 (or ignored) to support an unlimited number of simultaneous IPMI
 over
 # LAN sessions.
 #
 # If your system supports IPMI 2.0 and Serial-over-LAN (SOL),
 # aSOL_Payload_Access field may be listed below. Set the
 SOL_Payload_Access
 # field to Yes or No to enable or disable this username's ability to
 access
 # SOL.
 #
 # Please do not forget to uncomment those fields, such as Password, that
 may
 # be commented out during the checkout.
 #
 # Some motherboards may require a Username to be configured prior to other
 # fields being read/written. If this is the case, those fields will be set
 to
 # username-not-set-yet.
 #
 Section User1
 ## Give Username
 ## Username   NULL
 ## Give password or blank to clear. MAX 16 chars (20 chars if IPMI 2.0
 supported).
 ## Password
 ## Possible values: Yes/No or blank to not set
 Enable_User   Yes
 ## Possible values: Yes/No
 Lan_Enable_IPMI_Msgs  Yes
 ## Possible values: Yes/No
 Lan_Enable_Link_Auth  No
 ## Possible values: Yes/No
 Lan_Enable_Restricted_to_Callback No
 ## Possible values:
 Callback/User/Operator/Administrator/OEM_Proprietary/No_Access
 Lan_Privilege_Limit   Administrator
 ## Possible values: 0-17, 0 is unlimited; May be reset to 0 if not
 specified
 ## Lan_Session_Limit
 EndSection
 Section User2
 ## Give Username
 Username  ilox
 ## Give password or blank to clear. MAX 16 chars (20 chars if IPMI 2.0
 supported).
 ## Password
 ## Possible values: Yes/No or blank to not set
 Enable_User   Yes
 ## Possible values: Yes/No
 Lan_Enable_IPMI_Msgs  Yes
 ## Possible values: Yes/No
 Lan_Enable_Link_Auth  No
 ## Possible values: Yes/No
 Lan_Enable_Restricted_to_Callback No
 ## Possible values:
 Callback/User/Operator/Administrator/OEM_Proprietary/No_Access
 Lan_Privilege_Limit   Administrator
 ## Possible values: 0-17, 0 is unlimited; May be reset to 0 if not
 specified
 ## Lan_Session_Limit
 EndSection
 Section User3
 ## Give Username
 Username  OAtmp1322558051
 ## Give password or blank to clear. MAX 16 chars (20 chars if IPMI 2.0
 supported).
 ## Password
 ## Possible values: Yes/No or blank to not set
 Enable_User   Yes
 ## Possible values: Yes/No
 Lan_Enable_IPMI_Msgs  Yes
 ## Possible values: Yes/No
 Lan_Enable_Link_Auth  No
 ## Possible values: Yes/No
 Lan_Enable_Restricted_to_Callback No
 ## Possible values:
 Callback/User/Operator/Administrator/OEM_Proprietary/No_Access
 Lan_Privilege_Limit   Administrator
 ## Possible values: 0-17, 0 is unlimited; May be reset to 0 if not
 specified
 ## Lan_Session_Limit
 EndSection
 Section User4
 ## Give Username
 Username  OAtmp1322568826
 ## Give password or blank to clear. MAX 16 chars (20 chars if IPMI 2.0
 supported).
 ## Password
 ## Possible values: Yes/No or blank to not set
 Enable_User   Yes
 ## Possible values: Yes/No
 Lan_Enable_IPMI_Msgs

Re: [Freeipmi-users] ipmi support with HP iLO2 servers initial success!

2012-02-01 Thread Al Chu 
Hi John,

Ok.  I guess my only other side comment is that the rmcpplus bad
status error means that the nagios plugin was telling ipmimonitoring to
use the IPMI 2.0 protocol and not the IPMI 1.5 protocol.

For what you're doing, the IPMI 2.0 protocol is probably not necessary.
Possibly it was a bad config somewhere.

Al

On Wed, 2012-02-01 at 00:37 -0800, john s. wrote:
 
 Hi erverybody 
 
 At the moment the nagios plugin from werner is running in an endless loop
 for 1 hour and sleep time 
 
 beetween the cues  is 1 second  so after 30 min... they're no errors
 occured ... so far 
 
 
 
 So my guess is that it  has sth to be with the nagios config  
 
 
 
 
 best regards 
 
 john s. 
 
 
 
 
 
 
-- 
Albert Chu
ch...@llnl.gov
Computer Scientist
High Performance Systems Division
Lawrence Livermore National Laboratory


___
Freeipmi-users mailing list
Freeipmi-users@gnu.org
https://lists.gnu.org/mailman/listinfo/freeipmi-users

Re: [Freeipmi-users] ipmi support with HP iLO2 servers initial success!

2012-02-01 Thread john s. 


okay .. now i have modified the nagios config and 2 of 3 ilos are  working
fine ..


so far so good  


 until to this point  thanks for help  



but with the third ilo  i've got another problem 

he says that the user name is invalid .. :

ipmi-sensors: username invalid

the third ilo2 has an other fw ( newer):

2.07   08/17/2011 

is it possible that the new firmware update has an lock up protection or sth
else 


how can i find it out ...


best regards 

john s. 

 


-- 
View this message in context: 
http://old.nabble.com/ipmi-support-with-HP-iLO2-servers-initial-success%21-tp29527071p33243839.html
Sent from the FreeIPMI - Users mailing list archive at Nabble.com.


___
Freeipmi-users mailing list
Freeipmi-users@gnu.org
https://lists.gnu.org/mailman/listinfo/freeipmi-users

Re: [Freeipmi-users] ipmi support with HP iLO2 servers initial success!

2012-01-31 Thread john s. 


Hello erverybody 

Software: 
ubuntu 10.04 
freeipmi  1.0.9

Hardware:
ilo2 fw: 2.05   12/16/2010 


I use freeipmi to check our ilo2 kvm  over nagios 

so far so good but , but in an intervall from 20 seconds there comes the
following error : 

ipmi_ctx_open_outofband_2_0: bad rmcpplus status code
- Execution of ipmimonitoring failed with return code 1.
- ipmimonitoring was executed with the following parameters:
/usr/local/sbin/ipmimonitoring -h 192.xxx.xx.xxx --config-file
/usr/local/etc/freeipmi/freeipmi.conf -g Temperature --quiet-cache
--sdr-cache-recreate



does anybody know what this error message means??


best regards 

john s. 




-- 
View this message in context: 
http://old.nabble.com/ipmi-support-with-HP-iLO2-servers-initial-success%21-tp29527071p33235060.html
Sent from the FreeIPMI - Users mailing list archive at Nabble.com.


___
Freeipmi-users mailing list
Freeipmi-users@gnu.org
https://lists.gnu.org/mailman/listinfo/freeipmi-users

Re: [Freeipmi-users] ipmi support with HP iLO2 servers initial success!

2012-01-31 Thread Werner Fischer 
Hi John,

it seems to me that you are using the IPMI monitoring plugin, and that
the ipmimonitoring script (which is executed by the plugin) causes this
error.

I don't know ipmi_ctx_open_outofband_2_0: bad rmcpplus status code in
detail, but maybe you get this, because you query the IPMI BMC too
often?

How often does the plugin query your server's IPMI BMC?
For further investigation you could try to execute ipmimonitoring with
the --debug option:

/usr/local/sbin/ipmimonitoring -h 192.xxx.xx.xxx --config-file 
/usr/local/etc/freeipmi/freeipmi.conf -g Temperature --quiet-cache --debug

best regards,
Werner

On Die, 2012-01-31 at 02:06 -0800, john s. wrote:
 
 Hello erverybody 
 
 Software: 
 ubuntu 10.04 
 freeipmi  1.0.9
 
 Hardware:
 ilo2 fw: 2.05   12/16/2010 
 
 
 I use freeipmi to check our ilo2 kvm  over nagios 
 
 so far so good but , but in an intervall from 20 seconds there comes the
 following error : 
 
   ipmi_ctx_open_outofband_2_0: bad rmcpplus status code
 - Execution of ipmimonitoring failed with return code 1.
 - ipmimonitoring was executed with the following parameters:
 /usr/local/sbin/ipmimonitoring -h 192.xxx.xx.xxx --config-file
 /usr/local/etc/freeipmi/freeipmi.conf -g Temperature --quiet-cache
 --sdr-cache-recreate
 
 
 
 does anybody know what this error message means??
 
 
 best regards 
 
 john s. 
 
 
 
 

-- 
: Werner Fischer
: Technology Specialist
: Thomas-Krenn.AG | The server-experts
: http://www.thomas-krenn.com | http://www.thomas-krenn.com/wiki


___
Freeipmi-users mailing list
Freeipmi-users@gnu.org
https://lists.gnu.org/mailman/listinfo/freeipmi-users

Re: [Freeipmi-users] ipmi support with HP iLO2 servers initial success!

2012-01-31 Thread john s. 


Hi Werner 

The plugin check the temperatures in an intervall of every 20 seconds 

is it to often?


and the debug oupt is posted here :
http://paste2.org/p/1889575 http://paste2.org/p/1889575 


could you have a fast look on  it ... 

cause i have  no idea what I have to  figure  out from  the log in order  to
solve  the problem 


best regards 

john s. 

 

-- 
View this message in context: 
http://old.nabble.com/ipmi-support-with-HP-iLO2-servers-initial-success%21-tp29527071p33236403.html
Sent from the FreeIPMI - Users mailing list archive at Nabble.com.


___
Freeipmi-users mailing list
Freeipmi-users@gnu.org
https://lists.gnu.org/mailman/listinfo/freeipmi-users

Re: [Freeipmi-users] ipmi support with HP iLO2 servers initial success!

2012-01-31 Thread Al Chu 
Hi John,

Unfortunately, bad rmcpplus status code means it's an unexpected and
not-normal code (instead of bad username or bad password, which we
handle normally).

It does not appear the error occurs in this debug output.  Can you find
a case in which it does?

Al

On Tue, 2012-01-31 at 06:09 -0800, john s. wrote:
 
 Hi Werner 
 
 The plugin check the temperatures in an intervall of every 20 seconds 
 
 is it to often?
 
 
 and the debug oupt is posted here :
 http://paste2.org/p/1889575 http://paste2.org/p/1889575 
 
 
 could you have a fast look on  it ... 
 
 cause i have  no idea what I have to  figure  out from  the log in order  to
 solve  the problem 
 
 
 best regards 
 
 john s. 
 
  
 
-- 
Albert Chu
ch...@llnl.gov
Computer Scientist
High Performance Systems Division
Lawrence Livermore National Laboratory


___
Freeipmi-users mailing list
Freeipmi-users@gnu.org
https://lists.gnu.org/mailman/listinfo/freeipmi-users

Re: [Freeipmi-users] ipmi support with HP iLO2 servers initial success!

2011-12-08 Thread john s. 


Hello Al 

thnx for help ... 


best regards 

john s. 



-- 
View this message in context: 
http://old.nabble.com/ipmi-support-with-HP-iLO2-servers-initial-success%21-tp29527071p32933719.html
Sent from the FreeIPMI - Users mailing list archive at Nabble.com.


___
Freeipmi-users mailing list
Freeipmi-users@gnu.org
https://lists.gnu.org/mailman/listinfo/freeipmi-users

Re: [Freeipmi-users] ipmi support with HP iLO2 servers initial success!

2011-12-07 Thread john s. 


Hello Everybody 

Sorry for digging out this thread but i can't find  no other (newer) post
which is similar to this one ...

If it does work, then there is a bug.  Perhaps you can send me a --debug
output and we can take a look to figure out what the bug is. 

command :

ipmipower -h cut0iogw1-ilo -D LAN_2_0 -s 



so  is it  still a bug or is it the normal behaviour on hp ilo connects?


best regards 

john s. 




-- 
View this message in context: 
http://old.nabble.com/ipmi-support-with-HP-iLO2-servers-initial-success%21-tp29527071p32928090.html
Sent from the FreeIPMI - Users mailing list archive at Nabble.com.


___
Freeipmi-users mailing list
Freeipmi-users@gnu.org
https://lists.gnu.org/mailman/listinfo/freeipmi-users

Re: [Freeipmi-users] ipmi support with HP iLO2 servers initial success!

2011-12-07 Thread Albert Chu 
Hi John,

The short answer is there are a number of bugs in the HP iLO firmware.
But some combination of options and/or workaround flags will get around
them and allow you to use FreeIPMI w/ HP iLO.  (Assuming no firmware
fixes have occurred since this thread.)  See the manpage for a list of
workarounds.

My recollection is a lot of HP iLO machines do not support IPMI 1.5,
only IPMI 2.0, so you'll have to use -D=LAN_2_0 to use IPMI 2.0.

Al

On Wed, 2011-12-07 at 01:36 -0800, john s. wrote:
 
 Hello Everybody 
 
 Sorry for digging out this thread but i can't find  no other (newer) post
 which is similar to this one ...
 
 If it does work, then there is a bug.  Perhaps you can send me a --debug
 output and we can take a look to figure out what the bug is. 
 
 command :
 
 ipmipower -h cut0iogw1-ilo -D LAN_2_0 -s 
 
 
 
 so  is it  still a bug or is it the normal behaviour on hp ilo connects?
 
 
 best regards 
 
 john s. 
 
 
 
 
-- 
Albert Chu
ch...@llnl.gov
Computer Scientist
High Performance Systems Division
Lawrence Livermore National Laboratory



___
Freeipmi-users mailing list
Freeipmi-users@gnu.org
https://lists.gnu.org/mailman/listinfo/freeipmi-users

[Freeipmi-users] ipmi support with HP iLO2 servers initial success!

2010-08-24 Thread Christopher Maestas 
Hello,

With the recent update of the 2.00 iLO2 firmware, we can now support:


   - IPMI over LAN functionality. The IPMI 2.0 RMCP+ (or Linux ipmitool
   lanplus) protocol is supported with this release.
   - IPMI Serial Over LAN (SOL)
   - Data Center Manageability Interface (DCMI) v1.0 specification
   - Enhanced the in band Intelligent Platform Management Interface (IPMI)
   to comply with the IPMI specification version 2.0

I've been able to use ipmitool to test this successfully (power, SOL and
sensor gathering).  Here's what I do with ipmitool:
---
# rpm -q ipmitool
ipmitool-1.8.11-1
# ipmitool -I lanplus -H cut0iogw1-ilo -U USER -P PASS power status
Chassis Power is off
# ipmitool -I lanplus -H cut0iogw1-ilo -U USER -P PASS power on
Chassis Power Control: Up/On
# ipmitool -I lanplus -H cut0iogw1-ilo -U USER -P PASS power status
Chassis Power is on
---

For freeipmi (ipmipower) I found the following combination worked:
---
# ipmipower -h cut0iogw1-ilo -s
cut0iogw1-ilo: authentication type unavailable for attempted privilege level
# ipmipower -h cut0iogw1-ilo -D LAN_2_0 -s
cut0iogw1-ilo: on
# ipmipower -h cut0iogw1-ilo -D LAN_2_0 -f
cut0iogw1-ilo: ok
# ipmipower -h cut0iogw1-ilo -D LAN_2_0 -s
cut0iogw1-ilo: off
# ipmipower -h cut0iogw1-ilo -D LAN_2_0 -n
cut0iogw1-ilo: ok
# ipmipower -h cut0iogw1-ilo -D LAN_2_0 -s
cut0iogw1-ilo: on
---

I set the following in /etc/freeipmi.conf:
---
driver-type LAN_2_0
---

and it seems to work ok for the lo100 and ilo2 servers just fine.
---
# ipmipower -h cut0iogw1-ilo  -s
cut0iogw1-ilo: on
# ipmipower -h cut0admin1-lo  -s
cut0admin1-lo: on
---

I figure there may be other functional tests for ipmi compliance I can run
now that the initial flags have been worked around for freeipmi's ipmipower
command.  Then I figure on changing powerman/conman to use ipmi drivers for
ilo devices and see how that works.

Thanks,
-cdm
___
Freeipmi-users mailing list
Freeipmi-users@gnu.org
http://lists.gnu.org/mailman/listinfo/freeipmi-users

Re: [Freeipmi-users] ipmi support with HP iLO2 servers initial success!

2010-08-24 Thread Albert Chu 
Hi Chris,

 For freeipmi (ipmipower) I found the following combination worked:
 ---
 # ipmipower -h cut0iogw1-ilo -s
 cut0iogw1-ilo: authentication type unavailable for attempted privilege level

This isn't good.  It suggests that the HP firmware might be returning
bad/poor information in the Get Authentication Capabilities phase of
IPMI.  Does ipmipower work if you also specify the authcap workaround?
(-W authcap).

If it does work, then there is a bug.  Perhaps you can send me a --debug
output and we can take a look to figure out what the bug is.

Al

On Tue, 2010-08-24 at 15:29 -0700, Christopher Maestas wrote:
 Hello,
 
 With the recent update of the 2.00 iLO2 firmware, we can now support:
 
 
- IPMI over LAN functionality. The IPMI 2.0 RMCP+ (or Linux ipmitool
lanplus) protocol is supported with this release.
- IPMI Serial Over LAN (SOL)
- Data Center Manageability Interface (DCMI) v1.0 specification
- Enhanced the in band Intelligent Platform Management Interface (IPMI)
to comply with the IPMI specification version 2.0
 
 I've been able to use ipmitool to test this successfully (power, SOL and
 sensor gathering).  Here's what I do with ipmitool:
 ---
 # rpm -q ipmitool
 ipmitool-1.8.11-1
 # ipmitool -I lanplus -H cut0iogw1-ilo -U USER -P PASS power status
 Chassis Power is off
 # ipmitool -I lanplus -H cut0iogw1-ilo -U USER -P PASS power on
 Chassis Power Control: Up/On
 # ipmitool -I lanplus -H cut0iogw1-ilo -U USER -P PASS power status
 Chassis Power is on
 ---
 
 For freeipmi (ipmipower) I found the following combination worked:
 ---
 # ipmipower -h cut0iogw1-ilo -s
 cut0iogw1-ilo: authentication type unavailable for attempted privilege level
 # ipmipower -h cut0iogw1-ilo -D LAN_2_0 -s
 cut0iogw1-ilo: on
 # ipmipower -h cut0iogw1-ilo -D LAN_2_0 -f
 cut0iogw1-ilo: ok
 # ipmipower -h cut0iogw1-ilo -D LAN_2_0 -s
 cut0iogw1-ilo: off
 # ipmipower -h cut0iogw1-ilo -D LAN_2_0 -n
 cut0iogw1-ilo: ok
 # ipmipower -h cut0iogw1-ilo -D LAN_2_0 -s
 cut0iogw1-ilo: on
 ---
 
 I set the following in /etc/freeipmi.conf:
 ---
 driver-type LAN_2_0
 ---
 
 and it seems to work ok for the lo100 and ilo2 servers just fine.
 ---
 # ipmipower -h cut0iogw1-ilo  -s
 cut0iogw1-ilo: on
 # ipmipower -h cut0admin1-lo  -s
 cut0admin1-lo: on
 ---
 
 I figure there may be other functional tests for ipmi compliance I can run
 now that the initial flags have been worked around for freeipmi's ipmipower
 command.  Then I figure on changing powerman/conman to use ipmi drivers for
 ilo devices and see how that works.
 
 Thanks,
 -cdm
 ___
 Freeipmi-users mailing list
 Freeipmi-users@gnu.org
 http://*lists.gnu.org/mailman/listinfo/freeipmi-users
 
-- 
Albert Chu
ch...@llnl.gov
Computer Scientist
High Performance Systems Division
Lawrence Livermore National Laboratory


___
Freeipmi-users mailing list
Freeipmi-users@gnu.org
http://lists.gnu.org/mailman/listinfo/freeipmi-users

Re: [Freeipmi-users] ipmi support with HP iLO2 servers initial success!

2010-08-24 Thread Christopher Maestas 
Al,

I'm sorry I should have tagged that first case of using ipmipower as an
error.  Once I added -D LAN_2_0  things worked great.  I think I also
figured out the freeipmi.conf parameter (driver-type LAN_2_0) to change to
make it work by default and still talk to lo100 and iLO devices without any
issue at first glance

Things are running fine now.  I will continue to do some more testing
tomorrow with SOL, sensor gatherings.  In addition I will try and report
back on conman/powerman using their ipmi drivers work against the iLO server
as well.

Finally I will try and take a look at some tests specified here:

http://www.gnu.org/software/freeipmi/freeipmi-testing.txt

and report back.

-cdm

On Tue, Aug 24, 2010 at 5:11 PM, Albert Chu ch...@llnl.gov wrote:

 Hi Chris,

  For freeipmi (ipmipower) I found the following combination worked:
  ---
  # ipmipower -h cut0iogw1-ilo -s
  cut0iogw1-ilo: authentication type unavailable for attempted privilege
 level

 This isn't good.  It suggests that the HP firmware might be returning
 bad/poor information in the Get Authentication Capabilities phase of
 IPMI.  Does ipmipower work if you also specify the authcap workaround?
 (-W authcap).

 If it does work, then there is a bug.  Perhaps you can send me a --debug
 output and we can take a look to figure out what the bug is.

 Al

 On Tue, 2010-08-24 at 15:29 -0700, Christopher Maestas wrote:
  Hello,
 
  With the recent update of the 2.00 iLO2 firmware, we can now support:
 
 
 - IPMI over LAN functionality. The IPMI 2.0 RMCP+ (or Linux ipmitool
 lanplus) protocol is supported with this release.
 - IPMI Serial Over LAN (SOL)
 - Data Center Manageability Interface (DCMI) v1.0 specification
 - Enhanced the in band Intelligent Platform Management Interface
 (IPMI)
 to comply with the IPMI specification version 2.0
 
  I've been able to use ipmitool to test this successfully (power, SOL and
  sensor gathering).  Here's what I do with ipmitool:
  ---
  # rpm -q ipmitool
  ipmitool-1.8.11-1
  # ipmitool -I lanplus -H cut0iogw1-ilo -U USER -P PASS power status
  Chassis Power is off
  # ipmitool -I lanplus -H cut0iogw1-ilo -U USER -P PASS power on
  Chassis Power Control: Up/On
  # ipmitool -I lanplus -H cut0iogw1-ilo -U USER -P PASS power status
  Chassis Power is on
  ---
 
  For freeipmi (ipmipower) I found the following combination worked:
  ---
  # ipmipower -h cut0iogw1-ilo -s
  cut0iogw1-ilo: authentication type unavailable for attempted privilege
 level
  # ipmipower -h cut0iogw1-ilo -D LAN_2_0 -s
  cut0iogw1-ilo: on
  # ipmipower -h cut0iogw1-ilo -D LAN_2_0 -f
  cut0iogw1-ilo: ok
  # ipmipower -h cut0iogw1-ilo -D LAN_2_0 -s
  cut0iogw1-ilo: off
  # ipmipower -h cut0iogw1-ilo -D LAN_2_0 -n
  cut0iogw1-ilo: ok
  # ipmipower -h cut0iogw1-ilo -D LAN_2_0 -s
  cut0iogw1-ilo: on
  ---
 
  I set the following in /etc/freeipmi.conf:
  ---
  driver-type LAN_2_0
  ---
 
  and it seems to work ok for the lo100 and ilo2 servers just fine.
  ---
  # ipmipower -h cut0iogw1-ilo  -s
  cut0iogw1-ilo: on
  # ipmipower -h cut0admin1-lo  -s
  cut0admin1-lo: on
  ---
 
  I figure there may be other functional tests for ipmi compliance I can
 run
  now that the initial flags have been worked around for freeipmi's
 ipmipower
  command.  Then I figure on changing powerman/conman to use ipmi drivers
 for
  ilo devices and see how that works.
 
  Thanks,
  -cdm
  ___
  Freeipmi-users mailing list
  Freeipmi-users@gnu.org
  http://*lists.gnu.org/mailman/listinfo/freeipmi-users
 
 --
 Albert Chu
 ch...@llnl.gov
 Computer Scientist
 High Performance Systems Division
 Lawrence Livermore National Laboratory


___
Freeipmi-users mailing list
Freeipmi-users@gnu.org
http://lists.gnu.org/mailman/listinfo/freeipmi-users