• Spaces
  • People
  • Help
    • BMC Support Central BMC Communities BMC.com
    ×
    BMC TrueSight Operations Management 10.7

    Page tree
    Skip to end of metadata
    Go to start of metadata

    The BMC Real End User Experience Monitoring Cloud Probe component connects to a running Real User Collector. The following system requirements are necessary to install and use the Cloud Probe: 

    Operating system requirements

    The Cloud Probe supports the following operating systems:

    • Red Hat Enterprise Linux 5.8 and later (64-bit) 
    • Red Hat Enterprise Linux 6.x (64-bit) (Basic Server or Minimal installations)
    • Red Hat Enterprise Linux 7.x
    • CentOS 5.8 and later (64-bit) 
    • CentOS 6.x (64-bit)
    • CentOS 7.x (64-bit)
    • Ubuntu 14.04.xx LTS
    • Ubuntu 15.10
    • Ubuntu 16.04.xx LTS
    • Windows Server 2008 R2
    • Windows Server 2012
    • Windows Server 2012 R2 
    • Windows Server 2016

    Hardware requirements

    Each server where the Cloud Probe is installed requires the following minimum hardware:

    • 2 GB RAM
    • 2 CPUs

    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%

    Network requirements

    The Cloud Probe must connect to an instance of the Real User Collector using HTTPS. You can  change the default port (443), if necessary.

    For a list of the supported cipher suites, see Cipher suites support for SSL/TLS decryption.

    Network Time Protocol (NTP) synchronization

    Warning

    The data handled by application monitoring components, including all server components and agents, is time sensitive. If the time between components is not synchronized, you might see incorrect or partial data, or you might not see any data.

    Consult your operating system documentation to synchronize each component's internal clock with an NTP server on your network or on the Internet. Ensure that the clocks are regularly synchronized.

    This applies to all Real End User Experience Monitoring Software Edition components and integrated App Visibility Monitoring components.

    Software requirements

    Linux

     For Linux operating systems, you must have the following libraries installed:

    Note

     Exact names of the libraries may vary depending on your operating system and version.

    • Zlib
    • Libicu
    • Libpcap
    • Openssl
    • Pcre
    • Libcurl
    • Network Security Services (NSS)
    • ifconfig

     If you do not have these libraries installed, the installation will not run properly. 

    Windows 

    Before installing the Cloud Probe on a Windows operating system, you must download and install the WinPcap tool installed on the Cloud Probe machine.

    SSL/TLS and cipher suite support for HTTPS traffic

    If the Cloud Probe component monitors HTTPS traffic on the network, it supports the following SSL and TLS protocols versions:

    • SSL version: 3.0
    • TLS versions: 1.0, 1.1, and 1.2

     The following table lists the ciphers suites supported by the Cloud Probe:

    Supported SSL/TLS cipher suites

    Cipher suite nameCipher suite IDCipherMAC
    TLS_RSA_WITH_NULL_MD5

    0x000001

    		NULL

    MD5

    TLS_RSA_WITH_NULL_SHA0x000002NULLSHA
    TLS_RSA_EXPORT_WITH_RC4_40_MD50x000003RC4_40MD5
    TLS_RSA_WITH_RC4_128_MD50x000004RC4_128

    MD5

    TLS_RSA_WITH_RC4_128_SHA0x000005RC4_128SHA
    TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD50x000006RC2_CBC_40MD5
    TLS_RSA_WITH_IDEA_CBC_SHA0x000007IDEA_CBCSHA
    TLS_RSA_EXPORT_WITH_DES40_CBC_SHA

    0x000008

    		DES40_CBCSHA
    TLS_RSA_WITH_DES_CBC_SHA0x000009DES_CBCSHA
    TLS_RSA_WITH_3DES_EDE_CBC_SHA

    0x00000A

    		3DES_EDE_CBCSHA
    TLS_RSA_WITH_AES_128_CBC_SHA0x00002FAES_128_CBC

    SHA

    TLS_RSA_WITH_AES_256_CBC_SHA

    0x000035

    		AES_256_CBCSHA
    TLS_RSA_WITH_NULL_SHA256

    0x00003B

    		NULLSHA256
    TLS_RSA_WITH_AES_128_CBC_SHA256

    0x00003C

    		AES_128_CBCSHA256
    TLS_RSA_WITH_AES_256_CBC_SHA256

    0x00003D

    		AES_256_CBCSHA256
    TLS_RSA_WITH_CAMELLIA_128_CBC_SHA

    0x000041

    		CAMELLIA_128_CBCSHA
    TLS_RSA_EXPORT1024_WITH_RC4_56_MD5

    0x000060

    		RC4_56MD5
    TLS_RSA_EXPORT1024_WITH_RC2_CBC_56_MD5

    0x000061

    		RC2_CBC_56MD5
    TLS_RSA_EXPORT1024_WITH_DES_CBC_SHA

    0x000062

    		DES_CBCSHA
    TLS_RSA_EXPORT1024_WITH_RC4_56_SHA

    0x000064

    		RC4_56SHA
    TLS_RSA_WITH_CAMELLIA_256_CBC_SHA

    0x000084

    CAMELLIA_256_CBC

    		SHA
    TLS_RSA_PSK_WITH_RC4_128_SHA

    0x000092

    		RC4_128SHA
    TLS_RSA_PSK_WITH_3DES_EDE_CBC_SHA

    0x000093

    		3DES_EDE_CBCSHA
    TLS_RSA_PSK_WITH_AES_128_CBC_SHA

    0x000094

    		AES_128_CBCSHA
    TLS_RSA_PSK_WITH_AES_256_CBC_SHA

    0x000095

    		AES_256_CBCSHA
    TLS_RSA_WITH_SEED_CBC_SHA

    0x000096

    		SEED_CBCSHA
    TLS_RSA_WITH_AES_128_GCM_SHA2560x00009CAES_128_GCMSHA256
    TLS_RSA_WITH_AES_256_GCM_SHA3840x00009DAES_256_GCMSHA384
    TLS_RSA_PSK_WITH_AES_128_CBC_SHA256

    0x0000B6

    		AES_128_CBCSHA256
    TLS_RSA_PSK_WITH_AES_256_CBC_SHA384

    0x0000B7

    		AES_256_CBCSHA384
    TLS_RSA_PSK_WITH_NULL_SHA256

    0x0000B8

    		NULL

    SHA256

    TLS_RSA_PSK_WITH_NULL_SHA384

    0x0000B9

    		NULLSHA384
    SSL2_RC4_128_WITH_MD5

    0x010080

    		RC4_128MD5
    SSL2_RC4_128_EXPORT40_WITH_MD5

    0x020080

    		RC4_128_EXPORT40MD5
    SSL2_RC2_CBC_128_CBC_WITH_MD5

    0x030080

    		RC2_CBC_128_CBCMD5
    SSL2_RC2_CBC_128_CBC_WITH_MD5

    0x040080

    		RC2_CBC_128_CBCMD5
    SSL2_IDEA_128_CBC_WITH_MD5

    0x050080

    		IDEA_128_CBCMD5
    SSL2_DES_64_CBC_WITH_MD50x060040DES_64_CBCMD5
    SSL2_DES_192_EDE3_CBC_WITH_MD5

    0x0700C0

    		DES_192_EDE3_CBCMD5
    SSL2_RC4_64_WITH_MD5

    0x080080

    		RC4_64MD5

    Related topics

    Cloud Probe deployment use cases

    Setting up the monitored NIC for the Cloud Probe

    Installing the Cloud Probe

    8 Comments

    1. Sergey Kleyman

       

      1. Michael Taslitz

         

    2. Alexandre Boyer

       

      1. Michael Taslitz

         

    3. Alexandre Boyer

       

      1. Michael Taslitz

         

    4. Mohamed Eraky

      Dears,

      regarding the approximate percentage of CPU and RAM capacity used by the Cloud Probe.

      if I have 4000 hits per second last 5 mins this is mean the agent will consume 25% percentage form CPU and Memory 

      1. Sara Kamen

        Hi Mohamed,

        Yes, the Cloud Probe uses approximately the proportional amount of CPU and memory capacity. If the machine has the same specifications as the one documented above—on Linux, 2 virtual CPUs and 4Gb RAM—and the hit rate is about 4000 hits per second, then the agent uses approximately 20% CPU and 40% RAM.

        Alternatively, you can use a machine with four times the resources—on Linux, 8 virtual CPUs and 16Gb RAM)—so that the Cloud Probe supports four times the hit rate (4 x 1000 hit/sec) with 5% CPU and 10% RAM.

        Hope this helps!
        --Sara

    © Copyright 2005-2019 BMC Software, Inc.