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.
First, we will install the AD LDS Instance: 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 N
Steps to configure the vCenter Server to generate SNMP traps: A.In the Home page of vSphere Client B.Select vCenter Server Settings C.Select SNMP configuration D.Enable one of the SNMP receivers E. Provide the details for : Receiver URL : Provide the host name of the Management Server (target SNMP server / monitoring tool) which will be connected to the VMware vCenter Server. (VMware vCenter Server sends the SNMP traps to this Management Server) Configure port 162 as the SNMP port. Community String: Provide community string (default string is "public") SNMP versions v1/v2/v3 are supported That is all that is needed for the configuration. Now you need to configure alarm for generating SNMP traps in the vCenter server. When ever there is a change in the environment ( host state change, VM state change ,etc) the trigger will be generated and send an alert to the monitoring server. Configure the Alarms After you have setup the external SNMP server, v
In our previous posts , we saw the option to deploy the VCH using CLI utility, vSphere client etc. In this post, we see an option to automate the VCH deployment using vRealize Automation ( vRA) Background: The current automated world requires the seamless and fastest deployment of its infrastructure. VMware vSphere Integrated Containers gives developers an essential tool for streamlining the process of building and running containerized applications in production. The deployment of VCH is done through various methods as we see in our previous posts. But in this post, we are going to see how to automate the VCH deployment and the first VCH in few mouse clicks. By using the service catalog in vRealize Automation to provision Virtual Container Hosts on-demand as a ticketless offer, you can make your developers self-sufficient. The vRealize Automation 7.4 and later versions support provisioning and management of Virtual Container Hosts(VCH) for running vSphere Integrated Containe