Plan Host Data Collection
Prior to configuring APTARE StorageConsole to discover your host inventory, you must identify the hosts for which you will be collecting data. Because each enterprise has a unique inventory of hosts with specific access requirements and restrictions, the process of ensuring successful host data collection requires an assessment of the hosts in your environment and several configuration steps.
Host Resources Prerequisites and Configurations
To gather data from hosts, the following privileges are required.
Sudo Commands for Host Resources Collection
If you are using sudo to elevate access to root privileges, update the sudoers file:
• Sudoers file: /etc/sudoers
• Use the lists of the sudo commands (per OS) that are located on the Portal server in:
<Home>/opt/aptare/updates
• Comment out this line in the sudoers file: Defaults requiretty
Access Requirements by OS
Table 12.1 Host Resources Prerequisites by Operating System
Host OS | Host Access Requirements | Port Requirements | Notes |
Linux RH Linux SUSE CentOS AIX HP-UX Solaris | ssh or telnet must be enabled Some commands may require an account with super-user root privileges. sudo, sesudo, and pbrun are supported; ensure the user ID has required sudo, sesudo, or pbrun privileges. | ssh: 22 telnet: 23 | Collection uses ssh/telnet to execute commands. OS and application commands require root privileges for HBA API access. The sysstat utility must be installed on Linux servers or storage nodes for Linux host performance data collection. |
Windows | A WMI Proxy is required to collect from Windows hosts. All Windows hosts require a user ID with Administrator privileges for WMI. | RPC: TCP Port 135 for WMI DCOM: TCP/UDP 1024-65535 TCP/IP 1248, if WMI Proxy server is not the same as the Data Collector server | When the Data Collector Policy is configured to include file-level data, the Data Collector and WMI need to use a Windows Domain Administrator ID. |
WMI Proxy Requirements for Windows Host Data Collection
A WMI Proxy server is required for collecting data from Windows hosts.
• WMI uses DCOM for networking. DCOM dynamically allocates port numbers for clients. DCOM’s service runs on port 135 (a static port) and any client communicating with a host connects on this port. The DCOM service allocates the specific port for the WMI service. To set up a fixed port for WMI, see http://msdn.microsoft.com/en-us/library/bb219447%28VS.85%29.aspx.
• When installing the WMI Proxy, if the installer detects that Microsoft .NET is not already installed, it notes this dependency and then installs .NET for you. Microsoft .NET contains several necessary libraries.
• .NET Framework 4 is installed by default with Windows Server 2012. You must explicitly install .NET Framework 3.5 to support the WMI Proxy Service installation. You do not need to uninstall .NET Framework 4.
Table 12.2 Host Resources Prerequisites by Operating System
Data Collector Server OS | WMI Proxy Requirements | Notes |
Windows | WMI Proxy will be installed on the Data Collector server by default | |
Red Hat Linux SUSE CentOS | Identify a Windows machine on which to install the WMI Proxy | Note the IP address of the server on which the WMI Proxy resides, as you will use it during the Portal configuration process. |