Host access requirements
This section lists the access requirements for host resource data collection. You will use this information to populate the configurations used by the Host Discovery, Validation, and Collection processes.
User ID & Password Credentials: Root-level, read-only access is required for host data collection.
See Manage credentials.
Access Control: For security reasons, most enterprise environments mandate access control where a new non-root account is created, with temporarily elevated access to the required commands provided via an access control command, such as sudo. Otherwise, the root user is required for host access.
Files containing sudo commands per operating system can be found on the Portal server in: /opt/aptare/updates. These filenames contain both the OS and the version of the sudo commands file so that you can identify the files that contain the latest updates; for example: hpux_9.1.01, aix_9.1.01, linux_9.1.01, solaris_9.1.01.
Path: The system must have knowledge of the correct paths to access commands. An overview of the requirements is listed here, with the details for determining paths provided in Command Path Verification.
See Command path verification.
For Windows hosts, a path is required for fcinfo, hbacmd, and scli commands. For Linux hosts, if the Data Collector is installed on a Windows server, use plink.exe to determine the path; if the Data Collector is installed on a Linux server, determine the path by executing ssh.
It is critical for the Data Collector to probe the HBA in order to establish a host's relationship with storage. Without the HBA information, all storage for a host will be listed as local storage. An internal probing mechanism is used to gather Host Bus Adapter (HBA) data from Windows hosts.
: Either hbaverify, scli, hbacmd (required for both LUN Mapping and HBA data collection), or fcinfo.
: scli or hbacmd (required only for HBA information)
: scli or hbacmd (required only for HBA information)