AVAGO HBA driver - MPT3SAS vs MSGPT3

Similar Questions

• BIOS of ESX, NIC and HBA driver Versions

  Hi friends,

  am intermiediate POWERCLI user and shell the scritping, please you colud help launch me script below.

  more information http://www.sandfordit.com/vwiki/ESX_Script_Extracts_and_Examples

  Thanks in advance,

  Aldo.

  Get versions of driver BIOS, NIC and HBA is dependent on what is reported to the ESX provider CIM material supplier. This script has been written using different servers of HP and well can work for them.

  # ===============================================================
  # ESX Inventory Getter
  # ===============================================================
  # Simon Strutt        November 2010
  # ===============================================================
  #
  # Version 1
  # - Initial Creation
  #
  # Version 2 - Dec 2010
  # - Added BiosVer, CpuCores, CpuModel, HbaModel, NicModel
  # - Bugfix: Corrected VC connection handling
  # - Removed dependency on obsoleted properties (from upgrade to PowerCLI v4.1.1)
  #
  # Limitations
  # - Tested on HP DL380 (G7), BL465 (G7), BL495 (G6), BL685 (G5)
  # - Supports 1 distinct HBA model, 2 distinct NIC models
  #
  # ================================================================
   
  $start = Get-Date
  $OutputFile = "ESXs.csv"
  $VC_List = "ESX-Check.csv"
  $UserFile = "User.fil"
  $PassFile = "Pass.fil"                           # Encrypted file to store password in
  $Results = @()
   
  # Include library files
  . .\lib\Standard.ps1
   
  Start-Transcript -Path ESX-Inventory.log
  Log "Started script run at $start"
   
  # Function-U-like ===================================================================================
   
  Function Get-NicDriverVersion ($view, $driver) {
      # Gets the CIM provided driver version (tallies up driver name with CIM software component)
      $result = ($view.Runtime.HealthSystemRuntime.SystemHealthInfo.NumericSensorInfo | Where {$_.Name -like $driver + " driver*"} | Get-Unique).Name
      $result = ([regex]::Matches($result, "(\b\d)(.*)(?=\s)"))[0].Value         # HP regex to extract "2.102.440.0" for example
      $result
  }
   
  # =================================================================================================== 
   
  # Load list of VC's
  try {
      $VCs = Import-CSV $VC_List
  } catch {
      Log "ERROR: Failed to load list of vC's"
      Exit
  }
   
  # Load password credential from encrypted file
  $pass = Get-Content $PassFile | ConvertTo-SecureString
  $user = Get-Content $UserFile
  $cred = New-Object System.Management.Automation.PsCredential($user, $pass)
   
  foreach ($vc in $VCs) {
   
      # Connect to VC
      try {
          Log("Connecting to " + $vc.vc)
          $VCconn = Connect-VIServer -Server $vc.vc -Credential $cred -errorAction "Stop"
      } catch [VMware.VimAutomation.ViCore.Types.V1.ErrorHandling.InvalidLogin] {
          Log("Unable to connect to vCentre, invalid logon error !!")
          Log("Abandoning further script processing in order to prevent potential account lockout.")
          Break
      } catch {
          Log("Unable to connect to vCentre - " + $_)
          Continue
      }
   
      # Get ESX objects
      Log("Getting list of ESXs to check on " + ($vc.vc) + "...")
      $ESXs = Get-VMHost -Server $vc.vc | Sort -property Name
      Log("Got list of " + ($ESXs.Count) + " ESXs to check") 
   
      ForEach ($ESX in $ESXs) {
          $row = "" | Select VC, Cluster, Name, IP, Version, Make, Model, BiosVer, CpuCores, CpuModel, HbaModel, HbaDriver, HbaDriverVer, Nic1Model, Nic1Driver, Nic1DriverVer, Nic2Model, Nic2Driver, Nic2DriverVer
          Log($ESX.Name)
   
          # Store objects which get re-used for efficiency
          $ESXview = Get-View -VIObject $ESX
          $VMHostNetworkAdapter = Get-VMHostNetworkAdapter -VMHost $esx 
   
          # Get the basics
          $row.VC = $vc.vc
          $row.Cluster = $ESX.Parent
          $row.Name = $ESX.Name.Split(".")[0]
          $row.IP =  ($VMHostNetworkAdapter | Where {$_.ManagementTrafficEnabled -eq "True" -or $_.DeviceName -like "vswif*" -or $_.Name -eq "vmk0"}).IP
          $row.Version = $ESX.Version + " (" + $ESX.Build + ")"
          $row.Make = $ESX.Manufacturer
          $row.Model = $ESX.Model
   
          # Now onto the more ESX version / hardware specific stuff (new versions of hardware will require further work below)
   
          # BIOS
          if ($ESXView.Hardware.BiosInfo) {     # Works on some systems 
              $row.BiosVer = $ESXview.Hardware.BiosInfo.BiosVersion + " " + $ESXview.Hardware.BiosInfo.ReleaseDate.ToString("yyyy-MM-dd")   # Need date for HP servers as they use same version no for diff versions!
          } else {
              $row.BiosVer = ($ESXview.Runtime.HealthSystemRuntime.SystemHealthInfo.NumericSensorInfo | Where {$_.Name -like "*BIOS*"}).Name
              $row.BiosVer = ([regex]::Matches($row.BiosVer, "[A-Z]\d{2} 20\d{2}-\d{2}-\d{2}"))[0].Value           # HP regex to extract "A19 2010-09-30" for example
          }
   
          # CPU info
          $row.CpuCores = $ESXview.Hardware.CpuInfo.NumCpuCores.ToString() + " (" + $ESXview.Hardware.CpuPkg.count + "x" + $ESXview.Hardware.CpuPkg[0].ThreadId.count + ")"
          $row.CpuModel = $ESX.ExtensionData.Summary.Hardware.CpuModel
   
          # HBA info (script assumes only one HBA model in use)
          $row.HbaModel = ($ESX.ExtensionData.Config.StorageDevice.HostBusAdapter | Where {$_.Key -like "*FibreChannel*"})[0].Model
          $row.HbaDriver = ($ESX.ExtensionData.Config.StorageDevice.HostBusAdapter | Where {$_.Key -like "*FibreChannel*"})[0].Driver     # Includes version for ESX3
          $row.HbaDriverVer = ($ESXview.Runtime.HealthSystemRuntime.SystemHealthInfo.NumericSensorInfo | Where {$_.Name -like "*" + $row.HbaDriver + "*"}).Name
          $row.HbaDriverVer = ([regex]::Matches($row.HbaDriverVer, "(\b\d)(.*?)(?=\s)"))[0].Value
   
          # NIC info (script only supports two distinct NIC types)
          $nics = $ESXview.Hardware.PciDevice | Where {$_.ClassId -eq 512} | Select VendorName, DeviceName, Id | Sort-Object -Property DeviceName -Unique
          if ($nics.count) {
              $row.Nic1Model = $nics[0].VendorName + " " + $nics[0].Devicename
              $row.Nic2Model = $nics[1].VendorName + " " + $nics[1].Devicename
   
              # Use PCI ID to match up NIC hardware type with driver name
              $row.Nic1Driver = ($VMHostNetworkAdapter | Where {$_.ExtensionData.Pci -eq $nics[0].Id}).ExtensionData.Driver
              $row.Nic2Driver = ($VMHostNetworkAdapter | Where {$_.ExtensionData.Pci -eq $nics[1].Id}).ExtensionData.Driver
   
              $row.Nic1DriverVer = Get-NicDriverVersion $ESXview $row.Nic1Driver
              $row.Nic2DriverVer = Get-NicDriverVersion $ESXview $row.Nic2Driver
           } else {
              # Annoyingly, $nics is not an array if there's only one NIC type, hence seperate handling
              $row.Nic1Model = $nics.VendorName + " " + $nics.Devicename
              $row.Nic1Driver = ($VMHostNetworkAdapter | Where {$_.ExtensionData.Pci -eq $nics.Id}).ExtensionData.Driver
              $row.Nic1DriverVer = Get-NicDriverVersion $ESXview $row.Nic1Driver
          }
   
          $Results = $Results + $row
      }
      Disconnect-VIServer -Server $VCconn -Confirm:$false
  }
  $Results | Format-Table *
  Log("Writing results to $OutputFile...")
  $Results | Export-Csv -path $OutputFile -NoTypeInformation
   
  Log("All completed")
  Stop-Transcript
  			 
  Hi Aldo,.
  As directed by the PM, I sent you, I genericised the script a bit more, it should be easier to use (no need to the Standard.ps1 file).  Similarly the name of your Center virtual servers don't need to be put in a separate file CSV file is
  To avoid having to create credentials files, delete the following lines...
  # Load password credential from encrypted file
  $pass = Get-Content $PassFile | ConvertTo-SecureString
  $user = Get-Content $UserFile
  $cred = New-Object System.Management.Automation.PsCredential($user, $pass)
  
  .. .and replace by (the script will prompt you for the user/pass)...
  $cred = Get-Credential
  
  Hope this gets you operational.
  Note that I found to NIC and driver versions HBA is quite unreliable using this script, that there is a lot of consistency in what is returned by ICM to hardware vendors.  More on the servers I tested with firmware HBA was never available.  A more reliable, but more complex method is to use PowerShell for SSH for your ESX, which has its own problems, but is another approach (when you do audits of system I tend to use both).  See below for more info...
  http://vblog.Strutt.org.UK/2012/04/ESX-HBA-and-NIC-driverfirmware-versions/
  All the best...
  Simon
  		   

