Skip to main content
NetApp Knowledge Base

VPD midplane compare test fails with "midplane_compare test failure occurred (status=14)"

Last Updated:

Applies to

  • Data ONTAP (all versions)
  • DS224x
  • DS424x
  • DS212C
  • DS460C


  • VPD midplane compare test as part of VPD troubleshooting results in a VPD read failure
  • A message like the below will be seen 

     Cluster::*> system node run -node Node-01 -command sasadmin expander_cli 0a.10 'vpd midplane_compare'
Could not read VPD id 17 (bus=2 addr=00h off=0)!
midplane_compare test failure occurred (status=14)

  •  A "VPD midplane compare" failure can occur in one of two scenerios:
  1. Both VPD EEPROMs are readable BUT the contents of one of them is corrupt, or;
  2. One of the VPD EEPROMs is not readable.



Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.


  • Was this article helpful?