Foglight Evolve 9.2 - Administration and Configuration Guide

Management Server View and Management Server Metrics

The Management Server View dashboard is useful for examining the server performance. It can help you diagnose potential performance problems and identify bottlenecks in your environment.

Object Groups

Most of the object groups needed for service monitoring already exist. Administrators can use the Object Groups dashboard to classify a group of data and then use the Tier Definition dashboard to subscribe to which data groupings you want to use as tiers. Object groups do not bind to data.

An object group is a mapping to a certain set of data types of the objects you are interested in. Once an object group is defined, its mapping can be evaluated to return these objects. Because the result depends on what exist in Foglight by the time the evaluation is done, its membership list may vary.

Foglight ships with a number of default object groups and subgroups. These groups are marked as Created by Foglight and cannot be changed or deleted.

If an object group is used as a tier, it cannot be deleted. If an object group or object subgroup is used in a rule to define a dynamic group of components in a service, it cannot be deleted.

An object group cannot be used to define a rule in the Service Builder unless it contains more than one subgroup. Conversely, you are not allowed to delete all subgroups from an object group if the object group is used to create a rule to dynamically include a group of components in a service.

After creating an object group, you need to add one or more subgroups to that group. For more information, see Create an object subgroup.

An object subgroup contains one or more objects, selected using a common criteria, that make up that subgroup.For example you can create a subgroup that contains all agent instances whose names start with “tor”.

Use the Tier Definitions dashboard to associate an object group to a tier. A tier is another logical component that references one or more object groups, based on some common criteria. This type of logical structure helps you investigate performance problems associated with multiple objects. For example, to investigate the state of the monitored components within a tier, drill down on a tier and investigate the hosts that are related to it. For more information about services, see the Foglight User Guide.

The object groups that are made available in the Tier Definitions dashboard are based on object groups that were created using the Object Groups dashboard. For more information, see Create an object group.

The Object Groups that you select in the Tier Definitions dashboard appear in the Tier drop down list when selecting a new local or global service using the Service builder dashboard. These tiers are also used in the Service Operations Console, where they show service breakdown by tier.

NOTE: New tiers are hidden by default in the Service Operations Console. To display a new tier, in the Service Operations Console, click Customize Service Operations Console, open the Tier Selector tab, and ensure the newly-created tier is selected. For more information about the Service Operations Console, see the related help page.

The FMS Overview view is a starting point for performance analysis of the Foglight Management Server. It displays information about the database activity, data service performance, JVM performance, and server load in one unified view.

In federated environments, explore the diagnostics for each individual server: Federation Master, Federation Child, or a standalone Foglight Management Server. To do that, click Choose a Foglight Server and select a host from the list that appears.

This view provides more information on:

NOTE: To populate the metrics showing database inserts per 5 minutes for Oracle and SQL Server, you need to grant additional permissions to the database user. For more information, see Grant permissions to explore database activities.

Table 16. The following table describes what type of information to look for in the Performance Overview view.

To find out about…	See this view	Performance implications
Database inserts		Database insert spikes, slow processing
Data handling		Incoming data spikes (batchesProcessed increases), slow processing (batchesDiscarded increases)
Memory utilization		Too large topology, too much incoming data (freeMemory increases)
Server load		Load is higher than 0.7

The Agents view is designed to see what agents you are running, listed by type. By selecting agent types in the tree, a graph showing the number of agents as a function of time is plotted. This graph is handy for viewing changes to the agents, for example if a number of agents that you did not know about were added, or checking if old agents are properly removed.

The Baseline Measurements view shows internal database I/O statistics related to baseline computation. A metric baseline is the expected metric range for the given time period. When configured, IntelliProfile computes baselines for metrics, and stores that data in the database.

Table 17. Look for the following types of information in the Baseline Measurements view.

