• Spaces
  • Collections
  • Help
    • ×
     
     
    •  
    BMC Real End User Experience Monitoring 2.5

    Page tree

    This section lists hardware and software requirements for virtual machine-based components and for other components that must be met before installing the product.

    Platform requirements for virtual machines

    BMC Real End User Experience Monitoring components are virtual machines designed to run on the virtualization platform (hypervisor) products in the following table:

    Supported virtual machine platforms and operating systems

    Virtual platformOperating systemNotes

    Citrix Xen

    • XenServer 6.0.2
    		None

    Linux Kernel-based Virtual Machines (KVM)

    • Red Hat Enterprise Linux Server 6.3 (Santiago)
    		None

    Microsoft Hyper-V

    • Windows Server 2012
    • Windows Server 2008 R2
    		None

    VMware

    • ESX/ESXi 5.x
    • ESX/ESXi 4.x
    • ESX/ESXi 3.5
    • For component instances using more than 4 GB of memory, you must use VMware ESX/ESXi 5.x. You can also use VMware ESX/ESXi 4.x, but it must be the Enterprise Plus version. For more information, contact VMware Support.
    • OVF 1.0 files are supported by VMware vSphere 4 (and later) products, VMware vCenter 4 (and later), and VMware ESX/ESXi 4 (and later). For backward compatibility with earlier versions of vCenter and ESX, you must use a conversion tool, such as VMware vCenter Converter 4.0. (VMware discontinued support for the OVF format in vCenter Converter 4.3.) For more information, see the VMware website. For instructions on how to convert the description file, see Installing a component from an OVF file.

    Hardware requirements for virtual machines

    Server hardware and hypervisors must support 64-bit guests. Each instance of the various BMC Real End User Experience Monitoring components has the following minimum resource requirements:

    Minimum resource requirements per component instance

    Component

    Processor

    Memory

    Disk

    Number of network interfaces

    BMC Application Performance Management Console

    1 vCPU

    4 GB

    20 GB

    1

    Real User Analyzer

    2 vCPU

    8 GB

    16 GB1

    1

    Real User Collector

    1 vCPU

    8 GB

    28 GB

    2

    Real User Monitor2 vCPU8 GB16 GB12

    Performance Analytics Engine

    2 vCPU

    4 GB

    10 GB

    1

    Aggregation Server for Extended Reporting2 vCPU5 GB30 GB1
    Data Warehouse for Extended Reporting4 vCPU10 GB300—500 GB1
    1 An additional 100 GB minimum is recommended for storing traffic data.

    Recommendations

    • While recent hypervisor products are able to manage resource allocation dynamically, it is important not to overallocate processor and memory resources. It is also important to remember that the hypervisor itself has resource requirements. Therefore, if a given host has 32 GB of memory, for example, and you deploy components which together have requirements approaching 32 GB, you can expect problems.
    • To optimize the performance of a component, you can increase or decrease resource allocations. If performance is unsatisfactory, for example, you can add extra processing power or memory.

    Note

    Host hardware and memory latency can limit performance.

    For additional hardware requirements based on traffic volume, see Sizing considerations.

    System requirements for Real User Cloud Probe

    The Real User Cloud Probe agent connects to a running BMC Real End User Cloud Management system. The following system requirements are necessary to install the Cloud Probe:

    • Operating system:
      • Red Hat Enterprise Linux 5.8 (64-bit)
      • Red Hat Enterprise Linux 6.1 (64-bit) (Basic Server or Minimal installations)
      • Red Hat Enterprise Linux 6.2 (64-bit)
      • Red Hat Enterprise Linux 6.3 (64-bit)
      • Windows 2008 Server (R2)
      • Windows Server 2012
      • Windows Win 7 (64-bit)
      • Windows Win 8 (64-bit)
    • Hardware: Each server where the Real User Cloud Probe is installed requires the following minimum hardware:
      • 2 GB RAM
      • 2 CPUs
      • Network interface card (NIC) card that supports the ethtool command
    • Network: The Real User Cloud Probe must connect to an instance of the Real User Collector using HTTPS. You can change the default port (443), if necessary.

    Note

    Before installing Real User Cloud Probe on Windows operating system, ensure you have WinPcap tool installed on the Cloud Probe machine. It is necessary for the correct functioning of the Cloud Probe on Windows OS.

    Note

    In the table below, see the approximate percentage of CPU and RAM capacity used by the Cloud Probe on the tenant computer (tested with 2 virtual CPUs and 4Gb RAM on Linux, and with 4 virtual CPUs and 16Gb RAM on Windows).

    Cloud Probe CPU and RAM usage

    Operating systemExpected volume of trafficCPU consumptionRAM consumption
    Red Hat Enterprise Linux 6.3~1000 hits/sec~5%~10%
    Microsoft Windows 2008 Server (R2)~800 hits/sec~5%~10%

    For system and network configuration requirements before installing the Cloud Probe, see Setting up the Cloud Probe installation environment.

    System requirements for Extended Reporting

    The following systems are required to implement Extended Reporting.

    Oracle database

    The BMC Real End User Experience Monitoring Extended Reporting component requires a database instance to serve as the data warehouse. Following are the requirements for the database system.

    • Database: Oracle Database 11g Release 2 Enterprise Edition running on Linux (Oracle partitioning is required.)
    • Operating system: Red Hat Enterprise Linux 6.1, Basic Server or Minimal installations
    • Hardware: The database system requires the following minimum hardware:
      • 10 GB RAM
      • 4 CPUs
      • 300—500 GB storage

    SAP BusinessObjects Enterprise

    The BMC Real End User Experience Monitoring Extended Reporting component requires the SAP BusinessObjects Business Intelligence Platform version 4.0. 

    • Operating system: Microsoft Windows Server 2003 or Windows Server 2008, 64-bit versions only.
    • Hardware: The following minimum hardware is recommended:
      • 8 GB RAM
      • 4 CPUs
      • 80 GB storage

    You should validate the system requirements in the documentation for the SAP product through the SAP BusinessObjects Indirect Client Knowledge Center. You can register for documentation access on that site.

    Storage requirements

    Consult the following table for components that have storage requirements:

    Component storage requirements and recommendations

    ComponentStorage purposeRequirement
    Real User Analyzer or Real User MonitorUsed for saving historical data you can access via the Session Browser (Analyzer). This data is stored "on board" the component.

    The default disk configuration is 16 GB (only 1 GB for data storage). To accommodate larger volumes of data, you can create a data disk (minimum 100 GB; maximum 570 GB) for each Analyzer instance.

    Recommendation: Before installing the Analyzer instance, create the data disk with VMware tools.

    Warning: You can change processor and memory allocations any time during the life of the component instance. However, for data storage, if you change the disk, data collected to date is deleted.
    Performance Analytics EngineUsed for saving historical data you can access via the Performance Analytics Query feature (BMC Application Performance Management Console). This data is stored "off board" on a device such as a Network Attached Storage (NAS) system.

    The minimum useful storage allocation is 10 GB per BMC Real End User Experience Monitoring system. There is no upper limit.

    Note: More Performance Analytics Engine instances imply a higher volume of incoming data, so a larger storage allocation might be warranted.

    The following options are supported for the NAS device:

    • Server Message Block/Common Internet File System (SMB/CIFS)
    • Network File System (NFS)
    • Local disk

    The management of storage space is based on a rolling-buffer data structure (first in, first out—FIFO). When a storage disk reaches its maximum capacity, new data overwrites the oldest data.

    Aggregation Server for Extended ReportingUsed to temporarily store extracted data from an Analyzer and for transforming data into multidimensional data models (performance cubes). This data is not permanently stored on the NAS device.The minimum storage allocation is 30 GB. The Server Message Block/Common Internet File System (SMB/CIFS) protocol is supported for the NAS device.

    Network requirements

    BMC Real End User Experience Monitoring components are network devices interconnected to form a system. In addition, access to the interfaces of these components is achieved via the web. To avoid network-related performance issues, you must take certain configuration and infrastructure details into consideration when planning an installation. For example, the system works best when you deploy components on the same host. Where a common host is not possible, optimize the communications links between components. Similarly, the connection between Performance Analytics Engine instances and their storage devices must be optimal.

    For more information about network requirements and the required ports, see the following topics:

    For BMC Real End User Experience Monitoring Extended Reporting, the Aggregation Server and SAP BusinessObjects require access to the Oracle database default listener port (TCP 1521).

    Note

    The IPv6 management interface is not supported by the Real User Analyzer and the Aggregation Server.

    Warning

    vmxnet2 network adapter is not supported by the system.

    Supported LDAP servers

    • Microsoft Windows Server 2008 Active Directory
    • Microsoft Windows Server 2003 Active Directory
    • OpenLDAP (slapd)

    Compatible web browsers

    You can access the user interfaces by using the following combinations of operating systems and web browsers.

    Compatible web browsers and operating systems for the Console

     

    Browser →


    Operating system ↓

    Microsoft Internet Explorer 9

    Microsoft Internet Explorer 8

    Mozilla Firefox1

    Google Chrome1

    Apple Safari1

    Mac OS X

     

     

     

     
    (tick)

    Microsoft Windows 7
    (tick)
    (tick)
    (tick)
    (tick)

     

    Microsoft Windows XP

     
    (tick)

     

     

     

    Linux Ubuntu 10.04 LTS

     

     
    (tick)

     

     

    1 Use the latest version of the browser.

    Recommendation

    To access the documentation portal, BMC recommends that you use the Mozilla Firefox browser.

     

     

     

    16 Comments

    1. Yuriy Koziy

       

    2. Gregor Keller

       

      1. Yuriy Koziy

         

        1. Sandy Reid

           

    3. Craig Jackson

      I've been told that the Cloud Probe is now delivered for SuSE Linux Enterprise Server (SLES) as well as RHEL.

      Also, there are two newer versions of IE (10 and 11) in addition to those listed in the table.

      1. Melody Locke

        Hi, Craig.

        The browser compatibility list is correct. We currently support only IE8 and IE9. 

      2. Melody Locke

        Hi, Craig. 

        We currently don't support any platforms other than the ones listed. If you would like to install the Cloud Probe on a platform that is not supported, please open a ticket with Customer Support first. I have passed along your interest in these platforms to our development team.

    4. Chris Marcotte

       

    5. Chris Marcotte

       

      1. Veronika Konkova

         

    6. Chris Marcotte

       

      1. Veronika Konkova

         

    7. Chris Marcotte

       

      1. Melody Locke

         

    8. Anton Kasimov

      I don't understand how many network interfaces do I need for deploying all components on same host. I think that it's 2, one for listening traffic (without ip address) and one for manage REUEM (with ip address). Is it true?

      1. Louis-michel Gelinas

        Hi Anton, 

        You are right. Most EUEM components only require one NIC (to manage and use it). Components that do 'packet capture' (like Collectors/Monitors/APM Central) need a second NIC on which we only 'listen' to traffic to be analyzed. 

        Components that to not do 'packet capure' (like Analyzers/Consoles/etc) only need one NIC. 

         

        hope this helps. 

        lm

         

    © Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.