forked from docs/doc-exports
Yang, Tong
2195db241c
Reviewed-by: Pruthi, Vineet <vineet.pruthi@t-systems.com> Reviewed-by: Rechenburg, Matthias <matthias.rechenburg@t-systems.com> Co-authored-by: Yang, Tong <yangtong2@huawei.com> Co-committed-by: Yang, Tong <yangtong2@huawei.com>
72 lines
11 KiB
HTML
72 lines
11 KiB
HTML
<a name="admin_guide_000183"></a><a name="admin_guide_000183"></a>
|
|
|
|
<h1 class="topictitle1">Modifying the <span id="text15946118176">MRS</span> Manager Routing Table</h1>
|
|
<div id="body1529658735916"><div class="section" id="admin_guide_000183__scd1f9dafbfde48d79026ad3853fb0f36"><h4 class="sectiontitle">Scenario</h4><p id="admin_guide_000183__en-us_topic_0046662340_p1462819">When <span id="admin_guide_000183__text477311367589">MRS</span> Manager is installed, two pieces of routing information are automatically created on the active management node. You can run the <strong id="admin_guide_000183__b191732072111225">ip rule list</strong> command to view the routing information, as shown in the following example:</p>
|
|
<pre class="screen" id="admin_guide_000183__screen442968115410">0:from all lookup local
|
|
32764:from all to 10.10.100.100 lookup ntp_rt #NTP routing information created by <span id="admin_guide_000183__text741263911589">MRS</span> Manager (this information is unavailable if no external NTP clock source is configured).
|
|
32765:from 192.168.0.117 lookup om_rt #OM routing information created by the <span id="admin_guide_000183__text7588134145817">MRS</span> Manager.
|
|
32766:from all lookup main
|
|
32767:from all lookup default</pre>
|
|
<div class="note" id="admin_guide_000183__note2746496795047"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="admin_guide_000183__p4585811895047">If no external NTP server has been configured, only the OM routing information will be created.</p>
|
|
</div></div>
|
|
<p id="admin_guide_000183__en-us_topic_0046662340_p51272187">If the routing information created by <span id="admin_guide_000183__text18388843105819">MRS</span> Manager conflicts with the routing information configured in the enterprise network planning, the cluster administrator can use <strong id="admin_guide_000183__b212313964392141">autoroute.sh</strong> to disable or enable the routing information created by <span id="admin_guide_000183__text156568322235">MRS</span> Manager.</p>
|
|
</div>
|
|
<div class="section" id="admin_guide_000183__s1a58f892b6084378b262ab32d1fb1050"><h4 class="sectiontitle">Impact on the System</h4><p id="admin_guide_000183__en-us_topic_0046662340_p59406488">After the routing information created by <span id="admin_guide_000183__text8147194865810">MRS</span> Manager is disabled and before the new routing information is set, <span id="admin_guide_000183__text4328607599">MRS</span> Manager cannot be accessed but the clusters are running properly.</p>
|
|
</div>
|
|
<div class="section" id="admin_guide_000183__sc7134b15fa9647df922b450b894279ee"><h4 class="sectiontitle">Prerequisites</h4><p id="admin_guide_000183__en-us_topic_0046662340_p47196242"><span id="admin_guide_000183__text1485353125916">MRS</span> Manager has been installed.</p>
|
|
<p id="admin_guide_000183__p1147325014218">You have obtained routing information about the WS floating IP address.</p>
|
|
</div>
|
|
<div class="section" id="admin_guide_000183__sf4ac118287074ed5abd6263356492f2f"><h4 class="sectiontitle">Disable the Routing Information Created by the System</h4><ol id="admin_guide_000183__ol756117239189"><li id="admin_guide_000183__li19556623121816"><span>Log in to the active management node as user <strong id="admin_guide_000183__b10505238143317">omm</strong>. Run the following commands to disable the routing information created by the system:</span><p><p id="admin_guide_000183__p10556623141813"><strong id="admin_guide_000183__b1555692315181">cd ${BIGDATA_HOME}/om-server</strong><strong id="admin_guide_000183__b3556923181819">/om/sbin</strong></p>
|
|
<p class="litext" id="admin_guide_000183__p455611236183"><strong id="admin_guide_000183__b1955672313187">./autoroute.sh disable</strong></p>
|
|
<pre class="screen" id="admin_guide_000183__screen17857113271316">Deactivating Route.
|
|
Route operation (disable) successful.</pre>
|
|
</p></li><li id="admin_guide_000183__li255716231187"><span>Run the following command to view the execution result:</span><p><p class="litext" id="admin_guide_000183__p105566236182"><strong id="admin_guide_000183__b11556102381820">ip rule list</strong></p>
|
|
<pre class="screen" id="admin_guide_000183__screen105575239183">0:from all lookup local
|
|
32766:from all lookup main
|
|
32767:from all lookup default</pre>
|
|
</p></li><li id="admin_guide_000183__li125576237186"><span>Run the following command and enter the password of user <strong id="admin_guide_000183__b193996261711225">root</strong> to switch to user <strong id="admin_guide_000183__b69705238711225">root</strong>:</span><p><p class="litext" id="admin_guide_000183__p15571423191811"><strong id="admin_guide_000183__b185571023141819">su - root</strong></p>
|
|
</p></li><li id="admin_guide_000183__li1956092313180"><span>Run the following commands to manually create the routing information about the WS floating IP address:</span><p><p class="litext" id="admin_guide_000183__p1656015235184"><strong id="admin_guide_000183__b84770261411225">ip route add </strong><em id="admin_guide_000183__i8575837143719">Network segment of the WS floating IP address/Subnet mask of the WS floating IP address</em><strong id="admin_guide_000183__b63692879811225"> scope link src </strong><em id="admin_guide_000183__i19447143433817">WS floating IP address</em><strong id="admin_guide_000183__b124028916511225"> dev </strong><em id="admin_guide_000183__i7855423211225">NIC of the WS floating IP address</em><strong id="admin_guide_000183__b65614701511225"> table om_rt</strong></p>
|
|
<p class="litext" id="admin_guide_000183__p1756052311183"><strong id="admin_guide_000183__b185604238188">ip route add default via </strong><em id="admin_guide_000183__i11560323111816">Gateway of the WS floating IP address</em><strong id="admin_guide_000183__b1356011237185"> dev </strong><em id="admin_guide_000183__i3560223151819">NIC of the WS floating IP address</em><strong id="admin_guide_000183__b1756032391819"> table om_rt</strong></p>
|
|
<p class="litext" id="admin_guide_000183__p195601223101815"><strong id="admin_guide_000183__b61081391411225">ip rule add from </strong><em id="admin_guide_000183__i66633170711225">WS floating IP address</em><strong id="admin_guide_000183__b59435048811225"> table om_rt</strong></p>
|
|
<p class="litext" id="admin_guide_000183__p15560192331818">Example:</p>
|
|
<p class="litext" id="admin_guide_000183__p25601023201810"><strong id="admin_guide_000183__b3560923181819">ip route add 192.168.0.0/255.255.255.0 scope link src 192.168.0.117 dev eth0:ws table om_rt</strong></p>
|
|
<p class="litext" id="admin_guide_000183__p1356014231184"><strong id="admin_guide_000183__b15603235187">ip route add default via 192.168.0.254 dev eth0:ws table om_rt</strong></p>
|
|
<p class="litext" id="admin_guide_000183__p1556032321811"><strong id="admin_guide_000183__b155603237186">ip rule add from 192.168.0.117 table om_rt</strong></p>
|
|
<div class="note" id="admin_guide_000183__note139745356231"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="admin_guide_000183__p11974103572319">If IPv6 addresses are used, run the <strong id="admin_guide_000183__b13448856142318">ip -6 route add</strong> command.</p>
|
|
</div></div>
|
|
</p></li><li id="admin_guide_000183__li11561172317182"><span>Run the following commands to manually create the NTP service routing information. Skip this step when no external NTP clock source is configured.</span><p><p class="litext" id="admin_guide_000183__p056012235188"><strong id="admin_guide_000183__b125602023141811">ip route add default via </strong><em id="admin_guide_000183__i1560923121820">IP gateway of the NTP service</em><strong id="admin_guide_000183__b16560023131817"> dev </strong><em id="admin_guide_000183__i956012351816">NIC of the local IP address</em><strong id="admin_guide_000183__b1756015237189"> table ntp_rt</strong></p>
|
|
<p class="litext" id="admin_guide_000183__p55618235180"><strong id="admin_guide_000183__b0560172318181">ip rule add to </strong><em id="admin_guide_000183__i6560423121815">ntpIP</em><strong id="admin_guide_000183__b1656012318189"> table ntp_rt</strong></p>
|
|
<p class="litext" id="admin_guide_000183__p145617237184"><em id="admin_guide_000183__i6834131144319">NIC of the local IP address</em> indicates the NIC that can communicate with the network segment where the NTP server is located.</p>
|
|
<p class="litext" id="admin_guide_000183__p16561192381812">Example:</p>
|
|
<p class="litext" id="admin_guide_000183__p85611723101810"><strong id="admin_guide_000183__b12561162318189">ip route add default via 10.10.100.254 dev eth0 table ntp_rt</strong></p>
|
|
<p class="litext" id="admin_guide_000183__p65612234189"><strong id="admin_guide_000183__b756112312188">ip rule add to 10.10.100.100 table ntp_rt</strong></p>
|
|
</p></li><li id="admin_guide_000183__li856122319183"><span>View the execution result.</span><p><p id="admin_guide_000183__p19561723171814">In the following example, if the command output contains <strong id="admin_guide_000183__b169061587311225">om_rt</strong> and <strong id="admin_guide_000183__b19847155713446">ntp_rt</strong>, the operation is successful.</p>
|
|
<p id="admin_guide_000183__p1556172351812"><strong id="admin_guide_000183__b1856152318188">ip rule list</strong></p>
|
|
<pre class="screen" id="admin_guide_000183__screen2561192317187">0:from all lookup local
|
|
32764:from all to 10.10.100.100 lookup ntp_rt #This information is not displayed if 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</pre>
|
|
</p></li></ol>
|
|
</div>
|
|
<div class="section" id="admin_guide_000183__section1898175116193"><h4 class="sectiontitle">Enable the Routing Information Created by the System</h4><ol id="admin_guide_000183__ol109725620193"><li id="admin_guide_000183__li1495156101914"><span>Log in to the active management node as user <strong id="admin_guide_000183__b1786871654618">omm</strong>.</span></li><li id="admin_guide_000183__li1795756121910"><span>Run the following commands to enable the routing information created by the system:</span><p><p id="admin_guide_000183__p895856131917"><strong id="admin_guide_000183__b6951556171916">cd ${BIGDATA_HOME}/om-server</strong><strong id="admin_guide_000183__b49510562194">/om/sbin</strong></p>
|
|
<p class="litext" id="admin_guide_000183__p11955564198"><strong id="admin_guide_000183__b995155681910">./autoroute.sh enable</strong></p>
|
|
<pre class="screen" id="admin_guide_000183__screen1409184551411">Activating Route.
|
|
Route operation (enable) successful.</pre>
|
|
</p></li><li id="admin_guide_000183__li99785612195"><span>View the execution result.</span><p><p id="admin_guide_000183__p1197156161920">In the following example, if the command output contains <strong id="admin_guide_000183__b11172124364615">om_rt</strong> and <strong id="admin_guide_000183__b1694014218477">ntp_rt</strong>, the operation is successful.</p>
|
|
<p id="admin_guide_000183__p139713560197"><strong id="admin_guide_000183__b49785615197">ip rule list</strong></p>
|
|
<pre class="screen" id="admin_guide_000183__screen3976566196">0:from all lookup local
|
|
32764:from all to 10.10.100.100 lookup ntp_rt #This information is not displayed if 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</pre>
|
|
</p></li></ol>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="admin_guide_000166.html">Cluster Management</a></div>
|
|
</div>
|
|
</div>
|
|
|