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

    You can install BMC Discovery by using a virtual appliance or a kickstart DVD. To install BMC Discovery from a kickstart DVD, first download the kickstart DVD image from the BMC Electronic Product Distribution (EPD) site. The image is large. Therefore, make sure that you use a dual layer DVD and burner when writing the image to a physical DVD. Before Installing using the DVD, make sure that you read the prerequisites. For more information about installing on virtual appliance, see Installing the virtual appliance.


    No OS customizations are supported on the appliance

    The BMC Discovery software is delivered as an appliance model, virtual or physical, which includes the entire software stack from a Linux OS and the BMC application software. The OS must not be treated for general purpose use, but rather as a tightly integrated part of the BMC Discovery solution. If you need to customize the OS, you must use the command line level if explicitly described in this online documentation, or under the guidance of BMC Customer Support. For any urgent business need to change the OS configuration, contact BMC Customer Support.

    Third party software

    BMC Discovery is built as an appliance that is not intended to have any additional software installed on it. If you have an urgent business need to install additional software on the appliance, see the third party software support page.

    Prerequisites

    Before installing BMC Discovery from the DVD, make sure that you fulfill the following prerequisites:

    • You must be an experienced Linux system administrator.
    • You must have read the Hardware requirements page for clusters and standalone appliances, and the sizing guidelines documentation for the current version of the product.
    • You must have read the Appliance sizing guidelines.
    • You must install BMC Discovery on x86-64 based hardware that is supported by CentOS 6 or later (64-bit only). Installation on 32-bit machines is not possible.
    • Before running BMC Discovery in FIPS compliant mode, you must read Running in FIPS compliant mode.

     

    Appliance sizing guidelines 

    You might need to consider many factors when specifying the configuration of the appliance. Every environment is different and consequently the data published here is purely a guide as to how to configure your appliance.

     Click here for detailed information on determining the required specification for your appliance.

    There are many factors to be taken into consideration when specifying the configuration of the appliance. Every environment is different and consequently the data published here is purely a guide as to how to configure your appliance.

     

    This section defines four classes of appliance deployment, which broadly follow how BMC Discovery is deployed in the field. These classes are differentiated by the number of Operating System Instances (OSIs) that are being scanned by BMC Discovery. The names given to these classes are of use only in this document and do not relate to the various editions of BMC Discovery. The four classes are:

    The following initial guidelines are based on typical deployments of standalone systems in the field, and are intended to serve only as recommended configurations for your environment.

    • Proof of Concept—Small, time-limited test deployments of BMC Discovery, scanning up to 150 OSIs. The Proof of Concept class has minimal storage allowance as they are only intended for a limited period of scanning such as a week long trial. For longer periods or a continuously used development or UAT system, the Baseline class is the minimum recommended.
    • Baseline—A typical baseline as offered by BMC. Scanning up to 500 OSIs.
    • Datacentre—A typical large scale deployment. Scanning up to 5000 OSIs.
    • Consolidated Enterprise—Enterprise scale deployments, typically a Consolidation Appliance taking feeds from many Scanning Appliances. Typically scanning or consolidating of the order of 20000 OSIs or more. At these levels, a weekly scanning or focused scanning strategy may need to be adopted.

    Memory and swap considerations

    The recommended figures for memory provide a good level of performance in typical scenarios. The upper level should not be considered a limit, as BMC Discovery will make use of all available memory. Note that the operating system will often make use of some swap, even if there is plenty of RAM available – the use of swap is not in itself a sign that there is insufficient RAM, just a consequence of the operating system optimizing all of its memory resources.

    If RAM is available, the OS uses some as a filesystem cache which dramatically improves system performance. As datastore files grow then a correspondingly large increase in RAM can help to maintain levels of performance. In many cases, the datastore files are very large, of the order of 10 to 100 GB. For example, for a large datastore, performance improvements have been seen by increasing RAM from 32 GB to 128 GB and further still to 256 GB.

    The recommended figures for swap can be exceeded; there is no harm in doing so, and having more swap can mean more RAM is available for buffers and caches, improving performance. All virtual appliances are initially configured with 8 GB swap. Memory and swap usage depends on the nature of the discovery being performed, with Mainframe and VMware (vCenter/vSphere) devices requiring more than basic UNIX and Windows devices, where the following tables refer to CPUs, full use of a logical CPU (core) is assumed. For example, if eight CPUs are required, then you may provide them in the following ways:

    • Eight virtual CPUs in your virtualization platform, such as VMware Infrastructure.
    • Four dual core physical CPUs.
    • Two quad core physical CPUs.

    Appliance sizing guidelines

    Resource

    POC

    Baseline

    Datacentre

    Consolidated Enterprise

    CPUs

    2

    2

    4

    4 to 8

    RAM
    (GB) available to OS.

    2 to 4
    (see note below)

    4 to 8

    8 to 16

    16 to 32 or more

    Swap Space
    (GB)

    4 to 8

    8 to 16

    16 to 32

    16 to 32

    DB Disk (GB) - No backup

    37

    100

    200

    200 to 660

    DB Disk (GB) - With local backup

    37

    200

    400

    450 to 1300

    The disk configuration utility uses the following calculation to determine the best swap size.

    • Where the amount of memory is less than 16 GB swap size is set at double the memory size.
    • Where the amount of memory is between 16 and 32 GB swap is set at 32 GB.
    • Where the amount of memory exceeds 32 GB swap is set to equal them memory.

    The disk requirement with local backup is lower than in previous versions as the appliance backup feature does not use as much disk space as appliance snapshot when creating the backup.

    Memory requirements for POC class

    2GB RAM is sufficient for normal operation, but is insufficient to activate a new TKU. To activate a TKU requires 4GB of RAM. You can increase the memory for activation and then reduce it for normal operation if required.

    BMC recommends that for best performance, you use two logical disks. For single disk installations, your sizing calculations must be based on the size of the database plus the size of the OS disk (146 GB).

    Installing BMC Discovery

    Partitioning destroys all data on disks

    Installing BMC Discovery involves partitioning your disks. Partitioning disks destroys any data on those disks. Therefore, you must understand partitioning before installing BMC Discovery.

    To install BMC Discovery from a kickstart DVD:

    1. Boot your host using the kickstart DVD.
      For more information, see the documentation supplied with the hardware platform. A splash screen appears, which enables you to select installer options (press F2 to see more information). Choose from the following options:
      • install to install on a system configured as specified in Appliance hardware platforms. This option performs an installation that completely overwrites any data on the system, and enables you to set network configuration, keyboard layout, language and timezone. BMC Discovery will always be installed onto the first disk. Additional disks can be configured from the BMC Discovery UI when the install is complete.
      • custom This option enables you to customize disk partitioning, but is otherwise identical to the install option. Always use the install option in preference to the custom option, even if you have multiple disks. Should you use custom to create a non-standard disk layout, the Disk Configuration feature will not be able to manage BMC Discovery storage. When using the custom option, ensure that the /boot partition is 250 MB as in the default partitioning scheme.

        Unsupported boot options

        At this stage you can specify boot options if, for example, you want to customize the install. However, this is not supported. See the CentOS documentation for information on boot options.

    2. Specify one of the supported options at the boot: prompt and press Enter.
      The CentOS installer starts. If you have more than one network interface, you are prompted to choose one.
    3. Select the first ethernet device, eth0, and click OK.
    4. At the TCP/IP configuration screen, enter the required networking information and click OK.
      If you select manual configuration, one or more further configuration screens will be presented. Provide the requested information.
    5. If the disks are not recognized or have never been partitioned, a partitioning table warning is displayed. Click Yes to proceed.
    6. For the language to use during installation, select English and select the appropriate keyboard for the system.
    7. When the time zone configuration screen appears, perform the following steps:
      1. Tick the "System clock uses UTC" option.
      2. Select the correct time zone.
    8. If you selected the custom option, use the following steps to configure the disks:

      Non standard disk configuration

      These custom install instructions will result in a valid disk layout identical to that created by the install option. The disk configuration utility cannot be able to manage disks if volume groups or a non standard disk configuration are used.

      1. Which type of installation would you like...

        1. Select the Replace Existing Linux System(s) installation type.
        2. Do not select the Encrypt system option.
        3. Select the Review and modify partitioning layout option.
        4. Click Next.
      2. Please select a device...

        Partitioning destroys all data on disks.

      3. Delete the volume group shown beneath LVM Volume Groups and delete all remaining partitions on all disks.
        If you do not delete the LVM volume group, you will not be able to use the disk configuration utility to manage disks.

      4. Create the partitions in this volume using the sizes described in the following table as a guide.

    Mountpoint

    Type

    Size (MB)

     

    swap

    16384
    For more information about recommended swap size, see Appliance sizing guidelines.

    /boot

    ext4

    250

    /var

    ext4

    1768

    /var/log

    ext4

    896

    /var/log/audit

    ext4

    896

    /tmp

    ext4

    2048

    /home

    ext4

    1536

    /

    ext4

    1024

    /usr

    ext4

    100 (Fill to maximum allowable space.)

          The partitioning and installation of the OS and BMC Discovery begins. This might take some time.

    9. When the installation has completed, remove the DVD and click Reboot. The BMC Discovery banner displays networking information. The installation is now complete. If you have more than one disk, configure them post-installation using the disk configuration utility.

    • No labels