Cpu Reservation Error Timeout

Tweet Storage Performance and Timeout Issues Posted on April 10, 2012 by Rick Blythe Here's our second waiting for timed out hb log deep-dive from Nathan Small (Twitter handle: vSphereStorage). If you

Reservation State On Device Is Unknown.

missed the first one, here it is. History of the issue General storage performance issue while nmp device state in doubt; requested fast path state update experiencing timeouts and SCSI reservation issues (Timeout/conflict) on ESX 4.1 (VMware View) and ESX 5.0 environments. Need to determine why these events are being seen and scsi reservation conflict vmware how we can improve performance.The first step when troubleshooting this type of issue is to take a frame of reference that is visible across all hosts. Here is the issue observed on one of the ESX 4.1 host:ESXi 4.1:Mar 28 17:12:58 vmkernel: 34:11:37:08.013 cpu13:4262)NMP: nmp_PathDetermineFailure: SCSI cmd RESERVE failed on path vmhba1:C0:T2:L1,

Lun Reset Command

reservation state on device naa.60060480000190100554533032324644 is unknown.Mar 28 17:12:58 vmkernel: 34:11:37:08.013 cpu13:4262)ScsiDeviceIO: 1688: Command 0x16 to device "naa.60060480000190100554533032324644" failed H:0x5 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.Mar 28 17:12:58 vmkernel: 34:11:37:08.013 cpu13:4262)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe: NMP device "naa.60060480000190100554533032324644" state in doubt; requested fast path state update…Mar 28 17:12:58 vmkernel: 34:11:37:08.013 cpu14:4134)WARNING: FS3: 7120: Reservation error: TimeoutWhen reviewing the logs from the ESX 5.0 host, we see the issue observed at the same time:ESXi 5.0:2012-03-28T17:12:56.481Z cpu11:4107)NMP: nmp_PathDetermineFailure:2084: SCSI cmd RESERVE failed on path vmhba2:C0:T3:L23, reservation state on device naa.60060480000190100554533033364445 is unknown.2012-03-28T17:12:56.481Z cpu11:4107)NMP: nmp_ThrottleLogForDevice:2318: Cmd 0x16 (0x4124003d4740, 0) to dev "naa.60060480000190100554533033364445" on path "vmhba2:C0:T3:L23" Failed: H:0x8 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0. Act:EVAL2012-03-28T17:12:56.481Z cpu11:4107)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237:NMP device "naa.60060480000190100554533033364445" state in doubt; requested fast path state update…2012-03-28T17:12:56.481Z cpu11:4107)ScsiDeviceIO: 2322: Cmd(0x4124003d4740) 0x16, CmdSN 0x23102 from world 0 to dev "naa.60060480000190100554533033364445" failed H:0x8 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.2012-03-28T17:12:56.481Z cpu1:4132)WARNING: FS3: 1835: Reservation error: Timeou

clean. Screenshot instructions: Windows Mac Red Hat Linux Ubuntu Click URL instructions: Right-click on ad, choose "Copy Link", then paste here → (This may not be possible with some https://sourceforge.net/p/ipmiutil/mailman/message/20232479/ types of ads) More information about our ad policies X You seem to have CSS turned off. Please don't fill out this field. You seem to have CSS turned off. Please don't fill out this field. Briefly describe the problem (required): Upload screenshot of ad (required): Select a file, or drag & drop file here. ✔ ✘ Please provide the ad click URL, if scsi reservation possible: Home Browse IPMI Management Utilities Mailing Lists IPMI Management Utilities Brought to you by: arcress, gdicaire, kbanks, lapointep, thibaulf88 Summary Files Reviews Support Wiki Mailing Lists Tickets ▾ Support Requests Patches Feature Requests Bugs News Discussion Code-svn Code-git ipmiutil-developers Re: [ipmiutil-developers] ipmi_monitoring_sensor_readings_by_record_id: internal IPMI error Re: [ipmiutil-developers] ipmi_monitoring_sensor_readings_by_record_id: internal IPMI error From: Cress, Andrew R - 2008-08-26 18:46:26 David, For the cpu reservation error errors on ipmiutil getevt and ipmiutil health, it appears that the Dell BMC does not support the following commands: SetBmcEnables (cmd=0x2E, netfn=0x06) - gives completion code 0xCC GetChannelAuthenticationCapabilities (cmd=0x38, netfn=0x06) - gives completion code 0xCC Note that the error from set_bmc_enables means that the normal event message buffer is not available, but the SEL method would still work ok (ipmiutil getevt -s). Also, about the bmchealth error, I'll bet that the Dell BMC does not support the 'this channel' value (0x0E). ipmiutil cmd 00 20 18 38 0e 02 (what bmchealth does, 'this channel', will fail) ipmiutil cmd 00 20 18 30 01 02 (probably the lan channel, probably will work) For the sensor stuff, you can compare those results with the output of "ipmiutil sensor". Andy -----Original Message----- From: ipmiutil-developers-bounces@... [mailto:ipmiutil-developers-bounces@...] On Behalf Of Al Chu Sent: Tuesday, August 26, 2008 2:35 PM To: David Sparks Cc: ipmiutil-developers@... Subject: Re: [ipmiutil-developers]ipmi_monitoring_sensor_readings_by_record_id: internal IPMI error Hey David, I think this e-mail was meant for the freeipmi mailing list? Not ipmiutil? I'll respond to your e-mail on the freeipmi-devel@... mailing list. Al On Tue, 2008-08-26 at 11:31 -0700, David Sp