Foglight™ APM for Real User Experience 5.9.11

Developed for Foglight Management Server 5.7.5.8

Release Notes

August 2017

 


Contents

Welcome to Foglight APM for Real User Experience

New in this Release

Resolved Issues and Enhancements

Deprecated Features

Known Issues

Third Party Known Issues

Upgrade and Compatibility

System Requirements

Product Licensing

Getting Started with Foglight APM

About Us

 


Welcome to Foglight APM for Real User Experience

Foglight™ APM for Real User Experience (hereafter called Foglight APM) is an appliance-based application performance management solution. You can use Foglight APM to understand how real users navigate and interact with your monitored web sites and web applications.

Foglight APM adds a set of dashboards on the navigation panel, under Dashboards > APM. You can use these dashboards to perform the following tasks:

These Release Notes cover the resolved issues, known issues, workarounds, and other important information about the 5.9.11 release of Foglight APM. Review all sections before starting the installation.

 


New in this Release

This release contains the following new features and updates:

 


Resolved Issues and Enhancements

The following is a list of issues addressed and enhancements implemented in this release.

Defect ID

Resolved Issue

FAPM-2017

Fixed issue where the Message Discards chart in the Relayer Summary tab showed The Data to Display Is Not Available.

FAPM-1878

Fixed issue where some siteminder agents were blocked when initializing SMA API.

FAPM-1855

Fixed issue where Archiver throws the HTTP/1.1 400 Bad Request error during polling configuration from the Management Server 5.7.5.8.

FAPM-169

Fixed issue where Sniffer topology object still existed in the system after being removed in the UI.

Hotfixes Issued for Previous Release

The following is a list of issues resolved in hotfixes issued for the previous release. These issues are also fixed in this release.

Issues also Resolved in the quest-foglight-patch-5.9.10_20170315_47.pkg Hotfix

Defect ID

Resolved Issue

FAPM-1715

Included CVE-2017-5638 struts vulnerability.

FAPM-1674

Fixed issue where calendar control in the APM Hit Expert Search was hidden.

Issues also Resolved in the quest-foglight-patch-5.9.10_2017219_42.pkg Hotfix

Defect ID

Resolved Issue

FAPM-1633

Fixed the WCF script error occurred when adding a new Custom Field.

FAPM-1630

Added Search capability for filtering Custom Fields.

FAPM-1629

Added Search capability for filtering Script.

FAPM-1628

Added Search capability in the Traffic Analysis, Advanced Options, and Pivots views. 

FAPM-1605

Updated the Foglight license to extend its expiration date.

FAPM-1566

Added capability for starting up the FMS in the non-daemon state using the "rcfoglight stratfg" command.

FAPM-1342 Fixed issue where error occurred when clicking Begin New Update in the Update Appliance Software dashboard.
FAPM-1335 Fixed issue where the thread "EndUserQueryCommandExecutorSystemThread15" was stopped during the patch upgrade.

Issues also Resolved in the quest-foglight-patch-5.9.10_20161030_34.pkg Hotfix

Defect ID

Resolved Issue

FAPM-1151

Added Search capability for filtering Session Analyzers and Sequence Analyzers.

FAPM-1026

Improved the size of the Hit Analyzer drop-down list, to display longer Hit Analyzer names.

FAPM-1025

Added Search capability for filtering Hit Analyzers.

FAPM-999

Improved the install.log to provide detailed information about the .pkg file that has been installed.

FAPM-938

Implemented security updates to address the vulnerability in CURL/LIBCURL UP TO 7.50.0 0 - CVE-2016-5419.

FAPM-748

Fixed issues with Archiver/Sniffer registration.

Issues also Resolved in the quest-foglight-patch-5.9.10_20160803_26.pkg Hotfix

Defect ID

Resolved Issue

FAPM-869

FGL-17696

The server reads the topology during startup and proceeds to enable functions at that point. This includes rules and agent connections.
Since some services are not necessarily available at that point, for example scripting services, certain functions like evaluation of DMCs can be inoperable.

Correct interpretation of e.g. blackouts depends on controller/parent relationships and DMCs being ready which means that for a short period during startup alarms can occur that otherwise would not.

FAPM-767

The Scrollbar field is not displaying in APM > Traffic Capture > Monitored Subnets >  Add when there are more than eight CIDR blocks added.

FAPM-255

Added support for importing FxV configuration.

 

