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

eSight V300R010C00 Maintenance Guide 07

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).
OMMHA Local HA System

OMMHA Local HA System

This section describes common FAQs related to maintenance of the OMMHA HA system and provides reference information.

How Do I Distinguish the Active Server from the Standby One

Question

How do I determine which server is the active one and which server is the standby one?

Answer
  1. Log in to either of the two servers as ossuser.
  2. Run the following command to view the two-node cluster status:

    > cd /opt/ommha/ha/bin

    > ./status.sh

    HAMode                                                                            
    double                                   
                                             
    NodeName  HostName        HAVersion       StartTime    HAActive        HAAllResOK  HARunPhase          
    ha1       eSightServer40  V100R001C01     2017-09-16   active          normal      Actived             
    ha2       eSightServer46  V100R001C01     2017-09-16   standby         normal      Deactived           
                                             
    NodeName  ResName         ResStatus       ResHAStatus  ResType        
    ha1       MySQL           Active_normal   Normal       Active_standby 
    ha1       NMSServer       Normal          Normal       Single_active  
    ha1       RMFloatIp       Normal          Normal       Single_active  
    ha2       MySQL           Standby_normal  Normal       Active_standby 
    ha2       NMSServer       Stopped         Unknown      Single_active  
    ha2       RMFloatIp       Stopped         Normal       Single_active  

    The status of eSightServer40 is active, indicating that eSightServer40 is the active server, while eSightServer46 is the standby server.

How Do I View the Two-Node Cluster Status

Question

How do I view the running status of the two-node cluster?

Answer
  1. Log in to the server of which the status you want to query as ossuser.
  2. Run the following command to view the two-node cluster status:

    > cd /opt/ommha/ha/bin

    > ./status.sh

    HAMode                                                                            
    double                                   
                                             
    NodeName  HostName        HAVersion       StartTime    HAActive        HAAllResOK  HARunPhase          
    ha1       eSightServer40  V100R001C01     2017-09-16   active          normal      Actived             
    ha2       eSightServer46  V100R001C01     2017-09-16   standby         normal      Deactived           
                                             
    NodeName  ResName         ResStatus       ResHAStatus  ResType        
    ha1       MySQL           Active_normal   Normal       Active_standby 
    ha1       NMSServer       Normal          Normal       Single_active  
    ha1       RMFloatIp       Normal          Normal       Single_active  
    ha2       MySQL           Standby_normal  Normal       Active_standby 
    ha2       NMSServer       Stopped         Unknown      Single_active  
    ha2       RMFloatIp       Stopped         Normal       Single_active  

What Can I Do If the MySQL Database on the Standby Server Does Not Start After the Post-processing Script Is Executed in an OMMHA Incremental Two-Node Installation Scenario

Question

What can I do if the MySQL database on the standby server does not start after the post-processing script (install_post.sh) is executed in an OMMHA incremental two-node installation scenario?

Answer
  1. Log in to the active server as the root user.
  2. Re-execute the pre-processing script install_pre.sh in the directory where the installation file is stored.

    # cd Installation file directory

    # sh install_pre.sh

  3. Re-execute the post-processing script install_post.sh in the directory where the installation file is stored.

    # sh install_post.sh

    If the following information is displayed, the MySQL database on the standby server is started properly:

    HAMode                                                                            
    double                                   
                                             
    NodeName  HostName        HAVersion       StartTime    HAActive        HAAllResOK  HARunPhase          
    ha1       eSightServer40  V100R001C01     2017-09-16   active          normal      Actived             
    ha2       eSightServer46  V100R001C01     2017-09-16   standby         normal      Deactived           
                                             
    NodeName  ResName         ResStatus       ResHAStatus  ResType        
    ha1       MySQL           Active_normal   Normal       Active_standby 
    ha1       NMSServer       Normal          Normal       Single_active  
    ha1       RMFloatIp       Normal          Normal       Single_active  
    ha2       MySQL           Standby_normal  Normal       Active_standby 
    ha2       NMSServer       Stopped         Unknown      Single_active  
    ha2       RMFloatIp       Stopped         Normal       Single_active  

