Terms and Conditions

Minimum Use Period

1. Standard plan

This service does not require Minimum Use Period.

2. Custom plan

The minimum usage period can be selected from 2 years / 3 years / 5 years.

Notes for Customers Prior to Use

Baremetal Server

Creating Baremetal Server

<Standard plan>

  • Although there are differences depending on the OS type and flavor, it may take about 30 minutes to a maximum of 2 hours to create a baremetal server.

  • Baremetal servers that are in an error state when creating Baremetal server will not be charged. In addition, it will be automatically deleted after 7 days or more.

<Custom plan>

  • The standard delivery time for bare metal servers is 3.5 months. However, it may change depending on the customer&#39;s desired number of units, desired specifications, delivery status from hardware vendors, semiconductor shortage, etc. Therefore, we recommend that you inquire about the delivery date as soon as possible. For more information, please contact your sales representative.

Bare metal server server spec change

<Standard plan / Custom plan>

  • You cannot change the server specifications of a bare metal server. When changing to another server spec, the customer needs to create a new baremetal server with the new server spec and perform the server migration work.

Stock of Baremetal Server

<Standard plan>

  • If the baremetal server is out of stock, we may not be able to offer this menu.

Baremetal Server Cancellation

<Custom plan>

  • If you cancel or cancel before the minimum usage period after applying, we will charge the usage fee after deducting the number of months used from the minimum usage period. For example, if you apply for a baremetal server with a monthly usage limit of 200,000 yen for a minimum usage period of 3 years and cancel within 1 year after the start of use, 200,000 yen x (36 months-12 months) = 4.8 million yen. It will be a penalty.

Baremetal Server Network Settings

<Standard plan / Custom plan>

  • Baremetal Server has four physical NIC ports. With Logical Network, two ports are available for Data Plane connection and two ports for Storage Plane connection. Physical NIC port for each Plane is housed in a different Network Interface Card, and is connected to a different peer switch. Failure of physical NIC port / peer switch may occur. In that case, the connection point where a failure occurred will be disconnected. Therefore, for each connection with Data Plane / Storage Plane, make redundant configuration to cope with physical NIC port failure and peer switch failure.



<Standard plan / Custom plan>

  • Update of firmware should be made by customer. NTTCom suggests that firmware should be updated eventually.
    Customers are allowed to upgrade the firmware of Baremetal Server only with the version approved by this menu. Please refer to the chart below.
    (In case the parts replacement of Baremetal Server is performed, the firmware will be the particular version designated by this menu.)
    Please refer to tutorial for how to update firmware.

The firmware version specified in this menu is as follows. (As of March 2022)

  General Purpose 1 v1/General Purpose 2 v1/General Purpose 3 v1/Workload Optimized 1 v1 Workload Optimized 2 v1 General Purpose 1 v2/General Purpose 2 v2/General Purpose 3 v2/Workload Optimized 1 v2

General Purpose 2 v3 / General Purpose 3 v3 / Custom Plan v3


System ROM 2.00 or later

BMC Firmware 3.26 or higher

V - R1.18.0 or later

System ROM U32 v2.10 or higher

Web Console

iLO 2.22 and above (iLO4)

BMC Firmware 3.26 or higher

9.04 F (sdr 03.11) or later

iLO 1.45 and above (iLO5)


Smart Array P440ar Controller 2.52 or later

MegaRAID SAS Adapter 4.600-4907 or more

  • (No regulation)

Smart Array P816i-a SR gen10 or above


1.1200.0 or later

0x80000208 or later

  • (No regulation)

20.14.54 and above


<Standard plan / Custom plan>

  • UEFI function is provided through this menu however the number of Configurable features is limited by the service specifications.

  • Due to troubles such as the mother board failure, the customer may be requested to change the UEFI settings to the prescribed values.

  • Settings are recommended to be changed one by one . When customer initiates mass changes of multiple settings , the set values may or may not get reflected for all settings .

*In the custom plan, manual setting from BMC is possible.

Post-Installing Action

<Standard plan / Custom plan>

  • Customers are advised that post-installing action will be executed automatically after the deployment of Baremetal Server. Customers are further noted that they cannot operate the Baremetal Server prior to such Post-Installing Action is executed.

  • Please be advised that Baremetal Server menu will not be liable in any way when the Customer’s use of, or access to, the Server becomes impossible due to errors in the Customer’s Script. Charge will be continued until the Baremetal Server concerned is deleted.


