VALT Warm Standby - Revision history

IVSWikiBlue at 14:26, 24 October 2023

2023-10-24T14:26:16Z

IVSWikiBlue at 22:39, 27 July 2023

2023-07-27T22:39:01Z

← Older revision		Revision as of 22:39, 27 July 2023
Line 39:		Line 39:
	#Run {{Code Block - Mini \| text = <span class="code_file">VALTStandbyServerConfig.sh</span>}} on the standby server. Make sure to modify the variables at the top of the script to reflect your environment. Specifically the primaryip must be changed to the ip address of the primary server, the logfile and logpos variables must be set to the values output when running the script on the primary server.		#Run {{Code Block - Mini \| text = <span class="code_file">VALTStandbyServerConfig.sh</span>}} on the standby server. Make sure to modify the variables at the top of the script to reflect your environment. Specifically the primaryip must be changed to the ip address of the primary server, the logfile and logpos variables must be set to the values output when running the script on the primary server.

	If using the VALTRedundancy.tar.gz package, the failure.sh and restore.sh scripts should automatically be copied to the {{Code Block - Mini \| text = <span class="code_filepath">/usr/local/valt/bin/</span>}} directory and set to executable. These scripts are provided below if the {{Code Block - Mini \| text = <span class="code_2">VALTRedundancy.tar.gz</span> ~~package~~}} was not used. It is a good idea to update the variables in these scripts now so they are ready to be used in the event of a failover.		If using the VALTRedundancy.tar.gz package, the failure.sh and restore.sh scripts should automatically be copied to the {{Code Block - Mini \| text = <span class="code_filepath">/usr/local/valt/bin/</span>}} directory and set to executable. These scripts are provided below if the {{Code Block - Mini \| text = <span class="code_2">VALTRedundancy.tar.gz</span>}} package was not used. It is a good idea to update the variables in these scripts now so they are ready to be used in the event of a failover.

	<hr>		<hr>

IVSWikiBlue at 22:37, 27 July 2023

2023-07-27T22:37:46Z

← Older revision		Revision as of 22:37, 27 July 2023
Line 28:		Line 28:

	=Primary Server Config=		=Primary Server Config=
	Run {{Code Block - Mini \| text = PrimaryServerConfig.sh}} on the primary server. Make sure to modify the variables at the top of the script to reflect your environment. Specifically the standbyip must be changed to the ip address of the standby server.		Run {{Code Block - Mini \| text = <span class="code_file">PrimaryServerConfig.sh</span>}} on the primary server. Make sure to modify the variables at the top of the script to reflect your environment. Specifically the standbyip must be changed to the ip address of the standby server.

	The script will complete by providing the log file name and position. Make a note of these values as they will be needed to configure the standby server.		The script will complete by providing the log file name and position. Make a note of these values as they will be needed to configure the standby server.
Line 35:		Line 35:

	=Standby Server Config=		=Standby Server Config=
	#Run {{Code Block - Mini \| text = sudo -i}}		#Run {{Code Block - Mini \| text = <span class="code_regex">sudo</span> <span class="code_option">-i</span>}}
	#:If you do not use this specific command portions of the script will not execute properly.		#:If you do not use this specific command portions of the script will not execute properly.
	#Run {{Code Block - Mini \| text = VALTStandbyServerConfig.sh}} on the standby server. Make sure to modify the variables at the top of the script to reflect your environment. Specifically the primaryip must be changed to the ip address of the primary server, the logfile and logpos variables must be set to the values output when running the script on the primary server.		#Run {{Code Block - Mini \| text = <span class="code_file">VALTStandbyServerConfig.sh</span>}} on the standby server. Make sure to modify the variables at the top of the script to reflect your environment. Specifically the primaryip must be changed to the ip address of the primary server, the logfile and logpos variables must be set to the values output when running the script on the primary server.

	If using the VALTRedundancy.tar.gz package, the failure.sh and restore.sh scripts should automatically be copied to the {{Code Block - Mini \| text = /usr/local/valt/bin/}} directory and set to executable. These scripts are provided below if the {{Code Block - Mini \| text = VALTRedundancy.tar.gz package}} was not used. It is a good idea to update the variables in these scripts now so they are ready to be used in the event of a failover.		If using the VALTRedundancy.tar.gz package, the failure.sh and restore.sh scripts should automatically be copied to the {{Code Block - Mini \| text = <span class="code_filepath">/usr/local/valt/bin/</span>}} directory and set to executable. These scripts are provided below if the {{Code Block - Mini \| text = <span class="code_2">VALTRedundancy.tar.gz</span> package}} was not used. It is a good idea to update the variables in these scripts now so they are ready to be used in the event of a failover.

	<hr>		<hr>
