Pivot3 X5-6500 - Uninstall Plugin; Unregister Plugin Using Installer File for Linux

Setup & User Guide
| 80
DOC-246-GDE-Pivot3 Acuity 2.3 Setup & User Guide-v1.0.docx
Log in to the vSphere Web Client Pivot3 Plugin.
a. Navigate to Provisioning > Data Services > Host Access Group.
b. Select the Host Access Group associated with the volume(s) backing the applicable datastore(s) for the vPG.
c. Modify the selected Host Access Group and add the iSCSI Name found in step 1d.
Use the Plugin’s Modify Membership wizard to add the new Acuity-based X5 node to the vPG. The vPG modification
process will automatically add the necessary iSCSI addresses to the host’s iSCSI software adapter, and the software
will automatically start a storage rescan on the ESXi host.
For vPGs with N5 Storage
Log in to vCenter Web Client on the new host and locate the host’s iSCSI Name.
a. Navigate to Home > Hosts and Clusters.
b. Select the new ESXi host in the Navigator panel and navigate to Manage > Storage > Storage Adapters.
c. Locate the iSCSI software adapter section and click on the vmhba.
d. The web client lists the ESXi host’s iSCSI Name in the details within the vmhba’s Properties panel.
In the vCenter Web Client, add the N5 SAN addresses to the host’s Dynamic Discovery list.
a. Navigate to Home > Hosts and Clusters.
b. Select the new ESXi host in the Navigator panel and navigate to Manage > Storage > Storage Adapters.
c. Locate the iSCSI software adapter section and click on the vmhba.
d. Select the Targets tab.
e. Select the Dynamic Discovery tab and press Add.
f. One at a time, enter all SAN addresses for the N5 node in the box labeled iSCSI Server.
Log in to the N5 Web Application.
a. Navigate to Provision > Host Access Groups.
b. Select the Host Access Group associated with the volume(s) backing the applicable datastore(s) for the vPG.
c. Modify the selected Host Access Group and add the iSCSI name found in step 1d.
In the vSphere Web Client Pivot3 plugin, use the Modify Membership wizard to add the new Acuity-based node to the
vPG.
Perform a manual rescan of the ESXi hosts, and the new datastore should be visible.
BEST PRACTICE: To remove a ghosted datastore, shut down all associated VMs and reboot the affected host.