Issues also Resolved in the quest-foglight-patch-5.9.10_20160529_20.pkg Hotfix

Defect ID

Resolved Issue

FAPM-292

Fixed issue where the Sniffer > Summary dashboard displayed incorrectly the number of alarms when more than 100 alarms were triggered.

FAPM-195

Fixed issue where the update history log was shown twice in the Update History view.

FAPM-155

Fixed issue where the console would capture traffic, but the auto-discovery feature was not working.

FAPM-154

Added tooltips to the Busiest Web Sites and Busiest Endpoints tables.

FAPM-153

Updated the Summary - All Relayers view to display the number of Transfer Queues instead of the queues status.

FAPM-152

Fixed issue where the distribution chart for Hits was clickable.

FAPM-151

Fixed issue where the Alarms indicator in the appliance Summary tab was displaying an incorrect value.

FAPM-150

Fixed issue where the status of Domain boxes did not refresh after clearing alarms.

FAPM-149

Fixed issue where old Relayer queues were incorrectly displayed in the Relayer > Queues dashboard.

FAPM-148

Fixed issue where the graph chart and dot icons were clickable in the Hit Processing view.

FAPM-147

Fixed issue where no data was displayed when only one letter was used for City searching in the Monitored Subnets dashboard > Edit Monitored Subnet > Select Geographical Location dialog box.

FAPM-146

(APMDATA-2207)

Fixed issue where some System Health Alarms were not triggered correctly.

 


Deprecated Features

There are no features deprecated in this release.

 


Known Issues

The following is a list of issues known to exist at the time of this release.

General

Defect ID

Known Issue

FAPM-2081

The value of Error % in the Applicance Health > SSL Decryption table shows "n/a", when periods of Connection Error and Connections Dropped are different.

FAPM-2048

The "Failed to create agent DellUnixAgent/EmbeddedHostMonitor on remote host" error is reported in the log, after installing and starting the APM Virtual Machine appliance the first time.

FAPM-2043

Foglight APM for Real User Experience 5.9.11 is not compatible with the Management Server 5.9.x.

Workaround: Quest suggests NOT upgrading server-hosted Management Servers to version 5.9.x.

FAPM-2016

The Archiver cannot collect hit data from Sniffer, after restoring the Foglight appliance with NetVault.

Workaround:

1. Log into the appliance using root user credentials.

2. Execute the ipcs -m command to check shared memory IDs.

3. Execute the rcquest stop command to stop all services.

4. Execute the ipcrm -m#shmid command to remove shared memory.

5. Execute the rcquest start command to start all services.

FAPM-1251

Appliancemon throws the "Configuration poll failed: HTTP/1.1 503 Service Unavailable" error during the poll configuration.

APMDATA-1894

Other "APM" cartridges' objects displayed in Web Sites and Endpoints Dashboard > Endpoint Summary list.

APMDATA-1888

The Navigation Page Completion Time Unit does not display in Hit Detail View page.

APMDATA-1853

Slow response possibly due to ConfigurationManager locking during configuration export.

APMDATA-476
(formerly FGLEU-3978)

Appliance Health dashboard: An appliance running only the Management Server does not appear in the Appliances list.

APMDATA-433

Maps: In some cases, numeric codes are used to identify regions instead of the region names.

APM-6692

"Error Code 599" representations are different on "Search Hits" and  "Search Session".

APM-4910

Web Sites and Endpoints dashboard: When viewing historical data in the Busiest table, Volume may be displayed as "n\a". In this case, the historical data used to generate the table included the Volume data, but the rolled-up historical data used to populate the table did not contain the Volume data.
Workaround: To view the data, align the time range to a 30 minute interval.

APM-4439

Match Conditions dialog boxes: The dialog box does not accept blank values on a match condition.

FDOC-7990

The APM Installation and Setup Guide includes the following step in the "Setting the date and time" procedure:

"4. To use UTC (Coordinated Universal Time), select Hardware Clock Set To UTC. Clear this option to use local time."

This step is incorrect. It should be updated to say:

"4. Ensure that the check box is set so that the Hardware Clock is using UTC".

APM High Availability

Defect ID

Known Issue

APMDATA-558

Cannot reinstall the EndUser cartridge and its dependencies while both the primary and standby Management Servers are running.
Workaround:

  1. Uninstall the cartridges on both the primary and standby Management Servers.
  2. Shut down the standby server.
  3. Re-start the primary server, and install the cartridges.
  4. Start the standby server. The cartridges can be installed on the standby server automatically.