• Where can I find which version of HBA driver is loaded?

  I have ESXi 4 build 164009.  I'd like to find out what version of the Emulex is loaded on this host?

  the below works for ESX, and if you can activate the Technical Support mode get to the cli, this should work for ESXi as well

  http://KB.VMware.com/kb/1002413

• NIC & Storage Driver Version and Firmware

  Hello

  I would like to know powercli average to determine the firmware revision, version, and NETWORK/storage card driver name. I can take this info via

  esxcfg-info takes so long

  ethtool-i vmnic0

  Thank you

  The seller and the device to take a look at my post to appoint this material .

  According to the HW you use, you can try using the CIM for the information.

  Take a look at the BIOS of ESX, NIC and HBA driver Versions, which shows a way to do with HP hardware.

• ESXi 5 Server does not recognize HP StorageWorks 81B HBA

  I'll put up 4 ESXi 5 servers attached to a HP P2000 SAN. I'm quite familiar with ESX and VMware. have been running ESX 3.5 for about 3 years. This new environment gives me a problem that ESXi 5 does not see the HBAs HP StorageWorks 81 b installed on servers HP Proliant DL 380 G7. I see that it is a known issue and I have been tring to follow the directions outlined in the RFSO HP (see link below). I the document is poorly written and not very clear. I'm stuck at step 3 where it says:

  "Install the HBA driver. Download driver HBA Brocade, extract the compressed file and burn (or climb) the ISO image. Download and install VMware vSphere CLI. Open the CLI and change directory C:\Program VMware vSphere CLI\bin .

  Run the following command and check do not omit the dot and bar backslash:

  ".\Vihostupdate.pl server 10.12.243.130 - - root username - - password Password1-- install - - bundle E:\offline-bundle\BCD-bfa-2.3.0.2-00000-offline_bundle-344638.zip"

  I downloaded the ISO file and the file and the path "offline-bundle\BCD-bfa-2.3.0.2-00000-offline_bundle-344638.zip" exist on the CD but when I run the command in the CLI, it says "error connecting to the server" ". https://localhost/SDK/WebService ' ' host is perhaps not a vcenter or ESX server. I try to run it from a Windows Server that is not a vCenter server but how I go this from a vCenter server if I can not see the HBAs and therefore cannot see the SAN and am not currently in a position to implement the vCenter server. I also replaced the 10.12.243.130 IP address IP address of the ESX Server and that has not worked, and of course, I entered the correct password for the field 'Password1 '. I could run this command from the ESX Server, if so, what would be the command line? In any case, I'm stuck at this point. I called HP support and they were no help at all.

  http://h20000.www2.HP.com/bizsupport/TechSupport/document.jsp?lang=en & CC = UK & TaskID = 110 & prodSeriesId = 3662826 & prodTypeId = 12169 & objectid = c02773230

  According to HCL, the adapter is not supported on ESXi 5.0.

  However it looks like there is a driver for ESXi 5.0 to http://downloads.vmware.com/d/details/dt_esxi50_brocade_bfa_3000/dHRAYnRqdGpiZHAlJQ== that you could try (at your own risk) rather than the one you mentioned. Installation instructions are included in the zip file.

  André

