EMC Smarts Network Configuration Manager

Support Matrix EMC Smarts Network Configuration Manager Support Matrix Version 9.4 302-001-507 REV 01 January, 2015

Copyright 2015 EMC Corporation. All Rights Reserved. Published January, 2015 EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. 2

Table of Contents Revision history... 4 Purpose... 4 Audience... 4 System requirements... 4 Prerequisites... 4 Clients... 5 Bandwidth... 5 Combination, Application, Device, and Database server requirements... 5 Supported virtual hardware... 7 RSA Token server hardware requirements for Windows... 7 Network Configuration Manager Environment sizing... 8 Basic disk partitioning (Linux)... 9 Advanced disk partitioning... 10 Compatibility... 11 Interoperability... 11 Software requirements for Windows... 12 Software prerequisites... 12 Configuration requirements... 12 Software installed with Network Configuration Manager... 12 Software requirements for Linux... 14 Configuration requirements... 16 /etc/hosts... 16 /etc/resolv.conf... 16 Software installed with Network Configuration Manager... 16 Software requirements for NCM 9.4 Advisors... 17 Software prerequisites... 17 Software requirements for NCM Smarts Integration Adapters... 19 Software prerequisites... Error! Bookmark not defined. System and platform requirements... 19 Supported web browsers... Error! Bookmark not defined. 3

Revision history Date Revision Comment January, 2015 01 GA release Purpose This document describes the prerequisites for Network Configuration Manager on Windows and Linux platforms. Audience This document is part of the EMC Smarts Network Configuration Manager documentation set, and the information and procedures contained within this document are intended for individuals responsible for installing and deploying EMC Smarts Network Configuration Manager. Readers of this document should be familiar with: Red Hat Enterprise Linux and CentOS Linux operating systems Database architecture and concepts Security management Internet protocols, including https, TCP/IP, File Transfer Protocol (FTP), and Telnet Lightweight Directory Access Protocol (LDAP) and directory services Authentication and authorization System requirements Prerequisites The prerequisites for Network Configuration Manager: Email address where the job notifications will be sent from License keys for Network Configuration Manager Any Root CA Certificates to be used Fully Qualified Domain Name (FQDN) or IP Address for the outbound SMTP mail server Application server IP Address 4

OS Support Check the DNS and ensure www.springframework.org is reachable from AS and RA hosts. For hosts which cannot resolve this URL, fetch the IP address of www.springframework.org from any host that can resolve. Add the IP address entry for www.springframework.org in the /etc/hosts file. Database server IP Address EMC M&R (Watch4net) server IP Address Report Server FQDN or IP Address (for upgrade only) These are Operating Systems supported for NCM Core servers (AS, DS, DB), Advisors and Smarts Integration Adapter. OS Version Red Hat Linux 5.8 or later, 6.2, 6.3, 6,4, 6,5 and 7 Cent OS 6.4, 6.5 and 7 Windows 2012 2012 R2 Bandwidth Linux Windows Device pull Device push 150 KB 150 KB 300 KB 300 KB Combination, Application, Device, and Database server requirements The hardware requirements for Network Configuration Manager. Platform CPU Speed / CPU Model / No. of CPUs RAM Disk technology /size Disk configuration Minimum DB spindles Combination server Microsoft Windows Server 2012 R2, Linux 5.8 or later, 6.x and 7 2.67 GHz / x86_64 dual core / 4 16 GB SAS/ 1.5TB Minimum 300 GB. Maximize spindles. Use small, fast drives whenever possible. Dedicate RAID5 partition for [Product Directory] 3 5

