Online VMware Training

With the release of vCheck 6 and the easy to adapt HTML framework I have a very easy way to do just this, with a few simple changes to the plugins we can easily add any product into the reporting framework.

IgniteVM is used by database administrators to ensure service and availability of database instances running in VMware virtual machines. It shows the DBA what the database response time delays are, and what the contributing causes are at the instance, virtual machine, and physical layers. IgniteVM is a 24/7 monitoring tool, based on industry best practice Performance Intelligence and Wait-Time analysis methods. IgniteVM supports Oracle, SQL Server, DB2 LUW and Sybase databases across all operating systems, running in VMware vCenter Server or stand-alone ESX/ESXi host environments.

AlarmVM is used by VMware Administrators to detect problems in the VMware environment and proactively notify administrators. alarmVM is a 24/7 alarm monitoring tool that detects problems in VMware objects, including VMs, hosts, clusters, datastores and vCenter Servers. When alarm conditions are detected, alarmVM notifies VMware Administrators via email and/or SNMP trap.Key Benefits:alarmVM can be installed and set up to monitor a VMware environment in less than 20 minutes.It automatically activates out-of-the-box alarms so an entire VMware environment is being monitored simply by registering a vCenter Server.By default, alarmVM notifies all configured contacts about each alarm, eliminating the need to set up contacts for each alarm.Using inheritable alarm policies, it is easy to change default alarm behavior on entire sets of vSphere objects (e.g. all VMs in a datacenter or all VMs in a folder).A 30 day history of alarms is kept, so you can see what happened in the past. During this period, alarmVM shows graphs for metric-based alarms with the underlying detailed data that would not be available in vSphere Client.alarmVM shows how alarms are trending so you can see if trouble is easing or mounting in your VMware environment.

The virtual machines in a vApp can connect to vApp networks (isolated or routed) and organization networks (direct or fenced). You can add networks of different types to a vApp to address multiple networking scenarios. Select the Networking tab in a vApp and select the Show networking details check box to view a list of the networks that are available to the vApp. Virtual machines in the vApp can connect to these networks. If you want to connect a virtual machine to a different network, you must first add it to the vApp.A vApp can include vApp networks and organization networks. A vApp network can be isolated by selecting None in the Connection drop-down menu. An isolated vApp network is totally contained within the vApp. You can also route a vApp network to an organization network to provide connectivity to virtual machines outside of the vApp. For routed vApp networks, you can configure network services, such as a firewall and static routing.There's also a possibility to connect a vApp directly to an organization network. If you have multiple vApps that contain identical virtual machines connected to the same organization network and you want to start the vApps at the same time, you can fence the vApp. This allows you to power on the virtual machines without conflict, by isolating their MAC and IP addresses.It's also possible configure certain vApp networks to provide firewall services. Enable the firewall on a vApp network to enforce firewall rules on incoming traffic, outgoing traffic, or both. When you enable the firewall, you can specify a default firewall action to deny all incoming and outgoing traffic or to allow all incoming and outgoing traffic. You can also add specific firewall rules to allow or deny traffic that matches the rules to pass through the firewall. These rules take precedence over the default firewall action.

The Cisco Nexus 1000V is compatible with any upstream physical access layer switch that is Ethernet standard compliant, including the Catalyst 6500 series switch, Cisco Nexus switches, and switches from other network vendors. The Cisco Nexus 1000V is compatible with any server hardware listed in the VMware Hardware Compatibility List (HCL). Cisco and VMware jointly designed APIs that produced the Cisco Nexus 1000V. The Cisco Nexus 1000V is a distributed virtual switch solution that is fully integrated within the VMware virtual infrastructure, including VMware vCenter for the virtualization administrator. This solution offloads the configuration of the virtual switch and port groups to the network administrator to enforce a consistent data center network policy. In this release Java applications are introduced for VSM and VEM installation.

