FAQ(ECL2.0)

Baremetal Server - FAQ

Showing 1-6 of 6
Items per page:
  • How to make NIC redundancy at Baremetal ServerBaremetal Server, ECL2.0

    Steps to make NIC redundancy at Baremetal Server whose host OS is created with Enterprise Cloud 2.0 official template Red Hat Enterprise Linux 7 image is following.

    ==================================================
    1. Connect same logical network to each physical network device which connected each 2 physical NIC on same plane Baremetal server via Enterprise Cloud 2.0 Cloud computing control panel
    ==================================================
    Please make connection between same logical network and each physical network device which connected each 2 physical NIC on same plane Baremetal server with the procedure which informing at following tutorial. In this case, please specify each same segment type.

    In addition, please specify same segment ID about segment ID(VLAN ID) each in the case of using vlan in segment type.

    ==================================================
    2. Make redundant interface and configure IP address to redundant interface on Baremetal server host OS(Red Hat Enterprise Linux 7)
    ==================================================
    Please make interface redundancy with execute following command with Shell on Baremetal server host OS(Red Hat Enterprise Linux 7).

    --------------------------------------------------
    2-1. Disable IPv4 and IPv6 on physical NIC#1 and #2 which connected to the same plane on Baremetal server
    --------------------------------------------------
    # nmcli connection modify [physical_connection_name_1] autoconnect on ipv4.method disable ipv6.method ignore
    # nmcli connection modify [physical_connection_name_2] autoconnect on ipv4.method disable ipv6.method ignore

    ※Please specify the existing connection name which corresponds to physical NIC#1 on Baremetal server to physical_connection_name_1
    ※Please specify the existing connection name which corresponds to physical NIC#2 on Baremetal server to physical_connection_name_2

    --------------------------------------------------
    2-2. Create bonding interface using physical NIC#1 and #2 connected to the same plane on Baremetal server
    --------------------------------------------------
    # nmcli connection add type bond con-name [bond_connection_name_1] ifname [bond_interface_name_1] miimon 100 updelay 0 downdelay 0 mode active-backup primary [slave_interface_name_1] # nmcli connection add type bond-slave ifname [slave_interface_name_1] master [bond_interface_name_2] # nmcli connection add type bond-slave ifname [slave_interface_name_2] master [bond_interface_name_2]

    ※Please specify the existing connection name which corresponds to physical NIC#1 on Baremetal server to physical_connection_name_1
    ※Please specify the existing connection name which corresponds to physical NIC#2 on Baremetal server to physical_connection_name_2
    ※Please specify the new creating connection name for bonding interface to bond_connection_name_1
    ※Please specify the new creating bonding interface name to bond_interface_name_1
    ※Please specify the interface name of physical NIC#1 on Baremetal server which becomes to slave of bonding interface to slave_interface_name_1
    This interface becomes to primary physical NIC of bonding interface.
    ※Please specify to interface name of physical NIC#2 on Baremetal server which becomes to slave of bonding interface to slave_interface_name_2
    This interface becomes to secondary physical NIC of bonding interface.
    ※Please specify bonding interface name to bond_interface_name_2. Accordingly, please specify the same value as "bond_interface_name_1"

    --------------------------------------------------
    (Please carry out "2-3." in addition in the case of only using "flat" for segment type when connected with logical network in "1.".)
    2-3. Manually IP address setting to bonding interface(Please specify the parameters such as the default gateway more as needed.)
    --------------------------------------------------
    # nmcli connection modify [bond_connection_name_2] autoconnect on ipv4.method manual ipv4.address [ip_address_1]

    ※Please specify the connection name of bonding interface to bond_connection_name_2.
    Accordingly, please specify the same value as "bond_connection_name_1".
    ※Please specify the IP address assigned to bonding interface with CIDR format to ip_address_1.

    --------------------------------------------------
    (Please carry out "2-4." in addition in the case of only using "vlan" for segment type when connected with logical network in "1.".)
    2-4. Disable IPv4 and IPv6 on bonding interface.
    --------------------------------------------------
    # nmcli connection modify [bond_connection_name_2] autoconnect on ipv4.method disable ipv6.method ignore

    ※Please specify the connection name of bonding interface to bond_connection_name_2.
    Accordingly, please specify the same value as "bond_connection_name_1".

    --------------------------------------------------
    (Please carry out "2-5." in addition in the case of only using "vlan" for segment type when connected with logical network in "1.".)
    2-5. Create VLAN interface using bonding interface
    --------------------------------------------------
    # nmcli connection add type vlan dev [bond_interface_name_3] con-name [vlan_connection_name_1] ifname [vlan_interface_name] id [vlan_id]

    ※Please specify the new creating bonding interface name which VLAN interface uses to bond_interface_name_3.
    Accordingly, please specify the same value as "bond_interface_name_1".
    ※Please specify the new creating connection name which is for VLAN interface to vlan_connection_name_1
    ※Please specify the new creating VLAN interface name to vlan_interface_name.
    ※Please specify VLAN ID which corresponds to connected logical network to vlan_id.

    --------------------------------------------------
    (Please carry out "2-6." in addition in the case of only using "vlan" for segment type when connected with logical network in "1.".)
    2-6. Manually IP address setting to VLAN interface(Please specify the parameters such as the default gateway more as needed.)
    --------------------------------------------------
    # nmcli connection modify [vlan_connection_name_2] autoconnect on ipv4.method manual ipv4.address [ip_address_2]

    ※Please specify the connection name of VLAN interface to vlan_connection_name_2.
    Accordingly, please specify the same value as "vlan_connection_name_1".
    ※Please specify the IP address assigned to VLAN interface with CIDR format to ip_address_2.

    --------------------------------------------------
    2-7. Restarting network(or rebooting OS)
    --------------------------------------------------
    # systemctl restart network.service
    (# shutdown -r now)

    --------------------------------------------------

    Is this page helpful?

    Yes No
  • Why the hot swap is N/A at the time of an HDD failure regarding Workload Optimized 2?Baremetal Server, ECL2.0

    It is one of the specifications of Workload Optimized 2 that the customers can set up the RAID configuration and so forth. So, the hot swap is not available to protect the data owned by the customers.

    Is this page helpful?

    Yes No
  • How to change BIOS settings on Baremetal server?Baremetal Server, ECL2.0

    In the server list of Cloud Computing Control Panel, you can change the setting at 'Set UEFI' from the action of the target Baremetal server.

    Refer to below Tutorial regarding how to access to UEFI(BIOS) setting window.
    Tutorial - Baremetal Server Tools

    Refer to below Service Description regarding the list of UEFI settings.
    Service Description - Baremetal Server - UEFI Function

    Is this page helpful?

    Yes No
  • Are there any restrictions regarding virtual appliances which can work on Virtual server or Baremetal server?Baremetal Server, ECL2.0, Virtual Server

    There is no restriction regarding virtual appliances brought from Customer's environment which work on Virtual server or Baremetal server.

    However,  BYOL(Bring Your Own License) included virtual appliances is not supported, so we do not support if there are any troubles on its working.
    Reference: Service Descriptions - Image Storage

    Is this page helpful?

    Yes No
  • How to change the default gateway for VMware vSphere ESXi?Baremetal Server, ECL2.0

    Please follow the below steps.
    1. Execute the Remote Console Access to Baremetal server according to Tutorial.
    2. On DCUI screen, of VMware vSphere ESXi, press [F2].
    3. On Authentication Required screen, put User / Password and press [Enter].
    4. On System Customization screen, select "Configure Management Network" and press [Enter].
    5. On Configure Management Network screen, select "IP Configuration" and press [Enter].
    6. On IP Configuration screen, change IP address of Default Gateway and press [Enter].
    7. On IP Configuration screen, press [Esc].
    8. When you are required to reflect the change and reboot the management network, press [Y] on Configure Management Network : Confirm screen.

    Is this page helpful?

    Yes No
  • How to use yum?Baremetal Server, ECL2.0, Virtual Server

    Official image template RedhatOS case
    Repository is provided using Red Hat Update Infrastructure (RHUI). In order to use this RHUI, it is necessary to create a common function gateway on the tenant and connect it to the virtual server. Therefore, please refer to the following tutorial and check whether yum command can be executed.

    3.9. Common Function Gateways
    6.2.3. Add a Network Interface to the Instance

    You also need to create an ifcfg file and restart it. As for the ifcfg file, it becomes the contents of the guest OS and it is excluded from the support. We have confirmed that it becomes possible to communicate with NTP server by setting by referring to [Configuring an Interface with Dynamic Network Settings Using ifcfg Files] below.

    3.5. Configuring Ip Networking with ifcfg Files

    · Official image template CentOS
    By default, there is a repository under /etc/yum.repos.d/. In order to access this repository, it is necessary to subscribe Internet connection menu separately.

    Conditions for Usage with Other Menus

    Is this page helpful?

    Yes No

We appreciate your cooperation in improving the site

Did this FAQ be helpful? If you have any comments, please let us know.

Thank you

Your feedback has been received.