Installing a component from an ISO image file

The instructions below provide examples of how to deploy a virtual instance of a BMC Real End User Experience component onto a Linux Kernel-based Virtual Machine (KVM) or Microsoft Hyper-V platform by using an ISO image file. When you create a virtual machine by using the ISO image file, you must create the CPUs, network interfaces, and disk devices according to the sizing considerations. For detailed instructions on how to deploy a VM, refer to the documentation for your hypervisor platform and management tool.

For information on deploying components onto a VMware or Citrix platform from an OVF file, see Installing a component from an OVF file.

Before you begin

After you have downloaded the installation files, unzip each distribution package and save its components to one of the following locations:

• A file system local to your virtualization environment
• A network server accessible to your virtualization environment

Real User Collector, Monitor, and APM Central component instances

• For a Collector, Monitor, APM Central component instances, you must add a management port and a capture port to the appropriate virtual ports in your inventory. The management port requires a virtual network adapter.
• Each Collector, Monitor, APM Central component instance can have as many as four capture ports. You must add a virtual network adapter for each capture port.

• Capture ports must have Promiscuous Mode/Accept enabled.

  Capture limitations in Hyper-V

  Passive (promiscuous) mode traffic capture is not possible on a Microsoft Hyper-V system, because the Virtual Switch (vSwitch) will not forward packets to a virtual machine unless it has the MAC address of the virtual machine as a destination. In order to deploy a Real User Collector on Hyper-V, you must use Encapsulated Remote SPAN (ERSPAN) with a Generic Routing Encapsulation (GRE) tunnel to encapsulate and carry the traffic .

  For additional information, see the Knowledge Base article KA395990 (Support logon ID required).

Real User Analyzer, Monitor, and APM Central component instances

Before installing a Real User Analyzer, Monitor, and APM Central component instance, create the data disk. The descriptor file for the Analyzer, Monitor and APM Central is not preconfigured with a storage disk. To store a large volume of data, you must configure a disk between 100 and 570 GB in size.  For storage requirements, see Storage requirements in the System requirements and Sizing considerations.

To create a virtual machine and deploy a component on a Microsoft Hyper-V system

The following instructions describe how to create a new virtual machine and deploy a component on a Windows Server 2008 R2 Hyper-V host.

1. Start the Hyper-V Manager.
2. To create a virtual machine from which to to boot the ISO image, select Action > New > Virtual Machine.
3. In the New Virtual Machine Wizard, provide a meaningful Name for this Virtual Machine and click Next.
4. Enter the amount of RAM to allocate to the virtual machine and click Next. For memory requirements, see Hardware requirements for virtual machines in the System requirements and Sizing considerations.
5. Select the network to which this virtual machine should be connected and click Next. For network requirements, see Network requirements in the System requirements and BMC Real End User Experience Monitoring deployment use cases.
   

    

   Note

   The wizard installs one network card on the virtual machine. To capture traffic, a second network card should be added to a Real User Collector, Monitor, and APM Central component instance before you boot it to perform the installation in Step 9. Add a network card manually after the virtual machine is created. You can define a network in Hyper-V Manager by using the Virtual Network Manager.

6. Create or specify a hard disk and click Next. For storage requirements, see Storage requirements in the System requirements and Sizing considerations.

7. Click Install an operating system from a boot CD/DVD-ROM, and select the ISO image for the component that you want to install in this virtual machine.

8. Click Finish. 
9. Start the virtual machine and perform the installation of the component.
   
   1. In Hyper-V Manager, double-click the virtual machine to connect to it.

   2. Start the virtual machine. The virtual machine will boot from the ISO image and will perform checks to ensure the virtual hardware is appropriate for this product. If any hardware resource is inappropriate, messages explaining the problem and solution are displayed. You will need to shutdown, fix, and reboot the virtual machine if this occurs.

   3. If the hardware is appropriate, press Enter to initialize the image and start the installation.
      

      

      Once the installation is complete, the install procedure will automatically eject the (virtual) CD-ROM and reboot into the system. Once booted, the virtual machine will attempt to get an IP address using DHCP.
10. Set up a component instance.

To create a virtual machine and deploy a component on a Linux KVM system

1. Create a virtual machine from which to to boot the ISO image. On a KVM, you can use the Virsh install command to create the virtual machine. The example below demonstrates how to create the EUEM_Collector.

   Example

   virt-install --name "EUEM_Collector" \
       --ram 4096 --cpu host
       --network=bridge=br0,model=virtio \
       --network=bridge=br1,model=virtio \
       --disk /data01/EUEM_Collector.img,size=28,bus=virtio --vnc \
       -c /data01/isos/tc-1.4.60.100.iso

    

   Specify the parameters according to the type of component you are deploying and the Sizing considerations.

   • For memory requirements, see also Hardware requirements for virtual machines in the System requirements.

   • For storage requirements, see also Storage requirements in the System requirements.

   • For network requirements, see Network requirements in the System requirements and BMC Real End User Experience Monitoring deployment use cases. The first network card will be used a management port on all components, additional network cards will be used to capture traffic by a Real User Collector or a Real User Monitor. You can change this later; however, make sure you connect the second network card to the network where you want to monitor network traffic.

     Notes

     The  VirtIO network and disk drivers are critical to proper virtual machine performance. Refer to your virt-install documentation for more detail.

     You could also use the Virtual Machine Manager (virt-manager) to create the virtual machine. If you do, use the options in the virt-install example to obtain a similar configuration. To specify CPU configuration in virt-manager, select VM Settings > Processor > Configuration > Copy host CPU configuration and click Apply.

     
     
2. Use the Virtual Machine Manager (virt-manager) to perform the installation of the component, which is similar to the process describe in Step 9, of the procedure "To create a virtual machine and deploy a component on a Microsoft Hyper-V system."

3. For a Real User Collector or a Real User Monitor, apply the following settings to the network capture interface to ensure the product captures all packets.

   To set the	Issue the command	Instruction
   Capture bridge aging time to 0 to avoid keeping the MAC address table in bridge mode	brctl setageing br<n> 0	Replace n with the appropriate bridge index.
   Capture bridge forward delay to 0 to avoid dropping packets	brctl setfd br<n> 0	Replace n with the appropriate bridge index.

   Issue these commands after every reboot on the host as root. See the operating system documentation for information on how to make these settings persist.

4. Set up a component instance.

Related topics

Installation process overview for BMC Real End User Monitoring