Finding and interpreting configuration changes

This information can be used to find and interpret configuration changes by using the Fast Fabric Health Check tool.

Configuration changes are best found by using the Fast Fabric Health Check tool. For more information, see Health checking.

Note: If you have multiple primary fabric management servers, you must run the health check on each primary server, because Fast Fabric can only access subnets to which its server is attached. You might consider using the Cluster Systems Management/Management Server (CSM/MS) to remotely process this function on all primary fabric management servers.

At the end of the installation process, a baseline health check should be taken to have a comparison of the current configuration with a known good configuration. For more information, see Reestablishing a health check baseline. Comparison results reveal configuration changes.

After performing a current health check by using the all_analysis command, go to the analysis directory at /var/opt/iba/analysis/latest, and look for files ending in .diff. To determine what information is contained within each file, use the Fast Fabric Toolset Users Guide. This information helps you to determine what has changed.

If nothing has changed, you need to change back to the original configuration.

If the configuration changes are valid, take a new baseline by reestablishing a health check baseline.