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 V300R009C00 Local HA System Software Installation Guide (SUSE Linux + MySQL + OMMHA) 10

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 System IP Address of a Local HA System (OMMHA)

Changing the System IP Address of a Local HA System (OMMHA)

If the system IP address, heartbeat IP address, or southbound IP address of eSight on the VM network adapter is changed, or the floating IP address needs to be changed, you need to change related IP addresses on eSight.

Context

  • If the system or southbound floating IP address needs to be changed, you can perform operations in this section to change the floating IP address.
  • If the system IP address, heartbeat IP address, or southbound IP address of eSight on the VM network adapter is changed, you can perform operations in this section to change related IP addresses on eSight. This operation does not change the IP address of the network adapter. To change the IP address, see How Do I Change the Host Name, Route, or IP Address(SUSE Linux) (for SUSE Linux).

Precautions

This operation will stop and restart eSight, causing eSight service interruption.

Procedure

  1. Log in to the active eSight server as the ossuser user.
  2. Run the following command to switch to the root user:

    > su - root

  3. Run the following commands to change the eSight IP address:

    # cd /opt/ommha/config

    # chmod u+x config.sh

    # export TMOUT=0

    # ./config.sh

    NOTE:

    During the configuration, you can run the undo command to modify the previous configuration if it is incorrect.

  4. Enter 1 to select local-HA.

    ##################################################
    Welcome to eSight installation & configuration Wizard
    ##################################################
    Please select HA type, 1(local-HA)  2(remote-HA)[default:1]:
    >1

  5. Enter the system IP address of the active server, heartbeat and replication IP address of the active server, and floating IP address as prompted. (The following describes how to change an IPv4 address to an IPv6 address.)

    Please input local system ip address[default:10.10.108.1]: 
    >2001:db8:2de::e14
    Please input local heartbeat ip address[default:192.168.100.10]: 
    >2002:db8:2de::e14
    Please input float ip address[default:10.10.10.3]: 
    >2001:db8:1de::e14

  6. Configure the southbound and northbound service isolation as prompted.

    • In the scenario where southbound services are isolated from northbound services, enter y and press Enter. Then enter the planned southbound floating IP address.
      Enter 'y' to apply the setting of South IP Address or 'n' to ignore (y/n)[default:n]: 
      >y 
      Please input south float ip address: 
      >2003:db8:2de::e14
    • In the scenario where southbound services are not isolated from northbound services, enter n and press Enter.
      Enter 'y' to apply the setting of South IP Address or 'n' to ignore (y/n)[default:n]: 
      >n

  7. Enter the system IP address and heartbeat and replication IP address of the standby server as prompted.

    Please input remote system ip address[default:10.10.108.3]: 
    >2001:db8:3de::e14
    Please input remote heartbeat ip address[default:192.168.100.11]: 
    >2002:db8:3de::e14

  8. Confirm the configurations.

    Please confirm the following configurations...  
     ****************************************  
         local system ip  
             2001:db8:2de::e14
         local heartbeat ip  
             2002:db8:2de::e14
         float ip  
             2001:db8:1de::e14
         south float ip 
             2003:db8:2de::e14
         remote system ip  
             2001:db8:3de::e14
         remote heartbeat ip  
             2002:db8:3de::e14
     Enter 'y' to apply these values and proceed to the next step, or 'n' to return to make any changes (y/n):y 

  9. Enter the root user password of the standby server as prompted.

     Please input remote root password: 

  10. Check the resource status of the active and standby servers in the command output, that is, whether the value of ResStatus is normal. For details, see Table 1. If the status is normal, the operation is successful. Otherwise, contact Huawei technical support.

    If the value of HAActive is active, the corresponding node is the active server. If the value of HAActive is standby, the corresponding node is the standby server.

    NOTE:

    The initialization process takes about 15 minutes.

     begin init
     check component...
     check multi-subnetwork...  
     begin to check local parameters...  
     check parameters finish  
     begin to check remote parameters...  
     check remote parameters finish  
     begin to stop ommha  
     stop ommha finish  
     begin to rsync...   
     rsync finish. 
     begin to startup...  
     HAMode  
     double   
     NodeName    HostName        HAVersion    StartTime                   HAActive        HAAllResOK   HARunPhase  
     ha2        eSightServer174  V100R001C01  2017-07-05 14:14:50         active            normal       Actived  
     ha1        eSightServer165  V100R001C01  2017-07-07 10:43:20         standby           normal     Deactived   
      
     NodeName    ResName         ResStatus         ResHAStatus               ResType  
     ha2         Database          Active normal      Normal                Active_standby  
     ha2        NMSServer          Normal           Normal                Single_active  
     ha2        RMFloatIp          Normal           Normal                Single_active  
     ha2       RMSouthFloatIp      Normal           Normal                Single_active  
     ha1       Database           Standby normal     Normal                Active_standby  
     ha1       NMSServer           Stopped          Unknown               Single_active  
     ha1        RMFloatIp          Stopped          Normal                Single_active  
     ha1      RMSouthFloatIp       Stopped          Normal                Single_active  
    Table 9-3 Normal resource status of the eSight HA system

    Resource Item

    Description

    Node

    Normal Status

    Database

    Database resource status

    Active server

    Active_normal

    Standby server

    Standby_normal

    NMSServer

    eSight service resource status

    Active server

    Normal

    Standby server

    Stopped

    RMFloatIp

    System floating IP address status

    Active server

    Normal

    Standby server

    Stopped

    RMSouthFloatIp

    Southbound floating IP address status

    NOTE:

    This status is displayed only when the southbound and northbound services are isolated.

    Active server

    Normal

    Standby server

    Stopped

    NOTE:
    • After the IP address of eSight is changed, change the IP address of eSight accordingly in the systems connected to eSight.
    • After the IP address of eSight is changed, the IP address of eSight must be changed accordingly on the following types of devices connected to eSight:
      • Unified communications devices: CC solution, ECS, IAD, eSpace U2900, eSpace USM, VTC, and SBC (SX series)
      • Telepresence and videoconferencing devices: MCU
    • After the IP address of eSight is changed, change the IP address for servers and PON devices connected to eSight to report alarms accordingly.
    • If the eSight IP address changes during FusionCompute or FusionSphere management, eSight needs to send the new eSight IP address to the devices to ensure normal service running.
    • After configuring the southbound IP address, modify SNMP parameters of the FusionSphere accordingly and send the parameter settings to the OpenStack OM.
      • Set Alarm source address to OM Network Floating IP Address.
      • Select Synchronize SNMP Trap Settings to OpenStack OM.

Download
Updated: 2019-09-02

Document ID: EDOC1100011856

Views: 91678

Downloads: 53

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