To find out about…	See this view	Performance implications
Loaded baseline data		High peaks in the graph usually indicate an impact on the database performance, depending on the database capabilities.
Stored baseline data		High peaks in the graph usually indicate an impact on the database performance, depending on the database capabilities.
Server requests to load baseline data		High values in the graph may be a sign that baselining activities have a high impact on the database performance, depending on the database capabilities.
The number of metrics whose baseline data is removed from the database		This graph shows zero values at all times, unless baseline profiles are explicitly removed for trouble-shooting purposes, usually requiring manual intervention.
The number of requests to remove baseline profiles		This graph shows zero values at all times, unless baseline profiles are explicitly removed for trouble-shooting purposes, usually requiring manual intervention.
The number of server attempts to store baseline data		Normally these values should correspond to those appearing in the Store Call Count graph. If they are greater that means that some attempts failed due to database-related errors.
The number of requests to store baseline data		High peaks in the graph usually indicate an impact on the database performance, depending on the database capabilities.
The number of baseline management operations		High peaks in the graph usually indicate an impact on the database performance, depending on the database capabilities.
The number of outstanding baseline management operations		Outstanding baseline management operations can include enabling or disabling baselines for a particular metric. This graph can be expected to show zero values at all times.

The Connectivity view shows the Foglight connectivity for the JDBC connection pool and the user session count. It summarizes the database connection state from the perspective of the Foglight Management Server. By looking at this view, you can determine if there are enough JDBC connections to service application requests.

To find out about…	See this view	Performance implications
JDBC connections		Overused pool indicates a slow database.
User sessions		High number of sessions results in a high browser interface load, indicating a slow browser interface/server.

The Database Overview view displays the metrics that represent the reads, inserts, and updates of the database rows. These metrics can be used in performance load tests to track the unit load.

Contents of this view includes a drop down to select the host name. Here, you can select a Federation Master, Federation Child, or standalone server. To do that, click Choose a Foglight Server and select a host from the list that appears. It also contains the following embedded views:

The name of the metrics that contain database reads, inserts, and updates depend on the type of the supported database that Foglight uses to store information, as indicated in the following table.

Table 19. Database and recording metric types.

Database	Metric
MS SQL, PostgreSQL	num_rows_deleted
	num_rows_inserted
	num_rows_updated