Application server (small) Microsoft Windows Server 2012 R2, Linux 5.8 or later, 6.x and 7 2.67 GHz / x86_64 dual core / 4 16 GB SAS/ 1.5TB Minimum 300 GB (Linux) and 500GB (Windows). Maximize spindles. Use small, fast drives whenever possible. Dedicate RAID5 partition for [Product Directory] 6 Application server (large) Microsoft Windows Server 2012 R2, Linux 5.8 or later, 6.x and 7 2.67 GHz / x86_64 dual core / 4 32 GB SAS/ 1.5TB Minimum 300 GB (Linux) and 500GB (Windows). Maximize spindles. Use small, fast drives whenever possible. Dedicate RAID5 partition for [Product Directory] 6 Database server (small) Linux 5.8 or later, 6.x and 7 2.67 GHz / x86_64 dual core / 4 8 GB SAS/ 1.5TB Minimum 300 GB. Maximize spindles. Use small, fast drives whenever possible. Dedicate RAID1 partition for [Product Directory] 6 Database server (large) Linux 5.8 or later, 6.x and 7 2.67 GHz / x86_64 dual core / 4 16 GB SAS/ 1.5TB Minimum 300 GB. Maximize spindles. Use small, fast drives whenever possible. Dedicate RAID1 partition for [Product Directory] 6 Device server Microsoft Windows Server 2012 R2 Linux 5.8 or later, 6.x and 7 2.67 GHz / x86_64 dual core / 4 8 GB SAS/ 1.5TB Minimum 140 GB. Maximize spindles. Use small, fast drives whenever possible. Dedicate RAID1 partition for [Product Directory] 6 Report Advisor server Microsoft Windows Server 2012 R2, Linux 5.8 or later, 6.x and 7 2.67 GHz / x86_64 dual core / 4 16 GB SAS/ 1.5TB Minimum 300 GB (Linux) and 500GB (Windows). Maximize spindles. Use small, fast drives whenever possible. Dedicate 6 6

RAID5 partition for [Product Directory] Disk technology or size is the total disk size required (DAS), including Operating System, Network Configuration Manager application and database install requirements such as, swap and temp space. Disk configuration is the disk capacity required for the Network Configuration Manager database (not the application) formatted capacity Supported virtual hardware The supported virtual hardware for Network Configuration Manager. Support for virtualized deployments may vary per hypervisor due to the nature of integration between OS and hypervisor. VMWare: best practices are offered on VMWare hypervisors for the above operating systems on VMware ESX 5.1. All other hypervisors: SAS may be deployed on other hypervisors but EMC does not support performance and interoperability issues between the OS layer and hypervisor. We do not have best practices for deploying on non-vmware hypervisors. Check with hypervisor vendor to address issues not reproducible on physical or VMWare deployed environments. RSA Token server hardware requirements for Windows The RSA Token Server hardware requirements for Network Configuration Manager: CPU Model RAM Disk Technology / Size Disk configuration Token server 2.67 GHz, x86_64 dual core 2 GB SAS / 1.5TB Minimum 100 GB. Maximize spindles. Use small, fast drives whenever possible. Dedicate RAID5 partition for [Product Directory]. 7

NCM Clients Requirements Component Linux Windows Mac OS Version RHEL 5.8 or later, RHEL 6.x, 7 Windows 7, 8 and Win2k12 server Mavericks 10.9.x CentOS 6.4, 6.5 and 7 Processor 2 GHz 2 GHz + 2GHz+ Memory 2 GB 2 GB 2GB Storage 200 MB on disk 200 MB on disk 200 MB on disk Client Download Size 30 MB on disk 30 MB on disk 30 MB on disk Browser Versions Firefox 32 or later Microsoft Internet Explorer 10.0, 11.0 Safari 5.1.7 or later Firefox 32 or later Chrome 37 or later Safari 5.1.7 or later SSH Client SSH version 2 SSH version 2 SSH version 2 Java SE Development Kit Java 1.8.0_25 or later Java 1.8.0_25 or later Java 1.8.0_25 or later If an error appears when bringing up the GUI with NFS mounted, the NFS parameter file in /etc/default/nfs has to be modified by changing the maximum number of concurrent NFS requests to the last numeric argument on nfsd command line. For example: NFSD_SERVERS=512. The maximum number of concurrent lockd requests should be set to 128. For example: LOCKD_SERVERS=128. 8

Network Configuration Manager Environment sizing The type and number of servers needed to run Network Configuration Manager based on the number of devices. Combinati on server Application server Database server Report server (optional) Device server Up to 500 devices 1 N/A N/A N/A N/A Up to 5K devices N/A 1 Small N/A 1 1+ Up to 10K devices N/A 1 Large 1 Small 1 2+ Up to 25K devices N/A 1 Large 1 Large 1 5+ 25K+ devices Custom Architecture Quote Required The maximum number of Device servers per Application server is 40. Network Configuration Manager 9.4 can support up to 50,000 devices in a single deployment. To increase performance of Network Configuration Manager Environments with a high number of device changes, it is advisable to setup Network Configuration Manager using a larger sizing setup than is required. For example, if a large number of device changes will occur on a 500 device environment, use the 5K device sizing requirements when you setup your Network Configuration Manager environment. Refer to Sizing_Sheet_for_NCM_9.4 available at https://support.emc.com/ for further recommendations - EMC Network Configuration Manager Version 9.4 Performance Benchmarking and Sizing Guidelines Basic disk partitioning (Linux) The following information is provided as a recommendation for your Network Configuration Manager server disk partitioning scheme. This example assumes that you are installing the product on the /opt partition. If you are installing on a different partition, refer to the /opt partition size requirements when sizing that partition. 9