• How to find the coordinates of the HBA in the ESX service console

  Hello

  We would like to know the following details of HBA on the ESX Server. Help, please.

  • Manufacturer of HBA

  • HBA model

  • Description of HBA

  • Version of the HBA driver

  • HBA Firmware Version

  • WWN

  • WWP

  ESX 3.0.1 version specific.

  You can find in/proc/scsi /.

  the wwn you can get with VI Client in Configuration > storage

  Identify a HBA firmware

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=1002413

  If you have found this information useful, please consider awarding points to 'Correct' or 'Useful'*.

• How to connect the SCSI tape drive to comments

  New user of VMWare here - I like it so far.  In any case, I have a LTO3 SCSI drive, I would like to use with one of our virtual machines running on our host ESXi 4.1.  I installed a LSI 53 c 1030 SCSI HBA, appearing on the HW compatibility list.  The drive is an HP Ultrium 920 LTO3.  I use BackupExec 12.5 x 64 on the VM (Win2K8 R2 x 64).

  I can't find clear instructions for setting this up in ESXi.  Nothing in the implementation or the Config Guide.  I'm not if I use passthrough or without passthrough, etc..  Can someone tell me the good documentation on how to get this set up and work or by post simple steps to get the virtual machine, see the HBA/drive?

  TIA

  Hello

  If you had plugged the band to the HBA and then restarted the server, you can go to your virtual machine, and then change the settings and in the Hardware tab, add hardware.

  Go to SCSI devices and add the tape to the virtual machine.

  In other words, if your hardware supports, enable passthrough for the host HBA, in configuration, settings in advance.

  Then reboot and go to the settings of the virtual machine, adding hardware and click on PCI device, add the HBA to this virtual machine.