What Can I Do If a Message Indicating an Invalid License Is Displayed After the Active/Standby Switchover of the OMMHA Two-Node Cluster

Question

A license has been imported to the OMMHA two-node cluster. However, after the active/standby switchover, the license becomes invalid. How can I deal with this problem?

Answer

Re-import the license.

What Can I Do If the Local System IP Address Is Unavailable After I Install the OMMHA Two-Node Cluster System with an Image File?

Question

After I install the OMMHA two-node cluster system with an image file, the message "Local system ip is not available" is displayed. How can I deal with this problem?

Answer
  1. Log in to the active server as the root user.
  2. Check whether the system IP address of the active server is normal.

    # ifconfig

    Check whether the IP address and connection information are consistent, as shown in Figure 7-4 .

    Figure 7-4 Network information
    • If no, connect the active node to the standby node again and enter correct connection information,3.
    • If yes, the network may be abnormal. Connect the active node to the standby node again,3. If the fault persists, contact Huawei engineers for troubleshooting.
  3. Connect the active server to the standby server.

    For details about the connection, see "Installation and Commissioning > Local High Availability System Software Installation Guide (SUSE Linux + MySQL + OMMHA) > Installing the eSight System (Image Installation) > Connecting the Active and Standby Servers" in the eSight Product Documentation.

How Do I Change the Default Route Network Adapter of the OMMHA Two-Node Cluster Image

Question

If the image disc is used for installation, eSight uses eth0 to communicate with the external network by default. If the network adapter used for communicating with the external network is not eth0, change the default route network adapter to the network adapter connected to the external network.

Answer
  1. Stop eSight.
  2. Log in to the active eSight server as the root user using PuTTY.
  3. Run the following command to switch to the /etc/sysconfig/network directory:

    # cd /etc/sysconfig/network

  4. Disable the default network adapter eth0.

    1. Access the VIM editor.

      # vim ifcfg-eth0

    2. Use arrow keys to move the cursor to the line where DHCLIENT_SET_DEFAULT_ROUTE= is located.
    3. Press i, move the cursor to the line where DHCLIENT_SET_DEFAULT_ROUTE is located, and change the value to no.
      DHCLIENT_SET_DEFAULT_ROUTE='no'
    4. Press Esc and enter :wq to exit the VIM editor.

  5. Open the new network adapter. (The following describes how to change eth1 to the default route network adapter as an example.)

    1. Access the VIM editor.

      # vim ifcfg-eth1

    2. Use arrow keys to move the cursor to the line where DHCLIENT_SET_DEFAULT_ROUTE= is located.
    3. Press i, move the cursor, and change the value of DHCLIENT_SET_DEFAULT_ROUTE to yes.
      DHCLIENT_SET_DEFAULT_ROUTE='yes'
    4. Press Esc and enter :wq to exit the VIM editor.

  6. Run the following command to restart the network service:

    # service network restart

  7. Log in to the standby eSight server as the root user using PuTTY.
  8. Perform 3 to 6 on the standby eSight server.
  9. Start eSight.

How Do I Obtain the System IP Addresses of the Active and Standby Servers

Question

How do I obtain the system IP addresses of the active and standby servers?

