HP Matrix Operating Environment 7.3 Update 1 Installation and Configuration Guide for Provisioning with Virtual Resources

Table 3 VLAN tagging support using promiscous.switch.compatibility
Method of VLAN tagging support used
by IO with this settingSet if...
Default value of
promiscous.switch.compatibility
HP NCU is used to create vNICs for
each VLAN (6.2/6.3 method)
IO is upgraded to 7.0 and the
previous release implemented Hyper-V
VLAN tagging support
TRUE
Hyper-V VLAN discovered vSwitch is
marked as trunk in IO; VLANs carried
IO is upgraded to 7.0 and the
previous release did not implement
Hyper-V VLAN tagging support
FALSE
by the Hyper-V virtual trunk are defined
with VLAN IDs (7.0 method)
Hyper-V VLAN discovered vSwitch is
marked as trunk in IO; VLANs carried
IO 7.0 is a new installationFALSE
by the Hyper-V virtual trunk are defined
with VLAN IDs (7.0 method)
Perform the following steps in the infrastructure orchestration console to enable support for VLAN
tagging. This is the 7.0 or later method.
1. Discover virtual networks by refreshing the infrastructure orchestration console Networks tab.
2. On the Networks tab, select the 802.1Q network carrying multiple VLAN IDs and click Edit
Network.
3. Select the Trunk tab.
4. Check the Trunk checkbox, and click Save.
5. Define the VLANs that can be carried by the Hyper-V virtual trunk network.
a. On the Networks tab, click Create Network.
b. Specify a VLAN ID, and set Network Address, Network Mask, Default Gateway, MS
Domain, and WINS Servers for that VLAN ID by clicking the appropriate tab and filling
in the information.
c. Click Save.
Configuring software resources
Confirm that the software resources you intend to use in Matrix OE service templates are recognized
by Matrix infrastructure orchestration. Click the Software tab and review the contents listed; you
may select each row and inspect the details provided.
VM templates
Confirm that the VMware vCenter or Hyper-V VM templates you intend to use in Matrix OE service
templates are recognized by Matrix infrastructure orchestration.
By default, all templates are available to all users at the service provider level. To change this, see
“Enabling template assignment restriction for specific service provider level users” (page 107).
For public cloud bursting to Savvis, you must maintain a local VMware vCenter or Hyper-V template
for each template that will be uploaded to Savvis. Any change to the Matrix OE recognized
template location must be kept in sync with the configuration files that map the local (proxy) software
choices to Savvis deployment images. In preparation of bursting to Savvis confirm that the VM
templates you intend to map to Savvis templates are recognized by Matrix infrastructure
orchestration.
Enabling template assignment restriction for specific service provider level users
To enable template assignment restriction for specific service provider level users, follow these
steps:
1. Open the hpio.properties file in c:\Program Files\HP\Matrix infrastructure
orchestration\conf\.
Configuring Matrix infrastructure orchestration resources 107