1 files changed, 3 insertions, 85 deletions
diff --git a/doc/book-enea-edge-getting-started/doc/advanced_configurations.xml b/doc/book-enea-edge-getting-started/doc/advanced_configurations.xml
index 10f1e65..e321cf9 100644
--- a/doc/book-enea-edge-getting-started/doc/advanced_configurations.xml
+++ b/doc/book-enea-edge-getting-started/doc/advanced_configurations.xml
@@ -957,91 +957,9 @@ Configuration complete.</programlisting>
        View</emphasis>. The list of Enea Edge Management servers should be
        displayed, with one listed as Primary and the rest as Backup.</para>
-        <para>The High Availability configuration can be changed at a later
+        <para>To change the configuration at a later point after the
-        point, if, for instance, the IPs of the cluster have changed. Before 
+        installation, either uninstall and then reinstall the product, or
-          changing the settings in the configuration files, the Enea Edge 
+        contact Enea Support.</para>
-          Management application must first be stopped, followed by the 
-          MariaDB database.</para>
-          
-          <para>To change cluster settings, do the following:</para>
-        <itemizedlist>
-          <listitem>
-            <para>Change the configuration of the MariaDB with the new IPs: go
-            to <filename>/etc/my.cnf.d/wsrep.cnf</filename> and modify the
-            <literal>wsrep_cluster_address</literal> property.</para>
-          </listitem>
-          <listitem>
-            <para>Go to the Enea Edge Management installation folder, then to
-            application/config and edit
-            <filename>databaseConfig.xml</filename>. Change the list of IPs
-            under the <literal>&lt;location&gt;</literal> tag. The order of
-            the IPs is important, since the Edge Management will try to
-            contact them sequentially. Placing the local IP first (the one
-            identified by the protect.interface, see below) will improve
-            communication latency, since it will be done on the local
-            bus.</para>
-          </listitem>
-          <listitem>
-            <para>In the same folder, edit the
-            <filename>elementCenter.xml</filename> file. Below are the most
-            important properties relating to the High Availability
-            feature:</para>
-            <itemizedlist>
-              <listitem>
-                <para><emphasis role="bold">protect.enabled</emphasis>:
-                boolean value that enables protection mode.</para>
-              </listitem>
-              <listitem>
-                <para><emphasis role="bold">protect.group</emphasis>: the name
-                of the protection group.</para>
-              </listitem>
-              <listitem>
-                <para><emphasis
-                role="bold">protect.heartbeat.seconds</emphasis>: the time
-                resolution in which a primary server failure is detected. A
-                primary failure during the heartbeat signal period means that
-                service will no longer be available until the next heartbeat
-                occurs. One of the backup servers will take over as primary
-                afterwards.</para>
-              </listitem>
-              <listitem>
-                <para><emphasis
-                role="bold">protect.virtualIpAddress</emphasis>: the IP
-                address of the cluster. This value must be the same for all
-                members of the cluster.</para>
-              </listitem>
-              <listitem>
-                <para><emphasis role="bold">protect.vipNetmask</emphasis>: the
-                netmask of the virtual IP.</para>
-              </listitem>
-              <listitem>
-                <para><emphasis role="bold">protect.interface</emphasis>: the
-                interface responsible for handling ucpeManager traffic,
-                identified by IP address.</para>
-              </listitem>
-              <listitem>
-                <para><emphasis
-                role="bold">protect.arbiterIpAddress</emphasis>: the IP
-                address of the arbiter, used to elect a primary server.</para>
-              </listitem>
-              <listitem>
-                <para><emphasis role="bold">protect.arbiterPort</emphasis>:
-                the port to ping on the arbiter.</para>
-              </listitem>
-            </itemizedlist>
-          </listitem>
-        </itemizedlist>
      </section>
    </section>