If the installation fails on the standby server, shut down the primary server. The standby server becomes the new primary server and you can install the cartridges.

 


Third Party Known Issues

There are no known third-party issues specific to this release of Foglight APM for Real User Experience.

 


Upgrade and Compatibility

Upgrading appliance software components

You update appliance software using the APM > Support > Update Appliance Software dashboard. For instructions, see "Updating Appliance Software" in the online help or in the Foglight APM Administration and Configuration Guide.

Important: The .rpm installation during the Foglight APM upgrade might take around 5 - 15 minutes. Do NOT restart the appliance during this period, as the restart could result in the server appliance damage and data lost.

Note: Direct upgrades are only supported from Foglight APM version 5.9.10. Upgrading from versions prior to 5.9.10 requires more than one step. Before you begin, obtain all the necessary Foglight APM for Real User Experience upgrade packages from the Support Portal.

 

To upgrade the software components hosted on your appliances:

  1. Navigate to APM > Support > Update Appliance Software.
  2. Click Update Appliance.
    The Update Appliance Software dashboard opens in a separate web browser window.
  3. Do one of the following: 
  4. To review the full log, click the View Details link on right side of the dashboard. If you need help resolving any upgrade issues, contact Technical Support.

    All registered appliances are updated during this automated process. In addition, all appliance-hosted Management Servers are updated to the configuration described under Getting Started.

If your environment does not include any server-hosted Management Servers, you are done. Otherwise, continue to the next section.

Upgrading server-hosted Management Servers

If you are running Foglight APM on a server-hosted Management Server, after you update the appliance software, you need to install the Foglight APM for Real User Experience 5.9.11 cartridge on each server-hosted Management Server. You also need to confirm some dependencies.

Important: Foglight APM for Real User Experience 5.9.11 is only compatible with Foglight Management Server 5.7.5.8. Contact Quest Support first if you are going to upgrade the Foglight Management Server to a newer version.

 

Note: The Application-Operations cartridge preinstalls dependency mapping cartridges that are only activated when the specific domain is monitored.

Messages may appear in Foglight when the Applications-Operations cartridge is installed, but other domain-specific cartridges are not installed. These messages indicate that dependency mapping information for the domain is not available, and therefore the dependency integration cartridge for that domain is not enabled.

For example, the following message appears when the Cartridge for Sybase is not installed: 

Could not complete the requested operation, with the following messages:

Missing dependency for Cartridge: Dependency-Sybase-Integration-5.9.8.3 - 5983-20170601-1722:Sybase_MDA-5.5.8 (matches: LATEST)

Missing dependency for Cartridge: Dependency-MQ-Integration-5.9.8.3 - 5983-20170601-1722:MQ-5.5.5 (matches: LATEST)

 

To upgrade cartridges on a server-hosted Management Server:

  1. Upgrade the appliance software as described in the Upgrading appliance software components section.
  2. Log in to Foglight on the server you want to upgrade.
  3. In the bottom right of the browser window, click About. Ensure that you are running Foglight 5.7.5.8. Earlier Foglight versions are not compatible.
    Important: It is recommended to upgrade to the latest Foglight version, to take advantage of the ongoing improvements and defect fixes. For information about upgrading Foglight to the latest compatible version, refer to the Foglight Upgrade Guide.
  4. Navigate to Administration > Cartridges > Cartridge Inventory.
  5. Verify that the following cartridge versions appear in the Cartridge Inventory list. If not, install the required cartridges and any desired optional cartridges. For a list of cartridge names, see the Compatibility section.
  6. Verify successful installation. Navigate to Administration > Cartridges > Cartridge Inventory.
    On the Cartridge Inventory dashboard, look for the following cartridge versions:

Compatibility

This release of Foglight APM is compatible with the following components, which are available from the Foglight - Software Downloads page.

Note: This information applies for both Appliance-hosted Foglight Management Servers and Server-hosted Foglight Management Servers.

Component Name

Version

Cartridge Inventory Name

Section Name on Support Portal
(at time of release)

Foglight Management Server, 64-bit version only

5.7.5.8

n/a - See the About link in the footer of the Foglight browser interface.

Foglight Management Server

Foglight Agent Manager

