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.
1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next. The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance. 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click Next to display the App…
The previous post talks about vSphere Integrated Containers and their benefits. The VIC offers a robust solution that enables the vSphere environment to quickly get containers up and running in their current vSphere infrastructure. This environment can be useful for migrating current apps to containers or for in-house development. Architecture
In a traditional container environment, containers run as threads within the container host. vSphere Integrated Containers leverage the native constructs of vSphere for provisioning container-based applications into its own container running its own very minimal Linux kernel with just enough code to run a Docker image, thus preventing any issue with containers being accessed from other containers by pushing isolation of the container down to the hypervisor layer that is much better at handling this type of isolation.
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