Entuity Network Monitoring and Analytics 10.5 Server Sizing Guide

Entuity Network Monitoring and Analytics 10.5 Server Sizing Guide

Table of Contents 1 Introduction 3 2 Server Performance 3 2.1 Choosing a Server... 3 2.2 Supported Server Operating Systems for ENMA 10.5... 3 2.3 Server Performance Relationship... 4 2.4 x86-64 Processor Server Specification... 5 2.5 Additional Server Configuration... 5 3 ENMA Server Roles 6 3.1 Central License Server... 6 3.2 Consolidation Server... 6 3.3 Polling Server... 6 3.4 Integrated Flow Analyzer (IFA) Collector Server... 6 3.5 Notes... 6 3.5.1 Objects... 6 3.5.2 Ping Only Devices... 7 3.5.3 Virtual Server Configurations... 7 3.5.4 Hard Disk... 7

1 Introduction The purpose of this document is to outline how to specify servers for your ENMA installation. The chart and tables included in the document allow you to select a suitable server configuration based on loading factors and server type. 2 Server Performance 2.1 Choosing a Server Follow these steps in order to size your server: 1. Choose an Operating System. 2. Choose the designation of the server. See Section 3 - ENMA Server Roles: a. Central License Server b. Consolidation Server c. Polling Server d. Flow Collection Server 3. Estimate how many devices and objects will be managed by the server. 4. Plot these figures on the chart below. This will give you a band minimum, normal or maximum. 5. Reference the table for the Operating System you have chosen and look up the band in order to find the minimum specification for the server you need. 2.2 Supported Server Operating Systems for ENMA 10.5 x86-64 Processor a. Microsoft Windows 2008 SP2 (64 bit only) b. Microsoft Windows 2008 R2 (64 bit only) c. Red Hat Enterprise Linux Server release 6.x d. Oracle Enterprise Linux Server release 6.x

2.3 Server Performance Relationship Server Sizing CPU Clock Speed: The faster the clock speed the faster single threaded operations will be processed. The time to process functions such as "WebUI page display" and "reports generation" are governed by the speed of such single threaded operations. Therefore server clock speed will most noticeably affect the responsiveness of the user interface. We recommend that the servers have a minimum clock speed of 2.5 GHz and ideally have speeds nearer 3.0 GHz. No of CPU Cores: The number of CPU cores will govern how many multi-threaded operations can take place simultaneously. ENMA's polling engine has a multi-threaded architecture and therefore its polling capacity and data throughput increase with the number of available CPU cores. The relationship between polling capacity and cores is not linear (since more cores have greater contention for shared system and application resources) and our experience is that there are only small gains to be made by increasing beyond 12 cores. Recommended minimum core numbers are detailed in the tables above. Memory: It is important that the memory requirements of ENMA's running processes can be accommodated in physical memory. System performance is severely impacted when physical memory is exhausted and process memory allocations are paged to the disk. In addition there are benefits to be gained by having extra spare memory, since this will be used by the operating system to cache disk information which can improve database performance. Recommended minimum memory sizes are detailed in the tables below. Disk Capacity: Minimum disk space requirements cover ENMA's installed software, its embedded database and storage for standard usage of scheduled reports. Disk Performance: ENMA's database relies on fast throughput of data to the storage system. We recommend that systems are configured with the fastest storage system options available. As a guide we suggest that disk rotational speeds should be no slower than 15Krpm, and Input/Output Operations Per Second (IOPS) is rated at 150 or above.

2.4 x86-64 Processor Server Specification Server Configuration Minimum Normal Maximum Minimum CPU Clock Speed 2.5 GHz 2.5 GHz 2.5 GHz Intel Processor Family (or equivalent) Xeon E3 Family Xeon 5000 Sequence Xeon E5 Family Minimum No Cores 4 6 12 Windows Minimum Physical Memory 6 GB 12 GB 24 GB Linux Minimum Physical Memory 8 GB 16 GB 32 GB Disk Capacity 60 GB 90 GB 120 GB 2.5 Additional Server Configuration The following settings can be set in <enma_home>\etc\entuity.cfg. Configure must be run once the changes have been applied. Minimum Configuration: - no additional settings required Normal Configuration: [Database] key_buffer=1024m [MibServ] workers=40 [eosserver] javamemory=1024m Maximum Configuration: For Linux [Database] key_buffer=3072m table_cache=3072 For Windows [Database] key_buffer=1024m For all operating systems [DataStream] NumStreamInstTables=4 NumSampleCaches=8! CacheStreams=100000 [MibServ] workers=60 [eyepoller]

workers=50 [eosserver] javamemory=3072m 3 ENMA Server Roles 3.1 Central License Server The Central License Server allows the customer to license all their ENMA server instances from one central point. This makes it very easy to move device licenses between servers when required. If the server's only role is to act as a Central License Server (and not to poll or receive flows) the "Minimum Server Configuration" is adequate. 3.2 Consolidation Server In a multi-server environment one ENMA server can be designated as a Consolidation Server. Users will log on to the Consolidation Server in order to gain access to the information gathered and stored by multiple Polling Servers. If the server's only role is to act as a Consolidation Server (and not to poll or receive flows) the "Minimum Server Configuration" is adequate. 3.3 Polling Server The most significant loading factors in a Polling Server are the number of devices and the number of objects (i.e. physical and virtual interfaces) to be managed. The two loading factors are related such that the maximum number of devices that can be managed without effecting performance characteristics is inversely proportional to the total number of objects. Use the chart above to identify the most suitable server configuration based on managed device and object numbers. If the server's role is to act additionally as a Central License Server, a Consolidation Server or a Flow Collector (as well as a Polling Server) it is recommended that a faster processor clock speed (closer to 3GHz) is selected. 3.4 Integrated Flow Analyzer (IFA) Collector Server The recommended server configurations accommodate use of IFA Flow Collection. If the server's only role is to act as a Flow Collector (without polling) it is applicable to identify the server configuration from the chart using a object count of zero, otherwise the server should be sized in accordance with Section 3.3. 3.5 Notes 3.5.1 Objects The following are considered objects: Physical Port Virtual Port Monitored Application

3.5.2 Ping Only Devices It is possible to manage a device as a "ping only device" by using ICMP to poll its management IP address only. In this case, such devices will not affect the SNMP polling performance, so ping only devices should not be considered when looking at the chart. Entuity estimates that it would be possible to poll as many ping only devices as fully managed devices. 3.5.3 Virtual Server Configurations The virtual machine should be configured such that the physical machine specifications recommended in the Server Configuration Table is accommodated. The virtual machine should be configured so that it has sole access to the required amount on RAM and CPU. The supported operating systems have been formally tested on the following virtualization platform versions: 1. VMware ESXi 4.1, 5.0, 5.1 (Windows and Linux) 2. VMware Workstation 7.1.6 (Windows and Linux) 3. Oracle VM Server 2.2, 3.2.3 (Windows and Linux) 4. Citrix XenCenter 6.0.2 (Windows Only) 5. Microsoft HyperV 6.1 (Windows and Linux) 3.5.4 Hard Disk A SCSI Ultra 320 or SAS disk sub system is recommended for physical servers. Experience has shown that it is extremely advantageous to separate disk I/O generated by memory swapping from database traffic. Therefore the operating system and swap partition should be located on one physical disk with ENMA including its database on another. RAID 5 is not recommended as physical disk synchronization issues seem to cause high latency. RAID 1 (mirroring) is acceptable but must be a hardware implementation.