Line 46:		Line 46:
	# Update the shared DNS entry to reference the standby server.		# Update the shared DNS entry to reference the standby server.
	# Run the script by typing the following command:		# Run the script by typing the following command:
	#: {{Code Block - Mini \| text = sudo /usr/local/valt/bin/failure.sh}}		#: {{Code Block - Mini \| text = <span class="code_regex">sudo</span> <span class="code_filepath">/usr/local/valt/bin/</span><span class="code_file">failure.sh</span>}}

	<hr>		<hr>
Line 54:		Line 54:
	# Update the variables in the script below to reflect the correct primary ip, slaveuser, and slavepassword. <em>(If this was not done during initial setup)</em>		# Update the variables in the script below to reflect the correct primary ip, slaveuser, and slavepassword. <em>(If this was not done during initial setup)</em>
	# Run the script by typing the following command:		# Run the script by typing the following command:
	#: {{Code Block - Mini \| text = sudo /usr/local/valt/bin/restore.sh}}		#: {{Code Block - Mini \| text = <span class="code_regex">sudo</span> <span class="code_filepath">/usr/local/valt/bin/</span><span class="code_file">restore.sh</span>}}
	}}		}}

IVSWikiBlue at 22:25, 27 July 2023

2023-07-27T22:25:25Z

← Older revision		Revision as of 22:25, 27 July 2023
Line 22:		Line 22:

	=Script Package=		=Script Package=
	# Download VALTRedundancy.tar.gz by running the following command: {{Code Block - Mini \| text = wget --content-disposition https://ivs.box.com/shared/static/1062styfwr387efew51vt6mzqzsdd1m3.gz -O VALTRedundancy.tar.gz}}		# Download VALTRedundancy.tar.gz by running the following command: {{Code Block - Mini \| text = <span class="code_regex">wget</span> --content-disposition https://ivs.box.com/shared/static/1062styfwr387efew51vt6mzqzsdd1m3.gz <span class="code_option">-O</span> <span class="code_2">VALTRedundancy.tar.gz</span>}}
	# Extract the file using the following command: {{Code Block - Mini \| text = tar -xvf VALTRedundancy.tar.gz}}		# Extract the file using the following command: {{Code Block - Mini \| text = <span class="code_regex">tar</span> <span class="code_option">-xvf</span> <span class="code_2">VALTRedundancy.tar.gz</span>}}

	<hr>		<hr>

IVSWikiBlue at 21:53, 27 July 2023

2023-07-27T21:53:56Z

← Older revision		Revision as of 21:53, 27 July 2023
Line 22:		Line 22:

	=Script Package=		=Script Package=
	# Download VALTRedundancy.tar.gz by running the following command: ~~<div class~~=~~"codeText">~~wget --content-disposition https://ivs.box.com/shared/static/1062styfwr387efew51vt6mzqzsdd1m3.gz -O VALTRedundancy.tar.gz~~</div>~~		# Download VALTRedundancy.tar.gz by running the following command: {{Code Block - Mini \| text = wget --content-disposition https://ivs.box.com/shared/static/1062styfwr387efew51vt6mzqzsdd1m3.gz -O VALTRedundancy.tar.gz}}
	# Extract the file using the following command: ~~<code>~~tar -xvf VALTRedundancy.tar.gz~~</code>~~		# Extract the file using the following command: {{Code Block - Mini \| text = tar -xvf VALTRedundancy.tar.gz}}

	<hr>		<hr>

	=Primary Server Config=		=Primary Server Config=
	Run ~~<code>~~PrimaryServerConfig.sh~~</code>~~ on the primary server. Make sure to modify the variables at the top of the script to reflect your environment. Specifically the standbyip must be changed to the ip address of the standby server.		Run {{Code Block - Mini \| text = PrimaryServerConfig.sh}} on the primary server. Make sure to modify the variables at the top of the script to reflect your environment. Specifically the standbyip must be changed to the ip address of the standby server.

	The script will complete by providing the log file name and position. Make a note of these values as they will be needed to configure the standby server.		The script will complete by providing the log file name and position. Make a note of these values as they will be needed to configure the standby server.
