HP Matrix Operating Environment 7.2 Update 1 Infrastructure Orchestration User Guide

While a request is paused, the administrator can make the necessary modifications to the
environment to make the network available for allocation. When the request continues, another
attempt is made to allocate the network. The service request continues only when the network
resources are available.
VLAN carving allows a single template definition to be used by multiple organizations, each having
its own VLAN that may not yet be defined until the request is submitted.
For example, a subset of the organizations in the datacenter may want to use a network named
org-prod-Y-<org name> network:
• A defined IO template with an attribute-based network with “Allocation name Hint” =
“org-prod-Y-“ is made available to potentially all organizations.
• The organization “Marketing” creates a service from this template. The request is unable to
find an “org-prod-Y-*” network in the organization network pool, and the service request
pauses.
• The administrator is notified of the pause, and creates a “org-prod-Y-Marketing” subnet and
assigns this network to the organization network pool.
• The administrator resumes the service request.
• The service request attempts to allocate networks and finds the newly defined network in the
organization network pool and allocates it to the service.
• Subsequent service request using “org-prod-Y-*” will use the “org-prod-Y-Marketing” network.
• Only organizations that create the service with the “org-prod-Y-“ IO template will have subnets
created for them.
VLAN carving is also used when the available IPs for a subnet are exhausted. Any subsequent
request for that network will pause while the administrator adds additional IPs to the subnet.
Configuring trunk and VLAN networks
To define trunk and VLAN networks, perform the following steps. For information about support
for Hyper-V VLAN tagging, see “Configuring trunk and VLAN networks to enable support for
Hyper-V VLAN tagging” (page 70).
1. Define Virtual Connect networks using Virtual Connect Manager.
• Tunnel mode: Define each tunnel trunk in VC, which passes tagged packets unmodified.
(There is no need to inform VC which VLANs are carried by the tunnel.)
• Map mode: Define all networks in VC. Each VLAN carried by an uplink is explicitly
defined as a VC network. No VC network carries packets from multiple VLANs.
2. Discover Virtual Connect networks by refreshing the infrastructure orchestration console
Networks tab.
• VC networks are displayed as “Physical” in the Type column.
• VC networks that are configured as “tunnel VLAN tags” are displayed as “Trunk, Physical”
in the Type column.
68 Installation and configuration