• The fact to unplug cable adapter HBA on the ESXI host causing VI Client to hang

  We use HP DL380 G5 with the embedded HP version (ESX 3.5i U3 + latest patch)

  This server has all of the available features available (HA, DRS etc..) The server has 2 EMC QLogic 2340 HBA with the latest EMC firmware in it.

  If I look in the VCenter in a disk storage properties it shows me 4 available for SP on our SAN paths. (all MRU settings. we have SAN active/passive)

  Now, here's the problem we have:

  As soon as I unplug the fibrecable, the Vcenter must use another active path. It looks like this, the VM Machines are continue to operate, but only after a new analysis of the hba it also shows that the 2 paths are broken

  But when I close the VI Client and run it then the problems begin:

  • Machines of VM loses connections (rattling irregular and after awhile not available)

  • Customer VI freezes and does not

  In the end, I have reconnected the fibrecable (because each time I start the VI Client it crashes) all problems disappeared and everything works again.

  If I then take a look at the Machines-VM BSOD some are, some have the writeback failed

  Disconnect a fibrecable shall not give any disruption, that's why we have redundant HBA. But it does!

  Anyone have any suggestions?

  HBA QLogic VMkernel pilots understand firmware which (actually) hot-loaded on the HBA driver support.

  See http://communities.vmware.com/message/325181#325181

  So, don't bother with the HBA firmware level.

  See the latest "Fibre Channel SAN Configuration Guide.

  page 99: setting the time-out HBA to failover (value qlport_down_retry)

  Good luck.

• Windows - VIC12xx drivers

  I'm trying to locate the HBA drivers both NIC for the Win2K8R2 VIC1280. Can anyone point me in that direction?

  Hello

  You cann download the drivers from here

  UCS-bxxx - drivers. 2.0.3 b .iso

  http://www.Cisco.com/Cisco/software/release.html?mdfid=283853163&flowid=25821&softwareid=283853158&release=2.0%283b%29&relind=available&rellifecycle=&RelType=latest

  ENIC / location of the FNIC (HBA) driver

  http://www.Cisco.com/en/us/docs/unified_computing/UCS/OS-install-guides/Windows/BSERIES-WINDOWS_appendix_0100.html

  HTH

  Padma

• install ESXi on UCS to boot from SAN

  Hello

  I have ucs and I need to boot from SAN

  I need to confirm something

  When I was installing WindowsServer the UCS to boot from SAN. I have attached the iso drivers for the HBA driver so that the blade can detect the boot LUN.

  Now, I'm going to install ESXi. Do you know if I need to use the iso as drivers for the HBA as with windows or ESXi detects this and will present me the boot LUN to start the installation?

  We will use the ESXi, VMware no custom of Cisco

  Thank you

  Hello

  A major difference:

  MSFT Windows has no drivers of enic fnic UCS preinstalled with the distribution of iso.

  ESXi has, but most likely not one who demands that the UCS support matrix.

  See http://www.cisco.com/web/techdoc/ucs/interoperability/matrix/matrix.html

  Therefore you install ESXi ISO of the distribution, and then you update the drivers of the enic/fnic

  See http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/sw/vic_driver...

