HP c-Class Vmware manual Transferring the VSL files to the ESX or ESXi server

Page 14

Transferring the VSL files to the ESX or ESXi server

You must transfer the firmware file to the ESX or ESXi host. Depending on your ESX or ESXi version and your preferred installation method, you might also have to transfer the two bundle installation files to the host. HP recommends transferring all the files at this point and then choosing the installation method later.

With any method that you select for transferring the files, HP recommends saving the files to a datastore on the host. The example paths to the bundles and firmware in this guide show them located in a bundles directory on a datastore:

/vmfs/volumes/<datastore>/bundles/

Where datastore is the name of the datastore where the files are saved.

Transfer methods

You can transfer the files using one of several methods, including:

vSphere Client

vCLI vifs command

SCP (using SSH)

You can copy the files to the host from your remote system or from an NFS share.

vCLI example

To transfer files to the ESX or ESXi host using vCLI:

1.On your remote machine, be sure you have downloaded the appropriate files, and record the file locations.

2.Choose an available datastore with at least 200MB of available storage on the hypervisor that you will use to temporarily store the bundles.

3.Create a directory in the datastore named bundles using the vifs remote command: vifs --server <servername> --mkdir "[<datastore>]bundles"

The brackets ([]) and quotes ("") are required. Substitute your datastore name for the <datastore> variable.

IMPORTANT: When using the vCLI on a Windows operating system, many of the commands are slightly different. Most of the commands end with .pl. Throughout this guide, when you run the vCLI on a Windows operating system, you must add .pl to the command. For a Windows operating systems, this command is:

vifs.pl --server <servername> --mkdir "[<datastore>]bundles"

4.Use the following example command line to transfer each file individually to the bundles directory of the datastore:

vifs --server <servername> --put "<path-on-local-machine>/<filename>" "[<datastore>]bundles/<filename>"

Where <filename> is the full filename, For example: o iodrive_<version>.fff

o cross_vmware-esx-drivers-block-iomemory-vsl_<version>.offline-bundle.z ip

o iomemory-vsl_<version>.offline-bundle.zip.

Software installation 14

Image 14
Contents HP IO Accelerator Version 3.2.3 VMware ESX ESXi User Guide Page Contents Module parameters Contents summary About this guideProduct naming IntroductionOverview Performance attributes IO Accelerator capacity 320GB 640GB Models AJ878B BK836ARequired operating environment Supported firmware revisionsSupported hardware 192 096 048 12.4 GB 024 11.6 GB 15.7 GB 24 GB Introduction Before you begin ESX command-line installation Software installationCommand-line installation ESXi command line installationIomemory-vsl-version.zip Installation overviewDownloading the VMware ESXi driver Vifs.pl --server servername --mkdir datastorebundles Vmfs/volumes/datastore/bundlesTransferring the VSL files to the ESX or ESXi server Installing the VSL on ESXi 5.0 using vCLI Installing the VSL on ESXiInstalling the VSL on ESX or ESXi Installing the VSL on ESXi 5.0 using the command lineUpgrading the firmware using ESX Installing the VSL on ESX or ESXi 4.x using vCLIUpgrading procedure Upgrading device firmware from VSL 1.x.x or 2.x.x toIomemory-vsl block driver for ESX/ESXi Fio-bugreportIomemory-vsl block driver for ESXi Fio-update-iodrive iodriveversion.fff Enabling PCIe powerConfiguring the device to support VM disks Modifying a VMware resource pool to reserve memory Using the IO Accelerator as swap with ESX Command-line utilities for Tech Support Mode MaintenanceMaintenance tools Management utilities for ESXiEnabling PCIe power override Command line Purpose UtilityEnabling the override parameter Enabling the driver Common maintenance tasksDisabling the driver 1149D0969,1159E0972,24589Enabling auto attach Uninstalling the IO Accelerator driver packageDisabling auto attach # esxcfg-module -s autoattach=1 iomemory-vslUnmanaged shutdown issues Disabling Dvfs Performance and tuningIntroduction to performance and tuning Limiting Apci C-statesFio-attach UtilitiesUtilities reference Fio-attach device options Fio-beaconFio-bugreport Fio-beacon device optionsFio-bugreport Fio-detach device options Fio-detachFio-format Fio-pci-check Fio-format options deviceFio-status device options Fio-statusFio-pci-check options Utilities Fio-update-iodrive Geometry and capacity information not available appearsFio-update-iodrive options iodriveversion.fff Utilities Health metrics Monitoring IO Accelerator healthNand flash and component failure Health monitoring techniquesFlashback substitution events Esxcfg-module --server server-name iomemory-vsl -g Using module parametersModule parameters Working with IO Accelerators and VMDirectPathIO Using products with multiple devicesVMDirectPathIO For more information Subscription serviceResources HP contact information Support and other resourcesBefore you contact HP Customer Self RepairRéparation par le client CSR Riparazione da parte del cliente Reparaciones del propio cliente Reparo feito pelo cliente Support and other resources Support and other resources Support and other resources Regulatory information Safety and regulatory complianceWarranty information Acronyms and abbreviations Vmfs Documentation feedback Index Transferring VSL files