No matter how sophisticated the technology is , It still takes people !
Subscribe to this blog
Follow by Email
Install the iSCSI initiator
If you’re running an operating system on which the iSCSI initiator software is not installed, execute the file you downloaded and follow the installation instructions . The installer will ask you to decide which components you would like to install.
Choose your installation options. Initiator service— This is the service behind the actual work. Software initiator— The software initiator is the software service that handles iSCSI traffic. Microsoft MPIO Multipathing Support for iSCSI — MPIO is a way that you can increase the overall throughput and reliability of your iSCSI storage environment. See Step 6 for more information about how MPIO can be of benefit.
If you have a target that supports Microsoft’s MPIO (check with your manufacturer), you should enable this option. Otherwise, if your target supports MPIO through the use of a proprietary device-specific module (DSM), obtain that DSM from your array manufacturer and follow the manufacturer’s installation recommendations.
This post is related to the issue what we faced today when we replaced the SSL certificates in our setup. When I launched the web-client and access the update manager tab, I get the message "interface
com.vmware.vim.binding.integrity.VcIntegrity is not visible from class
I started off by
restarting the VMWare vSphere Update Manager Service for the affected vCSA: 1. Log into vCenter
using the email@example.com account. 2. Home - System
Configuration - Services - Restart
This did not resolve
my issue... And we tried restarting all the services by SSH/Console into the
affected server and run the following commands: service-control
--start --all Still no luck. Make sure the certs are applied and it gets reflected in the config file. ( verify if the thumbprint matches) root@homelab71 [
/usr/lib/vmware-updatemgr/bin ]# pwd/usr/lib/vmware-updatemgr/bin root@homelab71 [
/usr/lib/vmware-updatemgr/bin ]# ./updatemgr-util config -g | less
Before a running virtual machine can be migrated from one host to another there are some mandatory requirements that must first be met:
Hyper-V 2008 R2 must be deployed on both hosts. The first version of Hyper-V does not support live migration.
Source and destination Hyper-V hosts must be configured as a Failover cluster with shared storage enabled.
Source and destination systems must be using shared storage (i.e. via SAN or iSCSI configurations)
Source and destination systems must be running processors from the same manufacturer. It is not, for example, possible to migrate a virtual machine from an Intel based host to one containing an AMD CPU.
The virtual machine on which the migration is to be performed must be configured as Highly Available and to use Cluster Shared Volumes.
The virtual machine's Automatic Start Action setting must be set to do Nothing.
All Hyper-V hosts in the Failover cluster must be configured to boo…