1. VMware ESXi for BYOL Configuration Guide

1.1. About This Guide

1.1.1. Purpose of This Guide

This document is written for customers who have subscription of Enterprise Cloud 2.0 ( which will be called ECL2.0 hereinafter) and have some prior experience of using VMware vSphere products.
The following steps are assumed to be have been pre-configured before starting the configuration explained in this guide :-
List of Preliminarily Created Menus
Items Status
Subscription for ECL2.0 Completed Subscription
Logical Network Menu Completed creating total 3 IDs: For vSphere Management data (Data Plane) / For vSphere virtual server transmission data (Data Plane) / For Storage Connectivity (Storage Plane)
Block Storage (Provisioned I/O Performance) Menu Completed creating LUN
Firewall Menu (Brocade 5600 vRouter) Completed creating a Firewall
Internet Connectivity Menu Completed creating Internet Gateways

1.1.2. Pre-Setup Configured Image

ESXi for BYOLの構成イメージ

Figure:- ESXi Configuration Image

1.1.3. Post-Setup Deployed Image

ESXi for BYOLの構成イメージ

Figure :- ESXi Deployed Image

1.1.4. Preliminary Items Needed

Customers are required to have vSphere Client installed in their remote terminal ( vSphere Client is needed to control the operations on the ESXi servers except if customers have direct access to the ESXi console)
Customers are advised to refer to VMware’s vSphere Client and vSphere Web Client Software Requirements for further requirements for installation.
  • Customers are advised to prepare a ECL2.0 network having access to Internet.

1.1.5. Service Descriptions For Reference

Customers are advised to read the following service descriptions for reference:

  • Service Description: Baremetal Server
  • Service Description: OS
  • Service Description: VMware_ESXi for BYOL

1.1.6. At the Usage of This Guide

Customers are noted of the following information as they refer to this guide:

  • This guide introduces configurations Service Provider have deployed adhering to infrastructure constraints and service specification of ECL2.0. However, this guide will not guarantee for customer’s requirements or infrastructure constraints.
  • This guide focuses on deployment procedure unique to vSphere ESXi configuration in ECL2.0. This guide will not cover general and overall deployment process of vSphere ESXi.
  • This guide does not cover general operations or instructions for customers to configure Logical network , firewall or virtual servers utilized in this guide. For general operations related to these product customers are advised to refer to Enterprise Cloud 2.0 service descriptions and other such tutorials available online.
  • Customers are advised that any published details available in this guide can be changed, modified, or revised without prior notice.

1.2. Procedures of Configurations

1.2.1. Delete Logical Network Port

In Baremetal Server Menu, Logical Network Port for ESXI are created in tagged mode with default Segmentation ID or VLAN ID as 3.
In order for Customers to change the segment ID, that port should be deleted and a new port created in the particular logical network with segmentation ID of choice.

Figure :- Select the Port to be deleted.


Figure :- Confirm deletion of the Port

1.2.2. Add a New Port to Logical Network (Data Plane)

Add two (2) new ports to Data Plane of Logical Network.
The Logical Network port created will be used for VM Management Plane Data transmission and assigned segment ID (vlan) “100”

Figure :- Add a Port


Figure :- Details of Port Settings


Figure :- Confirm the port created.

1.2.3. Connect to ESXi Console via Baremetal Server`s ILO Remote Console access

Baremetal Remote Console Access will allow iLO log-in to Baremetal Server, and activate ESXi Console screen.

Figure :- Remote Console Access Details


Figure :- Log in to iLO:


Figure :- Log-in screen to ESXi

1.2.4. Modify Network Settings of ESXi

By manually reflecting the new settings of Logical Network Ports, ESXi Network Settings will be modified.
In this section segment ID (vlan) and IP Address screens will be illustrated here:

Figure :- ESXi vlan modification: Changed vlan from previous default value of 3 to 100


Figure :- Change IP Address of ESXi Network by reflecting the New IP address of the Logical Network Port added.

1.2.5. NIC Teaming Settings for ESXi vmnic Connected to Data Plane

Connect to the ESXi via vSphere Client from the Staging server ; modify the vmnic3 teaming configuration

Figure :- Validating vmnic3


Figure :- ESXi Teaming Setting

Logical Network port further requires IP Address. Even if NIC Teaming is applied to both logical network ports; IP Addresses will be set to both; therefore, Customers are hereby cautioned that the both of VLAN that is set to VMware ESXi vSwitch and logical network’s segment ID (VLAN) are transmittable.
Please refer to Baremetal server menu`s service specification for details on NIC Teaming.
Customers are noted port assignments are as follows:
<REFERENCE> Baremetal Server ESXi - NIC Names and Correlations Table:
Baremetal Server Physical NIC Port Logical Network Plane ESXi vmnic Usage within ESXi
1 Data Plane vmnic0
VM kernel Port (Manage / HA / vMotion)
Virtual Machine Port Group for Traffics
2 Storage Plane vmnic1 iSCSI connection with VM kernel Port Block Storage (Provisioned I/O Performance)
3 Storage Plane vmnic2 iSCSI connection with VM kernel Port Block Storage (Provisioned I/O Performance)
4 Data Plane vmnic3
VM kernel Port (Manage / HA / vMotion)
Virtual Machine Port Group for Traffics

