Enterprise Cloud Knowledge Center
Close the Menu
Home > Enterprise Cloud 2.0 Support Information > FAQ - Enterprise Cloud 2.0 > Is the redundant method available that uses the same IP address with different MAC addresses including the Windows Server Failover Cluster?

FAQ

Is the redundant method available that uses the same IP address with different MAC addresses including the Windows Server Failover Cluster?

(:Last updated）

We have confirmed that Windows Server Failover Cluster works under our verification environment.

As of July 2019, we have confirmed the operation with the next version.
- Windows Server 2012 R2​
- Windows Server 2016​

* Since the DAD function is disabled in the official image template of the virtual server, please follow the procedure below when using a failover cluster with a virtual server.

1. Input "regedt32" in search box on Start menu and enter.
2. Click "HKEYLOCAL MACHINE" in Registry Editor.
3. Click "System" -> "CurrentControlSet" -> "Services" -> "TcpIp" -> "Parameters".
4. Right-click "Parameters" and click "New" -> "DWORD(32-bit)Value".
5. Delete "New Value #1", right-click "ArpRetryCount" and click "Delete".
6. Reboot the virtual server.

  • ECL2.0
    •  
  • OS
    •  
  • Virtual Server
    •  

Related Pages

  • yum and dnf commands fail on Red Hat Enterprise Linux 8Baremetal Server, Dedicated Hypervisor, ECL2.0, OS, Virtual Server

    Issue

    The yum command and dnf command may fail in Red Hat Enterprise Linux 8 (RHEL8). We apologize for the inconvenience, but please follow the procedure described in the remedy.

    <Failure example>

    - Curl error (56): Failure when receiving data from the peer for -<Region Name>.ecl.ntt.com.local/pulp/repos/content/dist/rhel8/rhui/8/x86_64/appstream/os/repodata/repomd.xml
    [OpenSSL SSL_read: error:14094415:SSL routines:ssl3_read_bytes:sslv3 alert certificate expired,errno 0]

     

    Affected Template

    The following templates in each menu are affected.

    Menu

    Template

    Virtual Server *1

    • RedHatEnterpriseLinux-8.1_64_include-license_virtual-server_02

    • RedHatEnterpriseLinux-8.2_64_include-license_virtual-server_02

    Baremetal Server

    • RedHatEnterpriseLinux-8.1_64_include-license_baremetal-server_01

    Dedicated Hypervisor

    • RedHatEnterpriseLinux-8.1_64_include-license_hw9_vSphere-ESXi_02

    *１For these templates, customers can use yum or dnf without the following Solution.

    RedHatEnterpriseLinux-8.1_64_include-license_virtual-server_12

    RedHatEnterpriseLinux-8.2_64_include-license_virtual-server_12

    Solution

    To avoid the problem, the customer needs to renew the client certificate.

    ①Delete the existing existing rpm file

    rpm -e rh08-sr-rhui-client02-<Region Name>-ecl-ntt-com-2.0-1.noarch

    Select <Region Name> from jp1, jp2, jp4, jp5, jp6, uk1, de1, fr1, us1, sg1, hk1.

     

    ②Modify hosts file

    Add the following to /etc/ hosts file.

    169.254.127.24 rhcds-sr-vip-<Region Name>.ecl.ntt.com.local

     

    ③Get the new rpm file

    #curl --insecure https://<Link Local Address>/pub/rhui-client-packages/<rpm package name> >> <rpm package name>
    #curl --insecure https://<Link Local Address>/pub/rhui-gpg-key/RPM-GPG-KEY-rhui-custom >> RPM-GPG-KEY-rhui-custom

    ・Link Local Address

    Please specify 169.254.127.24 for <link local address>.

    ・rpm package name

    For <rpm package name>, specify an appropriate file according to the region.

    JP1 rh08-sr-rhui-client02-jp1-ecl-ntt-com-2.0-2.noarch.rpm
    JP2 rh08-sr-rhui-client02-jp2-ecl-ntt-com-2.0-2.noarch.rpm
    JP4 rh08-sr-rhui-client02-jp4-ecl-ntt-com-2.0-2.noarch.rpm
    JP5 rh08-sr-rhui-client02-jp5-ecl-ntt-com-2.0-2.noarch.rpm
    JP6 rh08-sr-rhui-client02-jp6-ecl-ntt-com-2.0-2.noarch.rpm
    US1 rh08-sr-rhui-client02-us1-ecl-ntt-com-2.0-2.noarch.rpm
    UK1 rh08-sr-rhui-client02-uk1-ecl-ntt-com-2.0-2.noarch.rpm
    SG1 rh08-sr-rhui-client02-sg1-ecl-ntt-com-2.0-2.noarch.rpm
    HK1 rh08-sr-rhui-client02-hk1-ecl-ntt-com-2.0-2.noarch.rpm
    DE1 rh08-sr-rhui-client02-de1-ecl-ntt-com-2.0-2.noarch.rpm
    AU1 rh08-sr-rhui-client02-au1-ecl-ntt-com-2.0-2.noarch.rpm
    FR1 rh08-sr-rhui-client02-fr1-ecl-ntt-com-2.0-2.noarch.rpm

     

    ④Install rpm files

    #chown root:root ~/<rpm package name>
    #chown root:root ~/RPM-GPG-KEY-rhui-custom
    #chmod u+x ~/<rpm package name>
    #chmod u+x ~/RPM-GPG-KEY-rhui-custom
    #rpm -U <rpm package name>

     

    ⑤Import GPG Key

    #rpm --import ~/RPM-GPG-KEY-rhui-custom

     

    Open in a new window
  • DNS setting of virtual server RHEL7.5 / CentOS 7.5ECL2.0, OS, Virtual Server

    Issue

    DNS setting is set to 8.8.8.8 after deploying virtual server menu Red Hat Enterprise Linux 7.5/Cent OS 7.5 image.

    Solution

    Execute the following command and change the IP address in the DNS settings (nameserver) to a value appropriate for the customer.

    1# vi /etc/resolv.conf

    For articles on DNS servers, please also refer to the following the link.

    Is the DNS Server provided to Customers?

    /en/faq/2.0/cfgw-dns/

    Open in a new window
  • Is the SID (Security Identifier) of Windows Server changed by snapshot duplication or system restore of the backup menu?ECL2.0, OS, Virtual Server / Specification

    No. In any cases, in principle, the SID of Windows Server is not changed.
    However, if you added Sysprep on Windows Server in advance, SID might be changed.

    Open in a new window
  • License activation fails on the virtual server created from Windows Server Official Image Template.ECL2.0, OS, Virtual Server / Operation, Specification

    There is a possibility that connectivity to the license server provided by NTT Com may not be established.
    Follow the steps below to ensure connectivity to the license server.

    Tutorial - Activate your OS License

    Reference：Service Descriptions - Windows Server - Conditions for Usage with Other Services

    In order to implement OS license authentication, a common function gateway is required. When using Windows Server, please make sure to apply common function gateway.
    Also, if the common function gateway is removed, OS license authentication will be lost. Therefore, please be careful not to remove the common function gateway from the Windows Server that you are using.

    Open in a new window
  • How to check whether the virtual server (RHEL) license activation is done or not?ECL2.0, OS, Virtual Server / Specification

    Regarding the authentication method of the virtual server (RHEL) created from the official image template in Enterprise Cloud 2.0, Red Hat Update Infrastructure (RHUI) is adopted instead of the license authentication method using subscription (RHN).

    Therefore, there is no problem even if valid subscriptions are not displayed or registered in the execution results such as [subscription - manager list - available].
    In addition, it is not necessary for customers to register their subscriptions.

    If you are connected to a common function gateway and you can connect to the Internet, yum and license authentication can be executed.

    Regarding verification of license authentication, if [yum repolist all] command etc. can be executed normally, it can be confirmed that license authentication is completed.

    Open in a new window

Support Information

Enterprise Cloud 2.0

Enterprise Cloud 1.0

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.

▲