Chat now with support
Chat with Support

Foglight Evolve 6.1.0 - Foglight Evolve Virtual Appliance Installation and Setup Guide

Configure the virtual appliance

To begin using Foglight Evolve, open a standard web browser and type the IP address of the Foglight Evolve virtual machine. For a list of validated web browsers, see the System Requirements and Platform Support Guide.

The page loads and requests a user name and password. The default user name is foglight and the default password is foglight_admin_password_placeholder.

Start monitoring your environment:

To collect data from a vCenter®, create at least one VMware® Performance agent, using the Foglight for VMware cartridge automatically installed with Foglight Evolve. For detailed instructions about this topic, see the Managing Virtualized Environments User and Reference Guide, “Configuring Monitoring Agents for Data Collection” section.
To collect data from the storage devices in your environment, you must configure StorageCollector agents, using the Storage & SAN/Storage Environment/Administration dashboard. For more information, refer to the Foglight for Storage Management User and Reference Guide.
To collect data from Hyper-V servers in your environment, you must create Hyper-V Performance agents, using the Foglight for Hyper-V cartridge automatically installed with Foglight Evolve. For more information, refer to the Foglight for Hyper-V User and Reference Guide.

Next step: If you need to change the static IP address of the FMS VM, see Change the network settings.

Change the network settings

 
* 
NOTE: The following procedure should be implemented only after the vApp has completed its initialization, after being deployed and started for the first time. Assigning a static IP address requires a restart of the network services on the virtual machine. Restarting the network before the vApp is initialized interrupts the connection between the FMS and DBS VMs, and could result in some cartridges not being enabled.
The vApp initialization process normally takes about 10 minutes after the vApp is started for the first time. The easiest way to determine that the vApp has completed its initialization is to look at the CPU utilization for the FMS. The CPU shows some activity during the initialization, but goes down to just a few percent when the initialization is complete.

Both FMS and DBS VMs have two NICs — one for communication to the outside and one just for communication to each other. The two NICs that communicate between the VMs have static IPs that should not be changed (192.168.200.1 and 192.168.200.2, respectively).

Change the NICs that are used to communicate to the outside world (that is, eth0) on both FMS and DBS VMs.

If DHCP is enabled, you should see IPs in your range assigned to the FMS and DBS VMs. If you have these IPs, open a web browser to http://<FMS IPaddress> and log in using the user name foglight and password foglight_admin_password_placeholder.

Figure 1. Changing a static IP address

If DHCP does not provide IPs for the FMS and DBS VMs, edit the network settings in the OS.

To configure networking for a static IP, the following information is needed:

•
IP address
•
Subnet Mask
•
Default gateway
•
Nameserver(s)
To change a static IP address:
1
Open a console and log in using the user name root and password F@g1i9hT#v01vE.
2
Run yast.
The YAST® menu appears.
3
Use the arrow keys to select System > Network Settings, then press Enter.
4
Tab to Device eth0 and press F4 to edit this device.
5
Tab to Statically assigned IP Address and press the spacebar to select it.
6
Tab to and fill out the IP Address and Subnet Mask Fields.
7
Press F10 to continue.
8
Use the arrow keys to select Hostname/DNS.
9
Tab to Domain Name and enter your domain.
10
Tab to the Name Server fields and enter one or more Name Servers.
11
Tab back up to the top row and use the arrow keys to select Routing.
12
Enter your default Gateway and press F10 to save the changes.
The changes are applied and the network is restarted.
13
Press F9 to quit and return to the console.
14
Once you are back on the console, ping your vCenter® by FQDN to ensure that the name server, gateway, and IP are working as expected.

Next step: If you need to change the timezone for your virtual appliance, see Change the timezone.

Change the timezone

The timezone settings in your virtual appliance can be changed in several ways. The following options are recommended:

•
Option 1. Manually change the date
•
Option 2. Manually change the timezone
•
Option 3. Change the hardware clock
•
Option 4. Change the localtime file
•
Option 5. Change the timezone file
Option 1. Manually change the date
To manually change the date:
1
Use the date command for both viewing and changing the date and time.
2
Change the time by using the date command followed by the month, day, hour, minute, and year, all numeric and no spaces. For example, to set the date and time to “November 2nd, 2003 12:57”, use the command
date 110212572003
Option 2. Manually change the timezone
To manually change the timezone:
1
The hardware clock can be updated in UTC (coordinated universal time), or a required local time.
hwclock --utc --systohc
2
Update it to local time by removing the --utc and adding --localtime.
hwclock --systohc
Option 3. Change the hardware clock

The date and time can be changed directly to the hardware clock and then used to update the system clock.

To change the system clock by updating the hardware clock:
1
Change the hardware clock.
hwclock --set --date=”02/19/2003 15:00:00”
hwclock -- show
2
Change the system clock.
hwclock --hctosys
date
Option 4. Change the localtime file

The /etc/ localtime file is a link to or a copy of a file containing information about time zone. Zone information files are usually in /usr/share/zoneinfo, but this depends on your distribution. If the localtime file points to a zone info file that is not the time zone, this can be changed by browsing the directories in /usr/share/zoneinfo to find the local zone or country, then find the city or a city in the same time zone, and link localtime to it.

To change the localtime file:
•
$ ln -sf /usr/share/zoneinfo/America/Los_Angeles /etc/localtime

Some applications may use the configuration file /etc/sysconfig/clock to determine the current time zone, so it is recommended to set the ZONE entry (for example, “America/Los_Angeles”).

Option 5. Change the timezone file
To change the timezone file:
•
Navigate to /etc/timezone and enter the required timezone. For example, if only “Asia/Vladivostok” is contained in this file, remove this entry using a text editor of your choice (for example vi) and replace it with the required entry (for example, “Australia/Melbourne”). A restart of the appliance/VM is not required after making this change.

Configuring anti-virus exclusion settings

Anti-virus software may negatively impact the CPU and system performance of machines running Foglight. To reduce resource consumption, it is highly recommended to exclude the relevant directory from being scanned by the anti-virus software. The common installation directory is as follows:

:\Dell\
:\Quest\
:\Quest Software\
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating