Check the following:
The configuration for the admin and public LANs has been designed
The network environment for the admin LAN is configured
A global zone is already connected to the admin LAN
NICs to be used in the non-global zones are already designed
The IDs for distinguishing the NICs used in the non-global zone have been designed.
When Using IBP
When using virtual L-Servers, after creating the IBP uplink sets to use for the public LAN and admin LAN, connect the IBP uplink sets to the VM host. It is not necessary to use the same name for the uplink set and the name of the network resource.
Designing NICs to be Used in Non-Global Zones
When creating L-Servers using Resource Orchestrator, create a non-global zone using exclusive IP settings.
When associating already created non-global zones with L-Servers, there are no restrictions on the network configurations.
When NICs for L-Servers are DHCP, place the DHCP servers, and configure the settings to allocate IP addresses to L-Servers.
Design IP addresses to allocate to L-Servers that do not overlap with IP addresses that are not managed in Resource Orchestrator.
[Solaris Zones (Solaris 10)]
For the NICs to be used by L-Servers, design them so those NICs will not be used in the global zone or non-global zones that have already been created.
When migrating VM guests (non-global zone) between VM hosts (global zones), perform design so a NIC with the same name is used on the source and destination.
Also, design the IDs for distinguishing the NICs used by the L-Server. This value corresponds to the VLAN ID of the network resource, so use a value between 1 and 4094.
The NIC hardware configurations must be the same on servers in the same pool.
