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 V300R010C00SPC200, 300, and 500 Maintenance Guide 09

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).
Changing the IP Address and Host Name of an HA System (Veritas)

Changing the IP Address and Host Name of an HA System (Veritas)

Changing the IP Address and Host Name of a Local HA System (Veritas)

This section describes how to change the IP address and host name of a local HA system.

Prerequisites

Before the configuration, ensure that:

  • To change the IP address for a local HA system, you must disconnect the active server from the standby server. For details, see Disconnecting the Active and Standby Servers.
  • In a local HA system, you must change the floating IP addresses of both active and standby servers.

Procedure

  1. Log in to the operating system as the ossuser user.
  2. Stop the eSight maintenance tool.

    #cd /opt/eSight/mttools/bin

    #./stop-sysmon.sh

  3. Modify the system IP address of the operating system.

    1. Use the following command to switch to the configuration tool directory.

      cd /opt/eSight/mttools/tools

    2. Execute the following script to modify the System IP address of the operating system, as shown in Figure 3-14.

      ./hacheck.sh

      NOTE:

      After the configuration is complete, the network service of the operating system will be restarted. If the configuration is not performed on the management port, the connection may be interrupted after the network service is restarted. Use the new IP address to log in to the Linux server.

      Figure 3-14 Modify the System IP address

  4. Synchronize the changed IP address as the ossuser user.

    1. Stop eSight. For details, see Stopping the eSight Service.
    2. Ensure the floating IP address of the active site is online.
      NOTE:

      For details, see Bringing a Resource Online.

    3. Run the following commands to change the IP address of the management network system to the new system IP address.

      # su - ossuser

      # cd /opt/eSight/mttools/tools

      # ./ipchange.sh

    4. In the IP Address Tool dialog box that is displayed, select an eSight server IP address and click Modify.

    5. In the dialog box that is displayed, click Yes.

  5. Change the server IP address listened by the Oracle database.

    1. Switch to oracle user.

      # su - oracle

    2. Change the server IP address or host name in the listener.ora file.

      > cd $ORACLE_HOME/network/admin

      > vi listener.ora

      # listener.ora Network Configuration File: /opt/oracle/product/11.2/db_1/network/admin/listener.ora 
       # Generated by Oracle configuration tools. 
        
       SID_LIST_LISTENER = 
         (SID_LIST = 
           (SID_DESC = 
             (GLOBAL_DBNAME = eSight) 
             (SID_NAME = eSight) 
           ) 
         ) 
        
       LISTENER = 
         (DESCRIPTION_LIST = 
           (DESCRIPTION = 
             (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521)) 
           ) 
           (DESCRIPTION = 
             (ADDRESS = (PROTOCOL = TCP)(HOST = eSightServer)(PORT = 31521)) 
           ) 
         ) 
       DYNAMIC_REGISTRATION_LISTENER = OFF 
       INBOUND_CONNECT_TIMEOUT_LISTENER = 1800

      Set the IP address or host name following HOST to the new IP address or host name.

    3. Restart the listener for the Oracle database.
      1. Stop the listener. For details, see Taking a Resource Group Offline.
      2. Start the listener. For details, see Bringing a Resource Group Online.

  6. After the IP address is changed, bring the FloatIP resource group offline.

    # hares -offline FloatIP -sys <hostname>

  7. Repeat 4.b to 6 to change the floating IP address for the standby server, IP address of the eSight system, and listening IP address of the database.
  8. Connect the primary and secondary servers. For details, see Connecting the Active and Standby Servers.
  9. Bring the AppService service group online and restart eSight.
  10. (Optional) If a distributed server is deployed on the network, perform the following operations to change its IP address:

    1. Log in to the active distributed node as the root user. Run the following commands to bring the AppService resource group offline on the active distributed node:

      hagrp -offline AppService -sys Host name of the active distributed node

      NOTE:

      Run the following commands to check the status of the AppService resource group. Perform the subsequent operations only when the resource group is in OFFLINE state.

      hagrp -state AppService -sys Server host name

    2. Run the following command to separate distributed nodes as the ossuser user.

      su - ossuser

      cd /opt/eSight/mttools/tools/distributed

      ./splitHA.sh

    3. Log in to the active and standby distributed nodes as the ossuser user. Run the following commands to start the connection tool:

      cd opt/eSight/mttools/tools

      ./connect_tool.sh

    4. Configure the IP address information as prompted.
      NOTE:

      Do not close the window during the configuration.

      • In the southbound and northbound non-isolation scenario, set the floating IP address and SSH password of eSight and click OK in the dialog box that is displayed.
      • In the southbound and northbound isolation scenario, set the southbound floating IP address and SSH password of eSight and click OK in the dialog box that is displayed.
    5. Log in to the active distributed node as the ossuser user. Run the following command to connect the active and standby nodes:

      cd /opt/eSight/mttools/tools/distributed

      ./joinHA.sh

      Please input peer heartbeat ip:
      Please input ossuser's password:
      connect success.
    6. Log in to the active distributed node as the root user. Run the following commands to bring the AppService resource group online on the active distributed node:

      hagrp -online AppService -sys Host name of the active distributed node

