Configuring the discovery profile

The Host storage sensor, is not enabled by default. To enable the sensor, you must create a discovery profile and then enable the sensor from the new profile.

The collection engine uses the HBA (host bus adapter) API to discover the HBAs and FC volumes that are configured on the host system. For a successful discovery, the vendor's HBA API library must be installed and configured correctly on the host system.

The following attributes can be modified:

deployCollectionEngineWindows

The default value for the deployCollectionEngineWindows attribute is true. The sensor copies the collection engine file to a location on the Windows target host system. After the discovery is complete, the collection engine file is deleted from the host. The location is entered in the collectionEngineWindowsPath attribute. If no path is specified on Windows systems, the collection engine file is copied to the TEMP directory.

If the value is false, the collection engine file is not copied.

collectionEnginePath

There is no default value for the collectionEnginePath attribute. Enter the absolute path to the UNIX collection engine directory, if required.

collectionEngineWindowsPath

There is no default value for the collectionEngineWindowsPath attribute. Enter the absolute path to the Windows collection engine directory, if required.

Entering the Windows path when the directory is on a network drive (created by using the net use command), might not work. Instead, enter the Windows path by using the UNC (Universal Naming Convention) method. For example, \\hostname\share\CollectionEngine.

collectionEngineSudoCommand

There is no default value for the collectionEngineSudoCommand attribute. Enter the command to use for privilege escalation on UNIX systems.

collectionEngineTimeout

The default value for the collectionEngineTimeout attribute is 30. This value specifies the time interval in minutes before a timeout occurs during a discovery.

collectionEngineForceUniqueName

The default value for the collectionEngineForceUniqueName attribute is false. If the value is false, the collection engine is not renamed when the collection engine is copied to the target system. If the value is true, a time stamp is added to the name of the collection engine before it is copied to the target system.

If you want to use sudo to give the discovery user permission to run the collection engine, then the collection engine name cannot be changed. In this case, the default value of false must be used.

In environments that use concurrent discovery, if multiple discoveries are run at the same time, against the same target systems, collisions can occur when deploying the collection engine. In situations like this, the collectionEngineForceUniqueName attribute can be set to true to force the name of the collection engine to be unique on the target system. If this attribute is set to true, sudo cannot be used.

If the Host storage sensor is enabled, do not enable the Storage sensor. If both sensors are enabled, some of the storages resources are discovered twice.