Answer
  1. Log in to the eSight server through the floating IP address of eSight. The server that is logged in to is the active server.
  2. Obtain the system IP addresses of the active and standby servers.

    # cat /opt/eSight/mttools/ha/var/ServerMode.xml

    <?xml version="1.0" encoding="utf-8"?>
    <root>
      <Server name="">
        <ip>10.137.116.89</ip>
      </Server>
      <Server name="">
        <ip>10.137.116.88</ip>
      </Server>
    </root>

    The IP addresses in the <ip> tags are the system IP addresses of the active and standby servers.

  3. Obtain the system IP address of the current active server.

    Run the following command as the root user to obtain all IP addresses of the current active server:

    # ip addr

    2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
        link/ether 00:0c:29:9d:4d:51 brd ff:ff:ff:ff:ff:ff
        inet 10.137.116.88/24 brd 10.137.116.255 scope global eth0

    In the information, if the IP address next to inet is the same as an IP address obtained in 2, the IP address is the system IP address of the active server. The other IP address obtained in 2 is the system IP address of the standby server.

How Do I Change the Host Name, Route, or IP Address

Question

How do I change the host name, route, or IP address of the eSight VM based on the network division?

Answer

You can perform operations in Changing the IP Address to change the IP address of the operating system, perform operations in Modifying the Route Information to modify the route information, and perform operations in Changing the Host Name to change the host name.

  • The following uses the active server as an example. After the operations are complete, perform the operations again on the standby server.
  • After the VM IP address is changed, you need to change the corresponding IP address on eSight.
  • Changing the IP Address
    1. Log in to the active eSight server as the root user using VNC.
    2. Go to the Network Settings window.
      1. Right-click on the system desktop and choose Open Terminal from the shortcut menu.
      2. In the command terminal window, run the yast2 lan command to go to the Network Settings window.

    3. Change the IP address and mask. The IPv6 address is used as an example.
      Assume that the network port corresponding to the system IP address is eth0, the IPv6 address is 3094::20, and the subnet mask is 64.
      1. On the Overview tab page, delete all default network settings.

        Select each network setting record and click Delete.

      2. Select the NIC where eth0 is located and click Edit.
      3. In the Network Card Setup window that is displayed, select Statically Assigned IP Address, set IP Address, Subnet Mask, and Hostname, and click Next.
        NOTE:
        • In a local HA system, if eSight is installed using the FusionSphere OpenStack OM, obtain the heartbeat and replication IP address based on Local High Availability System Software Installation Guide (SUSE Linux + MySQL + OMMHA) >

          Installing eSight Using the FusionSphere OpenStack OM (Full Image) > Installing eSight in Full Image Mode > Querying the Heartbeat and Replication IP Address.

        • In a remote HA system, if eSight is installed using the FusionSphere OpenStack OM, obtain the heartbeat and replication IP address based on Remote High Availability System Software Installation Guide (SUSE Linux + MySQL + OMMHA) > Installing the eSight Using the FusionSphere OpenStack OM (Full Image) > Installing eSight in Full Image Mode > Querying the Heartbeat and Replication IP Address.

      4. Repeat 3.a to 3.c to set the heartbeat and replication IP address and the southbound IP address.
        NOTE:

        The southbound IP address needs to be set only in the southbound and northbound service isolation scenario.

      5. Click OK to complete the IP address and mask settings.
    4. (Optional) In the new installation scenario where the IPv6 address is used, perform the following operations to change the value of net.ipv6.conf.default.accept_ra to 0:
      1. Open the /etc/sysctl.conf file.

        # vi /etc/sysctl.conf

      2. Press i to enter the editing mode.
        Change the value of net.ipv6.conf.default.accept_ra to 0.
        net.ipv6.conf.default.accept_ra = 0
      3. Press Esc to exit the editing mode, and run the :wq command to save and exit the file.
      4. Run the following commands for the modification to take effect:

        # sysctl -p

        # rcnetwork restart

      5. Run the following command to check whether the configuration takes effect:

        # ifconfig

        The IP address of the NIC must be the same as that configured in 3.

        eth0      Link encap:Ethernet  HWaddr FA:16:3E:3F:F2:42
                  inet6 addr: fe80::f816:3eff:fe3f:f242/64 Scope:Link
                  inet6 addr: 3094::20/64 Scope:Global
                  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
                  RX packets:208814 errors:0 dropped:0 overruns:0 frame:0
                  TX packets:118724 errors:0 dropped:0 overruns:0 carrier:0
                  collisions:0 txqueuelen:1000
                  RX bytes:24729332 (23.5 Mb)  TX bytes:19400634 (18.5 Mb)
  • Modifying the Route Information
    1. Log in to the active eSight server as the root user using VNC.
    2. Go to the Network Settings window.
      1. Right-click on the system desktop and choose Open Terminal from the shortcut menu.
      2. In the command terminal window, run the yast2 lan command to go to the Network Settings window.

    3. If the heartbeat and replication IP address and southbound IP address are not in the same network segment as the default IPv6 gateway set on Network Settings > Routing, set the routing information.

      Assume that the heartbeat NIC is eth1, the destination IP address is ff00::0, the subnet mask is 64, and the gateway is 3093::1.

      1. Click Add in the Routing Table area on the Routing tab page.
      2. Set Destination, Genmask, Gateway, and Device.

      3. Click OK.

      4. (Optional) In the southbound and northbound service isolation scenario, configure the southbound routing information based on 3.a to 3.c.
      5. Click OK.
      6. In the command terminal window, run the yast2 lan command to go to the Network Settings window. Check whether configurations are consistent with the plan.
    4. Configure the default gateway.

      The default IPv6 gateway 3094::1 is used as an example.

      1. In the Network Settings window, click the Routing tab.
      2. Set Default IPv6 Gateway based on the plan and click OK to set the default IPv6 gateway.

  • Changing the Host Name
    1. Log in to the active eSight server as the root user using VNC.
    2. Go to the Network Settings window.
      1. Right-click on the system desktop and choose Open Terminal from the shortcut menu.
      2. In the command terminal window, run the yast2 lan command to go to the Network Settings window.

    3. Change the host name of the operating system.
      1. On the Hostname/DNS tab change, change the host name.
        NOTE:
        • Different host names must be configured for the active and standby servers. For example, the active server name is eSightServer1 and the standby server name is eSightServer2.
        • If FusionSphere OpenStack OM is used for deployment, the host name of the VM operating system must be the same as the VM name set during VM creation.
        • If ManageOne ServiceCenter is used for deployment, the host name of the VM operating system must be the same as the cloud host name set during VM creation.

      2. In the Network Settings window, click the Routing tab.
      3. Select the NIC where eth0 is located and click Edit.
      4. In the Network Card Setup window, select Statically Assigned IP Address, set Hostname to that configured in 3.a, and click Next.

      5. Repeat 3.c to 3.d set the host names of other NICs in sequence.
      6. Click OK.