Mount point File system Size Linux Linux Linux /boot ext3 100 MB - <swap> 1 /var ext3 16000 MB / ext3 10000 MB /tmp ext3 4000 MB /opt ext3 40000-200000 MB 2 /usr ext3 4000 MB Advanced disk partitioning In large Network Configuration Manager configurations, you may receive performance benefits from placing the database on its own dedicated disks. The database is located under [Product directory]/db. For example, if you have 6 disks in the system, you could allocate 2 disks in RAID1 for the OS and application and allocate 4 disks in RAID5 for the database. If you have 10 disks or more, you may also separate the database and the database transaction log so that they reside on their own dedicated disks. The database transaction log is located under [Product directory]/db/controldb/data/pg_xlog. For example, if you have 10 disks in the system, you could allocate 2 disks in RAID1 for the OS and application, 6 disks in RAID5 for the database, and 2 disks in RAID1 for the database transaction log. 1 The swap value should equal two times the physical RAM for up to 2 gigabytes (GB) of physical RAM, and then one times the physical RAM for any amount above 2GB. For example, a system with 2GB of physical RAM would have 4GB of swap, while a system with 3GB of physical RAM would have 5GB of swap. 2 The /opt partition is used to store the Network Configuration Manager application data as well as 8 data backups. Large installations may need as much as 200 GB of disk space depending on the amount of historic information retained in the database. 10

NCM Compatibility Upgrading to Network Configuration Manager 9.4 will make previous versions of Advisors and Adapters inoperable until a compatible release is installed. The compatible versions for Network Configuration Manager 9.4: Smarts Integration Adapters 9.4 Advisors 9.4 (Report and Compliance) Network Configuration Manager Integration Modules After upgrading to Network Configuration Manager 9.4, the email, flat-file and integration modules are automatically installed. But the customizations to these module settings have to be re-done. SA Suite Interoperability NCM version 9.4 is part of Service Assurance Suite 9.4.0.0. The suite components interoperate as described here: Product Version SAM 9.3 9.2.X.X 9.1 IP(including TSM) 9.3 9.2.X.X 9.1 EMC M&R 6.4.x (If EMC M&R and SolutionPack for EMC Smarts are used to manage notifications, you must use SAM 9.4 with Notification Cache. 6.5.1 provides the latest version of the SolutionPack for Network Configuration Manager. 11

Software requirements for Windows Software prerequisites Do not install Network Configuration Manager on a Windows Domain Controller. The following software must be installed prior to installing Network Configuration Manager and prior to running the prerequisite check for all Combination, Application, and Device Servers. Strawberry-perl-5.12.3.0 32-bit: Visit the Strawberry Perl website to download a copy of Strawberry-perl- 5.12.3.0 32-bit. After installing Strawberry Perl for the first time, you must logout and then re-login so that the system PATH variable modification can take effect. Configuration requirements Network Configuration Manager requires a minimum page file size of 2000 MB for all server types. Ensure that when you use ping -a <IP address> command in the console, it returns the FQDN. This is essential for Network Configuration Manager Application communication with remote servers. Software installed with Network Configuration Manager The following software is installed automatically with Network Configuration Manager for all Combination and Application servers. PostgreSQL 9.0.18 64 bit The following softwares are installed automatically with Network Configuration Manager for all Combination, Application, Device, and Report Servers. Apache HTTP Server 2.2 o Apache HTTP Server 2.2 is included with the Network Configuration Manager distribution. o Network Configuration Manager will automatically install httpd-2.2.22- win32-x86-openssl-0.9.8t.msi. It is recommended to setup Apache as a service on Port 80, and select the Typical setup type when installing Apache HTTP Server 2.2. Apache Tomcat 8.0.11 12

o Network Configuration Manager will automatically install apachetomcat-8.0.11.exe. It is recommended to set the Connector Port to 8080, and select either the Minimal or Normal setup type when installing Tomcat 8.0.11. Username and password fields are optional. It is recommended to use a directory path that does not contain spaces (for example, C:\Tomcat8) when installing Tomcat 8.0.11 on Windows. Do not manually install Tomcat 8.0.11 prior to installing Advisors. This causes errors during installation. The following software is installed automatically with Network Configuration Manager for all Combination, Application, Device, Report, and Remote Database servers. Java SE Development Kit 8, 64-bit o Network Configuration Manager will automatically install jdk-8u25- windows-x64.exe if it is not already present in the system. Enable the Java plugins in your browser before you launch the user interface. The following software are part of Network Configuration Manager distribution and installed automatically with Network Configuration Manager for all Combination, Application, Device, Report, and Remote Database servers.. Microsoft Visual C++ Runtime Libraries vcredist_x86.exe,vcredist_x86_2008.exe, vcredist_x64.exe, vcredist_x64_2008.exe and vcredist_x64_mfc.exe Microsoft Visual C++ packages: o Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) o Microsoft Visual C++ 2005 SP1 Redistributable Package MFC Security Update o Microsoft Visual C++ 2008 Redistributable Package (x64) o Microsoft Visual C++ 2008 SP1 Redistributable Package (x64) OpenSSL v0.9.8zc Win32OpenSSL-0_9_8zc.exe It is recommended to accept the default directory (C:\OpenSSL) when installing OpenSSL on Windows. If a directory whose path contains spaces is used, the creation of the certificates will fail. When the install.pl script is run to install OpenSSL for Windows, the following warning message appears: The Win32 OpenSSL Installation Project setup has detected that a Command Prompt is currently running. Win32 OpenSSL will not work properly from already opened Command Prompts. It is highly recommended that you close all open Command Prompts before clicking Ok 13

