Specify the network interface to be allocated to an L-Server (non-global zone) based on the network resource. Therefore, it is necessary to associate the network resource and the network interface in the global zone in advance.
In the global zone, only one network interface can be associated with the network resource. When there are multiple network interfaces in the global zone, create a network resource for each network interface.
When using exclusive IP settings, the network interface in the global zone must be allocated to only one non-global zone. Only specify the network resources for one L-Server.
Use the VLAN ID as an identifier in order to associate the network resource with the network interface in the global zone. Use different VLAN IDs for each network interface in the global zone.
The VLAN ID is used as an identifier, but VLAN settings are not performed. When VLAN settings are required, configure them in advance.
It is necessary to configure the following settings beforehand.
Check the Network Interface
In VM hosts (global zones) managed with Resource Orchestrator, check that the network interfaces used by VM guests are not being used.
When migrating VM guests (non-global zone) between VM hosts (global zones), check if the source and destination network interfaces have the same name.
When configuring the network interface, if using a server virtualization software other than a Solaris Zone on the same manager, check that a different name from the one used for a virtual switch, a virtual network, or a virtual bridge on the other server virtualization software is used.
Define the Supported Network Interface and VLAN IDs.
Define the supported network interface and VLAN IDs in the virtual network definition file for Resource Orchestrator.
For details on definition file format, refer to "File Format for Virtual Network Definitions".
Create Network Resources
From the GUI:
Create network resources using the VLAN IDs specified in step 2.
In the [Create a network resource] dialog, check the [Use configured virtual switches.] checkbox.
From the Command-line:
Create the XML file that defines network resources.
Define the VLAN ID specified in step 2. in the XML file.
In this case, specify auto="false" in the Network element.
To create the network resource, execute the rcxadm network create command specifying the XML file created in step a.
The network resources are created.
For details on the rcxadm network command, refer to "3.9 rcxadm network" in the "Reference Guide (Command/XML) CE".
For details on the Network element, refer to "15.5 Network Resources" in the "Reference Guide (Command/XML) CE".
File Format for Virtual Network Definitions
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data
[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data
vnetwork_solariscontainer.rcxprop
Describe the network definition file in one line as below:
"Network interface name"=VLAN ID
For the VLAN ID, a value from 1 to 4094 can be specified.
Example
"bge1"=10
Blank spaces before and after equal signs ("=") are ignored.
Describe the network interface name correctly, as the entry is case-sensitive.
Save files using the UTF-8 character code.
When the same VLAN ID is included in a line with a different network interface name, the first occurrence in the file is valid and the lines after it are ignored.
An error occurs during L-Server (non-global zone) creation if the definition of the VLAN ID of the network resource connected to the NIC cannot be found.
