Top
PRIMECLUSTER Installation and Administration Guide4.6 Cloud Services
FUJITSU Software

21.1.3 Setting Instances

Create the instance and the virtual network interface that configure the cluster node.

When creating the virtual network interface, select the appropriate subnet based on the architectural pattern selected in "20.2.1 Network Takeover."

When selecting network takeover by the virtual router, uncheck the source/destination change.

When using an IAM role, refer to "20.9 Policy Design" and create a policy, and then attach the policy to the EC2 use case to create a role. After creating the role, associate the IAM role with the instances that use PRIMECLUSTER.

When using an IAM user, make sure that the policy described in "20.9 Policy Design" is attached to the IAM user.

If the policy is not attached, attach it.

When creating multiple virtual network interfaces and using a virtual network interface, for which a default gateway is not set, to communicate with interfaces on different subnets, static routing must be set for that virtual network interface. You do not need to set static routing when communicating only with interfaces on the same subnet.

Example

The following is an example of static routing configuration when using a network interface (eth1) different from the administrative LAN (eth0) as the cluster interconnect in the cluster system with a two-node configuration (CF node names are cluster node 1 and cluster node 2).

If the IP address for eth1 of the cluster node 1 is 172.30.64.4/20 and the IP address for eth1 of the cluster node 2 is 172.30.80.4/20, make the following settings on each node.

[For RHEL7]
Cluster node 1
  1. Stop the NetworkManager.

    # systemctl stop NetworkManager
    # systemctl disable NetworkManager
  2. Create /etc/sysconfig/network-scripts/route-eth1.

    # cat /etc/sysconfig/network-scripts/route-eth1
    172.30.80.0/20 via 172.30.64.1 dev eth1
  3. Restart the network connection.

    # systemctl restart network
  4. Make sure that the route set in step 2 has been added.

    # ip route show
    172.30.80.0/20 via 172.30.64.1 dev eth1
  5. Restart the OS.

Cluster node 2
  1. Stop the NetworkManager.

    # systemctl stop NetworkManager
    # systemctl disable NetworkManager
  2. Create /etc/sysconfig/network-scripts/route-eth1.

    # cat /etc/sysconfig/network-scripts/route-eth1
    172.30.64.0/20 via 172.30.80.1 dev eth1
  3. Restart the network connection.

    # systemctl restart network
  4. Make sure that the route set in step 2 has been added.

    # ip route show
    172.30.64.0/20 via 172.30.80.1 dev eth1
  5. Restart the OS.

[For RHEL8]
Cluster node 1
  1. Check the CONNECTION of eth1.

    # nmcli device status
    DEVICE  TYPE      STATE      CONNECTION
    eth0    ethernet  connected  System eth0
    eth1    ethernet  connected  Wired connection 1
    eth2    ethernet  connected  Wired connection 2
    eth3    ethernet  connected  Wired connection 3
    lo      loopback  unmanaged  --
  2. Add a route to the CONNECTION confirmed in step 1.

    # nmcli connection modify "Wired connection 1" +ipv4.routes "172.30.80.0/20 172.30.64.1
  3. Make sure that the route has been successfully added to the CONNECTION.

    # nmcli -g ipv4.routes connection show "Wired connection 1"
    172.30.80.0/20 172.30.64.1
  4. Restart the network connection.

    # nmcli connection down "Wired connection 1"
    # nmcli connection up "Wired connection 1"
  5. Make sure that the route set in step 2 has been added.

    # ip route show
    172.30.80.0/20 via 172.30.64.1 dev eth1 proto static metric 113
  6. Restart the OS.

Cluster node 2
  1. Check the CONNECTION of eth1.

    # nmcli device status
    DEVICE  TYPE      STATE      CONNECTION
    eth0    ethernet  connected  System eth0
    eth1    ethernet  connected  Wired connection 1
    eth2    ethernet  connected  Wired connection 2
    eth3    ethernet  connected  Wired connection 3
    lo      loopback  unmanaged  --
  2. Add a route to the CONNECTION confirmed in step 1.

    # nmcli connection modify "Wired connection 1" +ipv4.routes "172.30.64.0/20 172.30.80.1
  3. Make sure that the route has been successfully added to the CONNECTION.

    # nmcli -g ipv4.routes connection show "Wired connection 1"
    172.30.64.0/20 172.30.80.1
  4. Restart the network connection.

    # nmcli connection down "Wired connection 1"
    # nmcli connection up "Wired connection 1"
  5. Make sure that the route set in step 2 has been added.

    # ip route show
    172.30.64.0/20 via 172.30.80.1 dev eth1 proto static metric 113
  6. Restart the OS.

See

For details on how to configure the static routing, refer to the official OS documentation.