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.
17 | 5900-3367, January 2014
Every VMware VXLAN Network created in vShield Manager creates a separate dvPort Group on each dvSwitch as shown
in the screenshots below.
For the VMware VXLAN Network (VXLAN-Wire1) created in vShield Manager there are two dvPort Groups created in
vCenter (vxw-dvs-243-virtualwire-8-sid-5000-VXLAN-Wire1 on dvSwitch-Cluster-1 and vxw-dvs-246-virtualwire-8-sid-
5000-VXLAN-Wire1 on dvSwitch-Cluster-2).
Configuring Networks in Matrix OE
For the VMware VXLAN Network (VXLAN-Wire1) created in vShield Manager there are two networks visible in Matrix
infrastructure orchestration (vxw-dvs-243-virtualwire-8-sid-5000-VXLAN-Wire1 and vxw-dvs-246-virtualwire-8-sid-5000-
VXLAN-Wire1), since every dvPort Group is listed as a new Network in Matrix infrastructure orchestration. Both the
Networks in Matrix OE should be configured properly with appropriate values (such as DNS, Gateway, VLANs, DHCP,
etc.). When using static IPs, separate IP ranges should be defined for each network.