How To Set Up A Foglight Experience Monitor On A Network On A Pc Or Mac Or Mac Mac Or Ipa On A Computer Or Ipat On A Powerline On A Router On A Black Box On A 2Nd Generation Computer On A Mini

Transcription

1 Foglight Experience Monitor 5.7.0

2 2015 Dell Inc. ALL RIGHTS RESERVED. This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser s personal use without the written permission of Dell Inc. The information in this document is provided in connection with Dell products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Dell products. EXCEPT AS SET FORTH IN THE TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, DELL ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL DELL BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF DELL HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Dell makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Dell does not make any commitment to update the information contained in this document. If you have any questions regarding your potential use of this material, contact: Dell Inc. Attn: LEGAL Dept 5 Polaris Way Aliso Viejo, CA Refer to our web site (software.dell.com) for regional and international office information. Patents This product is protected by U.S. Patents # 6,928,471; 7,539,655; 7,565,336; and 7,941,385. For more information, go to Trademarks Dell, the Dell logo, and Foglight, IntelliProfile, PerformaSure, and Tag and Follow are trademarks of Dell Inc. "Apache HTTP Server", Apache, "Apache Tomcat" and "Tomcat" are trademarks of the Apache Software Foundation. Google is a registered trademark of Google Inc. Chrome, Android, and Nexus are trademarks of Google Inc. Red Hat, JBoss, the JBoss logo, and Red Hat Enterprise Linux are registered trademarks of Red Hat, Inc. in the U.S. and other countries. CentOS is a trademark of Red Hat, Inc. in the U.S. and other countries. Microsoft,.NET, Active Directory, Internet Explorer, Hyper-V, SharePoint, SQL Server, Windows, Windows Vista and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. AIX, IBM, and WebSphere are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide. Sun, Oracle, Java, Oracle Solaris, and WebLogic are trademarks or registered trademarks of Oracle and/or its affiliates in the United States and other countries. SPARC is a registered trademark of SPARC International, Inc. in the United States and other countries. Products bearing the SPARC trademarks are based on an architecture developed by Oracle Corporation. OpenLDAP is a registered trademark of the OpenLDAP Foundation. HP is a registered trademark that belongs to Hewlett-Packard Development Company, L.P. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. MySQL is a registered trademark of MySQL AB in the United States, the European Union and other countries. Novell and edirectory are registered trademarks of Novell, Inc., in the United States and other countries. VMware, ESX, ESXi, vsphere, vcenter, vmotion, and vcloud Director are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. Sybase is a registered trademark of Sybase, Inc. The X Window System and UNIX are registered trademarks of The Open Group. Mozilla and Firefox are registered trademarks of the Mozilla Foundation. "Eclipse", "Eclipse Foundation Member", "EclipseCon", "Eclipse Summit", "Built on Eclipse", "Eclipse Ready" "Eclipse Incubation", and Eclipse Proposals" are trademarks of Eclipse Foundation, Inc. IOS is a registered trademark or trademark of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries. Apple, ipad, iphone, Xcode, Mac OS, and Safari are trademarks of Apple Inc., registered in the U.S. and other countries. Ubuntu is a registered trademark of Canonical Ltd. Symantec and Veritas are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. YAST is a registered trademark of SUSE LLC in the United States and other countries. Citrix and XenDesktop are trademarks of Citrix Systems, Inc. and/or one or more of its subsidiaries, and may be registered in the United States Patent and Trademark Office and in other countries. AlertSite and DéjàClick are either trademarks or registered trademarks of Boca Internet Technologies, Inc. Samsung, Galaxy S, and Galaxy Note are registered trademarks of Samsung Electronics America, Inc. and/or its related entities. MOTOROLA is a registered trademarks of Motorola Trademark Holdings, LLC. The Trademark BlackBerry Bold is owned by Research In Motion Limited and is registered in the United States and may be pending or registered in other countries. Dell is not endorsed, sponsored, affiliated with or otherwise authorized by Research In Motion Limited. Ixia and the Ixia four-petal logo are registered trademarks or trademarks of Ixia. Legend CAUTION: A CAUTION icon indicates potential damage to hardware or loss of data if instructions are not followed. WARNING: A WARNING icon indicates a potential for property damage, personal injury, or death. IMPORTANT NOTE, NOTE, TIP, MOBILE, or VIDEO: An information icon indicates supporting information. Foglight Experience Monitor Updated - February 2015 Software Version