Available characters for post-installing action is as follows:abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789!”#$%&’()*+,-./:;<=>?@[]^_`{|}~


<Standard plan / Custom plan>

  • In the event that Customers select Official Image Template with Service Provider License (Windows/RHEL) to create Baremetal Server and then install other new OS, they are advised that the charge of existing Official Image Template will be continued.

  • The charge of Official Image Template with Service Provider Licenses will be associated with the existing Baremetal Server they installed to.
    (In case of Windows OS for example, Customers can change the Product Key of the Service Provider License to the Product Key of Customers’. But the charge of the OS as the Service Provider License is continued.)


  • OS Initial Password

  1. Customers can set the initial password of each user of the OS via the Customer Portal / API. After the Baremetal Server provisioning, password change via the Customer Portal / API is not possible.

  2. If Customers lost initial OS password, they have to restore / change the password by using Rescue Mode that each OS provides via the remote console. If the OS in question does not provide the Rescue Mode and if the Customer cannot create the Rescue Disk for the state before the password is lost, Customers will not be able to restore / change the password.

Workload Optimized 2

<Standard plan>

Please note that Workload Optimized 2 has restrictions on the following features.

  • Available official image templates will be limited to the followings.
    ・Windows Server 2012R2 Standard(SPLA)
    ・Windows Server 2012R2 Standard for BYOL
    ・Windows Server 2012R2 DataCenter for BYOL
  • Changing the settings of the UEFI, and confirmation of the UEFI setting status from the Customer Portal are not available.
    About the setting situation list, please refer to the following.


<Standard plan / Custom plan>

  • When the SSD write limit is approached, the customer may be contacted to replace the SSD.

Remote Console Access

<Standard plan / Custom plan>

  • SSL VPN is limited to maximum one session (connection) per user ID. Multiple clients cannot access the same user ID.

  • You will not be able to connect your network to SSL VPN. This menu is not for inter-base communication. It is a function to connect to the BMC of the baremetal server.

  • In case Customers’ communication is made via proxy server, connection may be failed.

  • If a conflict occurs between Customers’ network (on-premise) and IP address of SSL VPN, communication may become impossible within customers’ network.

  • Customers are not allowed to access remote console access via Arcstar Universal One or Multi-Cloud Connect. Only the access through Internet is available.


<Standard plan / Custom plan>


Baremetal Server


<Standard plan / Custom plan>

  • In case Customers independently upgrade the firmware, it may fall outside of the support coverage of this menu.
    (In case the parts replacement is performed due to failure of Baremetal Server, the firmware specified in this menu is applied to each part.)
  • Please refer to tutorial for how to update firmware.

  • The method specified in this menu
    • General Purpose 1 v1 / General Purpose 2 v1 / General Purpose 3 v1 / Workload Optimized 1 v1
      • Update by using HP Service Pack for ProLiant (SPP)/ HP Smart Update Manager
    • Workload Optimized 2 v1
      • Please contact us via ticket.

    • General Purpose 1 v2 / General Purpose 2 v2 / General Purpose 3 v2 / Workload Optimized 1 v2
      • Update using UPDATE_DVD
    • For General Purpose 2 v3 / General Purpose 3 v3 / Custom Plan v3
      • Update by using HP Service Pack for ProLiant (SPP)/ HP Smart Update Manager


<Standard plan / Custom plan>

  • Users with restricted privileges will be provided to Customers. Please do not use the functions other than the followings. If PXE boot has to be executed, it should be executed by the Customer, to build the system. At that time, make the settings to avoid confliction with the Customer’s DHCP or DHCP of the Logical Network.

    1. Access Baremetal Server via Console Access

    2. Use of Virtual Media function <via Console>

    3. Turn power ON/OFF

    4. UEFI manual setting, RAID setting * Custom plan only

  • Customers are prohibited from setting / changing the IP address in the BMC of the baremetal server provided in this menu. It may not be possible to monitor the bare metal server using the monitoring menu.

  • Communication between baremetal servers via BMC is not possible. (Blocked by the opposite switch). Customers cannot ping the BMC port of other baremetal servers.

  • Customers cannot retrieve event logs via the BMC directly from the BMC on the baremetal server.


<Standard plan / Custom plan>

  • Depending on the firmware version of UEFI, there is a possibility that events that don’t work properly occurs even after putting the function of changeable setting of the UEFI function list. After the event is confirmed in the menu, it will be posted as a “known event”.

  • For some UEFI functions, change settings, another UEFI setting may be required as a prerequisite. If UEFI setting as prerequisite is not set, operation can not be guaranteed for the corresponding setting.