to continue. It is safe to click Ok when this message is displayed. Do not close the Network Configuration Manager installation window. For details about upgrading OpenSSL on Windows, see the EMC Smarts Network Configuration Manager Security Configuration Guide. All these above mentioned packages are shipped with the Network Configuration Manager Installation bundle Software requirements for Linux Accept the default configuration when installing each prerequisite. Red Hat Enterprise Linux maintains bug fixes and distributes them continuously through their subscription service. Knowledge of current Redhat updates is essential. Version Architecture Group (if applicable) Package Software RHEL 5 RHEL /Cent OS 6 RHEL/ CentO S 7 RHEL 5 RHEL/C entos 6 RHEL/Ce ntos 7 RHEL 5 RHEL/Cent OS 6 RHEL/C entos 7 httpd 2.2 2.2 2.4.6 x86_64 x86_64 x86_64 Web Server Web Server Web Server mod_ssl 2.2 2.2 2.4.6 x86_64 x86_64 x86_64 Web Server tftp-server 5.2 x86_64 x86_64 x86_64 Legacy Network Server Web Server Legacy Network Server Web Server Legacy Networ k Server perl 5.8.8 5.10. 1 5.16.3 x86_64 x86_64 x86_64 14

sendmail x86_64 x86_64 x86_64 Mail Server Mail Server Mail Server wget 1.10. 2 1.12-1 1.1.4 x86_64 x86_64 x86_64 Base Base Base compat- libstdc++- 33 x86_64 x86_64 x86_64 libtermcap 2.0.8 2.0.8 2.0.8 x86_64 x86_64 x86_64 glibc 2.5 2.12 2.17 x86_64 and i686 x86_64 and i686 x86_64 and i686 audit-libs x86_64 x86_64 x86_64 krb5-libs 1.6 1.9 1.11 x86_64 x86_64 x86_64 e2fsprogs 1.39 1.41 1.42 x86_64 x86_64 x86_64 pam 1.1.8 x86_64 x86_64 x86_64 perl-dbd- Pg 2.19 x86_64 x86_64 x86_64 perl-dbi 1.6.27 x86_64 x86_64 x86_64 postgresqllibs x86_64 x86_64 x86_64 xinetd x86_64 x86_64 x86_64 telnet client x86_64 x86_64 x86_64 sysklogd 1.4.1 x86_64 rsyslog 4.6.2 7.4.7 x86_64 x86_64 15

