472Config

<?xml version="1.0"?>
	<!--Leave the version information intact-->
	<Settings version="4.7.2">

		<!--
		***************************************************************************
		*
		*		Mandatory configuration section
		*		All fields in this section must be configured in order for the script to work
		*
		***************************************************************************
		-->

		<!--
		*******************************************************************************
		*
		*	Credentials used for gathering the data
		*	You need to use the same credentials for all load balancers
		*
		*	For security reasons I'd advise you to create a dedicated user for this script using the following settings
		*	Role: Guest
		*	Partition Access: All
		*	Terminal Access: Disabled
		*
		*******************************************************************************
		-->

		<Credentials>
			<Username>EngF5Audr</Username>
			<Password>ejrtjjjet57</Password>
		</Credentials>

		<!--
		**************************************************************************************************************************************
		*
		*	This variable contains the load balancers which configuration you want base the report on.
		*
		*	Example:
		*	<Loadbalancers>
		*		<Loadbalancer>10.1.0.20</Loadbalancer>
		*		<Loadbalancer>192.168.1.23</Loadbalancer>
		*	</Loadbalancers>
		*
		**************************************************************************************************************************************
		-->

		<Loadbalancers>
			<Loadbalancer>10.60.88.15</Loadbalancer>
		</Loadbalancers>


		<!--
		**************************************************************************************************************************************
		*
		*	Which folder to store the generated report in. Can be a local path or a network path.
		*
		*	Examples
		*	<ReportRoot>D:\Inetpub\wwwroot\</ReportRoot>
		*	or
		*	<ReportRoot>\\aserver.domain.local\wwwshare$\</ReportRoot>
		*
		**************************************************************************************************************************************
		-->

		<ReportRoot>C:\Inetpub\wwwroot\</ReportRoot>

		<!--
		**************************************************************************************************************************************
		*
		*	Name the default document
		*	IIS users might want to set this to default.htm
		*	Apache users might want to set this to index.html
		*
		*	Examples:
		*	<DefaultDocument>default.html</DefaultDocument>
		*	or
		*	<DefaultDocument>index.html</DefaultDocument>
		*
		**************************************************************************************************************************************
		-->

		<DefaultDocument>default.html</DefaultDocument>

		<!--
		************************************************************
		*
		*	Optional configuration below
		*	The section below contains optional configuration.
		*
		*	Leave as is, or configure as you like.
		*
		************************************************************
		-->

		<!--
		**************************************************************************************************************************************
		*
		*	Log settings
		*
		*	<Enabled>		-	Determines if the logging is enabled or not. If it is enabled you MUST configure the other settings too.
		*	<LogFilePath>	- 	Where to store the log. Can also be a share.
		*	<LogLevel>		-	Which level to log. Verbose = Informational messages included, Normal = only errors/warnings
		*	<MaximumLines>	-	How many lines the logfile should be kept at (will be pruned at the end of script runtime). Depending on your environment, but you'll want to set this to a quite high number.
		*
		*	Example of enabled logging:
		*	<Logsettings>
		*		<Enabled>true</Enabled>
		*		<LogFilePath>C:\Script\Log\bigipreport.log</LogFilePath>
		*		<LogLevel>Verbose</LogLevel>
		*		<MaximumLines>100000</MaximumLines>
		*	</LogSettings>
		*
		*	Example of disabled logging:
		*	<LogSettings>
		*		<Enabled>false</Enabled>
		*		<LogFilePath></LogFilePath>
		*		<LogLevel></LogLevel>
		*		<MaximumLines></MaximumLines>
		*	</LogSettings>
		*
		**************************************************************************************************************************************
		-->

		<LogSettings>
			<Enabled>false</Enabled>
			<LogFilePath></LogFilePath>
			<LogLevel></LogLevel>
			<MaximumLines></MaximumLines>
		</LogSettings>

		<!--
		**************************************************************************************************************************************
		*
		*	This section controls how much information you want to see on the screen.
		*	Useful for debugging, but there's no harm to leave it on verbose
		*
		*	Levels:
		*	Normal 		- Only errors
		*	Verbose		- Informational messages too
		*
		*	Examples:
		*	<Outputlevel>Normal</Outputlevel>
		*	<Outputlevel>Verbose</Outputlevel>
		*
		**************************************************************************************************************************************
		-->

		<Outputlevel>Verbose</Outputlevel>


		<!--
			**************************************************************************************************************************************
			*
			*	Pool exceptions contains pools you don't want shown in the report, for instance any syslog pools.
			*	Can be left blank ($Global:poolexceptions = @())
			*
			*	Example:
			*	<PoolExceptions>
			*		<PoolException>/Common/mypool</PoolException>
			*		<PoolException>/Common/invisiblepool</PoolException>
			*		<PoolException>/Common/syslog_pool</PoolException>
			*		<PoolException>/MyPartition/anotherpool</PoolException>
			*	</PoolExceptions>
			*
			**************************************************************************************************************************************
		-->

		<PoolExceptions>
		</PoolExceptions>

		<!--
			**************************************************************************************************************************************
			*
			*	In many cases the load balancer is using internal virtual addresses while letting the firewall do the NAT.
			*	If you want to add external IP translation you can put them in a file.
			*
			*	The text file should contain rows with the format [public ip]=[private ip]
			*	1.1.1.1=10.10.10.1
			*	1.1.1.2=10.10.10.2
			*
			*	Examples of enabled nat file:
			*	<NATFilePath>C:\NATs\natfile.nat</NATFilePath>
			*	or
			*	<NATFilePath>\\myserver\share\natfile.txt</NATFilePath>
			*
			*	Example of disabled NAT file
			*	<NATFilePath></NATFilePath>
			*
			**************************************************************************************************************************************
		-->

		<NATFilePath></NATFilePath>

		<!--
			**************************************************************************************************************************************
			*
			*	This variable enables or disables the use of TLS1.2. If disabled the script will revert to TLS1.0
			*
			*	To enable, set the variable to true, otherwise false
			*
			*	Example:
			*	<UseTLS12>true</UseTLS12>
			*	or
			*	<UseTLS12>false</UseTLS12>
			*
			**************************************************************************************************************************************
		-->

		<UseTLS12>true</UseTLS12>

		<!--
			**************************************************************************************************************************************
			*
			*	In this section you can choose to hide partition information to save space in the report.
			*	To show, set to true. To hide, set to false.
			*
			*	Example:
			*	<PartitionInformation>
			*		<ShowPoolPartition>false</ShowPoolPartition>
			*		<ShowPoolMemberPartition>false</ShowPoolMemberPartition>
			*	</PartitionInformation>
			*
			**************************************************************************************************************************************
		-->

		<PartitionInformation>
			<ShowPoolPartition>false</ShowPoolPartition>
			<ShowPoolMemberPartition>false</ShowPoolMemberPartition>
		</PartitionInformation>

		<!--

		Here you can configure individual iRule you want to expose to the clients.
		These will be available in the iRules section even if iRules are disabled below.

		Example:
		<iRules>
			<iRule>
				<Loadbalancer>f501.j.local</Loadbalancer>
				<iRuleName>/Common/miscvip.j.local-pool_selection</iRuleName>
			</iRule>
			<iRule>
				<Loadbalancer>f502.j.local</Loadbalancer>
				<iRuleName>/Common/generate_ga_code</iRuleName>
			</iRule>
		</iRules>

		-->

		<iRules>
		</iRules>

		<!--
			**************************************************************************************************************************************
			*
			*	In this section you can choose to hide the load balancer TLD section to save space in the report.
			*	This means that "loadbalancername.mydomain.local" is shown as "loadbalancername"
			*
			*	Example:
			*	<HideLoadBalancerFQDN>true</HideLoadBalancerFQDN>
			*
			**************************************************************************************************************************************
		-->

		<HideLoadBalancerFQDN>true</HideLoadBalancerFQDN>

		<!--
			**************************************************************************************************************************************
			*
			*	Error reporting
			*	This means that "loadbalancername.mydomain.local" is shown as "loadbalancername"
			*
			*	<Enabled>	 	This variable controls if the reports sends emails or not.
			*					Note that if you use this one you MUST configure the mailerrorto and mailfrom variables too.
			*					Set to true to enable. False to disable
			*
			*	<Sender>		This is the variable containing the sender mail of the report.
			*
			*	<Recipients>	Contains the recipients of the report. Multiple recipients can be configured.
			*
			*	<SMTPServer>	Contains the address to the smtp server.
			*
			*	Example of enabled error reporting
			*	<ErrorReporting>
			*		<Enabled>true</Enabled>
			*		<Sender>myscript@mydomain.com</Sender>
			*		<Recipients>
			*			<Recipient>opsteam@mydomain.com</Recipient>
			*		</Recipients>
			*		<SMTPServer>mysmtpserver.mydomain.com</SMTPServer>
			*	</ErrorReporting>
			*
			*	Example of disabled error reporting:
			*	<ErrorReporting>
			*		<Enabled>false</Enabled>
			*	</ErrorReporting>
			-->

			<ErrorReporting>
				<Enabled>true</Enabled>
				<Sender>shanop@zapga.com</Sender>
					<Recipients>
					    <Recipient>phill.shannon@zapa.com</Recipient>
					</Recipients>
					<SMTPServer>exintxopen.zapa.com</SMTPServer>
				</ErrorReporting>


		<!--

			**************************************************************************************************************************************
			*
			*	Share the report should authenticate
			*	Used if the report is generated on a separate server
			*
			*	Example of share config:
			*	<Shares>
			*		<Share>
			*				<Path>\\myserver\myshare</Path>
			*				<Username>shareuser</Username>
			*				<Password>password</Password>
			*		</Share>
			*	</Shares>
			*
			*	Example of no share
			*	<Shares>
			*	</Shares>
			*
			**************************************************************************************************************************************

		-->

			<Shares>
			</Shares>

				<!--

			***********************************************************************************************************************************************
			*
			*	Global irules configuration
			*	Here you can configure if virtual server irules and data group lists should be listed and if they should be linked
			*
			*	Note:
			*	If you set any of these options to from true to false the report will clear any information in the next update from the json files
			*	in order to make sure that no unwanted data is available to clients
			*
			*	Right now you can't configure data group list links unless irules are enabled.
			*	Let me know if this is an issue and I'll see if I can fix it in a future version.
			*
			*	Example of when irules are showing in the virtual server details and both irules + data group lists are available for clients to see:
			*	<iRules>
			*		<Enabled>true</Enabled>
			*		<ShowiRuleLinks>true</ShowiRuleLinks>
			*		<ShowDataGroupListLinks>true</ShowDataGroupListLinks>
			*	</iRules>
			*
			*	Example of when irules are showing in the virtual server details, irules are available, but not the data group lists:
			*	<iRules>
			*		<Enabled>true</Enabled>
			*		<ShowiRuleLinks>true</ShowiRuleLinks>
			*		<ShowDataGroupListLinks>false</ShowDataGroupListLinks>
			*	</iRules>
			*	Example of when no iRules or data group lists is shown at all in the virtual server details:
			*	<iRules>
			*		<Enabled>false</Enabled>
			*		<ShowiRuleLinks>false</ShowiRuleLinks>
			*		<ShowDataGroupListLinks>false</ShowDataGroupListLinks>
			*	</iRules>
			*
			************************************************************************************************************************************************

		-->

			<iRules>
				<Enabled>true</Enabled>
				<ShowiRuleLinks>true</ShowiRuleLinks>
				<ShowDataGroupListsLinks>true</ShowDataGroupListsLinks>
			</iRules>

		<!--

			***********************************************************************************************************************************************
			*
			*	Export link settings
			*
			*	Enabled:
			*	<ExportLink>
			*		<Enabled>true</Enabled>
			*	</ExportLink>
			*
			*	Disabled:
			*	<ExportLink>
			*		<Enabled>false</Enabled>
			*	</ExportLink>			*
			************************************************************************************************************************************************

		-->

		<ExportLink>
			<Enabled>true</Enabled>
		</ExportLink>

	</Settings>