Changing the Southbound IP Address of a Local HA System (Veritas)

This section describes how to modify and roll back the southbound IP address of a local HA system.

Prerequisites

  • eSight has been stopped. See Stopping the eSight Service.
  • The mountFileRes, APPBOND, and RVGPrimary resource groups on the active and standby servers are online. For details, see Bringing a Resource Group Online.
  • The southbound IP address has been used to set bond2. For details, see "FAQ and Troubleshooting > How to Set the Network Adapter Binding" in the Local High Availability System Software Installation Guide (SUSE Linux + Oracle + Veritas).

Modification Procedure

  1. Log in to the active eSight server as the ossuser user.
  2. Run the following commands.

    > cd /opt/eSight/mttools/tools

    > sh hatool.sh southip

    Start Config southip... 
    Enter 'y' to apply the enable of South IP or 'n' to disable (y/n)

  3. Enter y and set the southbound IP address, network adapter, and subnet mask as prompted.

    If the following information is displayed, the modification is successful:

    Please input south floatip address: 
    192.168.3.162 
    Please input south ip netmask: 
    255.255.255.0 
    start add VCS resouce... 
    end add VCS resouce... 
    Config southip finish...

  4. Follow the Taking a Resource Group Offline chapter to bring the AppService resource offline.
  5. Log in to the standby server as the ossuser user and repeat 1 through 4.
  6. Log in to the active eSight server and follow the Bringing a Resource Group Online chapter to bring the AppService resource group online.
  7. (Optional) If a distributed server is deployed on the network, perform the following operations to change its IP address:

    1. Log in to the active distributed node as the root user. Run the following commands to bring the AppService resource group offline on the active distributed node:

      hagrp -offline AppService -sys Host name of the active distributed node

      NOTE:

      Run the following commands to check the status of the AppService resource group. Perform the subsequent operations only when the resource group is in OFFLINE state.

      hagrp -state AppService -sys Server host name

    2. Run the following command to separate distributed nodes as the ossuser user.

      su - ossuser

      cd /opt/eSight/mttools/tools/distributed

      ./splitHA.sh

    3. Log in to the active and standby distributed nodes as the ossuser user. Run the following commands to start the connection tool:

      cd opt/eSight/mttools/tools

      ./connect_tool.sh

    4. Configure the IP address information as prompted.
      NOTE:

      Do not close the window during the configuration.

      • In the southbound and northbound non-isolation scenario, set the floating IP address and SSH password of eSight and click OK in the dialog box that is displayed.
      • In the southbound and northbound isolation scenario, set the southbound floating IP address and SSH password of eSight and click OK in the dialog box that is displayed.
    5. Log in to the active distributed node as the ossuser user. Run the following command to connect the active and standby nodes:

      cd /opt/eSight/mttools/tools/distributed

      ./joinHA.sh

      Please input peer heartbeat ip:
      Please input ossuser's password:
      connect success.
    6. Log in to the active distributed node as the root user. Run the following commands to bring the AppService resource group online on the active distributed node:

      hagrp -online AppService -sys Host name of the active distributed node

Rollback Procedure

  1. Log in to the active eSight server as the ossuser user.
  2. Run the following commands.

    > cd /opt/eSight/mttools/tools

    > sh hatool.sh southip

    Start Config southip... 
    Enter 'y' to apply the enable of South IP or 'n' to disable (y/n)

  3. Enter n.

    If the following information is displayed, the rollback is successful:

    Disable southip for local ha system... 
    Config southip finish...

  4. Follow the Taking a Resource Group Offline chapter to bring the AppService resource offline.
  5. Log in to the standby server as the ossuser user and repeat 1 through 4.
  6. Log in to the active eSight server and follow the Bringing a Resource Group Online chapter to bring the AppService resource group online.
  7. (Optional) If a distributed node is deployed on the network, change the IP address of the distributed node by referring to 7.