Line 35:		Line 35:

	=Standby Server Config=		=Standby Server Config=
	#Run ~~<code>~~sudo -i~~</code>~~		#Run {{Code Block - Mini \| text = sudo -i}}
	#:If you do not use this specific command portions of the script will not execute properly.		#:If you do not use this specific command portions of the script will not execute properly.
	#Run ~~<code>~~VALTStandbyServerConfig.sh~~</code>~~ on the standby server. Make sure to modify the variables at the top of the script to reflect your environment. Specifically the primaryip must be changed to the ip address of the primary server, the logfile and logpos variables must be set to the values output when running the script on the primary server.		#Run {{Code Block - Mini \| text = VALTStandbyServerConfig.sh}} on the standby server. Make sure to modify the variables at the top of the script to reflect your environment. Specifically the primaryip must be changed to the ip address of the primary server, the logfile and logpos variables must be set to the values output when running the script on the primary server.

	If using the VALTRedundancy.tar.gz package, the failure.sh and restore.sh scripts should automatically be copied to the /usr/local/valt/bin/ directory and set to executable. These scripts are provided below if the VALTRedundancy.tar.gz package was not used. It is a good idea to update the variables in these scripts now so they are ready to be used in the event of a failover.		If using the VALTRedundancy.tar.gz package, the failure.sh and restore.sh scripts should automatically be copied to the {{Code Block - Mini \| text = /usr/local/valt/bin/}} directory and set to executable. These scripts are provided below if the {{Code Block - Mini \| text = VALTRedundancy.tar.gz package}} was not used. It is a good idea to update the variables in these scripts now so they are ready to be used in the event of a failover.

	<hr>		<hr>
Line 46:		Line 46:
	# Update the shared DNS entry to reference the standby server.		# Update the shared DNS entry to reference the standby server.
	# Run the script by typing the following command:		# Run the script by typing the following command:
	#: ~~<code>~~sudo /usr/local/valt/bin/failure.sh~~</code>~~		#: {{Code Block - Mini \| text = sudo /usr/local/valt/bin/failure.sh}}

	<hr>		<hr>
Line 52:		Line 52:
	=How to Return to the Primary Server=		=How to Return to the Primary Server=
	# Update the shared DNS entry to reference the standby server.		# Update the shared DNS entry to reference the standby server.
	# Update the variables in the script below to reflect the correct primary ip, slaveuser, and slavepassword. (If this was not done during initial setup)		# Update the variables in the script below to reflect the correct primary ip, slaveuser, and slavepassword. <em>(If this was not done during initial setup)</em>
	# Run the script by typing the following command:		# Run the script by typing the following command:
	#: ~~<code>~~sudo /usr/local/valt/bin/restore.sh~~</code>~~		#: {{Code Block - Mini \| text = sudo /usr/local/valt/bin/restore.sh}}
	}}		}}

IVSWikiBlue at 21:48, 27 July 2023

2023-07-27T21:48:48Z

