ROR provides the function for connection with virtual NICs, for virtual switches created on OVM for SPARC.
Manually perform virtual switch settings on OVM for SPARC in advance.
Use a different VLAN ID for each virtual switch on OVM for SPARC to connect the virtual switches created on OVM for SPARC with virtual NICs.
Point
When a virtual L-Server connected to the following network resources is created, the VLAN ID of the network resource is set for the pvid of the virtual NIC.
A virtual NIC connected to a public LAN network resource
A virtual NIC connected to the admin LAN network resource of a subnet other than the admin LAN subnet used by the ROR manager for control domain management
Configure the virtual switch so that the L-Server can communicate using the virtual NIC with the pvid configured.
It is necessary to configure the following settings beforehand.
Create Virtual Switches on OVM for SPARC
The virtual switch must be created on the VM host, in order to connect the L-Server to the network.
Create a virtual switch with the same name (including upper and lower case characters) for all VM hosts comprising the cluster.
This enables migration of VM guests between VM hosts.
When configuring a virtual switch on OVM for SPARC and server virtualization software other than OVM for SPARC is being used with the same manager, set a different name from the one used by the virtual switch, virtual network, and virtual bridge on the other virtualization software.
For details on how to create virtual switches on OVM for SPARC, refer to the OVM for SPARC manual.
Configure a Virtual Switch VLAN on OVM for SPARC
Configure a vid for each virtual switch to enable the L-Server to perform bidirectional communication using the tagged VLAN via virtual switches. It is not necessary to configure vid for the virtual switches only used for communication between Resource Orchestrator and the control domain.
Configure Virtual Switch Communication on OVM for SPARC
Right-click the LAN switch blade in the server resource tree, and select [Modify]-[Network Settings] from the popup menu.
Configure LAN switch blades to enable communication using the tagged VLAN between virtual switches created on OVM for SPARC using the same name.
The ROR console can be used for VLAN configuration of LAN switch blade external ports.
For details, refer to "5.4.4 Configuring VLANs on LAN Switch Blades" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Define the Virtual Switch Created on OVM for SPARC and the VLAN ID
Define the virtual switch created on OVM for SPARC and the VLAN ID 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 steps 2 and 3. In the [Create a network resource] dialog, check the [Use configured virtual switches/port profile.] checkbox.
From the Command-line:
Create the XML file that defines network resources.
Define the VLAN ID specified in steps 2 and 3 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.6 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_ovmforsparc.rcxprop
Describe the virtual network definition file in one line as below:
"Name of the virtual switch service created in OVM for SPARC"=VLAN ID |
For the VLAN ID, a value from 1 to 4094 can be specified.
Example
"primary-vsw0"=10
Blank spaces before and after equal signs ("=") are ignored.
Describe the virtual switch service 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 virtual switch service name, the first occurrence in the file is valid and the lines after it are ignored.
An error occurs during L-Server creation if the definition of the VLAN ID of the network resource connected to the NIC cannot be found.