Changing the IP Address and Host Name of a Remote HA System (Veritas)

This section describes how to change the IP address of a remote HA system.

Prerequisites

Before the configuration, ensure that:

  • To change the IP address for a remote HA system, you must disconnect the active server from the standby server. For details, see Disconnecting the Active and Standby Servers.
  • The method for changing the system IP address on the active and standby servers is the same.

Procedure

  1. Log in to the operating system as the ossuser user.
  2. Stop the eSight maintenance tool.

    #cd /opt/eSight/mttools/bin

    #./stop-sysmon.sh

  3. Modify the system IP address of the operating system.

    1. Use the following command to switch to the configuration tool directory.

      cd /opt/eSight/mttools/tools

    2. Execute the following script to modify the System IP address of the operating system, as shown in Figure 3-15.

      ./hacheck.sh

      NOTE:

      After the configuration is complete, the network service of the operating system will be restarted. If the configuration is not performed on the management port, the connection may be interrupted after the network service is restarted. Use the new IP address to log in to the Linux server.

      Figure 3-15 Modify the System IP address

  4. Synchronize the changed IP address.

    1. Stop eSight, see Stopping the eSight Service.
    2. Run the following commands to change the IP address of the management network system to the new system IP address.

      # cd /opt/eSight/mttools/tools

      # ./ipchange.sh

    3. In the IP Address Tool dialog box that is displayed, select an eSight server IP address and click Modify.

    4. In the dialog box that is displayed, click Yes.

  5. Change the server IP address listened by the Oracle database.

    1. Switch to oracle user.

      # su - oracle

    2. Change the server IP address or host name in the listener.ora file.

      > cd $ORACLE_HOME/network/admin

      > vi listener.ora

      # listener.ora Network Configuration File: /opt/oracle/product/11.2/db_1/network/admin/listener.ora 
       # Generated by Oracle configuration tools. 
        
       SID_LIST_LISTENER = 
         (SID_LIST = 
           (SID_DESC = 
             (GLOBAL_DBNAME = eSight) 
             (SID_NAME = eSight) 
           ) 
         ) 
        
       LISTENER = 
         (DESCRIPTION_LIST = 
           (DESCRIPTION = 
             (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521)) 
           ) 
           (DESCRIPTION = 
             (ADDRESS = (PROTOCOL = TCP)(HOST = eSightServer)(PORT = 31521)) 
           ) 
         ) 
       DYNAMIC_REGISTRATION_LISTENER = OFF 
       INBOUND_CONNECT_TIMEOUT_LISTENER = 1800

      Set the IP address or host name following HOST to the new IP address or host name.

    3. Restart the listener for the Oracle database.
      1. Stop the listener. For details, see Taking a Resource Group Offline.
      2. Start the listener. For details, see Bringing a Resource Group Online.

  6. Repeat Step 1 to Step 5 to change the IP address for the standby server, IP address of the eSight system, and listening IP address of the database.
  7. Connect the primary and secondary servers. For details, see Connecting the Active and Standby Servers.
  8. Bring the AppService service group online and restart eSight.
  9. (Optional) If a distributed server is deployed on the network, perform the following operations to change its IP address:

    1. Log in to the active distributed node as the root user. Run the following commands to bring the AppService resource group offline on the active distributed node:

      hagrp -offline AppService -sys Host name of the active distributed node

      NOTE:

      Run the following commands to check the status of the AppService resource group. Perform the subsequent operations only when the resource group is in OFFLINE state.

      hagrp -state AppService -sys Server host name

    2. Run the following command to separate distributed nodes as the ossuser user.

      su - ossuser

      cd /opt/eSight/mttools/tools/distributed

      ./splitHA.sh

    3. Log in to the active and standby distributed nodes as the ossuser user. Run the following commands to start the connection tool:

      cd opt/eSight/mttools/tools

      ./connect_tool.sh

    4. Configure the IP address information as prompted.
      NOTE:

      Do not close the window during the configuration.

      • In the southbound and northbound non-isolation scenario, set the system IP address and SSH password of the active eSight server and click OK in the dialog box that is displayed.
      • In the southbound and northbound isolation scenario, set the southbound IP address and SSH password of the active eSight server and click OK in the dialog box that is displayed.
    5. Log in to the active distributed node as the ossuser user. Run the following command to connect the active and standby nodes:

      cd /opt/eSight/mttools/tools/distributed

      ./joinHA.sh

      Please input peer heartbeat ip:
      Please input ossuser's password:
      connect success.
    6. Log in to the active distributed node as the root user. Run the following commands to bring the AppService resource group online on the active distributed node:

      hagrp -online AppService -sys Host name of the active distributed node