3 Contents Installing and configuring Pre-installation considerations Required hardware and network information Network taps Installing Foglight Experience Monitor Installing the appliance on the rack Connecting the appliance Making network connections Setting the appliance clock Entering required network information Configuring the appliance Using the web console and setup wizard Entering a permanent license key Configuring the Appliance Type Designating Time Servers Configuring protocols Detecting ports in use Configuring servers Completing the Setup Wizard Maintaining the appliance Advanced configuration options Appliance management Data monitoring Foglight Experience Monitor and Ixia Net Tool Optimizers Multi-appliance clusters About multi-appliance configurations Setting up High Availability (HA) mode Configuring Probes for High Availability mode Deleting High Availability configurations Aggregation of metrics and configuration Aggregating metrics Configuration settings Storing report sets Switching from stand-alone to clusters Creating a cluster from a stand-alone appliance Configuring the appliance Network settings Foglight Mail Network Time Servers (NTP) SNMP Other

4 User accounts User account management Global user account options Increasing security for user account management and access privileges Security settings on the appliance Configuring the web server to use SSL Disabling the use of SSL Report settings groups Adding groups Scheduled reports Metric categories Database metrics Baseline calculations Time frames Distribution metrics Percentile metrics Foglight metrics User agent transformations Database configuration Viewing the database page Viewing the database details page Resetting a database Resetting the configuration Exporting a configuration Importing a configuration Setting database retention Configuring remote database access Purging existing resources Appliance integrity Viewing system information System information in a multi-appliance setup Viewing and changing the license Database repair log Updating the appliance Installing an upgrade Backing up and restoring data Restoring a backup How backup works About the security of your appliance Specifying monitored web traffic Configuration settings Identifying protocols Manually adding protocols and ports Automatically discovering ports Removing protocols Managing protocols on a Portal

5 Managing monitored servers Manually adding a new server Automatically discovering servers Removing servers Editing server details Configuring server options Configuring SSL keys Exporting SSL keys from IIS Managing servers on a Portal Using filters to exclude traffic Defining URL filters Testing URL filters Defining subnet filters Defining subnets Manually adding subnets Automatically discovering subnets Checking for overlapping subnets Configuring a default subnet Removing subnet definitions Managing subnets on a Portal Identifying user sessions How user sessions are identified Configuring user session identification Defining user session options Configuring client IP tags Augmenting user sessions log information Using logout patterns to detect completed sessions Monitoring instrumented web pages Instrumenting web pages Configuring instrumentation options and metrics Transforming monitored URLs Managing URLs Encoded and decoded URLs Setting URL encoding in the Resource List Setting URL encoding for user sessions metrics in the All Metrics View Filtering data in the Resource List Processing and aggregating URLs Sending URLs to the Foglight Experience Viewer Transforming URLs example using variable rules Managing URL transformation rules Defining site rules Declaring site rules Automatically discovering site rules Editing and removing site rules Defining path rules Segment rules as path rule components Segment rule actions

6 Managing path rules Editing and removing path rules Managing variable rules Transforming query variables Transforming form variables Transforming session identification variables Performing actions on variable names and values Using hints Defining page hints Defining hit hints Defining asynchronous page hints Defining asynchronous hit hints Testing hints Deleting hints Using page definitions Advanced URL options Show ports in URLs option Show parameters in URLs option Show HTTP request methods in URLs option POSTs with no content-type should be handled as XML option Proxy tunneling Do not strip the www prefix from URLs option Ignore 401 codes during NTLM authentication option Exclude redirections from metric calculations option Use HTML parser for page recognition option Extensions Response codes Managing applications Integrating with CA SiteMinder Communicating with SiteMinder Integrating with SafeNet Hardware Security Modules (HSMs) Before you begin Configuring Foglight Experience Monitor to use SafeNet HSM Associating monitored SSL ports with HSM keys Managing application components Defining an application component Editing an application component Deleting an Application Component Defining an instrumented application component Editing an instrumented application component Deleting an instrumented application component Managing services definitions Defining a service Configuring services auto-discovery Configuring synthetic transactions Managing existing service definitions Using alternative methods to define a service