openssl 0.9.8 1.0.0 1.0.1e x86_64, x86_64 x86_64 distcache x86_64 To list the architecture of an.rpm file, use the following command, where [RPM] is the name of the rpm, and is optional. rpm -q -a --queryformat='%{n}-%{v}-%{r}.%{arch}\n' [RPM] Configuration requirements /etc/hosts The Network Configuration Manager requires a valid FQDN entry in the /etc/hosts and /etc/sysconfig/network files for all server types. For example: 127.0.0.1 localhost 192.168.1.100 myserver.mydomain.com myserver /etc/resolv.conf The Network Configuration Manager requires a valid DNS server entry in the /etc/resolv.conf file. For example: domain (your own domain name) nameserver (your own DNS server IP Address) search (your own domain name) Ensure that when you use hostname command in the console, it returns the FQDN. This is essential for communication of the Network Configuration Manager application communication with other remote servers. Software installed with Network Configuration Manager The following software is installed automatically with Network Configuration Manager for all Combination and Application servers. PostgreSQL 9.0.18 64 bit The following softwares are installed automatically with Network Configuration Manager for all Combination, Application, Device, and Report Servers. Apache HTTP Server 2.2 Apache HTTP Server 2.2 is included with the Network Configuration Manager distribution. Apache Tomcat 8.0.11 16

Network Configuration Manager will automatically install apache-tomcat- 8.0.11.zip. The following software is installed automatically with Network Configuration Manager for all Combination, Application, Device, Report, and Remote Database servers. Java SE Development Kit 8, 64-bit Network Configuration Manager will automatically install jdk-8u25-linuxx64.rpm. Enable the Java plugins in your browser before you launch the user interface. NCM 9.4 Advisors Requirements Advisors specific software prerequisites The EMC Smarts Network Configuration Manager Integration Adapter for Smarts Manager requires the following prerequisites: perl-dbd-pg must be installed on Red Hat Enterprise Linux stand-alone remote advisors server prior to installing advisors. PostgreSQL This section does not apply if you are installing Advisors on the same server where Application server is installed. By default, PostgreSQL only allows connection from 127.0.0.1, and only listens on the 127.0.0.1 address. If you initially setup the Network Configuration Manager to use a local Report Server, or you are installing Advisors as a remote server, PostgreSQL must be changed to allow connections from the remote server before installing Advisors. To change this setting in PostgreSQL, complete the following steps. Step Task 1 Log onto the server where PostgreSQL is running, as a user with administrator privileges. 2 Change directories to the Postgres data directory. By default this directory is [Product directory]/db/controldb/data 3 Open the postgresql.conf file for editing. 4 Locate the line in the postgresql.conf file beginning with listen_addresses =. Modify the value to the right of the equal sign, so it now reads 127.0.0.1, <Server IP>, where <Server IP> is the IP 17

address of the server running Postgres. For example, listen_addresses = 127.0.0.1, 172.17.0.174. This setting tells Postgres to listen on the local loopback (127.0.0.1), as well as on one of the public interfaces, where clients will connect. If the line has previously been commented out, remove the number sign (#) to uncomment the line. 5 Save, and exit the postgresql.conf file. 6 Open the pg_hba.conf file for editing. 7 Add the following line at the end of the file. host all all < IP address>/32 md5 8 Replace < IP address> with the IP address of the report server attempting to connect to the Postgres server. 9 Save, and exit the pg_hba.conf file. 10 Restart the PostgreSQL service. Use the service controldb restart command. 11 Restart the ncm-as service. Use the service ncm-as restart command. 12 Open the [Product directory]/ui/html/index.html file for editing. 13 Locate the line <a href="https://<server IP>/web">launch Network Configuration Manager Report advisor</a>, where <Server IP> is the IP address of the server running Postgres. Replace <Server IP> with the IP address of the new Report advisor server. For example, <a href="https://10.6.230.165/web">launch Network Configuration Manager Report advisor</a>. 14 Save, and exit the [Product directory]/ui/html/index.html file. 15 Open the [Product directory]/ui/html/powerup.jnlp file for editing. 16 Locate the line <property name="reports_advisor_url" value="https://<server IP>/web/"/>, where <Server IP> is an IP address or hostname. Replace <Server IP> with the IP address of the new Report advisor server. For example, <property name="reports_advisor_url" value="https://10.6.230.165/web/"/>. 17 Save, and exit the [Product directory]/ui/html/powerup.jnlp file 18

At setup, the Report server registers itself with the Application Server. Before installing the Report Server, ensure that the Application or Combination servers have the same data and time as the candidate Report advisor server. If not, the Report advisor server cannot communicate with the Application server. NCM Smarts Integration Adapter 9.4 requirements The Network Configuration Manager Integration Adapter for Smarts Manager requires the following software: EMC Smarts Network Configuration Manager 9.4 You must have EMC Smarts Network Configuration Manager 9.4 Application Server or Combination Server installed before installing the EMC Smarts Network Configuration Manager Integration Adapter for Smarts Manager. The EMC Smarts Integration Adapter has to be installed on the AS or CS host. 19