WWNs of HBAs are always available in BIOS or the controller setup during pre-boot on servers that have them installed. How to view it depends on the manufacturer. You can also use a Powershell script to query WMI for that information. http://gallery.technet.microsoft.com/scriptcenter/Find-HBA-and-WWPN-53121140 has a script that will do this for you.

Marked as answer by Boo_MonstersIncMicrosoft contingent staff, Moderator Sunday, December 16, 2012 12:49 PM

function Get-HBAWin {  
param(  
[String[]]$ComputerName = $ENV:ComputerName, 
[Switch]$LogOffline  
)  
  
$ComputerName | ForEach-Object {  
try { 
    $Computer = $_ 
     
    $Params = @{ 
        Namespace    = 'root\WMI' 
        class        = 'MSFC_FCAdapterHBAAttributes' 
        ComputerName = $Computer  
        ErrorAction  = 'Stop' 
        } 
     
    Get-WmiObject @Params  | ForEach-Object {  
            $hash=@{  
                ComputerName     = $_.__SERVER  
                NodeWWN          = (($_.NodeWWN) | ForEach-Object {"{0:X2}" -f $_}) -join ":"  
                Active           = $_.Active  
                DriverName       = $_.DriverName  
                DriverVersion    = $_.DriverVersion  
                FirmwareVersion  = $_.FirmwareVersion  
                Model            = $_.Model  
                ModelDescription = $_.ModelDescription  
                }  
            New-Object psobject -Property $hash  
        }#Foreach-Object(Adapter)  
}#try 
catch { 
    Write-Warning -Message $_ 
    if ($LogOffline) 
    { 
        "$Computer is offline or not supported" >> "$home\desktop\Offline.txt" 
    } 
} 
 
}#Foreach-Object(Computer)  
  
}#Get-HBAWin

you may use the PowerShell command, Get-WmiObject to retrieved the information in Windows Server 2012.

For example:

Get-WmiObject -class MSFC_FCAdapterHBAAttributes -namespace "root\WMI" | ForEach-Object {(($_.NodeWWN) | ForEach-Object {"{0:x}" -f $_}) -join ":"}


If you need assistance with PowerShell, this forum could help you.

http://social.technet.microsoft.com/Forums/windowsserver/en-US/home?forum=winserverpowershell

Hope this helps.

We are announcing our transition to a paid-only model and new pricing plans, starting today. In recent times, we were able to expand our user base exponentially. Our decision to switch to a new model will allow us to keep our focus on improvements and expansions to meet the increasing needs of our customers. It will also give us the possibility to introduce new services and expand our product range.

As of today, new accounts will not start with free included storage. Remaining customers will keep their free storage.

The hidden manufacturers modify some kernel-sources to get support for the specific boards in the Linux Kernel. Most of the time it is only done once and in a very dirty way. That’s why it is impossible for them to submit this patches to http://kernel.org they would never accept such hacks there.

Also they provide the Linux OS for the box most of the time compiled for exactly this kernel together with a cross toolchain for that system. So they more or less already defined the only C-library-version that the OS could be based on. The cross toolchain is only able to build binaries for exactly this uclibc/glibc.

What do we learn from this?
The selling companies cannot upgrade the kernel inside the boxes or they can do it only with major efforts…it is very unlikely that this will be done as it costs money. Because of the dirty hacks in the kernel sources some features are just impossible. After the hidden manufacturer has ported everything and the selling company has started to sell the box there won`t be many new innovative new features.