Changing the Southbound IP Address of a Remote HA System (Veritas)

This section describes how to change and roll back the southbound IP address of a remote HA system.

Prerequisites

  • eSight has been stopped. See Stopping the eSight Service.
  • The mountFileRes, APPBOND, and RVGPrimary resource groups on the active and standby servers are online. For details, see Bringing a Resource Group Online.
  • The southbound IP address has been used to set bond2. For details, see "FAQ and Troubleshooting > How to Set the Network Adapter Binding" in the Local High Availability System Software Installation Guide (SUSE Linux + Oracle + Veritas).

Modification Procedure

  1. Log in to the active eSight server as the ossuser user.
  2. Run the following commands.

    > cd /opt/eSight/mttools/tools

    > sh hatool.sh southip

    Start Config southip... 
    Enter 'y' to apply the enable of South IP or 'n' to disable (y/n)

  3. Enter y and set the southbound IP address as prompted.

    If the following information is displayed, the modification is successful:

    Please input south ip address: 
    192.168.3.211 
    Config southip for remote ha system... 
    Config southip finish...

  4. Follow the Taking a Resource Group Offline chapter to bring the AppService resource offline.
  5. Log in to the standby server as the ossuser user and repeat 1 through 4.
  6. Log in to the active eSight server and follow the Bringing a Resource Group Online chapter to bring the AppService resource group online.
  7. (Optional) If a distributed server is deployed on the network, perform the following operations to change its IP address:

    1. Log in to the active distributed node as the root user. Run the following commands to bring the AppService resource group offline on the active distributed node:

      hagrp -offline AppService -sys Host name of the active distributed node

      NOTE:

      Run the following commands to check the status of the AppService resource group. Perform the subsequent operations only when the resource group is in OFFLINE state.

      hagrp -state AppService -sys Server host name

    2. Run the following command to separate distributed nodes as the ossuser user.

      su - ossuser

      cd /opt/eSight/mttools/tools/distributed

      ./splitHA.sh

    3. Log in to the active and standby distributed nodes as the ossuser user. Run the following commands to start the connection tool:

      cd opt/eSight/mttools/tools

      ./connect_tool.sh

    4. Configure the IP address information as prompted.
      NOTE:

      Do not close the window during the configuration.

      • In the southbound and northbound non-isolation scenario, set the system IP address and SSH password of the active eSight server and click OK in the dialog box that is displayed.
      • In the southbound and northbound isolation scenario, set the southbound IP address and SSH password of the active eSight server and click OK in the dialog box that is displayed.
    5. Log in to the active distributed node as the ossuser user. Run the following command to connect the active and standby nodes:

      cd /opt/eSight/mttools/tools/distributed

      ./joinHA.sh

      Please input peer heartbeat ip:
      Please input ossuser's password:
      connect success.
    6. Log in to the active distributed node as the root user. Run the following commands to bring the AppService resource group online on the active distributed node:

      hagrp -online AppService -sys Host name of the active distributed node

Rollback Procedure

  1. Log in to the active eSight server as the ossuser user.
  2. Run the following commands.

    > cd /opt/eSight/mttools/tools

    > sh hatool.sh southip

    Start Config southip... 
    Enter 'y' to apply the enable of South IP or 'n' to disable (y/n)

  3. Enter n.

    If the following information is displayed, the rollback is successful:

    Disable southip for local ha system... 
    Config southip finish...

  4. Follow the Taking a Resource Group Offline chapter to bring the AppService resource offline.
  5. Log in to the standby server as the ossuser user and repeat 1 through 4.
  6. Log in to the active eSight server and follow the Bringing a Resource Group Online chapter to bring the AppService resource group online.
  7. (Optional) If a distributed server is deployed on the network, perform the following operations to change its IP address:

    1. Log in to the active distributed node as the root user. Run the following commands to bring the AppService resource group offline on the active distributed node:

      hagrp -offline AppService -sys Host name of the active distributed node

      NOTE:

      Run the following commands to check the status of the AppService resource group. Perform the subsequent operations only when the resource group is in OFFLINE state.

      hagrp -state AppService -sys Server host name

    2. Run the following command to separate distributed nodes as the ossuser user.

      su - ossuser

      cd /opt/eSight/mttools/tools/distributed

      ./splitHA.sh

    3. Log in to the active and standby distributed nodes as the ossuser user. Run the following commands to start the connection tool:

      cd opt/eSight/mttools/tools

      ./connect_tool.sh

    4. Configure the IP address information as prompted.
      NOTE:

      Do not close the window during the configuration.

      • In the southbound and northbound non-isolation scenario, set the floating IP address and SSH password of eSight and click OK in the dialog box that is displayed.
      • In the southbound and northbound isolation scenario, set the southbound floating IP address and SSH password of eSight and click OK in the dialog box that is displayed.
    5. Log in to the active distributed node as the ossuser user. Run the following command to connect the active and standby nodes:

      cd /opt/eSight/mttools/tools/distributed

      ./joinHA.sh

      Please input peer heartbeat ip:
      Please input ossuser's password:
      connect success.
    6. Log in to the active distributed node as the root user. Run the following commands to bring the AppService resource group online on the active distributed node:

      hagrp -online AppService -sys Host name of the active distributed node