How Do I Obtain the Heartbeat IP Addresses and Floating IP Address of the Active and Standby Servers

Question

How do I obtain the heartbeat IP addresses and floating IP address of the active and standby servers?

Answer
  1. Log in to the active server as the root user.
  2. Obtain the heartbeat IP addresses of the active and standby servers.

    # cat /opt/ommha/ha/module/haarb/conf/haarb.xml
    eSightServer1:/opt/install # cat /opt/ommha/ha/module/haarb/conf/haarb.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <haarb>  
    <link>
    <ippair>
    <node name="ha1" ip="192.168.116.89" port="31841"></node>
    <node name="ha2" ip="192.168.116.88" port="31841"></node>
    </ippair>
     </link>
    </haarb>

  3. Obtain the floating IP address of the active and standby servers.

    # cat /opt/ommha/ha/module/harm/plugin/conf/RMFloatIp.xml

    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
    <resources>        
    <resource name="RMFloatIp">        
    <params>
    <param name="floatIp" show="no" value="10.136.246.185"/>
    <param name="floatPort" show="no" value="eth0:1"/>
    <param name="mask" show="no" value="255.255.255.0"/>        
    </params>        
    </resource>
    </resources>

Translation
Download
Updated: 2019-06-30

Document ID: EDOC1100044373

Views: 24850

Downloads: 74

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