diff --git a/doc/book-enea-edge-getting-started/doc/advanced_configurations.xml b/doc/book-enea-edge-getting-started/doc/advanced_configurations.xml index 10f1e65..e321cf9 100644 --- a/doc/book-enea-edge-getting-started/doc/advanced_configurations.xml +++ b/doc/book-enea-edge-getting-started/doc/advanced_configurations.xml
@@ -957,91 +957,9 @@ Configuration complete.</programlisting>
957	View</emphasis>. The list of Enea Edge Management servers should be	957	View</emphasis>. The list of Enea Edge Management servers should be
958	displayed, with one listed as Primary and the rest as Backup.</para>	958	displayed, with one listed as Primary and the rest as Backup.</para>
959		959
960	<para>The High Availability configuration can be changed at a later	960	<para>To change the configuration at a later point after the
961	point, if, for instance, the IPs of the cluster have changed. Before	961	installation, either uninstall and then reinstall the product, or
962	changing the settings in the configuration files, the Enea Edge	962	contact Enea Support.</para>
963	Management application must first be stopped, followed by the
964	MariaDB database.</para>
965
966	<para>To change cluster settings, do the following:</para>
967
968	<itemizedlist>
969	<listitem>
970	<para>Change the configuration of the MariaDB with the new IPs: go
971	to <filename>/etc/my.cnf.d/wsrep.cnf</filename> and modify the
972	<literal>wsrep_cluster_address</literal> property.</para>
973	</listitem>
974
975	<listitem>
976	<para>Go to the Enea Edge Management installation folder, then to
977	application/config and edit
978	<filename>databaseConfig.xml</filename>. Change the list of IPs
979	under the <literal><location></literal> tag. The order of
980	the IPs is important, since the Edge Management will try to
981	contact them sequentially. Placing the local IP first (the one
982	identified by the protect.interface, see below) will improve
983	communication latency, since it will be done on the local
984	bus.</para>
985	</listitem>
986
987	<listitem>
988	<para>In the same folder, edit the
989	<filename>elementCenter.xml</filename> file. Below are the most
990	important properties relating to the High Availability
991	feature:</para>
992
993	<itemizedlist>
994	<listitem>
995	<para><emphasis role="bold">protect.enabled</emphasis>:
996	boolean value that enables protection mode.</para>
997	</listitem>
998
999	<listitem>
1000	<para><emphasis role="bold">protect.group</emphasis>: the name
1001	of the protection group.</para>
1002	</listitem>
1003
1004	<listitem>
1005	<para><emphasis
1006	role="bold">protect.heartbeat.seconds</emphasis>: the time
1007	resolution in which a primary server failure is detected. A
1008	primary failure during the heartbeat signal period means that
1009	service will no longer be available until the next heartbeat
1010	occurs. One of the backup servers will take over as primary
1011	afterwards.</para>
1012	</listitem>
1013
1014	<listitem>
1015	<para><emphasis
1016	role="bold">protect.virtualIpAddress</emphasis>: the IP
1017	address of the cluster. This value must be the same for all
1018	members of the cluster.</para>
1019	</listitem>
1020
1021	<listitem>
1022	<para><emphasis role="bold">protect.vipNetmask</emphasis>: the
1023	netmask of the virtual IP.</para>
1024	</listitem>
1025
1026	<listitem>
1027	<para><emphasis role="bold">protect.interface</emphasis>: the
1028	interface responsible for handling ucpeManager traffic,
1029	identified by IP address.</para>
1030	</listitem>
1031
1032	<listitem>
1033	<para><emphasis
1034	role="bold">protect.arbiterIpAddress</emphasis>: the IP
1035	address of the arbiter, used to elect a primary server.</para>
1036	</listitem>
1037
1038	<listitem>
1039	<para><emphasis role="bold">protect.arbiterPort</emphasis>:
1040	the port to ping on the arbiter.</para>
1041	</listitem>
1042	</itemizedlist>
1043	</listitem>
1044	</itemizedlist>
1045	</section>	963	</section>
1046	</section>	964	</section>
1047		965