Note: Required for monitoring Java® and .NET® applications.

5.8.5.8

FglAM-Adapter

Foglight Agent Manager

Foglight for Application Operations

5.9.8.5

Application-Operations

Foglight for Application Operations

Foglight for Microsoft .NET

Note: Required for monitoring .NET® applications.

5.9.11

ApplicationServers-DotNET

Foglight for Microsoft .NET

Foglight for Java EE Technologies

Note: Required for monitoring Java® applications.

5.9.11

ApplicationServers-Java

Foglight for JavaEE

 


System Requirements

System requirements depend on the type of Foglight APM Appliances you purchased, that is physical appliances or virtual appliances. If you are adding Foglight APM to an existing installation of Foglight, you also need to be aware of some software requirements. The appliances support SUSE Linux® Enterprise Server.


Note: When an appliance includes the Foglight Management Server, Foglight and the APM-related cartridges are preinstalled. For a complete list of components, see Getting Started.

Physical Appliances

The tables in this section provide information about the Dell™ PowerEdge™ hardware configurations supported in this release. This data is subject to change. To get the latest information, go to the Dell web site and search for your specific hardware. 

If you purchased Foglight APM on physical appliances, you received one or more Dell PowerEdge R730 servers, each with the following specifications:

System PowerEdge R730
Processors 2 x Intel Xeon E5-2640
Memory 128 GB
Drives 8 x 1TB 7.2K RPM Near-Line SAS 3.5in
(optional 8 x 2TB and 8 x 3TB drives available)
PCIe Cards 4 x 8 PCIe Slots + 2 x 16 PCIe Slots
Available PCIe Expansion Slots1 Three(3) x8 full-length, full-height
Power Supply Redundant
Total Input Power 495 watts
Total Weight 65 pounds
Declared A - Weighted Sound Power Level 4.7 bels
Disk Controller PERC H730P
Remote Access Controller iDRAC 7 Enterprise
Monitoring Ports2 6

Note 1: APM Sniffer appliances can utilize a maximum of 10 monitoring NIC ports. This can be done by installing either a single quad-port NIC or two dual-port NICs in the PCIe expansion slots. If your appliance was ordered with the option of an additional 10Gb dual-port NIC, then one of these expansion slots will be occupied.

Note 2: Up to 10 monitoring ports are supported.

Servers are pre-configured with one of the following Foglight APM appliance configurations:

An appliance ships with the following components:

Using Appliances Purchased for FxV or FxM with Foglight APM

Dell PowerEdge R720 servers originally purchased for an APM configuration can be upgraded to version 5.9.11.

Dell PowerEdge R720 servers originally purchased for an FxV or FxM configuration can be re-used by imaging the server with the desired Foglight APM configuration.

The following table describes the supported configurations. For instructions, see Foglight APM on DellTM PowerEdgeTM R720/R730 Appliance Imaging Field Guide. 

 

Note: While it is technically possible to run the Sniffer alone on an R720 Large configuration, the Sniffer does not require or use the extra memory and storage.

System PowerEdge R720 Large PowerEdge R720 Small
Former Configuration FxV FxM
Foglight APM Appliance Configurations One of the following configurations:
- All-in-One
- APM
- Management Server Only
- Archiver Only
Sniffer Only
Processors 2 x Intel Xeon E5-2640 2 x Intel Xeon E5-2640
Memory 128 GB 32 GB
Drives 8 x 1TB 7.2K RPM Near-Line SAS 3.5in
(optional 8 x 2TB and 8 x 3TB drives available). Configured for RAID-10.
4 x 1 TB 7.2K RPM Near-Line SAS 3.5in.
Configured for RAID-10.
PCIe Cards 4 x 8 PCIe Slots + 2 x 16 PCIe Slots 4 x 8 PCIe Slots + 2 x 16 PCIe Slots
Power Supply Redundant Redundant
Total Input Power 222 watts 222 watts
Airflow Rate 16 cubic feet per minute 16 cubic feet per minute
Total Weight 65 pounds 65 pounds
Total Input Current 2 amperes 2 amperes
Declared A - Weighted Sound Power Level 4.7 bels 4.7 bels
Air Temperature Rise 45.1 F 45.1 F
Disk Controller PERC H710P PERC H710P
Remote Access Controller iDRAC 7 Enterprise iDRAC 7 Enterprise
Monitoring Ports 1 6 6

