> Thanks a bunch Al. I really appreciate your response. You're welcome. Is it possible the firmware on the two boards is different?
I have this funny recollection that some boards would support ipmi 2.0 but not ipmi 1.5 and it ended up being a bug in the firmware. Al On Tue, 2017-01-24 at 08:50 -0800, Yu Lok Lam wrote: > Hi Al, > > See reply below: > > On 1/23/17 4:31 PM, Albert Chu wrote: > > The fact IPMI 2.0 (i.e. lanplus) works but not IPMI 1.5 works is > > curious. Is the output from: > > > > bmc-config --checkout -vv > > > > identical on both .23 and .24? > Yes, "bmc-config" for both are identical. > > > > > > > Have you tried "-D lan_2_0" with ipmi-sensors to try and force ipmi 2.0 > > on .24? > The "-D lan_2_0" option works! > > [root@XXXXXmon ~]# /usr/sbin/ipmi-sensors -h 192.168.160.24 -u XXXXX -p > XXXXX -l user -D lan_2_0 > ID | Name | Type | Reading | Units | Event > 4 | CPU1 Temp | Temperature | 27.00 | C | 'OK' > 71 | CPU2 Temp | Temperature | 30.00 | C | 'OK' > 138 | System Temp | Temperature | 26.00 | C | 'OK' > 205 | Peripheral Temp | Temperature | 38.00 | C | 'OK' > > Hmmm???? It still doesn't explain why one would need to force option > lan2.0 when the > bmc configs are identical. The original intent was to get the Nagios > Perl plugin "check_ipmi_sensor", > a wrapper for ipmi-sensors to work. Good news! I was able to get it to > work. > > [root@XXXXXmon ~]# /usr/lib64/nagios/plugins/check_ipmi_sensor -H > 192.168.160.24 -U XXXXX -P XXXXX -L user -O "-D lan_2_0" > IPMI Status: OK | 'CPU1 Temp'=27.00 'CPU2 Temp'=28.00 'System > Temp'=27.00 'Peripheral Temp'=38.00 'PCH Temp'=49.00 '10G Temp'=45.00 > 'P1-DIMMA1 TEMP'=28.00 'P1-DIMMB1 TEMP'=28.00 'P1-DIMMC1 TEMP'=38.00 > 'P1-DIMMD1 TEMP'=30.00 'P2-DIMME1 TEMP'=35.00 'P2-DIMMF1 TEMP'=34.00 > 'P2-DIMMG1 TEMP'=32.00 'P2-DIMMH1 TEMP'=33.00 'FAN1'=3075.00 > 'FAN2'=2925.00 'FAN3'=2925.00 'FAN5'=3075.00 'VTT'=0.99 'CPU1 > Vcore'=0.70 'CPU2 Vcore'=0.75 'VDIMM AB'=1.47 'VDIMM CD'=1.49 'VDIMM > EF'=1.50 'VDIMM GH'=1.49 '3.3V'=3.26 '+3.3VSB'=3.31 '5V'=4.93 > '+5VSB'=4.93 '12V'=12.19 'VBAT'=3.07 > > Thanks a bunch Al. I really appreciate your response. > > -Yulok Lam > > > > Al > > > > On Mon, 2017-01-23 at 16:16 -0800, Yulok Lam wrote: > >> Hi Albert, > >> > >> No, it does not. However, on a different system .23, it works. I > >> have double check the password on both systems and they are good. > >> See results for the .23 and .24 systems. > >> > >> [root@XXXXmon ~]# /usr/sbin/ipmi-sensors -h 192.168.160.24 -u XXXXX -p > >> XXXXX -l user > >> > >> /usr/sbin/ipmi-sensors: password verification timeout > >> > >> [root@XXXXmon ~]# > >> > >> =========================== > >> > >> [root@XXXXmon ~]# /usr/sbin/ipmi-sensors -h 192.168.160.23 -u XXXXX -p > >> XXXXX -l user > >> > >> ID | Name | Type | Reading | Units | > >> Event > >> > >> 4 | CPU1 Temp | Temperature | 28.00 | C | 'OK' > >> > >> 71 | CPU2 Temp | Temperature | 27.00 | C | 'OK' > >> > >> 138 | System Temp | Temperature | 29.00 | C | 'OK' > >> > >> ================================================= > >> > >> > >> I have one system where I need to use the "-I lanplus" option while > >> the other, I did not. Both systems are Supermicro X9DRW-7TPF+ and > >> running the same ipmitool 2.0/firmware 3.31. > >> > >> > >> [root@xyz ]# ipmitool -H 192.168.160.24 -U xxxxx -P xxxxx power status > >> Activate Session error: Invalid data field in request > >> Error: Unable to establish LAN session > >> Unable to get Chassis Power Status > >> > >> > >> [root@xyz ]# ipmitool -I lan -H 192.168.160.24 -U xxxx -P xxxxx power > >> status > >> Activate Session error: Invalid data field in request > >> Error: Unable to establish LAN session > >> Unable to get Chassis Power Status > >> > >> > >> [root@xyz ]# ipmitool -I lanplus -H 192.168.160.24 -U xxxxx -P xxxxx > >> power status > >> Chassis Power is on > >> [root@xyzx]# > >> > >> > >> =============== > >> [root@xxxxxx ~]# ipmitool mc info > >> Device ID : 32 > >> Device Revision : 1 > >> Firmware Revision : 3.31 > >> IPMI Version : 2.0 > >> Manufacturer ID : 10876 > >> Manufacturer Name : Supermicro > >> Product ID : 1824 (0x0720) > >> Product Name : Unknown (0x720) > >> Device Available : yes > >> Provides Device SDRs : no > >> Additional Device Support : > >> Sensor Device > >> SDR Repository Device > >> SEL Device > >> FRU Inventory Device > >> IPMB Event Receiver > >> IPMB Event Generator > >> Chassis Device > >> [root@xxxxxxxx ~]# > >> > >> > >> ================= > >> > >> > >> Success "without -I lanplus" on the .23 (different) server. > >> > >> > >> [root@xxxx ]# ipmitool -H 192.168.160.23 -U xxxxx -P xxx power status > >> Chassis Power is on > >> [root@xxx ]# > >> > >> > >> I am thinking there must be an option in ipmitool option that I am > >> forgetting. > >> > >> -Yulok Lam > >> > >> > >> > >> On Mon, Jan 23, 2017 at 3:59 PM, Albert Chu <ch...@llnl.gov> wrote: > >> Usually this means that the password you have doesn't work. > >> When you > >> do: > >> > >> /usr/sbin/ipmi-sensors -h 192.168.160.24 -u xxxxx -p xxxxx -l > >> user > >> --quiet-cache --sdr-cache-recreate --interpret-oem-data > >> --output-sensor-state --ignore-not-available-sensors > >> > >> On the command line, does it work? Or even something more > >> basic like: > >> > >> /usr/sbin/ipmi-sensors -h 192.168.160.24 -u xxxxx -p xxxxx > >> > >> Al > >> > >> On Mon, 2017-01-23 at 15:40 -0800, Yulok Lam wrote: > >> > Hi all, > >> > > >> > I am getting an error "password verification timeout" > >> using > >> > check_ipmi_sensor 3.2 a Nagios plugin check on a Supermicro > >> Server > >> > X9DRW-7TPF+ system. I have look through the documentation > >> via > >> > > >> > >> http://www.gnu.org/software/freeipmi/manpages/man8/ipmi-sensors-config.8.html#lbAO > >> > concerning "password verification timeout" but doesn't have > >> a direct > >> > solution. Any help would be greatly appreciated! > >> > > >> > > >> > [root@XXXXXmon > >> ~]# /usr/lib64/nagios/plugins/check_ipmi_sensor -H > >> > 192.168.160.24 -U xxxxx -P xxxxx -L user -vvv > >> > ------------- begin of debug output (-vvv is set): > >> ------------ > >> > script was executed with the following parameters: > >> > /usr/lib64/nagios/plugins/check_ipmi_sensor -H > >> 192.168.160.24 -U xxxxx > >> > -P xxxxx -L user -vvv > >> > check_ipmi_sensor version: > >> > 3.2 > >> > FreeIPMI version: > >> > ipmi-sensors - 1.2.9 > >> > FreeIPMI was executed with the following parameters: > >> > /usr/sbin/ipmi-sensors -h 192.168.160.24 -u xxxxx -p > >> xxxxx -l user > >> > --quiet-cache --sdr-cache-recreate --interpret-oem-data > >> > --output-sensor-state --ignore-not-available-sensors > >> > FreeIPMI return code: 1 > >> > output of FreeIPMI: > >> > /usr/sbin/ipmi-sensors: password verification timeout > >> > > >> > output of FRU data: > >> > --------------------- end of debug output > >> --------------------- > >> > /usr/sbin/ipmi-sensors: password verification timeout > >> > > >> > -> Execution of /usr/sbin/ipmi-sensors failed with return > >> code 1. > >> > -> /usr/sbin/ipmi-sensors was executed with the following > >> parameters: > >> > /usr/sbin/ipmi-sensors -h 192.168.160.24 -u xxxxx -p > >> xxxxx -l user > >> > --quiet-cache --sdr-cache-recreate --interpret-oem-data > >> > --output-sensor-state --ignore-not-available-sensors > >> > [root@XXXXXmon ~]# > >> > > >> > Thanks, > >> > >> -- > >> Albert Chu > >> ch...@llnl.gov > >> Computer Scientist > >> High Performance Systems Division > >> Lawrence Livermore National Laboratory > >> > >> > >> > >> > >> > >> > >> -- > >> Yu Lok > -- Albert Chu ch...@llnl.gov Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory _______________________________________________ Freeipmi-users mailing list Freeipmi-users@gnu.org https://lists.gnu.org/mailman/listinfo/freeipmi-users