Help Center> MapReduce Service> User Guide (ME-Abu Dhabi Region)> FusionInsight Manager Operation Guide (Applicable to 3.x)> Cluster Management> Modifying the Manager Routing Table
Updated on 2022-02-22 GMT+08:00
View PDF

Modifying the Manager Routing Table

Scenario

After the FusionInsight Manager is installed, the system automatically creates two pieces of routing information on the active management node. Run the ip rule list command to view the routing information, as shown in the following example:

0:  from all lookup local  
32764:  from all to 10.10.100.100 lookup ntp_rt  #FusionInsight Manager NTP routing information created by the system. The information is not displayed when no external NTP clock source is configured. FusionInsight Manager
from 1EI Managerm_rt #FusionInsight Manager routing information created by the system 
32766:  from all lookup main  
32767:  from all lookup default

If the external NTP server has not been configured, only the OM routing information om_rt will be created.

When the routing information created by the FusionInsight Manager system conflicts with the routing information of the enterprise, use the autoroute.sh tool to disable or enable routes created by FusionInsight Manager.

Impact on the System

After the routing information created by the FusionInsight Manager system is disabled and before the new routing information is set, FusionInsight Manager cannot be accessed but operating of the cluster will not be affected.

Prerequisites

The Manager has already been installed.

Disable the routing information created by the system.

  1. Log in to the active management node as user omm. Run the following commands to disable the routing information created by the system:

    cd ${BIGDATA_HOME}/om-server/om/sbin

    ./autoroute.sh disable

    Deactivating Route. 
Route operation (disable) successful.

  2. Run the following command to view the execution result:

    ip rule list

    0:  from all lookup local  
32766:  from all lookup main  
32767:  from all lookup default

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

    su - root

  4. Run the following commands to manually create WS floating IP address routing information:

    ip route add WS floating IP address Network segment number/WS floating IP address subnet mask scope link src WS floating IP address dev WS floating IP address NIC table om_rt

    ip route add default via WS floating IP address gateway dev WS floating IP address NIC table om_rt

    ip rule add from WS floating IP address table om_rt

    For example,

    ip route add 192.168.0.0/255.255.255.0 scope link src 192.168.0.117 dev eth0:ws table om_rt

    ip route add default via 192.168.0.254 dev eth0:ws table om_rt

    ip rule add from 192.168.0.117 table om_rt

    If the IP address mode of the current network is IPv6, run the ip -6 route add command.

  5. Run the following commands to manually create NTP service routing information (Skip this step when no external NTP clock source is configured.):

    ip route add default via NtpIP address gateway dev NIC of the local host IP address table ntp_rt

    ip rule add to NTP IP address table ntp_rt

    NIC of the local host IP address indicates the NIC that can interwork with the network segment where the NTP server is located.

    For example,

    ip route add default via 10.10.100.254 dev eth0 table ntp_rt

    ip rule add to 10.10.100.100 table ntp_rt

  6. Run the following command to view the execution result. For example, if routing information of which the routing table names are om_rt and ntp_rt is generated, the operation is successful.

    ip rule list

    0:  from all lookup local 
32764:  from all to 10.10.100.100 lookup ntp_rt #The information is not displayed when no external NTP clock source is configured.
32765:  from 192.168.0.117 lookup om_rt  
32766:  from all lookup main  
32767:  from all lookup default

Enable the routing information created by the system.

  1. Log in to the active management node as user omm.
  2. Run the following commands to enable the routing information created by the system:

    cd ${BIGDATA_HOME}/om-server/om/sbin

    ./autoroute.sh enable

    Activating Route. 
Route operation (enable) successful.

  3. Run the following command to view the execution result. For example, if routing information of which the routing table names are ntp_rt and om_rt is generated, the operation is successful.

    ip rule list

    0:  from all lookup local  
32764:  from all to 10.10.100.100 lookup ntp_rt  #The information is not displayed when no external NTP clock source is configured.
32765:  from 192.168.0.117 lookup om_rt  
32766:  from all lookup main  
32767:  from all lookup default

Parent topic: Cluster Management