Note 1: Up to 10 monitoring ports are supported.

Virtual Appliances

If you purchased Foglight APM on virtual appliances, you received one or more OVF templates to deploy on VMware® vSphere®.

Virtual Appliance Template Virtual APM Virtual Sniffer Virtual Archiver Virtual Management Server
VMware vSphere Version vSphere 5.0 or later vSphere 5.0 or later vSphere 5.0 or later vSphere 5.0 or later
Guest OS Suse Linux Enterprise 11 (64-bit) Suse Linux Enterprise 11 (64-bit) Suse Linux Enterprise 11 (64-bit) Suse Linux Enterprise 11 (64-bit)
CPUs 8 4 4 4
Memory 28 GB 8 GB 16 GB 12 GB
Storage - Operating System Partition 15 GB 15 GB 15 GB 15 GB
Storage - Data Partitions 1 FMS data partition - 100 GB
Archiver data partition - 200 GB
n/a 200 GB 100 GB
Note 1: Data partitions can be increased up to a maximum of 2 TB. For Virtual APM, the combined total of the two partitions cannot exceed 2 TB.

Software Requirements for Server-hosted Foglight Management Servers

When installing Foglight APM on a server-hosted Management Server, Foglight APM inherits the system and software requirements of Foglight. For Foglight system and software requirements, including supported browsers, see the Foglight System Requirements and Platform Support Guide.

Foglight APM adds the following system requirements to the Foglight system requirements.

Foglight Version

Foglight 5.7.5.8, 64-bit version only

Foglight Agent Manager Version

Foglight Agent Manager 5.8.5.8 (required for monitoring Java® and .NET® applications)

Cartridge Dependencies

Foglight for Application Operations version 5.9.8.5

Foglight for Microsoft .NET version 5.9.11 (required for monitoring .NET® applications)

Foglight for Java EE Technologies version 5.9.11 (required for monitoring Java® applications)

Software Requirements

OpenSSL — required for local private keys

256-bit encryption for Java® — for instructions on enabling 256-bit encryption, see "Setting Up Server-hosted Management Servers" in the Foglight APM Installation and Setup Guide

Platform

Same as Foglight. For more information, see the Foglight System Requirements and Platform Support Guide.

Memory

8 GB or greater recommended (6 GB minimum heap for a 64-bit Management Server, plus 2 GB for this cartridge)

Hard Disk Space

200 GB or greater recommended

Operating System

Same as Foglight. For more information, see the Foglight System Requirements and Platform Support Guide.

 


Product Licensing

Foglight APM Physical or Virtual Appliances

When purchasing Foglight APM on appliances, the Foglight APM license includes licensing for the components list in the Getting Started section. When purchasing physical appliances, a license for Quest NetVault is included for backing up and restoring physical appliances.

Adding Foglight APM for Real User Experience to a Foglight Installation

When adding Foglight APM to a Foglight installation where the Management Server runs on a server (rather than in an appliance), the Foglight APM license covers use of the Foglight APM for Real User Experience cartridge and the software on the Sniffer and Archiver appliances. You need separate licenses for Foglight itself and for any other cartridges you want to install. For more information, contact your Sales representative and see the Foglight Release Notes.

Activating a License

To activate a trial or a purchased commercial license:

  1. On the navigation panel, under Dashboards, click Administration > Setup > Manage Licenses.
  2. Click Install.
  3. In the Install License dialog box, click Browse.
  4. In the file browser that appears, specify the location of the license file.
  5. In the Install License dialog box, click Install License.

 


Getting Started with Foglight APM

Contents of the Release Package

The Foglight APM 5.9.11 release package contains the following:

Contents of the top-level cartridges

Cartridge Name

Top-level Cartridge Inventory Name and Version

Sub-Cartridges Inventory Name and Version

Foglight APM for Real User Experience

EndUser-5_9_11.car

n/a

Foglight for Application Operations

Application-Operations-5_9_8_5.car

n/a

Foglight for Microsoft .NET

Note: Required for monitoring .NET® applications.

ApplicationServers-DotNET-5_9_11.car

see Getting Started with Foglight for Microsoft .NET in the Foglight for Microsoft .NET Release Notes

Foglight for Java EE Technologies

Note: Required for monitoring Java® applications.

ApplicationServers-Java-5_9_11.car

see Getting Started with Foglight for Java EE Technologies in the Foglight for Java EE Technologies Release Notes