7 Monitoring Microsoft Office SharePoint Servers Configuring SharePoint monitoring Configuring how URLs display SharePoint and SOAP Monitoring PeopleSoft applications Monitoring PeopleSoft applications Configuring how URLs display Monitoring Siebel applications Monitoring Siebel applications Configuring how URLs display Monitoring SOAP applications Defining a SOAP application Modifying SOAP application definitions Defining a SOAP transaction Managing existing SOAP transaction definitions Mapping SOAP operations to a web service Adding and removing SOAP tags Configuring enterprise-wide service levels Setting enterprise-based service levels Foglight components and the appliance Connecting to the Foglight Experience Viewer How Foglight Experience Monitor and Foglight Experience Viewer work together Connecting the appliance to your network Connecting Foglight Experience Viewer to a Foglight Experience Monitor Configuring monitoring appliances Foglight Management Server Ensuring product compatibility Setting up the Cartridge for FxM Configuring the appliance for data communication Exporting metrics to Foglight Synthetic transaction scripts Using the console program Accessing the console program Logging in using the Dell Remote Access Controller (DRAC) Logging in from Microsoft Windows Logging in from Linux and UNIX Exploring the main menu Network configuration Configuring the control device Configuring the auxiliary device settings Displaying information for monitor devices Advanced network settings System date and time configuration System date configuration System time configuration System timezone configuration

8 Database management Account management Change password Enable and disable SSH access Enable and disable web access Appliance update Update from CD Update from PKG file Update from USB flash drive Advanced options Configuring the appliance type Configuring Foglight Experience Viewer settings Reset firewall to allow HTTP Add and remove network device Configuring the license More advanced options System restart Troubleshooting Sample output for NIC driver Reporting system status Logging out of the console program Troubleshooting the appliance Common issues when installing the appliance Appliance connection failure through a web browser All reports are empty Verify the network configuration and connectivity Verify the network tap configuration Verify the server configuration Appliance runtime issues Foglight Experience Monitor reports Report sets are not updating Confirming system health System performance System events Database performance Error rates Using the appliance support tools Install log Creating a support bundle Monitor NIC activity test TCP dump Appendix: Third party software Using X-Forwarded-For Enabling the insert X-Forwarded-For in the HTTP profile irule Configuring the web server to extract the IP address from the HTTP header

9 Appendix: Dell PowerEdge system appliance Dell PowerEdge R300 and R Dell PowerEdge R Dell PowerEdge R Dell PowerEdge R Updating the Dell system firmware on the appliance Accessing the drivers and downloads Downloading the ISO images Updating the firmware on the appliance Contacting Dell Technical support resources

10 1 Installing and configuring Foglight Experience Monitor is a comprehensive appliance-based solution that empowers organizations to effectively manage, troubleshoot, and optimize all components of the service delivery chain under their control. With our turn-key, self-contained computer system, customers gain unprecedented visibility into the inner workings of their network infrastructure and the quality of the end user s experience. The appliance provides concise, accurate information in real-time about component performance, systematic failures, and a wealth of other information. This provides configuration instructions, conceptual information, and instructions on how to use the browser interface. This guide is intended for users who want to configure Foglight Experience Monitor using the browser interface. Foglight Experience Monitor appliances are shipped with the Foglight Experience Monitor Quick Installation Guide, which provides all the essential information required to physically install the appliance, connect it to your network, and configure it to collect network traffic. This section follows the steps outlined in the Quick Installation Guide, and provides additional information about installing and configuring the appliance, as well as references to topics covered elsewhere in the or in the User Guide. For more information, see these topics: Pre-installation considerations Installing Foglight Experience Monitor Configuring the appliance Maintaining the appliance Advanced configuration options Pre-installation considerations This section provides a quick overview of items and network information required during the installation of a Foglight Experience Monitor appliance. For more information, see these topics: Required hardware and network information Network taps Required hardware and network information The following hardware is required before installation: Monitor and Keyboard during the installation process, you need a VGA monitor and keyboard with a USB connector to perform the initial setup of the appliance. Network Cables the appliance requires network cables to connect its Control port to your network and its Monitoring ports to network taps. If you plan to use multiple Monitoring ports, the corresponding number of cables is required (for more information, see Multiple monitoring ports). The following network information is required before installation: 10

