This section explains the preparations for setting up a network.
The network environment and physical server required to run Resource Orchestrator must satisfy the following prerequisites:
The configuration for the admin and public LANs has been designed
The network environment for the admin LAN is configured
For details on the network environment for the admin LAN, refer to "4.2.1.1 Admin LAN Network Design".
Perform the following procedures if necessary.
The configuration for the iSCSI LAN has been designed
For details on how to design and configure a network environment for iSCSI, refer to "4.2.1.3 Physical Network Design for the Public LAN and iSCSI LAN" in the "ServerView Resource Orchestrator Setup Guide".
Note
When using a physical L-Server, the default physical network adapter numbers available for the admin LAN are as given below.
When not performing redundancy, "1" is available
When performing redundancy, "1" and "2" are available
When using a NIC other than the default one, the configuration at the time of physical server registration and at L-Server creation must be the same. Thus when designing systems it is recommended that physical servers registered in the same server pool use the same NIC index.
Information
The first NIC that is available for the admin LAN can be changed.
For details, refer to "2.4.2 Registering Blade Servers" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
When Using IBP
When using IBP, it is necessary to create IBP uplink set for the public LAN and the admin LAN in advance.
When using physical L-Servers, it is necessary to create an IBP uplink set for the public LAN and the admin LAN in advance, using VIOM.
Public LAN
Create a network resource with the same name as the created uplink set.
Admin LAN
Describe the name of the admin LAN uplink set in the uplink set definition file for the admin LAN.
When the definition file does not exist, define it as follows.
[Windows]
Installation_folder\Manager\etc\customize_data\vnetwork_ibp.rcxprop
Describe the definition file in individual lines as below:
Key = Value |
Item | Key | Value | Remarks |
|---|---|---|---|
Presence or absence of IBP environment | support_ibp_mode |
| Specify one of the following:
If left blank, "false" is set. |
Admin LAN settings | external_admin_net_name | The name of the admin LAN uplink set | Enabled when ibp_mode is set to "true" |
When using iSCSI
When using iSCSI, create an iSCSI network definition file.
Network Definition File for iSCSI
Create the following file in advance to define the network information used for iSCSI boot.
The network information is linked with the iSCSI boot information that is registered using the iSCSI boot operation command (rcxadm iscsictl).
Refer to "2.4.2 iSCSI Boot Information" in the "Reference Guide (Resource Management) CE" beforehand.
[Windows]
Installation_folder\Manager\etc\customize_data
[Linux]
/etc/opt/FJSVrcvmr/customize_data
User Groups
iscsi_user_group_name.rcxprop
Common on System
iscsi.rcxprop
In the definition file, an item to define is entered on each line. Enter the items in the following format.
Variable = Value |
When adding comments, start the line with a number sign ("#").
Variable | Meaning | Value |
|---|---|---|
server_model.model_name.boot_nic | Specify the server model name and NIC to be booted using iSCSI. Multiple NICs can be specified.
When setting the default, specify an asterisk ("*"). | Specify the items in the following format. NIC[index] index is an integer starting from "1". |
Example
#Server Section server_model.BX922.boot_nic = NIC1 server_model.BX924.boot_nic = NIC1,NIC2 server_model.*.boot_nic = NIC1,NIC2 server_model.RX300. boot_nic = NIC1,NIC2 |