Installation Instructions

For detailed information about installing Foglight APM, see the Foglight APM Installation and Setup Guide. The guide includes instructions for physical appliances, virtual appliances, and installations where the Management Server is not located on an appliance.

 

Note: The Application-Operations cartridge preinstalls dependency mapping cartridges that are only activated when the specific domain is monitored.

Messages may appear in Foglight when the Application-Operations cartridge is installed, but other domain-specific cartridges are not installed. These messages indicate that dependency mapping information for the domain is not available, and therefore the dependency integration cartridge for that domain is not enabled.

For example, the following message appears when Foglight for Sybase is not installed: 

Could not complete the requested operation, with the following messages:

Missing dependency for Cartridge: Dependency-Sybase-Integration-5.9.8.3 - 5983-20170601-1722:Sybase_MDA-5.5.8 (matches: LATEST)

Missing dependency for Cartridge: Dependency-MQ-Integration-5.9.8.3 - 5983-20170601-1722:MQ-5.5.5 (matches: LATEST)

Additional resources

Additional information is available from the following:

Globalization

This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.

This release is Unicode-enabled and supports any character set. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia, Japan.

 


About Us

We are more than just a name

We are on a quest to make your information technology work harder for you. That is why we build community-driven software solutions that help you spend less time on IT administration and more time on business innovation. We help you modernize your data center, get you to the cloud quicker and provide the expertise, security and accessibility you need to grow your data-driven business. Combined with Quest’s invitation to the global community to be a part of its innovation, and our firm commitment to ensuring customer satisfaction, we continue to deliver solutions that have a real impact on our customers today and leave a legacy we are proud of. We are challenging the status quo by transforming into a new software company. And as your partner, we work tirelessly to make sure your information technology is designed for you and by you. This is our mission, and we are in this together. Welcome to a new Quest. You are invited to Join the Innovation™.

Our brand, our vision. Together.

Our logo reflects our story: innovation, community and support. An important part of this story begins with the letter Q. It is a perfect circle, representing our commitment to technological precision and strength. The space in the Q itself symbolizes our need to add the missing piece — you — to the community, to the new Quest.

Contacting Quest

For sales or other inquiries, visit www.quest.com/contact.

Technical support resources

Technical support is available to Quest customers with a valid maintenance contract and customers who have trial versions. You can access the Quest Support Portal at https://support.quest.com.

The Support Portal provides self-help tools you can use to solve problems quickly and independently, 24 hours a day, 365 days a year. The Support Portal enables you to:

 


Copyright© 2017 Quest Software Inc.

Quest, the Quest logo, Foglight, and Join the Innovation are trademarks and registered trademarks of Quest Software Inc. in the U.S.A. and other countries. For a complete list of Quest Software trademarks, please visit our website at www.quest.com/legal. 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. Fedora and the Infinity design logo are trademarks of Red Hat, Inc. Microsoft, .NET, Active Directory, Internet Explorer, Hyper-V, Office 365, SharePoint, Silverlight,SQL Server, Visual Basic, 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, PowerPC, PowerVM, and WebSphere are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide. Java, Oracle, Oracle Solaris, PeopleSoft, Siebel, Sun, WebLogic, and ZFS 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 HewlettPackard 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. 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, Mac OS, Safari, Swift, and Xcode 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. OpenSUSE, SUSE, and YAST are registered trademarks of SUSE LCC in the United States and other countries. Citrix, AppFlow, NetScaler, XenApp, 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. PostgreSQL is a registered trademark of the PostgreSQL Global Development Group. MariaDB is a trademark or registered trademark of MariaDB Corporation Ab in the European Union and United States of America and/or other countries. Intel, Itanium, Pentium, and Xeon are trademarks of Intel Corporation in the U.S. and/or other countries. Debian is a registered trademark of Software in the Public Interest, Inc. OpenStack is a trademark of the OpenStack Foundation. Amazon Web Services, the "Powered by Amazon Web Services" logo, and "Amazon RDS" are trademarks of Amazon.com, Inc. or its affiliates in the United States and/or other countries. Infobright, Infobright Community Edition and Infobright Enterprise Edition are trademarks of Infobright Inc. POLYCOM®, RealPresence® Collaboration Server, and RMX® are registered trademarks of Polycom, Inc. All other marks and names mentioned herein may be trademarks of their respective companies.