|
»
»
"authentication type unavailable for attempted privilege level" with Intel S5000PAL Mainboard
|
View:
New views
12 Messages
—
Rating Filter:
Alert me
|
 |
"authentication type unavailable for attempted privilege level" with Intel S5000PAL Mainboard
by Werner Fischer-2
::
Rate this Message:
Dear freeipmi users/developers,
I'm trying to monitor an Intel SR2500 server (this server has the Intel S5000PAL mainboard in it). While I can monitor it using ipmitool, I keep getting errors with ipmimonitoring from freeipmi. Also using the "-W" parameter for workarounds (as described in the manpage of ipmimonitoring) doesn't help: -------------------------------------------------------------------------- [root@tpw ~]# ipmitool -I lan -H 192.168.1.211 -U admin -P relation sdr BB +1.2V Vtt | 1.20 Volts | ok BB +1.5V AUX | 1.47 Volts | ok BB +1.5V | 1.48 Volts | ok BB +1.8V | 1.79 Volts | ok BB +3.3V | 3.35 Volts | ok BB +3.3V STB | 3.35 Volts | ok ^C [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation ipmi_monitoring_sensor_readings_by_record_id: authentication type unavailable for attempted privilege level [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation ipmi_monitoring_sensor_readings_by_record_id: authentication type unavailable for attempted privilege level [root@tpw ~]# rpm -q freeipmi freeipmi-0.5.1-3.fc9.i386 [root@tpw ~]# -------------------------------------------------------------------------- I checked the manpage: "authentication type unavailable for attempted privilege level" - The authentication type you wish to authenticate with is not available for this privilege level. Please try again with an alternate authentication type or alternate privilege level. It may also be possible the available authenti- cation types you can authenticate with are not correctly configured on the remote BMC. But the settings at the BMC side seem to be ok: -------------------------------------------------------------------------- [root@tpw ~]# ipmitool -I lan -H 192.168.1.211 -U admin -P relation lan print 1 Set in Progress : Set Complete Auth Type Support : NONE MD5 PASSWORD Auth Type Enable : Callback : : User : : Operator : : Admin : MD5 PASSWORD : OEM : IP Address Source : Static Address IP Address : 192.168.1.211 Subnet Mask : 255.255.255.0 MAC Address : 00:0e:0c:ea:92:a2 [...] [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -a MD5 -u admin -p relation ipmimonitoring: authentication type unavailable for attempted privilege level [root@tpw ~]# -------------------------------------------------------------------------- Also compiling the newest version and using it does not help: -------------------------------------------------------------------------- [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation ipmimonitoring: authentication type unavailable for attempted privilege level [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation ipmimonitoring: authentication type unavailable for attempted privilege level [root@tpw ~]# rpm -q freeipmi freeipmi-0.7.11-1.fc9.i386 [root@tpw ~]# -------------------------------------------------------------------------- In contrast, monitoring a system with a new Supermicro X8DT3-F mainboard works fine with freeipmi-0.5.1-3.fc9.i386 and also with freeipmi-0.7.11-1.fc9.i386: -------------------------------------------------------------------------- [root@tpw ~]# ipmitool -I lan -H 10.10.10.233 -U ADMIN -P ADMIN sdr CPU1 Temp | 0 unspecified | ok CPU2 Temp | no reading | ns System Temp | 45 degrees C | ok CPU1 Vcore | 0.98 Volts | ok CPU2 Vcore | no reading | ns CPU1 DIMM | 1.51 Volts | ok CPU2 DIMM | no reading | ns ^C [root@tpw ~]# ipmimonitoring -h 10.10.10.233 -u ADMIN -p ADMIN Record_ID | Sensor Name | Sensor Group | Monitoring Status| Sensor Units | Sensor Reading 4 | System Temp | Temperature | Nominal | C | 45.000000 5 | CPU1 Vcore | Voltage | Nominal | V | 0.976000 6 | CPU2 Vcore | Voltage | Nominal | V | 0.000000 7 | CPU1 DIMM | Voltage | Nominal | V | 1.512000 8 | CPU2 DIMM | Voltage | Nominal | V | 0.000000 9 | +1.5V | Voltage | Nominal | V | 1.504000 10 | +3.3V | Voltage | Nominal | V | 3.240000 11 | +3.3VSB | Voltage | Nominal | V | 3.240000 12 | +5V | Voltage | Nominal | V | 5.120000 13 | +12V | Voltage | Nominal | V | 12.190000 14 | VBAT | Voltage | Nominal | V | 3.240000 15 | Fan1 | Fan | Nominal | RPM | 6528.000000 16 | Fan2 | Fan | Nominal | RPM | 7072.000000 17 | Fan3 | Fan | Nominal | RPM | 0.000000 18 | Fan4 | Fan | Nominal | RPM | 0.000000 19 | Fan5 | Fan | Nominal | RPM | 5644.000000 20 | Fan6 | Fan | Nominal | RPM | 5304.000000 21 | Fan7 | Fan | Nominal | RPM | 7072.000000 22 | Fan8 | Fan | Nominal | RPM | 0.000000 23 | Intrusion | Physical Security | Nominal | N/A | '' 24 | PS Failure | Power Supply | Nominal | N/A | '' [root@tpw ~]# -------------------------------------------------------------------------- Does anybody have an idea how this problem could be fixed? best regards, Werner _______________________________________________ Freeipmi-users mailing list Freeipmi-users@... http://lists.gnu.org/mailman/listinfo/freeipmi-users |
|
|
Re: "authentication type unavailable for attempted privilege level" with Intel S5000PAL Mainboard
by Al Chu11
::
Rate this Message:
Hi Werner,
It's possible the motherboard is not reporting supported authentication types correctly. You could give the "authcap" workaround a shot. However, if this is being non-compliant in the way that I think it is, the "authcap" workaround won't work (b/c it currently handles a different non-compliance bug). Could you send me the output from --debug? If we can verify the issue, I'll implement a new workaround for you. BTW, if you need the intel20 workarounds for IPMI 2.0, you may need to upgrade. There were some bugs found a few releases ago. 0.7.4 - 12/15/08 ---------------- <snip> o Fix Intel IPMI 2.0 workarounds in all tools/libraries. <snip> Al On Wed, 2009-08-19 at 14:16 +0200, Werner Fischer wrote: > Dear freeipmi users/developers, > > I'm trying to monitor an Intel SR2500 server (this server has the Intel > S5000PAL mainboard in it). > > While I can monitor it using ipmitool, I keep getting errors with > ipmimonitoring from freeipmi. Also using the "-W" parameter for > workarounds (as described in the manpage of ipmimonitoring) doesn't > help: > > -------------------------------------------------------------------------- > [root@tpw ~]# ipmitool -I lan -H 192.168.1.211 -U admin -P relation sdr > BB +1.2V Vtt | 1.20 Volts | ok > BB +1.5V AUX | 1.47 Volts | ok > BB +1.5V | 1.48 Volts | ok > BB +1.8V | 1.79 Volts | ok > BB +3.3V | 3.35 Volts | ok > BB +3.3V STB | 3.35 Volts | ok > ^C > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > ipmi_monitoring_sensor_readings_by_record_id: authentication type unavailable for attempted privilege level > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > ipmi_monitoring_sensor_readings_by_record_id: authentication type unavailable for attempted privilege level > [root@tpw ~]# rpm -q freeipmi > freeipmi-0.5.1-3.fc9.i386 > [root@tpw ~]# > -------------------------------------------------------------------------- > > I checked the manpage: > "authentication type unavailable for attempted privilege level" - The authentication type you wish > to authenticate with is not available for this privilege level. Please try again with an alternate > authentication type or alternate privilege level. It may also be possible the available authenti- > cation types you can authenticate with are not correctly configured on the remote BMC. > But the settings at the BMC side seem to be ok: > > -------------------------------------------------------------------------- > [root@tpw ~]# ipmitool -I lan -H 192.168.1.211 -U admin -P relation lan print 1 > Set in Progress : Set Complete > Auth Type Support : NONE MD5 PASSWORD > Auth Type Enable : Callback : > : User : > : Operator : > : Admin : MD5 PASSWORD > : OEM : > IP Address Source : Static Address > IP Address : 192.168.1.211 > Subnet Mask : 255.255.255.0 > MAC Address : 00:0e:0c:ea:92:a2 > [...] > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -a MD5 -u admin -p relation > ipmimonitoring: authentication type unavailable for attempted privilege level > [root@tpw ~]# > -------------------------------------------------------------------------- > > Also compiling the newest version and using it does not help: > -------------------------------------------------------------------------- > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > ipmimonitoring: authentication type unavailable for attempted privilege level > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > ipmimonitoring: authentication type unavailable for attempted privilege level > [root@tpw ~]# rpm -q freeipmi > freeipmi-0.7.11-1.fc9.i386 > [root@tpw ~]# > -------------------------------------------------------------------------- > > In contrast, monitoring a system with a new Supermicro X8DT3-F mainboard > works fine with freeipmi-0.5.1-3.fc9.i386 and also with > freeipmi-0.7.11-1.fc9.i386: > > -------------------------------------------------------------------------- > [root@tpw ~]# ipmitool -I lan -H 10.10.10.233 -U ADMIN -P ADMIN sdr > CPU1 Temp | 0 unspecified | ok > CPU2 Temp | no reading | ns > System Temp | 45 degrees C | ok > CPU1 Vcore | 0.98 Volts | ok > CPU2 Vcore | no reading | ns > CPU1 DIMM | 1.51 Volts | ok > CPU2 DIMM | no reading | ns > ^C > [root@tpw ~]# ipmimonitoring -h 10.10.10.233 -u ADMIN -p ADMIN > Record_ID | Sensor Name | Sensor Group | Monitoring Status| Sensor Units | Sensor Reading > 4 | System Temp | Temperature | Nominal | C | 45.000000 > 5 | CPU1 Vcore | Voltage | Nominal | V | 0.976000 > 6 | CPU2 Vcore | Voltage | Nominal | V | 0.000000 > 7 | CPU1 DIMM | Voltage | Nominal | V | 1.512000 > 8 | CPU2 DIMM | Voltage | Nominal | V | 0.000000 > 9 | +1.5V | Voltage | Nominal | V | 1.504000 > 10 | +3.3V | Voltage | Nominal | V | 3.240000 > 11 | +3.3VSB | Voltage | Nominal | V | 3.240000 > 12 | +5V | Voltage | Nominal | V | 5.120000 > 13 | +12V | Voltage | Nominal | V | 12.190000 > 14 | VBAT | Voltage | Nominal | V | 3.240000 > 15 | Fan1 | Fan | Nominal | RPM | 6528.000000 > 16 | Fan2 | Fan | Nominal | RPM | 7072.000000 > 17 | Fan3 | Fan | Nominal | RPM | 0.000000 > 18 | Fan4 | Fan | Nominal | RPM | 0.000000 > 19 | Fan5 | Fan | Nominal | RPM | 5644.000000 > 20 | Fan6 | Fan | Nominal | RPM | 5304.000000 > 21 | Fan7 | Fan | Nominal | RPM | 7072.000000 > 22 | Fan8 | Fan | Nominal | RPM | 0.000000 > 23 | Intrusion | Physical Security | Nominal | N/A | '' > 24 | PS Failure | Power Supply | Nominal | N/A | '' > [root@tpw ~]# > -------------------------------------------------------------------------- > > Does anybody have an idea how this problem could be fixed? > > best regards, > Werner > > > > _______________________________________________ > Freeipmi-users mailing list > Freeipmi-users@... > http://*lists.gnu.org/mailman/listinfo/freeipmi-users > Albert Chu chu11@... Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory _______________________________________________ Freeipmi-users mailing list Freeipmi-users@... http://lists.gnu.org/mailman/listinfo/freeipmi-users |
|
|
Re: "authentication type unavailable for attempted privilege level" with Intel S5000PAL Mainboard
by Werner Fischer-2
::
Rate this Message:
Hi Al,
thanks for your fast answer. Below you find the requested debug output. I'm using version 0.7.11. The "authcap" workaround does not fix the problem. After executing with debug to the affected Intel S5000PAL system (IP 192.168.1.211) I again verified the correct behavior of ipmimonitoring to the other system (Supermicro) to IP 10.10.10.233. [root@tpw ~]# rpm -q freeipmi freeipmi-0.7.11-1.fc9.i386 [root@tpw ~]# ipmimonitoring -V ipmimonitoring - 0.7.11 Copyright (C) 2007-2008 Lawrence Livermore National Security, LLC. Copyright (C) 2006-2007 The Regents of the University of California. This program is free software; you may redistribute it under the terms of the GNU General Public License. This program has absolutely no warranty. [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation ipmimonitoring: authentication type unavailable for attempted privilege level [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation ipmimonitoring: authentication type unavailable for attempted privilege level [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="authcap" -u admin -p relation ipmimonitoring: authentication type unavailable for attempted privilege level [root@tpw ~]# ipmimonitoring -h 192.168.1.211 --debug -u admin -p relation 192.168.1.211: ===================================================== 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Request 192.168.1.211: ===================================================== 192.168.1.211: RMCP Header: 192.168.1.211: ------------ 192.168.1.211: [ 6h] = version[ 8b] 192.168.1.211: [ 0h] = reserved[ 8b] 192.168.1.211: [ FFh] = sequence_number[ 8b] 192.168.1.211: [ 7h] = message_class.class[ 5b] 192.168.1.211: [ 0h] = message_class.reserved[ 2b] 192.168.1.211: [ 0h] = message_class.ack[ 1b] 192.168.1.211: IPMI Session Header: 192.168.1.211: -------------------- 192.168.1.211: [ 0h] = authentication_type[ 8b] 192.168.1.211: [ 0h] = session_sequence_number[32b] 192.168.1.211: [ 0h] = session_id[32b] 192.168.1.211: [ 9h] = ipmi_msg_len[ 8b] 192.168.1.211: IPMI Message Header: 192.168.1.211: -------------------- 192.168.1.211: [ 20h] = rs_addr[ 8b] 192.168.1.211: [ 0h] = rs_lun[ 2b] 192.168.1.211: [ 6h] = net_fn[ 6b] 192.168.1.211: [ C8h] = checksum1[ 8b] 192.168.1.211: [ 81h] = rq_addr[ 8b] 192.168.1.211: [ 0h] = rq_lun[ 2b] 192.168.1.211: [ 8h] = rq_seq[ 6b] 192.168.1.211: IPMI Command Data: 192.168.1.211: ------------------ 192.168.1.211: [ 38h] = cmd[ 8b] 192.168.1.211: [ Eh] = channel_number[ 4b] 192.168.1.211: [ 0h] = reserved1[ 4b] 192.168.1.211: [ 3h] = maximum_privilege_level[ 4b] 192.168.1.211: [ 0h] = reserved2[ 4b] 192.168.1.211: IPMI Trailer: 192.168.1.211: -------------- 192.168.1.211: [ 16h] = checksum2[ 8b] 192.168.1.211: ===================================================== 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Response 192.168.1.211: ===================================================== 192.168.1.211: RMCP Header: 192.168.1.211: ------------ 192.168.1.211: [ 6h] = version[ 8b] 192.168.1.211: [ 0h] = reserved[ 8b] 192.168.1.211: [ FFh] = sequence_number[ 8b] 192.168.1.211: [ 7h] = message_class.class[ 5b] 192.168.1.211: [ 0h] = message_class.reserved[ 2b] 192.168.1.211: [ 0h] = message_class.ack[ 1b] 192.168.1.211: IPMI Session Header: 192.168.1.211: -------------------- 192.168.1.211: [ 0h] = authentication_type[ 8b] 192.168.1.211: [ 0h] = session_sequence_number[32b] 192.168.1.211: [ 0h] = session_id[32b] 192.168.1.211: [ 10h] = ipmi_msg_len[ 8b] 192.168.1.211: IPMI Message Header: 192.168.1.211: -------------------- 192.168.1.211: [ 81h] = rq_addr[ 8b] 192.168.1.211: [ 0h] = rq_lun[ 2b] 192.168.1.211: [ 7h] = net_fn[ 6b] 192.168.1.211: [ 63h] = checksum1[ 8b] 192.168.1.211: [ 20h] = rs_addr[ 8b] 192.168.1.211: [ 0h] = rs_lun[ 2b] 192.168.1.211: [ 8h] = rq_seq[ 6b] 192.168.1.211: IPMI Command Data: 192.168.1.211: ------------------ 192.168.1.211: [ 38h] = cmd[ 8b] 192.168.1.211: [ 0h] = comp_code[ 8b] 192.168.1.211: [ 1h] = channel_number[ 8b] 192.168.1.211: [ 0h] = authentication_type.none[ 1b] 192.168.1.211: [ 0h] = authentication_type.md2[ 1b] 192.168.1.211: [ 0h] = authentication_type.md5[ 1b] 192.168.1.211: [ 0h] = authentication_type.reserved1[ 1b] 192.168.1.211: [ 0h] = authentication_type.straight_password_key[ 1b] 192.168.1.211: [ 0h] = authentication_type.oem_prop[ 1b] 192.168.1.211: [ 0h] = authentication_type.reserved2[ 2b] 192.168.1.211: [ 0h] = authentication_status.anonymous_login[ 1b] 192.168.1.211: [ 0h] = authentication_status.null_username[ 1b] 192.168.1.211: [ 1h] = authentication_status.non_null_username[ 1b] 192.168.1.211: [ 0h] = authentication_status.user_level_authentication[ 1b] 192.168.1.211: [ 0h] = authentication_status.per_message_authentication[ 1b] 192.168.1.211: [ 0h] = authentication_status.reserved[ 3b] 192.168.1.211: [ 0h] = reserved1[ 8b] 192.168.1.211: [ 0h] = oem_id[24b] 192.168.1.211: [ 0h] = oem_auxiliary_data[ 8b] 192.168.1.211: IPMI Trailer: 192.168.1.211: -------------- 192.168.1.211: [ 83h] = checksum2[ 8b] ipmimonitoring: authentication type unavailable for attempted privilege level [root@tpw ~]# [root@tpw ~]# [root@tpw ~]# [root@tpw ~]# ipmimonitoring -h 10.10.10.233 -u ADMIN -p ADMIN Record_ID | Sensor Name | Sensor Group | Monitoring Status| Sensor Units | Sensor Reading 4 | System Temp | Temperature | Nominal | C | 41.000000 5 | CPU1 Vcore | Voltage | Nominal | V | 0.976000 7 | CPU1 DIMM | Voltage | Nominal | V | 1.512000 9 | +1.5V | Voltage | Nominal | V | 1.504000 10 | +3.3V | Voltage | Nominal | V | 3.240000 11 | +3.3VSB | Voltage | Nominal | V | 3.240000 12 | +5V | Voltage | Nominal | V | 5.120000 13 | +12V | Voltage | Nominal | V | 12.190000 14 | VBAT | Voltage | Nominal | V | 3.216000 15 | Fan1 | Fan | Nominal | RPM | 3264.000000 16 | Fan2 | Fan | Nominal | RPM | 3536.000000 19 | Fan5 | Fan | Nominal | RPM | 2788.000000 20 | Fan6 | Fan | Nominal | RPM | 2652.000000 21 | Fan7 | Fan | Nominal | RPM | 3536.000000 23 | Intrusion | Physical Security | Nominal | N/A | 'OK' 24 | PS Failure | Power Supply | Nominal | N/A | 'OK' [root@tpw ~]# Werner On Wed, 2009-08-19 at 08:58 -0700, Al Chu wrote: > Hi Werner, > > It's possible the motherboard is not reporting supported authentication > types correctly. You could give the "authcap" workaround a shot. > However, if this is being non-compliant in the way that I think it is, > the "authcap" workaround won't work (b/c it currently handles a > different non-compliance bug). Could you send me the output from > --debug? If we can verify the issue, I'll implement a new workaround > for you. > > BTW, if you need the intel20 workarounds for IPMI 2.0, you may need to > upgrade. There were some bugs found a few releases ago. > > 0.7.4 - 12/15/08 > ---------------- > <snip> > o Fix Intel IPMI 2.0 workarounds in all tools/libraries. > <snip> > > Al > > On Wed, 2009-08-19 at 14:16 +0200, Werner Fischer wrote: > > Dear freeipmi users/developers, > > > > I'm trying to monitor an Intel SR2500 server (this server has the Intel > > S5000PAL mainboard in it). > > > > While I can monitor it using ipmitool, I keep getting errors with > > ipmimonitoring from freeipmi. Also using the "-W" parameter for > > workarounds (as described in the manpage of ipmimonitoring) doesn't > > help: > > > > -------------------------------------------------------------------------- > > [root@tpw ~]# ipmitool -I lan -H 192.168.1.211 -U admin -P relation sdr > > BB +1.2V Vtt | 1.20 Volts | ok > > BB +1.5V AUX | 1.47 Volts | ok > > BB +1.5V | 1.48 Volts | ok > > BB +1.8V | 1.79 Volts | ok > > BB +3.3V | 3.35 Volts | ok > > BB +3.3V STB | 3.35 Volts | ok > > ^C > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > > ipmi_monitoring_sensor_readings_by_record_id: authentication type unavailable for attempted privilege level > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > > ipmi_monitoring_sensor_readings_by_record_id: authentication type unavailable for attempted privilege level > > [root@tpw ~]# rpm -q freeipmi > > freeipmi-0.5.1-3.fc9.i386 > > [root@tpw ~]# > > -------------------------------------------------------------------------- > > > > I checked the manpage: > > "authentication type unavailable for attempted privilege level" - The authentication type you wish > > to authenticate with is not available for this privilege level. Please try again with an alternate > > authentication type or alternate privilege level. It may also be possible the available authenti- > > cation types you can authenticate with are not correctly configured on the remote BMC. > > But the settings at the BMC side seem to be ok: > > > > -------------------------------------------------------------------------- > > [root@tpw ~]# ipmitool -I lan -H 192.168.1.211 -U admin -P relation lan print 1 > > Set in Progress : Set Complete > > Auth Type Support : NONE MD5 PASSWORD > > Auth Type Enable : Callback : > > : User : > > : Operator : > > : Admin : MD5 PASSWORD > > : OEM : > > IP Address Source : Static Address > > IP Address : 192.168.1.211 > > Subnet Mask : 255.255.255.0 > > MAC Address : 00:0e:0c:ea:92:a2 > > [...] > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -a MD5 -u admin -p relation > > ipmimonitoring: authentication type unavailable for attempted privilege level > > [root@tpw ~]# > > -------------------------------------------------------------------------- > > > > Also compiling the newest version and using it does not help: > > -------------------------------------------------------------------------- > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > > ipmimonitoring: authentication type unavailable for attempted privilege level > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > > ipmimonitoring: authentication type unavailable for attempted privilege level > > [root@tpw ~]# rpm -q freeipmi > > freeipmi-0.7.11-1.fc9.i386 > > [root@tpw ~]# > > -------------------------------------------------------------------------- > > > > In contrast, monitoring a system with a new Supermicro X8DT3-F mainboard > > works fine with freeipmi-0.5.1-3.fc9.i386 and also with > > freeipmi-0.7.11-1.fc9.i386: > > > > -------------------------------------------------------------------------- > > [root@tpw ~]# ipmitool -I lan -H 10.10.10.233 -U ADMIN -P ADMIN sdr > > CPU1 Temp | 0 unspecified | ok > > CPU2 Temp | no reading | ns > > System Temp | 45 degrees C | ok > > CPU1 Vcore | 0.98 Volts | ok > > CPU2 Vcore | no reading | ns > > CPU1 DIMM | 1.51 Volts | ok > > CPU2 DIMM | no reading | ns > > ^C > > [root@tpw ~]# ipmimonitoring -h 10.10.10.233 -u ADMIN -p ADMIN > > Record_ID | Sensor Name | Sensor Group | Monitoring Status| Sensor Units | Sensor Reading > > 4 | System Temp | Temperature | Nominal | C | 45.000000 > > 5 | CPU1 Vcore | Voltage | Nominal | V | 0.976000 > > 6 | CPU2 Vcore | Voltage | Nominal | V | 0.000000 > > 7 | CPU1 DIMM | Voltage | Nominal | V | 1.512000 > > 8 | CPU2 DIMM | Voltage | Nominal | V | 0.000000 > > 9 | +1.5V | Voltage | Nominal | V | 1.504000 > > 10 | +3.3V | Voltage | Nominal | V | 3.240000 > > 11 | +3.3VSB | Voltage | Nominal | V | 3.240000 > > 12 | +5V | Voltage | Nominal | V | 5.120000 > > 13 | +12V | Voltage | Nominal | V | 12.190000 > > 14 | VBAT | Voltage | Nominal | V | 3.240000 > > 15 | Fan1 | Fan | Nominal | RPM | 6528.000000 > > 16 | Fan2 | Fan | Nominal | RPM | 7072.000000 > > 17 | Fan3 | Fan | Nominal | RPM | 0.000000 > > 18 | Fan4 | Fan | Nominal | RPM | 0.000000 > > 19 | Fan5 | Fan | Nominal | RPM | 5644.000000 > > 20 | Fan6 | Fan | Nominal | RPM | 5304.000000 > > 21 | Fan7 | Fan | Nominal | RPM | 7072.000000 > > 22 | Fan8 | Fan | Nominal | RPM | 0.000000 > > 23 | Intrusion | Physical Security | Nominal | N/A | '' > > 24 | PS Failure | Power Supply | Nominal | N/A | '' > > [root@tpw ~]# > > -------------------------------------------------------------------------- > > > > Does anybody have an idea how this problem could be fixed? > > > > best regards, > > Werner > > > > > > > > _______________________________________________ > > Freeipmi-users mailing list > > Freeipmi-users@... > > http://*lists.gnu.org/mailman/listinfo/freeipmi-users > > _______________________________________________ Freeipmi-users mailing list Freeipmi-users@... http://lists.gnu.org/mailman/listinfo/freeipmi-users |
|
|
Re: "authentication type unavailable for attempted privilege level" with Intel S5000PAL Mainboard
by Al Chu11
::
Rate this Message:
Hi Werner,
> 192.168.1.211: [ 0h] = authentication_type.none[ 1b] > 192.168.1.211: [ 0h] = authentication_type.md2[ 1b] > 192.168.1.211: [ 0h] = authentication_type.md5[ 1b] > 192.168.1.211: [ 0h] = authentication_type.reserved1[ 1b] > 192.168.1.211: [ 0h] = authentication_type.straight_password_key[ 1b] > 192.168.1.211: [ 0h] = authentication_type.oem_prop[ 1b] This indicates that no authentication support is enabled, which is very unlikely of being true (which we could verify via 'bmc-config --checkout --section=lan_conf_auth'). I'll modify the 'authcap' workaround to also encompass this case and post a beta tar.gz for you to check out. Al On Fri, 2009-08-21 at 09:58 +0200, Werner Fischer wrote: > Hi Al, > > thanks for your fast answer. > > Below you find the requested debug output. I'm using version 0.7.11. The > "authcap" workaround does not fix the problem. After executing with > debug to the affected Intel S5000PAL system (IP 192.168.1.211) I again > verified the correct behavior of ipmimonitoring to the other system > (Supermicro) to IP 10.10.10.233. > > [root@tpw ~]# rpm -q freeipmi > freeipmi-0.7.11-1.fc9.i386 > [root@tpw ~]# ipmimonitoring -V > ipmimonitoring - 0.7.11 > Copyright (C) 2007-2008 Lawrence Livermore National Security, LLC. > Copyright (C) 2006-2007 The Regents of the University of California. > This program is free software; you may redistribute it under the terms of > the GNU General Public License. This program has absolutely no warranty. > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > ipmimonitoring: authentication type unavailable for attempted privilege level > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > ipmimonitoring: authentication type unavailable for attempted privilege level > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="authcap" -u admin -p relation > ipmimonitoring: authentication type unavailable for attempted privilege level > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 --debug -u admin -p relation > 192.168.1.211: ===================================================== > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Request > 192.168.1.211: ===================================================== > 192.168.1.211: RMCP Header: > 192.168.1.211: ------------ > 192.168.1.211: [ 6h] = version[ 8b] > 192.168.1.211: [ 0h] = reserved[ 8b] > 192.168.1.211: [ FFh] = sequence_number[ 8b] > 192.168.1.211: [ 7h] = message_class.class[ 5b] > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > 192.168.1.211: IPMI Session Header: > 192.168.1.211: -------------------- > 192.168.1.211: [ 0h] = authentication_type[ 8b] > 192.168.1.211: [ 0h] = session_sequence_number[32b] > 192.168.1.211: [ 0h] = session_id[32b] > 192.168.1.211: [ 9h] = ipmi_msg_len[ 8b] > 192.168.1.211: IPMI Message Header: > 192.168.1.211: -------------------- > 192.168.1.211: [ 20h] = rs_addr[ 8b] > 192.168.1.211: [ 0h] = rs_lun[ 2b] > 192.168.1.211: [ 6h] = net_fn[ 6b] > 192.168.1.211: [ C8h] = checksum1[ 8b] > 192.168.1.211: [ 81h] = rq_addr[ 8b] > 192.168.1.211: [ 0h] = rq_lun[ 2b] > 192.168.1.211: [ 8h] = rq_seq[ 6b] > 192.168.1.211: IPMI Command Data: > 192.168.1.211: ------------------ > 192.168.1.211: [ 38h] = cmd[ 8b] > 192.168.1.211: [ Eh] = channel_number[ 4b] > 192.168.1.211: [ 0h] = reserved1[ 4b] > 192.168.1.211: [ 3h] = maximum_privilege_level[ 4b] > 192.168.1.211: [ 0h] = reserved2[ 4b] > 192.168.1.211: IPMI Trailer: > 192.168.1.211: -------------- > 192.168.1.211: [ 16h] = checksum2[ 8b] > 192.168.1.211: ===================================================== > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Response > 192.168.1.211: ===================================================== > 192.168.1.211: RMCP Header: > 192.168.1.211: ------------ > 192.168.1.211: [ 6h] = version[ 8b] > 192.168.1.211: [ 0h] = reserved[ 8b] > 192.168.1.211: [ FFh] = sequence_number[ 8b] > 192.168.1.211: [ 7h] = message_class.class[ 5b] > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > 192.168.1.211: IPMI Session Header: > 192.168.1.211: -------------------- > 192.168.1.211: [ 0h] = authentication_type[ 8b] > 192.168.1.211: [ 0h] = session_sequence_number[32b] > 192.168.1.211: [ 0h] = session_id[32b] > 192.168.1.211: [ 10h] = ipmi_msg_len[ 8b] > 192.168.1.211: IPMI Message Header: > 192.168.1.211: -------------------- > 192.168.1.211: [ 81h] = rq_addr[ 8b] > 192.168.1.211: [ 0h] = rq_lun[ 2b] > 192.168.1.211: [ 7h] = net_fn[ 6b] > 192.168.1.211: [ 63h] = checksum1[ 8b] > 192.168.1.211: [ 20h] = rs_addr[ 8b] > 192.168.1.211: [ 0h] = rs_lun[ 2b] > 192.168.1.211: [ 8h] = rq_seq[ 6b] > 192.168.1.211: IPMI Command Data: > 192.168.1.211: ------------------ > 192.168.1.211: [ 38h] = cmd[ 8b] > 192.168.1.211: [ 0h] = comp_code[ 8b] > 192.168.1.211: [ 1h] = channel_number[ 8b] > 192.168.1.211: [ 0h] = authentication_type.none[ 1b] > 192.168.1.211: [ 0h] = authentication_type.md2[ 1b] > 192.168.1.211: [ 0h] = authentication_type.md5[ 1b] > 192.168.1.211: [ 0h] = authentication_type.reserved1[ 1b] > 192.168.1.211: [ 0h] = authentication_type.straight_password_key[ 1b] > 192.168.1.211: [ 0h] = authentication_type.oem_prop[ 1b] > 192.168.1.211: [ 0h] = authentication_type.reserved2[ 2b] > 192.168.1.211: [ 0h] = authentication_status.anonymous_login[ 1b] > 192.168.1.211: [ 0h] = authentication_status.null_username[ 1b] > 192.168.1.211: [ 1h] = authentication_status.non_null_username[ 1b] > 192.168.1.211: [ 0h] = authentication_status.user_level_authentication[ 1b] > 192.168.1.211: [ 0h] = authentication_status.per_message_authentication[ 1b] > 192.168.1.211: [ 0h] = authentication_status.reserved[ 3b] > 192.168.1.211: [ 0h] = reserved1[ 8b] > 192.168.1.211: [ 0h] = oem_id[24b] > 192.168.1.211: [ 0h] = oem_auxiliary_data[ 8b] > 192.168.1.211: IPMI Trailer: > 192.168.1.211: -------------- > 192.168.1.211: [ 83h] = checksum2[ 8b] > ipmimonitoring: authentication type unavailable for attempted privilege level > [root@tpw ~]# > [root@tpw ~]# > [root@tpw ~]# > [root@tpw ~]# ipmimonitoring -h 10.10.10.233 -u ADMIN -p ADMIN > Record_ID | Sensor Name | Sensor Group | Monitoring Status| Sensor Units | Sensor Reading > 4 | System Temp | Temperature | Nominal | C | 41.000000 > 5 | CPU1 Vcore | Voltage | Nominal | V | 0.976000 > 7 | CPU1 DIMM | Voltage | Nominal | V | 1.512000 > 9 | +1.5V | Voltage | Nominal | V | 1.504000 > 10 | +3.3V | Voltage | Nominal | V | 3.240000 > 11 | +3.3VSB | Voltage | Nominal | V | 3.240000 > 12 | +5V | Voltage | Nominal | V | 5.120000 > 13 | +12V | Voltage | Nominal | V | 12.190000 > 14 | VBAT | Voltage | Nominal | V | 3.216000 > 15 | Fan1 | Fan | Nominal | RPM | 3264.000000 > 16 | Fan2 | Fan | Nominal | RPM | 3536.000000 > 19 | Fan5 | Fan | Nominal | RPM | 2788.000000 > 20 | Fan6 | Fan | Nominal | RPM | 2652.000000 > 21 | Fan7 | Fan | Nominal | RPM | 3536.000000 > 23 | Intrusion | Physical Security | Nominal | N/A | 'OK' > 24 | PS Failure | Power Supply | Nominal | N/A | 'OK' > [root@tpw ~]# > > Werner > > On Wed, 2009-08-19 at 08:58 -0700, Al Chu wrote: > > Hi Werner, > > > > It's possible the motherboard is not reporting supported authentication > > types correctly. You could give the "authcap" workaround a shot. > > However, if this is being non-compliant in the way that I think it is, > > the "authcap" workaround won't work (b/c it currently handles a > > different non-compliance bug). Could you send me the output from > > --debug? If we can verify the issue, I'll implement a new workaround > > for you. > > > > BTW, if you need the intel20 workarounds for IPMI 2.0, you may need to > > upgrade. There were some bugs found a few releases ago. > > > > 0.7.4 - 12/15/08 > > ---------------- > > <snip> > > o Fix Intel IPMI 2.0 workarounds in all tools/libraries. > > <snip> > > > > Al > > > > On Wed, 2009-08-19 at 14:16 +0200, Werner Fischer wrote: > > > Dear freeipmi users/developers, > > > > > > I'm trying to monitor an Intel SR2500 server (this server has the Intel > > > S5000PAL mainboard in it). > > > > > > While I can monitor it using ipmitool, I keep getting errors with > > > ipmimonitoring from freeipmi. Also using the "-W" parameter for > > > workarounds (as described in the manpage of ipmimonitoring) doesn't > > > help: > > > > > > -------------------------------------------------------------------------- > > > [root@tpw ~]# ipmitool -I lan -H 192.168.1.211 -U admin -P relation sdr > > > BB +1.2V Vtt | 1.20 Volts | ok > > > BB +1.5V AUX | 1.47 Volts | ok > > > BB +1.5V | 1.48 Volts | ok > > > BB +1.8V | 1.79 Volts | ok > > > BB +3.3V | 3.35 Volts | ok > > > BB +3.3V STB | 3.35 Volts | ok > > > ^C > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > > > ipmi_monitoring_sensor_readings_by_record_id: authentication type unavailable for attempted privilege level > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > > > ipmi_monitoring_sensor_readings_by_record_id: authentication type unavailable for attempted privilege level > > > [root@tpw ~]# rpm -q freeipmi > > > freeipmi-0.5.1-3.fc9.i386 > > > [root@tpw ~]# > > > -------------------------------------------------------------------------- > > > > > > I checked the manpage: > > > "authentication type unavailable for attempted privilege level" - The authentication type you wish > > > to authenticate with is not available for this privilege level. Please try again with an alternate > > > authentication type or alternate privilege level. It may also be possible the available authenti- > > > cation types you can authenticate with are not correctly configured on the remote BMC. > > > But the settings at the BMC side seem to be ok: > > > > > > -------------------------------------------------------------------------- > > > [root@tpw ~]# ipmitool -I lan -H 192.168.1.211 -U admin -P relation lan print 1 > > > Set in Progress : Set Complete > > > Auth Type Support : NONE MD5 PASSWORD > > > Auth Type Enable : Callback : > > > : User : > > > : Operator : > > > : Admin : MD5 PASSWORD > > > : OEM : > > > IP Address Source : Static Address > > > IP Address : 192.168.1.211 > > > Subnet Mask : 255.255.255.0 > > > MAC Address : 00:0e:0c:ea:92:a2 > > > [...] > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -a MD5 -u admin -p relation > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > [root@tpw ~]# > > > -------------------------------------------------------------------------- > > > > > > Also compiling the newest version and using it does not help: > > > -------------------------------------------------------------------------- > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > [root@tpw ~]# rpm -q freeipmi > > > freeipmi-0.7.11-1.fc9.i386 > > > [root@tpw ~]# > > > -------------------------------------------------------------------------- > > > > > > In contrast, monitoring a system with a new Supermicro X8DT3-F mainboard > > > works fine with freeipmi-0.5.1-3.fc9.i386 and also with > > > freeipmi-0.7.11-1.fc9.i386: > > > > > > -------------------------------------------------------------------------- > > > [root@tpw ~]# ipmitool -I lan -H 10.10.10.233 -U ADMIN -P ADMIN sdr > > > CPU1 Temp | 0 unspecified | ok > > > CPU2 Temp | no reading | ns > > > System Temp | 45 degrees C | ok > > > CPU1 Vcore | 0.98 Volts | ok > > > CPU2 Vcore | no reading | ns > > > CPU1 DIMM | 1.51 Volts | ok > > > CPU2 DIMM | no reading | ns > > > ^C > > > [root@tpw ~]# ipmimonitoring -h 10.10.10.233 -u ADMIN -p ADMIN > > > Record_ID | Sensor Name | Sensor Group | Monitoring Status| Sensor Units | Sensor Reading > > > 4 | System Temp | Temperature | Nominal | C | 45.000000 > > > 5 | CPU1 Vcore | Voltage | Nominal | V | 0.976000 > > > 6 | CPU2 Vcore | Voltage | Nominal | V | 0.000000 > > > 7 | CPU1 DIMM | Voltage | Nominal | V | 1.512000 > > > 8 | CPU2 DIMM | Voltage | Nominal | V | 0.000000 > > > 9 | +1.5V | Voltage | Nominal | V | 1.504000 > > > 10 | +3.3V | Voltage | Nominal | V | 3.240000 > > > 11 | +3.3VSB | Voltage | Nominal | V | 3.240000 > > > 12 | +5V | Voltage | Nominal | V | 5.120000 > > > 13 | +12V | Voltage | Nominal | V | 12.190000 > > > 14 | VBAT | Voltage | Nominal | V | 3.240000 > > > 15 | Fan1 | Fan | Nominal | RPM | 6528.000000 > > > 16 | Fan2 | Fan | Nominal | RPM | 7072.000000 > > > 17 | Fan3 | Fan | Nominal | RPM | 0.000000 > > > 18 | Fan4 | Fan | Nominal | RPM | 0.000000 > > > 19 | Fan5 | Fan | Nominal | RPM | 5644.000000 > > > 20 | Fan6 | Fan | Nominal | RPM | 5304.000000 > > > 21 | Fan7 | Fan | Nominal | RPM | 7072.000000 > > > 22 | Fan8 | Fan | Nominal | RPM | 0.000000 > > > 23 | Intrusion | Physical Security | Nominal | N/A | '' > > > 24 | PS Failure | Power Supply | Nominal | N/A | '' > > > [root@tpw ~]# > > > -------------------------------------------------------------------------- > > > > > > Does anybody have an idea how this problem could be fixed? > > > > > > best regards, > > > Werner > > > > > > > > > > > > _______________________________________________ > > > Freeipmi-users mailing list > > > Freeipmi-users@... > > > http://**lists.gnu.org/mailman/listinfo/freeipmi-users > > > > > > > _______________________________________________ > Freeipmi-users mailing list > Freeipmi-users@... > http://*lists.gnu.org/mailman/listinfo/freeipmi-users > Albert Chu chu11@... Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory _______________________________________________ Freeipmi-users mailing list Freeipmi-users@... http://lists.gnu.org/mailman/listinfo/freeipmi-users |
|
|
Re: "authentication type unavailable for attempted privilege level" with Intel S5000PAL Mainboard
by Al Chu11
::
Rate this Message:
Hi Werner,
I've got a test tar.gz here: http://ftp.gluster.com/pub/freeipmi/qa-release/freeipmi-0.7.12.beta2.tar.gz This makes it so the 'authcap' workaround should work for you. Can you give it a shot to make sure it works? Thanks, Al On Fri, 2009-08-21 at 08:44 -0700, Al Chu wrote: > Hi Werner, > > > 192.168.1.211: [ 0h] = authentication_type.none[ 1b] > > 192.168.1.211: [ 0h] = authentication_type.md2[ 1b] > > 192.168.1.211: [ 0h] = authentication_type.md5[ 1b] > > 192.168.1.211: [ 0h] = authentication_type.reserved1[ 1b] > > 192.168.1.211: [ 0h] = authentication_type.straight_password_key[ 1b] > > 192.168.1.211: [ 0h] = authentication_type.oem_prop[ 1b] > > This indicates that no authentication support is enabled, which is very > unlikely of being true (which we could verify via 'bmc-config --checkout > --section=lan_conf_auth'). > > I'll modify the 'authcap' workaround to also encompass this case and > post a beta tar.gz for you to check out. > > Al > > On Fri, 2009-08-21 at 09:58 +0200, Werner Fischer wrote: > > Hi Al, > > > > thanks for your fast answer. > > > > Below you find the requested debug output. I'm using version 0.7.11. The > > "authcap" workaround does not fix the problem. After executing with > > debug to the affected Intel S5000PAL system (IP 192.168.1.211) I again > > verified the correct behavior of ipmimonitoring to the other system > > (Supermicro) to IP 10.10.10.233. > > > > [root@tpw ~]# rpm -q freeipmi > > freeipmi-0.7.11-1.fc9.i386 > > [root@tpw ~]# ipmimonitoring -V > > ipmimonitoring - 0.7.11 > > Copyright (C) 2007-2008 Lawrence Livermore National Security, LLC. > > Copyright (C) 2006-2007 The Regents of the University of California. > > This program is free software; you may redistribute it under the terms of > > the GNU General Public License. This program has absolutely no warranty. > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > > ipmimonitoring: authentication type unavailable for attempted privilege level > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > > ipmimonitoring: authentication type unavailable for attempted privilege level > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="authcap" -u admin -p relation > > ipmimonitoring: authentication type unavailable for attempted privilege level > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 --debug -u admin -p relation > > 192.168.1.211: ===================================================== > > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Request > > 192.168.1.211: ===================================================== > > 192.168.1.211: RMCP Header: > > 192.168.1.211: ------------ > > 192.168.1.211: [ 6h] = version[ 8b] > > 192.168.1.211: [ 0h] = reserved[ 8b] > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > 192.168.1.211: IPMI Session Header: > > 192.168.1.211: -------------------- > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > 192.168.1.211: [ 0h] = session_id[32b] > > 192.168.1.211: [ 9h] = ipmi_msg_len[ 8b] > > 192.168.1.211: IPMI Message Header: > > 192.168.1.211: -------------------- > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > 192.168.1.211: [ 6h] = net_fn[ 6b] > > 192.168.1.211: [ C8h] = checksum1[ 8b] > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > 192.168.1.211: [ 8h] = rq_seq[ 6b] > > 192.168.1.211: IPMI Command Data: > > 192.168.1.211: ------------------ > > 192.168.1.211: [ 38h] = cmd[ 8b] > > 192.168.1.211: [ Eh] = channel_number[ 4b] > > 192.168.1.211: [ 0h] = reserved1[ 4b] > > 192.168.1.211: [ 3h] = maximum_privilege_level[ 4b] > > 192.168.1.211: [ 0h] = reserved2[ 4b] > > 192.168.1.211: IPMI Trailer: > > 192.168.1.211: -------------- > > 192.168.1.211: [ 16h] = checksum2[ 8b] > > 192.168.1.211: ===================================================== > > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Response > > 192.168.1.211: ===================================================== > > 192.168.1.211: RMCP Header: > > 192.168.1.211: ------------ > > 192.168.1.211: [ 6h] = version[ 8b] > > 192.168.1.211: [ 0h] = reserved[ 8b] > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > 192.168.1.211: IPMI Session Header: > > 192.168.1.211: -------------------- > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > 192.168.1.211: [ 0h] = session_id[32b] > > 192.168.1.211: [ 10h] = ipmi_msg_len[ 8b] > > 192.168.1.211: IPMI Message Header: > > 192.168.1.211: -------------------- > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > 192.168.1.211: [ 7h] = net_fn[ 6b] > > 192.168.1.211: [ 63h] = checksum1[ 8b] > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > 192.168.1.211: [ 8h] = rq_seq[ 6b] > > 192.168.1.211: IPMI Command Data: > > 192.168.1.211: ------------------ > > 192.168.1.211: [ 38h] = cmd[ 8b] > > 192.168.1.211: [ 0h] = comp_code[ 8b] > > 192.168.1.211: [ 1h] = channel_number[ 8b] > > 192.168.1.211: [ 0h] = authentication_type.none[ 1b] > > 192.168.1.211: [ 0h] = authentication_type.md2[ 1b] > > 192.168.1.211: [ 0h] = authentication_type.md5[ 1b] > > 192.168.1.211: [ 0h] = authentication_type.reserved1[ 1b] > > 192.168.1.211: [ 0h] = authentication_type.straight_password_key[ 1b] > > 192.168.1.211: [ 0h] = authentication_type.oem_prop[ 1b] > > 192.168.1.211: [ 0h] = authentication_type.reserved2[ 2b] > > 192.168.1.211: [ 0h] = authentication_status.anonymous_login[ 1b] > > 192.168.1.211: [ 0h] = authentication_status.null_username[ 1b] > > 192.168.1.211: [ 1h] = authentication_status.non_null_username[ 1b] > > 192.168.1.211: [ 0h] = authentication_status.user_level_authentication[ 1b] > > 192.168.1.211: [ 0h] = authentication_status.per_message_authentication[ 1b] > > 192.168.1.211: [ 0h] = authentication_status.reserved[ 3b] > > 192.168.1.211: [ 0h] = reserved1[ 8b] > > 192.168.1.211: [ 0h] = oem_id[24b] > > 192.168.1.211: [ 0h] = oem_auxiliary_data[ 8b] > > 192.168.1.211: IPMI Trailer: > > 192.168.1.211: -------------- > > 192.168.1.211: [ 83h] = checksum2[ 8b] > > ipmimonitoring: authentication type unavailable for attempted privilege level > > [root@tpw ~]# > > [root@tpw ~]# > > [root@tpw ~]# > > [root@tpw ~]# ipmimonitoring -h 10.10.10.233 -u ADMIN -p ADMIN > > Record_ID | Sensor Name | Sensor Group | Monitoring Status| Sensor Units | Sensor Reading > > 4 | System Temp | Temperature | Nominal | C | 41.000000 > > 5 | CPU1 Vcore | Voltage | Nominal | V | 0.976000 > > 7 | CPU1 DIMM | Voltage | Nominal | V | 1.512000 > > 9 | +1.5V | Voltage | Nominal | V | 1.504000 > > 10 | +3.3V | Voltage | Nominal | V | 3.240000 > > 11 | +3.3VSB | Voltage | Nominal | V | 3.240000 > > 12 | +5V | Voltage | Nominal | V | 5.120000 > > 13 | +12V | Voltage | Nominal | V | 12.190000 > > 14 | VBAT | Voltage | Nominal | V | 3.216000 > > 15 | Fan1 | Fan | Nominal | RPM | 3264.000000 > > 16 | Fan2 | Fan | Nominal | RPM | 3536.000000 > > 19 | Fan5 | Fan | Nominal | RPM | 2788.000000 > > 20 | Fan6 | Fan | Nominal | RPM | 2652.000000 > > 21 | Fan7 | Fan | Nominal | RPM | 3536.000000 > > 23 | Intrusion | Physical Security | Nominal | N/A | 'OK' > > 24 | PS Failure | Power Supply | Nominal | N/A | 'OK' > > [root@tpw ~]# > > > > Werner > > > > On Wed, 2009-08-19 at 08:58 -0700, Al Chu wrote: > > > Hi Werner, > > > > > > It's possible the motherboard is not reporting supported authentication > > > types correctly. You could give the "authcap" workaround a shot. > > > However, if this is being non-compliant in the way that I think it is, > > > the "authcap" workaround won't work (b/c it currently handles a > > > different non-compliance bug). Could you send me the output from > > > --debug? If we can verify the issue, I'll implement a new workaround > > > for you. > > > > > > BTW, if you need the intel20 workarounds for IPMI 2.0, you may need to > > > upgrade. There were some bugs found a few releases ago. > > > > > > 0.7.4 - 12/15/08 > > > ---------------- > > > <snip> > > > o Fix Intel IPMI 2.0 workarounds in all tools/libraries. > > > <snip> > > > > > > Al > > > > > > On Wed, 2009-08-19 at 14:16 +0200, Werner Fischer wrote: > > > > Dear freeipmi users/developers, > > > > > > > > I'm trying to monitor an Intel SR2500 server (this server has the Intel > > > > S5000PAL mainboard in it). > > > > > > > > While I can monitor it using ipmitool, I keep getting errors with > > > > ipmimonitoring from freeipmi. Also using the "-W" parameter for > > > > workarounds (as described in the manpage of ipmimonitoring) doesn't > > > > help: > > > > > > > > -------------------------------------------------------------------------- > > > > [root@tpw ~]# ipmitool -I lan -H 192.168.1.211 -U admin -P relation sdr > > > > BB +1.2V Vtt | 1.20 Volts | ok > > > > BB +1.5V AUX | 1.47 Volts | ok > > > > BB +1.5V | 1.48 Volts | ok > > > > BB +1.8V | 1.79 Volts | ok > > > > BB +3.3V | 3.35 Volts | ok > > > > BB +3.3V STB | 3.35 Volts | ok > > > > ^C > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > > > > ipmi_monitoring_sensor_readings_by_record_id: authentication type unavailable for attempted privilege level > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > > > > ipmi_monitoring_sensor_readings_by_record_id: authentication type unavailable for attempted privilege level > > > > [root@tpw ~]# rpm -q freeipmi > > > > freeipmi-0.5.1-3.fc9.i386 > > > > [root@tpw ~]# > > > > -------------------------------------------------------------------------- > > > > > > > > I checked the manpage: > > > > "authentication type unavailable for attempted privilege level" - The authentication type you wish > > > > to authenticate with is not available for this privilege level. Please try again with an alternate > > > > authentication type or alternate privilege level. It may also be possible the available authenti- > > > > cation types you can authenticate with are not correctly configured on the remote BMC. > > > > But the settings at the BMC side seem to be ok: > > > > > > > > -------------------------------------------------------------------------- > > > > [root@tpw ~]# ipmitool -I lan -H 192.168.1.211 -U admin -P relation lan print 1 > > > > Set in Progress : Set Complete > > > > Auth Type Support : NONE MD5 PASSWORD > > > > Auth Type Enable : Callback : > > > > : User : > > > > : Operator : > > > > : Admin : MD5 PASSWORD > > > > : OEM : > > > > IP Address Source : Static Address > > > > IP Address : 192.168.1.211 > > > > Subnet Mask : 255.255.255.0 > > > > MAC Address : 00:0e:0c:ea:92:a2 > > > > [...] > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -a MD5 -u admin -p relation > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > [root@tpw ~]# > > > > -------------------------------------------------------------------------- > > > > > > > > Also compiling the newest version and using it does not help: > > > > -------------------------------------------------------------------------- > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > [root@tpw ~]# rpm -q freeipmi > > > > freeipmi-0.7.11-1.fc9.i386 > > > > [root@tpw ~]# > > > > -------------------------------------------------------------------------- > > > > > > > > In contrast, monitoring a system with a new Supermicro X8DT3-F mainboard > > > > works fine with freeipmi-0.5.1-3.fc9.i386 and also with > > > > freeipmi-0.7.11-1.fc9.i386: > > > > > > > > -------------------------------------------------------------------------- > > > > [root@tpw ~]# ipmitool -I lan -H 10.10.10.233 -U ADMIN -P ADMIN sdr > > > > CPU1 Temp | 0 unspecified | ok > > > > CPU2 Temp | no reading | ns > > > > System Temp | 45 degrees C | ok > > > > CPU1 Vcore | 0.98 Volts | ok > > > > CPU2 Vcore | no reading | ns > > > > CPU1 DIMM | 1.51 Volts | ok > > > > CPU2 DIMM | no reading | ns > > > > ^C > > > > [root@tpw ~]# ipmimonitoring -h 10.10.10.233 -u ADMIN -p ADMIN > > > > Record_ID | Sensor Name | Sensor Group | Monitoring Status| Sensor Units | Sensor Reading > > > > 4 | System Temp | Temperature | Nominal | C | 45.000000 > > > > 5 | CPU1 Vcore | Voltage | Nominal | V | 0.976000 > > > > 6 | CPU2 Vcore | Voltage | Nominal | V | 0.000000 > > > > 7 | CPU1 DIMM | Voltage | Nominal | V | 1.512000 > > > > 8 | CPU2 DIMM | Voltage | Nominal | V | 0.000000 > > > > 9 | +1.5V | Voltage | Nominal | V | 1.504000 > > > > 10 | +3.3V | Voltage | Nominal | V | 3.240000 > > > > 11 | +3.3VSB | Voltage | Nominal | V | 3.240000 > > > > 12 | +5V | Voltage | Nominal | V | 5.120000 > > > > 13 | +12V | Voltage | Nominal | V | 12.190000 > > > > 14 | VBAT | Voltage | Nominal | V | 3.240000 > > > > 15 | Fan1 | Fan | Nominal | RPM | 6528.000000 > > > > 16 | Fan2 | Fan | Nominal | RPM | 7072.000000 > > > > 17 | Fan3 | Fan | Nominal | RPM | 0.000000 > > > > 18 | Fan4 | Fan | Nominal | RPM | 0.000000 > > > > 19 | Fan5 | Fan | Nominal | RPM | 5644.000000 > > > > 20 | Fan6 | Fan | Nominal | RPM | 5304.000000 > > > > 21 | Fan7 | Fan | Nominal | RPM | 7072.000000 > > > > 22 | Fan8 | Fan | Nominal | RPM | 0.000000 > > > > 23 | Intrusion | Physical Security | Nominal | N/A | '' > > > > 24 | PS Failure | Power Supply | Nominal | N/A | '' > > > > [root@tpw ~]# > > > > -------------------------------------------------------------------------- > > > > > > > > Does anybody have an idea how this problem could be fixed? > > > > > > > > best regards, > > > > Werner > > > > > > > > > > > > > > > > _______________________________________________ > > > > Freeipmi-users mailing list > > > > Freeipmi-users@... > > > > http://**lists.gnu.org/mailman/listinfo/freeipmi-users > > > > > > > > > > > > _______________________________________________ > > Freeipmi-users mailing list > > Freeipmi-users@... > > http://*lists.gnu.org/mailman/listinfo/freeipmi-users > > Albert Chu chu11@... Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory _______________________________________________ Freeipmi-users mailing list Freeipmi-users@... http://lists.gnu.org/mailman/listinfo/freeipmi-users |
|
|
Re: "authentication type unavailable for attempted privilege level" with Intel S5000PAL Mainboard
by Werner Fischer-2
::
Rate this Message:
Hi Al,
thanks for the updated tar.gz. I tried it, but somehow it still seems to cause problems (see below). I'll be two days out of office - so I can do further tests on Thursday. thanks for your support! [root@tpw ~]# rpm -q freeipmi freeipmi-0.7.12.beta2-1.fc9.i386 [root@tpw ~]# ipmimonitoring -V ipmimonitoring - 0.7.12.beta2 Copyright (C) 2007-2008 Lawrence Livermore National Security, LLC. Copyright (C) 2006-2007 The Regents of the University of California. This program is free software; you may redistribute it under the terms of the GNU General Public License. This program has absolutely no warranty. [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation ipmimonitoring: authentication type unavailable for attempted privilege level [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation ipmimonitoring: authentication type unavailable for attempted privilege level [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="authcap" -u admin -p relation ipmimonitoring: authentication type unavailable for attempted privilege level [root@tpw ~]# ipmimonitoring -h 192.168.1.211 --debug -u admin -p relation 192.168.1.211: ===================================================== 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Request 192.168.1.211: ===================================================== 192.168.1.211: RMCP Header: 192.168.1.211: ------------ 192.168.1.211: [ 6h] = version[ 8b] 192.168.1.211: [ 0h] = reserved[ 8b] 192.168.1.211: [ FFh] = sequence_number[ 8b] 192.168.1.211: [ 7h] = message_class.class[ 5b] 192.168.1.211: [ 0h] = message_class.reserved[ 2b] 192.168.1.211: [ 0h] = message_class.ack[ 1b] 192.168.1.211: IPMI Session Header: 192.168.1.211: -------------------- 192.168.1.211: [ 0h] = authentication_type[ 8b] 192.168.1.211: [ 0h] = session_sequence_number[32b] 192.168.1.211: [ 0h] = session_id[32b] 192.168.1.211: [ 9h] = ipmi_msg_len[ 8b] 192.168.1.211: IPMI Message Header: 192.168.1.211: -------------------- 192.168.1.211: [ 20h] = rs_addr[ 8b] 192.168.1.211: [ 0h] = rs_lun[ 2b] 192.168.1.211: [ 6h] = net_fn[ 6b] 192.168.1.211: [ C8h] = checksum1[ 8b] 192.168.1.211: [ 81h] = rq_addr[ 8b] 192.168.1.211: [ 0h] = rq_lun[ 2b] 192.168.1.211: [ 13h] = rq_seq[ 6b] 192.168.1.211: IPMI Command Data: 192.168.1.211: ------------------ 192.168.1.211: [ 38h] = cmd[ 8b] 192.168.1.211: [ Eh] = channel_number[ 4b] 192.168.1.211: [ 0h] = reserved1[ 4b] 192.168.1.211: [ 3h] = maximum_privilege_level[ 4b] 192.168.1.211: [ 0h] = reserved2[ 4b] 192.168.1.211: IPMI Trailer: 192.168.1.211: -------------- 192.168.1.211: [ EAh] = checksum2[ 8b] 192.168.1.211: ===================================================== 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Response 192.168.1.211: ===================================================== 192.168.1.211: RMCP Header: 192.168.1.211: ------------ 192.168.1.211: [ 6h] = version[ 8b] 192.168.1.211: [ 0h] = reserved[ 8b] 192.168.1.211: [ FFh] = sequence_number[ 8b] 192.168.1.211: [ 7h] = message_class.class[ 5b] 192.168.1.211: [ 0h] = message_class.reserved[ 2b] 192.168.1.211: [ 0h] = message_class.ack[ 1b] 192.168.1.211: IPMI Session Header: 192.168.1.211: -------------------- 192.168.1.211: [ 0h] = authentication_type[ 8b] 192.168.1.211: [ 0h] = session_sequence_number[32b] 192.168.1.211: [ 0h] = session_id[32b] 192.168.1.211: [ 10h] = ipmi_msg_len[ 8b] 192.168.1.211: IPMI Message Header: 192.168.1.211: -------------------- 192.168.1.211: [ 81h] = rq_addr[ 8b] 192.168.1.211: [ 0h] = rq_lun[ 2b] 192.168.1.211: [ 7h] = net_fn[ 6b] 192.168.1.211: [ 63h] = checksum1[ 8b] 192.168.1.211: [ 20h] = rs_addr[ 8b] 192.168.1.211: [ 0h] = rs_lun[ 2b] 192.168.1.211: [ 13h] = rq_seq[ 6b] 192.168.1.211: IPMI Command Data: 192.168.1.211: ------------------ 192.168.1.211: [ 38h] = cmd[ 8b] 192.168.1.211: [ 0h] = comp_code[ 8b] 192.168.1.211: [ 1h] = channel_number[ 8b] 192.168.1.211: [ 0h] = authentication_type.none[ 1b] 192.168.1.211: [ 0h] = authentication_type.md2[ 1b] 192.168.1.211: [ 0h] = authentication_type.md5[ 1b] 192.168.1.211: [ 0h] = authentication_type.reserved1[ 1b] 192.168.1.211: [ 0h] = authentication_type.straight_password_key[ 1b] 192.168.1.211: [ 0h] = authentication_type.oem_prop[ 1b] 192.168.1.211: [ 0h] = authentication_type.reserved2[ 2b] 192.168.1.211: [ 0h] = authentication_status.anonymous_login[ 1b] 192.168.1.211: [ 0h] = authentication_status.null_username[ 1b] 192.168.1.211: [ 1h] = authentication_status.non_null_username[ 1b] 192.168.1.211: [ 0h] = authentication_status.user_level_authentication[ 1b] 192.168.1.211: [ 0h] = authentication_status.per_message_authentication[ 1b] 192.168.1.211: [ 0h] = authentication_status.reserved[ 3b] 192.168.1.211: [ 0h] = reserved1[ 8b] 192.168.1.211: [ 0h] = oem_id[24b] 192.168.1.211: [ 0h] = oem_auxiliary_data[ 8b] 192.168.1.211: IPMI Trailer: 192.168.1.211: -------------- 192.168.1.211: [ 57h] = checksum2[ 8b] ipmimonitoring: authentication type unavailable for attempted privilege level [root@tpw ~]# On Fri, 2009-08-21 at 14:03 -0700, Al Chu wrote: > Hi Werner, > > I've got a test tar.gz here: > > http://ftp.gluster.com/pub/freeipmi/qa-release/freeipmi-0.7.12.beta2.tar.gz > > This makes it so the 'authcap' workaround should work for you. Can you > give it a shot to make sure it works? > > Thanks, > Al > > On Fri, 2009-08-21 at 08:44 -0700, Al Chu wrote: > > Hi Werner, > > > > > 192.168.1.211: [ 0h] = authentication_type.none[ 1b] > > > 192.168.1.211: [ 0h] = authentication_type.md2[ 1b] > > > 192.168.1.211: [ 0h] = authentication_type.md5[ 1b] > > > 192.168.1.211: [ 0h] = authentication_type.reserved1[ 1b] > > > 192.168.1.211: [ 0h] = authentication_type.straight_password_key[ 1b] > > > 192.168.1.211: [ 0h] = authentication_type.oem_prop[ 1b] > > > > This indicates that no authentication support is enabled, which is very > > unlikely of being true (which we could verify via 'bmc-config --checkout > > --section=lan_conf_auth'). > > > > I'll modify the 'authcap' workaround to also encompass this case and > > post a beta tar.gz for you to check out. > > > > Al > > > > On Fri, 2009-08-21 at 09:58 +0200, Werner Fischer wrote: > > > Hi Al, > > > > > > thanks for your fast answer. > > > > > > Below you find the requested debug output. I'm using version 0.7.11. The > > > "authcap" workaround does not fix the problem. After executing with > > > debug to the affected Intel S5000PAL system (IP 192.168.1.211) I again > > > verified the correct behavior of ipmimonitoring to the other system > > > (Supermicro) to IP 10.10.10.233. > > > > > > [root@tpw ~]# rpm -q freeipmi > > > freeipmi-0.7.11-1.fc9.i386 > > > [root@tpw ~]# ipmimonitoring -V > > > ipmimonitoring - 0.7.11 > > > Copyright (C) 2007-2008 Lawrence Livermore National Security, LLC. > > > Copyright (C) 2006-2007 The Regents of the University of California. > > > This program is free software; you may redistribute it under the terms of > > > the GNU General Public License. This program has absolutely no warranty. > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="authcap" -u admin -p relation > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 --debug -u admin -p relation > > > 192.168.1.211: ===================================================== > > > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Request > > > 192.168.1.211: ===================================================== > > > 192.168.1.211: RMCP Header: > > > 192.168.1.211: ------------ > > > 192.168.1.211: [ 6h] = version[ 8b] > > > 192.168.1.211: [ 0h] = reserved[ 8b] > > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > > 192.168.1.211: IPMI Session Header: > > > 192.168.1.211: -------------------- > > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > > 192.168.1.211: [ 0h] = session_id[32b] > > > 192.168.1.211: [ 9h] = ipmi_msg_len[ 8b] > > > 192.168.1.211: IPMI Message Header: > > > 192.168.1.211: -------------------- > > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > > 192.168.1.211: [ 6h] = net_fn[ 6b] > > > 192.168.1.211: [ C8h] = checksum1[ 8b] > > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > > 192.168.1.211: [ 8h] = rq_seq[ 6b] > > > 192.168.1.211: IPMI Command Data: > > > 192.168.1.211: ------------------ > > > 192.168.1.211: [ 38h] = cmd[ 8b] > > > 192.168.1.211: [ Eh] = channel_number[ 4b] > > > 192.168.1.211: [ 0h] = reserved1[ 4b] > > > 192.168.1.211: [ 3h] = maximum_privilege_level[ 4b] > > > 192.168.1.211: [ 0h] = reserved2[ 4b] > > > 192.168.1.211: IPMI Trailer: > > > 192.168.1.211: -------------- > > > 192.168.1.211: [ 16h] = checksum2[ 8b] > > > 192.168.1.211: ===================================================== > > > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Response > > > 192.168.1.211: ===================================================== > > > 192.168.1.211: RMCP Header: > > > 192.168.1.211: ------------ > > > 192.168.1.211: [ 6h] = version[ 8b] > > > 192.168.1.211: [ 0h] = reserved[ 8b] > > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > > 192.168.1.211: IPMI Session Header: > > > 192.168.1.211: -------------------- > > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > > 192.168.1.211: [ 0h] = session_id[32b] > > > 192.168.1.211: [ 10h] = ipmi_msg_len[ 8b] > > > 192.168.1.211: IPMI Message Header: > > > 192.168.1.211: -------------------- > > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > > 192.168.1.211: [ 7h] = net_fn[ 6b] > > > 192.168.1.211: [ 63h] = checksum1[ 8b] > > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > > 192.168.1.211: [ 8h] = rq_seq[ 6b] > > > 192.168.1.211: IPMI Command Data: > > > 192.168.1.211: ------------------ > > > 192.168.1.211: [ 38h] = cmd[ 8b] > > > 192.168.1.211: [ 0h] = comp_code[ 8b] > > > 192.168.1.211: [ 1h] = channel_number[ 8b] > > > 192.168.1.211: [ 0h] = authentication_type.none[ 1b] > > > 192.168.1.211: [ 0h] = authentication_type.md2[ 1b] > > > 192.168.1.211: [ 0h] = authentication_type.md5[ 1b] > > > 192.168.1.211: [ 0h] = authentication_type.reserved1[ 1b] > > > 192.168.1.211: [ 0h] = authentication_type.straight_password_key[ 1b] > > > 192.168.1.211: [ 0h] = authentication_type.oem_prop[ 1b] > > > 192.168.1.211: [ 0h] = authentication_type.reserved2[ 2b] > > > 192.168.1.211: [ 0h] = authentication_status.anonymous_login[ 1b] > > > 192.168.1.211: [ 0h] = authentication_status.null_username[ 1b] > > > 192.168.1.211: [ 1h] = authentication_status.non_null_username[ 1b] > > > 192.168.1.211: [ 0h] = authentication_status.user_level_authentication[ 1b] > > > 192.168.1.211: [ 0h] = authentication_status.per_message_authentication[ 1b] > > > 192.168.1.211: [ 0h] = authentication_status.reserved[ 3b] > > > 192.168.1.211: [ 0h] = reserved1[ 8b] > > > 192.168.1.211: [ 0h] = oem_id[24b] > > > 192.168.1.211: [ 0h] = oem_auxiliary_data[ 8b] > > > 192.168.1.211: IPMI Trailer: > > > 192.168.1.211: -------------- > > > 192.168.1.211: [ 83h] = checksum2[ 8b] > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > [root@tpw ~]# > > > [root@tpw ~]# > > > [root@tpw ~]# > > > [root@tpw ~]# ipmimonitoring -h 10.10.10.233 -u ADMIN -p ADMIN > > > Record_ID | Sensor Name | Sensor Group | Monitoring Status| Sensor Units | Sensor Reading > > > 4 | System Temp | Temperature | Nominal | C | 41.000000 > > > 5 | CPU1 Vcore | Voltage | Nominal | V | 0.976000 > > > 7 | CPU1 DIMM | Voltage | Nominal | V | 1.512000 > > > 9 | +1.5V | Voltage | Nominal | V | 1.504000 > > > 10 | +3.3V | Voltage | Nominal | V | 3.240000 > > > 11 | +3.3VSB | Voltage | Nominal | V | 3.240000 > > > 12 | +5V | Voltage | Nominal | V | 5.120000 > > > 13 | +12V | Voltage | Nominal | V | 12.190000 > > > 14 | VBAT | Voltage | Nominal | V | 3.216000 > > > 15 | Fan1 | Fan | Nominal | RPM | 3264.000000 > > > 16 | Fan2 | Fan | Nominal | RPM | 3536.000000 > > > 19 | Fan5 | Fan | Nominal | RPM | 2788.000000 > > > 20 | Fan6 | Fan | Nominal | RPM | 2652.000000 > > > 21 | Fan7 | Fan | Nominal | RPM | 3536.000000 > > > 23 | Intrusion | Physical Security | Nominal | N/A | 'OK' > > > 24 | PS Failure | Power Supply | Nominal | N/A | 'OK' > > > [root@tpw ~]# > > > > > > Werner > > > > > > On Wed, 2009-08-19 at 08:58 -0700, Al Chu wrote: > > > > Hi Werner, > > > > > > > > It's possible the motherboard is not reporting supported authentication > > > > types correctly. You could give the "authcap" workaround a shot. > > > > However, if this is being non-compliant in the way that I think it is, > > > > the "authcap" workaround won't work (b/c it currently handles a > > > > different non-compliance bug). Could you send me the output from > > > > --debug? If we can verify the issue, I'll implement a new workaround > > > > for you. > > > > > > > > BTW, if you need the intel20 workarounds for IPMI 2.0, you may need to > > > > upgrade. There were some bugs found a few releases ago. > > > > > > > > 0.7.4 - 12/15/08 > > > > ---------------- > > > > <snip> > > > > o Fix Intel IPMI 2.0 workarounds in all tools/libraries. > > > > <snip> > > > > > > > > Al > > > > > > > > On Wed, 2009-08-19 at 14:16 +0200, Werner Fischer wrote: > > > > > Dear freeipmi users/developers, > > > > > > > > > > I'm trying to monitor an Intel SR2500 server (this server has the Intel > > > > > S5000PAL mainboard in it). > > > > > > > > > > While I can monitor it using ipmitool, I keep getting errors with > > > > > ipmimonitoring from freeipmi. Also using the "-W" parameter for > > > > > workarounds (as described in the manpage of ipmimonitoring) doesn't > > > > > help: > > > > > > > > > > -------------------------------------------------------------------------- > > > > > [root@tpw ~]# ipmitool -I lan -H 192.168.1.211 -U admin -P relation sdr > > > > > BB +1.2V Vtt | 1.20 Volts | ok > > > > > BB +1.5V AUX | 1.47 Volts | ok > > > > > BB +1.5V | 1.48 Volts | ok > > > > > BB +1.8V | 1.79 Volts | ok > > > > > BB +3.3V | 3.35 Volts | ok > > > > > BB +3.3V STB | 3.35 Volts | ok > > > > > ^C > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > > > > > ipmi_monitoring_sensor_readings_by_record_id: authentication type unavailable for attempted privilege level > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > > > > > ipmi_monitoring_sensor_readings_by_record_id: authentication type unavailable for attempted privilege level > > > > > [root@tpw ~]# rpm -q freeipmi > > > > > freeipmi-0.5.1-3.fc9.i386 > > > > > [root@tpw ~]# > > > > > -------------------------------------------------------------------------- > > > > > > > > > > I checked the manpage: > > > > > "authentication type unavailable for attempted privilege level" - The authentication type you wish > > > > > to authenticate with is not available for this privilege level. Please try again with an alternate > > > > > authentication type or alternate privilege level. It may also be possible the available authenti- > > > > > cation types you can authenticate with are not correctly configured on the remote BMC. > > > > > But the settings at the BMC side seem to be ok: > > > > > > > > > > -------------------------------------------------------------------------- > > > > > [root@tpw ~]# ipmitool -I lan -H 192.168.1.211 -U admin -P relation lan print 1 > > > > > Set in Progress : Set Complete > > > > > Auth Type Support : NONE MD5 PASSWORD > > > > > Auth Type Enable : Callback : > > > > > : User : > > > > > : Operator : > > > > > : Admin : MD5 PASSWORD > > > > > : OEM : > > > > > IP Address Source : Static Address > > > > > IP Address : 192.168.1.211 > > > > > Subnet Mask : 255.255.255.0 > > > > > MAC Address : 00:0e:0c:ea:92:a2 > > > > > [...] > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -a MD5 -u admin -p relation > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > [root@tpw ~]# > > > > > -------------------------------------------------------------------------- > > > > > > > > > > Also compiling the newest version and using it does not help: > > > > > -------------------------------------------------------------------------- > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > [root@tpw ~]# rpm -q freeipmi > > > > > freeipmi-0.7.11-1.fc9.i386 > > > > > [root@tpw ~]# > > > > > -------------------------------------------------------------------------- > > > > > > > > > > In contrast, monitoring a system with a new Supermicro X8DT3-F mainboard > > > > > works fine with freeipmi-0.5.1-3.fc9.i386 and also with > > > > > freeipmi-0.7.11-1.fc9.i386: > > > > > > > > > > -------------------------------------------------------------------------- > > > > > [root@tpw ~]# ipmitool -I lan -H 10.10.10.233 -U ADMIN -P ADMIN sdr > > > > > CPU1 Temp | 0 unspecified | ok > > > > > CPU2 Temp | no reading | ns > > > > > System Temp | 45 degrees C | ok > > > > > CPU1 Vcore | 0.98 Volts | ok > > > > > CPU2 Vcore | no reading | ns > > > > > CPU1 DIMM | 1.51 Volts | ok > > > > > CPU2 DIMM | no reading | ns > > > > > ^C > > > > > [root@tpw ~]# ipmimonitoring -h 10.10.10.233 -u ADMIN -p ADMIN > > > > > Record_ID | Sensor Name | Sensor Group | Monitoring Status| Sensor Units | Sensor Reading > > > > > 4 | System Temp | Temperature | Nominal | C | 45.000000 > > > > > 5 | CPU1 Vcore | Voltage | Nominal | V | 0.976000 > > > > > 6 | CPU2 Vcore | Voltage | Nominal | V | 0.000000 > > > > > 7 | CPU1 DIMM | Voltage | Nominal | V | 1.512000 > > > > > 8 | CPU2 DIMM | Voltage | Nominal | V | 0.000000 > > > > > 9 | +1.5V | Voltage | Nominal | V | 1.504000 > > > > > 10 | +3.3V | Voltage | Nominal | V | 3.240000 > > > > > 11 | +3.3VSB | Voltage | Nominal | V | 3.240000 > > > > > 12 | +5V | Voltage | Nominal | V | 5.120000 > > > > > 13 | +12V | Voltage | Nominal | V | 12.190000 > > > > > 14 | VBAT | Voltage | Nominal | V | 3.240000 > > > > > 15 | Fan1 | Fan | Nominal | RPM | 6528.000000 > > > > > 16 | Fan2 | Fan | Nominal | RPM | 7072.000000 > > > > > 17 | Fan3 | Fan | Nominal | RPM | 0.000000 > > > > > 18 | Fan4 | Fan | Nominal | RPM | 0.000000 > > > > > 19 | Fan5 | Fan | Nominal | RPM | 5644.000000 > > > > > 20 | Fan6 | Fan | Nominal | RPM | 5304.000000 > > > > > 21 | Fan7 | Fan | Nominal | RPM | 7072.000000 > > > > > 22 | Fan8 | Fan | Nominal | RPM | 0.000000 > > > > > 23 | Intrusion | Physical Security | Nominal | N/A | '' > > > > > 24 | PS Failure | Power Supply | Nominal | N/A | '' > > > > > [root@tpw ~]# > > > > > -------------------------------------------------------------------------- > > > > > > > > > > Does anybody have an idea how this problem could be fixed? > > > > > > > > > > best regards, > > > > > Werner > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > Freeipmi-users mailing list > > > > > Freeipmi-users@... > > > > > http://**lists.gnu.org/mailman/listinfo/freeipmi-users > > > > > > > > > > > > > > > > > _______________________________________________ > > > Freeipmi-users mailing list > > > Freeipmi-users@... > > > http://*lists.gnu.org/mailman/listinfo/freeipmi-users > > > _______________________________________________ Freeipmi-users mailing list Freeipmi-users@... http://lists.gnu.org/mailman/listinfo/freeipmi-users |
|
|
Re: "authentication type unavailable for attempted privilege level" with Intel S5000PAL Mainboard
by Al Chu11
::
Rate this Message:
Hi Werner,
Thanks for the feedback. > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 --debug -u admin -p > relation Could you run --debug with the -W "authcap". I'm wondering if it's failing in a different location and the workaround has to be in multiple places. A few other random thoughts. Could you also try different authentication types. Like "-a md2" and "-a straight_password_key". Also, what is the output of "bmc-config --checkout --section=lan_conf_auth", just so we can check to make sure the configuration looks good. Thanks, Al On Mon, 2009-08-24 at 15:31 +0200, Werner Fischer wrote: > Hi Al, > > thanks for the updated tar.gz. I tried it, but somehow it still seems to > cause problems (see below). I'll be two days out of office - so I can do > further tests on Thursday. > > thanks for your support! > > [root@tpw ~]# rpm -q freeipmi > freeipmi-0.7.12.beta2-1.fc9.i386 > [root@tpw ~]# ipmimonitoring -V > ipmimonitoring - 0.7.12.beta2 > Copyright (C) 2007-2008 Lawrence Livermore National Security, LLC. > Copyright (C) 2006-2007 The Regents of the University of California. > This program is free software; you may redistribute it under the terms of > the GNU General Public License. This program has absolutely no warranty. > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > ipmimonitoring: authentication type unavailable for attempted privilege level > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > ipmimonitoring: authentication type unavailable for attempted privilege level > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="authcap" -u admin -p relation > ipmimonitoring: authentication type unavailable for attempted privilege level > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 --debug -u admin -p relation > 192.168.1.211: ===================================================== > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Request > 192.168.1.211: ===================================================== > 192.168.1.211: RMCP Header: > 192.168.1.211: ------------ > 192.168.1.211: [ 6h] = version[ 8b] > 192.168.1.211: [ 0h] = reserved[ 8b] > 192.168.1.211: [ FFh] = sequence_number[ 8b] > 192.168.1.211: [ 7h] = message_class.class[ 5b] > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > 192.168.1.211: IPMI Session Header: > 192.168.1.211: -------------------- > 192.168.1.211: [ 0h] = authentication_type[ 8b] > 192.168.1.211: [ 0h] = session_sequence_number[32b] > 192.168.1.211: [ 0h] = session_id[32b] > 192.168.1.211: [ 9h] = ipmi_msg_len[ 8b] > 192.168.1.211: IPMI Message Header: > 192.168.1.211: -------------------- > 192.168.1.211: [ 20h] = rs_addr[ 8b] > 192.168.1.211: [ 0h] = rs_lun[ 2b] > 192.168.1.211: [ 6h] = net_fn[ 6b] > 192.168.1.211: [ C8h] = checksum1[ 8b] > 192.168.1.211: [ 81h] = rq_addr[ 8b] > 192.168.1.211: [ 0h] = rq_lun[ 2b] > 192.168.1.211: [ 13h] = rq_seq[ 6b] > 192.168.1.211: IPMI Command Data: > 192.168.1.211: ------------------ > 192.168.1.211: [ 38h] = cmd[ 8b] > 192.168.1.211: [ Eh] = channel_number[ 4b] > 192.168.1.211: [ 0h] = reserved1[ 4b] > 192.168.1.211: [ 3h] = maximum_privilege_level[ 4b] > 192.168.1.211: [ 0h] = reserved2[ 4b] > 192.168.1.211: IPMI Trailer: > 192.168.1.211: -------------- > 192.168.1.211: [ EAh] = checksum2[ 8b] > 192.168.1.211: ===================================================== > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Response > 192.168.1.211: ===================================================== > 192.168.1.211: RMCP Header: > 192.168.1.211: ------------ > 192.168.1.211: [ 6h] = version[ 8b] > 192.168.1.211: [ 0h] = reserved[ 8b] > 192.168.1.211: [ FFh] = sequence_number[ 8b] > 192.168.1.211: [ 7h] = message_class.class[ 5b] > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > 192.168.1.211: IPMI Session Header: > 192.168.1.211: -------------------- > 192.168.1.211: [ 0h] = authentication_type[ 8b] > 192.168.1.211: [ 0h] = session_sequence_number[32b] > 192.168.1.211: [ 0h] = session_id[32b] > 192.168.1.211: [ 10h] = ipmi_msg_len[ 8b] > 192.168.1.211: IPMI Message Header: > 192.168.1.211: -------------------- > 192.168.1.211: [ 81h] = rq_addr[ 8b] > 192.168.1.211: [ 0h] = rq_lun[ 2b] > 192.168.1.211: [ 7h] = net_fn[ 6b] > 192.168.1.211: [ 63h] = checksum1[ 8b] > 192.168.1.211: [ 20h] = rs_addr[ 8b] > 192.168.1.211: [ 0h] = rs_lun[ 2b] > 192.168.1.211: [ 13h] = rq_seq[ 6b] > 192.168.1.211: IPMI Command Data: > 192.168.1.211: ------------------ > 192.168.1.211: [ 38h] = cmd[ 8b] > 192.168.1.211: [ 0h] = comp_code[ 8b] > 192.168.1.211: [ 1h] = channel_number[ 8b] > 192.168.1.211: [ 0h] = authentication_type.none[ 1b] > 192.168.1.211: [ 0h] = authentication_type.md2[ 1b] > 192.168.1.211: [ 0h] = authentication_type.md5[ 1b] > 192.168.1.211: [ 0h] = authentication_type.reserved1[ 1b] > 192.168.1.211: [ 0h] = authentication_type.straight_password_key[ 1b] > 192.168.1.211: [ 0h] = authentication_type.oem_prop[ 1b] > 192.168.1.211: [ 0h] = authentication_type.reserved2[ 2b] > 192.168.1.211: [ 0h] = authentication_status.anonymous_login[ 1b] > 192.168.1.211: [ 0h] = authentication_status.null_username[ 1b] > 192.168.1.211: [ 1h] = authentication_status.non_null_username[ 1b] > 192.168.1.211: [ 0h] = authentication_status.user_level_authentication[ 1b] > 192.168.1.211: [ 0h] = authentication_status.per_message_authentication[ 1b] > 192.168.1.211: [ 0h] = authentication_status.reserved[ 3b] > 192.168.1.211: [ 0h] = reserved1[ 8b] > 192.168.1.211: [ 0h] = oem_id[24b] > 192.168.1.211: [ 0h] = oem_auxiliary_data[ 8b] > 192.168.1.211: IPMI Trailer: > 192.168.1.211: -------------- > 192.168.1.211: [ 57h] = checksum2[ 8b] > ipmimonitoring: authentication type unavailable for attempted privilege level > [root@tpw ~]# > > > On Fri, 2009-08-21 at 14:03 -0700, Al Chu wrote: > > Hi Werner, > > > > I've got a test tar.gz here: > > > > http://*ftp.gluster.com/pub/freeipmi/qa-release/freeipmi-0.7.12.beta2.tar.gz > > > > This makes it so the 'authcap' workaround should work for you. Can you > > give it a shot to make sure it works? > > > > Thanks, > > Al > > > > On Fri, 2009-08-21 at 08:44 -0700, Al Chu wrote: > > > Hi Werner, > > > > > > > 192.168.1.211: [ 0h] = authentication_type.none[ 1b] > > > > 192.168.1.211: [ 0h] = authentication_type.md2[ 1b] > > > > 192.168.1.211: [ 0h] = authentication_type.md5[ 1b] > > > > 192.168.1.211: [ 0h] = authentication_type.reserved1[ 1b] > > > > 192.168.1.211: [ 0h] = authentication_type.straight_password_key[ 1b] > > > > 192.168.1.211: [ 0h] = authentication_type.oem_prop[ 1b] > > > > > > This indicates that no authentication support is enabled, which is very > > > unlikely of being true (which we could verify via 'bmc-config --checkout > > > --section=lan_conf_auth'). > > > > > > I'll modify the 'authcap' workaround to also encompass this case and > > > post a beta tar.gz for you to check out. > > > > > > Al > > > > > > On Fri, 2009-08-21 at 09:58 +0200, Werner Fischer wrote: > > > > Hi Al, > > > > > > > > thanks for your fast answer. > > > > > > > > Below you find the requested debug output. I'm using version 0.7.11. The > > > > "authcap" workaround does not fix the problem. After executing with > > > > debug to the affected Intel S5000PAL system (IP 192.168.1.211) I again > > > > verified the correct behavior of ipmimonitoring to the other system > > > > (Supermicro) to IP 10.10.10.233. > > > > > > > > [root@tpw ~]# rpm -q freeipmi > > > > freeipmi-0.7.11-1.fc9.i386 > > > > [root@tpw ~]# ipmimonitoring -V > > > > ipmimonitoring - 0.7.11 > > > > Copyright (C) 2007-2008 Lawrence Livermore National Security, LLC. > > > > Copyright (C) 2006-2007 The Regents of the University of California. > > > > This program is free software; you may redistribute it under the terms of > > > > the GNU General Public License. This program has absolutely no warranty. > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="authcap" -u admin -p relation > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 --debug -u admin -p relation > > > > 192.168.1.211: ===================================================== > > > > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Request > > > > 192.168.1.211: ===================================================== > > > > 192.168.1.211: RMCP Header: > > > > 192.168.1.211: ------------ > > > > 192.168.1.211: [ 6h] = version[ 8b] > > > > 192.168.1.211: [ 0h] = reserved[ 8b] > > > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > > > 192.168.1.211: IPMI Session Header: > > > > 192.168.1.211: -------------------- > > > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > > > 192.168.1.211: [ 0h] = session_id[32b] > > > > 192.168.1.211: [ 9h] = ipmi_msg_len[ 8b] > > > > 192.168.1.211: IPMI Message Header: > > > > 192.168.1.211: -------------------- > > > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > > > 192.168.1.211: [ 6h] = net_fn[ 6b] > > > > 192.168.1.211: [ C8h] = checksum1[ 8b] > > > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > > > 192.168.1.211: [ 8h] = rq_seq[ 6b] > > > > 192.168.1.211: IPMI Command Data: > > > > 192.168.1.211: ------------------ > > > > 192.168.1.211: [ 38h] = cmd[ 8b] > > > > 192.168.1.211: [ Eh] = channel_number[ 4b] > > > > 192.168.1.211: [ 0h] = reserved1[ 4b] > > > > 192.168.1.211: [ 3h] = maximum_privilege_level[ 4b] > > > > 192.168.1.211: [ 0h] = reserved2[ 4b] > > > > 192.168.1.211: IPMI Trailer: > > > > 192.168.1.211: -------------- > > > > 192.168.1.211: [ 16h] = checksum2[ 8b] > > > > 192.168.1.211: ===================================================== > > > > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Response > > > > 192.168.1.211: ===================================================== > > > > 192.168.1.211: RMCP Header: > > > > 192.168.1.211: ------------ > > > > 192.168.1.211: [ 6h] = version[ 8b] > > > > 192.168.1.211: [ 0h] = reserved[ 8b] > > > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > > > 192.168.1.211: IPMI Session Header: > > > > 192.168.1.211: -------------------- > > > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > > > 192.168.1.211: [ 0h] = session_id[32b] > > > > 192.168.1.211: [ 10h] = ipmi_msg_len[ 8b] > > > > 192.168.1.211: IPMI Message Header: > > > > 192.168.1.211: -------------------- > > > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > > > 192.168.1.211: [ 7h] = net_fn[ 6b] > > > > 192.168.1.211: [ 63h] = checksum1[ 8b] > > > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > > > 192.168.1.211: [ 8h] = rq_seq[ 6b] > > > > 192.168.1.211: IPMI Command Data: > > > > 192.168.1.211: ------------------ > > > > 192.168.1.211: [ 38h] = cmd[ 8b] > > > > 192.168.1.211: [ 0h] = comp_code[ 8b] > > > > 192.168.1.211: [ 1h] = channel_number[ 8b] > > > > 192.168.1.211: [ 0h] = authentication_type.none[ 1b] > > > > 192.168.1.211: [ 0h] = authentication_type.md2[ 1b] > > > > 192.168.1.211: [ 0h] = authentication_type.md5[ 1b] > > > > 192.168.1.211: [ 0h] = authentication_type.reserved1[ 1b] > > > > 192.168.1.211: [ 0h] = authentication_type.straight_password_key[ 1b] > > > > 192.168.1.211: [ 0h] = authentication_type.oem_prop[ 1b] > > > > 192.168.1.211: [ 0h] = authentication_type.reserved2[ 2b] > > > > 192.168.1.211: [ 0h] = authentication_status.anonymous_login[ 1b] > > > > 192.168.1.211: [ 0h] = authentication_status.null_username[ 1b] > > > > 192.168.1.211: [ 1h] = authentication_status.non_null_username[ 1b] > > > > 192.168.1.211: [ 0h] = authentication_status.user_level_authentication[ 1b] > > > > 192.168.1.211: [ 0h] = authentication_status.per_message_authentication[ 1b] > > > > 192.168.1.211: [ 0h] = authentication_status.reserved[ 3b] > > > > 192.168.1.211: [ 0h] = reserved1[ 8b] > > > > 192.168.1.211: [ 0h] = oem_id[24b] > > > > 192.168.1.211: [ 0h] = oem_auxiliary_data[ 8b] > > > > 192.168.1.211: IPMI Trailer: > > > > 192.168.1.211: -------------- > > > > 192.168.1.211: [ 83h] = checksum2[ 8b] > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > [root@tpw ~]# > > > > [root@tpw ~]# > > > > [root@tpw ~]# > > > > [root@tpw ~]# ipmimonitoring -h 10.10.10.233 -u ADMIN -p ADMIN > > > > Record_ID | Sensor Name | Sensor Group | Monitoring Status| Sensor Units | Sensor Reading > > > > 4 | System Temp | Temperature | Nominal | C | 41.000000 > > > > 5 | CPU1 Vcore | Voltage | Nominal | V | 0.976000 > > > > 7 | CPU1 DIMM | Voltage | Nominal | V | 1.512000 > > > > 9 | +1.5V | Voltage | Nominal | V | 1.504000 > > > > 10 | +3.3V | Voltage | Nominal | V | 3.240000 > > > > 11 | +3.3VSB | Voltage | Nominal | V | 3.240000 > > > > 12 | +5V | Voltage | Nominal | V | 5.120000 > > > > 13 | +12V | Voltage | Nominal | V | 12.190000 > > > > 14 | VBAT | Voltage | Nominal | V | 3.216000 > > > > 15 | Fan1 | Fan | Nominal | RPM | 3264.000000 > > > > 16 | Fan2 | Fan | Nominal | RPM | 3536.000000 > > > > 19 | Fan5 | Fan | Nominal | RPM | 2788.000000 > > > > 20 | Fan6 | Fan | Nominal | RPM | 2652.000000 > > > > 21 | Fan7 | Fan | Nominal | RPM | 3536.000000 > > > > 23 | Intrusion | Physical Security | Nominal | N/A | 'OK' > > > > 24 | PS Failure | Power Supply | Nominal | N/A | 'OK' > > > > [root@tpw ~]# > > > > > > > > Werner > > > > > > > > On Wed, 2009-08-19 at 08:58 -0700, Al Chu wrote: > > > > > Hi Werner, > > > > > > > > > > It's possible the motherboard is not reporting supported authentication > > > > > types correctly. You could give the "authcap" workaround a shot. > > > > > However, if this is being non-compliant in the way that I think it is, > > > > > the "authcap" workaround won't work (b/c it currently handles a > > > > > different non-compliance bug). Could you send me the output from > > > > > --debug? If we can verify the issue, I'll implement a new workaround > > > > > for you. > > > > > > > > > > BTW, if you need the intel20 workarounds for IPMI 2.0, you may need to > > > > > upgrade. There were some bugs found a few releases ago. > > > > > > > > > > 0.7.4 - 12/15/08 > > > > > ---------------- > > > > > <snip> > > > > > o Fix Intel IPMI 2.0 workarounds in all tools/libraries. > > > > > <snip> > > > > > > > > > > Al > > > > > > > > > > On Wed, 2009-08-19 at 14:16 +0200, Werner Fischer wrote: > > > > > > Dear freeipmi users/developers, > > > > > > > > > > > > I'm trying to monitor an Intel SR2500 server (this server has the Intel > > > > > > S5000PAL mainboard in it). > > > > > > > > > > > > While I can monitor it using ipmitool, I keep getting errors with > > > > > > ipmimonitoring from freeipmi. Also using the "-W" parameter for > > > > > > workarounds (as described in the manpage of ipmimonitoring) doesn't > > > > > > help: > > > > > > > > > > > > -------------------------------------------------------------------------- > > > > > > [root@tpw ~]# ipmitool -I lan -H 192.168.1.211 -U admin -P relation sdr > > > > > > BB +1.2V Vtt | 1.20 Volts | ok > > > > > > BB +1.5V AUX | 1.47 Volts | ok > > > > > > BB +1.5V | 1.48 Volts | ok > > > > > > BB +1.8V | 1.79 Volts | ok > > > > > > BB +3.3V | 3.35 Volts | ok > > > > > > BB +3.3V STB | 3.35 Volts | ok > > > > > > ^C > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > > > > > > ipmi_monitoring_sensor_readings_by_record_id: authentication type unavailable for attempted privilege level > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > > > > > > ipmi_monitoring_sensor_readings_by_record_id: authentication type unavailable for attempted privilege level > > > > > > [root@tpw ~]# rpm -q freeipmi > > > > > > freeipmi-0.5.1-3.fc9.i386 > > > > > > [root@tpw ~]# > > > > > > -------------------------------------------------------------------------- > > > > > > > > > > > > I checked the manpage: > > > > > > "authentication type unavailable for attempted privilege level" - The authentication type you wish > > > > > > to authenticate with is not available for this privilege level. Please try again with an alternate > > > > > > authentication type or alternate privilege level. It may also be possible the available authenti- > > > > > > cation types you can authenticate with are not correctly configured on the remote BMC. > > > > > > But the settings at the BMC side seem to be ok: > > > > > > > > > > > > -------------------------------------------------------------------------- > > > > > > [root@tpw ~]# ipmitool -I lan -H 192.168.1.211 -U admin -P relation lan print 1 > > > > > > Set in Progress : Set Complete > > > > > > Auth Type Support : NONE MD5 PASSWORD > > > > > > Auth Type Enable : Callback : > > > > > > : User : > > > > > > : Operator : > > > > > > : Admin : MD5 PASSWORD > > > > > > : OEM : > > > > > > IP Address Source : Static Address > > > > > > IP Address : 192.168.1.211 > > > > > > Subnet Mask : 255.255.255.0 > > > > > > MAC Address : 00:0e:0c:ea:92:a2 > > > > > > [...] > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -a MD5 -u admin -p relation > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > [root@tpw ~]# > > > > > > -------------------------------------------------------------------------- > > > > > > > > > > > > Also compiling the newest version and using it does not help: > > > > > > -------------------------------------------------------------------------- > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > [root@tpw ~]# rpm -q freeipmi > > > > > > freeipmi-0.7.11-1.fc9.i386 > > > > > > [root@tpw ~]# > > > > > > -------------------------------------------------------------------------- > > > > > > > > > > > > In contrast, monitoring a system with a new Supermicro X8DT3-F mainboard > > > > > > works fine with freeipmi-0.5.1-3.fc9.i386 and also with > > > > > > freeipmi-0.7.11-1.fc9.i386: > > > > > > > > > > > > -------------------------------------------------------------------------- > > > > > > [root@tpw ~]# ipmitool -I lan -H 10.10.10.233 -U ADMIN -P ADMIN sdr > > > > > > CPU1 Temp | 0 unspecified | ok > > > > > > CPU2 Temp | no reading | ns > > > > > > System Temp | 45 degrees C | ok > > > > > > CPU1 Vcore | 0.98 Volts | ok > > > > > > CPU2 Vcore | no reading | ns > > > > > > CPU1 DIMM | 1.51 Volts | ok > > > > > > CPU2 DIMM | no reading | ns > > > > > > ^C > > > > > > [root@tpw ~]# ipmimonitoring -h 10.10.10.233 -u ADMIN -p ADMIN > > > > > > Record_ID | Sensor Name | Sensor Group | Monitoring Status| Sensor Units | Sensor Reading > > > > > > 4 | System Temp | Temperature | Nominal | C | 45.000000 > > > > > > 5 | CPU1 Vcore | Voltage | Nominal | V | 0.976000 > > > > > > 6 | CPU2 Vcore | Voltage | Nominal | V | 0.000000 > > > > > > 7 | CPU1 DIMM | Voltage | Nominal | V | 1.512000 > > > > > > 8 | CPU2 DIMM | Voltage | Nominal | V | 0.000000 > > > > > > 9 | +1.5V | Voltage | Nominal | V | 1.504000 > > > > > > 10 | +3.3V | Voltage | Nominal | V | 3.240000 > > > > > > 11 | +3.3VSB | Voltage | Nominal | V | 3.240000 > > > > > > 12 | +5V | Voltage | Nominal | V | 5.120000 > > > > > > 13 | +12V | Voltage | Nominal | V | 12.190000 > > > > > > 14 | VBAT | Voltage | Nominal | V | 3.240000 > > > > > > 15 | Fan1 | Fan | Nominal | RPM | 6528.000000 > > > > > > 16 | Fan2 | Fan | Nominal | RPM | 7072.000000 > > > > > > 17 | Fan3 | Fan | Nominal | RPM | 0.000000 > > > > > > 18 | Fan4 | Fan | Nominal | RPM | 0.000000 > > > > > > 19 | Fan5 | Fan | Nominal | RPM | 5644.000000 > > > > > > 20 | Fan6 | Fan | Nominal | RPM | 5304.000000 > > > > > > 21 | Fan7 | Fan | Nominal | RPM | 7072.000000 > > > > > > 22 | Fan8 | Fan | Nominal | RPM | 0.000000 > > > > > > 23 | Intrusion | Physical Security | Nominal | N/A | '' > > > > > > 24 | PS Failure | Power Supply | Nominal | N/A | '' > > > > > > [root@tpw ~]# > > > > > > -------------------------------------------------------------------------- > > > > > > > > > > > > Does anybody have an idea how this problem could be fixed? > > > > > > > > > > > > best regards, > > > > > > Werner > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > Freeipmi-users mailing list > > > > > > Freeipmi-users@... > > > > > > http://***lists.gnu.org/mailman/listinfo/freeipmi-users > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > Freeipmi-users mailing list > > > > Freeipmi-users@... > > > > http://**lists.gnu.org/mailman/listinfo/freeipmi-users > > > > > > > > _______________________________________________ > Freeipmi-users mailing list > Freeipmi-users@... > http://*lists.gnu.org/mailman/listinfo/freeipmi-users > Albert Chu chu11@... Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory _______________________________________________ Freeipmi-users mailing list Freeipmi-users@... http://lists.gnu.org/mailman/listinfo/freeipmi-users |
|
|
Re: "authentication type unavailable for attempted privilege level" with Intel S5000PAL Mainboard
by Werner Fischer-2
::
Rate this Message:
Hi Al,
sorry for my late reply. Now I'm back in the office. You find my results below: On Mon, 2009-08-24 at 10:40 -0700, Al Chu wrote: > Hi Werner, > > Thanks for the feedback. > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 --debug -u admin -p > > relation > > Could you run --debug with the -W "authcap". I'm wondering if it's > failing in a different location and the workaround has to be in multiple > places. ------------------------------------------------------------------------------------- [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W "authcap" --debug -u admin -p relation 192.168.1.211: ===================================================== 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Request 192.168.1.211: ===================================================== 192.168.1.211: RMCP Header: 192.168.1.211: ------------ 192.168.1.211: [ 6h] = version[ 8b] 192.168.1.211: [ 0h] = reserved[ 8b] 192.168.1.211: [ FFh] = sequence_number[ 8b] 192.168.1.211: [ 7h] = message_class.class[ 5b] 192.168.1.211: [ 0h] = message_class.reserved[ 2b] 192.168.1.211: [ 0h] = message_class.ack[ 1b] 192.168.1.211: IPMI Session Header: 192.168.1.211: -------------------- 192.168.1.211: [ 0h] = authentication_type[ 8b] 192.168.1.211: [ 0h] = session_sequence_number[32b] 192.168.1.211: [ 0h] = session_id[32b] 192.168.1.211: [ 9h] = ipmi_msg_len[ 8b] 192.168.1.211: IPMI Message Header: 192.168.1.211: -------------------- 192.168.1.211: [ 20h] = rs_addr[ 8b] 192.168.1.211: [ 0h] = rs_lun[ 2b] 192.168.1.211: [ 6h] = net_fn[ 6b] 192.168.1.211: [ C8h] = checksum1[ 8b] 192.168.1.211: [ 81h] = rq_addr[ 8b] 192.168.1.211: [ 0h] = rq_lun[ 2b] 192.168.1.211: [ 33h] = rq_seq[ 6b] 192.168.1.211: IPMI Command Data: 192.168.1.211: ------------------ 192.168.1.211: [ 38h] = cmd[ 8b] 192.168.1.211: [ Eh] = channel_number[ 4b] 192.168.1.211: [ 0h] = reserved1[ 4b] 192.168.1.211: [ 3h] = maximum_privilege_level[ 4b] 192.168.1.211: [ 0h] = reserved2[ 4b] 192.168.1.211: IPMI Trailer: 192.168.1.211: -------------- 192.168.1.211: [ 6Ah] = checksum2[ 8b] 192.168.1.211: ===================================================== 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Response 192.168.1.211: ===================================================== 192.168.1.211: RMCP Header: 192.168.1.211: ------------ 192.168.1.211: [ 6h] = version[ 8b] 192.168.1.211: [ 0h] = reserved[ 8b] 192.168.1.211: [ FFh] = sequence_number[ 8b] 192.168.1.211: [ 7h] = message_class.class[ 5b] 192.168.1.211: [ 0h] = message_class.reserved[ 2b] 192.168.1.211: [ 0h] = message_class.ack[ 1b] 192.168.1.211: IPMI Session Header: 192.168.1.211: -------------------- 192.168.1.211: [ 0h] = authentication_type[ 8b] 192.168.1.211: [ 0h] = session_sequence_number[32b] 192.168.1.211: [ 0h] = session_id[32b] 192.168.1.211: [ 10h] = ipmi_msg_len[ 8b] 192.168.1.211: IPMI Message Header: 192.168.1.211: -------------------- 192.168.1.211: [ 81h] = rq_addr[ 8b] 192.168.1.211: [ 0h] = rq_lun[ 2b] 192.168.1.211: [ 7h] = net_fn[ 6b] 192.168.1.211: [ 63h] = checksum1[ 8b] 192.168.1.211: [ 20h] = rs_addr[ 8b] 192.168.1.211: [ 0h] = rs_lun[ 2b] 192.168.1.211: [ 33h] = rq_seq[ 6b] 192.168.1.211: IPMI Command Data: 192.168.1.211: ------------------ 192.168.1.211: [ 38h] = cmd[ 8b] 192.168.1.211: [ 0h] = comp_code[ 8b] 192.168.1.211: [ 1h] = channel_number[ 8b] 192.168.1.211: [ 0h] = authentication_type.none[ 1b] 192.168.1.211: [ 0h] = authentication_type.md2[ 1b] 192.168.1.211: [ 0h] = authentication_type.md5[ 1b] 192.168.1.211: [ 0h] = authentication_type.reserved1[ 1b] 192.168.1.211: [ 0h] = authentication_type.straight_password_key[ 1b] 192.168.1.211: [ 0h] = authentication_type.oem_prop[ 1b] 192.168.1.211: [ 0h] = authentication_type.reserved2[ 2b] 192.168.1.211: [ 0h] = authentication_status.anonymous_login[ 1b] 192.168.1.211: [ 0h] = authentication_status.null_username[ 1b] 192.168.1.211: [ 1h] = authentication_status.non_null_username[ 1b] 192.168.1.211: [ 0h] = authentication_status.user_level_authentication[ 1b] 192.168.1.211: [ 0h] = authentication_status.per_message_authentication[ 1b] 192.168.1.211: [ 0h] = authentication_status.reserved[ 3b] 192.168.1.211: [ 0h] = reserved1[ 8b] 192.168.1.211: [ 0h] = oem_id[24b] 192.168.1.211: [ 0h] = oem_auxiliary_data[ 8b] 192.168.1.211: IPMI Trailer: 192.168.1.211: -------------- 192.168.1.211: [ D7h] = checksum2[ 8b] 192.168.1.211: ===================================================== 192.168.1.211: IPMI 1.5 Get Session Challenge Request 192.168.1.211: ===================================================== 192.168.1.211: RMCP Header: 192.168.1.211: ------------ 192.168.1.211: [ 6h] = version[ 8b] 192.168.1.211: [ 0h] = reserved[ 8b] 192.168.1.211: [ FFh] = sequence_number[ 8b] 192.168.1.211: [ 7h] = message_class.class[ 5b] 192.168.1.211: [ 0h] = message_class.reserved[ 2b] 192.168.1.211: [ 0h] = message_class.ack[ 1b] 192.168.1.211: IPMI Session Header: 192.168.1.211: -------------------- 192.168.1.211: [ 0h] = authentication_type[ 8b] 192.168.1.211: [ 0h] = session_sequence_number[32b] 192.168.1.211: [ 0h] = session_id[32b] 192.168.1.211: [ 18h] = ipmi_msg_len[ 8b] 192.168.1.211: IPMI Message Header: 192.168.1.211: -------------------- 192.168.1.211: [ 20h] = rs_addr[ 8b] 192.168.1.211: [ 0h] = rs_lun[ 2b] 192.168.1.211: [ 6h] = net_fn[ 6b] 192.168.1.211: [ C8h] = checksum1[ 8b] 192.168.1.211: [ 81h] = rq_addr[ 8b] 192.168.1.211: [ 0h] = rq_lun[ 2b] 192.168.1.211: [ 34h] = rq_seq[ 6b] 192.168.1.211: IPMI Command Data: 192.168.1.211: ------------------ 192.168.1.211: [ 39h] = cmd[ 8b] 192.168.1.211: [ 2h] = authentication_type[ 4b] 192.168.1.211: [ 0h] = reserved[ 4b] 192.168.1.211: [ BYTE ARRAY ... ] = user_name[16B] 192.168.1.211: [ 61h 64h 6Dh 69h 6Eh 00h 00h 00h ] 192.168.1.211: [ 00h 00h 00h 00h 00h 00h 00h 00h ] 192.168.1.211: IPMI Trailer: 192.168.1.211: -------------- 192.168.1.211: [ 6Bh] = checksum2[ 8b] 192.168.1.211: ===================================================== 192.168.1.211: IPMI 1.5 Get Session Challenge Response 192.168.1.211: ===================================================== 192.168.1.211: RMCP Header: 192.168.1.211: ------------ 192.168.1.211: [ 6h] = version[ 8b] 192.168.1.211: [ 0h] = reserved[ 8b] 192.168.1.211: [ FFh] = sequence_number[ 8b] 192.168.1.211: [ 7h] = message_class.class[ 5b] 192.168.1.211: [ 0h] = message_class.reserved[ 2b] 192.168.1.211: [ 0h] = message_class.ack[ 1b] 192.168.1.211: IPMI Session Header: 192.168.1.211: -------------------- 192.168.1.211: [ 0h] = authentication_type[ 8b] 192.168.1.211: [ 0h] = session_sequence_number[32b] 192.168.1.211: [ 0h] = session_id[32b] 192.168.1.211: [ 1Ch] = ipmi_msg_len[ 8b] 192.168.1.211: IPMI Message Header: 192.168.1.211: -------------------- 192.168.1.211: [ 81h] = rq_addr[ 8b] 192.168.1.211: [ 0h] = rq_lun[ 2b] 192.168.1.211: [ 7h] = net_fn[ 6b] 192.168.1.211: [ 63h] = checksum1[ 8b] 192.168.1.211: [ 20h] = rs_addr[ 8b] 192.168.1.211: [ 0h] = rs_lun[ 2b] 192.168.1.211: [ 34h] = rq_seq[ 6b] 192.168.1.211: IPMI Command Data: 192.168.1.211: ------------------ 192.168.1.211: [ 39h] = cmd[ 8b] 192.168.1.211: [ 0h] = comp_code[ 8b] 192.168.1.211: [ AC03D99h] = temp_session_id[32b] 192.168.1.211: [ BYTE ARRAY ... ] = challenge_string[16B] 192.168.1.211: [ 69h F4h 8Ah 89h 60h E4h E2h 1Ch ] 192.168.1.211: [ 2Ah CCh 96h A0h 6Dh 5Ah CAh 7Ah ] 192.168.1.211: IPMI Trailer: 192.168.1.211: -------------- 192.168.1.211: [ 4Eh] = checksum2[ 8b] 192.168.1.211: ===================================================== 192.168.1.211: IPMI 1.5 Activiate Session Request 192.168.1.211: ===================================================== 192.168.1.211: RMCP Header: 192.168.1.211: ------------ 192.168.1.211: [ 6h] = version[ 8b] 192.168.1.211: [ 0h] = reserved[ 8b] 192.168.1.211: [ FFh] = sequence_number[ 8b] 192.168.1.211: [ 7h] = message_class.class[ 5b] 192.168.1.211: [ 0h] = message_class.reserved[ 2b] 192.168.1.211: [ 0h] = message_class.ack[ 1b] 192.168.1.211: IPMI Session Header: 192.168.1.211: -------------------- 192.168.1.211: [ 2h] = authentication_type[ 8b] 192.168.1.211: [ 0h] = session_sequence_number[32b] 192.168.1.211: [ AC03D99h] = session_id[32b] 192.168.1.211: [ BYTE ARRAY ... ] = authentication_code[16B] 192.168.1.211: [ 6Bh 25h AAh 78h 0Bh D3h F8h 14h ] 192.168.1.211: [ C4h 57h 15h 6Eh 15h C3h 15h F6h ] 192.168.1.211: [ 1Dh] = ipmi_msg_len[ 8b] 192.168.1.211: IPMI Message Header: 192.168.1.211: -------------------- 192.168.1.211: [ 20h] = rs_addr[ 8b] 192.168.1.211: [ 0h] = rs_lun[ 2b] 192.168.1.211: [ 6h] = net_fn[ 6b] 192.168.1.211: [ C8h] = checksum1[ 8b] 192.168.1.211: [ 81h] = rq_addr[ 8b] 192.168.1.211: [ 0h] = rq_lun[ 2b] 192.168.1.211: [ 35h] = rq_seq[ 6b] 192.168.1.211: IPMI Command Data: 192.168.1.211: ------------------ 192.168.1.211: [ 3Ah] = cmd[ 8b] 192.168.1.211: [ 2h] = authentication_type[ 4b] 192.168.1.211: [ 0h] = reserved1[ 4b] 192.168.1.211: [ 3h] = maximum_privilege_level[ 4b] 192.168.1.211: [ 0h] = reserved2[ 4b] 192.168.1.211: [ BYTE ARRAY ... ] = challenge_string[16B] 192.168.1.211: [ 69h F4h 8Ah 89h 60h E4h E2h 1Ch ] 192.168.1.211: [ 2Ah CCh 96h A0h 6Dh 5Ah CAh 7Ah ] 192.168.1.211: [ 279F274Fh] = initial_outbound_sequence_number[32b] 192.168.1.211: IPMI Trailer: 192.168.1.211: -------------- 192.168.1.211: [ 47h] = checksum2[ 8b] 192.168.1.211: ===================================================== 192.168.1.211: IPMI 1.5 Activiate Session Response 192.168.1.211: ===================================================== 192.168.1.211: RMCP Header: 192.168.1.211: ------------ 192.168.1.211: [ 6h] = version[ 8b] 192.168.1.211: [ 0h] = reserved[ 8b] 192.168.1.211: [ FFh] = sequence_number[ 8b] 192.168.1.211: [ 7h] = message_class.class[ 5b] 192.168.1.211: [ 0h] = message_class.reserved[ 2b] 192.168.1.211: [ 0h] = message_class.ack[ 1b] 192.168.1.211: IPMI Session Header: 192.168.1.211: -------------------- 192.168.1.211: [ 2h] = authentication_type[ 8b] 192.168.1.211: [ 0h] = session_sequence_number[32b] 192.168.1.211: [ AC03D99h] = session_id[32b] 192.168.1.211: [ BYTE ARRAY ... ] = authentication_code[16B] 192.168.1.211: [ 29h BCh 75h CEh 94h F5h 23h 0Eh ] 192.168.1.211: [ A9h A9h 97h FFh 58h 22h C4h 89h ] 192.168.1.211: [ 8h] = ipmi_msg_len[ 8b] 192.168.1.211: IPMI Message Header: 192.168.1.211: -------------------- 192.168.1.211: [ 81h] = rq_addr[ 8b] 192.168.1.211: [ 0h] = rq_lun[ 2b] 192.168.1.211: [ 7h] = net_fn[ 6b] 192.168.1.211: [ 63h] = checksum1[ 8b] 192.168.1.211: [ 20h] = rs_addr[ 8b] 192.168.1.211: [ 0h] = rs_lun[ 2b] 192.168.1.211: [ 35h] = rq_seq[ 6b] 192.168.1.211: IPMI Command Data: 192.168.1.211: ------------------ 192.168.1.211: [ 3Ah] = cmd[ 8b] 192.168.1.211: [ CCh] = comp_code[ 8b] 192.168.1.211: IPMI Trailer: 192.168.1.211: -------------- 192.168.1.211: [ 6h] = checksum2[ 8b] ipmi_ctx_open_outofband: bad completion code: request data/parameter invalid [root@tpw ~]# ------------------------------------------------------------------------------------- > > A few other random thoughts. > > Could you also try different authentication types. Like "-a md2" and > "-a straight_password_key". [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="authcap" -u admin -p relation ipmimonitoring: authentication type unavailable for attempted privilege level [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="authcap" -a md2 -u admin -p relation ipmimonitoring: authentication type unavailable for attempted privilege level [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="authcap" -a STRAIGHT_PASSWORD_KEY -u admin -p relation ipmimonitoring: authentication type unavailable for attempted privilege level [root@tpw ~]# > > Also, what is the output of "bmc-config --checkout > --section=lan_conf_auth", just so we can check to make sure the > configuration looks good. I ran the command remotely as I have currently no Linux installed on the box (if it is necessary, just tell me, than I can put a Linux on it and run bmc-config locally): [root@tpw ~]# bmc-config -h 192.168.1.211 -u admin -p relation --checkout --section=lan_conf_auth # # Section Lan_Conf_Auth Comments # # In the Lan_Conf_Auth section, allowable authentication mechanisms for IPMI 1.5 # is configured. Most users will want to set all "MD5" authentication to "Yes" # and the rest to "No". If you have configured a NULL username and a NULL # password, you will also want to configure some of the "None" fields to "Yes" # to allow "None" authentication to work. Some motherboards do not allow you to # enable OEM authentication, so you may wish to set all OEM related fields to # "No". # Section Lan_Conf_Auth ## Possible values: Yes/No Callback_Enable_Auth_Type_None No ## Possible values: Yes/No Callback_Enable_Auth_Type_MD5 No ## Possible values: Yes/No Callback_Enable_Auth_Type_Straight_Password No ## Possible values: Yes/No User_Enable_Auth_Type_None No ## Possible values: Yes/No User_Enable_Auth_Type_MD5 No ## Possible values: Yes/No User_Enable_Auth_Type_Straight_Password No ## Possible values: Yes/No Operator_Enable_Auth_Type_None No ## Possible values: Yes/No Operator_Enable_Auth_Type_MD5 No ## Possible values: Yes/No Operator_Enable_Auth_Type_Straight_Password No ## Possible values: Yes/No Admin_Enable_Auth_Type_None No ## Possible values: Yes/No Admin_Enable_Auth_Type_MD5 Yes ## Possible values: Yes/No Admin_Enable_Auth_Type_Straight_Password Yes ## Possible values: Yes/No OEM_Enable_Auth_Type_None No ## Possible values: Yes/No OEM_Enable_Auth_Type_MD5 No ## Possible values: Yes/No OEM_Enable_Auth_Type_Straight_Password No EndSection [root@tpw ~]# If you need any further results, just let me know! Thanks for your support, Werner > > Thanks, > > Al > > On Mon, 2009-08-24 at 15:31 +0200, Werner Fischer wrote: > > Hi Al, > > > > thanks for the updated tar.gz. I tried it, but somehow it still seems to > > cause problems (see below). I'll be two days out of office - so I can do > > further tests on Thursday. > > > > thanks for your support! > > > > [root@tpw ~]# rpm -q freeipmi > > freeipmi-0.7.12.beta2-1.fc9.i386 > > [root@tpw ~]# ipmimonitoring -V > > ipmimonitoring - 0.7.12.beta2 > > Copyright (C) 2007-2008 Lawrence Livermore National Security, LLC. > > Copyright (C) 2006-2007 The Regents of the University of California. > > This program is free software; you may redistribute it under the terms of > > the GNU General Public License. This program has absolutely no warranty. > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > > ipmimonitoring: authentication type unavailable for attempted privilege level > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > > ipmimonitoring: authentication type unavailable for attempted privilege level > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="authcap" -u admin -p relation > > ipmimonitoring: authentication type unavailable for attempted privilege level > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 --debug -u admin -p relation > > 192.168.1.211: ===================================================== > > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Request > > 192.168.1.211: ===================================================== > > 192.168.1.211: RMCP Header: > > 192.168.1.211: ------------ > > 192.168.1.211: [ 6h] = version[ 8b] > > 192.168.1.211: [ 0h] = reserved[ 8b] > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > 192.168.1.211: IPMI Session Header: > > 192.168.1.211: -------------------- > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > 192.168.1.211: [ 0h] = session_id[32b] > > 192.168.1.211: [ 9h] = ipmi_msg_len[ 8b] > > 192.168.1.211: IPMI Message Header: > > 192.168.1.211: -------------------- > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > 192.168.1.211: [ 6h] = net_fn[ 6b] > > 192.168.1.211: [ C8h] = checksum1[ 8b] > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > 192.168.1.211: [ 13h] = rq_seq[ 6b] > > 192.168.1.211: IPMI Command Data: > > 192.168.1.211: ------------------ > > 192.168.1.211: [ 38h] = cmd[ 8b] > > 192.168.1.211: [ Eh] = channel_number[ 4b] > > 192.168.1.211: [ 0h] = reserved1[ 4b] > > 192.168.1.211: [ 3h] = maximum_privilege_level[ 4b] > > 192.168.1.211: [ 0h] = reserved2[ 4b] > > 192.168.1.211: IPMI Trailer: > > 192.168.1.211: -------------- > > 192.168.1.211: [ EAh] = checksum2[ 8b] > > 192.168.1.211: ===================================================== > > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Response > > 192.168.1.211: ===================================================== > > 192.168.1.211: RMCP Header: > > 192.168.1.211: ------------ > > 192.168.1.211: [ 6h] = version[ 8b] > > 192.168.1.211: [ 0h] = reserved[ 8b] > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > 192.168.1.211: IPMI Session Header: > > 192.168.1.211: -------------------- > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > 192.168.1.211: [ 0h] = session_id[32b] > > 192.168.1.211: [ 10h] = ipmi_msg_len[ 8b] > > 192.168.1.211: IPMI Message Header: > > 192.168.1.211: -------------------- > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > 192.168.1.211: [ 7h] = net_fn[ 6b] > > 192.168.1.211: [ 63h] = checksum1[ 8b] > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > 192.168.1.211: [ 13h] = rq_seq[ 6b] > > 192.168.1.211: IPMI Command Data: > > 192.168.1.211: ------------------ > > 192.168.1.211: [ 38h] = cmd[ 8b] > > 192.168.1.211: [ 0h] = comp_code[ 8b] > > 192.168.1.211: [ 1h] = channel_number[ 8b] > > 192.168.1.211: [ 0h] = authentication_type.none[ 1b] > > 192.168.1.211: [ 0h] = authentication_type.md2[ 1b] > > 192.168.1.211: [ 0h] = authentication_type.md5[ 1b] > > 192.168.1.211: [ 0h] = authentication_type.reserved1[ 1b] > > 192.168.1.211: [ 0h] = authentication_type.straight_password_key[ 1b] > > 192.168.1.211: [ 0h] = authentication_type.oem_prop[ 1b] > > 192.168.1.211: [ 0h] = authentication_type.reserved2[ 2b] > > 192.168.1.211: [ 0h] = authentication_status.anonymous_login[ 1b] > > 192.168.1.211: [ 0h] = authentication_status.null_username[ 1b] > > 192.168.1.211: [ 1h] = authentication_status.non_null_username[ 1b] > > 192.168.1.211: [ 0h] = authentication_status.user_level_authentication[ 1b] > > 192.168.1.211: [ 0h] = authentication_status.per_message_authentication[ 1b] > > 192.168.1.211: [ 0h] = authentication_status.reserved[ 3b] > > 192.168.1.211: [ 0h] = reserved1[ 8b] > > 192.168.1.211: [ 0h] = oem_id[24b] > > 192.168.1.211: [ 0h] = oem_auxiliary_data[ 8b] > > 192.168.1.211: IPMI Trailer: > > 192.168.1.211: -------------- > > 192.168.1.211: [ 57h] = checksum2[ 8b] > > ipmimonitoring: authentication type unavailable for attempted privilege level > > [root@tpw ~]# > > > > > > On Fri, 2009-08-21 at 14:03 -0700, Al Chu wrote: > > > Hi Werner, > > > > > > I've got a test tar.gz here: > > > > > > http://*ftp.gluster.com/pub/freeipmi/qa-release/freeipmi-0.7.12.beta2.tar.gz > > > > > > This makes it so the 'authcap' workaround should work for you. Can you > > > give it a shot to make sure it works? > > > > > > Thanks, > > > Al > > > > > > On Fri, 2009-08-21 at 08:44 -0700, Al Chu wrote: > > > > Hi Werner, > > > > > > > > > 192.168.1.211: [ 0h] = authentication_type.none[ 1b] > > > > > 192.168.1.211: [ 0h] = authentication_type.md2[ 1b] > > > > > 192.168.1.211: [ 0h] = authentication_type.md5[ 1b] > > > > > 192.168.1.211: [ 0h] = authentication_type.reserved1[ 1b] > > > > > 192.168.1.211: [ 0h] = authentication_type.straight_password_key[ 1b] > > > > > 192.168.1.211: [ 0h] = authentication_type.oem_prop[ 1b] > > > > > > > > This indicates that no authentication support is enabled, which is very > > > > unlikely of being true (which we could verify via 'bmc-config --checkout > > > > --section=lan_conf_auth'). > > > > > > > > I'll modify the 'authcap' workaround to also encompass this case and > > > > post a beta tar.gz for you to check out. > > > > > > > > Al > > > > > > > > On Fri, 2009-08-21 at 09:58 +0200, Werner Fischer wrote: > > > > > Hi Al, > > > > > > > > > > thanks for your fast answer. > > > > > > > > > > Below you find the requested debug output. I'm using version 0.7.11. The > > > > > "authcap" workaround does not fix the problem. After executing with > > > > > debug to the affected Intel S5000PAL system (IP 192.168.1.211) I again > > > > > verified the correct behavior of ipmimonitoring to the other system > > > > > (Supermicro) to IP 10.10.10.233. > > > > > > > > > > [root@tpw ~]# rpm -q freeipmi > > > > > freeipmi-0.7.11-1.fc9.i386 > > > > > [root@tpw ~]# ipmimonitoring -V > > > > > ipmimonitoring - 0.7.11 > > > > > Copyright (C) 2007-2008 Lawrence Livermore National Security, LLC. > > > > > Copyright (C) 2006-2007 The Regents of the University of California. > > > > > This program is free software; you may redistribute it under the terms of > > > > > the GNU General Public License. This program has absolutely no warranty. > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="authcap" -u admin -p relation > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 --debug -u admin -p relation > > > > > 192.168.1.211: ===================================================== > > > > > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Request > > > > > 192.168.1.211: ===================================================== > > > > > 192.168.1.211: RMCP Header: > > > > > 192.168.1.211: ------------ > > > > > 192.168.1.211: [ 6h] = version[ 8b] > > > > > 192.168.1.211: [ 0h] = reserved[ 8b] > > > > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > > > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > > > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > > > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > > > > 192.168.1.211: IPMI Session Header: > > > > > 192.168.1.211: -------------------- > > > > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > > > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > > > > 192.168.1.211: [ 0h] = session_id[32b] > > > > > 192.168.1.211: [ 9h] = ipmi_msg_len[ 8b] > > > > > 192.168.1.211: IPMI Message Header: > > > > > 192.168.1.211: -------------------- > > > > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > > > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > > > > 192.168.1.211: [ 6h] = net_fn[ 6b] > > > > > 192.168.1.211: [ C8h] = checksum1[ 8b] > > > > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > > > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > > > > 192.168.1.211: [ 8h] = rq_seq[ 6b] > > > > > 192.168.1.211: IPMI Command Data: > > > > > 192.168.1.211: ------------------ > > > > > 192.168.1.211: [ 38h] = cmd[ 8b] > > > > > 192.168.1.211: [ Eh] = channel_number[ 4b] > > > > > 192.168.1.211: [ 0h] = reserved1[ 4b] > > > > > 192.168.1.211: [ 3h] = maximum_privilege_level[ 4b] > > > > > 192.168.1.211: [ 0h] = reserved2[ 4b] > > > > > 192.168.1.211: IPMI Trailer: > > > > > 192.168.1.211: -------------- > > > > > 192.168.1.211: [ 16h] = checksum2[ 8b] > > > > > 192.168.1.211: ===================================================== > > > > > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Response > > > > > 192.168.1.211: ===================================================== > > > > > 192.168.1.211: RMCP Header: > > > > > 192.168.1.211: ------------ > > > > > 192.168.1.211: [ 6h] = version[ 8b] > > > > > 192.168.1.211: [ 0h] = reserved[ 8b] > > > > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > > > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > > > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > > > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > > > > 192.168.1.211: IPMI Session Header: > > > > > 192.168.1.211: -------------------- > > > > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > > > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > > > > 192.168.1.211: [ 0h] = session_id[32b] > > > > > 192.168.1.211: [ 10h] = ipmi_msg_len[ 8b] > > > > > 192.168.1.211: IPMI Message Header: > > > > > 192.168.1.211: -------------------- > > > > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > > > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > > > > 192.168.1.211: [ 7h] = net_fn[ 6b] > > > > > 192.168.1.211: [ 63h] = checksum1[ 8b] > > > > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > > > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > > > > 192.168.1.211: [ 8h] = rq_seq[ 6b] > > > > > 192.168.1.211: IPMI Command Data: > > > > > 192.168.1.211: ------------------ > > > > > 192.168.1.211: [ 38h] = cmd[ 8b] > > > > > 192.168.1.211: [ 0h] = comp_code[ 8b] > > > > > 192.168.1.211: [ 1h] = channel_number[ 8b] > > > > > 192.168.1.211: [ 0h] = authentication_type.none[ 1b] > > > > > 192.168.1.211: [ 0h] = authentication_type.md2[ 1b] > > > > > 192.168.1.211: [ 0h] = authentication_type.md5[ 1b] > > > > > 192.168.1.211: [ 0h] = authentication_type.reserved1[ 1b] > > > > > 192.168.1.211: [ 0h] = authentication_type.straight_password_key[ 1b] > > > > > 192.168.1.211: [ 0h] = authentication_type.oem_prop[ 1b] > > > > > 192.168.1.211: [ 0h] = authentication_type.reserved2[ 2b] > > > > > 192.168.1.211: [ 0h] = authentication_status.anonymous_login[ 1b] > > > > > 192.168.1.211: [ 0h] = authentication_status.null_username[ 1b] > > > > > 192.168.1.211: [ 1h] = authentication_status.non_null_username[ 1b] > > > > > 192.168.1.211: [ 0h] = authentication_status.user_level_authentication[ 1b] > > > > > 192.168.1.211: [ 0h] = authentication_status.per_message_authentication[ 1b] > > > > > 192.168.1.211: [ 0h] = authentication_status.reserved[ 3b] > > > > > 192.168.1.211: [ 0h] = reserved1[ 8b] > > > > > 192.168.1.211: [ 0h] = oem_id[24b] > > > > > 192.168.1.211: [ 0h] = oem_auxiliary_data[ 8b] > > > > > 192.168.1.211: IPMI Trailer: > > > > > 192.168.1.211: -------------- > > > > > 192.168.1.211: [ 83h] = checksum2[ 8b] > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > [root@tpw ~]# > > > > > [root@tpw ~]# > > > > > [root@tpw ~]# > > > > > [root@tpw ~]# ipmimonitoring -h 10.10.10.233 -u ADMIN -p ADMIN > > > > > Record_ID | Sensor Name | Sensor Group | Monitoring Status| Sensor Units | Sensor Reading > > > > > 4 | System Temp | Temperature | Nominal | C | 41.000000 > > > > > 5 | CPU1 Vcore | Voltage | Nominal | V | 0.976000 > > > > > 7 | CPU1 DIMM | Voltage | Nominal | V | 1.512000 > > > > > 9 | +1.5V | Voltage | Nominal | V | 1.504000 > > > > > 10 | +3.3V | Voltage | Nominal | V | 3.240000 > > > > > 11 | +3.3VSB | Voltage | Nominal | V | 3.240000 > > > > > 12 | +5V | Voltage | Nominal | V | 5.120000 > > > > > 13 | +12V | Voltage | Nominal | V | 12.190000 > > > > > 14 | VBAT | Voltage | Nominal | V | 3.216000 > > > > > 15 | Fan1 | Fan | Nominal | RPM | 3264.000000 > > > > > 16 | Fan2 | Fan | Nominal | RPM | 3536.000000 > > > > > 19 | Fan5 | Fan | Nominal | RPM | 2788.000000 > > > > > 20 | Fan6 | Fan | Nominal | RPM | 2652.000000 > > > > > 21 | Fan7 | Fan | Nominal | RPM | 3536.000000 > > > > > 23 | Intrusion | Physical Security | Nominal | N/A | 'OK' > > > > > 24 | PS Failure | Power Supply | Nominal | N/A | 'OK' > > > > > [root@tpw ~]# > > > > > > > > > > Werner > > > > > > > > > > On Wed, 2009-08-19 at 08:58 -0700, Al Chu wrote: > > > > > > Hi Werner, > > > > > > > > > > > > It's possible the motherboard is not reporting supported authentication > > > > > > types correctly. You could give the "authcap" workaround a shot. > > > > > > However, if this is being non-compliant in the way that I think it is, > > > > > > the "authcap" workaround won't work (b/c it currently handles a > > > > > > different non-compliance bug). Could you send me the output from > > > > > > --debug? If we can verify the issue, I'll implement a new workaround > > > > > > for you. > > > > > > > > > > > > BTW, if you need the intel20 workarounds for IPMI 2.0, you may need to > > > > > > upgrade. There were some bugs found a few releases ago. > > > > > > > > > > > > 0.7.4 - 12/15/08 > > > > > > ---------------- > > > > > > <snip> > > > > > > o Fix Intel IPMI 2.0 workarounds in all tools/libraries. > > > > > > <snip> > > > > > > > > > > > > Al > > > > > > > > > > > > On Wed, 2009-08-19 at 14:16 +0200, Werner Fischer wrote: > > > > > > > Dear freeipmi users/developers, > > > > > > > > > > > > > > I'm trying to monitor an Intel SR2500 server (this server has the Intel > > > > > > > S5000PAL mainboard in it). > > > > > > > > > > > > > > While I can monitor it using ipmitool, I keep getting errors with > > > > > > > ipmimonitoring from freeipmi. Also using the "-W" parameter for > > > > > > > workarounds (as described in the manpage of ipmimonitoring) doesn't > > > > > > > help: > > > > > > > > > > > > > > -------------------------------------------------------------------------- > > > > > > > [root@tpw ~]# ipmitool -I lan -H 192.168.1.211 -U admin -P relation sdr > > > > > > > BB +1.2V Vtt | 1.20 Volts | ok > > > > > > > BB +1.5V AUX | 1.47 Volts | ok > > > > > > > BB +1.5V | 1.48 Volts | ok > > > > > > > BB +1.8V | 1.79 Volts | ok > > > > > > > BB +3.3V | 3.35 Volts | ok > > > > > > > BB +3.3V STB | 3.35 Volts | ok > > > > > > > ^C > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > > > > > > > ipmi_monitoring_sensor_readings_by_record_id: authentication type unavailable for attempted privilege level > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > > > > > > > ipmi_monitoring_sensor_readings_by_record_id: authentication type unavailable for attempted privilege level > > > > > > > [root@tpw ~]# rpm -q freeipmi > > > > > > > freeipmi-0.5.1-3.fc9.i386 > > > > > > > [root@tpw ~]# > > > > > > > -------------------------------------------------------------------------- > > > > > > > > > > > > > > I checked the manpage: > > > > > > > "authentication type unavailable for attempted privilege level" - The authentication type you wish > > > > > > > to authenticate with is not available for this privilege level. Please try again with an alternate > > > > > > > authentication type or alternate privilege level. It may also be possible the available authenti- > > > > > > > cation types you can authenticate with are not correctly configured on the remote BMC. > > > > > > > But the settings at the BMC side seem to be ok: > > > > > > > > > > > > > > -------------------------------------------------------------------------- > > > > > > > [root@tpw ~]# ipmitool -I lan -H 192.168.1.211 -U admin -P relation lan print 1 > > > > > > > Set in Progress : Set Complete > > > > > > > Auth Type Support : NONE MD5 PASSWORD > > > > > > > Auth Type Enable : Callback : > > > > > > > : User : > > > > > > > : Operator : > > > > > > > : Admin : MD5 PASSWORD > > > > > > > : OEM : > > > > > > > IP Address Source : Static Address > > > > > > > IP Address : 192.168.1.211 > > > > > > > Subnet Mask : 255.255.255.0 > > > > > > > MAC Address : 00:0e:0c:ea:92:a2 > > > > > > > [...] > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -a MD5 -u admin -p relation > > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > > [root@tpw ~]# > > > > > > > -------------------------------------------------------------------------- > > > > > > > > > > > > > > Also compiling the newest version and using it does not help: > > > > > > > -------------------------------------------------------------------------- > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > > [root@tpw ~]# rpm -q freeipmi > > > > > > > freeipmi-0.7.11-1.fc9.i386 > > > > > > > [root@tpw ~]# > > > > > > > -------------------------------------------------------------------------- > > > > > > > > > > > > > > In contrast, monitoring a system with a new Supermicro X8DT3-F mainboard > > > > > > > works fine with freeipmi-0.5.1-3.fc9.i386 and also with > > > > > > > freeipmi-0.7.11-1.fc9.i386: > > > > > > > > > > > > > > -------------------------------------------------------------------------- > > > > > > > [root@tpw ~]# ipmitool -I lan -H 10.10.10.233 -U ADMIN -P ADMIN sdr > > > > > > > CPU1 Temp | 0 unspecified | ok > > > > > > > CPU2 Temp | no reading | ns > > > > > > > System Temp | 45 degrees C | ok > > > > > > > CPU1 Vcore | 0.98 Volts | ok > > > > > > > CPU2 Vcore | no reading | ns > > > > > > > CPU1 DIMM | 1.51 Volts | ok > > > > > > > CPU2 DIMM | no reading | ns > > > > > > > ^C > > > > > > > [root@tpw ~]# ipmimonitoring -h 10.10.10.233 -u ADMIN -p ADMIN > > > > > > > Record_ID | Sensor Name | Sensor Group | Monitoring Status| Sensor Units | Sensor Reading > > > > > > > 4 | System Temp | Temperature | Nominal | C | 45.000000 > > > > > > > 5 | CPU1 Vcore | Voltage | Nominal | V | 0.976000 > > > > > > > 6 | CPU2 Vcore | Voltage | Nominal | V | 0.000000 > > > > > > > 7 | CPU1 DIMM | Voltage | Nominal | V | 1.512000 > > > > > > > 8 | CPU2 DIMM | Voltage | Nominal | V | 0.000000 > > > > > > > 9 | +1.5V | Voltage | Nominal | V | 1.504000 > > > > > > > 10 | +3.3V | Voltage | Nominal | V | 3.240000 > > > > > > > 11 | +3.3VSB | Voltage | Nominal | V | 3.240000 > > > > > > > 12 | +5V | Voltage | Nominal | V | 5.120000 > > > > > > > 13 | +12V | Voltage | Nominal | V | 12.190000 > > > > > > > 14 | VBAT | Voltage | Nominal | V | 3.240000 > > > > > > > 15 | Fan1 | Fan | Nominal | RPM | 6528.000000 > > > > > > > 16 | Fan2 | Fan | Nominal | RPM | 7072.000000 > > > > > > > 17 | Fan3 | Fan | Nominal | RPM | 0.000000 > > > > > > > 18 | Fan4 | Fan | Nominal | RPM | 0.000000 > > > > > > > 19 | Fan5 | Fan | Nominal | RPM | 5644.000000 > > > > > > > 20 | Fan6 | Fan | Nominal | RPM | 5304.000000 > > > > > > > 21 | Fan7 | Fan | Nominal | RPM | 7072.000000 > > > > > > > 22 | Fan8 | Fan | Nominal | RPM | 0.000000 > > > > > > > 23 | Intrusion | Physical Security | Nominal | N/A | '' > > > > > > > 24 | PS Failure | Power Supply | Nominal | N/A | '' > > > > > > > [root@tpw ~]# > > > > > > > -------------------------------------------------------------------------- > > > > > > > > > > > > > > Does anybody have an idea how this problem could be fixed? > > > > > > > > > > > > > > best regards, > > > > > > > Werner > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > Freeipmi-users mailing list > > > > > > > Freeipmi-users@... > > > > > > > http://***lists.gnu.org/mailman/listinfo/freeipmi-users > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > Freeipmi-users mailing list > > > > > Freeipmi-users@... > > > > > http://**lists.gnu.org/mailman/listinfo/freeipmi-users > > > > > > > > > > > > > _______________________________________________ > > Freeipmi-users mailing list > > Freeipmi-users@... > > http://*lists.gnu.org/mailman/listinfo/freeipmi-users > > _______________________________________________ Freeipmi-users mailing list Freeipmi-users@... http://lists.gnu.org/mailman/listinfo/freeipmi-users |
|
|
Re: "authentication type unavailable for attempted privilege level" with Intel S5000PAL Mainboard
by Al Chu11
::
Rate this Message:
Hey Werner,
Actually, your default config may be the issue afterall, not the motherboard. Your default config is not allowing authentication by any privilege level other than "admin". How about trying ipmimonitoring with the -l admin, to tell ipmimonitoring to use the admin privilege level. Out of my curiosity, did the Intel motherboard come like this by default? Al On Mon, 2009-08-31 at 12:18 +0200, Werner Fischer wrote: > Hi Al, > > sorry for my late reply. Now I'm back in the office. You find my results > below: > > On Mon, 2009-08-24 at 10:40 -0700, Al Chu wrote: > > Hi Werner, > > > > Thanks for the feedback. > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 --debug -u admin -p > > > relation > > > > Could you run --debug with the -W "authcap". I'm wondering if it's > > failing in a different location and the workaround has to be in multiple > > places. > sure, here it is: > > ------------------------------------------------------------------------------------- > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W "authcap" --debug -u admin -p relation > 192.168.1.211: ===================================================== > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Request > 192.168.1.211: ===================================================== > 192.168.1.211: RMCP Header: > 192.168.1.211: ------------ > 192.168.1.211: [ 6h] = version[ 8b] > 192.168.1.211: [ 0h] = reserved[ 8b] > 192.168.1.211: [ FFh] = sequence_number[ 8b] > 192.168.1.211: [ 7h] = message_class.class[ 5b] > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > 192.168.1.211: IPMI Session Header: > 192.168.1.211: -------------------- > 192.168.1.211: [ 0h] = authentication_type[ 8b] > 192.168.1.211: [ 0h] = session_sequence_number[32b] > 192.168.1.211: [ 0h] = session_id[32b] > 192.168.1.211: [ 9h] = ipmi_msg_len[ 8b] > 192.168.1.211: IPMI Message Header: > 192.168.1.211: -------------------- > 192.168.1.211: [ 20h] = rs_addr[ 8b] > 192.168.1.211: [ 0h] = rs_lun[ 2b] > 192.168.1.211: [ 6h] = net_fn[ 6b] > 192.168.1.211: [ C8h] = checksum1[ 8b] > 192.168.1.211: [ 81h] = rq_addr[ 8b] > 192.168.1.211: [ 0h] = rq_lun[ 2b] > 192.168.1.211: [ 33h] = rq_seq[ 6b] > 192.168.1.211: IPMI Command Data: > 192.168.1.211: ------------------ > 192.168.1.211: [ 38h] = cmd[ 8b] > 192.168.1.211: [ Eh] = channel_number[ 4b] > 192.168.1.211: [ 0h] = reserved1[ 4b] > 192.168.1.211: [ 3h] = maximum_privilege_level[ 4b] > 192.168.1.211: [ 0h] = reserved2[ 4b] > 192.168.1.211: IPMI Trailer: > 192.168.1.211: -------------- > 192.168.1.211: [ 6Ah] = checksum2[ 8b] > 192.168.1.211: ===================================================== > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Response > 192.168.1.211: ===================================================== > 192.168.1.211: RMCP Header: > 192.168.1.211: ------------ > 192.168.1.211: [ 6h] = version[ 8b] > 192.168.1.211: [ 0h] = reserved[ 8b] > 192.168.1.211: [ FFh] = sequence_number[ 8b] > 192.168.1.211: [ 7h] = message_class.class[ 5b] > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > 192.168.1.211: IPMI Session Header: > 192.168.1.211: -------------------- > 192.168.1.211: [ 0h] = authentication_type[ 8b] > 192.168.1.211: [ 0h] = session_sequence_number[32b] > 192.168.1.211: [ 0h] = session_id[32b] > 192.168.1.211: [ 10h] = ipmi_msg_len[ 8b] > 192.168.1.211: IPMI Message Header: > 192.168.1.211: -------------------- > 192.168.1.211: [ 81h] = rq_addr[ 8b] > 192.168.1.211: [ 0h] = rq_lun[ 2b] > 192.168.1.211: [ 7h] = net_fn[ 6b] > 192.168.1.211: [ 63h] = checksum1[ 8b] > 192.168.1.211: [ 20h] = rs_addr[ 8b] > 192.168.1.211: [ 0h] = rs_lun[ 2b] > 192.168.1.211: [ 33h] = rq_seq[ 6b] > 192.168.1.211: IPMI Command Data: > 192.168.1.211: ------------------ > 192.168.1.211: [ 38h] = cmd[ 8b] > 192.168.1.211: [ 0h] = comp_code[ 8b] > 192.168.1.211: [ 1h] = channel_number[ 8b] > 192.168.1.211: [ 0h] = authentication_type.none[ 1b] > 192.168.1.211: [ 0h] = authentication_type.md2[ 1b] > 192.168.1.211: [ 0h] = authentication_type.md5[ 1b] > 192.168.1.211: [ 0h] = authentication_type.reserved1[ 1b] > 192.168.1.211: [ 0h] = authentication_type.straight_password_key[ 1b] > 192.168.1.211: [ 0h] = authentication_type.oem_prop[ 1b] > 192.168.1.211: [ 0h] = authentication_type.reserved2[ 2b] > 192.168.1.211: [ 0h] = authentication_status.anonymous_login[ 1b] > 192.168.1.211: [ 0h] = authentication_status.null_username[ 1b] > 192.168.1.211: [ 1h] = authentication_status.non_null_username[ 1b] > 192.168.1.211: [ 0h] = authentication_status.user_level_authentication[ 1b] > 192.168.1.211: [ 0h] = authentication_status.per_message_authentication[ 1b] > 192.168.1.211: [ 0h] = authentication_status.reserved[ 3b] > 192.168.1.211: [ 0h] = reserved1[ 8b] > 192.168.1.211: [ 0h] = oem_id[24b] > 192.168.1.211: [ 0h] = oem_auxiliary_data[ 8b] > 192.168.1.211: IPMI Trailer: > 192.168.1.211: -------------- > 192.168.1.211: [ D7h] = checksum2[ 8b] > 192.168.1.211: ===================================================== > 192.168.1.211: IPMI 1.5 Get Session Challenge Request > 192.168.1.211: ===================================================== > 192.168.1.211: RMCP Header: > 192.168.1.211: ------------ > 192.168.1.211: [ 6h] = version[ 8b] > 192.168.1.211: [ 0h] = reserved[ 8b] > 192.168.1.211: [ FFh] = sequence_number[ 8b] > 192.168.1.211: [ 7h] = message_class.class[ 5b] > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > 192.168.1.211: IPMI Session Header: > 192.168.1.211: -------------------- > 192.168.1.211: [ 0h] = authentication_type[ 8b] > 192.168.1.211: [ 0h] = session_sequence_number[32b] > 192.168.1.211: [ 0h] = session_id[32b] > 192.168.1.211: [ 18h] = ipmi_msg_len[ 8b] > 192.168.1.211: IPMI Message Header: > 192.168.1.211: -------------------- > 192.168.1.211: [ 20h] = rs_addr[ 8b] > 192.168.1.211: [ 0h] = rs_lun[ 2b] > 192.168.1.211: [ 6h] = net_fn[ 6b] > 192.168.1.211: [ C8h] = checksum1[ 8b] > 192.168.1.211: [ 81h] = rq_addr[ 8b] > 192.168.1.211: [ 0h] = rq_lun[ 2b] > 192.168.1.211: [ 34h] = rq_seq[ 6b] > 192.168.1.211: IPMI Command Data: > 192.168.1.211: ------------------ > 192.168.1.211: [ 39h] = cmd[ 8b] > 192.168.1.211: [ 2h] = authentication_type[ 4b] > 192.168.1.211: [ 0h] = reserved[ 4b] > 192.168.1.211: [ BYTE ARRAY ... ] = user_name[16B] > 192.168.1.211: [ 61h 64h 6Dh 69h 6Eh 00h 00h 00h ] > 192.168.1.211: [ 00h 00h 00h 00h 00h 00h 00h 00h ] > 192.168.1.211: IPMI Trailer: > 192.168.1.211: -------------- > 192.168.1.211: [ 6Bh] = checksum2[ 8b] > 192.168.1.211: ===================================================== > 192.168.1.211: IPMI 1.5 Get Session Challenge Response > 192.168.1.211: ===================================================== > 192.168.1.211: RMCP Header: > 192.168.1.211: ------------ > 192.168.1.211: [ 6h] = version[ 8b] > 192.168.1.211: [ 0h] = reserved[ 8b] > 192.168.1.211: [ FFh] = sequence_number[ 8b] > 192.168.1.211: [ 7h] = message_class.class[ 5b] > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > 192.168.1.211: IPMI Session Header: > 192.168.1.211: -------------------- > 192.168.1.211: [ 0h] = authentication_type[ 8b] > 192.168.1.211: [ 0h] = session_sequence_number[32b] > 192.168.1.211: [ 0h] = session_id[32b] > 192.168.1.211: [ 1Ch] = ipmi_msg_len[ 8b] > 192.168.1.211: IPMI Message Header: > 192.168.1.211: -------------------- > 192.168.1.211: [ 81h] = rq_addr[ 8b] > 192.168.1.211: [ 0h] = rq_lun[ 2b] > 192.168.1.211: [ 7h] = net_fn[ 6b] > 192.168.1.211: [ 63h] = checksum1[ 8b] > 192.168.1.211: [ 20h] = rs_addr[ 8b] > 192.168.1.211: [ 0h] = rs_lun[ 2b] > 192.168.1.211: [ 34h] = rq_seq[ 6b] > 192.168.1.211: IPMI Command Data: > 192.168.1.211: ------------------ > 192.168.1.211: [ 39h] = cmd[ 8b] > 192.168.1.211: [ 0h] = comp_code[ 8b] > 192.168.1.211: [ AC03D99h] = temp_session_id[32b] > 192.168.1.211: [ BYTE ARRAY ... ] = challenge_string[16B] > 192.168.1.211: [ 69h F4h 8Ah 89h 60h E4h E2h 1Ch ] > 192.168.1.211: [ 2Ah CCh 96h A0h 6Dh 5Ah CAh 7Ah ] > 192.168.1.211: IPMI Trailer: > 192.168.1.211: -------------- > 192.168.1.211: [ 4Eh] = checksum2[ 8b] > 192.168.1.211: ===================================================== > 192.168.1.211: IPMI 1.5 Activiate Session Request > 192.168.1.211: ===================================================== > 192.168.1.211: RMCP Header: > 192.168.1.211: ------------ > 192.168.1.211: [ 6h] = version[ 8b] > 192.168.1.211: [ 0h] = reserved[ 8b] > 192.168.1.211: [ FFh] = sequence_number[ 8b] > 192.168.1.211: [ 7h] = message_class.class[ 5b] > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > 192.168.1.211: IPMI Session Header: > 192.168.1.211: -------------------- > 192.168.1.211: [ 2h] = authentication_type[ 8b] > 192.168.1.211: [ 0h] = session_sequence_number[32b] > 192.168.1.211: [ AC03D99h] = session_id[32b] > 192.168.1.211: [ BYTE ARRAY ... ] = authentication_code[16B] > 192.168.1.211: [ 6Bh 25h AAh 78h 0Bh D3h F8h 14h ] > 192.168.1.211: [ C4h 57h 15h 6Eh 15h C3h 15h F6h ] > 192.168.1.211: [ 1Dh] = ipmi_msg_len[ 8b] > 192.168.1.211: IPMI Message Header: > 192.168.1.211: -------------------- > 192.168.1.211: [ 20h] = rs_addr[ 8b] > 192.168.1.211: [ 0h] = rs_lun[ 2b] > 192.168.1.211: [ 6h] = net_fn[ 6b] > 192.168.1.211: [ C8h] = checksum1[ 8b] > 192.168.1.211: [ 81h] = rq_addr[ 8b] > 192.168.1.211: [ 0h] = rq_lun[ 2b] > 192.168.1.211: [ 35h] = rq_seq[ 6b] > 192.168.1.211: IPMI Command Data: > 192.168.1.211: ------------------ > 192.168.1.211: [ 3Ah] = cmd[ 8b] > 192.168.1.211: [ 2h] = authentication_type[ 4b] > 192.168.1.211: [ 0h] = reserved1[ 4b] > 192.168.1.211: [ 3h] = maximum_privilege_level[ 4b] > 192.168.1.211: [ 0h] = reserved2[ 4b] > 192.168.1.211: [ BYTE ARRAY ... ] = challenge_string[16B] > 192.168.1.211: [ 69h F4h 8Ah 89h 60h E4h E2h 1Ch ] > 192.168.1.211: [ 2Ah CCh 96h A0h 6Dh 5Ah CAh 7Ah ] > 192.168.1.211: [ 279F274Fh] = initial_outbound_sequence_number[32b] > 192.168.1.211: IPMI Trailer: > 192.168.1.211: -------------- > 192.168.1.211: [ 47h] = checksum2[ 8b] > 192.168.1.211: ===================================================== > 192.168.1.211: IPMI 1.5 Activiate Session Response > 192.168.1.211: ===================================================== > 192.168.1.211: RMCP Header: > 192.168.1.211: ------------ > 192.168.1.211: [ 6h] = version[ 8b] > 192.168.1.211: [ 0h] = reserved[ 8b] > 192.168.1.211: [ FFh] = sequence_number[ 8b] > 192.168.1.211: [ 7h] = message_class.class[ 5b] > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > 192.168.1.211: IPMI Session Header: > 192.168.1.211: -------------------- > 192.168.1.211: [ 2h] = authentication_type[ 8b] > 192.168.1.211: [ 0h] = session_sequence_number[32b] > 192.168.1.211: [ AC03D99h] = session_id[32b] > 192.168.1.211: [ BYTE ARRAY ... ] = authentication_code[16B] > 192.168.1.211: [ 29h BCh 75h CEh 94h F5h 23h 0Eh ] > 192.168.1.211: [ A9h A9h 97h FFh 58h 22h C4h 89h ] > 192.168.1.211: [ 8h] = ipmi_msg_len[ 8b] > 192.168.1.211: IPMI Message Header: > 192.168.1.211: -------------------- > 192.168.1.211: [ 81h] = rq_addr[ 8b] > 192.168.1.211: [ 0h] = rq_lun[ 2b] > 192.168.1.211: [ 7h] = net_fn[ 6b] > 192.168.1.211: [ 63h] = checksum1[ 8b] > 192.168.1.211: [ 20h] = rs_addr[ 8b] > 192.168.1.211: [ 0h] = rs_lun[ 2b] > 192.168.1.211: [ 35h] = rq_seq[ 6b] > 192.168.1.211: IPMI Command Data: > 192.168.1.211: ------------------ > 192.168.1.211: [ 3Ah] = cmd[ 8b] > 192.168.1.211: [ CCh] = comp_code[ 8b] > 192.168.1.211: IPMI Trailer: > 192.168.1.211: -------------- > 192.168.1.211: [ 6h] = checksum2[ 8b] > ipmi_ctx_open_outofband: bad completion code: request data/parameter invalid > [root@tpw ~]# > > ------------------------------------------------------------------------------------- > > > > > A few other random thoughts. > > > > Could you also try different authentication types. Like "-a md2" and > > "-a straight_password_key". > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="authcap" -u admin -p relation > ipmimonitoring: authentication type unavailable for attempted privilege level > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="authcap" -a md2 -u admin -p relation > ipmimonitoring: authentication type unavailable for attempted privilege level > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="authcap" -a STRAIGHT_PASSWORD_KEY -u admin -p relation > ipmimonitoring: authentication type unavailable for attempted privilege level > [root@tpw ~]# > > > > > Also, what is the output of "bmc-config --checkout > > --section=lan_conf_auth", just so we can check to make sure the > > configuration looks good. > I ran the command remotely as I have currently no Linux installed on the > box (if it is necessary, just tell me, than I can put a Linux on it and > run bmc-config locally): > > [root@tpw ~]# bmc-config -h 192.168.1.211 -u admin -p relation --checkout --section=lan_conf_auth > # > # Section Lan_Conf_Auth Comments > # > # In the Lan_Conf_Auth section, allowable authentication mechanisms for IPMI 1.5 > # is configured. Most users will want to set all "MD5" authentication to "Yes" > # and the rest to "No". If you have configured a NULL username and a NULL > # password, you will also want to configure some of the "None" fields to "Yes" > # to allow "None" authentication to work. Some motherboards do not allow you to > # enable OEM authentication, so you may wish to set all OEM related fields to > # "No". > # > Section Lan_Conf_Auth > ## Possible values: Yes/No > Callback_Enable_Auth_Type_None No > ## Possible values: Yes/No > Callback_Enable_Auth_Type_MD5 No > ## Possible values: Yes/No > Callback_Enable_Auth_Type_Straight_Password No > ## Possible values: Yes/No > User_Enable_Auth_Type_None No > ## Possible values: Yes/No > User_Enable_Auth_Type_MD5 No > ## Possible values: Yes/No > User_Enable_Auth_Type_Straight_Password No > ## Possible values: Yes/No > Operator_Enable_Auth_Type_None No > ## Possible values: Yes/No > Operator_Enable_Auth_Type_MD5 No > ## Possible values: Yes/No > Operator_Enable_Auth_Type_Straight_Password No > ## Possible values: Yes/No > Admin_Enable_Auth_Type_None No > ## Possible values: Yes/No > Admin_Enable_Auth_Type_MD5 Yes > ## Possible values: Yes/No > Admin_Enable_Auth_Type_Straight_Password Yes > ## Possible values: Yes/No > OEM_Enable_Auth_Type_None No > ## Possible values: Yes/No > OEM_Enable_Auth_Type_MD5 No > ## Possible values: Yes/No > OEM_Enable_Auth_Type_Straight_Password No > EndSection > [root@tpw ~]# > > If you need any further results, just let me know! > > Thanks for your support, > Werner > > > > > Thanks, > > > > Al > > > > On Mon, 2009-08-24 at 15:31 +0200, Werner Fischer wrote: > > > Hi Al, > > > > > > thanks for the updated tar.gz. I tried it, but somehow it still seems to > > > cause problems (see below). I'll be two days out of office - so I can do > > > further tests on Thursday. > > > > > > thanks for your support! > > > > > > [root@tpw ~]# rpm -q freeipmi > > > freeipmi-0.7.12.beta2-1.fc9.i386 > > > [root@tpw ~]# ipmimonitoring -V > > > ipmimonitoring - 0.7.12.beta2 > > > Copyright (C) 2007-2008 Lawrence Livermore National Security, LLC. > > > Copyright (C) 2006-2007 The Regents of the University of California. > > > This program is free software; you may redistribute it under the terms of > > > the GNU General Public License. This program has absolutely no warranty. > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="authcap" -u admin -p relation > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 --debug -u admin -p relation > > > 192.168.1.211: ===================================================== > > > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Request > > > 192.168.1.211: ===================================================== > > > 192.168.1.211: RMCP Header: > > > 192.168.1.211: ------------ > > > 192.168.1.211: [ 6h] = version[ 8b] > > > 192.168.1.211: [ 0h] = reserved[ 8b] > > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > > 192.168.1.211: IPMI Session Header: > > > 192.168.1.211: -------------------- > > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > > 192.168.1.211: [ 0h] = session_id[32b] > > > 192.168.1.211: [ 9h] = ipmi_msg_len[ 8b] > > > 192.168.1.211: IPMI Message Header: > > > 192.168.1.211: -------------------- > > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > > 192.168.1.211: [ 6h] = net_fn[ 6b] > > > 192.168.1.211: [ C8h] = checksum1[ 8b] > > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > > 192.168.1.211: [ 13h] = rq_seq[ 6b] > > > 192.168.1.211: IPMI Command Data: > > > 192.168.1.211: ------------------ > > > 192.168.1.211: [ 38h] = cmd[ 8b] > > > 192.168.1.211: [ Eh] = channel_number[ 4b] > > > 192.168.1.211: [ 0h] = reserved1[ 4b] > > > 192.168.1.211: [ 3h] = maximum_privilege_level[ 4b] > > > 192.168.1.211: [ 0h] = reserved2[ 4b] > > > 192.168.1.211: IPMI Trailer: > > > 192.168.1.211: -------------- > > > 192.168.1.211: [ EAh] = checksum2[ 8b] > > > 192.168.1.211: ===================================================== > > > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Response > > > 192.168.1.211: ===================================================== > > > 192.168.1.211: RMCP Header: > > > 192.168.1.211: ------------ > > > 192.168.1.211: [ 6h] = version[ 8b] > > > 192.168.1.211: [ 0h] = reserved[ 8b] > > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > > 192.168.1.211: IPMI Session Header: > > > 192.168.1.211: -------------------- > > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > > 192.168.1.211: [ 0h] = session_id[32b] > > > 192.168.1.211: [ 10h] = ipmi_msg_len[ 8b] > > > 192.168.1.211: IPMI Message Header: > > > 192.168.1.211: -------------------- > > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > > 192.168.1.211: [ 7h] = net_fn[ 6b] > > > 192.168.1.211: [ 63h] = checksum1[ 8b] > > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > > 192.168.1.211: [ 13h] = rq_seq[ 6b] > > > 192.168.1.211: IPMI Command Data: > > > 192.168.1.211: ------------------ > > > 192.168.1.211: [ 38h] = cmd[ 8b] > > > 192.168.1.211: [ 0h] = comp_code[ 8b] > > > 192.168.1.211: [ 1h] = channel_number[ 8b] > > > 192.168.1.211: [ 0h] = authentication_type.none[ 1b] > > > 192.168.1.211: [ 0h] = authentication_type.md2[ 1b] > > > 192.168.1.211: [ 0h] = authentication_type.md5[ 1b] > > > 192.168.1.211: [ 0h] = authentication_type.reserved1[ 1b] > > > 192.168.1.211: [ 0h] = authentication_type.straight_password_key[ 1b] > > > 192.168.1.211: [ 0h] = authentication_type.oem_prop[ 1b] > > > 192.168.1.211: [ 0h] = authentication_type.reserved2[ 2b] > > > 192.168.1.211: [ 0h] = authentication_status.anonymous_login[ 1b] > > > 192.168.1.211: [ 0h] = authentication_status.null_username[ 1b] > > > 192.168.1.211: [ 1h] = authentication_status.non_null_username[ 1b] > > > 192.168.1.211: [ 0h] = authentication_status.user_level_authentication[ 1b] > > > 192.168.1.211: [ 0h] = authentication_status.per_message_authentication[ 1b] > > > 192.168.1.211: [ 0h] = authentication_status.reserved[ 3b] > > > 192.168.1.211: [ 0h] = reserved1[ 8b] > > > 192.168.1.211: [ 0h] = oem_id[24b] > > > 192.168.1.211: [ 0h] = oem_auxiliary_data[ 8b] > > > 192.168.1.211: IPMI Trailer: > > > 192.168.1.211: -------------- > > > 192.168.1.211: [ 57h] = checksum2[ 8b] > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > [root@tpw ~]# > > > > > > > > > On Fri, 2009-08-21 at 14:03 -0700, Al Chu wrote: > > > > Hi Werner, > > > > > > > > I've got a test tar.gz here: > > > > > > > > http://**ftp.gluster.com/pub/freeipmi/qa-release/freeipmi-0.7.12.beta2.tar.gz > > > > > > > > This makes it so the 'authcap' workaround should work for you. Can you > > > > give it a shot to make sure it works? > > > > > > > > Thanks, > > > > Al > > > > > > > > On Fri, 2009-08-21 at 08:44 -0700, Al Chu wrote: > > > > > Hi Werner, > > > > > > > > > > > 192.168.1.211: [ 0h] = authentication_type.none[ 1b] > > > > > > 192.168.1.211: [ 0h] = authentication_type.md2[ 1b] > > > > > > 192.168.1.211: [ 0h] = authentication_type.md5[ 1b] > > > > > > 192.168.1.211: [ 0h] = authentication_type.reserved1[ 1b] > > > > > > 192.168.1.211: [ 0h] = authentication_type.straight_password_key[ 1b] > > > > > > 192.168.1.211: [ 0h] = authentication_type.oem_prop[ 1b] > > > > > > > > > > This indicates that no authentication support is enabled, which is very > > > > > unlikely of being true (which we could verify via 'bmc-config --checkout > > > > > --section=lan_conf_auth'). > > > > > > > > > > I'll modify the 'authcap' workaround to also encompass this case and > > > > > post a beta tar.gz for you to check out. > > > > > > > > > > Al > > > > > > > > > > On Fri, 2009-08-21 at 09:58 +0200, Werner Fischer wrote: > > > > > > Hi Al, > > > > > > > > > > > > thanks for your fast answer. > > > > > > > > > > > > Below you find the requested debug output. I'm using version 0.7.11. The > > > > > > "authcap" workaround does not fix the problem. After executing with > > > > > > debug to the affected Intel S5000PAL system (IP 192.168.1.211) I again > > > > > > verified the correct behavior of ipmimonitoring to the other system > > > > > > (Supermicro) to IP 10.10.10.233. > > > > > > > > > > > > [root@tpw ~]# rpm -q freeipmi > > > > > > freeipmi-0.7.11-1.fc9.i386 > > > > > > [root@tpw ~]# ipmimonitoring -V > > > > > > ipmimonitoring - 0.7.11 > > > > > > Copyright (C) 2007-2008 Lawrence Livermore National Security, LLC. > > > > > > Copyright (C) 2006-2007 The Regents of the University of California. > > > > > > This program is free software; you may redistribute it under the terms of > > > > > > the GNU General Public License. This program has absolutely no warranty. > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="authcap" -u admin -p relation > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 --debug -u admin -p relation > > > > > > 192.168.1.211: ===================================================== > > > > > > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Request > > > > > > 192.168.1.211: ===================================================== > > > > > > 192.168.1.211: RMCP Header: > > > > > > 192.168.1.211: ------------ > > > > > > 192.168.1.211: [ 6h] = version[ 8b] > > > > > > 192.168.1.211: [ 0h] = reserved[ 8b] > > > > > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > > > > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > > > > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > > > > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > > > > > 192.168.1.211: IPMI Session Header: > > > > > > 192.168.1.211: -------------------- > > > > > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > > > > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > > > > > 192.168.1.211: [ 0h] = session_id[32b] > > > > > > 192.168.1.211: [ 9h] = ipmi_msg_len[ 8b] > > > > > > 192.168.1.211: IPMI Message Header: > > > > > > 192.168.1.211: -------------------- > > > > > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > > > > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > > > > > 192.168.1.211: [ 6h] = net_fn[ 6b] > > > > > > 192.168.1.211: [ C8h] = checksum1[ 8b] > > > > > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > > > > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > > > > > 192.168.1.211: [ 8h] = rq_seq[ 6b] > > > > > > 192.168.1.211: IPMI Command Data: > > > > > > 192.168.1.211: ------------------ > > > > > > 192.168.1.211: [ 38h] = cmd[ 8b] > > > > > > 192.168.1.211: [ Eh] = channel_number[ 4b] > > > > > > 192.168.1.211: [ 0h] = reserved1[ 4b] > > > > > > 192.168.1.211: [ 3h] = maximum_privilege_level[ 4b] > > > > > > 192.168.1.211: [ 0h] = reserved2[ 4b] > > > > > > 192.168.1.211: IPMI Trailer: > > > > > > 192.168.1.211: -------------- > > > > > > 192.168.1.211: [ 16h] = checksum2[ 8b] > > > > > > 192.168.1.211: ===================================================== > > > > > > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Response > > > > > > 192.168.1.211: ===================================================== > > > > > > 192.168.1.211: RMCP Header: > > > > > > 192.168.1.211: ------------ > > > > > > 192.168.1.211: [ 6h] = version[ 8b] > > > > > > 192.168.1.211: [ 0h] = reserved[ 8b] > > > > > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > > > > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > > > > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > > > > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > > > > > 192.168.1.211: IPMI Session Header: > > > > > > 192.168.1.211: -------------------- > > > > > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > > > > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > > > > > 192.168.1.211: [ 0h] = session_id[32b] > > > > > > 192.168.1.211: [ 10h] = ipmi_msg_len[ 8b] > > > > > > 192.168.1.211: IPMI Message Header: > > > > > > 192.168.1.211: -------------------- > > > > > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > > > > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > > > > > 192.168.1.211: [ 7h] = net_fn[ 6b] > > > > > > 192.168.1.211: [ 63h] = checksum1[ 8b] > > > > > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > > > > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > > > > > 192.168.1.211: [ 8h] = rq_seq[ 6b] > > > > > > 192.168.1.211: IPMI Command Data: > > > > > > 192.168.1.211: ------------------ > > > > > > 192.168.1.211: [ 38h] = cmd[ 8b] > > > > > > 192.168.1.211: [ 0h] = comp_code[ 8b] > > > > > > 192.168.1.211: [ 1h] = channel_number[ 8b] > > > > > > 192.168.1.211: [ 0h] = authentication_type.none[ 1b] > > > > > > 192.168.1.211: [ 0h] = authentication_type.md2[ 1b] > > > > > > 192.168.1.211: [ 0h] = authentication_type.md5[ 1b] > > > > > > 192.168.1.211: [ 0h] = authentication_type.reserved1[ 1b] > > > > > > 192.168.1.211: [ 0h] = authentication_type.straight_password_key[ 1b] > > > > > > 192.168.1.211: [ 0h] = authentication_type.oem_prop[ 1b] > > > > > > 192.168.1.211: [ 0h] = authentication_type.reserved2[ 2b] > > > > > > 192.168.1.211: [ 0h] = authentication_status.anonymous_login[ 1b] > > > > > > 192.168.1.211: [ 0h] = authentication_status.null_username[ 1b] > > > > > > 192.168.1.211: [ 1h] = authentication_status.non_null_username[ 1b] > > > > > > 192.168.1.211: [ 0h] = authentication_status.user_level_authentication[ 1b] > > > > > > 192.168.1.211: [ 0h] = authentication_status.per_message_authentication[ 1b] > > > > > > 192.168.1.211: [ 0h] = authentication_status.reserved[ 3b] > > > > > > 192.168.1.211: [ 0h] = reserved1[ 8b] > > > > > > 192.168.1.211: [ 0h] = oem_id[24b] > > > > > > 192.168.1.211: [ 0h] = oem_auxiliary_data[ 8b] > > > > > > 192.168.1.211: IPMI Trailer: > > > > > > 192.168.1.211: -------------- > > > > > > 192.168.1.211: [ 83h] = checksum2[ 8b] > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > [root@tpw ~]# > > > > > > [root@tpw ~]# > > > > > > [root@tpw ~]# > > > > > > [root@tpw ~]# ipmimonitoring -h 10.10.10.233 -u ADMIN -p ADMIN > > > > > > Record_ID | Sensor Name | Sensor Group | Monitoring Status| Sensor Units | Sensor Reading > > > > > > 4 | System Temp | Temperature | Nominal | C | 41.000000 > > > > > > 5 | CPU1 Vcore | Voltage | Nominal | V | 0.976000 > > > > > > 7 | CPU1 DIMM | Voltage | Nominal | V | 1.512000 > > > > > > 9 | +1.5V | Voltage | Nominal | V | 1.504000 > > > > > > 10 | +3.3V | Voltage | Nominal | V | 3.240000 > > > > > > 11 | +3.3VSB | Voltage | Nominal | V | 3.240000 > > > > > > 12 | +5V | Voltage | Nominal | V | 5.120000 > > > > > > 13 | +12V | Voltage | Nominal | V | 12.190000 > > > > > > 14 | VBAT | Voltage | Nominal | V | 3.216000 > > > > > > 15 | Fan1 | Fan | Nominal | RPM | 3264.000000 > > > > > > 16 | Fan2 | Fan | Nominal | RPM | 3536.000000 > > > > > > 19 | Fan5 | Fan | Nominal | RPM | 2788.000000 > > > > > > 20 | Fan6 | Fan | Nominal | RPM | 2652.000000 > > > > > > 21 | Fan7 | Fan | Nominal | RPM | 3536.000000 > > > > > > 23 | Intrusion | Physical Security | Nominal | N/A | 'OK' > > > > > > 24 | PS Failure | Power Supply | Nominal | N/A | 'OK' > > > > > > [root@tpw ~]# > > > > > > > > > > > > Werner > > > > > > > > > > > > On Wed, 2009-08-19 at 08:58 -0700, Al Chu wrote: > > > > > > > Hi Werner, > > > > > > > > > > > > > > It's possible the motherboard is not reporting supported authentication > > > > > > > types correctly. You could give the "authcap" workaround a shot. > > > > > > > However, if this is being non-compliant in the way that I think it is, > > > > > > > the "authcap" workaround won't work (b/c it currently handles a > > > > > > > different non-compliance bug). Could you send me the output from > > > > > > > --debug? If we can verify the issue, I'll implement a new workaround > > > > > > > for you. > > > > > > > > > > > > > > BTW, if you need the intel20 workarounds for IPMI 2.0, you may need to > > > > > > > upgrade. There were some bugs found a few releases ago. > > > > > > > > > > > > > > 0.7.4 - 12/15/08 > > > > > > > ---------------- > > > > > > > <snip> > > > > > > > o Fix Intel IPMI 2.0 workarounds in all tools/libraries. > > > > > > > <snip> > > > > > > > > > > > > > > Al > > > > > > > > > > > > > > On Wed, 2009-08-19 at 14:16 +0200, Werner Fischer wrote: > > > > > > > > Dear freeipmi users/developers, > > > > > > > > > > > > > > > > I'm trying to monitor an Intel SR2500 server (this server has the Intel > > > > > > > > S5000PAL mainboard in it). > > > > > > > > > > > > > > > > While I can monitor it using ipmitool, I keep getting errors with > > > > > > > > ipmimonitoring from freeipmi. Also using the "-W" parameter for > > > > > > > > workarounds (as described in the manpage of ipmimonitoring) doesn't > > > > > > > > help: > > > > > > > > > > > > > > > > -------------------------------------------------------------------------- > > > > > > > > [root@tpw ~]# ipmitool -I lan -H 192.168.1.211 -U admin -P relation sdr > > > > > > > > BB +1.2V Vtt | 1.20 Volts | ok > > > > > > > > BB +1.5V AUX | 1.47 Volts | ok > > > > > > > > BB +1.5V | 1.48 Volts | ok > > > > > > > > BB +1.8V | 1.79 Volts | ok > > > > > > > > BB +3.3V | 3.35 Volts | ok > > > > > > > > BB +3.3V STB | 3.35 Volts | ok > > > > > > > > ^C > > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > > > > > > > > ipmi_monitoring_sensor_readings_by_record_id: authentication type unavailable for attempted privilege level > > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > > > > > > > > ipmi_monitoring_sensor_readings_by_record_id: authentication type unavailable for attempted privilege level > > > > > > > > [root@tpw ~]# rpm -q freeipmi > > > > > > > > freeipmi-0.5.1-3.fc9.i386 > > > > > > > > [root@tpw ~]# > > > > > > > > -------------------------------------------------------------------------- > > > > > > > > > > > > > > > > I checked the manpage: > > > > > > > > "authentication type unavailable for attempted privilege level" - The authentication type you wish > > > > > > > > to authenticate with is not available for this privilege level. Please try again with an alternate > > > > > > > > authentication type or alternate privilege level. It may also be possible the available authenti- > > > > > > > > cation types you can authenticate with are not correctly configured on the remote BMC. > > > > > > > > But the settings at the BMC side seem to be ok: > > > > > > > > > > > > > > > > -------------------------------------------------------------------------- > > > > > > > > [root@tpw ~]# ipmitool -I lan -H 192.168.1.211 -U admin -P relation lan print 1 > > > > > > > > Set in Progress : Set Complete > > > > > > > > Auth Type Support : NONE MD5 PASSWORD > > > > > > > > Auth Type Enable : Callback : > > > > > > > > : User : > > > > > > > > : Operator : > > > > > > > > : Admin : MD5 PASSWORD > > > > > > > > : OEM : > > > > > > > > IP Address Source : Static Address > > > > > > > > IP Address : 192.168.1.211 > > > > > > > > Subnet Mask : 255.255.255.0 > > > > > > > > MAC Address : 00:0e:0c:ea:92:a2 > > > > > > > > [...] > > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -a MD5 -u admin -p relation > > > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > > > [root@tpw ~]# > > > > > > > > -------------------------------------------------------------------------- > > > > > > > > > > > > > > > > Also compiling the newest version and using it does not help: > > > > > > > > -------------------------------------------------------------------------- > > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > > > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > > > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > > > [root@tpw ~]# rpm -q freeipmi > > > > > > > > freeipmi-0.7.11-1.fc9.i386 > > > > > > > > [root@tpw ~]# > > > > > > > > -------------------------------------------------------------------------- > > > > > > > > > > > > > > > > In contrast, monitoring a system with a new Supermicro X8DT3-F mainboard > > > > > > > > works fine with freeipmi-0.5.1-3.fc9.i386 and also with > > > > > > > > freeipmi-0.7.11-1.fc9.i386: > > > > > > > > > > > > > > > > -------------------------------------------------------------------------- > > > > > > > > [root@tpw ~]# ipmitool -I lan -H 10.10.10.233 -U ADMIN -P ADMIN sdr > > > > > > > > CPU1 Temp | 0 unspecified | ok > > > > > > > > CPU2 Temp | no reading | ns > > > > > > > > System Temp | 45 degrees C | ok > > > > > > > > CPU1 Vcore | 0.98 Volts | ok > > > > > > > > CPU2 Vcore | no reading | ns > > > > > > > > CPU1 DIMM | 1.51 Volts | ok > > > > > > > > CPU2 DIMM | no reading | ns > > > > > > > > ^C > > > > > > > > [root@tpw ~]# ipmimonitoring -h 10.10.10.233 -u ADMIN -p ADMIN > > > > > > > > Record_ID | Sensor Name | Sensor Group | Monitoring Status| Sensor Units | Sensor Reading > > > > > > > > 4 | System Temp | Temperature | Nominal | C | 45.000000 > > > > > > > > 5 | CPU1 Vcore | Voltage | Nominal | V | 0.976000 > > > > > > > > 6 | CPU2 Vcore | Voltage | Nominal | V | 0.000000 > > > > > > > > 7 | CPU1 DIMM | Voltage | Nominal | V | 1.512000 > > > > > > > > 8 | CPU2 DIMM | Voltage | Nominal | V | 0.000000 > > > > > > > > 9 | +1.5V | Voltage | Nominal | V | 1.504000 > > > > > > > > 10 | +3.3V | Voltage | Nominal | V | 3.240000 > > > > > > > > 11 | +3.3VSB | Voltage | Nominal | V | 3.240000 > > > > > > > > 12 | +5V | Voltage | Nominal | V | 5.120000 > > > > > > > > 13 | +12V | Voltage | Nominal | V | 12.190000 > > > > > > > > 14 | VBAT | Voltage | Nominal | V | 3.240000 > > > > > > > > 15 | Fan1 | Fan | Nominal | RPM | 6528.000000 > > > > > > > > 16 | Fan2 | Fan | Nominal | RPM | 7072.000000 > > > > > > > > 17 | Fan3 | Fan | Nominal | RPM | 0.000000 > > > > > > > > 18 | Fan4 | Fan | Nominal | RPM | 0.000000 > > > > > > > > 19 | Fan5 | Fan | Nominal | RPM | 5644.000000 > > > > > > > > 20 | Fan6 | Fan | Nominal | RPM | 5304.000000 > > > > > > > > 21 | Fan7 | Fan | Nominal | RPM | 7072.000000 > > > > > > > > 22 | Fan8 | Fan | Nominal | RPM | 0.000000 > > > > > > > > 23 | Intrusion | Physical Security | Nominal | N/A | '' > > > > > > > > 24 | PS Failure | Power Supply | Nominal | N/A | '' > > > > > > > > [root@tpw ~]# > > > > > > > > -------------------------------------------------------------------------- > > > > > > > > > > > > > > > > Does anybody have an idea how this problem could be fixed? > > > > > > > > > > > > > > > > best regards, > > > > > > > > Werner > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > Freeipmi-users mailing list > > > > > > > > Freeipmi-users@... > > > > > > > > http://****lists.gnu.org/mailman/listinfo/freeipmi-users > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > Freeipmi-users mailing list > > > > > > Freeipmi-users@... > > > > > > http://***lists.gnu.org/mailman/listinfo/freeipmi-users > > > > > > > > > > > > > > > > > > _______________________________________________ > > > Freeipmi-users mailing list > > > Freeipmi-users@... > > > http://**lists.gnu.org/mailman/listinfo/freeipmi-users > > > > > > > _______________________________________________ > Freeipmi-users mailing list > Freeipmi-users@... > http://*lists.gnu.org/mailman/listinfo/freeipmi-users > Albert Chu chu11@... Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory _______________________________________________ Freeipmi-users mailing list Freeipmi-users@... http://lists.gnu.org/mailman/listinfo/freeipmi-users |
|
|
Re: "authentication type unavailable for attempted privilege level" with Intel S5000PAL Mainboard
by Werner Fischer-2
::
Rate this Message:
Hi Al,
you are absolutely right! In this way it works: [root@tpw ~]# ipmimonitoring -V ipmimonitoring - 0.7.12.beta2 Copyright (C) 2007-2008 Lawrence Livermore National Security, LLC. Copyright (C) 2006-2007 The Regents of the University of California. This program is free software; you may redistribute it under the terms of the GNU General Public License. This program has absolutely no warranty. [root@tpw ~]# [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -l admin -u admin -p relation Caching SDR repository information: /root/.freeipmi/sdr-cache/sdr-cache-tpw.192.168.1.211 Caching SDR record 143 of 143 (current record ID 143) Record_ID | Sensor Name | Sensor Group | Monitoring Status| Sensor Units | Sensor Reading 1 | BB +1.2V Vtt | Voltage | Nominal | V | 1.197000 2 | BB +1.5V AUX | Voltage | Nominal | V | 1.466400 3 | BB +1.5V | Voltage | Nominal | V | 1.482000 4 | BB +1.8V | Voltage | Nominal | V | 1.785000 5 | BB +3.3V | Voltage | Nominal | V | 3.354000 6 | BB +3.3V STB | Voltage | Nominal | V | 3.354000 7 | BB +1.5V ESB | Voltage | Nominal | V | 1.505400 8 | BB +5V | Voltage | Nominal | V | 5.070000 9 | BB +12V AUX | Voltage | Nominal | V | 11.904000 I have configured the IPMI settings and IPMI user via the "Intel Server Deployment" CD: http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&Inst=Yes&ProductID=2451&DwnldID=17974&strOSs=38&OSFullName=OS%20Independent&lang=eng I was not aware of the -l option. Sorry for causing the inconvenience. And thanks a lot again for your help! Best regards, Werner On Mon, 2009-08-31 at 10:06 -0700, Al Chu wrote: > Hey Werner, > > Actually, your default config may be the issue afterall, not the > motherboard. Your default config is not allowing authentication by any > privilege level other than "admin". How about trying ipmimonitoring > with the -l admin, to tell ipmimonitoring to use the admin privilege > level. > > Out of my curiosity, did the Intel motherboard come like this by > default? > > Al > > On Mon, 2009-08-31 at 12:18 +0200, Werner Fischer wrote: > > Hi Al, > > > > sorry for my late reply. Now I'm back in the office. You find my results > > below: > > > > On Mon, 2009-08-24 at 10:40 -0700, Al Chu wrote: > > > Hi Werner, > > > > > > Thanks for the feedback. > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 --debug -u admin -p > > > > relation > > > > > > Could you run --debug with the -W "authcap". I'm wondering if it's > > > failing in a different location and the workaround has to be in multiple > > > places. > > sure, here it is: > > > > ------------------------------------------------------------------------------------- > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W "authcap" --debug -u admin -p relation > > 192.168.1.211: ===================================================== > > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Request > > 192.168.1.211: ===================================================== > > 192.168.1.211: RMCP Header: > > 192.168.1.211: ------------ > > 192.168.1.211: [ 6h] = version[ 8b] > > 192.168.1.211: [ 0h] = reserved[ 8b] > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > 192.168.1.211: IPMI Session Header: > > 192.168.1.211: -------------------- > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > 192.168.1.211: [ 0h] = session_id[32b] > > 192.168.1.211: [ 9h] = ipmi_msg_len[ 8b] > > 192.168.1.211: IPMI Message Header: > > 192.168.1.211: -------------------- > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > 192.168.1.211: [ 6h] = net_fn[ 6b] > > 192.168.1.211: [ C8h] = checksum1[ 8b] > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > 192.168.1.211: [ 33h] = rq_seq[ 6b] > > 192.168.1.211: IPMI Command Data: > > 192.168.1.211: ------------------ > > 192.168.1.211: [ 38h] = cmd[ 8b] > > 192.168.1.211: [ Eh] = channel_number[ 4b] > > 192.168.1.211: [ 0h] = reserved1[ 4b] > > 192.168.1.211: [ 3h] = maximum_privilege_level[ 4b] > > 192.168.1.211: [ 0h] = reserved2[ 4b] > > 192.168.1.211: IPMI Trailer: > > 192.168.1.211: -------------- > > 192.168.1.211: [ 6Ah] = checksum2[ 8b] > > 192.168.1.211: ===================================================== > > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Response > > 192.168.1.211: ===================================================== > > 192.168.1.211: RMCP Header: > > 192.168.1.211: ------------ > > 192.168.1.211: [ 6h] = version[ 8b] > > 192.168.1.211: [ 0h] = reserved[ 8b] > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > 192.168.1.211: IPMI Session Header: > > 192.168.1.211: -------------------- > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > 192.168.1.211: [ 0h] = session_id[32b] > > 192.168.1.211: [ 10h] = ipmi_msg_len[ 8b] > > 192.168.1.211: IPMI Message Header: > > 192.168.1.211: -------------------- > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > 192.168.1.211: [ 7h] = net_fn[ 6b] > > 192.168.1.211: [ 63h] = checksum1[ 8b] > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > 192.168.1.211: [ 33h] = rq_seq[ 6b] > > 192.168.1.211: IPMI Command Data: > > 192.168.1.211: ------------------ > > 192.168.1.211: [ 38h] = cmd[ 8b] > > 192.168.1.211: [ 0h] = comp_code[ 8b] > > 192.168.1.211: [ 1h] = channel_number[ 8b] > > 192.168.1.211: [ 0h] = authentication_type.none[ 1b] > > 192.168.1.211: [ 0h] = authentication_type.md2[ 1b] > > 192.168.1.211: [ 0h] = authentication_type.md5[ 1b] > > 192.168.1.211: [ 0h] = authentication_type.reserved1[ 1b] > > 192.168.1.211: [ 0h] = authentication_type.straight_password_key[ 1b] > > 192.168.1.211: [ 0h] = authentication_type.oem_prop[ 1b] > > 192.168.1.211: [ 0h] = authentication_type.reserved2[ 2b] > > 192.168.1.211: [ 0h] = authentication_status.anonymous_login[ 1b] > > 192.168.1.211: [ 0h] = authentication_status.null_username[ 1b] > > 192.168.1.211: [ 1h] = authentication_status.non_null_username[ 1b] > > 192.168.1.211: [ 0h] = authentication_status.user_level_authentication[ 1b] > > 192.168.1.211: [ 0h] = authentication_status.per_message_authentication[ 1b] > > 192.168.1.211: [ 0h] = authentication_status.reserved[ 3b] > > 192.168.1.211: [ 0h] = reserved1[ 8b] > > 192.168.1.211: [ 0h] = oem_id[24b] > > 192.168.1.211: [ 0h] = oem_auxiliary_data[ 8b] > > 192.168.1.211: IPMI Trailer: > > 192.168.1.211: -------------- > > 192.168.1.211: [ D7h] = checksum2[ 8b] > > 192.168.1.211: ===================================================== > > 192.168.1.211: IPMI 1.5 Get Session Challenge Request > > 192.168.1.211: ===================================================== > > 192.168.1.211: RMCP Header: > > 192.168.1.211: ------------ > > 192.168.1.211: [ 6h] = version[ 8b] > > 192.168.1.211: [ 0h] = reserved[ 8b] > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > 192.168.1.211: IPMI Session Header: > > 192.168.1.211: -------------------- > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > 192.168.1.211: [ 0h] = session_id[32b] > > 192.168.1.211: [ 18h] = ipmi_msg_len[ 8b] > > 192.168.1.211: IPMI Message Header: > > 192.168.1.211: -------------------- > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > 192.168.1.211: [ 6h] = net_fn[ 6b] > > 192.168.1.211: [ C8h] = checksum1[ 8b] > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > 192.168.1.211: [ 34h] = rq_seq[ 6b] > > 192.168.1.211: IPMI Command Data: > > 192.168.1.211: ------------------ > > 192.168.1.211: [ 39h] = cmd[ 8b] > > 192.168.1.211: [ 2h] = authentication_type[ 4b] > > 192.168.1.211: [ 0h] = reserved[ 4b] > > 192.168.1.211: [ BYTE ARRAY ... ] = user_name[16B] > > 192.168.1.211: [ 61h 64h 6Dh 69h 6Eh 00h 00h 00h ] > > 192.168.1.211: [ 00h 00h 00h 00h 00h 00h 00h 00h ] > > 192.168.1.211: IPMI Trailer: > > 192.168.1.211: -------------- > > 192.168.1.211: [ 6Bh] = checksum2[ 8b] > > 192.168.1.211: ===================================================== > > 192.168.1.211: IPMI 1.5 Get Session Challenge Response > > 192.168.1.211: ===================================================== > > 192.168.1.211: RMCP Header: > > 192.168.1.211: ------------ > > 192.168.1.211: [ 6h] = version[ 8b] > > 192.168.1.211: [ 0h] = reserved[ 8b] > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > 192.168.1.211: IPMI Session Header: > > 192.168.1.211: -------------------- > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > 192.168.1.211: [ 0h] = session_id[32b] > > 192.168.1.211: [ 1Ch] = ipmi_msg_len[ 8b] > > 192.168.1.211: IPMI Message Header: > > 192.168.1.211: -------------------- > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > 192.168.1.211: [ 7h] = net_fn[ 6b] > > 192.168.1.211: [ 63h] = checksum1[ 8b] > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > 192.168.1.211: [ 34h] = rq_seq[ 6b] > > 192.168.1.211: IPMI Command Data: > > 192.168.1.211: ------------------ > > 192.168.1.211: [ 39h] = cmd[ 8b] > > 192.168.1.211: [ 0h] = comp_code[ 8b] > > 192.168.1.211: [ AC03D99h] = temp_session_id[32b] > > 192.168.1.211: [ BYTE ARRAY ... ] = challenge_string[16B] > > 192.168.1.211: [ 69h F4h 8Ah 89h 60h E4h E2h 1Ch ] > > 192.168.1.211: [ 2Ah CCh 96h A0h 6Dh 5Ah CAh 7Ah ] > > 192.168.1.211: IPMI Trailer: > > 192.168.1.211: -------------- > > 192.168.1.211: [ 4Eh] = checksum2[ 8b] > > 192.168.1.211: ===================================================== > > 192.168.1.211: IPMI 1.5 Activiate Session Request > > 192.168.1.211: ===================================================== > > 192.168.1.211: RMCP Header: > > 192.168.1.211: ------------ > > 192.168.1.211: [ 6h] = version[ 8b] > > 192.168.1.211: [ 0h] = reserved[ 8b] > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > 192.168.1.211: IPMI Session Header: > > 192.168.1.211: -------------------- > > 192.168.1.211: [ 2h] = authentication_type[ 8b] > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > 192.168.1.211: [ AC03D99h] = session_id[32b] > > 192.168.1.211: [ BYTE ARRAY ... ] = authentication_code[16B] > > 192.168.1.211: [ 6Bh 25h AAh 78h 0Bh D3h F8h 14h ] > > 192.168.1.211: [ C4h 57h 15h 6Eh 15h C3h 15h F6h ] > > 192.168.1.211: [ 1Dh] = ipmi_msg_len[ 8b] > > 192.168.1.211: IPMI Message Header: > > 192.168.1.211: -------------------- > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > 192.168.1.211: [ 6h] = net_fn[ 6b] > > 192.168.1.211: [ C8h] = checksum1[ 8b] > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > 192.168.1.211: [ 35h] = rq_seq[ 6b] > > 192.168.1.211: IPMI Command Data: > > 192.168.1.211: ------------------ > > 192.168.1.211: [ 3Ah] = cmd[ 8b] > > 192.168.1.211: [ 2h] = authentication_type[ 4b] > > 192.168.1.211: [ 0h] = reserved1[ 4b] > > 192.168.1.211: [ 3h] = maximum_privilege_level[ 4b] > > 192.168.1.211: [ 0h] = reserved2[ 4b] > > 192.168.1.211: [ BYTE ARRAY ... ] = challenge_string[16B] > > 192.168.1.211: [ 69h F4h 8Ah 89h 60h E4h E2h 1Ch ] > > 192.168.1.211: [ 2Ah CCh 96h A0h 6Dh 5Ah CAh 7Ah ] > > 192.168.1.211: [ 279F274Fh] = initial_outbound_sequence_number[32b] > > 192.168.1.211: IPMI Trailer: > > 192.168.1.211: -------------- > > 192.168.1.211: [ 47h] = checksum2[ 8b] > > 192.168.1.211: ===================================================== > > 192.168.1.211: IPMI 1.5 Activiate Session Response > > 192.168.1.211: ===================================================== > > 192.168.1.211: RMCP Header: > > 192.168.1.211: ------------ > > 192.168.1.211: [ 6h] = version[ 8b] > > 192.168.1.211: [ 0h] = reserved[ 8b] > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > 192.168.1.211: IPMI Session Header: > > 192.168.1.211: -------------------- > > 192.168.1.211: [ 2h] = authentication_type[ 8b] > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > 192.168.1.211: [ AC03D99h] = session_id[32b] > > 192.168.1.211: [ BYTE ARRAY ... ] = authentication_code[16B] > > 192.168.1.211: [ 29h BCh 75h CEh 94h F5h 23h 0Eh ] > > 192.168.1.211: [ A9h A9h 97h FFh 58h 22h C4h 89h ] > > 192.168.1.211: [ 8h] = ipmi_msg_len[ 8b] > > 192.168.1.211: IPMI Message Header: > > 192.168.1.211: -------------------- > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > 192.168.1.211: [ 7h] = net_fn[ 6b] > > 192.168.1.211: [ 63h] = checksum1[ 8b] > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > 192.168.1.211: [ 35h] = rq_seq[ 6b] > > 192.168.1.211: IPMI Command Data: > > 192.168.1.211: ------------------ > > 192.168.1.211: [ 3Ah] = cmd[ 8b] > > 192.168.1.211: [ CCh] = comp_code[ 8b] > > 192.168.1.211: IPMI Trailer: > > 192.168.1.211: -------------- > > 192.168.1.211: [ 6h] = checksum2[ 8b] > > ipmi_ctx_open_outofband: bad completion code: request data/parameter invalid > > [root@tpw ~]# > > > > ------------------------------------------------------------------------------------- > > > > > > > > A few other random thoughts. > > > > > > Could you also try different authentication types. Like "-a md2" and > > > "-a straight_password_key". > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="authcap" -u admin -p relation > > ipmimonitoring: authentication type unavailable for attempted privilege level > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="authcap" -a md2 -u admin -p relation > > ipmimonitoring: authentication type unavailable for attempted privilege level > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="authcap" -a STRAIGHT_PASSWORD_KEY -u admin -p relation > > ipmimonitoring: authentication type unavailable for attempted privilege level > > [root@tpw ~]# > > > > > > > > Also, what is the output of "bmc-config --checkout > > > --section=lan_conf_auth", just so we can check to make sure the > > > configuration looks good. > > I ran the command remotely as I have currently no Linux installed on the > > box (if it is necessary, just tell me, than I can put a Linux on it and > > run bmc-config locally): > > > > [root@tpw ~]# bmc-config -h 192.168.1.211 -u admin -p relation --checkout --section=lan_conf_auth > > # > > # Section Lan_Conf_Auth Comments > > # > > # In the Lan_Conf_Auth section, allowable authentication mechanisms for IPMI 1.5 > > # is configured. Most users will want to set all "MD5" authentication to "Yes" > > # and the rest to "No". If you have configured a NULL username and a NULL > > # password, you will also want to configure some of the "None" fields to "Yes" > > # to allow "None" authentication to work. Some motherboards do not allow you to > > # enable OEM authentication, so you may wish to set all OEM related fields to > > # "No". > > # > > Section Lan_Conf_Auth > > ## Possible values: Yes/No > > Callback_Enable_Auth_Type_None No > > ## Possible values: Yes/No > > Callback_Enable_Auth_Type_MD5 No > > ## Possible values: Yes/No > > Callback_Enable_Auth_Type_Straight_Password No > > ## Possible values: Yes/No > > User_Enable_Auth_Type_None No > > ## Possible values: Yes/No > > User_Enable_Auth_Type_MD5 No > > ## Possible values: Yes/No > > User_Enable_Auth_Type_Straight_Password No > > ## Possible values: Yes/No > > Operator_Enable_Auth_Type_None No > > ## Possible values: Yes/No > > Operator_Enable_Auth_Type_MD5 No > > ## Possible values: Yes/No > > Operator_Enable_Auth_Type_Straight_Password No > > ## Possible values: Yes/No > > Admin_Enable_Auth_Type_None No > > ## Possible values: Yes/No > > Admin_Enable_Auth_Type_MD5 Yes > > ## Possible values: Yes/No > > Admin_Enable_Auth_Type_Straight_Password Yes > > ## Possible values: Yes/No > > OEM_Enable_Auth_Type_None No > > ## Possible values: Yes/No > > OEM_Enable_Auth_Type_MD5 No > > ## Possible values: Yes/No > > OEM_Enable_Auth_Type_Straight_Password No > > EndSection > > [root@tpw ~]# > > > > If you need any further results, just let me know! > > > > Thanks for your support, > > Werner > > > > > > > > Thanks, > > > > > > Al > > > > > > On Mon, 2009-08-24 at 15:31 +0200, Werner Fischer wrote: > > > > Hi Al, > > > > > > > > thanks for the updated tar.gz. I tried it, but somehow it still seems to > > > > cause problems (see below). I'll be two days out of office - so I can do > > > > further tests on Thursday. > > > > > > > > thanks for your support! > > > > > > > > [root@tpw ~]# rpm -q freeipmi > > > > freeipmi-0.7.12.beta2-1.fc9.i386 > > > > [root@tpw ~]# ipmimonitoring -V > > > > ipmimonitoring - 0.7.12.beta2 > > > > Copyright (C) 2007-2008 Lawrence Livermore National Security, LLC. > > > > Copyright (C) 2006-2007 The Regents of the University of California. > > > > This program is free software; you may redistribute it under the terms of > > > > the GNU General Public License. This program has absolutely no warranty. > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="authcap" -u admin -p relation > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 --debug -u admin -p relation > > > > 192.168.1.211: ===================================================== > > > > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Request > > > > 192.168.1.211: ===================================================== > > > > 192.168.1.211: RMCP Header: > > > > 192.168.1.211: ------------ > > > > 192.168.1.211: [ 6h] = version[ 8b] > > > > 192.168.1.211: [ 0h] = reserved[ 8b] > > > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > > > 192.168.1.211: IPMI Session Header: > > > > 192.168.1.211: -------------------- > > > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > > > 192.168.1.211: [ 0h] = session_id[32b] > > > > 192.168.1.211: [ 9h] = ipmi_msg_len[ 8b] > > > > 192.168.1.211: IPMI Message Header: > > > > 192.168.1.211: -------------------- > > > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > > > 192.168.1.211: [ 6h] = net_fn[ 6b] > > > > 192.168.1.211: [ C8h] = checksum1[ 8b] > > > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > > > 192.168.1.211: [ 13h] = rq_seq[ 6b] > > > > 192.168.1.211: IPMI Command Data: > > > > 192.168.1.211: ------------------ > > > > 192.168.1.211: [ 38h] = cmd[ 8b] > > > > 192.168.1.211: [ Eh] = channel_number[ 4b] > > > > 192.168.1.211: [ 0h] = reserved1[ 4b] > > > > 192.168.1.211: [ 3h] = maximum_privilege_level[ 4b] > > > > 192.168.1.211: [ 0h] = reserved2[ 4b] > > > > 192.168.1.211: IPMI Trailer: > > > > 192.168.1.211: -------------- > > > > 192.168.1.211: [ EAh] = checksum2[ 8b] > > > > 192.168.1.211: ===================================================== > > > > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Response > > > > 192.168.1.211: ===================================================== > > > > 192.168.1.211: RMCP Header: > > > > 192.168.1.211: ------------ > > > > 192.168.1.211: [ 6h] = version[ 8b] > > > > 192.168.1.211: [ 0h] = reserved[ 8b] > > > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > > > 192.168.1.211: IPMI Session Header: > > > > 192.168.1.211: -------------------- > > > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > > > 192.168.1.211: [ 0h] = session_id[32b] > > > > 192.168.1.211: [ 10h] = ipmi_msg_len[ 8b] > > > > 192.168.1.211: IPMI Message Header: > > > > 192.168.1.211: -------------------- > > > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > > > 192.168.1.211: [ 7h] = net_fn[ 6b] > > > > 192.168.1.211: [ 63h] = checksum1[ 8b] > > > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > > > 192.168.1.211: [ 13h] = rq_seq[ 6b] > > > > 192.168.1.211: IPMI Command Data: > > > > 192.168.1.211: ------------------ > > > > 192.168.1.211: [ 38h] = cmd[ 8b] > > > > 192.168.1.211: [ 0h] = comp_code[ 8b] > > > > 192.168.1.211: [ 1h] = channel_number[ 8b] > > > > 192.168.1.211: [ 0h] = authentication_type.none[ 1b] > > > > 192.168.1.211: [ 0h] = authentication_type.md2[ 1b] > > > > 192.168.1.211: [ 0h] = authentication_type.md5[ 1b] > > > > 192.168.1.211: [ 0h] = authentication_type.reserved1[ 1b] > > > > 192.168.1.211: [ 0h] = authentication_type.straight_password_key[ 1b] > > > > 192.168.1.211: [ 0h] = authentication_type.oem_prop[ 1b] > > > > 192.168.1.211: [ 0h] = authentication_type.reserved2[ 2b] > > > > 192.168.1.211: [ 0h] = authentication_status.anonymous_login[ 1b] > > > > 192.168.1.211: [ 0h] = authentication_status.null_username[ 1b] > > > > 192.168.1.211: [ 1h] = authentication_status.non_null_username[ 1b] > > > > 192.168.1.211: [ 0h] = authentication_status.user_level_authentication[ 1b] > > > > 192.168.1.211: [ 0h] = authentication_status.per_message_authentication[ 1b] > > > > 192.168.1.211: [ 0h] = authentication_status.reserved[ 3b] > > > > 192.168.1.211: [ 0h] = reserved1[ 8b] > > > > 192.168.1.211: [ 0h] = oem_id[24b] > > > > 192.168.1.211: [ 0h] = oem_auxiliary_data[ 8b] > > > > 192.168.1.211: IPMI Trailer: > > > > 192.168.1.211: -------------- > > > > 192.168.1.211: [ 57h] = checksum2[ 8b] > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > [root@tpw ~]# > > > > > > > > > > > > On Fri, 2009-08-21 at 14:03 -0700, Al Chu wrote: > > > > > Hi Werner, > > > > > > > > > > I've got a test tar.gz here: > > > > > > > > > > http://**ftp.gluster.com/pub/freeipmi/qa-release/freeipmi-0.7.12.beta2.tar.gz > > > > > > > > > > This makes it so the 'authcap' workaround should work for you. Can you > > > > > give it a shot to make sure it works? > > > > > > > > > > Thanks, > > > > > Al > > > > > > > > > > On Fri, 2009-08-21 at 08:44 -0700, Al Chu wrote: > > > > > > Hi Werner, > > > > > > > > > > > > > 192.168.1.211: [ 0h] = authentication_type.none[ 1b] > > > > > > > 192.168.1.211: [ 0h] = authentication_type.md2[ 1b] > > > > > > > 192.168.1.211: [ 0h] = authentication_type.md5[ 1b] > > > > > > > 192.168.1.211: [ 0h] = authentication_type.reserved1[ 1b] > > > > > > > 192.168.1.211: [ 0h] = authentication_type.straight_password_key[ 1b] > > > > > > > 192.168.1.211: [ 0h] = authentication_type.oem_prop[ 1b] > > > > > > > > > > > > This indicates that no authentication support is enabled, which is very > > > > > > unlikely of being true (which we could verify via 'bmc-config --checkout > > > > > > --section=lan_conf_auth'). > > > > > > > > > > > > I'll modify the 'authcap' workaround to also encompass this case and > > > > > > post a beta tar.gz for you to check out. > > > > > > > > > > > > Al > > > > > > > > > > > > On Fri, 2009-08-21 at 09:58 +0200, Werner Fischer wrote: > > > > > > > Hi Al, > > > > > > > > > > > > > > thanks for your fast answer. > > > > > > > > > > > > > > Below you find the requested debug output. I'm using version 0.7.11. The > > > > > > > "authcap" workaround does not fix the problem. After executing with > > > > > > > debug to the affected Intel S5000PAL system (IP 192.168.1.211) I again > > > > > > > verified the correct behavior of ipmimonitoring to the other system > > > > > > > (Supermicro) to IP 10.10.10.233. > > > > > > > > > > > > > > [root@tpw ~]# rpm -q freeipmi > > > > > > > freeipmi-0.7.11-1.fc9.i386 > > > > > > > [root@tpw ~]# ipmimonitoring -V > > > > > > > ipmimonitoring - 0.7.11 > > > > > > > Copyright (C) 2007-2008 Lawrence Livermore National Security, LLC. > > > > > > > Copyright (C) 2006-2007 The Regents of the University of California. > > > > > > > This program is free software; you may redistribute it under the terms of > > > > > > > the GNU General Public License. This program has absolutely no warranty. > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="authcap" -u admin -p relation > > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 --debug -u admin -p relation > > > > > > > 192.168.1.211: ===================================================== > > > > > > > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Request > > > > > > > 192.168.1.211: ===================================================== > > > > > > > 192.168.1.211: RMCP Header: > > > > > > > 192.168.1.211: ------------ > > > > > > > 192.168.1.211: [ 6h] = version[ 8b] > > > > > > > 192.168.1.211: [ 0h] = reserved[ 8b] > > > > > > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > > > > > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > > > > > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > > > > > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > > > > > > 192.168.1.211: IPMI Session Header: > > > > > > > 192.168.1.211: -------------------- > > > > > > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > > > > > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > > > > > > 192.168.1.211: [ 0h] = session_id[32b] > > > > > > > 192.168.1.211: [ 9h] = ipmi_msg_len[ 8b] > > > > > > > 192.168.1.211: IPMI Message Header: > > > > > > > 192.168.1.211: -------------------- > > > > > > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > > > > > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > > > > > > 192.168.1.211: [ 6h] = net_fn[ 6b] > > > > > > > 192.168.1.211: [ C8h] = checksum1[ 8b] > > > > > > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > > > > > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > > > > > > 192.168.1.211: [ 8h] = rq_seq[ 6b] > > > > > > > 192.168.1.211: IPMI Command Data: > > > > > > > 192.168.1.211: ------------------ > > > > > > > 192.168.1.211: [ 38h] = cmd[ 8b] > > > > > > > 192.168.1.211: [ Eh] = channel_number[ 4b] > > > > > > > 192.168.1.211: [ 0h] = reserved1[ 4b] > > > > > > > 192.168.1.211: [ 3h] = maximum_privilege_level[ 4b] > > > > > > > 192.168.1.211: [ 0h] = reserved2[ 4b] > > > > > > > 192.168.1.211: IPMI Trailer: > > > > > > > 192.168.1.211: -------------- > > > > > > > 192.168.1.211: [ 16h] = checksum2[ 8b] > > > > > > > 192.168.1.211: ===================================================== > > > > > > > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Response > > > > > > > 192.168.1.211: ===================================================== > > > > > > > 192.168.1.211: RMCP Header: > > > > > > > 192.168.1.211: ------------ > > > > > > > 192.168.1.211: [ 6h] = version[ 8b] > > > > > > > 192.168.1.211: [ 0h] = reserved[ 8b] > > > > > > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > > > > > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > > > > > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > > > > > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > > > > > > 192.168.1.211: IPMI Session Header: > > > > > > > 192.168.1.211: -------------------- > > > > > > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > > > > > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > > > > > > 192.168.1.211: [ 0h] = session_id[32b] > > > > > > > 192.168.1.211: [ 10h] = ipmi_msg_len[ 8b] > > > > > > > 192.168.1.211: IPMI Message Header: > > > > > > > 192.168.1.211: -------------------- > > > > > > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > > > > > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > > > > > > 192.168.1.211: [ 7h] = net_fn[ 6b] > > > > > > > 192.168.1.211: [ 63h] = checksum1[ 8b] > > > > > > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > > > > > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > > > > > > 192.168.1.211: [ 8h] = rq_seq[ 6b] > > > > > > > 192.168.1.211: IPMI Command Data: > > > > > > > 192.168.1.211: ------------------ > > > > > > > 192.168.1.211: [ 38h] = cmd[ 8b] > > > > > > > 192.168.1.211: [ 0h] = comp_code[ 8b] > > > > > > > 192.168.1.211: [ 1h] = channel_number[ 8b] > > > > > > > 192.168.1.211: [ 0h] = authentication_type.none[ 1b] > > > > > > > 192.168.1.211: [ 0h] = authentication_type.md2[ 1b] > > > > > > > 192.168.1.211: [ 0h] = authentication_type.md5[ 1b] > > > > > > > 192.168.1.211: [ 0h] = authentication_type.reserved1[ 1b] > > > > > > > 192.168.1.211: [ 0h] = authentication_type.straight_password_key[ 1b] > > > > > > > 192.168.1.211: [ 0h] = authentication_type.oem_prop[ 1b] > > > > > > > 192.168.1.211: [ 0h] = authentication_type.reserved2[ 2b] > > > > > > > 192.168.1.211: [ 0h] = authentication_status.anonymous_login[ 1b] > > > > > > > 192.168.1.211: [ 0h] = authentication_status.null_username[ 1b] > > > > > > > 192.168.1.211: [ 1h] = authentication_status.non_null_username[ 1b] > > > > > > > 192.168.1.211: [ 0h] = authentication_status.user_level_authentication[ 1b] > > > > > > > 192.168.1.211: [ 0h] = authentication_status.per_message_authentication[ 1b] > > > > > > > 192.168.1.211: [ 0h] = authentication_status.reserved[ 3b] > > > > > > > 192.168.1.211: [ 0h] = reserved1[ 8b] > > > > > > > 192.168.1.211: [ 0h] = oem_id[24b] > > > > > > > 192.168.1.211: [ 0h] = oem_auxiliary_data[ 8b] > > > > > > > 192.168.1.211: IPMI Trailer: > > > > > > > 192.168.1.211: -------------- > > > > > > > 192.168.1.211: [ 83h] = checksum2[ 8b] > > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > > [root@tpw ~]# > > > > > > > [root@tpw ~]# > > > > > > > [root@tpw ~]# > > > > > > > [root@tpw ~]# ipmimonitoring -h 10.10.10.233 -u ADMIN -p ADMIN > > > > > > > Record_ID | Sensor Name | Sensor Group | Monitoring Status| Sensor Units | Sensor Reading > > > > > > > 4 | System Temp | Temperature | Nominal | C | 41.000000 > > > > > > > 5 | CPU1 Vcore | Voltage | Nominal | V | 0.976000 > > > > > > > 7 | CPU1 DIMM | Voltage | Nominal | V | 1.512000 > > > > > > > 9 | +1.5V | Voltage | Nominal | V | 1.504000 > > > > > > > 10 | +3.3V | Voltage | Nominal | V | 3.240000 > > > > > > > 11 | +3.3VSB | Voltage | Nominal | V | 3.240000 > > > > > > > 12 | +5V | Voltage | Nominal | V | 5.120000 > > > > > > > 13 | +12V | Voltage | Nominal | V | 12.190000 > > > > > > > 14 | VBAT | Voltage | Nominal | V | 3.216000 > > > > > > > 15 | Fan1 | Fan | Nominal | RPM | 3264.000000 > > > > > > > 16 | Fan2 | Fan | Nominal | RPM | 3536.000000 > > > > > > > 19 | Fan5 | Fan | Nominal | RPM | 2788.000000 > > > > > > > 20 | Fan6 | Fan | Nominal | RPM | 2652.000000 > > > > > > > 21 | Fan7 | Fan | Nominal | RPM | 3536.000000 > > > > > > > 23 | Intrusion | Physical Security | Nominal | N/A | 'OK' > > > > > > > 24 | PS Failure | Power Supply | Nominal | N/A | 'OK' > > > > > > > [root@tpw ~]# > > > > > > > > > > > > > > Werner > > > > > > > > > > > > > > On Wed, 2009-08-19 at 08:58 -0700, Al Chu wrote: > > > > > > > > Hi Werner, > > > > > > > > > > > > > > > > It's possible the motherboard is not reporting supported authentication > > > > > > > > types correctly. You could give the "authcap" workaround a shot. > > > > > > > > However, if this is being non-compliant in the way that I think it is, > > > > > > > > the "authcap" workaround won't work (b/c it currently handles a > > > > > > > > different non-compliance bug). Could you send me the output from > > > > > > > > --debug? If we can verify the issue, I'll implement a new workaround > > > > > > > > for you. > > > > > > > > > > > > > > > > BTW, if you need the intel20 workarounds for IPMI 2.0, you may need to > > > > > > > > upgrade. There were some bugs found a few releases ago. > > > > > > > > > > > > > > > > 0.7.4 - 12/15/08 > > > > > > > > ---------------- > > > > > > > > <snip> > > > > > > > > o Fix Intel IPMI 2.0 workarounds in all tools/libraries. > > > > > > > > <snip> > > > > > > > > > > > > > > > > Al > > > > > > > > > > > > > > > > On Wed, 2009-08-19 at 14:16 +0200, Werner Fischer wrote: > > > > > > > > > Dear freeipmi users/developers, > > > > > > > > > > > > > > > > > > I'm trying to monitor an Intel SR2500 server (this server has the Intel > > > > > > > > > S5000PAL mainboard in it). > > > > > > > > > > > > > > > > > > While I can monitor it using ipmitool, I keep getting errors with > > > > > > > > > ipmimonitoring from freeipmi. Also using the "-W" parameter for > > > > > > > > > workarounds (as described in the manpage of ipmimonitoring) doesn't > > > > > > > > > help: > > > > > > > > > > > > > > > > > > -------------------------------------------------------------------------- > > > > > > > > > [root@tpw ~]# ipmitool -I lan -H 192.168.1.211 -U admin -P relation sdr > > > > > > > > > BB +1.2V Vtt | 1.20 Volts | ok > > > > > > > > > BB +1.5V AUX | 1.47 Volts | ok > > > > > > > > > BB +1.5V | 1.48 Volts | ok > > > > > > > > > BB +1.8V | 1.79 Volts | ok > > > > > > > > > BB +3.3V | 3.35 Volts | ok > > > > > > > > > BB +3.3V STB | 3.35 Volts | ok > > > > > > > > > ^C > > > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > > > > > > > > > ipmi_monitoring_sensor_readings_by_record_id: authentication type unavailable for attempted privilege level > > > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > > > > > > > > > ipmi_monitoring_sensor_readings_by_record_id: authentication type unavailable for attempted privilege level > > > > > > > > > [root@tpw ~]# rpm -q freeipmi > > > > > > > > > freeipmi-0.5.1-3.fc9.i386 > > > > > > > > > [root@tpw ~]# > > > > > > > > > -------------------------------------------------------------------------- > > > > > > > > > > > > > > > > > > I checked the manpage: > > > > > > > > > "authentication type unavailable for attempted privilege level" - The authentication type you wish > > > > > > > > > to authenticate with is not available for this privilege level. Please try again with an alternate > > > > > > > > > authentication type or alternate privilege level. It may also be possible the available authenti- > > > > > > > > > cation types you can authenticate with are not correctly configured on the remote BMC. > > > > > > > > > But the settings at the BMC side seem to be ok: > > > > > > > > > > > > > > > > > > -------------------------------------------------------------------------- > > > > > > > > > [root@tpw ~]# ipmitool -I lan -H 192.168.1.211 -U admin -P relation lan print 1 > > > > > > > > > Set in Progress : Set Complete > > > > > > > > > Auth Type Support : NONE MD5 PASSWORD > > > > > > > > > Auth Type Enable : Callback : > > > > > > > > > : User : > > > > > > > > > : Operator : > > > > > > > > > : Admin : MD5 PASSWORD > > > > > > > > > : OEM : > > > > > > > > > IP Address Source : Static Address > > > > > > > > > IP Address : 192.168.1.211 > > > > > > > > > Subnet Mask : 255.255.255.0 > > > > > > > > > MAC Address : 00:0e:0c:ea:92:a2 > > > > > > > > > [...] > > > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -a MD5 -u admin -p relation > > > > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > > > > [root@tpw ~]# > > > > > > > > > -------------------------------------------------------------------------- > > > > > > > > > > > > > > > > > > Also compiling the newest version and using it does not help: > > > > > > > > > -------------------------------------------------------------------------- > > > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > > > > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > > > > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > > > > [root@tpw ~]# rpm -q freeipmi > > > > > > > > > freeipmi-0.7.11-1.fc9.i386 > > > > > > > > > [root@tpw ~]# > > > > > > > > > -------------------------------------------------------------------------- > > > > > > > > > > > > > > > > > > In contrast, monitoring a system with a new Supermicro X8DT3-F mainboard > > > > > > > > > works fine with freeipmi-0.5.1-3.fc9.i386 and also with > > > > > > > > > freeipmi-0.7.11-1.fc9.i386: > > > > > > > > > > > > > > > > > > -------------------------------------------------------------------------- > > > > > > > > > [root@tpw ~]# ipmitool -I lan -H 10.10.10.233 -U ADMIN -P ADMIN sdr > > > > > > > > > CPU1 Temp | 0 unspecified | ok > > > > > > > > > CPU2 Temp | no reading | ns > > > > > > > > > System Temp | 45 degrees C | ok > > > > > > > > > CPU1 Vcore | 0.98 Volts | ok > > > > > > > > > CPU2 Vcore | no reading | ns > > > > > > > > > CPU1 DIMM | 1.51 Volts | ok > > > > > > > > > CPU2 DIMM | no reading | ns > > > > > > > > > ^C > > > > > > > > > [root@tpw ~]# ipmimonitoring -h 10.10.10.233 -u ADMIN -p ADMIN > > > > > > > > > Record_ID | Sensor Name | Sensor Group | Monitoring Status| Sensor Units | Sensor Reading > > > > > > > > > 4 | System Temp | Temperature | Nominal | C | 45.000000 > > > > > > > > > 5 | CPU1 Vcore | Voltage | Nominal | V | 0.976000 > > > > > > > > > 6 | CPU2 Vcore | Voltage | Nominal | V | 0.000000 > > > > > > > > > 7 | CPU1 DIMM | Voltage | Nominal | V | 1.512000 > > > > > > > > > 8 | CPU2 DIMM | Voltage | Nominal | V | 0.000000 > > > > > > > > > 9 | +1.5V | Voltage | Nominal | V | 1.504000 > > > > > > > > > 10 | +3.3V | Voltage | Nominal | V | 3.240000 > > > > > > > > > 11 | +3.3VSB | Voltage | Nominal | V | 3.240000 > > > > > > > > > 12 | +5V | Voltage | Nominal | V | 5.120000 > > > > > > > > > 13 | +12V | Voltage | Nominal | V | 12.190000 > > > > > > > > > 14 | VBAT | Voltage | Nominal | V | 3.240000 > > > > > > > > > 15 | Fan1 | Fan | Nominal | RPM | 6528.000000 > > > > > > > > > 16 | Fan2 | Fan | Nominal | RPM | 7072.000000 > > > > > > > > > 17 | Fan3 | Fan | Nominal | RPM | 0.000000 > > > > > > > > > 18 | Fan4 | Fan | Nominal | RPM | 0.000000 > > > > > > > > > 19 | Fan5 | Fan | Nominal | RPM | 5644.000000 > > > > > > > > > 20 | Fan6 | Fan | Nominal | RPM | 5304.000000 > > > > > > > > > 21 | Fan7 | Fan | Nominal | RPM | 7072.000000 > > > > > > > > > 22 | Fan8 | Fan | Nominal | RPM | 0.000000 > > > > > > > > > 23 | Intrusion | Physical Security | Nominal | N/A | '' > > > > > > > > > 24 | PS Failure | Power Supply | Nominal | N/A | '' > > > > > > > > > [root@tpw ~]# > > > > > > > > > -------------------------------------------------------------------------- > > > > > > > > > > > > > > > > > > Does anybody have an idea how this problem could be fixed? > > > > > > > > > > > > > > > > > > best regards, > > > > > > > > > Werner > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > > Freeipmi-users mailing list > > > > > > > > > Freeipmi-users@... > > > > > > > > > http://****lists.gnu.org/mailman/listinfo/freeipmi-users > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > Freeipmi-users mailing list > > > > > > > Freeipmi-users@... > > > > > > > http://***lists.gnu.org/mailman/listinfo/freeipmi-users > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > Freeipmi-users mailing list > > > > Freeipmi-users@... > > > > http://**lists.gnu.org/mailman/listinfo/freeipmi-users > > > > > > > > > > > > _______________________________________________ > > Freeipmi-users mailing list > > Freeipmi-users@... > > http://*lists.gnu.org/mailman/listinfo/freeipmi-users > > _______________________________________________ Freeipmi-users mailing list Freeipmi-users@... http://lists.gnu.org/mailman/listinfo/freeipmi-users |
|
|
Re: "authentication type unavailable for attempted privilege level" with Intel S5000PAL Mainboard
by Al Chu11
::
Rate this Message:
Hi Werner,
Great to hear. > I have configured the IPMI settings and IPMI user via the "Intel > Server Deployment" CD: > http://*downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&Inst=Yes&ProductID=2451&DwnldID=17974&strOSs=38&OSFullName=OS%20Independent&lang=eng Ugh ... that's sort of disappointing. Once in awhile I've thought of defaulting every FreeIPMI tool and all libraries to have a default privilege of 'admin', because some vendors just seem to want to have all their software default to use 'admin' privileges everywhere. However, I have restrained myself because having different security levels/privileges is part of the reason privileges exist in IPMI. Sigh ... :P Al On Thu, 2009-09-03 at 17:45 +0200, Werner Fischer wrote: > Hi Al, > > you are absolutely right! > > In this way it works: > > [root@tpw ~]# ipmimonitoring -V > ipmimonitoring - 0.7.12.beta2 > Copyright (C) 2007-2008 Lawrence Livermore National Security, LLC. > Copyright (C) 2006-2007 The Regents of the University of California. > This program is free software; you may redistribute it under the terms of > the GNU General Public License. This program has absolutely no warranty. > [root@tpw ~]# > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -l admin -u admin -p relation > Caching SDR repository information: /root/.freeipmi/sdr-cache/sdr-cache-tpw.192.168.1.211 > Caching SDR record 143 of 143 (current record ID 143) > Record_ID | Sensor Name | Sensor Group | Monitoring Status| Sensor Units | Sensor Reading > 1 | BB +1.2V Vtt | Voltage | Nominal | V | 1.197000 > 2 | BB +1.5V AUX | Voltage | Nominal | V | 1.466400 > 3 | BB +1.5V | Voltage | Nominal | V | 1.482000 > 4 | BB +1.8V | Voltage | Nominal | V | 1.785000 > 5 | BB +3.3V | Voltage | Nominal | V | 3.354000 > 6 | BB +3.3V STB | Voltage | Nominal | V | 3.354000 > 7 | BB +1.5V ESB | Voltage | Nominal | V | 1.505400 > 8 | BB +5V | Voltage | Nominal | V | 5.070000 > 9 | BB +12V AUX | Voltage | Nominal | V | 11.904000 > > I have configured the IPMI settings and IPMI user via the "Intel Server Deployment" CD: > http://*downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&Inst=Yes&ProductID=2451&DwnldID=17974&strOSs=38&OSFullName=OS%20Independent&lang=eng > > I was not aware of the -l option. > Sorry for causing the inconvenience. > > And thanks a lot again for your help! > > Best regards, > Werner > > On Mon, 2009-08-31 at 10:06 -0700, Al Chu wrote: > > Hey Werner, > > > > Actually, your default config may be the issue afterall, not the > > motherboard. Your default config is not allowing authentication by any > > privilege level other than "admin". How about trying ipmimonitoring > > with the -l admin, to tell ipmimonitoring to use the admin privilege > > level. > > > > Out of my curiosity, did the Intel motherboard come like this by > > default? > > > > Al > > > > On Mon, 2009-08-31 at 12:18 +0200, Werner Fischer wrote: > > > Hi Al, > > > > > > sorry for my late reply. Now I'm back in the office. You find my results > > > below: > > > > > > On Mon, 2009-08-24 at 10:40 -0700, Al Chu wrote: > > > > Hi Werner, > > > > > > > > Thanks for the feedback. > > > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 --debug -u admin -p > > > > > relation > > > > > > > > Could you run --debug with the -W "authcap". I'm wondering if it's > > > > failing in a different location and the workaround has to be in multiple > > > > places. > > > sure, here it is: > > > > > > ------------------------------------------------------------------------------------- > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W "authcap" --debug -u admin -p relation > > > 192.168.1.211: ===================================================== > > > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Request > > > 192.168.1.211: ===================================================== > > > 192.168.1.211: RMCP Header: > > > 192.168.1.211: ------------ > > > 192.168.1.211: [ 6h] = version[ 8b] > > > 192.168.1.211: [ 0h] = reserved[ 8b] > > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > > 192.168.1.211: IPMI Session Header: > > > 192.168.1.211: -------------------- > > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > > 192.168.1.211: [ 0h] = session_id[32b] > > > 192.168.1.211: [ 9h] = ipmi_msg_len[ 8b] > > > 192.168.1.211: IPMI Message Header: > > > 192.168.1.211: -------------------- > > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > > 192.168.1.211: [ 6h] = net_fn[ 6b] > > > 192.168.1.211: [ C8h] = checksum1[ 8b] > > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > > 192.168.1.211: [ 33h] = rq_seq[ 6b] > > > 192.168.1.211: IPMI Command Data: > > > 192.168.1.211: ------------------ > > > 192.168.1.211: [ 38h] = cmd[ 8b] > > > 192.168.1.211: [ Eh] = channel_number[ 4b] > > > 192.168.1.211: [ 0h] = reserved1[ 4b] > > > 192.168.1.211: [ 3h] = maximum_privilege_level[ 4b] > > > 192.168.1.211: [ 0h] = reserved2[ 4b] > > > 192.168.1.211: IPMI Trailer: > > > 192.168.1.211: -------------- > > > 192.168.1.211: [ 6Ah] = checksum2[ 8b] > > > 192.168.1.211: ===================================================== > > > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Response > > > 192.168.1.211: ===================================================== > > > 192.168.1.211: RMCP Header: > > > 192.168.1.211: ------------ > > > 192.168.1.211: [ 6h] = version[ 8b] > > > 192.168.1.211: [ 0h] = reserved[ 8b] > > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > > 192.168.1.211: IPMI Session Header: > > > 192.168.1.211: -------------------- > > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > > 192.168.1.211: [ 0h] = session_id[32b] > > > 192.168.1.211: [ 10h] = ipmi_msg_len[ 8b] > > > 192.168.1.211: IPMI Message Header: > > > 192.168.1.211: -------------------- > > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > > 192.168.1.211: [ 7h] = net_fn[ 6b] > > > 192.168.1.211: [ 63h] = checksum1[ 8b] > > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > > 192.168.1.211: [ 33h] = rq_seq[ 6b] > > > 192.168.1.211: IPMI Command Data: > > > 192.168.1.211: ------------------ > > > 192.168.1.211: [ 38h] = cmd[ 8b] > > > 192.168.1.211: [ 0h] = comp_code[ 8b] > > > 192.168.1.211: [ 1h] = channel_number[ 8b] > > > 192.168.1.211: [ 0h] = authentication_type.none[ 1b] > > > 192.168.1.211: [ 0h] = authentication_type.md2[ 1b] > > > 192.168.1.211: [ 0h] = authentication_type.md5[ 1b] > > > 192.168.1.211: [ 0h] = authentication_type.reserved1[ 1b] > > > 192.168.1.211: [ 0h] = authentication_type.straight_password_key[ 1b] > > > 192.168.1.211: [ 0h] = authentication_type.oem_prop[ 1b] > > > 192.168.1.211: [ 0h] = authentication_type.reserved2[ 2b] > > > 192.168.1.211: [ 0h] = authentication_status.anonymous_login[ 1b] > > > 192.168.1.211: [ 0h] = authentication_status.null_username[ 1b] > > > 192.168.1.211: [ 1h] = authentication_status.non_null_username[ 1b] > > > 192.168.1.211: [ 0h] = authentication_status.user_level_authentication[ 1b] > > > 192.168.1.211: [ 0h] = authentication_status.per_message_authentication[ 1b] > > > 192.168.1.211: [ 0h] = authentication_status.reserved[ 3b] > > > 192.168.1.211: [ 0h] = reserved1[ 8b] > > > 192.168.1.211: [ 0h] = oem_id[24b] > > > 192.168.1.211: [ 0h] = oem_auxiliary_data[ 8b] > > > 192.168.1.211: IPMI Trailer: > > > 192.168.1.211: -------------- > > > 192.168.1.211: [ D7h] = checksum2[ 8b] > > > 192.168.1.211: ===================================================== > > > 192.168.1.211: IPMI 1.5 Get Session Challenge Request > > > 192.168.1.211: ===================================================== > > > 192.168.1.211: RMCP Header: > > > 192.168.1.211: ------------ > > > 192.168.1.211: [ 6h] = version[ 8b] > > > 192.168.1.211: [ 0h] = reserved[ 8b] > > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > > 192.168.1.211: IPMI Session Header: > > > 192.168.1.211: -------------------- > > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > > 192.168.1.211: [ 0h] = session_id[32b] > > > 192.168.1.211: [ 18h] = ipmi_msg_len[ 8b] > > > 192.168.1.211: IPMI Message Header: > > > 192.168.1.211: -------------------- > > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > > 192.168.1.211: [ 6h] = net_fn[ 6b] > > > 192.168.1.211: [ C8h] = checksum1[ 8b] > > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > > 192.168.1.211: [ 34h] = rq_seq[ 6b] > > > 192.168.1.211: IPMI Command Data: > > > 192.168.1.211: ------------------ > > > 192.168.1.211: [ 39h] = cmd[ 8b] > > > 192.168.1.211: [ 2h] = authentication_type[ 4b] > > > 192.168.1.211: [ 0h] = reserved[ 4b] > > > 192.168.1.211: [ BYTE ARRAY ... ] = user_name[16B] > > > 192.168.1.211: [ 61h 64h 6Dh 69h 6Eh 00h 00h 00h ] > > > 192.168.1.211: [ 00h 00h 00h 00h 00h 00h 00h 00h ] > > > 192.168.1.211: IPMI Trailer: > > > 192.168.1.211: -------------- > > > 192.168.1.211: [ 6Bh] = checksum2[ 8b] > > > 192.168.1.211: ===================================================== > > > 192.168.1.211: IPMI 1.5 Get Session Challenge Response > > > 192.168.1.211: ===================================================== > > > 192.168.1.211: RMCP Header: > > > 192.168.1.211: ------------ > > > 192.168.1.211: [ 6h] = version[ 8b] > > > 192.168.1.211: [ 0h] = reserved[ 8b] > > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > > 192.168.1.211: IPMI Session Header: > > > 192.168.1.211: -------------------- > > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > > 192.168.1.211: [ 0h] = session_id[32b] > > > 192.168.1.211: [ 1Ch] = ipmi_msg_len[ 8b] > > > 192.168.1.211: IPMI Message Header: > > > 192.168.1.211: -------------------- > > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > > 192.168.1.211: [ 7h] = net_fn[ 6b] > > > 192.168.1.211: [ 63h] = checksum1[ 8b] > > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > > 192.168.1.211: [ 34h] = rq_seq[ 6b] > > > 192.168.1.211: IPMI Command Data: > > > 192.168.1.211: ------------------ > > > 192.168.1.211: [ 39h] = cmd[ 8b] > > > 192.168.1.211: [ 0h] = comp_code[ 8b] > > > 192.168.1.211: [ AC03D99h] = temp_session_id[32b] > > > 192.168.1.211: [ BYTE ARRAY ... ] = challenge_string[16B] > > > 192.168.1.211: [ 69h F4h 8Ah 89h 60h E4h E2h 1Ch ] > > > 192.168.1.211: [ 2Ah CCh 96h A0h 6Dh 5Ah CAh 7Ah ] > > > 192.168.1.211: IPMI Trailer: > > > 192.168.1.211: -------------- > > > 192.168.1.211: [ 4Eh] = checksum2[ 8b] > > > 192.168.1.211: ===================================================== > > > 192.168.1.211: IPMI 1.5 Activiate Session Request > > > 192.168.1.211: ===================================================== > > > 192.168.1.211: RMCP Header: > > > 192.168.1.211: ------------ > > > 192.168.1.211: [ 6h] = version[ 8b] > > > 192.168.1.211: [ 0h] = reserved[ 8b] > > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > > 192.168.1.211: IPMI Session Header: > > > 192.168.1.211: -------------------- > > > 192.168.1.211: [ 2h] = authentication_type[ 8b] > > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > > 192.168.1.211: [ AC03D99h] = session_id[32b] > > > 192.168.1.211: [ BYTE ARRAY ... ] = authentication_code[16B] > > > 192.168.1.211: [ 6Bh 25h AAh 78h 0Bh D3h F8h 14h ] > > > 192.168.1.211: [ C4h 57h 15h 6Eh 15h C3h 15h F6h ] > > > 192.168.1.211: [ 1Dh] = ipmi_msg_len[ 8b] > > > 192.168.1.211: IPMI Message Header: > > > 192.168.1.211: -------------------- > > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > > 192.168.1.211: [ 6h] = net_fn[ 6b] > > > 192.168.1.211: [ C8h] = checksum1[ 8b] > > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > > 192.168.1.211: [ 35h] = rq_seq[ 6b] > > > 192.168.1.211: IPMI Command Data: > > > 192.168.1.211: ------------------ > > > 192.168.1.211: [ 3Ah] = cmd[ 8b] > > > 192.168.1.211: [ 2h] = authentication_type[ 4b] > > > 192.168.1.211: [ 0h] = reserved1[ 4b] > > > 192.168.1.211: [ 3h] = maximum_privilege_level[ 4b] > > > 192.168.1.211: [ 0h] = reserved2[ 4b] > > > 192.168.1.211: [ BYTE ARRAY ... ] = challenge_string[16B] > > > 192.168.1.211: [ 69h F4h 8Ah 89h 60h E4h E2h 1Ch ] > > > 192.168.1.211: [ 2Ah CCh 96h A0h 6Dh 5Ah CAh 7Ah ] > > > 192.168.1.211: [ 279F274Fh] = initial_outbound_sequence_number[32b] > > > 192.168.1.211: IPMI Trailer: > > > 192.168.1.211: -------------- > > > 192.168.1.211: [ 47h] = checksum2[ 8b] > > > 192.168.1.211: ===================================================== > > > 192.168.1.211: IPMI 1.5 Activiate Session Response > > > 192.168.1.211: ===================================================== > > > 192.168.1.211: RMCP Header: > > > 192.168.1.211: ------------ > > > 192.168.1.211: [ 6h] = version[ 8b] > > > 192.168.1.211: [ 0h] = reserved[ 8b] > > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > > 192.168.1.211: IPMI Session Header: > > > 192.168.1.211: -------------------- > > > 192.168.1.211: [ 2h] = authentication_type[ 8b] > > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > > 192.168.1.211: [ AC03D99h] = session_id[32b] > > > 192.168.1.211: [ BYTE ARRAY ... ] = authentication_code[16B] > > > 192.168.1.211: [ 29h BCh 75h CEh 94h F5h 23h 0Eh ] > > > 192.168.1.211: [ A9h A9h 97h FFh 58h 22h C4h 89h ] > > > 192.168.1.211: [ 8h] = ipmi_msg_len[ 8b] > > > 192.168.1.211: IPMI Message Header: > > > 192.168.1.211: -------------------- > > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > > 192.168.1.211: [ 7h] = net_fn[ 6b] > > > 192.168.1.211: [ 63h] = checksum1[ 8b] > > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > > 192.168.1.211: [ 35h] = rq_seq[ 6b] > > > 192.168.1.211: IPMI Command Data: > > > 192.168.1.211: ------------------ > > > 192.168.1.211: [ 3Ah] = cmd[ 8b] > > > 192.168.1.211: [ CCh] = comp_code[ 8b] > > > 192.168.1.211: IPMI Trailer: > > > 192.168.1.211: -------------- > > > 192.168.1.211: [ 6h] = checksum2[ 8b] > > > ipmi_ctx_open_outofband: bad completion code: request data/parameter invalid > > > [root@tpw ~]# > > > > > > ------------------------------------------------------------------------------------- > > > > > > > > > > > A few other random thoughts. > > > > > > > > Could you also try different authentication types. Like "-a md2" and > > > > "-a straight_password_key". > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="authcap" -u admin -p relation > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="authcap" -a md2 -u admin -p relation > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="authcap" -a STRAIGHT_PASSWORD_KEY -u admin -p relation > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > [root@tpw ~]# > > > > > > > > > > > Also, what is the output of "bmc-config --checkout > > > > --section=lan_conf_auth", just so we can check to make sure the > > > > configuration looks good. > > > I ran the command remotely as I have currently no Linux installed on the > > > box (if it is necessary, just tell me, than I can put a Linux on it and > > > run bmc-config locally): > > > > > > [root@tpw ~]# bmc-config -h 192.168.1.211 -u admin -p relation --checkout --section=lan_conf_auth > > > # > > > # Section Lan_Conf_Auth Comments > > > # > > > # In the Lan_Conf_Auth section, allowable authentication mechanisms for IPMI 1.5 > > > # is configured. Most users will want to set all "MD5" authentication to "Yes" > > > # and the rest to "No". If you have configured a NULL username and a NULL > > > # password, you will also want to configure some of the "None" fields to "Yes" > > > # to allow "None" authentication to work. Some motherboards do not allow you to > > > # enable OEM authentication, so you may wish to set all OEM related fields to > > > # "No". > > > # > > > Section Lan_Conf_Auth > > > ## Possible values: Yes/No > > > Callback_Enable_Auth_Type_None No > > > ## Possible values: Yes/No > > > Callback_Enable_Auth_Type_MD5 No > > > ## Possible values: Yes/No > > > Callback_Enable_Auth_Type_Straight_Password No > > > ## Possible values: Yes/No > > > User_Enable_Auth_Type_None No > > > ## Possible values: Yes/No > > > User_Enable_Auth_Type_MD5 No > > > ## Possible values: Yes/No > > > User_Enable_Auth_Type_Straight_Password No > > > ## Possible values: Yes/No > > > Operator_Enable_Auth_Type_None No > > > ## Possible values: Yes/No > > > Operator_Enable_Auth_Type_MD5 No > > > ## Possible values: Yes/No > > > Operator_Enable_Auth_Type_Straight_Password No > > > ## Possible values: Yes/No > > > Admin_Enable_Auth_Type_None No > > > ## Possible values: Yes/No > > > Admin_Enable_Auth_Type_MD5 Yes > > > ## Possible values: Yes/No > > > Admin_Enable_Auth_Type_Straight_Password Yes > > > ## Possible values: Yes/No > > > OEM_Enable_Auth_Type_None No > > > ## Possible values: Yes/No > > > OEM_Enable_Auth_Type_MD5 No > > > ## Possible values: Yes/No > > > OEM_Enable_Auth_Type_Straight_Password No > > > EndSection > > > [root@tpw ~]# > > > > > > If you need any further results, just let me know! > > > > > > Thanks for your support, > > > Werner > > > > > > > > > > > Thanks, > > > > > > > > Al > > > > > > > > On Mon, 2009-08-24 at 15:31 +0200, Werner Fischer wrote: > > > > > Hi Al, > > > > > > > > > > thanks for the updated tar.gz. I tried it, but somehow it still seems to > > > > > cause problems (see below). I'll be two days out of office - so I can do > > > > > further tests on Thursday. > > > > > > > > > > thanks for your support! > > > > > > > > > > [root@tpw ~]# rpm -q freeipmi > > > > > freeipmi-0.7.12.beta2-1.fc9.i386 > > > > > [root@tpw ~]# ipmimonitoring -V > > > > > ipmimonitoring - 0.7.12.beta2 > > > > > Copyright (C) 2007-2008 Lawrence Livermore National Security, LLC. > > > > > Copyright (C) 2006-2007 The Regents of the University of California. > > > > > This program is free software; you may redistribute it under the terms of > > > > > the GNU General Public License. This program has absolutely no warranty. > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="authcap" -u admin -p relation > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 --debug -u admin -p relation > > > > > 192.168.1.211: ===================================================== > > > > > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Request > > > > > 192.168.1.211: ===================================================== > > > > > 192.168.1.211: RMCP Header: > > > > > 192.168.1.211: ------------ > > > > > 192.168.1.211: [ 6h] = version[ 8b] > > > > > 192.168.1.211: [ 0h] = reserved[ 8b] > > > > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > > > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > > > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > > > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > > > > 192.168.1.211: IPMI Session Header: > > > > > 192.168.1.211: -------------------- > > > > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > > > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > > > > 192.168.1.211: [ 0h] = session_id[32b] > > > > > 192.168.1.211: [ 9h] = ipmi_msg_len[ 8b] > > > > > 192.168.1.211: IPMI Message Header: > > > > > 192.168.1.211: -------------------- > > > > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > > > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > > > > 192.168.1.211: [ 6h] = net_fn[ 6b] > > > > > 192.168.1.211: [ C8h] = checksum1[ 8b] > > > > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > > > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > > > > 192.168.1.211: [ 13h] = rq_seq[ 6b] > > > > > 192.168.1.211: IPMI Command Data: > > > > > 192.168.1.211: ------------------ > > > > > 192.168.1.211: [ 38h] = cmd[ 8b] > > > > > 192.168.1.211: [ Eh] = channel_number[ 4b] > > > > > 192.168.1.211: [ 0h] = reserved1[ 4b] > > > > > 192.168.1.211: [ 3h] = maximum_privilege_level[ 4b] > > > > > 192.168.1.211: [ 0h] = reserved2[ 4b] > > > > > 192.168.1.211: IPMI Trailer: > > > > > 192.168.1.211: -------------- > > > > > 192.168.1.211: [ EAh] = checksum2[ 8b] > > > > > 192.168.1.211: ===================================================== > > > > > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Response > > > > > 192.168.1.211: ===================================================== > > > > > 192.168.1.211: RMCP Header: > > > > > 192.168.1.211: ------------ > > > > > 192.168.1.211: [ 6h] = version[ 8b] > > > > > 192.168.1.211: [ 0h] = reserved[ 8b] > > > > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > > > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > > > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > > > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > > > > 192.168.1.211: IPMI Session Header: > > > > > 192.168.1.211: -------------------- > > > > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > > > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > > > > 192.168.1.211: [ 0h] = session_id[32b] > > > > > 192.168.1.211: [ 10h] = ipmi_msg_len[ 8b] > > > > > 192.168.1.211: IPMI Message Header: > > > > > 192.168.1.211: -------------------- > > > > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > > > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > > > > 192.168.1.211: [ 7h] = net_fn[ 6b] > > > > > 192.168.1.211: [ 63h] = checksum1[ 8b] > > > > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > > > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > > > > 192.168.1.211: [ 13h] = rq_seq[ 6b] > > > > > 192.168.1.211: IPMI Command Data: > > > > > 192.168.1.211: ------------------ > > > > > 192.168.1.211: [ 38h] = cmd[ 8b] > > > > > 192.168.1.211: [ 0h] = comp_code[ 8b] > > > > > 192.168.1.211: [ 1h] = channel_number[ 8b] > > > > > 192.168.1.211: [ 0h] = authentication_type.none[ 1b] > > > > > 192.168.1.211: [ 0h] = authentication_type.md2[ 1b] > > > > > 192.168.1.211: [ 0h] = authentication_type.md5[ 1b] > > > > > 192.168.1.211: [ 0h] = authentication_type.reserved1[ 1b] > > > > > 192.168.1.211: [ 0h] = authentication_type.straight_password_key[ 1b] > > > > > 192.168.1.211: [ 0h] = authentication_type.oem_prop[ 1b] > > > > > 192.168.1.211: [ 0h] = authentication_type.reserved2[ 2b] > > > > > 192.168.1.211: [ 0h] = authentication_status.anonymous_login[ 1b] > > > > > 192.168.1.211: [ 0h] = authentication_status.null_username[ 1b] > > > > > 192.168.1.211: [ 1h] = authentication_status.non_null_username[ 1b] > > > > > 192.168.1.211: [ 0h] = authentication_status.user_level_authentication[ 1b] > > > > > 192.168.1.211: [ 0h] = authentication_status.per_message_authentication[ 1b] > > > > > 192.168.1.211: [ 0h] = authentication_status.reserved[ 3b] > > > > > 192.168.1.211: [ 0h] = reserved1[ 8b] > > > > > 192.168.1.211: [ 0h] = oem_id[24b] > > > > > 192.168.1.211: [ 0h] = oem_auxiliary_data[ 8b] > > > > > 192.168.1.211: IPMI Trailer: > > > > > 192.168.1.211: -------------- > > > > > 192.168.1.211: [ 57h] = checksum2[ 8b] > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > [root@tpw ~]# > > > > > > > > > > > > > > > On Fri, 2009-08-21 at 14:03 -0700, Al Chu wrote: > > > > > > Hi Werner, > > > > > > > > > > > > I've got a test tar.gz here: > > > > > > > > > > > > http://***ftp.gluster.com/pub/freeipmi/qa-release/freeipmi-0.7.12.beta2.tar.gz > > > > > > > > > > > > This makes it so the 'authcap' workaround should work for you. Can you > > > > > > give it a shot to make sure it works? > > > > > > > > > > > > Thanks, > > > > > > Al > > > > > > > > > > > > On Fri, 2009-08-21 at 08:44 -0700, Al Chu wrote: > > > > > > > Hi Werner, > > > > > > > > > > > > > > > 192.168.1.211: [ 0h] = authentication_type.none[ 1b] > > > > > > > > 192.168.1.211: [ 0h] = authentication_type.md2[ 1b] > > > > > > > > 192.168.1.211: [ 0h] = authentication_type.md5[ 1b] > > > > > > > > 192.168.1.211: [ 0h] = authentication_type.reserved1[ 1b] > > > > > > > > 192.168.1.211: [ 0h] = authentication_type.straight_password_key[ 1b] > > > > > > > > 192.168.1.211: [ 0h] = authentication_type.oem_prop[ 1b] > > > > > > > > > > > > > > This indicates that no authentication support is enabled, which is very > > > > > > > unlikely of being true (which we could verify via 'bmc-config --checkout > > > > > > > --section=lan_conf_auth'). > > > > > > > > > > > > > > I'll modify the 'authcap' workaround to also encompass this case and > > > > > > > post a beta tar.gz for you to check out. > > > > > > > > > > > > > > Al > > > > > > > > > > > > > > On Fri, 2009-08-21 at 09:58 +0200, Werner Fischer wrote: > > > > > > > > Hi Al, > > > > > > > > > > > > > > > > thanks for your fast answer. > > > > > > > > > > > > > > > > Below you find the requested debug output. I'm using version 0.7.11. The > > > > > > > > "authcap" workaround does not fix the problem. After executing with > > > > > > > > debug to the affected Intel S5000PAL system (IP 192.168.1.211) I again > > > > > > > > verified the correct behavior of ipmimonitoring to the other system > > > > > > > > (Supermicro) to IP 10.10.10.233. > > > > > > > > > > > > > > > > [root@tpw ~]# rpm -q freeipmi > > > > > > > > freeipmi-0.7.11-1.fc9.i386 > > > > > > > > [root@tpw ~]# ipmimonitoring -V > > > > > > > > ipmimonitoring - 0.7.11 > > > > > > > > Copyright (C) 2007-2008 Lawrence Livermore National Security, LLC. > > > > > > > > Copyright (C) 2006-2007 The Regents of the University of California. > > > > > > > > This program is free software; you may redistribute it under the terms of > > > > > > > > the GNU General Public License. This program has absolutely no warranty. > > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > > > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > > > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="authcap" -u admin -p relation > > > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 --debug -u admin -p relation > > > > > > > > 192.168.1.211: ===================================================== > > > > > > > > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Request > > > > > > > > 192.168.1.211: ===================================================== > > > > > > > > 192.168.1.211: RMCP Header: > > > > > > > > 192.168.1.211: ------------ > > > > > > > > 192.168.1.211: [ 6h] = version[ 8b] > > > > > > > > 192.168.1.211: [ 0h] = reserved[ 8b] > > > > > > > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > > > > > > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > > > > > > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > > > > > > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > > > > > > > 192.168.1.211: IPMI Session Header: > > > > > > > > 192.168.1.211: -------------------- > > > > > > > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > > > > > > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > > > > > > > 192.168.1.211: [ 0h] = session_id[32b] > > > > > > > > 192.168.1.211: [ 9h] = ipmi_msg_len[ 8b] > > > > > > > > 192.168.1.211: IPMI Message Header: > > > > > > > > 192.168.1.211: -------------------- > > > > > > > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > > > > > > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > > > > > > > 192.168.1.211: [ 6h] = net_fn[ 6b] > > > > > > > > 192.168.1.211: [ C8h] = checksum1[ 8b] > > > > > > > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > > > > > > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > > > > > > > 192.168.1.211: [ 8h] = rq_seq[ 6b] > > > > > > > > 192.168.1.211: IPMI Command Data: > > > > > > > > 192.168.1.211: ------------------ > > > > > > > > 192.168.1.211: [ 38h] = cmd[ 8b] > > > > > > > > 192.168.1.211: [ Eh] = channel_number[ 4b] > > > > > > > > 192.168.1.211: [ 0h] = reserved1[ 4b] > > > > > > > > 192.168.1.211: [ 3h] = maximum_privilege_level[ 4b] > > > > > > > > 192.168.1.211: [ 0h] = reserved2[ 4b] > > > > > > > > 192.168.1.211: IPMI Trailer: > > > > > > > > 192.168.1.211: -------------- > > > > > > > > 192.168.1.211: [ 16h] = checksum2[ 8b] > > > > > > > > 192.168.1.211: ===================================================== > > > > > > > > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Response > > > > > > > > 192.168.1.211: ===================================================== > > > > > > > > 192.168.1.211: RMCP Header: > > > > > > > > 192.168.1.211: ------------ > > > > > > > > 192.168.1.211: [ 6h] = version[ 8b] > > > > > > > > 192.168.1.211: [ 0h] = reserved[ 8b] > > > > > > > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > > > > > > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > > > > > > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > > > > > > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > > > > > > > 192.168.1.211: IPMI Session Header: > > > > > > > > 192.168.1.211: -------------------- > > > > > > > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > > > > > > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > > > > > > > 192.168.1.211: [ 0h] = session_id[32b] > > > > > > > > 192.168.1.211: [ 10h] = ipmi_msg_len[ 8b] > > > > > > > > 192.168.1.211: IPMI Message Header: > > > > > > > > 192.168.1.211: -------------------- > > > > > > > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > > > > > > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > > > > > > > 192.168.1.211: [ 7h] = net_fn[ 6b] > > > > > > > > 192.168.1.211: [ 63h] = checksum1[ 8b] > > > > > > > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > > > > > > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > > > > > > > 192.168.1.211: [ 8h] = rq_seq[ 6b] > > > > > > > > 192.168.1.211: IPMI Command Data: > > > > > > > > 192.168.1.211: ------------------ > > > > > > > > 192.168.1.211: [ 38h] = cmd[ 8b] > > > > > > > > 192.168.1.211: [ 0h] = comp_code[ 8b] > > > > > > > > 192.168.1.211: [ 1h] = channel_number[ 8b] > > > > > > > > 192.168.1.211: [ 0h] = authentication_type.none[ 1b] > > > > > > > > 192.168.1.211: [ 0h] = authentication_type.md2[ 1b] > > > > > > > > 192.168.1.211: [ 0h] = authentication_type.md5[ 1b] > > > > > > > > 192.168.1.211: [ 0h] = authentication_type.reserved1[ 1b] > > > > > > > > 192.168.1.211: [ 0h] = authentication_type.straight_password_key[ 1b] > > > > > > > > 192.168.1.211: [ 0h] = authentication_type.oem_prop[ 1b] > > > > > > > > 192.168.1.211: [ 0h] = authentication_type.reserved2[ 2b] > > > > > > > > 192.168.1.211: [ 0h] = authentication_status.anonymous_login[ 1b] > > > > > > > > 192.168.1.211: [ 0h] = authentication_status.null_username[ 1b] > > > > > > > > 192.168.1.211: [ 1h] = authentication_status.non_null_username[ 1b] > > > > > > > > 192.168.1.211: [ 0h] = authentication_status.user_level_authentication[ 1b] > > > > > > > > 192.168.1.211: [ 0h] = authentication_status.per_message_authentication[ 1b] > > > > > > > > 192.168.1.211: [ 0h] = authentication_status.reserved[ 3b] > > > > > > > > 192.168.1.211: [ 0h] = reserved1[ 8b] > > > > > > > > 192.168.1.211: [ 0h] = oem_id[24b] > > > > > > > > 192.168.1.211: [ 0h] = oem_auxiliary_data[ 8b] > > > > > > > > 192.168.1.211: IPMI Trailer: > > > > > > > > 192.168.1.211: -------------- > > > > > > > > 192.168.1.211: [ 83h] = checksum2[ 8b] > > > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > > > [root@tpw ~]# > > > > > > > > [root@tpw ~]# > > > > > > > > [root@tpw ~]# > > > > > > > > [root@tpw ~]# ipmimonitoring -h 10.10.10.233 -u ADMIN -p ADMIN > > > > > > > > Record_ID | Sensor Name | Sensor Group | Monitoring Status| Sensor Units | Sensor Reading > > > > > > > > 4 | System Temp | Temperature | Nominal | C | 41.000000 > > > > > > > > 5 | CPU1 Vcore | Voltage | Nominal | V | 0.976000 > > > > > > > > 7 | CPU1 DIMM | Voltage | Nominal | V | 1.512000 > > > > > > > > 9 | +1.5V | Voltage | Nominal | V | 1.504000 > > > > > > > > 10 | +3.3V | Voltage | Nominal | V | 3.240000 > > > > > > > > 11 | +3.3VSB | Voltage | Nominal | V | 3.240000 > > > > > > > > 12 | +5V | Voltage | Nominal | V | 5.120000 > > > > > > > > 13 | +12V | Voltage | Nominal | V | 12.190000 > > > > > > > > 14 | VBAT | Voltage | Nominal | V | 3.216000 > > > > > > > > 15 | Fan1 | Fan | Nominal | RPM | 3264.000000 > > > > > > > > 16 | Fan2 | Fan | Nominal | RPM | 3536.000000 > > > > > > > > 19 | Fan5 | Fan | Nominal | RPM | 2788.000000 > > > > > > > > 20 | Fan6 | Fan | Nominal | RPM | 2652.000000 > > > > > > > > 21 | Fan7 | Fan | Nominal | RPM | 3536.000000 > > > > > > > > 23 | Intrusion | Physical Security | Nominal | N/A | 'OK' > > > > > > > > 24 | PS Failure | Power Supply | Nominal | N/A | 'OK' > > > > > > > > [root@tpw ~]# > > > > > > > > > > > > > > > > Werner > > > > > > > > > > > > > > > > On Wed, 2009-08-19 at 08:58 -0700, Al Chu wrote: > > > > > > > > > Hi Werner, > > > > > > > > > > > > > > > > > > It's possible the motherboard is not reporting supported authentication > > > > > > > > > types correctly. You could give the "authcap" workaround a shot. > > > > > > > > > However, if this is being non-compliant in the way that I think it is, > > > > > > > > > the "authcap" workaround won't work (b/c it currently handles a > > > > > > > > > different non-compliance bug). Could you send me the output from > > > > > > > > > --debug? If we can verify the issue, I'll implement a new workaround > > > > > > > > > for you. > > > > > > > > > > > > > > > > > > BTW, if you need the intel20 workarounds for IPMI 2.0, you may need to > > > > > > > > > upgrade. There were some bugs found a few releases ago. > > > > > > > > > > > > > > > > > > 0.7.4 - 12/15/08 > > > > > > > > > ---------------- > > > > > > > > > <snip> > > > > > > > > > o Fix Intel IPMI 2.0 workarounds in all tools/libraries. > > > > > > > > > <snip> > > > > > > > > > > > > > > > > > > Al > > > > > > > > > > > > > > > > > > On Wed, 2009-08-19 at 14:16 +0200, Werner Fischer wrote: > > > > > > > > > > Dear freeipmi users/developers, > > > > > > > > > > > > > > > > > > > > I'm trying to monitor an Intel SR2500 server (this server has the Intel > > > > > > > > > > S5000PAL mainboard in it). > > > > > > > > > > > > > > > > > > > > While I can monitor it using ipmitool, I keep getting errors with > > > > > > > > > > ipmimonitoring from freeipmi. Also using the "-W" parameter for > > > > > > > > > > workarounds (as described in the manpage of ipmimonitoring) doesn't > > > > > > > > > > help: > > > > > > > > > > > > > > > > > > > > -------------------------------------------------------------------------- > > > > > > > > > > [root@tpw ~]# ipmitool -I lan -H 192.168.1.211 -U admin -P relation sdr > > > > > > > > > > BB +1.2V Vtt | 1.20 Volts | ok > > > > > > > > > > BB +1.5V AUX | 1.47 Volts | ok > > > > > > > > > > BB +1.5V | 1.48 Volts | ok > > > > > > > > > > BB +1.8V | 1.79 Volts | ok > > > > > > > > > > BB +3.3V | 3.35 Volts | ok > > > > > > > > > > BB +3.3V STB | 3.35 Volts | ok > > > > > > > > > > ^C > > > > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > > > > > > > > > > ipmi_monitoring_sensor_readings_by_record_id: authentication type unavailable for attempted privilege level > > > > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > > > > > > > > > > ipmi_monitoring_sensor_readings_by_record_id: authentication type unavailable for attempted privilege level > > > > > > > > > > [root@tpw ~]# rpm -q freeipmi > > > > > > > > > > freeipmi-0.5.1-3.fc9.i386 > > > > > > > > > > [root@tpw ~]# > > > > > > > > > > -------------------------------------------------------------------------- > > > > > > > > > > > > > > > > > > > > I checked the manpage: > > > > > > > > > > "authentication type unavailable for attempted privilege level" - The authentication type you wish > > > > > > > > > > to authenticate with is not available for this privilege level. Please try again with an alternate > > > > > > > > > > authentication type or alternate privilege level. It may also be possible the available authenti- > > > > > > > > > > cation types you can authenticate with are not correctly configured on the remote BMC. > > > > > > > > > > But the settings at the BMC side seem to be ok: > > > > > > > > > > > > > > > > > > > > -------------------------------------------------------------------------- > > > > > > > > > > [root@tpw ~]# ipmitool -I lan -H 192.168.1.211 -U admin -P relation lan print 1 > > > > > > > > > > Set in Progress : Set Complete > > > > > > > > > > Auth Type Support : NONE MD5 PASSWORD > > > > > > > > > > Auth Type Enable : Callback : > > > > > > > > > > : User : > > > > > > > > > > : Operator : > > > > > > > > > > : Admin : MD5 PASSWORD > > > > > > > > > > : OEM : > > > > > > > > > > IP Address Source : Static Address > > > > > > > > > > IP Address : 192.168.1.211 > > > > > > > > > > Subnet Mask : 255.255.255.0 > > > > > > > > > > MAC Address : 00:0e:0c:ea:92:a2 > > > > > > > > > > [...] > > > > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -a MD5 -u admin -p relation > > > > > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > > > > > [root@tpw ~]# > > > > > > > > > > -------------------------------------------------------------------------- > > > > > > > > > > > > > > > > > > > > Also compiling the newest version and using it does not help: > > > > > > > > > > -------------------------------------------------------------------------- > > > > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > > > > > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > > > > > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > > > > > [root@tpw ~]# rpm -q freeipmi > > > > > > > > > > freeipmi-0.7.11-1.fc9.i386 > > > > > > > > > > [root@tpw ~]# > > > > > > > > > > -------------------------------------------------------------------------- > > > > > > > > > > > > > > > > > > > > In contrast, monitoring a system with a new Supermicro X8DT3-F mainboard > > > > > > > > > > works fine with freeipmi-0.5.1-3.fc9.i386 and also with > > > > > > > > > > freeipmi-0.7.11-1.fc9.i386: > > > > > > > > > > > > > > > > > > > > -------------------------------------------------------------------------- > > > > > > > > > > [root@tpw ~]# ipmitool -I lan -H 10.10.10.233 -U ADMIN -P ADMIN sdr > > > > > > > > > > CPU1 Temp | 0 unspecified | ok > > > > > > > > > > CPU2 Temp | no reading | ns > > > > > > > > > > System Temp | 45 degrees C | ok > > > > > > > > > > CPU1 Vcore | 0.98 Volts | ok > > > > > > > > > > CPU2 Vcore | no reading | ns > > > > > > > > > > CPU1 DIMM | 1.51 Volts | ok > > > > > > > > > > CPU2 DIMM | no reading | ns > > > > > > > > > > ^C > > > > > > > > > > [root@tpw ~]# ipmimonitoring -h 10.10.10.233 -u ADMIN -p ADMIN > > > > > > > > > > Record_ID | Sensor Name | Sensor Group | Monitoring Status| Sensor Units | Sensor Reading > > > > > > > > > > 4 | System Temp | Temperature | Nominal | C | 45.000000 > > > > > > > > > > 5 | CPU1 Vcore | Voltage | Nominal | V | 0.976000 > > > > > > > > > > 6 | CPU2 Vcore | Voltage | Nominal | V | 0.000000 > > > > > > > > > > 7 | CPU1 DIMM | Voltage | Nominal | V | 1.512000 > > > > > > > > > > 8 | CPU2 DIMM | Voltage | Nominal | V | 0.000000 > > > > > > > > > > 9 | +1.5V | Voltage | Nominal | V | 1.504000 > > > > > > > > > > 10 | +3.3V | Voltage | Nominal | V | 3.240000 > > > > > > > > > > 11 | +3.3VSB | Voltage | Nominal | V | 3.240000 > > > > > > > > > > 12 | +5V | Voltage | Nominal | V | 5.120000 > > > > > > > > > > 13 | +12V | Voltage | Nominal | V | 12.190000 > > > > > > > > > > 14 | VBAT | Voltage | Nominal | V | 3.240000 > > > > > > > > > > 15 | Fan1 | Fan | Nominal | RPM | 6528.000000 > > > > > > > > > > 16 | Fan2 | Fan | Nominal | RPM | 7072.000000 > > > > > > > > > > 17 | Fan3 | Fan | Nominal | RPM | 0.000000 > > > > > > > > > > 18 | Fan4 | Fan | Nominal | RPM | 0.000000 > > > > > > > > > > 19 | Fan5 | Fan | Nominal | RPM | 5644.000000 > > > > > > > > > > 20 | Fan6 | Fan | Nominal | RPM | 5304.000000 > > > > > > > > > > 21 | Fan7 | Fan | Nominal | RPM | 7072.000000 > > > > > > > > > > 22 | Fan8 | Fan | Nominal | RPM | 0.000000 > > > > > > > > > > 23 | Intrusion | Physical Security | Nominal | N/A | '' > > > > > > > > > > 24 | PS Failure | Power Supply | Nominal | N/A | '' > > > > > > > > > > [root@tpw ~]# > > > > > > > > > > -------------------------------------------------------------------------- > > > > > > > > > > > > > > > > > > > > Does anybody have an idea how this problem could be fixed? > > > > > > > > > > > > > > > > > > > > best regards, > > > > > > > > > > Werner > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > > > Freeipmi-users mailing list > > > > > > > > > > Freeipmi-users@... > > > > > > > > > > http://*****lists.gnu.org/mailman/listinfo/freeipmi-users > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > Freeipmi-users mailing list > > > > > > > > Freeipmi-users@... > > > > > > > > http://****lists.gnu.org/mailman/listinfo/freeipmi-users > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > Freeipmi-users mailing list > > > > > Freeipmi-users@... > > > > > http://***lists.gnu.org/mailman/listinfo/freeipmi-users > > > > > > > > > > > > > > > > > _______________________________________________ > > > Freeipmi-users mailing list > > > Freeipmi-users@... > > > http://**lists.gnu.org/mailman/listinfo/freeipmi-users > > > > > > > _______________________________________________ > Freeipmi-users mailing list > Freeipmi-users@... > http://*lists.gnu.org/mailman/listinfo/freeipmi-users > Albert Chu chu11@... Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory _______________________________________________ Freeipmi-users mailing list Freeipmi-users@... http://lists.gnu.org/mailman/listinfo/freeipmi-users |
|
|
Re: "authentication type unavailable for attempted privilege level" with Intel S5000PAL Mainboard
by Werner Fischer-2
::
Rate this Message:
Hi Al,
I took a look at the tool once again and the version that I have on CD (D36234-008 - the latest version on the URL below is D36234-010) allows to set IPMI users with "admin" and "user" privilege levels. According to http://download.intel.com/design/servers/ipmi/IPMI2_0E4_Markup_061209.pdf chapter "6.8 Channel Privilege Levels" it really makes sense not to use the "admin" level just for querying sensor states. So for this purposes I'll just configure the level "user" in the future and use "-l USER" for the ipmimonitoring command. I agree with you not to default every FreeIPMI tool and all libraries to the "admin" level. Sure, sometimes it may not work at the first try, but know people can find this discussion in the mailing list archives and then it will work for them, too ;-) And I'll add this information also in the public Wiki system (German) that we have in the company I'm working for: http://www.thomas-krenn.com/de/wiki/Kategorie:Remote-Management Thanks again for great help, Werner On Thu, 2009-09-03 at 09:26 -0700, Al Chu wrote: > Hi Werner, > > Great to hear. > > > I have configured the IPMI settings and IPMI user via the "Intel > > Server Deployment" CD: > > http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&Inst=Yes&ProductID=2451&DwnldID=17974&strOSs=38&OSFullName=OS%20Independent&lang=eng > > Ugh ... that's sort of disappointing. Once in awhile I've thought of > defaulting every FreeIPMI tool and all libraries to have a default > privilege of 'admin', because some vendors just seem to want to have all > their software default to use 'admin' privileges everywhere. > > However, I have restrained myself because having different security > levels/privileges is part of the reason privileges exist in IPMI. > > Sigh ... :P > > Al > > On Thu, 2009-09-03 at 17:45 +0200, Werner Fischer wrote: > > Hi Al, > > > > you are absolutely right! > > > > In this way it works: > > > > [root@tpw ~]# ipmimonitoring -V > > ipmimonitoring - 0.7.12.beta2 > > Copyright (C) 2007-2008 Lawrence Livermore National Security, LLC. > > Copyright (C) 2006-2007 The Regents of the University of California. > > This program is free software; you may redistribute it under the terms of > > the GNU General Public License. This program has absolutely no warranty. > > [root@tpw ~]# > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -l admin -u admin -p relation > > Caching SDR repository information: /root/.freeipmi/sdr-cache/sdr-cache-tpw.192.168.1.211 > > Caching SDR record 143 of 143 (current record ID 143) > > Record_ID | Sensor Name | Sensor Group | Monitoring Status| Sensor Units | Sensor Reading > > 1 | BB +1.2V Vtt | Voltage | Nominal | V | 1.197000 > > 2 | BB +1.5V AUX | Voltage | Nominal | V | 1.466400 > > 3 | BB +1.5V | Voltage | Nominal | V | 1.482000 > > 4 | BB +1.8V | Voltage | Nominal | V | 1.785000 > > 5 | BB +3.3V | Voltage | Nominal | V | 3.354000 > > 6 | BB +3.3V STB | Voltage | Nominal | V | 3.354000 > > 7 | BB +1.5V ESB | Voltage | Nominal | V | 1.505400 > > 8 | BB +5V | Voltage | Nominal | V | 5.070000 > > 9 | BB +12V AUX | Voltage | Nominal | V | 11.904000 > > > > I have configured the IPMI settings and IPMI user via the "Intel Server Deployment" CD: > > http://*downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&Inst=Yes&ProductID=2451&DwnldID=17974&strOSs=38&OSFullName=OS%20Independent&lang=eng > > > > I was not aware of the -l option. > > Sorry for causing the inconvenience. > > > > And thanks a lot again for your help! > > > > Best regards, > > Werner > > > > On Mon, 2009-08-31 at 10:06 -0700, Al Chu wrote: > > > Hey Werner, > > > > > > Actually, your default config may be the issue afterall, not the > > > motherboard. Your default config is not allowing authentication by any > > > privilege level other than "admin". How about trying ipmimonitoring > > > with the -l admin, to tell ipmimonitoring to use the admin privilege > > > level. > > > > > > Out of my curiosity, did the Intel motherboard come like this by > > > default? > > > > > > Al > > > > > > On Mon, 2009-08-31 at 12:18 +0200, Werner Fischer wrote: > > > > Hi Al, > > > > > > > > sorry for my late reply. Now I'm back in the office. You find my results > > > > below: > > > > > > > > On Mon, 2009-08-24 at 10:40 -0700, Al Chu wrote: > > > > > Hi Werner, > > > > > > > > > > Thanks for the feedback. > > > > > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 --debug -u admin -p > > > > > > relation > > > > > > > > > > Could you run --debug with the -W "authcap". I'm wondering if it's > > > > > failing in a different location and the workaround has to be in multiple > > > > > places. > > > > sure, here it is: > > > > > > > > ------------------------------------------------------------------------------------- > > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W "authcap" --debug -u admin -p relation > > > > 192.168.1.211: ===================================================== > > > > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Request > > > > 192.168.1.211: ===================================================== > > > > 192.168.1.211: RMCP Header: > > > > 192.168.1.211: ------------ > > > > 192.168.1.211: [ 6h] = version[ 8b] > > > > 192.168.1.211: [ 0h] = reserved[ 8b] > > > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > > > 192.168.1.211: IPMI Session Header: > > > > 192.168.1.211: -------------------- > > > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > > > 192.168.1.211: [ 0h] = session_id[32b] > > > > 192.168.1.211: [ 9h] = ipmi_msg_len[ 8b] > > > > 192.168.1.211: IPMI Message Header: > > > > 192.168.1.211: -------------------- > > > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > > > 192.168.1.211: [ 6h] = net_fn[ 6b] > > > > 192.168.1.211: [ C8h] = checksum1[ 8b] > > > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > > > 192.168.1.211: [ 33h] = rq_seq[ 6b] > > > > 192.168.1.211: IPMI Command Data: > > > > 192.168.1.211: ------------------ > > > > 192.168.1.211: [ 38h] = cmd[ 8b] > > > > 192.168.1.211: [ Eh] = channel_number[ 4b] > > > > 192.168.1.211: [ 0h] = reserved1[ 4b] > > > > 192.168.1.211: [ 3h] = maximum_privilege_level[ 4b] > > > > 192.168.1.211: [ 0h] = reserved2[ 4b] > > > > 192.168.1.211: IPMI Trailer: > > > > 192.168.1.211: -------------- > > > > 192.168.1.211: [ 6Ah] = checksum2[ 8b] > > > > 192.168.1.211: ===================================================== > > > > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Response > > > > 192.168.1.211: ===================================================== > > > > 192.168.1.211: RMCP Header: > > > > 192.168.1.211: ------------ > > > > 192.168.1.211: [ 6h] = version[ 8b] > > > > 192.168.1.211: [ 0h] = reserved[ 8b] > > > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > > > 192.168.1.211: IPMI Session Header: > > > > 192.168.1.211: -------------------- > > > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > > > 192.168.1.211: [ 0h] = session_id[32b] > > > > 192.168.1.211: [ 10h] = ipmi_msg_len[ 8b] > > > > 192.168.1.211: IPMI Message Header: > > > > 192.168.1.211: -------------------- > > > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > > > 192.168.1.211: [ 7h] = net_fn[ 6b] > > > > 192.168.1.211: [ 63h] = checksum1[ 8b] > > > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > > > 192.168.1.211: [ 33h] = rq_seq[ 6b] > > > > 192.168.1.211: IPMI Command Data: > > > > 192.168.1.211: ------------------ > > > > 192.168.1.211: [ 38h] = cmd[ 8b] > > > > 192.168.1.211: [ 0h] = comp_code[ 8b] > > > > 192.168.1.211: [ 1h] = channel_number[ 8b] > > > > 192.168.1.211: [ 0h] = authentication_type.none[ 1b] > > > > 192.168.1.211: [ 0h] = authentication_type.md2[ 1b] > > > > 192.168.1.211: [ 0h] = authentication_type.md5[ 1b] > > > > 192.168.1.211: [ 0h] = authentication_type.reserved1[ 1b] > > > > 192.168.1.211: [ 0h] = authentication_type.straight_password_key[ 1b] > > > > 192.168.1.211: [ 0h] = authentication_type.oem_prop[ 1b] > > > > 192.168.1.211: [ 0h] = authentication_type.reserved2[ 2b] > > > > 192.168.1.211: [ 0h] = authentication_status.anonymous_login[ 1b] > > > > 192.168.1.211: [ 0h] = authentication_status.null_username[ 1b] > > > > 192.168.1.211: [ 1h] = authentication_status.non_null_username[ 1b] > > > > 192.168.1.211: [ 0h] = authentication_status.user_level_authentication[ 1b] > > > > 192.168.1.211: [ 0h] = authentication_status.per_message_authentication[ 1b] > > > > 192.168.1.211: [ 0h] = authentication_status.reserved[ 3b] > > > > 192.168.1.211: [ 0h] = reserved1[ 8b] > > > > 192.168.1.211: [ 0h] = oem_id[24b] > > > > 192.168.1.211: [ 0h] = oem_auxiliary_data[ 8b] > > > > 192.168.1.211: IPMI Trailer: > > > > 192.168.1.211: -------------- > > > > 192.168.1.211: [ D7h] = checksum2[ 8b] > > > > 192.168.1.211: ===================================================== > > > > 192.168.1.211: IPMI 1.5 Get Session Challenge Request > > > > 192.168.1.211: ===================================================== > > > > 192.168.1.211: RMCP Header: > > > > 192.168.1.211: ------------ > > > > 192.168.1.211: [ 6h] = version[ 8b] > > > > 192.168.1.211: [ 0h] = reserved[ 8b] > > > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > > > 192.168.1.211: IPMI Session Header: > > > > 192.168.1.211: -------------------- > > > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > > > 192.168.1.211: [ 0h] = session_id[32b] > > > > 192.168.1.211: [ 18h] = ipmi_msg_len[ 8b] > > > > 192.168.1.211: IPMI Message Header: > > > > 192.168.1.211: -------------------- > > > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > > > 192.168.1.211: [ 6h] = net_fn[ 6b] > > > > 192.168.1.211: [ C8h] = checksum1[ 8b] > > > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > > > 192.168.1.211: [ 34h] = rq_seq[ 6b] > > > > 192.168.1.211: IPMI Command Data: > > > > 192.168.1.211: ------------------ > > > > 192.168.1.211: [ 39h] = cmd[ 8b] > > > > 192.168.1.211: [ 2h] = authentication_type[ 4b] > > > > 192.168.1.211: [ 0h] = reserved[ 4b] > > > > 192.168.1.211: [ BYTE ARRAY ... ] = user_name[16B] > > > > 192.168.1.211: [ 61h 64h 6Dh 69h 6Eh 00h 00h 00h ] > > > > 192.168.1.211: [ 00h 00h 00h 00h 00h 00h 00h 00h ] > > > > 192.168.1.211: IPMI Trailer: > > > > 192.168.1.211: -------------- > > > > 192.168.1.211: [ 6Bh] = checksum2[ 8b] > > > > 192.168.1.211: ===================================================== > > > > 192.168.1.211: IPMI 1.5 Get Session Challenge Response > > > > 192.168.1.211: ===================================================== > > > > 192.168.1.211: RMCP Header: > > > > 192.168.1.211: ------------ > > > > 192.168.1.211: [ 6h] = version[ 8b] > > > > 192.168.1.211: [ 0h] = reserved[ 8b] > > > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > > > 192.168.1.211: IPMI Session Header: > > > > 192.168.1.211: -------------------- > > > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > > > 192.168.1.211: [ 0h] = session_id[32b] > > > > 192.168.1.211: [ 1Ch] = ipmi_msg_len[ 8b] > > > > 192.168.1.211: IPMI Message Header: > > > > 192.168.1.211: -------------------- > > > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > > > 192.168.1.211: [ 7h] = net_fn[ 6b] > > > > 192.168.1.211: [ 63h] = checksum1[ 8b] > > > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > > > 192.168.1.211: [ 34h] = rq_seq[ 6b] > > > > 192.168.1.211: IPMI Command Data: > > > > 192.168.1.211: ------------------ > > > > 192.168.1.211: [ 39h] = cmd[ 8b] > > > > 192.168.1.211: [ 0h] = comp_code[ 8b] > > > > 192.168.1.211: [ AC03D99h] = temp_session_id[32b] > > > > 192.168.1.211: [ BYTE ARRAY ... ] = challenge_string[16B] > > > > 192.168.1.211: [ 69h F4h 8Ah 89h 60h E4h E2h 1Ch ] > > > > 192.168.1.211: [ 2Ah CCh 96h A0h 6Dh 5Ah CAh 7Ah ] > > > > 192.168.1.211: IPMI Trailer: > > > > 192.168.1.211: -------------- > > > > 192.168.1.211: [ 4Eh] = checksum2[ 8b] > > > > 192.168.1.211: ===================================================== > > > > 192.168.1.211: IPMI 1.5 Activiate Session Request > > > > 192.168.1.211: ===================================================== > > > > 192.168.1.211: RMCP Header: > > > > 192.168.1.211: ------------ > > > > 192.168.1.211: [ 6h] = version[ 8b] > > > > 192.168.1.211: [ 0h] = reserved[ 8b] > > > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > > > 192.168.1.211: IPMI Session Header: > > > > 192.168.1.211: -------------------- > > > > 192.168.1.211: [ 2h] = authentication_type[ 8b] > > > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > > > 192.168.1.211: [ AC03D99h] = session_id[32b] > > > > 192.168.1.211: [ BYTE ARRAY ... ] = authentication_code[16B] > > > > 192.168.1.211: [ 6Bh 25h AAh 78h 0Bh D3h F8h 14h ] > > > > 192.168.1.211: [ C4h 57h 15h 6Eh 15h C3h 15h F6h ] > > > > 192.168.1.211: [ 1Dh] = ipmi_msg_len[ 8b] > > > > 192.168.1.211: IPMI Message Header: > > > > 192.168.1.211: -------------------- > > > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > > > 192.168.1.211: [ 6h] = net_fn[ 6b] > > > > 192.168.1.211: [ C8h] = checksum1[ 8b] > > > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > > > 192.168.1.211: [ 35h] = rq_seq[ 6b] > > > > 192.168.1.211: IPMI Command Data: > > > > 192.168.1.211: ------------------ > > > > 192.168.1.211: [ 3Ah] = cmd[ 8b] > > > > 192.168.1.211: [ 2h] = authentication_type[ 4b] > > > > 192.168.1.211: [ 0h] = reserved1[ 4b] > > > > 192.168.1.211: [ 3h] = maximum_privilege_level[ 4b] > > > > 192.168.1.211: [ 0h] = reserved2[ 4b] > > > > 192.168.1.211: [ BYTE ARRAY ... ] = challenge_string[16B] > > > > 192.168.1.211: [ 69h F4h 8Ah 89h 60h E4h E2h 1Ch ] > > > > 192.168.1.211: [ 2Ah CCh 96h A0h 6Dh 5Ah CAh 7Ah ] > > > > 192.168.1.211: [ 279F274Fh] = initial_outbound_sequence_number[32b] > > > > 192.168.1.211: IPMI Trailer: > > > > 192.168.1.211: -------------- > > > > 192.168.1.211: [ 47h] = checksum2[ 8b] > > > > 192.168.1.211: ===================================================== > > > > 192.168.1.211: IPMI 1.5 Activiate Session Response > > > > 192.168.1.211: ===================================================== > > > > 192.168.1.211: RMCP Header: > > > > 192.168.1.211: ------------ > > > > 192.168.1.211: [ 6h] = version[ 8b] > > > > 192.168.1.211: [ 0h] = reserved[ 8b] > > > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > > > 192.168.1.211: IPMI Session Header: > > > > 192.168.1.211: -------------------- > > > > 192.168.1.211: [ 2h] = authentication_type[ 8b] > > > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > > > 192.168.1.211: [ AC03D99h] = session_id[32b] > > > > 192.168.1.211: [ BYTE ARRAY ... ] = authentication_code[16B] > > > > 192.168.1.211: [ 29h BCh 75h CEh 94h F5h 23h 0Eh ] > > > > 192.168.1.211: [ A9h A9h 97h FFh 58h 22h C4h 89h ] > > > > 192.168.1.211: [ 8h] = ipmi_msg_len[ 8b] > > > > 192.168.1.211: IPMI Message Header: > > > > 192.168.1.211: -------------------- > > > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > > > 192.168.1.211: [ 7h] = net_fn[ 6b] > > > > 192.168.1.211: [ 63h] = checksum1[ 8b] > > > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > > > 192.168.1.211: [ 35h] = rq_seq[ 6b] > > > > 192.168.1.211: IPMI Command Data: > > > > 192.168.1.211: ------------------ > > > > 192.168.1.211: [ 3Ah] = cmd[ 8b] > > > > 192.168.1.211: [ CCh] = comp_code[ 8b] > > > > 192.168.1.211: IPMI Trailer: > > > > 192.168.1.211: -------------- > > > > 192.168.1.211: [ 6h] = checksum2[ 8b] > > > > ipmi_ctx_open_outofband: bad completion code: request data/parameter invalid > > > > [root@tpw ~]# > > > > > > > > ------------------------------------------------------------------------------------- > > > > > > > > > > > > > > A few other random thoughts. > > > > > > > > > > Could you also try different authentication types. Like "-a md2" and > > > > > "-a straight_password_key". > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="authcap" -u admin -p relation > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="authcap" -a md2 -u admin -p relation > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="authcap" -a STRAIGHT_PASSWORD_KEY -u admin -p relation > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > [root@tpw ~]# > > > > > > > > > > > > > > Also, what is the output of "bmc-config --checkout > > > > > --section=lan_conf_auth", just so we can check to make sure the > > > > > configuration looks good. > > > > I ran the command remotely as I have currently no Linux installed on the > > > > box (if it is necessary, just tell me, than I can put a Linux on it and > > > > run bmc-config locally): > > > > > > > > [root@tpw ~]# bmc-config -h 192.168.1.211 -u admin -p relation --checkout --section=lan_conf_auth > > > > # > > > > # Section Lan_Conf_Auth Comments > > > > # > > > > # In the Lan_Conf_Auth section, allowable authentication mechanisms for IPMI 1.5 > > > > # is configured. Most users will want to set all "MD5" authentication to "Yes" > > > > # and the rest to "No". If you have configured a NULL username and a NULL > > > > # password, you will also want to configure some of the "None" fields to "Yes" > > > > # to allow "None" authentication to work. Some motherboards do not allow you to > > > > # enable OEM authentication, so you may wish to set all OEM related fields to > > > > # "No". > > > > # > > > > Section Lan_Conf_Auth > > > > ## Possible values: Yes/No > > > > Callback_Enable_Auth_Type_None No > > > > ## Possible values: Yes/No > > > > Callback_Enable_Auth_Type_MD5 No > > > > ## Possible values: Yes/No > > > > Callback_Enable_Auth_Type_Straight_Password No > > > > ## Possible values: Yes/No > > > > User_Enable_Auth_Type_None No > > > > ## Possible values: Yes/No > > > > User_Enable_Auth_Type_MD5 No > > > > ## Possible values: Yes/No > > > > User_Enable_Auth_Type_Straight_Password No > > > > ## Possible values: Yes/No > > > > Operator_Enable_Auth_Type_None No > > > > ## Possible values: Yes/No > > > > Operator_Enable_Auth_Type_MD5 No > > > > ## Possible values: Yes/No > > > > Operator_Enable_Auth_Type_Straight_Password No > > > > ## Possible values: Yes/No > > > > Admin_Enable_Auth_Type_None No > > > > ## Possible values: Yes/No > > > > Admin_Enable_Auth_Type_MD5 Yes > > > > ## Possible values: Yes/No > > > > Admin_Enable_Auth_Type_Straight_Password Yes > > > > ## Possible values: Yes/No > > > > OEM_Enable_Auth_Type_None No > > > > ## Possible values: Yes/No > > > > OEM_Enable_Auth_Type_MD5 No > > > > ## Possible values: Yes/No > > > > OEM_Enable_Auth_Type_Straight_Password No > > > > EndSection > > > > [root@tpw ~]# > > > > > > > > If you need any further results, just let me know! > > > > > > > > Thanks for your support, > > > > Werner > > > > > > > > > > > > > > Thanks, > > > > > > > > > > Al > > > > > > > > > > On Mon, 2009-08-24 at 15:31 +0200, Werner Fischer wrote: > > > > > > Hi Al, > > > > > > > > > > > > thanks for the updated tar.gz. I tried it, but somehow it still seems to > > > > > > cause problems (see below). I'll be two days out of office - so I can do > > > > > > further tests on Thursday. > > > > > > > > > > > > thanks for your support! > > > > > > > > > > > > [root@tpw ~]# rpm -q freeipmi > > > > > > freeipmi-0.7.12.beta2-1.fc9.i386 > > > > > > [root@tpw ~]# ipmimonitoring -V > > > > > > ipmimonitoring - 0.7.12.beta2 > > > > > > Copyright (C) 2007-2008 Lawrence Livermore National Security, LLC. > > > > > > Copyright (C) 2006-2007 The Regents of the University of California. > > > > > > This program is free software; you may redistribute it under the terms of > > > > > > the GNU General Public License. This program has absolutely no warranty. > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="authcap" -u admin -p relation > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 --debug -u admin -p relation > > > > > > 192.168.1.211: ===================================================== > > > > > > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Request > > > > > > 192.168.1.211: ===================================================== > > > > > > 192.168.1.211: RMCP Header: > > > > > > 192.168.1.211: ------------ > > > > > > 192.168.1.211: [ 6h] = version[ 8b] > > > > > > 192.168.1.211: [ 0h] = reserved[ 8b] > > > > > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > > > > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > > > > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > > > > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > > > > > 192.168.1.211: IPMI Session Header: > > > > > > 192.168.1.211: -------------------- > > > > > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > > > > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > > > > > 192.168.1.211: [ 0h] = session_id[32b] > > > > > > 192.168.1.211: [ 9h] = ipmi_msg_len[ 8b] > > > > > > 192.168.1.211: IPMI Message Header: > > > > > > 192.168.1.211: -------------------- > > > > > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > > > > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > > > > > 192.168.1.211: [ 6h] = net_fn[ 6b] > > > > > > 192.168.1.211: [ C8h] = checksum1[ 8b] > > > > > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > > > > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > > > > > 192.168.1.211: [ 13h] = rq_seq[ 6b] > > > > > > 192.168.1.211: IPMI Command Data: > > > > > > 192.168.1.211: ------------------ > > > > > > 192.168.1.211: [ 38h] = cmd[ 8b] > > > > > > 192.168.1.211: [ Eh] = channel_number[ 4b] > > > > > > 192.168.1.211: [ 0h] = reserved1[ 4b] > > > > > > 192.168.1.211: [ 3h] = maximum_privilege_level[ 4b] > > > > > > 192.168.1.211: [ 0h] = reserved2[ 4b] > > > > > > 192.168.1.211: IPMI Trailer: > > > > > > 192.168.1.211: -------------- > > > > > > 192.168.1.211: [ EAh] = checksum2[ 8b] > > > > > > 192.168.1.211: ===================================================== > > > > > > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Response > > > > > > 192.168.1.211: ===================================================== > > > > > > 192.168.1.211: RMCP Header: > > > > > > 192.168.1.211: ------------ > > > > > > 192.168.1.211: [ 6h] = version[ 8b] > > > > > > 192.168.1.211: [ 0h] = reserved[ 8b] > > > > > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > > > > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > > > > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > > > > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > > > > > 192.168.1.211: IPMI Session Header: > > > > > > 192.168.1.211: -------------------- > > > > > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > > > > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > > > > > 192.168.1.211: [ 0h] = session_id[32b] > > > > > > 192.168.1.211: [ 10h] = ipmi_msg_len[ 8b] > > > > > > 192.168.1.211: IPMI Message Header: > > > > > > 192.168.1.211: -------------------- > > > > > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > > > > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > > > > > 192.168.1.211: [ 7h] = net_fn[ 6b] > > > > > > 192.168.1.211: [ 63h] = checksum1[ 8b] > > > > > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > > > > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > > > > > 192.168.1.211: [ 13h] = rq_seq[ 6b] > > > > > > 192.168.1.211: IPMI Command Data: > > > > > > 192.168.1.211: ------------------ > > > > > > 192.168.1.211: [ 38h] = cmd[ 8b] > > > > > > 192.168.1.211: [ 0h] = comp_code[ 8b] > > > > > > 192.168.1.211: [ 1h] = channel_number[ 8b] > > > > > > 192.168.1.211: [ 0h] = authentication_type.none[ 1b] > > > > > > 192.168.1.211: [ 0h] = authentication_type.md2[ 1b] > > > > > > 192.168.1.211: [ 0h] = authentication_type.md5[ 1b] > > > > > > 192.168.1.211: [ 0h] = authentication_type.reserved1[ 1b] > > > > > > 192.168.1.211: [ 0h] = authentication_type.straight_password_key[ 1b] > > > > > > 192.168.1.211: [ 0h] = authentication_type.oem_prop[ 1b] > > > > > > 192.168.1.211: [ 0h] = authentication_type.reserved2[ 2b] > > > > > > 192.168.1.211: [ 0h] = authentication_status.anonymous_login[ 1b] > > > > > > 192.168.1.211: [ 0h] = authentication_status.null_username[ 1b] > > > > > > 192.168.1.211: [ 1h] = authentication_status.non_null_username[ 1b] > > > > > > 192.168.1.211: [ 0h] = authentication_status.user_level_authentication[ 1b] > > > > > > 192.168.1.211: [ 0h] = authentication_status.per_message_authentication[ 1b] > > > > > > 192.168.1.211: [ 0h] = authentication_status.reserved[ 3b] > > > > > > 192.168.1.211: [ 0h] = reserved1[ 8b] > > > > > > 192.168.1.211: [ 0h] = oem_id[24b] > > > > > > 192.168.1.211: [ 0h] = oem_auxiliary_data[ 8b] > > > > > > 192.168.1.211: IPMI Trailer: > > > > > > 192.168.1.211: -------------- > > > > > > 192.168.1.211: [ 57h] = checksum2[ 8b] > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > [root@tpw ~]# > > > > > > > > > > > > > > > > > > On Fri, 2009-08-21 at 14:03 -0700, Al Chu wrote: > > > > > > > Hi Werner, > > > > > > > > > > > > > > I've got a test tar.gz here: > > > > > > > > > > > > > > http://***ftp.gluster.com/pub/freeipmi/qa-release/freeipmi-0.7.12.beta2.tar.gz > > > > > > > > > > > > > > This makes it so the 'authcap' workaround should work for you. Can you > > > > > > > give it a shot to make sure it works? > > > > > > > > > > > > > > Thanks, > > > > > > > Al > > > > > > > > > > > > > > On Fri, 2009-08-21 at 08:44 -0700, Al Chu wrote: > > > > > > > > Hi Werner, > > > > > > > > > > > > > > > > > 192.168.1.211: [ 0h] = authentication_type.none[ 1b] > > > > > > > > > 192.168.1.211: [ 0h] = authentication_type.md2[ 1b] > > > > > > > > > 192.168.1.211: [ 0h] = authentication_type.md5[ 1b] > > > > > > > > > 192.168.1.211: [ 0h] = authentication_type.reserved1[ 1b] > > > > > > > > > 192.168.1.211: [ 0h] = authentication_type.straight_password_key[ 1b] > > > > > > > > > 192.168.1.211: [ 0h] = authentication_type.oem_prop[ 1b] > > > > > > > > > > > > > > > > This indicates that no authentication support is enabled, which is very > > > > > > > > unlikely of being true (which we could verify via 'bmc-config --checkout > > > > > > > > --section=lan_conf_auth'). > > > > > > > > > > > > > > > > I'll modify the 'authcap' workaround to also encompass this case and > > > > > > > > post a beta tar.gz for you to check out. > > > > > > > > > > > > > > > > Al > > > > > > > > > > > > > > > > On Fri, 2009-08-21 at 09:58 +0200, Werner Fischer wrote: > > > > > > > > > Hi Al, > > > > > > > > > > > > > > > > > > thanks for your fast answer. > > > > > > > > > > > > > > > > > > Below you find the requested debug output. I'm using version 0.7.11. The > > > > > > > > > "authcap" workaround does not fix the problem. After executing with > > > > > > > > > debug to the affected Intel S5000PAL system (IP 192.168.1.211) I again > > > > > > > > > verified the correct behavior of ipmimonitoring to the other system > > > > > > > > > (Supermicro) to IP 10.10.10.233. > > > > > > > > > > > > > > > > > > [root@tpw ~]# rpm -q freeipmi > > > > > > > > > freeipmi-0.7.11-1.fc9.i386 > > > > > > > > > [root@tpw ~]# ipmimonitoring -V > > > > > > > > > ipmimonitoring - 0.7.11 > > > > > > > > > Copyright (C) 2007-2008 Lawrence Livermore National Security, LLC. > > > > > > > > > Copyright (C) 2006-2007 The Regents of the University of California. > > > > > > > > > This program is free software; you may redistribute it under the terms of > > > > > > > > > the GNU General Public License. This program has absolutely no warranty. > > > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > > > > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > > > > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="authcap" -u admin -p relation > > > > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 --debug -u admin -p relation > > > > > > > > > 192.168.1.211: ===================================================== > > > > > > > > > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Request > > > > > > > > > 192.168.1.211: ===================================================== > > > > > > > > > 192.168.1.211: RMCP Header: > > > > > > > > > 192.168.1.211: ------------ > > > > > > > > > 192.168.1.211: [ 6h] = version[ 8b] > > > > > > > > > 192.168.1.211: [ 0h] = reserved[ 8b] > > > > > > > > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > > > > > > > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > > > > > > > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > > > > > > > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > > > > > > > > 192.168.1.211: IPMI Session Header: > > > > > > > > > 192.168.1.211: -------------------- > > > > > > > > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > > > > > > > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > > > > > > > > 192.168.1.211: [ 0h] = session_id[32b] > > > > > > > > > 192.168.1.211: [ 9h] = ipmi_msg_len[ 8b] > > > > > > > > > 192.168.1.211: IPMI Message Header: > > > > > > > > > 192.168.1.211: -------------------- > > > > > > > > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > > > > > > > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > > > > > > > > 192.168.1.211: [ 6h] = net_fn[ 6b] > > > > > > > > > 192.168.1.211: [ C8h] = checksum1[ 8b] > > > > > > > > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > > > > > > > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > > > > > > > > 192.168.1.211: [ 8h] = rq_seq[ 6b] > > > > > > > > > 192.168.1.211: IPMI Command Data: > > > > > > > > > 192.168.1.211: ------------------ > > > > > > > > > 192.168.1.211: [ 38h] = cmd[ 8b] > > > > > > > > > 192.168.1.211: [ Eh] = channel_number[ 4b] > > > > > > > > > 192.168.1.211: [ 0h] = reserved1[ 4b] > > > > > > > > > 192.168.1.211: [ 3h] = maximum_privilege_level[ 4b] > > > > > > > > > 192.168.1.211: [ 0h] = reserved2[ 4b] > > > > > > > > > 192.168.1.211: IPMI Trailer: > > > > > > > > > 192.168.1.211: -------------- > > > > > > > > > 192.168.1.211: [ 16h] = checksum2[ 8b] > > > > > > > > > 192.168.1.211: ===================================================== > > > > > > > > > 192.168.1.211: IPMI 1.5 Get Channel Authentication Capabilities Response > > > > > > > > > 192.168.1.211: ===================================================== > > > > > > > > > 192.168.1.211: RMCP Header: > > > > > > > > > 192.168.1.211: ------------ > > > > > > > > > 192.168.1.211: [ 6h] = version[ 8b] > > > > > > > > > 192.168.1.211: [ 0h] = reserved[ 8b] > > > > > > > > > 192.168.1.211: [ FFh] = sequence_number[ 8b] > > > > > > > > > 192.168.1.211: [ 7h] = message_class.class[ 5b] > > > > > > > > > 192.168.1.211: [ 0h] = message_class.reserved[ 2b] > > > > > > > > > 192.168.1.211: [ 0h] = message_class.ack[ 1b] > > > > > > > > > 192.168.1.211: IPMI Session Header: > > > > > > > > > 192.168.1.211: -------------------- > > > > > > > > > 192.168.1.211: [ 0h] = authentication_type[ 8b] > > > > > > > > > 192.168.1.211: [ 0h] = session_sequence_number[32b] > > > > > > > > > 192.168.1.211: [ 0h] = session_id[32b] > > > > > > > > > 192.168.1.211: [ 10h] = ipmi_msg_len[ 8b] > > > > > > > > > 192.168.1.211: IPMI Message Header: > > > > > > > > > 192.168.1.211: -------------------- > > > > > > > > > 192.168.1.211: [ 81h] = rq_addr[ 8b] > > > > > > > > > 192.168.1.211: [ 0h] = rq_lun[ 2b] > > > > > > > > > 192.168.1.211: [ 7h] = net_fn[ 6b] > > > > > > > > > 192.168.1.211: [ 63h] = checksum1[ 8b] > > > > > > > > > 192.168.1.211: [ 20h] = rs_addr[ 8b] > > > > > > > > > 192.168.1.211: [ 0h] = rs_lun[ 2b] > > > > > > > > > 192.168.1.211: [ 8h] = rq_seq[ 6b] > > > > > > > > > 192.168.1.211: IPMI Command Data: > > > > > > > > > 192.168.1.211: ------------------ > > > > > > > > > 192.168.1.211: [ 38h] = cmd[ 8b] > > > > > > > > > 192.168.1.211: [ 0h] = comp_code[ 8b] > > > > > > > > > 192.168.1.211: [ 1h] = channel_number[ 8b] > > > > > > > > > 192.168.1.211: [ 0h] = authentication_type.none[ 1b] > > > > > > > > > 192.168.1.211: [ 0h] = authentication_type.md2[ 1b] > > > > > > > > > 192.168.1.211: [ 0h] = authentication_type.md5[ 1b] > > > > > > > > > 192.168.1.211: [ 0h] = authentication_type.reserved1[ 1b] > > > > > > > > > 192.168.1.211: [ 0h] = authentication_type.straight_password_key[ 1b] > > > > > > > > > 192.168.1.211: [ 0h] = authentication_type.oem_prop[ 1b] > > > > > > > > > 192.168.1.211: [ 0h] = authentication_type.reserved2[ 2b] > > > > > > > > > 192.168.1.211: [ 0h] = authentication_status.anonymous_login[ 1b] > > > > > > > > > 192.168.1.211: [ 0h] = authentication_status.null_username[ 1b] > > > > > > > > > 192.168.1.211: [ 1h] = authentication_status.non_null_username[ 1b] > > > > > > > > > 192.168.1.211: [ 0h] = authentication_status.user_level_authentication[ 1b] > > > > > > > > > 192.168.1.211: [ 0h] = authentication_status.per_message_authentication[ 1b] > > > > > > > > > 192.168.1.211: [ 0h] = authentication_status.reserved[ 3b] > > > > > > > > > 192.168.1.211: [ 0h] = reserved1[ 8b] > > > > > > > > > 192.168.1.211: [ 0h] = oem_id[24b] > > > > > > > > > 192.168.1.211: [ 0h] = oem_auxiliary_data[ 8b] > > > > > > > > > 192.168.1.211: IPMI Trailer: > > > > > > > > > 192.168.1.211: -------------- > > > > > > > > > 192.168.1.211: [ 83h] = checksum2[ 8b] > > > > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > > > > [root@tpw ~]# > > > > > > > > > [root@tpw ~]# > > > > > > > > > [root@tpw ~]# > > > > > > > > > [root@tpw ~]# ipmimonitoring -h 10.10.10.233 -u ADMIN -p ADMIN > > > > > > > > > Record_ID | Sensor Name | Sensor Group | Monitoring Status| Sensor Units | Sensor Reading > > > > > > > > > 4 | System Temp | Temperature | Nominal | C | 41.000000 > > > > > > > > > 5 | CPU1 Vcore | Voltage | Nominal | V | 0.976000 > > > > > > > > > 7 | CPU1 DIMM | Voltage | Nominal | V | 1.512000 > > > > > > > > > 9 | +1.5V | Voltage | Nominal | V | 1.504000 > > > > > > > > > 10 | +3.3V | Voltage | Nominal | V | 3.240000 > > > > > > > > > 11 | +3.3VSB | Voltage | Nominal | V | 3.240000 > > > > > > > > > 12 | +5V | Voltage | Nominal | V | 5.120000 > > > > > > > > > 13 | +12V | Voltage | Nominal | V | 12.190000 > > > > > > > > > 14 | VBAT | Voltage | Nominal | V | 3.216000 > > > > > > > > > 15 | Fan1 | Fan | Nominal | RPM | 3264.000000 > > > > > > > > > 16 | Fan2 | Fan | Nominal | RPM | 3536.000000 > > > > > > > > > 19 | Fan5 | Fan | Nominal | RPM | 2788.000000 > > > > > > > > > 20 | Fan6 | Fan | Nominal | RPM | 2652.000000 > > > > > > > > > 21 | Fan7 | Fan | Nominal | RPM | 3536.000000 > > > > > > > > > 23 | Intrusion | Physical Security | Nominal | N/A | 'OK' > > > > > > > > > 24 | PS Failure | Power Supply | Nominal | N/A | 'OK' > > > > > > > > > [root@tpw ~]# > > > > > > > > > > > > > > > > > > Werner > > > > > > > > > > > > > > > > > > On Wed, 2009-08-19 at 08:58 -0700, Al Chu wrote: > > > > > > > > > > Hi Werner, > > > > > > > > > > > > > > > > > > > > It's possible the motherboard is not reporting supported authentication > > > > > > > > > > types correctly. You could give the "authcap" workaround a shot. > > > > > > > > > > However, if this is being non-compliant in the way that I think it is, > > > > > > > > > > the "authcap" workaround won't work (b/c it currently handles a > > > > > > > > > > different non-compliance bug). Could you send me the output from > > > > > > > > > > --debug? If we can verify the issue, I'll implement a new workaround > > > > > > > > > > for you. > > > > > > > > > > > > > > > > > > > > BTW, if you need the intel20 workarounds for IPMI 2.0, you may need to > > > > > > > > > > upgrade. There were some bugs found a few releases ago. > > > > > > > > > > > > > > > > > > > > 0.7.4 - 12/15/08 > > > > > > > > > > ---------------- > > > > > > > > > > <snip> > > > > > > > > > > o Fix Intel IPMI 2.0 workarounds in all tools/libraries. > > > > > > > > > > <snip> > > > > > > > > > > > > > > > > > > > > Al > > > > > > > > > > > > > > > > > > > > On Wed, 2009-08-19 at 14:16 +0200, Werner Fischer wrote: > > > > > > > > > > > Dear freeipmi users/developers, > > > > > > > > > > > > > > > > > > > > > > I'm trying to monitor an Intel SR2500 server (this server has the Intel > > > > > > > > > > > S5000PAL mainboard in it). > > > > > > > > > > > > > > > > > > > > > > While I can monitor it using ipmitool, I keep getting errors with > > > > > > > > > > > ipmimonitoring from freeipmi. Also using the "-W" parameter for > > > > > > > > > > > workarounds (as described in the manpage of ipmimonitoring) doesn't > > > > > > > > > > > help: > > > > > > > > > > > > > > > > > > > > > > -------------------------------------------------------------------------- > > > > > > > > > > > [root@tpw ~]# ipmitool -I lan -H 192.168.1.211 -U admin -P relation sdr > > > > > > > > > > > BB +1.2V Vtt | 1.20 Volts | ok > > > > > > > > > > > BB +1.5V AUX | 1.47 Volts | ok > > > > > > > > > > > BB +1.5V | 1.48 Volts | ok > > > > > > > > > > > BB +1.8V | 1.79 Volts | ok > > > > > > > > > > > BB +3.3V | 3.35 Volts | ok > > > > > > > > > > > BB +3.3V STB | 3.35 Volts | ok > > > > > > > > > > > ^C > > > > > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > > > > > > > > > > > ipmi_monitoring_sensor_readings_by_record_id: authentication type unavailable for attempted privilege level > > > > > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > > > > > > > > > > > ipmi_monitoring_sensor_readings_by_record_id: authentication type unavailable for attempted privilege level > > > > > > > > > > > [root@tpw ~]# rpm -q freeipmi > > > > > > > > > > > freeipmi-0.5.1-3.fc9.i386 > > > > > > > > > > > [root@tpw ~]# > > > > > > > > > > > -------------------------------------------------------------------------- > > > > > > > > > > > > > > > > > > > > > > I checked the manpage: > > > > > > > > > > > "authentication type unavailable for attempted privilege level" - The authentication type you wish > > > > > > > > > > > to authenticate with is not available for this privilege level. Please try again with an alternate > > > > > > > > > > > authentication type or alternate privilege level. It may also be possible the available authenti- > > > > > > > > > > > cation types you can authenticate with are not correctly configured on the remote BMC. > > > > > > > > > > > But the settings at the BMC side seem to be ok: > > > > > > > > > > > > > > > > > > > > > > -------------------------------------------------------------------------- > > > > > > > > > > > [root@tpw ~]# ipmitool -I lan -H 192.168.1.211 -U admin -P relation lan print 1 > > > > > > > > > > > Set in Progress : Set Complete > > > > > > > > > > > Auth Type Support : NONE MD5 PASSWORD > > > > > > > > > > > Auth Type Enable : Callback : > > > > > > > > > > > : User : > > > > > > > > > > > : Operator : > > > > > > > > > > > : Admin : MD5 PASSWORD > > > > > > > > > > > : OEM : > > > > > > > > > > > IP Address Source : Static Address > > > > > > > > > > > IP Address : 192.168.1.211 > > > > > > > > > > > Subnet Mask : 255.255.255.0 > > > > > > > > > > > MAC Address : 00:0e:0c:ea:92:a2 > > > > > > > > > > > [...] > > > > > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -a MD5 -u admin -p relation > > > > > > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > > > > > > [root@tpw ~]# > > > > > > > > > > > -------------------------------------------------------------------------- > > > > > > > > > > > > > > > > > > > > > > Also compiling the newest version and using it does not help: > > > > > > > > > > > -------------------------------------------------------------------------- > > > > > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -u admin -p relation > > > > > > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > > > > > > [root@tpw ~]# ipmimonitoring -h 192.168.1.211 -W="intel20" -u admin -p relation > > > > > > > > > > > ipmimonitoring: authentication type unavailable for attempted privilege level > > > > > > > > > > > [root@tpw ~]# rpm -q freeipmi > > > > > > > > > > > freeipmi-0.7.11-1.fc9.i386 > > > > > > > > > > > [root@tpw ~]# > > > > > > > > > > > -------------------------------------------------------------------------- > > > > > > > > > > > > > > > > > > > > > > In contrast, monitoring a system with a new Supermicro X8DT3-F mainboard > > > > > > > > > > > works fine with freeipmi-0.5.1-3.fc9.i386 and also with > > > > > > > > > > > freeipmi-0.7.11-1.fc9.i386: > > > > > > > > > > > > > > > > > > > > > > -------------------------------------------------------------------------- > > > > > > > > > > > [root@tpw ~]# ipmitool -I lan -H 10.10.10.233 -U ADMIN -P ADMIN sdr > > > > > > > > > > > CPU1 Temp | 0 unspecified | ok > > > > > > > > > > > CPU2 Temp | no reading | ns > > > > > > > > > > > System Temp | 45 degrees C | ok > > > > > > > > > > > CPU1 Vcore | 0.98 Volts | ok > > > > > > > > > > > CPU2 Vcore | no reading | ns > > > > > > > > > > > CPU1 DIMM | 1.51 Volts | ok > > > > > > > > > > > CPU2 DIMM | no reading | ns > > > > > > > > > > > ^C > > > > > > > > > > > [root@tpw ~]# ipmimonitoring -h 10.10.10.233 -u ADMIN -p ADMIN > > > > > > > > > > > Record_ID | Sensor Name | Sensor Group | Monitoring Status| Sensor Units | Sensor Reading > > > > > > > > > > > 4 | System Temp | Temperature | Nominal | C | 45.000000 > > > > > > > > > > > 5 | CPU1 Vcore | Voltage | Nominal | V | 0.976000 > > > > > > > > > > > 6 | CPU2 Vcore | Voltage | Nominal | V | 0.000000 > > > > > > > > > > > 7 | CPU1 DIMM | Voltage | Nominal | V | 1.512000 > > > > > > > > > > > 8 | CPU2 DIMM | Voltage | Nominal | V | 0.000000 > > > > > > > > > > > 9 | +1.5V | Voltage | Nominal | V | 1.504000 > > > > > > > > > > > 10 | +3.3V | Voltage | Nominal | V | 3.240000 > > > > > > > > > > > 11 | +3.3VSB | Voltage | Nominal | V | 3.240000 > > > > > > > > > > > 12 | +5V | Voltage | Nominal | V | 5.120000 > > > > > > > > > > > 13 | +12V | Voltage | Nominal | V | 12.190000 > > > > > > > > > > > 14 | VBAT | Voltage | Nominal | V | 3.240000 > > > > > > > > > > > 15 | Fan1 | Fan | Nominal | RPM | 6528.000000 > > > > > > > > > > > 16 | Fan2 | Fan | Nominal | RPM | 7072.000000 > > > > > > > > > > > 17 | Fan3 | Fan | Nominal | RPM | 0.000000 > > > > > > > > > > > 18 | Fan4 | Fan | Nominal | RPM | 0.000000 > > > > > > > > > > > 19 | Fan5 | Fan | Nominal | RPM | 5644.000000 > > > > > > > > > > > 20 | Fan6 | Fan | Nominal | RPM | 5304.000000 > > > > > > > > > > > 21 | Fan7 | Fan | Nominal | RPM | 7072.000000 > > > > > > > > > > > 22 | Fan8 | Fan | Nominal | RPM | 0.000000 > > > > > > > > > > > 23 | Intrusion | Physical Security | Nominal | N/A | '' > > > > > > > > > > > 24 | PS Failure | Power Supply | Nominal | N/A | '' > > > > > > > > > > > [root@tpw ~]# > > > > > > > > > > > -------------------------------------------------------------------------- > > > > > > > > > > > > > > > > > > > > > > Does anybody have an idea how this problem could be fixed? > > > > > > > > > > > > > > > > > > > > > > best regards, > > > > > > > > > > > Werner > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > > > > Freeipmi-users mailing list > > > > > > > > > > > Freeipmi-users@... > > > > > > > > > > > http://*****lists.gnu.org/mailman/listinfo/freeipmi-users > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > > Freeipmi-users mailing list > > > > > > > > > Freeipmi-users@... > > > > > > > > > http://****lists.gnu.org/mailman/listinfo/freeipmi-users > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > Freeipmi-users mailing list > > > > > > Freeipmi-users@... > > > > > > http://***lists.gnu.org/mailman/listinfo/freeipmi-users > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > Freeipmi-users mailing list > > > > Freeipmi-users@... > > > > http://**lists.gnu.org/mailman/listinfo/freeipmi-users > > > > > > > > > > > > _______________________________________________ > > Freeipmi-users mailing list > > Freeipmi-users@... > > http://*lists.gnu.org/mailman/listinfo/freeipmi-users > > _______________________________________________ Freeipmi-users mailing list Freeipmi-users@... http://lists.gnu.org/mailman/listinfo/freeipmi-users |
| Free embeddable forum powered by Nabble | Forum Help |
