Capacity Manager Configurations > Host Resources Prerequisites and Configurations
  
Version 10.3.00P13
Host Resources Prerequisites and Configurations
To gather data from hosts, the following privileges are required.
Host Access Privileges, Sudo Commands, Ports, and WMI Proxy Requirements
WMI Proxy Requirements for Windows Host Data Collection
Host Resources Supported Configurations
Supported Host Bus Adapters (HBAs)
Host Access Privileges, Sudo Commands, Ports, and WMI Proxy Requirements
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 2 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..
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.
 
Host Resources Supported Configurations
You can configure Capacity Manager to collect the following Host Resources data:
Table 3 Host Resources Supported Configurations
Host Resource
Supported Configurations/Versions
Port
Prerequisites and Notes
Applications
SQL: Microsoft SQL Server 2005 and SQL Server 2008
1433
The Data Collector requires a user account with permissions to execute the procedures: sp_helpdb and sp_spaceused.
Local authentication only is supported at this time.
 
Exchange: Microsoft Exchange Server 2003, 2007, 2010
389
The user name must have privileges to search under the DN within the Active Directory. Typically, this is an Administrator.
Microsoft Exchange 2003: WMI used for data collection.
Microsoft Exchange 2007 and 2010: Data collection requires PowerShell remoting to be enabled on the Exchange server. The Data Collector connects to PowerShell via the WMI Proxy to execute PowerShell commands. For details on remoting, see the Microsoft Administrator’s Guide to Windows PowerShell Remoting.
 
Oracle: Oracle 11g, Oracle 12c
1521
Oracle user must have SELECT_CATALOG_ROLE role granted
 
Oracle ASM: Oracle ASM, v10gR1, 10gR2, 11gR1, 11gR2, 12c
1521
Oracle ASM requires a user with SYSASM (Oracle-supported only for 11g and above) or SYSDBA privileges
Containers
Oracle Containers
 
Sometimes referred to as Solaris Zones.
Clustering
Clustering technologies, both active-active and active-passive
 
Clusters are listed as Related Hosts in reports. This relationship is established when multiple servers are accessing the same storage.
File Systems
• Solaris ZFS; Solaris Volume Manager (SVM) Metastat
• AIX 5.2, 5.3 JFS and JFS2, with correlation to SAN disks
• SUSE SLES 9, 10; 32 & 64 bit REISER FS & EXT3 & Logical Volume Manager (LVM & LVM2)
• VxFS on all supported Operating Systems
• Windows NTFS
• Oracle ASM
• Linux ext4 file systems
 
 
Multi-pathing
• EMC PowerPath
• Hitachi Dynamic Link Manager (HDLM)
• VERITAS Dynamic Multi-Pathing (VxDMP)
• Device Mapper Multipath for Linux
• Microsoft MPIO - Windows 2003, 2008 (R2), Windows 2012 (R2) drivers
 
 
 
 
 
If using a non-supported MPIO driver, storage capacity may be double-counted in capacity reports.
Operating Systems
• Red Hat Linux Enterprise Server 5 and 6
• Solaris 8, 9, 10 (SPARC ONLY), x86
• Windows 2003; Windows 2008 Server; Windows 2012 Server.
• IBM AIX
• HP-UX
• SUSE
 
In general, APTARE supports these operating systems up to and including the latest OS patch level.
Volume Managers
• Veritas Volume Manager 5.0 and 5.1 (Supported OS: RedHat Linux, Solaris, AIX, HP-UX, Windows)
• Solaris Volume Manager
• Linux Logical Volume Manager
• AIX Logical Volume Manager
• HP-UX Logical Volume Manager
 
Besides Veritas Volume Manager, each of the operating systems comes with its own built-in logical volume manager, so no specific version numbers are mentioned
Supported Host Bus Adapters (HBAs)
Table 4 Host Bus Adapters: Supported Configurations
HBA OS
Supported Configurations/Versions
Prerequisites
Windows
HBA information is obtained using OS commands, looking for specific operating system files and directories. Product-specific commands (Emulex and QLogic) are also used.
An internal probing mechanism is used to gather HBA data.
AIX & HP-UX
HBA information is obtained using OS commands. No product-specific commands are used; therefore, Capacity Manager supports all HBAs supported by these operating systems.
fcmsutil (used only for HP-UX HBA information; should already be installed by default)
Linux
HBA information is obtained using OS commands, looking for specific operating system files and directories. Product-specific commands (Emulex and QLogic) are also used.
scli or hbacmd (required only for HBA information)
Solaris
HBA information is obtained using OS commands such as luxadm. Product-specific commands (Emulex and QLogic) are also used.
scli or hbacmd (required only for HBA information)