Unsupported content


This version of the product is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Installing from the Kickstart DVD

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 if 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 the 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. We reserve the right to withdraw support, and make no guarantees that future upgrades will be compatible or maintain any of those customizations. We may ask for customizations to be removed for testing purposes. In practice, we will try and provide support for issues that are unrelated to the OS layer.


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.


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.
  • You must have read the Appliance sizing guidelines.
  • You must install BMC Discovery on x86-64 based hardware that is supported by CentOS 7/Red Hat Enterprise Linux 7 (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.


Do not customize the installed packages

The installation provides the opportunity to customize the installed packages. You must not do this. The configuration of the appliance is tightly controlled, which provides better supportability and lower costs, while maintaining a configuration optimized for the particular requirements of the BMC Discovery application. Additional packages may compromise the security, performance, and stability of the appliance.

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.

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 scanned by BMC Discovery. An OSI is a host, switch, router, storage device, printer, and so on.

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 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.

The four classes are:

  • 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, 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


(up to 150 OSIs)

(up to 500 OSIs)

(up to 5000 OSIs)

Consolidated Enterprise
(scanning or consolidating of the order of 20000 OSIs or more)






(GB) available to OS.

2 to 8
(see note below)

8 to 16

16 to 64

64 or more

Swap Space

4 to 16

16 to 32

32 to 64


DB Disk (GB) - No backup





DB Disk (GB) - With local backup






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

We recommend 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 specification. 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 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 750 MB as in the default partitioning scheme.


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

  2. Specify one of the supported options at the boot: prompt and press Enter.
    The OS installer starts. 
  3. For the language to use during installation, select English, and click Continue.
  4. From the KEYBOARD section, select the appropriate keyboard for the system, and click Done.
  5. In the NETWORK & HOSTNAME section, enter a host name, for example, appliance01 and click Apply.
    1. Select and enable the first ethernet device, the name varies depending on the hardware. For example, it might be ens160.


      You must enable a network device; they are disabled by default. To do so, click the slider button so that ON is visible. Failing to do so will mean the network device does not activate when the appliance boots.

    2. If you have any other network interfaces, enable those.
    3. Click Done.
  6. From DATE & TIME, select your timezone. Do not enable Network Time (NTP) in the installer, you should do that from the UI after you have completed the installation. Click Done.
  7. From INSTALLATION SUMMARY, click Begin Installation.
  8. When the installation has completed, remove the DVD and click Reboot. The installation is now complete. If you have more than one disk, configure them post-installation using the disk configuration utility.
  9. Once the appliance reboots, you can access the UI. You are immediately prompted to change the system (UI) password, and the root and tideway (command line) passwords.

If you chose the custom option

If you selected the custom option, use the following steps to configure the disks:


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

  2. If required to encrypt all partitions (excluding /boot) on the system with a single password, click the Encrypt my data check box. You will enter a password later.
  3. Select the disk onto which to install BMC Discovery and click Done. If you had selected Encrypt my data, you will now be prompted for a password. Set the password and click Save password.

    By default LVM is selected, you can use LVM, though if you do, you will be unable to use the Disk Configuration utility after installation. If you do not require LVM, select Standard Partition. You will be unable to use the Disk Configuration utility if any partitions are encrypted. 

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

    1. To add a mount point, click + at the bottom of the installation utility's partition table.
    2. When you enter partition sizes, the default is MB, you must specify GB explicitly.
    3. Click Add mount point to add the mount point.

    4. Change the file system to ext4






      750 MB



      5 GB



      5 GB


      8 GB



      1.7 GB



      1.2 GB



      896 MB



      2 GB



      Leave the desired capacity field empty to allow the partition to expand to the maximum allowable space.

    5. Click the Encrypt check box if encryption of the individual partition is required. You will be prompted for a password later. 

  5. Click Done. If you selected to encrypt individual partitions, you will now be prompted for a password. Set the password and click Save password.

  6. You are presented with a summary of changes. Review the changes. If they are correct, click Accept Changes.

  7. Click Begin Installation.

Related topics

Was this page helpful? Yes No Submitting... Thank you