1.2.6. Add a Port to Storage Plane Logical Network

Customers can add a Port to Storage plane NIC via Customer Portal.


Figure :- Add a Port to Baremetal Server


Figure :- Segmentation ID of Storage Plan Logical Network Ports is set to 200 .

1.2.7. Create VM Kernel Interface connected to Storage Plane

Customers can create an interface in vSwitch connected to Storage Plane from vSphere Client.

  • In order for Customers to plan redundancies in multipath, 2 VM Kernel interface will be created.
  • Network settings will grant IP Address belonging to the same logical network/ same subnet
<Example> Exemplar Settings in Storage Connectivity
VM Kernel Interface VLAN Logical Network IP Address
Storage-NW01 200 Storage01-ESXi 192.168.XXX.11
Storage-NW02 200 Storage01-ESXi 192.168.XXX.12

Figure :- Example of Creating VM Kernel Interface

  • Implement settings to enable iSCSI Port Bind
    Multipath settings will not be available if placed only with the above Interface Settings.
    In order for the Customers to enable iSCSI Multipath, Port Bind Settings needs to be configured
    This particular Settings will be implemented to avoid conflict of redundancies in iSCSI Multipath and vSwitch redundancy function.
    For the details Customers are advised to refer to Considerations for using software iSCSI port binding in ESX/ESXi (2038869) published in VMware inc KB
<Example> Port Bind Example Setting for Storage Connectivity
VM Kernel Interface Before / After of the Change Active Standby Unused
Storage-NW01 Before vmnic1 vmnic2 N/A
  After vmnic1 N/A vmnic2
Storage-NW02 Before vmnic1 vmnic2 N/A
  After vmnic2 N/A vmnic1

Above Settings will take place in the Teaming Settings Screen below for respective VM Kernel Interface:


Figure:- VM Kernel Teaming Settings

1.2.8. Create iSCSI Software Adapter

  • Customers can enable (or validate) the iSCSI software adapter for ESXI from the Vmware vSphere Client.

Figure :- Prior to the initiation (or validation) of iSCSI software


Figure :- After the iSCSI software is initiated.

1.2.9. Port Binding Settings for the iSCSI adapter


Figure :- Before Port Binding Settings take place.


Figure :- After Port Binding Settings take place.

1.2.10. iSCSI Initiator Settings / Storage Mounting

  • Pre-created Block Storage (Provisioned I/O Performance) LUN will be targeted for iSCSI Initiator in settings.
    After the settings take place, Storage is mountable in ESXi Storage Adapter Settings Screen.

Figure :- Connect Storage that is connected with iSCSI

iSCSI Qualified Name(iQN)の確認後

Figure :- Confirmation of iSCSI Qualified Name (iQN)

1.2.11. Create Data Store

  • Create Data Store by configuring LUN Settings.

Figure :- Add LUN.


Figure :- Completion of data store creation

1.2.12. Create Virtual Server

  • Start creating Virtual Server.

Figure :- Create Virtual Server.


Figure :- Completion of data store creation

1.2.13. BYOL ISO for Virtual Server

  • Upload binary files such as OS etc. from local folder in data store.
    Install OS by mounting CD / DVD drives to Virtual server.

Figure :- Upload a file to data store.


Figure :- Mounting CD / DVD drive to Virtual Server.


Figure :- Select binary to be installed.

1.2.14. Add a New Port to Logical Network in Data Plane for Virtual Machine data traffic

  • Create a new Port in Logical network to enable VM data traffic for the Virtual machine created in previous section
    This particular setting will be applied to physical ports connected to Data Plane.
    Settings can be configured via Customer Portal.
Example Settings for Virtual Machine Connectivity
Logical Network Port VLAN Logical Network vmnic
VM-Seg01 300 Data03-BM vmnic0
VM-Seg01 300 Data03-BM vmnic3

Figure :- Before adding a new port to Logical Network.


Figure :- After adding a new port to Logical Network.

1.2.15. Create a Port Group for Virtual Machine

  • Using the configuration of port created in Logical Network in the previous section, create a Virtual Machine Port Group in vSwitch.
    After creating this port group, it’s Teaming settings will be configured as below to reflect the changes:

Figure :- Before adding a Virtual Machine Port Group.


Figure :- After adding a Virtual Machine Port Group.


Figure :- NIC Teaming Settings of Virtual Machine Port Group.

NIC Teaming Setting Example for a Virtual Machine Port Group
Virtual Machine Port Group Before / After the Change Active Standby Unused
VM-seg1 Before vmnic0,vmnic3 N/A N/A
  After vmnic3 vmnic0 N/A