APD Errors on ESX host after upgrade

Recently, I upgraded all my ESX to 6 to get the full VDP feature. A week after upgrade I started noticing VM issues and slowness on data discovery.

VMware support pointed out the logs .............."naa.60a98000383032754c3f4671786d6339" - failed to issue command due to Not found (APD), try again." on only two ISCSI LUN out of four.  They traced the log back couple of days before the upgrade, that makes it confusing if it happened due to upgrade or was already there. VMware said it needs to be addressed by Netapps.

Netapp took 1 week just to collect logs never had support person calling. Today there was another support person calling and ran Interoperability Matrix Tool. When we selected ONTAP 8.2 with ESX 6 the protocol for ISCSI was grayed and he speculated  that ESX 6 does not support ISCSI on ONTAP 8.2 7 node but it did not show any error or explanation. He said netapps has communicated  this bug fix to vmware and until the fix is released by VMware it wont work on ONTAP 8.2 and it should be up to vmware. The article on bug fix is vague and does not clearly explains, if it is ISCSI or could it fix if I change datastore to NFS.

Now VMware recommeds, if netapps has pointed out issue with 6 then I should rollback the version. But I am sure if rollback would really fix it. Plus I have already done clean install on one ESX host thinking how clean installation works in comparison to issues showed after upgrade.

Another, point I came across while doing clean installation on one ESX host to eliminate if the issue is with upgrade was virtual network setup. Looks like the remote support vendor had setup multi-homed network switch with two ISCSI  kernel storage switch (active and unused order NIC is different on both as active/ unused ) with same network subnet, one management network and vm network on same subnet different than storage subnet and one additional VLAN for voice using two 10 GB NIC cards. MTU on storage network is set to 9000.
I had some issues discovering storage ISCSI LUN after discovering adaptor. I had to create separate network switch for storage by using one of 10 G adapter and once the storage was discovered and changed the it back to same as the other virtual switches. This add another confusion, if it is something to do with multi homed setup, if this is the case why problem started showing after 6 months only at the time of upgrade. The log on clean installed still shows error on ISCSI storage network but not exactly the ADP error but does show bunch of error with ISCSI.

Has anyone experienced similar kind of issue with ESX upgrade using netapps FAS2554 ontap 7 mode
pchettriIT DirectorAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
We've had issues, with ESXi 6.0.0GA ad 6.0.0B with OnTap, I'll have to check notes to get the versions.

But also multihomed iSCSI paths does not sound correct, did NetApp not suggest how to configure best practice.

see here

HOW TO: Add an iSCSI Software Adaptor and Create an iSCSI Multipath Network in VMware vSphere Hypervisor ESXi 4.1

HOW TO: Add an iSCSI Software Adaptor and Create an iSCSI Multipath Network in VMware vSphere Hypervisor ESXi 5.0

(valid configuration also for ESXi 6.0)

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
pchettriIT DirectorAuthor Commented:
I have exact recommended setup as suggested in your article and it was working for last 6 months until I upgraded. The only thing strange is vmware found logs a week before it was upgraded

I two NICS bonded together on in Vswitch which is also bonded with LACP in Brocade switch physically
 In Vswitch it has three VM kernel port.

Two VM kernel port with ISCSI and vmotion enabled and followed active and unused setup with each other and they are in same network subnet (
One is standard vkernel (mangament network) with different IP subnet (
Vmnetwork with (

All of them created in single vswitch with two adapter. following article. ISCSI with same network is bound together and rest of them in different network. Only network that is common without bonding is vmnetwork and management network.

Configurations with more than one vmknic interface on the same IP subnet should be avoided, unless the vmknics on the same subnet are bound together using iSCSI port-binding or configured for Multi-NIC vMotion.
For more information about Multiple-NIC vMotion, see Multiple-NIC vMotion in vSphere 5 (2007467).
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
LACP is NOT supported on ESXi with Standard vSwitches.

We have  Data ONTAP 8.2.3 7-Mode       and  Data ONTAP 8.2.2 7-Mode, using with ESXi 6.0 with no issues.
IT Pros Agree: AI and Machine Learning Key

We’d all like to think our company’s data is well protected, but when you ask IT professionals they admit the data probably is not as safe as it could be.

pchettriIT DirectorAuthor Commented:
Are you using ISCSI or NFS on ONTAP 8.2.3 7 mode? Netapp customer support determine only on the basis on this tool that I have attached. The only thing it does is shows ISCSI protocol as grayed out when I select ESX 6 with ONTAP 8.2.2
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
We are using iSCSI and NFS, but most of our clients, are now favouring NFS, and also based on NetApp FAS design, NFS is lower overhead, because there are less "stacks" than using iSCSI, especially now there is the VAAI plugins for NFS.

As the FAS filer were orignally developed around NFS, so less layers.
pchettriIT DirectorAuthor Commented:
Hi Andrew,

Does NFS datastore support MTU 9000 transfer?
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Yes, we use it with MTU 9000 (Jumbo Frames).

Jumbo Frames enabled on VMKernel Portgroups, Storage Switches, and we run two different VLANS (VIFS) into our Filer Heads, VLAN for iSCSI and VLAN for NFS.

So storage protocols, are isolated across the switches.

We used to use iSCSI with NetApp Filers for years, since 2004, when NFS licenses you had to pay for, and then we have been switching now to NFS.

Not many clients left now....
pchettriIT DirectorAuthor Commented:
I was going through the article

HOW TO: Add an iSCSI Software Adaptor and Create an iSCSI Multipath Network in VMware vSphere Hypervisor ESXi 5.0

and I noticed a "Bind with VMkernel network adaptor".  I noticed one of my host does not have  NIC added to this dialog box. Would it be an issue for storage?
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
If you have not bound iSCSI to a network interface, the interface cannot be used for iSCSI traffic.

So if using multipath, it will not function as expected.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.