Let's expand that analysis to verifying that those HBA's also have a certain driver version and a certain firmware level, as shown in the following example profile:

any profile name

the 'OS' field = Solaris the 'Model' field = LP-9000

the 'DriverVersion' field = whatever the 'FirmwareVersion' field = whatever

IMPORTANT: The use of special characters in the field values are interpreted as regular expressions (or wildcards) by the search. For example, "Model LP900[02]" will match the values "LP-9000" or "LP-9002". "FirmwareVersion 3.90A[0-9]" will match any firmware version 3.90A0 through 3.90A9.

3.Once you have your profiles configured, run HBA Risk Analysis or Switch Risk Analysis. The tool compares every HBA or switch against the profiles and flags any HBA or switch that does not match at least one profile.

Global Change Management

Global Change Management lets you save the current configuration and/or compare changes with a previous configuration.

Accessing Global Change Management

1.Access Business Tools.

2.Click Global Change Management Tools.

Saving the Current Configuration

To save the current configuration, use option 0. The current configuration is saved to a DAT file in the following directory. This file can be opened by using a text editor, such as Notepad:

%JBOSS4_DIST%\server\appiq\remotescripts\advisors\saved-configurations

The DAT file contains the data for the elements discovered in the configuration. The following is an example of a portion of a DAT file for a saved configuration:

$VAR1 = 'conf3';

$VAR2 = 1117783473; __DATA__

$VAR1 = { '1002' => { 'PROPERTIES' => {

'ID' => '1002', 'HostType' => 'Default', 'DnsName' => 'QA67', 'SupportFlags' => '7',

....

where

•$VAR1 is the configuration name, which is conf3 in this case.

678 Business Tools