Changing the Heartbeat IP Address of an HA System (Veritas)

This topic describes how to change the heartbeat IP address for an HA system.

Prerequisites

  • To change the heartbeat IP address for an HA system, you must disconnect the active server from the standby server. For details, see Disconnecting the Active and Standby Servers.
  • The method for changing the heartbeat IP address on the active server is the same as that on the standby server.

Procedure

  1. Log in to the operating system as the ossuser user.
  2. Stop the eSight maintenance tool process on the active server.

    #cd /opt/eSight/mttools/bin

    #./stop-sysmon.sh

  3. Modify the heartbeat IP address of the operating system.

    1. Use the following command to switch to the configuration tool directory.

      cd /opt/eSight/mttools/tools

    2. Execute the following script to modify the heartbeat IP address of the operating system.

      ./hacheck.sh

      NOTE:

      After the configuration is complete, the network service of the operating system will be restarted. If the configuration is not performed on the management port, the connection may be interrupted after the network service is restarted. Use the new IP address to log in to the Linux server.

  4. Change the heartbeat IP address of the HA system.

    Run the following commands to set the new heartbeat IP address to the VCS.

    # haconf -makerw

    # haclus -modify ClusterAddress New heartbeat IP address

    # haconf -dump -makero

    # rcnetwork restart

  5. Repeat 1 to 4 to change the heartbeat IP address for the standby server.
  6. Connect the primary and secondary servers. For details, see Connecting the Active and Standby Servers.
  7. Bring the AppService service group online and restart eSight.
  8. (Optional) If a distributed server is deployed on the network, perform the following operations to change its IP address:

    1. Log in to the active distributed node as the root user. Run the following commands to bring the AppService resource group offline on the active distributed node:

      hagrp -offline AppService -sys Host name of the active distributed node

      NOTE:

      Run the following commands to check the status of the AppService resource group. Perform the subsequent operations only when the resource group is in OFFLINE state.

      hagrp -state AppService -sys Server host name

    2. Run the following command to separate distributed nodes as the ossuser user.

      su - ossuser

      cd /opt/eSight/mttools/tools/distributed

      ./splitHA.sh

    3. Log in to the active and standby distributed nodes as the ossuser user. Run the following commands to start the connection tool:

      cd opt/eSight/mttools/tools

      ./connect_tool.sh

    4. Configure the IP address information as prompted.
      NOTE:

      Do not close the window during the configuration.

      • In the southbound and northbound non-isolation scenario, set the floating IP address and SSH password of eSight and click OK in the dialog box that is displayed.
      • In the southbound and northbound isolation scenario, set the southbound floating IP address and SSH password of eSight and click OK in the dialog box that is displayed.
      • In the southbound and northbound non-isolation scenario, set the system IP address and SSH password of the active eSight server and click OK in the dialog box that is displayed.
      • In the southbound and northbound isolation scenario, set the southbound IP address and SSH password of the active eSight server and click OK in the dialog box that is displayed.
    5. Log in to the active distributed node as the ossuser user. Run the following command to connect the active and standby nodes:

      cd /opt/eSight/mttools/tools/distributed

      ./joinHA.sh

      Please input peer heartbeat ip:
      Please input ossuser's password:
      connect success.
    6. Log in to the active distributed node as the root user. Run the following commands to bring the AppService resource group online on the active distributed node:

      hagrp -online AppService -sys Host name of the active distributed node

Translation
Download
Updated: 2019-09-12

Document ID: EDOC1100044373

Views: 34347

Downloads: 107

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