← Older revision		Revision as of 21:48, 27 July 2023
Line 58:		Line 58:

	{{Section \| title = <h1>Scripts</h1> \| content =		{{Section \| title = <h1>Scripts</h1> \| content =
	{{Section - Expand \| title = ValtPrimaryServerConfig.sh \| content =		{{Section - Expand \| color = #E6B8B8 \| title = ValtPrimaryServerConfig.sh \| content =
	<pre>		<pre>
	#!/bin/bash		#!/bin/bash
Line 119:		Line 119:
	}}		}}

	{{Section - Expand \| title = ValtStandbyServerConfig.sh \| content =		{{Section - Expand \| color = #E6CFB8 \| title = ValtStandbyServerConfig.sh \| content =
	<pre>		<pre>
	#!/bin/bash		#!/bin/bash
Line 206:		Line 206:
	}}		}}

	{{Section - Expand \| title = failure.sh \| content =		{{Section - Expand \| color = #E6E6B8 \| title = failure.sh \| content =
	<pre>		<pre>
	#!/bin/bash		#!/bin/bash
Line 235:		Line 235:
	}}		}}

	{{Section - Expand \| title = restore.sh \| content =		{{Section - Expand \| color = #CFE6B8 \| title = restore.sh \| content =
	<pre>		<pre>
	#!/bin/bash		#!/bin/bash

IVSWikiBlue at 21:46, 27 July 2023

2023-07-27T21:46:59Z

← Older revision		Revision as of 21:46, 27 July 2023
Line 1:		Line 1:
	{{Aside \| hue = 0 \| icon = ⚠ \| content = <b>DISCLAIMER:</b> This is not a step by step instruction. This article assumes the reader has a working understanding of the VALT application and how to modify the configuration files. This procedure should only be completed by an IVS support engineer. This may be incorporated into the command line menu in the future.}}		{{Aside \| hue = 0 \| icon = ⚠ \| content = <b>DISCLAIMER:</b> This is not a step by step instruction. This article assumes the reader has a working understanding of the VALT application and how to modify the configuration files. This procedure should only be completed by an IVS support engineer. This may be incorporated into the command line menu in the future.}}
	__TOC__		__TOC__
			{{Section \| content =
	=About=		=About=
	~~<div class="section">~~
	The easiest way to achieve a highly available VALT server is by utilizing a VM on a Hypervisor with shared storage that supports High Availability (HA). Both VMWare and Hyper-V have integrated HA capabilities. If there is a need to make the VALT server highly available, IVS strongly recommends deploying the VALT appliance in a virtual environment and leveraging the hypervisor's HA capabilities. If this is not an option, the procedure below will allow you to configure two VALT appliances with one as a primary server and the second as a warm standby. This procedure will configure the MYSQL databases in a master slave configuration and replicate all changes from the primary to the standby server. Video files can be synchronized periodically. The configuration given below will replicate video files on a daily basis, but this can be customized by adjusting the cronjob scheduling.		The easiest way to achieve a highly available VALT server is by utilizing a VM on a Hypervisor with shared storage that supports High Availability (HA). Both VMWare and Hyper-V have integrated HA capabilities. If there is a need to make the VALT server highly available, IVS strongly recommends deploying the VALT appliance in a virtual environment and leveraging the hypervisor's HA capabilities. If this is not an option, the procedure below will allow you to configure two VALT appliances with one as a primary server and the second as a warm standby. This procedure will configure the MYSQL databases in a master slave configuration and replicate all changes from the primary to the standby server. Video files can be synchronized periodically. The configuration given below will replicate video files on a daily basis, but this can be customized by adjusting the cronjob scheduling.
	<~~/div~~>
			<hr>

	=Prerequisites=		=Prerequisites=
	~~<div class="section">~~
	*A DNS entry (CNAME or A) resolving to the primary server.		*A DNS entry (CNAME or A) resolving to the primary server.
	** This should not be the primary DNS entry for that server and will be changed in the event of a failure.		** This should not be the primary DNS entry for that server and will be changed in the event of a failure.
Line 18:		Line 18:
	* The only config file in /etc/apache2/sites-enabled/ should be valt.conf. If default-ssl.conf is in this directory, delete it.		* The only config file in /etc/apache2/sites-enabled/ should be valt.conf. If default-ssl.conf is in this directory, delete it.
	* If using https, the certificate should already be installed on the primary server		* If using https, the certificate should already be installed on the primary server
	<~~/div~~>
			<hr>

	=Script Package=		=Script Package=
	~~<div class="section">~~
	# Download VALTRedundancy.tar.gz by running the following command: <div class="codeText">wget --content-disposition https://ivs.box.com/shared/static/1062styfwr387efew51vt6mzqzsdd1m3.gz -O VALTRedundancy.tar.gz</div>		# Download VALTRedundancy.tar.gz by running the following command: <div class="codeText">wget --content-disposition https://ivs.box.com/shared/static/1062styfwr387efew51vt6mzqzsdd1m3.gz -O VALTRedundancy.tar.gz</div>
	# Extract the file using the following command: <code>tar -xvf VALTRedundancy.tar.gz</code>		# Extract the file using the following command: <code>tar -xvf VALTRedundancy.tar.gz</code>
	<~~/div~~>
			<hr>

	=Primary Server Config=		=Primary Server Config=
	~~<div class="section">~~
	Run <code>PrimaryServerConfig.sh</code> on the primary server. Make sure to modify the variables at the top of the script to reflect your environment. Specifically the standbyip must be changed to the ip address of the standby server.		Run <code>PrimaryServerConfig.sh</code> on the primary server. Make sure to modify the variables at the top of the script to reflect your environment. Specifically the standbyip must be changed to the ip address of the standby server.

	The script will complete by providing the log file name and position. Make a note of these values as they will be needed to configure the standby server.		The script will complete by providing the log file name and position. Make a note of these values as they will be needed to configure the standby server.
	<~~/div~~>
			<hr>

	=Standby Server Config=		=Standby Server Config=
	~~<div class="section">~~
	#Run <code>sudo -i</code>		#Run <code>sudo -i</code>
	#:If you do not use this specific command portions of the script will not execute properly.		#:If you do not use this specific command portions of the script will not execute properly.
Line 40:		Line 40:

	If using the VALTRedundancy.tar.gz package, the failure.sh and restore.sh scripts should automatically be copied to the /usr/local/valt/bin/ directory and set to executable. These scripts are provided below if the VALTRedundancy.tar.gz package was not used. It is a good idea to update the variables in these scripts now so they are ready to be used in the event of a failover.		If using the VALTRedundancy.tar.gz package, the failure.sh and restore.sh scripts should automatically be copied to the /usr/local/valt/bin/ directory and set to executable. These scripts are provided below if the VALTRedundancy.tar.gz package was not used. It is a good idea to update the variables in these scripts now so they are ready to be used in the event of a failover.
	<~~/div~~>
			<hr>

	=How to Initiate a Failover to the Standby Server=		=How to Initiate a Failover to the Standby Server=
	~~<div class="section">~~
	# Update the shared DNS entry to reference the standby server.		# Update the shared DNS entry to reference the standby server.
	# Run the script by typing the following command:		# Run the script by typing the following command:
	#: <code>sudo /usr/local/valt/bin/failure.sh</code>		#: <code>sudo /usr/local/valt/bin/failure.sh</code>
	<~~/div~~>
			<hr>

	=How to Return to the Primary Server=		=How to Return to the Primary Server=
	~~<div class="section">~~
	# Update the shared DNS entry to reference the standby server.		# Update the shared DNS entry to reference the standby server.
	# Update the variables in the script below to reflect the correct primary ip, slaveuser, and slavepassword. (If this was not done during initial setup)		# Update the variables in the script below to reflect the correct primary ip, slaveuser, and slavepassword. (If this was not done during initial setup)
	# Run the script by typing the following command:		# Run the script by typing the following command:
	#: <code>sudo /usr/local/valt/bin/restore.sh</code>		#: <code>sudo /usr/local/valt/bin/restore.sh</code>
	~~</div>~~		}}

	=Scripts=		{{Section \| title = <h1>Scripts</h1> \| content =
	===ValtPrimaryServerConfig.sh===		{{Section - Expand \| title = ValtPrimaryServerConfig.sh \| content =
	<~~nowiki~~>#!/bin/bash		<pre>
			#!/bin/bash
	# This script will configure an existing VALT server to function as a primary server.		# This script will configure an existing VALT server to function as a primary server.
	# You will need to run VALTStandbyServerConfig.sh on the warm standby server.		# You will need to run VALTStandbyServerConfig.sh on the warm standby server.
Line 114:		Line 115:
	echo -e "Master Log File: $sqlfile"		echo -e "Master Log File: $sqlfile"
	echo -e "Master Log Position: $position"		echo -e "Master Log Position: $position"
	fi</~~nowiki~~>		fi
			</pre>
			}}

	===ValtStandbyServerConfig.sh===		{{Section - Expand \| title = ValtStandbyServerConfig.sh \| content =
	<~~nowiki~~>		<pre>
	#!/bin/bash		#!/bin/bash
	# This script will configure an existing VALT server to function as a		# This script will configure an existing VALT server to function as a
Line 200:		Line 203:
	chmod +x /usr/local/valt/bin/restore.sh		chmod +x /usr/local/valt/bin/restore.sh
	fi		fi
			</pre>
			}}

	~~</nowiki>~~		{{Section - Expand \| title = failure.sh \| content =
			<pre>
	===failure.sh===
	<~~nowiki~~>
	#!/bin/bash		#!/bin/bash
	#This script will make the redundant VALT server the primary VALT server.		#This script will make the redundant VALT server the primary VALT server.
Line 229:		Line 232:
	service valtcontrols start		service valtcontrols start
	fi		fi
			</pre>
			}}

	~~</nowiki>~~		{{Section - Expand \| title = restore.sh \| content =
	===restore.sh===		<pre>
	<~~nowiki~~>
	#!/bin/bash		#!/bin/bash
	# This script will migrate the database and all recordings back to the primary VALT server.		# This script will migrate the database and all recordings back to the primary VALT server.
Line 276:		Line 280:
	mysql --defaults-extra-file=/usr/local/valt/conf/standby.cnf -e "START SLAVE;"		mysql --defaults-extra-file=/usr/local/valt/conf/standby.cnf -e "START SLAVE;"
	fi		fi
			</pre>
	</~~nowiki~~>		}} }}

IVSWikiBlue at 16:31, 27 July 2023

2023-07-27T16:31:29Z

← Older revision		Revision as of 16:31, 27 July 2023
Line 1:		Line 1:
			{{Aside \| hue = 0 \| icon = ⚠ \| content = <b>DISCLAIMER:</b> This is not a step by step instruction. This article assumes the reader has a working understanding of the VALT application and how to modify the configuration files. This procedure should only be completed by an IVS support engineer. This may be incorporated into the command line menu in the future.}}
			__TOC__
	=About=		=About=
	<div class="section">		<div class="section">
	The easiest way to achieve a highly available VALT server is by utilizing a VM on a Hypervisor with shared storage that supports High Availability (HA). Both VMWare and Hyper-V have integrated HA capabilities. If there is a need to make the VALT server highly available, IVS strongly recommends deploying the VALT appliance in a virtual environment and leveraging the hypervisor's HA capabilities. If this is not an option, the procedure below will allow you to configure two VALT appliances with one as a primary server and the second as a warm standby. This procedure will configure the MYSQL databases in a master slave configuration and replicate all changes from the primary to the standby server. Video files can be synchronized periodically. The configuration given below will replicate video files on a daily basis, but this can be customized by adjusting the cronjob scheduling.		The easiest way to achieve a highly available VALT server is by utilizing a VM on a Hypervisor with shared storage that supports High Availability (HA). Both VMWare and Hyper-V have integrated HA capabilities. If there is a need to make the VALT server highly available, IVS strongly recommends deploying the VALT appliance in a virtual environment and leveraging the hypervisor's HA capabilities. If this is not an option, the procedure below will allow you to configure two VALT appliances with one as a primary server and the second as a warm standby. This procedure will configure the MYSQL databases in a master slave configuration and replicate all changes from the primary to the standby server. Video files can be synchronized periodically. The configuration given below will replicate video files on a daily basis, but this can be customized by adjusting the cronjob scheduling.
	</div>		</div>

	~~=Disclaimer=~~
	~~<div class="floating_card"><b>~~
	This is not a step by step instruction. This article assumes the reader has a working understanding of the VALT application and how to modify the configuration files. This procedure should only be completed by an IVS support engineer. This may be incorporated into the command line menu in the future.
	~~</b></div>~~

	=Prerequisites=		=Prerequisites=

IVSWikiBlue at 20:00, 2 August 2022

2022-08-02T20:00:02Z

← Older revision		Revision as of 20:00, 2 August 2022
Line 50:		Line 50:
	# Run the script by typing the following command:		# Run the script by typing the following command:
	#: <code>sudo /usr/local/valt/bin/failure.sh</code>		#: <code>sudo /usr/local/valt/bin/failure.sh</code>
			</div>

	=How to Return to the Primary Server=		=How to Return to the Primary Server=
			<div class="section">
	# Update the shared DNS entry to reference the standby server.		# Update the shared DNS entry to reference the standby server.
	# Update the variables in the script below to reflect the correct primary ip, slaveuser, and slavepassword. (If this was not done during initial setup)		# Update the variables in the script below to reflect the correct primary ip, slaveuser, and slavepassword. (If this was not done during initial setup)

IVSWikiBlue: /* Disclaimer */

2022-08-02T19:55:24Z

Disclaimer

← Older revision		Revision as of 19:55, 2 August 2022
Line 5:		Line 5:

	=Disclaimer=		=Disclaimer=
	<div class="~~section~~">		<div class="floating_card"><b>
	This is not a step by step instruction. This article assumes the reader has a working understanding of the VALT application and how to modify the configuration files. This procedure should only be completed by an IVS support engineer. This may be incorporated into the command line menu in the future.		This is not a step by step instruction. This article assumes the reader has a working understanding of the VALT application and how to modify the configuration files. This procedure should only be completed by an IVS support engineer. This may be incorporated into the command line menu in the future.
	</div>		</b></div>

	=Prerequisites=		=Prerequisites=