This api, "storage-adapter-get-adapter-info", is the same one used by Get-NaStorageAdapterInfo...however the objects output by that cmdlet do not have the port name property, as you noted. On my test system the initiator ports are only used as FC-AL initiators for shelves, so the WWPN and WWNN are the same. It could be that these values are always the same so there is/was no value in having both and that is the rationale behind removing them. Or it could be a bug...

Could you please test the above with your system(s) and let me know if they are different or the same. If they are different it may be worth opening a bug to determine if it was an oversight due to an API change between ZAPI versions or something similiar.

Hope that helps.

Andrew

If this post resolved your issue, please help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

Re: Get-NaStorageAdapterInfo issue (v3.2) - No FcPortName Info

Thanks for your help and reply. I think you pointed to the right direction. Here is what I found after a few tests against my systems.

It appreas that Data ONTAP 7-Mode does NOT assign different strings to WWNN and WWPN if it is initiator type adapter AND the card is from NetApp ( or , with NetAPP OUI 00A098 more acurately speaking) The version I tested is 8.2.3P5, if the card is not from NetApp, let's see it is from QLogic, which I tested, then the WWPN and WWNNs are not the same, which is normal. The version I tested is 8.1.4P9.

I think to populate both WWPN and WWPN are more desirable and to assign different value to WWPN and WWNN is more practical.

2. Get-NaFcAdapter will return different output depends on Data ONTAP version, again , at least it is true for the two versions I tested. In 8.1.4P9, it reports ONLY TARGET ports, in 8.2.3P5, it report both and got improved.

That's the reason why I mentioned on very top saying that Get-NaFCAdapter lists only target ports, actually that is a wrong statement, it is version related.

3. I did ran the code you provided, and the WWPN did not return under both versions

4. Any documents that I can reference if I want to use Invoke-SystemAPI in case the cmdlets not work properly like what you are doing? I did download the NetApp Manageability SDK, not sure if the doc with it is the one I should reference.

Re: Get-NaStorageAdapterInfo issue (v3.2) - No FcPortName Info

Regarding #2, the PowerShell Toolkit uses the NMSDK, which is itself based on ZAPI versions. ZAPI periodically changes and will add/remove vaues, options, and entire APIs, so it's no surprise that different ONTAP versions have different results.

For #4 you'll want to use the documentation labeled "NetApp Manageability SDK" from the A-Z documentation page. Once there you'll see links for docs on the .NET, Java, and generic NMSDK (at the bottom). The latter is the one you want for ZAPI info.

Andrew

If this post resolved your issue, please help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

Re: Get-NaStorageAdapterInfo issue (v3.2) - No FcPortName Info

Appreciated your help, I will reference the API as needed trying to get what I need and now closer to get it resolved with your help. And yes, it's normal that the APIs changes from version to version, and that's why we get more and more functions out there.

Also, tons of thanks to the PSTK team, which makes our management to our 100+ NetApp systems (Na, Nc and Ne...) much easier.