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 "9.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 "9.1.3 Physical Network Design for the Public LAN and iSCSI LAN".
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.
On the physical L-Servers used by L-Platforms, only the default NIC can be used. The physical network adapter number for Network Interface Cards that can be used as an admin LAN on the L-Platform is as below:
When not performing redundancy, "1" is available
When performing redundancy, "1" and "2" are available
When deploying a physical L-Server, if using the UMC function by configuring [Function number expansion (Onboard)], note the following two points:
It is necessary to disable UMC of the registration target server before registering the server. When UMC is enabled, disable it.
Only the default NIC can be used as the admin LAN. The physical network adapter numbers that can be used for Network Interface Cards are as below:
When not performing redundancy, "1" is available
When performing redundancy, "1" and "2" are available
Information
The first NIC that is available for the admin LAN can be changed.
For details, refer to "5.4.2 Registering Blade Servers" in 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 there are no definition files, refer to "7.1.9 Definition File for Admin LAN Uplink Set" in the "Setup Guide CE".
When Using iSCSI
For details on the definition files for iSCSI networks, refer to "7.1.10 Definition File for iSCSI Network" in the "Setup Guide CE".
When Using the UMC Function
To deploy an L-Server on the Resource Orchestrator manager, it is necessary to connect to the admin LAN using an untagged VLAN.
Since a physical L-Server of the management target communicates with tagged VLANs using the VLAN ID2 or a larger ID when UMC is enabled, it is necessary to convert the tagged VLAN to an untagged VLAN using an L2 switch that relays the admin LAN communications.
Admin LAN
Design the network to enable communication between the admin IP of the Resource Orchestrator manager, the admin IP (oob) of the LAN switch blade, and the MMB admin IP using an untagged VLAN. Configure the LAN switch blade port connected to the physical server of the management target configuring UMC in order to enable communication using a tagged VLAN.
Network Resources
When configuring the admin IP of the Resource Orchestrator manager and the admin IP of the physical server of the management target configuring UMC in the same subnet, create an admin LAN resource that uses a VLAN ID2 or larger. The admin LAN network resource directly connected to the ROR manager is automatically created during installation using the network resource name, "AdminLan", and the VLAN ID, 1. After deleting the admin LAN resource that uses VLAN ID1, recreate it as an admin LAN resource using VLAN ID2 or a larger ID.
Information
When deploying a physical L-Server, the UMC function is configured on the CNA according to the L-Server setting as follows:
Bandwidth
The value found by dividing 100 percent by [Number of functions per port] for the L-Server is automatically set.
When the value of [Number of functions per port] is 2, 50 % is set. When the value is 4, 25 % is set.
LPVID
The VLAN IDs of the network resources which are allocated to L-Servers and for which [Untagged VLAN] is enabled are set.
Note
When using the UMC function, there are the following advisory notes. For details, refer to the hardware manual.
Setting the same VLAN ID for different functions which belong to the same physical port is not possible.
Assign the LPVID within the range between VLAN ID2 and 4094. VLAN ID 1 cannot be assigned. It is necessary to set LPVIDs for all functions that are defined as NICs.
For the ports of the L2 switches connected to CNA, the VLAN ID of LPVID must be set as the tagged VLAN port.
L2 switches connected to CNA must be connected using 10G.
