No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Huawei SAP HANA Appliance Two Node Installation Guide (RH5885H and RH8100 V3+Redhat) 08

Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuring Network IP Addresses

Configuring Network IP Addresses

Configure the network IP addresses of the two servers in an HA cluster system as planned.

Table 2-1 describes an example configuration of network IP addresses.

Table 2-1 Network IP addresses

Device Name

Type

IP Address Planning

Remarks

RH5885H V3/RH8100 V3

Management network BMC

Node1: 192.168.2.10

Node2: 192.168.2.11

BMC management IP addresses.

OS management port eth0

Redhat cluster secondary heartbeat

Node1: 192.168.2.20

Node2: 192.168.2.21

The IP addresses of the OS management port and BMC management port should be on the same network segment.

Cluster internal port Bond0

10GE Ethernet

Node1: 10.5.2.10

Node2: 10.5.2.11

IP addresses in the private network segment.

Two servers are bound by using two 10GE NICs for HANA database synchronization and cluster redundant heartbeat links.

Service network port Bond2

10GE Ethernet

Node1: 10.5.1.10

Node2: 10.5.1.11

IP addresses in the service network segment. Also use to cluster main heartbeat links and prevent a cluster from brain splitting.

Service network port

Virtual IP address

10.5.1.12

Virtual IP address in the service network segment.

Services access a HANA HA cluster through a virtual IP address, which is on the same network segment as the service network.

The cluster system environment requires three network segments. The plan for network IP addresses in this document is as follows:

BMC network ports: 192.168.2.20 and 192.168.2.21. Connect the RH5885H V3/RH8100 V3 BMC network ports to the GE switch.

OS maintenance network port: 192.168.2.10 and 192.168.2.11. Connect the RH5885H V3/RH8100 V3 GE network ports to the GE switch. It is recommended that the IP addresses of the OS maintenance network ports and BMC network ports are reachable or on the same network segment.

Database synchronization network ports: 10.5.2.10 and 10.5.2.11. Use two 10GE ports on two NICs of the RH5885H V3/RH8100 V3 to synchronize the system replication channel and primary cluster heartbeat for HANA database (one port on each NIC).

Uplink service ports: 10.5.1.10 and 10.5.1.11. Use the other two 10GE ports on the two NICs of the RH5885H V3/RH8100 V3 (one port on each NIC), Also use to cluster main heartbeat links and prevent a cluster from brain splitting.

NOTE:

It is recommended that two 10GE network ports are used to bind with an uplink service port and a database synchronization network port respectively to form an HA network.

This section uses system replication port configuration as an example to describe port binding.

Log in to the S6700 switch, and run the dis mac command to query the mapping among port MAC addresses. Find out the MAC address of the port to be configured, run the ifconfig command to find the corresponding eth* port, and configure port binding.

Configuration on the CLI (Applicable to Redhat6.7)

NOTE:

This section uses port bond0 (physical ports eth2 and eth3) as an example to describe how to configure network IP addresses.

  1. In the /etc/modprobe.d/ directory, create a file named bonding.conf. And add the following commands to bonding.conf.

    [root@HW00001 modprobe.d ]# vi bonding.conf
    alias  bond0 bonding
    options bond0 mode=2 miimon=100
    alias  bond1 bonding
    options bond1 mode=2 miimon=100

  2. Save and close the bonding.conf file, and run the following command to make the configuration take effect.

    modprobe bonding

  3. In the /etc/sysconfig/network-scripts/ directory, create a file named ifcfg-eth2.

    [root@HW00001 home]# vi /etc/sysconfig/network-scripts/ifcfg-eth2

  4. Add the following commands to ifcfg-eth2:

    DEVICE=eth2
    ONBOOT=yes
    BOOTPROTO=none
    TYPE=Ethernet
    MASTER=bond0
    SLAVE=yes
    USERCTL=no
    STARTMODE=hotplug

  5. Save and close the ifcfg-eth2 file. Then, create a file named ifcfg-eth3.

    [root@HW00001 home]# vi /etc/sysconfig/network-scripts/ifcfg-eth3

  6. Add the following commands to ifcfg-eth3:

    DEVICE=eth3
    ONBOOT=yes
    BOOTPROTO=none
    TYPE=Ethernet
    MASTER=bond0
    SLAVE=yes
    USERCTL=no
    STARTMODE=hotplug

  7. Save and close the ifcfg-eth3 file.
  8. In the /etc/sysconfig/network-scripts/ directory, create a file named ifcfg-bond0.

    [root@ HW00001 home]# vi /etc/sysconfig/network-scripts/ifcfg-bond0

  9. Add the following commands to ifcfg-bond0:

    DEVICE=bond0
    BONDING_MASTER=yes
    BONDING_MODULE_OPTS=mode=2 miimon=100
    BOOTPROTO=static
    IPADDR=10.5.2.10
    NETMASK=255.255.240.0
    MTU=1500
    NAME='Emulex OneConnect 10Gb NIC eth2-eth3'
    STARTMODE=auto
    USERCONTROL=no
    BONDING_SLAVE0=eth2
    BONDING_SLAVE1=eth3

  10. Save and close the ifcfg-bond0 file.
  11. Repeat steps 3 to 10 to create bond1.
  12. Create gateway, In the /etc/sysconfig/ directory, run vi network.

    [root@ HW00001 sysconfig] # vi network
    GATEWAY=10.10.1.254

  13. Configure all network IP addresses of the two servers in the same way.

Configuration on the CLI (Applicable to Redhat7.2)

NOTE:

This section uses port bond0 (physical ports ens4f0, ens6f0) as an example to describe how to configure network IP addresses.

  1. Run nmcli con add type bond ifname bond0 mode balance-xor , create bond0.

    nmcli con add type bond ifname bond0 mode balance-xor

  2. Run nmcli connection modify bond-bond0 ipv4.addresses 10.5.2.10/24 ,Add IP address to bond0.

    nmcli connection modify bond-bond0 ipv4.addresses 10.5.2.10/24

  3. Run nmcli connection modify bond-bond0 ipv4.method manual.

    nmcli connection modify bond-bond0 ipv4.method manual

  4. Run nmcli con add type bond-slave ifname ens4f0 master bond-bond0, please use the actual name to replace ens4f0.

    nmcli con add type bond-slave ifname ens4f0 master bond-bond0

  5. Run nmcli con add type bond-slave ifname ens6f0 master bond-bond0 , please use the actual name to replace ens6f0.

    nmcli con add type bond-slave ifname ens6f0 master bond-bond0

  6. Run nmcli connection show to check the configuration information:

    bond-slave-ens4f0  1c88d785-b280-4999-96d5-237d4e761e43  802-3-ethernet  ens4f0
    bond-slave-ens6f0  e6845549-b897-4cb8-9487-9004c71e3741  802-3-ethernet  ens6f0
    bond-bond0          5a3cb631-be4c-44d5-ae9a-95b01d6a6c03  bond            bond0

  7. Repeat steps 1 to 6 to create bond1.
  8. Create gateway , In the /etc/sysconfig/ directory, run vi network .

    [root@ HW00001 sysconfig] # vi network
    GATEWAY=10.10.1.254

  9. Run /etc/init.d/network restart to restart the network.
  10. Configure all network IP addresses of the two servers in the same way.
Translation
Download
Updated: 2019-05-14

Document ID: EDOC1100019155

Views: 18141

Downloads: 94

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next