11 Appliance IP Address a unique IP address assigned to Foglight Experience Monitor. Subnet Mask the subnet mask that corresponds to the Foglight Experience Monitor IP address and the subnet. Gateway the IP address of your network s gateway. Primary DNS IP Address allows the appliance to perform DNS look-ups. Network Time Protocol (NTP) server the IP address of one or more NTP servers. This allows the appliance to synchronize its clock with an external NTP server. Ports the port numbers used on your network for HTTP and HTTPS network traffic. Figure 1. Monitor Devices menu The Monitor Devices menu in the console program shows which monitoring ports are in use. For more information about the console program, see Displaying information for monitor devices and Accessing the console program. Network taps A network tap provides monitoring access to the traffic flowing across a network. Different types of devices are often used as network taps, but only full-duplex network taps and smart taps with full-duplex enabled guarantee the 100% data capture that requires to provide complete and accurate data processing and reporting. A true full-duplex tap splits the ingress traffic (requests to the web servers) and egress traffic (responses from the web servers) into two streams. When those streams are fed into two separate monitoring NICs on an appliance, you get full data capture. IMPORTANT: Foglight Experience Monitor does NOT support monitoring web traffic using SPAN ports or aggregation network taps. These devices do not reliably mirror all traffic routed through them to the monitoring port, which results in inaccurate data in Foglight Experience Monitor. For more information, see Understanding packet drops with unsupported network taps. Configuring a network tap Installing a tap between two points on a network requires that the network cable connecting these points be replaced with a pair of cables both feeding into the tap. The tap passes through all traffic between the two points normally so there is no disruption to the normal traffic flow, and it also copies that traffic to its monitor port. Connecting the tap s monitor port to one of the appliance s monitoring ports provides the network traffic that the appliance needs to monitor your applications. Two tap providers include Datacom Systems ( and NetOptics ( 11

12 It is important that you consider the type of ports you are connecting (for example, RJ45, fiber LC, fiber SC). Network taps have different connector options that should match the type of connections used on your network. IMPORTANT: Connecting the appliance to a port that is part of a VLAN results in incomplete traffic monitoring and inaccurate metrics. As a member of a VLAN, that port is only exposed to VLAN broadcast traffic, and cannot see traffic going to other servers. Consequently, this is not a valid deployment option. To connect the network tap to a network, disconnect the cables from switch/server/router A and B. Next, connect the cable from switch/server/router A into Network port A on the network tap, and the cable from switch/server/router B into Network port B on the network tap. Figure 2. Connecting a network tap to the network Network Ports Monitor Ports To switch, server or router NOTE: Use this configuration when the network tap does not have a power supply. To connect the network tap to the appliance, connect Monitor port A to Monitoring NIC 1 (eth2) on the Foglight Experience Monitor appliance. Next, connect Monitor port B to Monitoring NIC 2 (eth3) on the Foglight Experience Monitor appliance. Figure 3. Connecting the network tap to the appliance Network Ports Monitor Ports To monitoring NIC 1 To monitoring NIC 2 Multiple monitoring ports Foglight Experience Monitor currently supports Dell PowerEdge systems that have up to eight monitoring NIC ports. NOTE: The number of Ethernet ports available on your appliance varies, depending on the hardware type. For a list of supported hardware platforms and guidance in identifying the Ethernet ports, see Appendix: Dell PowerEdge system appliance. When using multiple monitoring ports, the appliance automatically reads each NIC port for incoming traffic. No additional configuration on the part of the administrator is required. The console program allows you to see which ports the appliance is using for monitoring and enables you to perform basic troubleshooting for each port. 12

13 Understanding packet drops with unsupported network taps SPAN ports and aggregation network taps are often used for small-scale monitoring purposes. However, they are not reliable enough to support a large-scale, enterprise-critical monitoring solution like. The following bullets explain why these devices are unsuitable for use with. SPAN ports SPAN ports (also known as diagnostic ports) can be found on most switches and routers. Network traffic flowing through a switch can be mirrored to the SPAN port, which in turn connects to a monitoring solution. Switch providers do not guarantee that 100% of the traffic reaches the SPAN port. Spikes in traffic through the switch can result in a significant number of dropped packets (from 5% to as much as 20% of all packets). Dropped packets translate to poor data quality in. Aggregation network taps Aggregation network taps take a full-duplex link and merge the ingress and egress streams into a one half-duplex stream. While they drop substantially fewer packets than SPAN ports (due to the use of buffering), aggregation taps are not guaranteed to capture 100% of the traffic routed through them. Aggregation taps generally drop less than 1% of packets, but a 1% drop rate (potentially higher in some instances) has a significant impact on the quality of the data in. For information on supported network taps, see Network taps. Monitoring individual web servers In the simplest case, where the traffic you want to monitor is handled by one or two web servers, connect the appliance to a network tap located in front of the individual web servers. The appliance monitors only this traffic. Monitoring web server farms To monitor all web servers in a server farm, connect the appliance to a network tap between the firewall and the load balancer, as shown in the following diagram. This allows an appliance to see all traffic before it is separated out by server destinations. Redundant paths to the server farm (or multiple server farms) may mean deploying additional network taps to obtain complete coverage. IMPORTANT: If you have a reverse proxy in your network, load balancer, or you may want to choose a different deployment location. For more information, see Understanding how load balancers and reverse proxies affect metrics. Figure 4. Connecting the appliance to a network tap 13

14 Configuring web servers in a server farm When the network tap is installed between the firewall and the load balancer, the traffic contains only the IP address of the load balancer rather than the web servers. While this behavior is important for security purposes, it means that Foglight Experience Monitor attributes the data for all web servers to the load balancer IP address. Usually, you want data attributed to individual web servers. To enable the appliance to track data by web server, you need to configure the web servers to insert an extra shared HTTP response header into the traffic. For example, you can create an HTTP response header called SERVER-ID. On each web server, you assign a unique, fictitious (for security purposes) IP address to this header. After the Foglight Experience Monitor web console is running, an FxM Administrator defines a server identifier with the same name as the response header, and the appliance automatically begins tracking hits by web server. For more information, see Configuring server options. Understanding how load balancers and reverse proxies affect metrics Some load balancers and all reverse proxies multiplex requests from multiple client connections onto one proxy network connection to the web server. So, while there could be thousands of connections coming into the website, the load balancer or proxy may maintain only a dozen connections to each web server. This network architecture will affect some of the metrics collected by Foglight Experience Monitor, depending on where the network tap is installed in relation to the load balancer or proxy. The affected metrics are Network Latency and Processing Time for hits and pages, which are also included in the calculations of End-to- End Time for hits and pages. For more information about how these metrics are calculated, see How standard metrics are calculated in the FxM Metric Reference Guide. When a network tap is installed between the client and the reverse proxy, Network Latency is an estimate of the time it takes for a request to travel from the end user s device to the point where the tap is located. This is the desired measurement. The Processing Time includes the time spent on the request by the load balancer or reverse proxy and the web server, which in many cases is acceptable, but may not be desirable if your stakeholders want the Processing Time to reflect the performance of the web server only. When a tap is between the load balancer or reverse proxy and the server farm, the Processing Time reflects the time spent by a web server without the overhead of the load balancer or proxy, but the Network Latency is a fraction of the actual Network Latency. In this scenario, Network Latency is based on the time it takes for a request to travel from the load balancer or reverse proxy to the tap. The following table summarizes the trade-off in metric calculations. Select the deployment option that suits your needs. Table 1. Deployment options and metric calculations Network Tap Installed Network Latency Processing Time Between the client and the load balancer or reverse proxy (recommended) Between the load balancer or reverse proxy and the server farm Estimate of time elapsed from the end user s device to the tap, which is the expected value. Estimate of time elapsed from the load balancer or reverse proxy to the tap, which is a fraction of the expected value. Time spent on a request by the load balancer or reverse proxy and a web server. Time spent on a request by a web server. Some customers install network taps in both locations and configure two separate installations of Foglight Experience Monitor to monitor the taps. The Foglight Experience Monitor instance monitoring the client side tap provides accurate Network Latency metrics, while the Foglight Experience Monitor instance monitoring the server farm side provides accurate Processing Times and volume metrics for each web server. IMPORTANT: If you install network taps on both sides of a load balancer or reverse proxy, do not connect them to the same installation of Foglight Experience Monitor. The metrics collected in this fashion are inaccurate. 14

15 Installing Foglight Experience Monitor This section provides directions for installing the hardware and for connecting the Foglight Experience Monitor to the network. For more information, see these topics: Installing the appliance on the rack Connecting the appliance Making network connections Setting the appliance clock Entering required network information Installing the appliance on the rack All Dell PowerEdge systems ship with a full set of documentation and rack-mounting hardware. For instructions on how to unpack and physically install the Foglight Experience hardware in the network rack, see the Dell Systems Rack Installation Guide or Dell Systems Rack Installation Instructions. IMPORTANT: If you are deploying a Foglight Experience Viewer along with the Foglight Experience Monitor, before continuing with this procedure, see Connecting to the Foglight Experience Viewer. Connecting the appliance When mounting the Foglight Experience Monitor appliance onto the server rack, all network hardware must be connected before beginning the logical configurations. NOTE: The number of Ethernet ports available on your appliance varies, depending on the hardware type. For a list of supported hardware platforms and help identifying the Ethernet ports, see Appendix: Dell PowerEdge system appliance. To connect the appliance: 1 Attach one end of the network cable to the correct monitoring port (eth2-eth5). NOTE: The fiber-capable NICs use an LC connector. If your network uses SC connections, use an SCto-LC adapter cable to make the proper connection. 2 Plug the other end of the cable into the network tap. 3 Attach another network cable to the control port (eth0) on the appliance. 4 Plug the other end of the cable into the appropriate port on your WAN. 5 Attach the power cable, USB keyboard, and VGA monitor to the appropriate ports on the rear panel of the appliance. 6 Power on the appliance. TIP: After the appliance has been deployed, if you encounter problems with appliance data collection, or communication issues between the Foglight Experience Monitor and other machines on the network, see Troubleshooting the appliance for help. Making network connections The console program allows you to perform the initial configuration of the appliance. When setting up the appliance for the first time, you must set the system clock, and configure network settings. 15

16 Logging into the console If you correctly attached all cables to the Foglight Experience Monitor (as outlined in Connecting the appliance), the console program login prompt appears on the connected VGA monitor after powering on the appliance. For more information about logging into the console, see Accessing the console program. Log in with user name settings setup and password setup. TIP: After this installation, you can modify the account password using the console program. See Account management. All account passwords can also be modified in the web console. See User accounts. After successfully logging in, the main menu appears. Figure 5. Welcome to Setup menu Setting the appliance clock These options allow you to change the appliance date, time, and time zone. To set the system clock: 1 From the console main menu, arrow down to System Time Configuration and press Enter. 2 To modify the date, arrow down to Change Date and press Enter. The System Date Configuration screen appears. 3 Using the calendar options, enter today s date and return to the System Date / Time System menu. 16

17 4 To modify the time, arrow down to Change Time and press Enter. The System Time Configuration screen appears. 5 Type the current time in the 24-hour hh:mm:ss format and return to the System Date / Time System menu. 6 To modify the timezone, arrow to the Change Timezone and press Enter. The YAST screen appears. Select the clock and time zone that you want the appliance to use when displaying data. You can leave the UTC setting unchanged at its default value. 7 Press OK to return to the main menu. Entering required network information From the console main menu, arrow down to Network Configuration and press Enter. Figure 6. Network Configuration menu Arrow down to a selection to view and set network options. Setting control device options To enter required network information: 1 From the Network Configuration menu, arrow down to the Control Device option. The control device is the NIC port that is used for external access to the appliance through a web browser or an SSH client. 2 Enter the following information: 17

18 IP Address you are assigning to the appliance Netmask used for the network segment in which the appliance is located Network Gateway IP address Hostname for the appliance (for example a fully qualified domain name such as agent4.dell.com) the IP address for the primary DNS server the IP address of the secondary DNS server 3 Press OK to return to the Network Configuration menu. 4 Arrow down to Save Settings and press Enter. 5 The Save Changes dialog appears. To save settings, tab to the Yes option and press Enter. The system saves all of the new network settings, and begins the verification process. Each of the network settings are tested and the results are displayed in the console program. If the network configuration test fails, return to the Network Configuration Menu and verify that the IP addresses you have entered are correct. When the network configuration test succeeds, your appliance is now properly connected to your network and configured for use. Logging out of the console program After passing the network verification test, you are returned to the console program main menu. Tab to the Exit option and press Enter to leave the console program, and initialize the appliance. Configuring the appliance The Setup Wizard takes you through the installation process. For more information, see these topics: Using the web console and setup wizard Entering a permanent license key Configuring the Appliance Type Designating Time Servers Configuring protocols Detecting ports in use Configuring servers Completing the Setup Wizard 18

19 Using the web console and setup wizard The web console provides a user interface through which users can examine the metrics collected by the system and create customized reports. It is accessed whenever you use a web browser to connect to the IP address or hostname assigned to the appliance. When you connect to the appliance for the first time, the Setup Wizard is initialized, and guides you through the steps necessary to get the appliance started. IMPORTANT: You must have cookies enabled in your web browser in order to log in to, and use the web console. To log in to the Wizard: 1 Open a web browser on any computer on the same network as the Foglight Experience Monitor. 2 Type the Foglight Experience Monitor IP address or host name in the browser s URL address box (For example, or fxm.company.com). The IP address and host name were respectively configured at step 1 and step 6 in the previous section, Making network connections on page 15. The web console login screen appears: 3 Type admin in the Login and Password boxes, then click Submit. After logging in, the Setup Wizard introduction page is displayed. The Setup Wizard introduction page displays a list of items you need in order to complete the Setup Wizard: a license key specify whether the appliance is a portal, probe, or stand-alone an IP address for an NTP server ports used for TCP traffic on your network 19

20 IP addresses of the servers you intend to monitor NOTE: For Multi-Appliance Users - If you are currently creating a portal as part of a multi-appliance cluster, you only need to set the NTP server. Every page of the Setup Wizard has four buttons along the bottom of the page. Table 2. Setup wizard generic buttons Cancel Back Next Finished Click this to terminate the Setup Wizard at any time; the Foglight Experience Monitor will not be configured, and then next time you log in the Setup Wizard will automatically restart. Click this at any time if you want to return to the previous page of the Setup Wizard to make changes. Moves you to the next page of the Setup Wizard; click this when you have completed the current page. Finishes the process. This button is only enabled on the last page of the Wizard. IMPORTANT: Avoid using your web browser s back and forward buttons when using the Setup Wizard. Instead, use the Back and Next buttons provided on each page of the Wizard. 4 Click Next to continue to the next Setup Wizard step. Entering a permanent license key If a permanent license key has already been installed on your appliance skip this step of the Setup Wizard and proceed directly to the next step. If your appliance has only a temporary key the Appliance License page of the Setup Wizard appears as shown in the following illustration. Figure 7. Appliance License page To obtain a permanent license key, you need to provide Dell Technical Support with the Host Id as shown on this page. Once you receive the license key paste it into the License Key field and click Next to continue. Configuring the Appliance Type The next Wizard Setup step is the Type page. 20