• Host switches mode does not not randomly. Must reboot to recover the access

  Assessment:

  + Host:

  \==+Hardware info:

  |----Product Name............................................. Flex System x 240 compute node-[873715-X]-

  |----Vendor Name.............................................. IBM

  / var/log # vmware - vl

  VMware ESXi 5.5.0 build-2302651

  VMware ESXi 5.5.0 Update 2

  vmksummary.log:

  2015 02-08 T 14: 51:29Z bootstop: host started

  2015 02-08 T 15: 00:02Z heartbeat: place 0d0h11m18s, 18 mV; [[37365 vmx 8154248 Ko] [37342 vmx 8444240 Ko] [37804 vmx Ko 13521300]] [[37579 Oba - LSIESG_SMI 10% max] [35668 sfcb-pycim 24% max] [35680 Oba-vmwa]

  re_bas 30% max]]

  While they inspected the vmkernel logs, we see that the abandoned HBA driver command & since there was no Ackonwledge of this demolition of the side storage it resets the SCSI IO

  8 Feb 09:29:31 vmkernel: cpu39:4876634) lpfc: lpfc_scsi_cmd_iocb_cmpl:2185: 0: (0): 3271: FCP cmd x 89 failed < 1/0 > sid x721a01, enticed x72f500, oxid x1b4 iotag x4ba.

  Asked host Abort Req

  8 Feb 09:29:31 vmkernel: cpu25:32854) NMP: nmp_ThrottleLogForDevice:2322: Cmd 0 x 89 (0x4136ce66d440, 32821) dev "naa.60050768019807b72800000000000000" on the path "vmh".

  BA1:C0:T1:l0"failure: H:0 x 5 D:0 x 0 P:0 x 0 Possible sense data: 0 x 0 0 x 0 0 x 0. Law: EVAL

  8 Feb 09:29:31 vmkernel: cpu25:32854) WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: State of 'naa.60050768019807b72800000000000000' of device NMP doubt; has asked

  fast track status update...

  8 Feb 09:29:31 vmkernel: cpu25:32854) ScsiDeviceIO: 2338: Cmd (0x4136ce66d440) 0 x 89, ISP CmdSN worldwide 32821 to dev «naa.60050768019807b72800000000000000» 0x47f84b

  conduit H:0 x 5 D:0 x 0 P:0 x 0 Possible sense data: 0 x 0 0 x 0 0 x 0.

  8 Feb 09:29:31 vmkernel: cpu39:4876634) lpfc: lpfc_scsi_cmd_iocb_cmpl:2185: 0: (0): 3271: FCP cmd x 89 failed < 1/19 > sid x721a01, x72f500, oxid x 648 iotag x94e SLA fact

  t asked the host Abort Req

  8 Feb 09:29:31 vmkernel: cpu25:32854) NMP: nmp_ThrottleLogForDevice:2322: Cmd 0 x 89 (0x4136ceb8a840, 32821) dev "naa.60050768019807b72800000000000283" on the path "vmh".

  BA1:C0:T1:L19"failure: H:0 x 5 D:0 x 0 P:0 x 0 Possible sense data: 0 x 0 0 x 0 0 x 0. Law: EVAL

  8 Feb 09:29:31 vmkernel: cpu25:32854) WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: State of 'naa.60050768019807b72800000000000283' of device NMP doubt; has asked

  fast track status update...

  8 Feb 09:29:31 vmkernel: cpu25:32854) ScsiDeviceIO: 2338: Cmd (0x4136ceb8a840) 0 x 89, ISP CmdSN worldwide 32821 to dev «naa.60050768019807b72800000000000283» 0x1b595c

  conduit H:0 x 5 D:0 x 0 P:0 x 0 Possible sense data: 0 x 0 0 x 0 0 x 0.

  upgrade the version of the Emulex driver 10.2.340.18 & Firmware for 10.2.340.10

• Output format of two get various cmdlets

  I would like to get an output of two commands various get and put them in the same format-table... Y at - it assistance from high level to do this?  There is no folder location in the output of get-passthroughdevice, but it does in get - vm...

  Get-VM-name "vm1 | Get-PassthroughDevice |

  Select * | Where-Object {$_.} Name - eq "Cisco FCoE HBA Driver VIC"} |

  Format-Table-property @{Expression = {$_.}} VM}; Label="VM_Name";width=25},@{expression={$_. Name}; Label = "PCI_Type"; width = 50}

  Get-VM-name "vm1 |

  Format-Table-property @{Expression = {$_.}} Name}; Label="VM_Name";width=50},@{expression={$_. File}; Label = "Folder"; width = 50}

  Try like this (the file information is here)

  Get-VM-name "vm1 | Get-PassthroughDevice |

  Where-Object {$_.} Name - eq "Cisco FCoE HBA Driver VIC"} |

  Select @{N = "VM"; E={$_. UM Name}},@{N='Folder'; E={$_. UM Folder.Name}}, Name