Power Operations

<Standard plan / Custom plan>

  • It may take about one hour to start / stop a baremetal server. It depends on software installed on the host OS.

  • The flavor of v2 will be restarted 5 times when PXE boot is performed. (It will take more than 30 minutes to complete.)

  • If v2 server performs server reboot after boot mode change, server may not start up. In that case please start server again.



<Standard plan / Custom plan>

  • cloud-init/cloudbase-init script
    Cloud-init script is installed by default for the template with Provider License.
    Cloud-init script is composed of metadata (OS account, OS account’s password, SSH public key, hostname) and user data (Linux: shell script, Windows: PowerShell).
    Cloud-init Script is executed at the timing of OS boot.
    Customers can freely edit only the user data(※) via Customer Portal / API.
    1.RHEL/CentOS/Ubuntu : cloud-init
    2.Windows : cloudbase-init.

License Charge / Support

<Standard plan / Custom plan>

  • Customers are advised that Baremetal Server menu does not take any responsibility for any of damage or difficulty caused by the re-installation of Official Image Template to their Baremetal Server.

Customer-Bring-In Licenses / Applications

<Standard plan / Custom plan>

  • Under the customer responsibility, you can install applications / open source software etc on the bare metal server.
    This menu does not manage the application that customers bring in and the operation management of open source software. In addition, we do not assume any responsibility for its operation / operation.

  • General Purpose 1 v1 / General Purpose 2 v1 / General Purpose 3 v1 / Workload Optimized 1 v1 / General Purpose 2 v3 / General Purpose 3 v3 / Custom Plan For v3, Microsoft Windows Server / Red hat Enterprise Linux / SUSE Linux Enterprise Server
    If you bring in a ISO image of a paid operating system, you need the server vendor’s driver / maintenance tool (HP server: Service Pack for Proliant).
    If you would like to bring the above ISO image please refer to the bare metal server tutorial.

Troubleshooting Support

<Standard plan / Custom plan>

  • In case cold swapping is necessary, Customers will be informed of possible dates for the replacement work.

  • If the Customers cannot be reached by the specified date of this service, the cold swapping will be conducted on the date specified by NTT Com.

  • In case Customers request cold swapping, they are required to check the server’s health by themselves.

  • Customers are required to report any failure related to link down.

  • In the confirmation communication from this service after the work is completed, if Customers cannot be reached or Customers do not contact us, it will be considered that the normalcy is confirmed at the date and time specified by this service.

  • This Menu does not offer to ensure the Customers’ OS / Application normalcy or consistency after either part replacement or maintenance operations are completed.

  • After detailed check of hot swapping, cold swapping may be chosen in some cases depending on the failure condition. For details, please refer to the section of “Baremetal Server Troubleshooting Support Flow”. (Reference: “Operation of Baremetal Server Menu”)

  • In the case of events that can not be detected by the monitoring menu, based on the report from customers, the failure correspondence will start.

  • In case hot swapping by NTT Com is needed and the power of Baremetal Server has been turned off by Customers, they are forewarned that we may turn on the power temporarily to check the server’s health.

  • Even in case hot swap is requested, cold swap may be proposed in some cases depending on failure and support conditions.

<Custom plan>

  • Please note that when recreating a server after deleting it, if the server fails before it becomes reusable (during initialization), we may take measures such as replacing parts without notifying the customer. please give me.

Hot Swapping of HDD / SSD

<Standard plan / Custom plan>

  • For some locations and flavors, hot swapping of HDD/SDD will be performed upon Customer’s request when HDD/SDD failure occurred.

  • For the requesting method, refer to an explanation in the email sent from NTT Com at the time of the failure occurrence.
    For the locations where HDD/SDD Hot Swapping is possible, please refer to the following.
  • If HDD/SDD RAID setting is implemented, Rebuild will be automatically started when HDD/SDD for failure replacement is inserted. During rebuilding, both read and write performances may drop.

  • Though it is rare, data destruction may occur during HDD/SDD swapping work. NTT Com will not be liable for data destruction. Just in case, daily backup is recommended.

  • Completion of hot swapping work will be reported when the HDD is recognized as physically normal. NTT Com side will not check even completion of rebuilding.

  • If Customers want HDD/SDD hot swapping, they are advised to check in advance if RAID setting is made so as to allow HDD/SDD hot swapping.