When creating a database only use capitols even the username and the password need to be in capitols Also use the fully qualified domain name as a database server, don't use IP-addresses. For configuring vCenter information, scroll down and notice the vCenter configuration information that is necessary. It is very important that the vCenter Server Address field is correctly populated. If you have used IP addresses for all site pairing activities, continue to use IP addresses in this location. If your SRM sites were paired with host names or fully qualified domain names, it is important that you do the same at this location as you did when pairing the sites. VRMS requires naming consistency throughout the process in order to function correctly. Enter the vCenter Server Address for the site you are currently using, which should be the protected site (Site A) vCenter. Click on Generate and Install an SSL Certificate after all the information is filled out.

vSphere Replication (VR) uses replication technologies included in ESX Servers with the assistance of virtual appliances to replicate virtual machines between sites. VR is provided by vSphere Replication Servers (VR Servers or VRS). VR Servers are managed by the vSphere Replication Managment Server (VRMS). Both VRMS and VR Servers are virtual appliances. VRMS provides a way to manage VR Servers across multiple hosts. If you are using VR, you must establish at least one vSphere Replication Server and exactly one VRMS at the recovery site. To enable replication in both directions, you must deploy exactly one VRMS at each site and at least one VRS at each site. You may want to create multiple VR Servers at each site if multiple servers are required to meet your load balancing needs for replication of virtual machines. Each VRMS must be registered with a corresponding vCenter Server. For example, the primary site VRMS must be registered with the primary site vCenter Servers.Both the VRMS and VRS appliances provide a virtual appliance management interface (VAMI). These interfaces can be used to configure the VRMS database, as well as network settings, public-key certificates, and passwords for the appliances. Before using VR, you need to configure the VR infrastructure including having managed IP defined in runtime settings at both sites and having a VRMS database installed. This video provides useful guidance to help ensure you complete the installation and configuration process correctly. When installing SRM, be certain to select the VR option. If you have installed SRM and want to add VR, you can add that option by running the installer again. So, here are the steps for configure-ring vSphere SRM Replication for a Single Virtual Machine.1. On the vSphere Client Home page, click VMs and Templates. 2. Browse the inventory to find the single virtual machine to be replicated using VR. Right-click the virtual machine and click vSphere Replication.3. In the Replication Settings page, configure general replication settings. These settings include the disk file location to which the virtual machine is replicated on the recovery site, how often the virtual machine is replicated, and how the guest OS is quiesced. Use the Recovery Point Objective (RPO) slider or enter a value to configure the maximum amount of data that can be lost during the recovery. The available range is from 15 minutes to 24 hours. For example, a recovery point objective of one hour seeks to ensure that the virtual machine loses no more than one hour of data during the recovery. For smaller RPOs, less data is lost in a recovery, but more network bandwidth is consumed keeping the replica synchronized. The available quiescing types are determined by the virtual machine's operating system. Microsoft Volume Shadow Copy Service (VSS) quiescing is supported for Windows virtual machines running Windows XP or later. Linux does not support quiescing. If no target file location is specified or if you want to override the default determined by the datastore mappings, click Browse to select a target location for the virtual machine.

In this video I’ll show you how SDD storage is detected by the ESXi host after adding a new datastore. You will also learn how to configure VMware ESXi host swapping and redirecting virtual machine swap files to solid state storage.

VMware vCenter Server allows you to centrally manage hosts from either a physical or virtual Windows machine, and enables the use of advanced features such as vSphere Distributed Resource Scheduler (DRS), vSphere High Availability (HA), vSphere vMotion, vSphere Storage vMotion, and vSphere Auto Deploy. You can install vCenter Server in a Microsoft Windows virtual machine that runs on an ESXi host. Deploying the vCenter Server system in the virtual machine has the following advantages:- You can provide high availability for the vCenter Server system by using vSphere HA.- You can migrate the VM containing vCenter from one host to another.- You can create snapshots of the vCenter Server virtual machine.- Rather than dedicating a separate server to the vCenter Server system, you can place it in a virtual machine running on the same host where your other virtual machines run.This video will show you how to install VMware vCenter Server 5.0 in a virtual machine 13 simple steps.

This quick start video provides a simplified, step-by-step set of instructions for creating a new virtual machine on the StratoGen vCloud platform. The StratoGen vCloud platform is built upon VMware vCloud Director 1.5. This video is a supplement to the vCloud director 1.5 user manual which provides comprehensive information about the platform.