MySQL	innodb_rows_inserted
	innodb_rows_inserted_per5min: #innodb_rows_inserted# * 300
	avg_inserts_per5min: avg(#innodb_rows_inserted_per5min for 60 minutes#)
Oracle	qa_db_inserts : select sum(inserts) from sys.dba_tab_modifications where TABLE_OWNER='xxxx'
	delta_db_inserts: delta(#qa_db_inserts from QA_DB_INSERTS_Agent_Table_DB_INSERT_COUNT#)
	delta_avg_per5min: avg(#delta_db_inserts for 60 minutes#)

NOTE: Permissions for MySQL and PostgreSQL are granted automatically. However, to populate the database dashboard metrics for Oracle and Microsoft SQL Server, special permissions must be granted for the database user in the Foglight Management Server. For more information, see Grant permissions to explore database activities.

Table 20. The following table describes what type of information to look for in the Database Overview view.

To find out about…	See this view	Performance implications
Database row operations		High number of database operations may indicate a possible database bottleneck. The cause could be related to a problem on the server sid, such as topology changes.
Database I/O		High load may indicate a possible database bottleneck. Check the database specifications.
Database buffer		May indicate a dirty database buffer, possibly because the innodb pool buffer is too small.
Database inserts		Check if there is anything more than row operations.

This view shows the invocation counts of and time spent on garbage collection. It contains two embedded views:

The Java Virtual Machine (JVM) view provides full details on the JVM memory activity. This view is particularly useful if you are performing detailed JVM tuning for the different memory spaces.

To find out more about the JVM heap generation, observe the spikes on the embedded views. Big spikes with a slow climb are better than small spikes (too little available memory) or a quick climb (frequent garbage collection).

This view shows the number of rulettes (rule instances) that are bound to specific object instances. This view is useful for understanding the environment complexity.

The Rulette and Topology view shows how many rules and rule instances are running. Many rulettes, especially as a function of the number of objects, can indicate that you are overloading your server or if some old rules are still running.

This view lists Foglight scripts with the script ID, script name, sum (ms), count, the difference between minimum and maximum invocation time, and the name of the cartridge in which the script is defined. A plot summary of the script invocation time also appears.

This view shows the Foglight Management Server load metrics and JVM performance.

This view highlights the data and metrics that are being processed in time or getting discarded.

The Service - Data & Message view shows details on data handling of the Foglight Management Server such as the number of skipped messages and the number of discarded metrics. The top-right embedded view shows the percentage of data that is dropped by the server over time, while the top-left embedded view shows the counts of total and skipped messages over time. A high percentage of dropped data can often indicate a server overload. The embedded view in the bottom right is useful for indicating how long data processing is expected to take. If that value grows over time, that is a good indication that the Foglight Management Server cannot keep up with the load from the agents.

The Service - Derivation and Query view shows activity in the derivation and query service such as the number of evaluations, rulettes, errors, and cache performance.

This view shows a mix of graphs that indicate the cost of metrics such as how many derived metrics are running in the Foglight Management Server, how many metric evaluations have occurred, and information on finding metrics in memory. Metrics are resource-demanding if there are a lot of derived metrics compared to the number of topology objects, or if the memory settings are such that no metric history is being kept in memory.

The Service - Persistence view shows metric details for the Foglight Management Server that is related to:

This view shows the number of topology changes, skipped messages, and total messages. This view is useful for understanding the topology structure relating to agent activity.

The Service - Topology & Agent Manager is a two-part view.

The UI Query Time view is similar to the Script Invocation Time view (see page 204) except that it shows tables for a query instead of a script.

This view shows a query table listing the query name, query ID, amount of time spent on invocation, count, and difference between minimal and maximal invocation time. A graph summarizing query invocation time also appears.

Some Foglight dashboards have reports associated with them. This allows you to run a report based on the current dashboard. You can generate the report using the Reports menu in the top-right corner.

The Performance Overview dashboard and Management Server View are associated with the Management Server Performance Summary Report. Run this report by choosing Management Server Performance Summary Report from the Reports menu, and specifying the input parameters in the report wizard.

The report wizard provides more information about the Management Server Performance Summary Report and instructions on how to set the input values. For more information about reports in Foglight, see the Foglight User Help.

Foglight Agent Manager Performance Overview

The Overview view shows the numbers of remote hosts and Foglight agent instances that are connected to the Foglight Management Server. It also shows the maximal length of time spent by the Agent Manager (FglAM) on data polling.

The Message Processing tab shows tables for the number of pending messages and the number of incoming queue threads for a selected FglAM instance.

The Clock Skew tab contains a graph that displays the upstream difference per second for a selected FglAM instance.

The Bandwidth tab displays metrics for bandwidth usage samples taken at prescribed intervals per second for a selected FglAM instance, including the bytes in, bytes out, and real request time for a selected servlet. The bandwidth statistics reflect the bandwidth (bytes per second) used by the FglAM instance data over a specific time interval.

The Misbehaving Clients tab displays the disconnections per count for a selected FglAM instance.

The XML Serialization tab shows tables of the serialization rate and time for the message serialization to and from XML for a selected FglAM instance.

The CPU tab displays the amount of time the CPU associated with a selected FglAM instance spends executing active processes and their number. For example, a sudden increase in CPU time may indicate that the user code is running inefficiently or a possible runaway process. Also, high CPU loads sometimes suggest that the host needs more CPU power to run efficiently.

The Memory Usage tab displays the amount of available memory and swap space for a selected FglAM instance. For example, a shortage of swap space often suggests a memory shortage, while a decline in the available memory may indicate a memory leaking process.

The CDT Submission tab displays information about the complexity of data that agents collect and submit for Canonical Data Transform (CDT) processing. Excessively large values or sudden increases in this data can result in performance problems.

The following metrics are displayed for each agent:

Backing Up and Restoring Foglight

The following table shows the possible ways of backing up Foglight, some of which include the backup of the file system, and in some cases the system registry (on Windows). Each option shows a sequence of actions that can be performed to back up Foglight.

Table 21. Options for backing up Foglight.

Foglight Single Tier
	Foglight Management Server on Windows with embedded MySQL
Option 1			• Stop the Foglight Management Server. • Perform a full system backup, including the file system and the Windows Registry.
Option 2			• Issue a mysqldump command to export the MySQL database. Alternatively, use the InnoDB HotBackup tool to back up the embedded MySQL database. TIP: To restore the database after backing it up with the mysql command, use MySQL. To restore the database after backing it up with InnoDB HotBackup and applying the logs, shut down the Foglight Management Server, copy the backup files to <Foglight_home>/mysql/data, and start the Foglight Management Server • Perform a full system backup, including the file system and the Windows Registry, but excluding the MySQL data and transaction logs.
Option 3			• Issue a mysqldump command to export the MySQL database to a remote drive or a backup tape. TIP: This option does not require backing up the Foglight installation directory. To restore Foglight after choosing this backup method, you need to complete the following actions: 1. Install the Foglight Management Server and any cartridges that existed in the previous installation. 2. Shut down Foglight. 3. Delete the MySQL data files. 4. Start MySQL and import the exported dump file. 5. Shut down MySQL. 6. Start Foglight. Alternatively, instead of steps 3 through 6, use the InnoDB HotBackup tool to back up the embedded MySQL database.
	Foglight Management Server on Windows with embedded PostgreSQL
Option 1			• Stop the Foglight Management Server. • Use the zip tool to compress the installation directory of the Foglight Management Server. TIP: If you want to restore the database to a non-embedded PostgreSQL server, see the “Foglight Two Tier” section followed in this table.
	Foglight Management Server on Unix with embedded MySQL
Option 1			• Stop the Foglight Management Server. • Create a TAR or a ZIP file containing the Foglight installation directory and copy it to a remote drive or a backup tape. TIP: The ZIP format is recommended. TAR files can result in corrupted binary and MySQL data files.
Option 2			• Issue a mysqldump command to export the MySQL database to a remote drive or a backup tape. Alternatively, use the InnoDB HotBackup tool to back up the embedded MySQL database. • Create a TAR or a ZIP file containing the Foglight installation directory, excluding the MySQL data files, and copy it to a remote drive or a backup tape. TIP: The ZIP format is recommended. TAR files can result in corrupted binary and MySQL data files.
	Foglight Management Server on Unix with embedded PostgreSQL
Option 1			• Stop the Foglight Management Server. • Create a TAR or a ZIP file containing the Foglight installation directory and copy it to a remote drive or a backup tape. TIP: The ZIP format is recommended. TAR files can result in corrupted binary and PostgreSQL data files. The following is the example of backup commands: ZIP: zip -r Foglight.zip <Foglight_home> TAR: tar -cvf Foglight.tar <Foglight_home> TAR.GZ: tar -zcvf Foglight.tar.gz <Foglight_home> TIP: To restore the database, copy the compressed file to the desired directory and extract this file to the installation directory. If you want to restore the database to a non-embedded PostgreSQL server, see the “Foglight Two Tier” section followed in this table.
Foglight Two Tier
	Foglight Management Server on Windows with MS SQL Server on a remote computer
Option 1			• Use MS SQL tools to back up the database. TIP: To restore the database after choosing this backup method, use MS SQL tools. • Stop the Foglight Management Server. • Use backup tools from your Windows environment to back up the Foglight installation directory.
	Foglight Management Server on Windows with MySQL on a remote computer
Option 1			• Issue a mysqldump command to export the MySQL database. TIP: To restore the database after choosing this backup method, use MySQL. • Stop the Foglight Management Server. • Use backup tools from your Windows environment to back up the Foglight installation directory.
	Foglight Management Server on Windows with PostgreSQL on a remote computer
Option 1			• Stop the Foglight Management Server. • Issue a pg_dump command to export the PostgreSQL database. TIP: To restore the database after choosing this backup method, use PostgreSQL. • Use the root account to dump the Foglight datase. The following is the example of commands: The default password is “foglight” that was set during the installation. The database information can be found in the server.database.* settings under <Foglight_home>/config/server.config. pg_dump.exe -Fc -d foglight -p 15432 -U root -W > <backup_path>/foglightDB.dmp • Use backup tools from your Windows environment to back up the Foglight installation directory.
	Foglight Management Server on Unix with MySQL on a remote computer
Option 1			• Issue a mysqldump command to export the MySQL database. TIP: To restore the database after choosing this backup method, use MySQL. • Stop the Foglight Management Server. • Create a TAR or a ZIP file containing the Foglight installation directory and copy it to a remote drive or a backup tape. TIP: The ZIP format is recommended. TAR files can result in corrupted binary and MySQL data files.
	Foglight Management Server on Windows with Oracle on a remote computer
Option 1			• Use Oracle tools to back up the database. TIP: To restore the database after choosing this backup method, use Oracle tools. • Stop the Foglight Management Server. • Use backup tools from your Windows environment to back up the Foglight installation directory.
	Foglight Management Server on Unix with Oracle on a remote computer
Option 1			• Use Oracle tools to back up the database. TIP: To restore the database after choosing this backup method, use Oracle tools. • Stop the Foglight Management Server. • Create a TAR or a ZIP file containing the Foglight installation directory and copy it to a remote drive or a backup tape. TIP: The ZIP format is recommended. TAR files can result in corrupted binary and MySQL data files.
	Foglight Management Server on Unix with PostgreSQL on a remote computer
Option 1			• Stop the Foglight Management Server. • Issue a pg_dump command to export the PostgreSQL database. TIP: To restore the database after choosing this backup method, use PostgreSQL. • Use the root account to dump the Foglight datase. The following is the example of commands: The default password is “foglight” that was set during the installation. The database information can be found in the server.database.* settings under <Foglight_home>/config/server.config. pg_dump -Fc -d foglight -p 15432 -U root -W > <backup_path>/foglightDB.dmp • Create a TAR or a ZIP file containing the Foglight installation directory and copy it to a remote drive or a backup tape. TIP: The ZIP format is recommended. TAR files can result in corrupted binary and PostgreSQL data files.

The procedures below contain detailed information on how to back up the Foglight installation directory and the database, without backing up the file system or the system registry (on Windows).

IMPORTANT: If you are using an external database and intend to upgrade Foglight after backing it up, you should leave the database running. Doing so allows the installer to successfully upgrade the database.

NOTE: Failing to shut down the Foglight Management Server correctly may result in errors.

Table 22. Where to find more information on different backup methods.

Database	Type	For more information, see..
MS SQL	External	To back up an MS SQL database used by the Foglight Management Server:
MySQL	External	To back up a MySQL database using MySQL commands:
MySQL	Internal	To back up a MySQL database using MySQL commands: or To back up an embedded MySQL database using the InnoDB Hot Backup tool:
Oracle	External	To back up an Oracle database used by the Foglight Management Server:
PostgreSQL	External	Backup and Restore

NOTE: Failing to shut down the Foglight Management Server correctly may result in errors.

Table 23. Where to find more information on different backup methods.

Database	Type	For more information, see..
MS SQL	External	To back up an MS SQL database used by the Foglight Management Server:
MySQL	External	To back up a MySQL database using MySQL commands:
MySQL	Internal	To back up a MySQL database using MySQL commands: or To back up an embedded MySQL database using the InnoDB Hot Backup tool:
Oracle	External	To back up an Oracle database used by the Foglight Management Server:
PostgreSQL	External	Backup and Restore

NOTE: The archive must include the config, cartridge, support, license, and scripts directories and all their content.

TIP: To ensure that the SQL Server remembers your password the next time you attempt to log in, select the Remember password check box.

TIP: For additional information about these settings, see your MS SQL documentation.

TIP: The Foglight database, represented by the foglight node in the Object Explorer tree, is installed on the MS SQL Server during the Foglight Management Server installation. For additional information, see the Installation and Setup Guide set.

TIP: The Backup Up Database—foglight dialog box includes two pages, each showing a different collection of settings: General and Options. By default, the General page is selected. To switch between the General and Options pages, select the appropriate page in the Select a page pane in the upper-left.

TIP: You will need this information when restoring the database from the backup file. For information on how to restore an MS SQL database, see Restoring Foglight.

IMPORTANT: For internal (embedded) MySQL databases only, continue with steps 3 and 4. For external MySQL databases, the backup is now complete.

NOTE: Foglight ships with the InnoDB Hot Backup® tool. You can use this tool to back up an embedded MySQL database as an alternative to the above procedure. For information on how to use this tool, see To back up an embedded MySQL database using the InnoDB Hot Backup tool:.

IMPORTANT: Use the back slash character ‘\’ as a directory separator on Windows platforms; on Unix platforms, use the forward slash ‘/’.

NOTE: The above example illustrates the process of backing up a MySQL database on Windows, which uses the back slash character as a directory separator. On Unix platforms, use the forward slash to separate directories.

NOTE: The above example illustrates the process of backing up a MySQL database on Windows, which uses the back slash character as a directory separator and the dir command to list files. On Unix platforms, use the forward slash to separate directories and the list -l command.

NOTE: The example below illustrates the process of backing up a MySQL database on Windows, which uses the back slash character as a directory separator. On Unix platforms, use the forward slash to separate directories.

NOTE: The code line above illustrates the process of applying logs to an uncompressed backup. If you are applying logs to a compressed backup, use the --uncompress option. For example: C:\Quest\Foglight\mysql\bin>ibbackup --apply-log --uncompress C:\Quest\Foglight\backup \config\backup.cnf For more information about the command-line options for creating compressed and uncompressed backups, see Step 4.

NOTE: The example bellow illustrates the process of backing up a MySQL database on Windows, which uses the back slash character as a directory separator and the dir command to list files. On Unix platforms, use the forward slash to separate directories and the list -l command.

“Restoring” a physical backup means reconstructing it and making it available to users. This section outlines how to restore an old Foglight installation. The process is similar for Windows and Unix systems.

NOTE: To restore a previous Foglight installation, you must have a backed up copy of that version. For information about how to back up a Foglight system, see Backing up Foglight.

Table 24. Select the procedure that matches the backed up database type you have.

Database	Type	Backed up using..	For more information, see..
MS SQL	External	MS SQL commands	To restore an MS SQL database from the database export file:
MySQL	External	MySQL commands	To restore a MySQL database from the database export file:
MySQL	Internal	MySQL commands	To restore a MySQL database from the database export file:
MySQL	Internal	InnoDB Hot Backup	To restore an embedded MySQL database previously backed up using the InnoDB tools:
Oracle	External	Oracle tools	To restore an Oracle database from the database export file:
PostgreSQL	Internal	Zip tools	To restore the previous Foglight installation directory:
PostgreSQL	Internal	Zip tools	To restore the previous Foglight installation directory:
PostgreSQL	External	PostgreSQL commands	To restore a PostgreSQL database on Windows from the database export file:
PostgreSQL	External	PostgreSQL commands	To restore a PostgreSQL database on Unix from the database export file:

TIP: To ensure that the SQL Server remembers your password the next time you attempt to log in, select the Remember password check box.

TIP: For additional information about these settings, see your MS SQL documentation.

TIP: The Foglight database, represented by the foglight node in the Object Explorer tree, is installed on the MS SQL Server during the Foglight Management Server installation. For additional information, see the Installation and Setup Guide set.

TIP: The default location and name of this file is C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup\foglight.bak.

IMPORTANT: In cases where there are multiple databases, it is important to specify which database this import is associated with by issuing the use <database> command. Failing to do so results in an error.

NOTE: The SQL file is the backup file you must create in order to restore your MySQL database (see To back up a MySQL database using MySQL commands:).

NOTE: The files oracle_drop_dp.sql and oracle_drop_db.sql are included with Foglight when you use an Oracle database, The files are located in the <Foglight_home>/scripts/sql directory.

NOTE: The dbdump file is the backup file you must create in order to restore your Oracle database (see To back up an Oracle database used by the Foglight Management Server:).

TIP: Change the pg_hba.conf file to ensure that authentication method is password, if needed. For more information about PostgreSQL connections and authentication, see Connections and Authentication.

NOTE: The database name, username, and password of the backup database and new database must be identical.

NOTE: Make sure to run Foglight and restore the database using the non-root user.

TIP: Change the pg_hba.conf file to ensure that authentication method is password, if needed. For more information about PostgreSQL connections and authentication, see Connections and Authentication.

NOTE: The database name, username, and password of the backup database and new database must be identical.

NOTE: To restore a previous Foglight installation, you must have a backed up copy of that version. For information about how to back up a Foglight system, see Backing up Foglight.

The previous Foglight installation is now restored.

In some cases it may be required to move the Foglight Management Server to different hardware. This may result in a change to the Management Server host name, IP address, or both, while the database may or may not move.

If the host name changes, you must obtain a new Foglight license.To receive a new license, send an email to license@quest.com with your contact and site ID information, along with an explanation of why you need a license. Changing only the IP address, while the host name remains the same, does not require a license update.

If the host name changes, you must also update the CATALYST_URL registry variable. This registry variable contains the Management Server host name and port, which are used to build the alarm URLs sent in email message alerts. For more information about email settings, see Explore the Mail (Global Settings) view.

This sectiontopic describes the process of moving the Foglight Management Server to a different computer.

If you have other configuration changes in your environment that are related to this change, you may need to perform additional configuration steps. Those changes can include:

For more information on how to implement these configuration changes, visit the Support Portal at https://support.quest.com/.