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 V100R006C10 Block Storage Service Troubleshooting Guide 04

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).
Failed to Change the FSM Management IP Address

Failed to Change the FSM Management IP Address

Symptom

A failure message is displayed when the user changes the management IP address of the FusionStorage Manager (FSM) node or changes the management IP addresses of both FSM and FusionStorage Agent (FSA) nodes at the same time on the FusionStorage Block Self-Maintenance Platform.

Possible Causes

  • Failed to change the IP address of the Operation and Maintenance Management (OMM) component.
  • Failed to modify the configuration file of the FSA node.
  • Failed to modify the configuration file and change the management IP address of the FSM node.

Fault Diagnosis

None

Procedure

    Obtain parameters required for changing the management IP address.

    1. Log in to the FSM node.

      If the FSM node is deployed on a VM, log in to the FSM node using Virtual Network Computing (VNC). If the FSM node is deployed on a physical server, log in to the FSM node using the baseboard management controller (BMC) of the server as user dsware.

      NOTE:
      The default password of user dsware is IaaS@OS-CLOUD9!, and the default password of user root is IaaS@OS-CLOUD8!.

    2. Run the following command and enter the password of user root to switch to user root:

      su - root

    3. Run the following command to obtain parameters required for changing the management IP address:

      grep "/cluster/managerip/modify" /var/log/dsware/manager/log-fsm-audit.log

      Information similar to the following is displayed:

      [2015-09-09 19:10:09,044] [Request] [user=admin] [ip=192.168.40.253] [url=/cluster/managerip/modify; method=POST; msg={"netPlaneType":"external","gateway":"192.168.40.1","netMask":"255.255.254.0","om_active_ip":"192.168.40.15","om_standby_ip":"192.168.40.16","om_float_ip":"192.168.40.14","hosts":[{"old_net_addr":"192.168.40.11","new_net_addr":"192.168.40.21"},{"old_net_addr":"192.168.40.12","new_net_addr":"192.168.40.22"}]}]
      [2015-09-09 19:10:38,417] [Response] [url=/cluster/managerip/modify; resultCode=200; msg={"result":1,"detail":[{"ip":"192.168.40.12","errorCode":32501020,"description":"Failed to change the management IP address."}]}]
      

      Table 4-1 describes the parameters contained in the Request message in the command output.

      In the command output, the Response message shows the IP address of the failed node and provides details about the failure.

      NOTE:
      If the command output contains multiple IP address change records, obtain the latest record.
      Table 4-1  Parameters

      Parameter

      Example Value

      Description

      Parameter 1

      netPlaneType=external

      Specifies the network plane type of the IP address to be changed. The value can be internal or external. external indicates that the external network plane IP address is to be changed, and internal indicates that the internal network plane IP address is to be changed.

      Parameter 2

      om_active_ip = 192.168.40.15

      Specifies the new IP address of the active FSM node.

      Parameter 3

      om_standby_ip = 192.168.40.16

      Specifies the new IP address of the standby FSM node.

      Parameter 4

      om_float_ip = 192.168.40.14

      Specifies the new floating IP address of the FSM nodes.

      Parameter 5

      gateway = 192.168.40.1

      Specifies the new gateway of the FSM nodes.

      Parameter 6

      netMask = 255.255.254.0

      Specifies the new subnet mask of the FSM nodes.

      Parameter 7

      hosts=[{old_net_addr = 192.168.40.11, new_net_addr = 192.168.40.21}, {old_net_addr = 192.168.40.12, new_net_addr = 192.168.40.22}]

      Specifies the old and new IP addresses of the FSA nodes.

    Obtain the old FSM floating IP address.

    1. Run the following command to switch to user omm:

      su - omm

    2. Run the following command to switch to the database command line interface (CLI):

      gsql -U omm -d omm -p 21600

      You are required to enter the password for logging in to the database. The default password of the database is IaaS@DATABASE-PublicCLOUD9!.

      The omm account will be locked for about 270 seconds in the event of three consecutive incorrect password attempts.

    3. Run the following commands to query the IP address in the OMM data table:

      set search_path=omm_1;

      select to_char(to_timestamp(blogtime), 'YYYY-MM-DD HH24:MI:SS') as start_time, detailinfo_en from tbl_operate_log where operatename_en ='Modify Manage IP' and operateresult = 1;

      NOTE:
      If the command output displayed is not complete, you can press the spacebar to view the next page. In addition, you can press q to exit the result view.

      Table 4-2 lists the command output. Multiple records may be displayed. You can obtain the management IP address based on the change time.

      If the DETAILINFO_EN field in the command output contains FSM Float IP, the first IP address after FSM Float IP is the old floating IP address of the FSM nodes.

      If the DETAILINFO_EN field in the command output does not contain FSM Float IP, the floating IP address is not changed.

      Table 4-2  Query result
      START_TIME DETAILINFO_EN
      2015-09-09 19:10:09

      FSM Float IP:

      192.168.61.14>192.168.61.24;

      Server IP List:

      192.168.61.10>192.168.62.10;…

    4. Enter \q to exit the database CLI.
    5. Run the following command to log out:

      exit

    Modify the configuration information of the FSM nodes.

    1. Run the following command on the current FSM node to check whether active is displayed in the command output:

      sh /opt/omm/oms/workspace/ha/module/hacom/script/get_harole.sh

      • If yes, go to 12.
      • If no, go to 10.

    2. Log in to the other FSM node.

      If the FSM node is deployed on a VM, log in to the FSM node using VNC. If the FSM node is deployed on a physical server, log in to the FSM node using the BMC of the server as user dsware.

    3. Run the following command and enter the password of user root to switch to user root:

      su - root

    4. Run the following command to switch to user omm:

      su - omm

    5. Run the following command to switch to the CLI:

      gsql -U omm -d omm -p 21600

      You are required to enter the password for logging in to the database. The default password of the database is IaaS@DATABASE-PublicCLOUD9!.

      The omm account will be locked for about 270 seconds in the event of three consecutive incorrect password attempts.

    6. Run the following commands to query the IP address in the OMM data table:

      set search_path=omm_1;

      select * from tbl_swm_serverinfo;

    7. Check whether the floating IP address and management IP addresses of active and standby FSM nodes as well as the OMA IP address in the data table are all the new management IP address.

      • If yes, go to 17.
      • If no, go to 16.

    8. Run the following command to change the floating IP address and management IP addresses of active and standby FSM nodes as well as the OMA IP address in the database:

      update tbl_swm_serverinfo set SRVIP = 'New management IP address' where SRVIP = 'Old management IP address';

      For example, run the following command: update tbl_swm_serverinfo set SRVIP = '192.168.40.20' where SRVIP = '192.168.40.10';

    9. Run the following commands to query the IP address in the FSM data table:

      set search_path=dsware_1;

      select * from tbl_server_info;

    10. Check whether the IP address in the FSM data table is the new management IP address.

      • If yes, go to 20.
      • If no, go to 19.

    11. Run the following command to change the IP address in the FSM database:

      update tbl_server_info set MANAGEIP = 'New management IP address' where MANAGEIP = 'Old management IP address';

      For example, run the following command: update tbl_server_info set MANAGEIP = '192.168.40.20' where MANAGEIP = '192.168.40.10';

    12. Enter \q to exit the database CLI.
    13. Run the following command to log out:

      exit

    14. Check whether the floating IP address has been changed based on the result in 6.

      • If yes, go to 23.
      • If no, go to 19.

    15. Perform required operations based on the network plane mode of the floating IP address that has been changed.

      NOTE:
      You can query the network plane mode using the cat /opt/dsware/manager/webapps/dsware/WEB-INF/manager-ha.properties | grep "double_plane" command. If double_plane=false is displayed, the FSM node is equipped with a single network plane.

      • If the FSM node is equipped with a single network plane, perform the following operations to change the floating IP address in the configuration file:

        1. Run the following command to change the floating IP address in the Tomcat configuration file:

          sed -i 's/address=".*"/address="New floating IP address"/' /opt/omm/oms/workspace/tomcat/conf/server.xml

          For example, run the following command:

          sed -i 's/address=".*"/address="192.168.40.14"/' /opt/omm/oms/workspace/tomcat/conf/server.xml

        2. Run the following command to change the IP address monitored by the FMS process:

          sed -i "s/thrift_server_ip=.*/thrift_server_ip=New floating IP address/" /opt/omm/oms/workspace/conf/fms/application.properties

          For example, run the following command:

          sed -i "s/thrift_server_ip=.*/thrift_server_ip=192.168.40.14/" /opt/omm/oms/workspace/conf/fms/application.properties

        3. Run the following command to change the IP address monitored by the PMS process:

          sed -i "s/thrift_server_ip=.*/thrift_server_ip=New floating IP address/" /opt/omm/oms/workspace/conf/pms/application.properties

          For example, run the following command:

          sed -i "s/thrift_server_ip=.*/thrift_server_ip=192.168.40.14/" /opt/omm/oms/workspace/conf/pms/application.properties

      • If the FSM node is equipped with dual planes and the external management plane IP address is changed, run the following command to change the floating IP address in the configuration file:

        sed -i 's/address=".*"/address="New floating IP address"/' /opt/omm/oms/workspace/tomcat/conf/server.xml

        For example, run the following command:

        sed -i 's/address=".*"/address="192.168.40.14"/' /opt/omm/oms/workspace/tomcat/conf/server.xml

      • If the FSM node is equipped with dual planes and the internal management plane IP address is changed, run the following command to change the floating IP address in the configuration file:

        1. Run the following command to change the IP address monitored by the FMS process:

          sed -i "s/thrift_server_ip=.*/thrift_server_ip=New floating IP address/" /opt/omm/oms/workspace/conf/fms/application.properties

          For example, run the following command:

          sed -i "s/thrift_server_ip=.*/thrift_server_ip=192.168.40.14/" /opt/omm/oms/workspace/conf/fms/application.properties

        2. Run the following command to change the IP address monitored by the PMS process:

          sed -i "s/thrift_server_ip=.*/thrift_server_ip=New floating IP address/" /opt/omm/oms/workspace/conf/pms/application.properties

          For example, run the following command:

          sed -i "s/thrift_server_ip=.*/thrift_server_ip=192.168.40.14/" /opt/omm/oms/workspace/conf/pms/application.properties

    16. Perform required operations based on the network plane mode of the IP address that has been changed.

      NOTE:
      You can query the network plane mode using the cat /opt/dsware/manager/webapps/dsware/WEB-INF/manager-ha.properties | grep "double_plane" command. If double_plane=false is displayed, the FSM node is equipped with a single network plane.

      • If the FSM node is equipped with a single network plane, or if it is equipped with dual planes and the external network plane IP address is changed, run the following command to change the IP address in the HA configuration file of the FSM node:

        sh /opt/dsware/manager/webapps/dsware/WEB-INF/script/modifyMgntIpInCfg.sh "Floating IP address" "IP address of the active FSM node" "IP address of the standby FSM node" "Subnet mask" "Gateway"

        If the floating IP address, IP address of the standby FSM node, or gateway does not exist, enter 255.255.255.255.

      • If the FSM node is equipped with dual planes and the internal network plane IP address is changed, run the following command to change the IP address in the HA configuration file of the FSM node:

        sh /opt/dsware/manager/webapps/dsware/WEB-INF/script/modifyInnerIpInCfg.sh "Floating IP address" "IP address of the active FSM node" "IP address of the standby FSM node" "Subnet mask" "Gateway"

        If the floating IP address, IP address of the standby FSM node, or gateway does not exist, enter 255.255.255.255.

    17. Run the following command to restart the HA process:

      sh /opt/omm/oms/workspace/ha/module/hacom/script/stop_ha.sh

    18. If active and standby FSM nodes are deployed, modify the configuration information of the other FSM node. For details, see 22 to 25.
    19. Check whether the IP addresses of FSA nodes are changed.

      • If yes, go to 28.
      • If no, no further action is required.

    Modify the configuration information of FSA nodes.

    1. Check the result based on the command output in 3.

      The FSA nodes fail the IP address change if their IP addresses are displayed in the Response message.

    2. Check whether the IP addresses of any FSA nodes fail to change.

      • If yes, go to 30.
      • If no, no further action is required.

    3. Use PuTTY to log in to the first failed FSA node.

      Ensure that the old management IP address of the FSA node is used to establish the connection.

    4. Run the su - root command to switch to user root.
    5. Check whether the floating IP address has been changed based on the result in 6.

      • If yes, go to 33.
      • If no, go to 42.

    6. Check whether the dsware_manager_ip value in the /opt/dsware/agent/conf/dsware_manager_ip file is the new floating IP address.

      If it is not, run the following command to change the IP address:

      sed -i "s/dsware_manager_ip=.*/dsware_manager_ip=New IP address/" /opt/dsware/agent/conf/dsware_manager_ip

    7. Check whether the SERVERIP value in the /opt/omm/oma/workspace/conf/servercfg.cfg file is the new floating IP address.

      If it is not, run the following command to change the IP address:

      sed -i "s/SERVERIP=.*/SERVERIP=New IP address/" /opt/omm/oma/workspace/conf/servercfg.cfg

    8. Check whether the SERVERIP value in the /opt/omm/oma/workspace/conf/upda.cfg file is the new floating IP address.

      If it is not, run the following command to change the IP address:

      sed -i "s/SERVERIP=.*/SERVERIP=New IP address/" /opt/omm/oma/workspace/conf/upda.cfg

    9. Check whether the old floating IP address exists in the /opt/dsware/agent/conf/dsware_cluster_info file.

      If it does, run the following command to change the IP address:

      sed -i "s/Old floating IP address/New floating IP address/" /opt/dsware/agent/conf/dsware_cluster_info

    10. Check whether the old floating IP address exists in the /opt/dsware/vbs/conf/vbs_cluster_info file.

      If it does, run the following command to change the IP address:

      sed -i "s/Old floating IP address/New floating IP address/" /opt/dsware/vbs/conf/vbs_cluster_info

    11. Check whether the vbs_Old floating IP address_conf.cfg configuration file exists in the /opt/dsware/vbs/conf/ directory.

      If it does, run the following command to rename the file:

      mv /opt/dsware/vbs/conf/vbs_Old floating IP address_conf.cfg /opt/dsware/vbs/conf/vbs_New floating IP address_conf.cfg

    12. Run the sh /opt/dsware/agent/script/dswareAgent_tool.sh restart command to restart the FSA process.
    13. Check whether the volume_attach_inf configuration file exists in the /opt/dsware/agent/conf/ directory.

      • If yes, go to 41.
      • If no, go to 42.

    14. Check whether the old floating IP address exists in the volume_attach_inf file.

      If the old floating IP address exists, run the following command to change it:

      sed -i "s/Old floating IP address/New floating IP address/" /opt/dsware/agent/conf/volume_attach_inf

      After the modification is successful, restart the node OS. When the OS is restarted, run the lsscsi command to check whether the volume can be successfully attached.

    15. Check whether the node_manager_ip value in the /etc/node_manager_ip file is the new management IP address.

      If it is not, run the following command to change the IP address:

      sed -i "s/node_manager_ip=.*/node_manager_ip=New IP address/" /etc/node_manager_ip

    16. Check whether the LOCALIP value in the /opt/omm/oma/workspace/conf/servercfg.cfg file is the new management IP address.

      If it is not, run the following command to change the IP address:

      sed -i "s/LOCALIP=.*/LOCALIP=New IP address/" /opt/omm/oma/workspace/conf/servercfg.cfg

    17. Check whether the LOCALIP value in the /opt/omm/oma/workspace/conf/upda.cfg file is the new management IP address.

      If it is not, run the following command to change the IP address:

      sed -i "s/LOCALIP=.*/LOCALIP=New IP address/" /opt/omm/oma/workspace/conf/upda.cfg

    18. Run the following commands to restart FSA and OMA processes:

      sh /opt/dsware/agent/script/dswareAgent_tool.sh restart

      restart_oma_app

      NOTE:
      If the management IP address of the host accommodating the FSA node has not been changed, the processes fail to restart. Therefore, change the management IP address of the host in a timely manner. After the management IP address is changed, the FSA and OMA processes restart automatically.

    19. Modify the configuration information of other failed FSA nodes. For details, see 30 to 45.

Related Information

None

Translation
Download
Updated: 2019-02-01

Document ID: EDOC1000175245

Views: 3182

Downloads: 4

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