PowerCLI: Show HBA Path Status

18 thoughts on “PowerCLI: Show HBA Path Status”

1. Hi, can we do run this script on a cluster rather than running across the board ?

   Thanks

   • Hi Vcpguy,

     You can limit to a single cluster by adjusting the Get-View line at the very top to include a SearchRoot parameter. For example:

     Get-View -ViewType "HostSystem" -Property Name,Config.StorageDevice -SearchRoot (Get-Cluster "some Cluster" | Get-View).MoRef

     The above will limit the hosts to a cluster with the name “some Cluster”.

     Hope that helps and thanks for reading!

     Andrew

2. getting below error while running

   ConvertFrom-Csv : Cannot validate argument on parameter ‘InputObject’. The argu
   ment is null, empty, or an element of the argument collection contains a null v
   alue. Supply a collection that does not contain any null values and then try th
   e command again.
   At C:UsersmurtiDesktopHBA.PS1:34 char:82
   + ConvertFrom-Csv -Header “VMHost”, “HBA”, “Active”, “Dead”, “Standby” -InputOb
   ject <<<< $result | ft -AutoSize
   + CategoryInfo : InvalidData: (:) [ConvertFrom-Csv], ParameterBin
   dingValidationException
   + FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.Power
   Shell.Commands.ConvertFromCsvCommand

3. I’m having an issue with this script duplicating the total # of paths. Have you seen this before? Also how could I get the cluster info back like John’s original script?

   Thanks

   • Andrew,

     The only thing that comes to mind is if each HBA sees two, or more, paths to the LUNs. Aside from that, I’m drawing a blank. Can you give any more details of your environment?

     Thanks for reading,

     Andrew

4. What if your path selection is round robin, are you still supposed to see the same number of Active and StandBy paths?

5. Hi All,

   I received the below error and I edited the last time as listed below and the script worked. Thanks.

   Error :
   ——–
   “Microsoft.PowerShell.Commands.Internal.Format.FormatStartData” is
   not legal or not in the correct sequence. This is likely caused by a user-specified “format-table”
   command which is conflicting with the default formatting.
   + CategoryInfo : InvalidData: (:) [out-lineoutput], InvalidOperationException
   + FullyQualifiedErrorId : ConsoleLineOutputOutOfSequencePacket,Microsoft.PowerShell.Commands.O
   utLineOutputCommand

   Change code :

   ConvertFrom-Csv -Header “VMHost”, “HBA”, “Active”, “Dead”, “Standby” -InputObject $result | Format-Table -AutoSize | Out-Default

6. Sorry for the necro-post here, but if anyone is experiencing an issue where the total number of paths is more than expected, it’s because you have multiple paths to the same LUN (for example, through 2 different fabrics, or through 2 different controller heads). In my case, I was seeing a quadrupling of the expected paths as my fabrics are very redundant.

   The fix for this is to change this code:

   $_.Target | %{
   $_.Lun | %{
   $id = $_.ScsiLun

   $multipathInfo = $view.Config.StorageDevice.MultipathInfo.Lun | ?{ $_.Lun -eq $id }

   $a = [ARRAY]($multipathInfo.Path | ?{ $_.PathState -like "active" })
   $s = [ARRAY]($multipathInfo.Path | ?{ $_.PathState -like "standby" })
   $d = [ARRAY]($multipathInfo.Path | ?{ $_.PathState -like "dead" })

   $active += $a.Count
$standby += $s.Count
$dead += $d.Count
}
}


   to simply this:

   
$multipathInfo = $view.Config.StorageDevice.MultipathInfo.Lun | ? { $_.Path.Adapter -like "*FibreChannelHba*" }

   $a = [ARRAY]($multipathInfo.Path | ?{ $_.PathState -like "active" })
   $s = [ARRAY]($multipathInfo.Path | ?{ $_.PathState -like "standby" })
   $d = [ARRAY]($multipathInfo.Path | ?{ $_.PathState -like "dead" })

   $active += $a.Count
$standby += $s.Count
$dead += $d.Count


   The extra foreach loops (the %{ blocks, for those curious) end up causing the script to double, triple, quadruple (or more, depending on the actual number of paths to each LUN) the count of actual paths.

   Also note the duplicate adapter filter here; if your host has additional onboard adapters for things like the local drive array, it’ll show up as an extra path where you may or may not care (remove everything after the pipe in the $multipathInfo line if you do).

7. Excellent article, thanks Andrew. And, also to Ryan J’s post as well – I was getting double/triple numbers on my report.

8. I’m getting also too much paths per hba.

9. Pingback: Check Paths on FC-HBA’s – Chris – vBlog

10. Check out this solution http://vblog.hochsticher.de/?p=334 this should count correctly 😉

    • Hi Christoph,

      Thanks for reading, and thank you for contributing! Great work on your script.

      Andrew

11. Hi Andrew,

    Thanks!

    Yeah, it’s an old topic but still important 😉

12. How can i Export the result to csv ?

    • Hello Prabhu,

      Since the result is already technically a CSV before it’s formatted for display, all you would need to do is pipe $result to Out-File at the end.

      # set the result to a file
      $result | Out-File -Filepath .\result.csv
      

      Hope that helps.

      Andrew

13. Doesn’t work with EMC PPVE , any solution out there ?

14. great, thank you!