HP Matrix Operating Environment support of VMware VXLAN environments

Sign up for updates
hp.com/go/getupdated
Share with colleagues
Rate this document
© Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties
for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed
as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Trademark acknowledgments, if
needed.
5 | 5900-3367, January 2014
2. Ensure service templates are created using the correct networks to avoid connectivity issues. If a service is
provisioned using a VXLAN which is not part of the network scope, the VMs will have connectivity issues. Thus,
the architect defining the service template in Matrix infrastructure orchestration Designer has to choose
networks carefully. If the administrator or user is customizing networks at the time the service is created, the
network should be chosen carefully. It is possible to disable network customization if desired.
3. Clusters which are not part of VXLAN scope can also see the port groups of VXLAN from vCenter. VMs must be
created using ESX hosts or clusters which are part of VXLAN scope, otherwise the VMs created will have network
connectivity issues. Administrators should ensure suitable grouping of ESX hosts/clusters into server pools.
4. Matrix infrastructure orchestration ESXi cluster provisioning does not support ESX host creation configured with
VXLAN. The necessary dvSwitch and the respective networks configurations for VXLAN are not created at
runtime and post vShield Manager settings are required after ESXi deployment. Matrix can create ESXi hosts
without VXLAN, and manual post configurations can be done to enable VXLAN in the provisioned server.
5. The VXLAN solution has only been tested for IPv4.
Setting up the VMware VXLAN environment
The document does not describe detailed steps to deploy a VMware VXLAN environment, but does cover some of the
main steps (with screenshots). A complete VMware VXLAN deployment guide can be found at
http://www.vmware.com/files/pdf/techpaper/VMware-VXLAN-Deployment-Guide.pdf
The following environment was used for scenarios discussed in this document.
 VMware ESXi 5.1 [Minimum two NICs with dvSwitch configured using the second NIC]
 VMware vSphere 5.1
 VMware vShield Manager 5.1.2 (VMware vCloud Networking and Security 5.1.2)
 Physical network was not configured with VLAN
Configuring VMware vShield Manager
The important steps to install and configure vShield Manager are described below. It is assumed that ESXi hosts, vCenter
are installed and configured. Hosts are added to vCenter. Latest vShield Manager OVA template can be downloaded
from https://my.vmware.com/web/vmware/downloads.
1. Deploy the OVA template of vShield Manger in vCenter Server 5.1 and configure it as per the vShield Installation
and Upgrade Guide.