• Batch Move-VM (in a folder) of the output of Get - VM

  Hey guys, I wanted to check with everyone and see if I could get feedback on it.  I do some cleaning and organization and I have most of the script for what I want to do, but currently I don't know how to make through export to a CSV file, and then, by running a separate script to move the virtual machines based on a CSV import.

  Is there a way to do this in a single swift script by referring to the output of the below for use with the Move-VM cmdlet?

  Getting the virtual machine I need to navigate:

  Get-VM-location "data center" | Get-PassthroughDevice |

  Select * | Where-Object {$_.} Name - eq "Cisco FCoE HBA Driver VIC"} |

  Format-Table-property @{Expression = {$_.}} VM}; Label="VM_Name";width=25},@{expression={$_. Name}; Label = "PCI_Type"; Width = 75}

  Try like this

  Get-VM-location "data center" |

  Where {$_ |} Get-PassthroughDevice | Where-Object {$_.} Name - eq "Cisco FCoE HBA Driver VIC"}} |

  Move-VM-Destination $folder

• Scripted installation crush LUN SAN FC

  After an incident, I was the only one to take the blame of I want to start a discussion on a scripted installation problem.

  We used a script to kickstart to a wide configuration of our ESXI 5.x several times. This time, I adapt a kickstart to an ESXi 5.1 U1 (custom HP) script and I forgot to disable the FC connection from the blade server. Subsequently, installing replaced a vmfs LUNS DATA and I had to restore several VM´s running with a lot of discussion later.

  That's why I want to ask the community if someone really smart guy looked at this issue before to keep installing stupid people (me) to crush the SAn FC lun without connections stop FC?

  I added a KS.cfg of sample to give you an overview that we install.

  I would appreciate if anyone can give me advice.

  On my blades, when to use kickstart, I use the installation option - firstdisk to force th einstall to use the local disk by specifying the internal disk controller driver.  Of course, this does not work when you use the SAN boot, but if you install on a local drive, it should work.

  Example:

  install firstdisk - mptsas

  You can also add the preservevmfs - pass if you are super paranoid, but if the local disk is a VMFS, your encrypted facility likely mistake.

  Another thing that I do, it's the Image Builder CLI allows you to create a custom image that has the FC HBA deleted drivers, so the installer can not possibly access the LUN CF.  Once installed ESXi, during the kickstart script firstboot section, I have install the HBA driver.  Yet once, if you start in SAN, this won't help.

  Example:

  # Script FirstBoot

  firstboot % - interpreter = busybox

  # In Maintenance mode
  Vim - cmd hostsvc/maintenance_mode_enter

  ############################################
  # Install/configure the drivers.

  # Install HBA QLogic FC-FCoE adapter driver
  software esxcli vib install d http://x.x.x.x:8181/Drivers/vib/qla2xxx-934.5.6.0-offline_bundle-887798

• 100% CPU after deleting store data/VMFS Rescan

  I experience a spike in the CPU (hitting 100% in 'real time' graphic vCenter) after a deletion of data and for a new scan VMFS store. Everyone knows about this problem before? If so, what were the steps you took to solve the problem?

  I'm under Qlogic FC HBA (qle2460) and esx hosts are connected to a Clariion CX4 Bay. I also have PowerPath installed VE. I made sure that I am under the latest HBA driver, but I still have the issue.

  Thanks in advance!

  Problem persists, you should be able to see these messages in your log files.  Until you go to ESXi 5 and can have the Rescan avoid them completely, you can still see these.  At least, I always do and on several different groups.  The time-out makes faster restart, but rescan suffers the same deadline.  Not as long as the shoe, as you have driver loading fc, which causes the delay, then the LUNs and vmfs, scans which adds another time, or two, which is the same question to take 3 times as long as the boot.  The advanced value helps to relieve waiting times of 1/2 of the total, but not all the.  The new analysis includes a timeout during the analysis of lun and not for a reload of pilot.

  At least what I've seen in my experience.

  -KjB