Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 5 results
    • Manual mNode deployment fails on ESXi 6.x due to expired certificate
      https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/Manual_mNode_deployment_fails_on_ESXi_6.x_due_to_expired_certificate
      Manual mNode deployment fails on VMware ESXi 6.5 and 6.7 due to "Invalid Certificate". When deploying mNode manually via vCenter 6.5 and 6.7, the "Publisher" field of the "Review details" pane indicat...Manual mNode deployment fails on VMware ESXi 6.5 and 6.7 due to "Invalid Certificate". When deploying mNode manually via vCenter 6.5 and 6.7, the "Publisher" field of the "Review details" pane indicates that the certificate is invalid. If you use the Flash client, the OVA will be blocked from deploying. You do not have the option to accept the OVA as untrusted and proceed anyway. If you use the HTML5 client, you will not have any issue deploying.
    • NetApp Element Plug-In for VMware vCenter Server (VCP) is not visible in vSphere HTML5 web client
      https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/NetApp_Element_Plug_In_for_VMware_vCenter_Server_VCP_is_not_visible_in_vSphere_HTML5_web_client
      Applies to NetApp Element Plug-In for VMware vCenter Server (VCP) NetApp HCI VMware vSphere 6.7 Update 2 (all builds and releases in U2) 6.7u2 6.7u2a 6.7u2b Issue When upgrading or installing vCenter ...Applies to NetApp Element Plug-In for VMware vCenter Server (VCP) NetApp HCI VMware vSphere 6.7 Update 2 (all builds and releases in U2) 6.7u2 6.7u2a 6.7u2b Issue When upgrading or installing vCenter 6.7 U2 (including Update 2a and 2b) and subsequently registering the NetApp Solidfire/HCI vCenter plugin (VCP), the plugin does not appear in the HTML5 web client.
    • Upgrading vCenter Server from 6.5 to 6.7 fails at Pre-upgrade check with the alert: The source machine hostname resolves to IPV6 address(es)
      https://kb.netapp.com/Legacy/NetApp_HCI/OS/6.5_to_6.7_fails_at_Pre-upgrade_check_with_the_alert
      Applies to Source vCenter Server Version: 6.5 Target vCenter Server Version: 6.7 vCenter Server IPV6 not configured Issue During the upgrade process of vCenter 6.5 to 6.7, the installer will not proce...Applies to Source vCenter Server Version: 6.5 Target vCenter Server Version: 6.7 vCenter Server IPV6 not configured Issue During the upgrade process of vCenter 6.5 to 6.7, the installer will not proceed at the Pre-upgrade check phase and it's unable to proceed with the upgrade. Example output and alert can be found under Additional Information section.
    • vVol datastores (building blocks) become inaccessible
      https://kb.netapp.com/data-mgmt/OTV/VSC_Kbs/vVol_datastores_building_blocks_become_inaccessible
      Applies to vSphere API for Storage Awareness (VASA) 9.7 NetApp Element software Issue vVols building blocks (datastores) suddenly become inaccessible, A review of the VASA provider indicates that the ...Applies to vSphere API for Storage Awareness (VASA) 9.7 NetApp Element software Issue vVols building blocks (datastores) suddenly become inaccessible, A review of the VASA provider indicates that the service is running normally as shown below and its correctly registering in vCenter GUI as shown below A review of the space on VP also slows that, there is sufficient space under /opt vCenter shows the vVol as 'inaccessible':
    • vVOL datastore are showing as inaccessible or 0 bytes
      https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/vVOL_datastore_are_showing_as_inaccessible_or_0_bytes
      2018-02-13T16:29:07.853Z info vvold[FFE92B70] [Originator@6876 sub=Default] Initialize: Failed 2018-02-13T16:29:20.085Z info vvold[FFA8BB70] [Originator@6876 sub=Default] Came to 2018-02-13T16:29:37.8...2018-02-13T16:29:07.853Z info vvold[FFE92B70] [Originator@6876 sub=Default] Initialize: Failed 2018-02-13T16:29:20.085Z info vvold[FFA8BB70] [Originator@6876 sub=Default] Came to 2018-02-13T16:29:37.875Z info vvold[FFE92B70] [Originator@6876 sub=Default] 2018-02-13T16:29:37.875Z info vvold[FFE92B70] [Originator@6876 sub=Default] Initialize: Failed 2018-02-13T16:29:40.085Z info vvold[FFA4A380] [Originator@6876 sub=Default] Came to