Resource Library

In 2013, VMware announced VMware Virtual SAN (VSAN), which is VMware's native version of Software Defined Storage (SDS). It is simple, easy to setup and managed by user-defined policies. This paper explains VSAN, its basic requirements and how it works.

This vSphere Essentials white paper will give you a basic understanding of some of the concerns or planning points to consider as you get ready to deploy vSphere in your organization. This is a glimpse into some of the essential things to consider for implementing vSphere. This will focus on some of the basics that vSphere administrators run into when installing the latest features and not realizing they still have some older versions implemented.

There are two types of virtual switches available using vSphere, the vSphere Standard Switch and the vSphere Distributed Switch. The vSphere Standard Switch (vSwitch or vSS) resides in and is manually configured and administered on each ESXi host. The vSphere Distributed Switch (dvSwitch or vDS) provides similar functionality but is centralized to vCenter Server and is more featured. This white paper will cover the vDS architecture as well as an overview of many of the different features that are exclusive to the vSphere Distributed Switch.

VMware Horizon 6 was announced in April and began shipping in June 2014, bringing a more unified suite delivering more integration with infrastructure and cloud products and more simplicity for all devices. Along with the numerous updates across the Horizon suite, VMware has transitioned to a more traditional product licensing hierarchy. This paper explores the new licensing model and provides an overview of the new features associated with VMware Horizon 6.

When properly utilized, VLANs and trunks provide flexibility, stability and ease of troubleshooting. This paper provides technical details about VLANs and trunks, along with design options at a basic to intermediate level. Recommendations and commands are included throughout.

Examine fifteen common myths surrounding virtualization, including many that prevent IT administrators (or their bosses) from getting the maximum value from virtualization. This paper is designed to be vendor-neutral; in other words, the basic concepts and advantages are the same whether you choose to use Citrix XenServer, VMware vSphere, Microsoft Hyper-V, or one of the many Linux-based solutions. We'll break the reasons into three broad categories (Cost/ROI, Performance, and Other), allowing you to focus in on a specific area if desired, or you can review the entire white paper for a broader view.

Many people believe that cloud computing requires server (or desktop) virtualization. But does it? We will look at using virtualization without cloud computing, cloud computing without virtualization, and then look at using both together. In each case, we'll look at where each deployment might be most useful, some use cases for it and some limitations.

One of the advantages of vSphere is that you can move a virtual machine from one location to another, across servers, storage locations-even data centers. Physical servers don't have that ability and that can have many implications for disaster recovery, availability, and so forth. This white paper explains why migrations are useful, the methods that vSphere makes available for you to manually move a virtual machine (VM), and how vSphere can automate the process for you in various scenarios.

The methods we have used in the past to secure our networks won’t work for tomorrow’s networks. Cloud-based applications and multi-tenant environments require greater scalability, agility and control. Software-defined networking (SDN), such as that provided by VMware NSX, can deliver a new platform that transforms networking and provides for much more specific control of the security of your data and networked applications.  In this white paper, author Bill Ferguson describes the microsegmentation of security and illustrates how you can use NSX to provide security that works on today’s and tomorrow’s networks.

This white paper describes a technique for defining processes called SIPOC (Suppliers, Inputs, Process, Outputs, and Customers). SIPOC provides a structured way to define the key elements of any process. SIPOC can be used as a means of defining any of the service management processes presented in ITIL® best practices. Furthermore, SIPOC can be used as the preliminary input into the more formal documentation of a process in one of many process design tools.