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

FusionStorage V100R006C30 Block Storage Service Disaster Recovery Feature Guide 03

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).
The Arbitration Plane Uses an Independent Network Port

The Arbitration Plane Uses an Independent Network Port

Prerequisites

Conditions

  • The local PC can properly communicate with the planned arbitration plane and the BMC plane of the server. The local PC and the server to be installed are connected to the same switch, and their IP addresses belong to the same quorum network segment.
  • You have obtained the BMC IP address, username, and password for logging in to the BMC system of the server.
  • The firewall on the local PC is disabled.

Data

  • Password of user root for logging in to the server
  • IP address for the arbitration plane of the server

Procedure

    1. Open a browser on the local PC, and enter http://BMC IP address of the server to be installed in the address bar, and press Enter to go to the login page.
    2. Log in to the server BMC system as instructed.

      The default username and password for logging in to the server BMC system is Administrator and Admin@9000, respectively.

      The server management page is displayed.

      NOTE:
      If a blade server is used, you cannot log in to the BMC system of a single blade. It is recommended that you log in to the management module (MM) of the subrack accommodating the blade and open the remote control window of the blade.

    3. Click Remote Control.

      For some Huawei servers, you must choose Remote Virtual Console (shared mode) on the Remote Control page to open the remote control window.

      The remote control window is displayed.

    4. Log in to the server as user root.
    5. Run one of the following commands based on the OS in use to switch to the directory containing the network port configuration file:

      • If the Red Hat, Oracle or CentOS is used, run the cd /etc/sysconfig/network-scripts command.
      • If the SUSE is used, run the cd /etc/sysconfig/network command.

    6. If the network port configuration file does not exist in the current directory, you can run the vi Configuration file name command to edit the file and then save the configuration. Then a network port configuration file will be created.

      NOTE:
      The following steps provide an example of configuring the network port configuration file using the vi editor:
      1. Run the vi Configuration file name command to open the network port configuration file using vi editor.

        For example, run the vi ifcfg-eth0 command.

      2. Press i to enter editing mode.
      3. Edit the configuration file.
      4. Press Esc and enter :wq to save the modification and exit the vi editor.

      Table 2-9  Network port configuration file information (using the bonded port)

      Configuration File Name

      Configuration File Content (Red Hat, Oracle, and CentOS)

      Configuration File Content (SUSE Linux OS)

      ifcfg-eth0

      DEVICE=eth0

      BOOTPROTO=none

      ONBOOT=yes

      MASTER=fsb_data1

      SLAVE=yes

      USERCTL=no

      DEVICE=eth0

      BOOTPROTO=static

      STARTMODE=onboot

      USERCONTROL=no

      ifcfg-eth1

      DEVICE=eth1

      BOOTPROTO=none

      ONBOOT=yes

      MASTER=fsb_data1

      SLAVE=yes

      USERCTL=no

      DEVICE=eth1

      BOOTPROTO=static

      STARTMODE=onboot

      USERCONTROL=no

      ifcfg-fsb_data1

      DEVICE=fsb_data1

      IPADDR=IP address

      NETMASK=subnet mask

      ONBOOT=yes

      BOOTPROTO=none

      USERCTL=no

      TYPE=Bonding

      MTU=1500

      BONDING_OPTS='mode=1 miimon=100'

      DEVICE=fsb_data1

      IPADDR=IP address

      NETMASK=subnet mask

      BOOTPROTO=static

      STARTMODE=onboot

      IPV6_DAD_WAIT=0

      BONDING_MASTER=yes

      BONDING_MODULE_OPTS='mode=1 miimon=100'

      BONDING_SLAVE0=eth0

      BONDING_SLAVE1=eth1

      Table 2-10  Network port configuration file information (using VLAN)

      Configuration File Name

      Configuration File Content (Red Hat, Oracle, and CentOS)

      Configuration File Content (SUSE Linux OS)

      ifcfg-eth0

      DEVICE=eth0

      BOOTPROTO=none

      ONBOOT=yes

      MASTER=fsb_bond0

      SLAVE=yes

      USERCTL=no

      DEVICE=eth0

      BOOTPROTO=static

      STARTMODE=onboot

      USERCONTROL=no

      ifcfg-eth1

      DEVICE=eth1

      BOOTPROTO=none

      ONBOOT=yes

      MASTER=fsb_bond0

      SLAVE=yes

      USERCTL=no

      DEVICE=eth1

      BOOTPROTO=static

      STARTMODE=onboot

      USERCONTROL=no

      ifcfg-fsb_bond0

      DEVICE=fsb_bond0

      IPADDR=IP address

      NETMASK=subnet mask

      ONBOOT=yes

      BOOTPROTO=none

      USERCTL=no

      TYPE=Bonding

      MTU=1500

      BONDING_OPTS='mode=1 miimon=100'

      DEVICE=fsb_bond0

      IPADDR=IP address

      NETMASK=subnet mask

      BOOTPROTO=static

      STARTMODE=onboot

      IPV6_DAD_WAIT=0

      BONDING_MASTER=yes

      BONDING_MODULE_OPTS='mode=1 miimon=100'

      BONDING_SLAVE0=eth0

      BONDING_SLAVE1=eth1

      ifcfg-vlanXXX

      DEVICE=vlanID /*Its value is consistent with the configuration file name, for example, vlan101.*/

      IPADDR=IP address

      NETMASK=subnet mask

      BOOTPROTO=none

      PHYSDEV=fsb_bond0

      ONBOOT=yes

      USERCTL=no

      VLAN=yes

      VLAN_ID=ID /*For example, 101*/

      DEVICE=vlanID /*Its value is consistent with the configuration file name, for example, vlan101.*/

      IPADDR=IP address

      NETMASK=subnet mask

      BOOTPROTO=static

      ETHERDEVICE=fsb_bond0

      STARTMODE=onboot

      IPV6_DAD_WAIT=0

      USERCONTROL=no

      VLAN=yes

      VLAN_ID=ID /*For example, 101*/

    7. Press Esc and enter :wq to save the modification and exit the vi editor.
    8. Run one of the following commands based on the in-use OS to edit the configuration file and configure the default gateway:

      • If the Red Hat 7.x is used, configure the default gateway in the network port configuration file. For example, run the vi /etc/sysconfig/network-scripts/ifcfg-fsb_bond command.
      • If the Red Hat 6.x, Oracle or CentOS is used, run the vi /etc/sysconfig/network command.
      • If the SUSE is used, run the vim /etc/sysconfig/network/routes command.

    9. Add the default gateway information of the arbitration plane in the configuration file.

      The following is an example:
      • RedHat, Oracle, CentOS: GATEWAY=192.168.40.1
      • SUSE: default 192.168.40.1

    10. Press Esc and enter :wq to save the modification and exit the vi editor.
    11. Run the following command to restart the network service:

      service network restart

    12. Use the method from 1 to 11 to configure the quorum IP address and default gateway for the node that uses the HyperMetro function.
Translation
Download
Updated: 2019-01-17

Document ID: EDOC1100044928

Views: 17602

Downloads: 34

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