Original Publication Date: 04/29/2013
This release note documents the version 4.0.0 of BIG-IQ Cloud.
BIG-IQ™ Cloud provides administrators a method to supply cloud tenants on-demand access to shared cloud resources such as networks, servers, storage, applications, and services. These cloud resources can be private or public, depending on the customer's requirements. Each tenant has restricted and dedicated access to resources based on a specific user account or tenant role, ensuring that tenants have access only to their own resources. Cloud space can be easily reallocated as needed, providing flexible resource balancing.
To properly display, the BIG-IQ system requires that your screen resolution is set to 1280x1024 or higher.
BIG-IQ supports the following browsers and versions:
For procedures about specifying network options and performing initial configuration, refer to the Setup and Getting Started guide specific to the hypervisor on which you install BIG-IQ Cloud.
|Issue||Description||Workaround (if available)|
|ID 414779||The user name and role are listed in the upper right corner of the BIG-IQ Cloud screen. For Administrator and Cloud Tenant users, BIG-IQ Cloud incorrectly displays Role: user.|
|ID 415163||When you are using the search feature, BIG-IQ Cloud returns query results only if they match the entire case-sensitive search string. It does not return partial matches.|
|ID 415329||The same device is listed multiple times in the Devices panel after a user completes the discovery process. This issue occurs when a user discovers the same device using different IP address. For example, if a user initially discovers a device using the management IP address, and then again using its self IP address, the device is listed twice in the Devices panel.||To resolve this situation, delete the superfluous device listings.|
|ID 415459||It is important that before you deploy the cloud management and monitoring agent to a BIG-IP device, you verify that no critical network traffic is targeted for that device. During the cloud agent update, the traffic interface (TMM) on the device restarts to ensure support for the new BIG-IQ Cloud monitoring and management components.|
|ID 416688||A device might display multiple times, as associated to a cloud connector. This issue occurs if an cloud provider inadvertently adds multiple instances of a device to a cloud connector.||To resolve this issue, remove the duplicate instances from the cloud connector.|
|ID 416870||If a vShield Manager or vCloud Director user explicitly removes the BIG-IQ Cloud registration, the VMware cloud connector for that VMware product continues to display in the Connectors panel, but as unhealthy.||To work around this issue, delete the VMware connector in BIG-IQ Cloud.|
|ID 417051||BIG-IQ Cloud does not currently support devices with IPV6 addresses.||Use IPV4 addresses to discover devices.|
|ID 417089||Only a cloud tenant user can add an application. When logged in as an administrator, you cannot add an application to the Applications panel. The Applications panel displays, but the add (+) icon does not appear.||As the administrator user, if you want to add an application, log out and log back in as cloud tenant.|
|ID 417162||When you place your cursor on a connector in the Connectors panel, the Catalog panel does not display associated application templates. Instead, the number displayed in the Catalog panel is always 0 for the selected connector.|
|ID 417165||If the health of a cloud connector changes, BIG-IQ Cloud does not immediately display the change in the Connectors panel. Health monitoring works as designed through the API.||To view the current health of a cloud connector, refresh your browser.|
|ID 417179||When you select an application from the Applications panel, the associated servers do not display properly in the Servers panel. This occurs when an application shares a server with another application.||To avoid this issue, do not share servers between multiple applications.|
|ID 417334||You may need to perform multiple queries to the REST storage database to obtain the information you need for auditing changes.||For assistance, provide F5 customer support a qkview file or remote access to your BIG-IQ system.|
|ID 417416||BIG-IQ system users must log in with a user name and password that was created on the BIG-IQ system. User credentials are authenticated only on the local device. You cannot use an external authentication systems, such as LDAP or RADIUS, to authenticate BIG-IQ system users.|
|ID 417501||If a cloud provider assigns a Cloud Tenant role to a user but does not associated that user with a tenant, the user receives an error message when attempting to log in to BIG-IQ Cloud.||Associate the cloud tenant user to a tenant. Cloud tenant users who are not associated with a tenant are denied access to the BIG-IQ Cloud UI.|
|ID 417524||The BIG-IQ cloud provider assigns tenant resources to specific managed devices. A tenant can deploy an application to that device only if it is powered on, enabled, and in a healthy state.|
|ID 417871||When a user is logged in as administrator, newly deployed VMware vShield applications do not display in the BIG-IQ Cloud Applications panel, and the associated servers do not appear in the Servers panel.||To work around this issue, refresh the BIG-IQ Cloud browser twice. The first refresh updates the Applications panel, the second refresh updates the Servers panel.|
|ID 417874||If a cloud provider does not request that a tenant remove all applications from a device before deleting it or marking it as unmanaged, the applications remain associated with that device. If the device is re-discovered, the applications persist and display for the tenant, but are not available for use. These applications cannot be removed through the user interface.||To remove orphaned applications, the cloud provider must log in directly to the managed device and delete them. To avoid this situation, cloud providers must first request that tenants remove applications before they delete a device on which those applications exist.|
|ID 418490||The VMware vSphere hypervisor returns TMM restart messages when using the 4 core configuration option.||To work around this issue, run the bigstart restart command.|
|ID 418745||If you delete an iApp and immediately create another with the same name, the new iApp instance fails.||To avoid this situation, verify that the iApp you deleted is not listed on the device, before you create the new iApp.|
|ID 418899||An iApp that a tenant created may not display in the Catalog panel.||To resolve this issue, refresh the BIG-IQ Cloud browser.|
|ID 418941||When logged on as a cloud provider, if you select a tenant that is using a catalog object, the associated catalog object is not highlighted.||Click an application. When you do so, all associated tenants and catalog objects are highlighted.|
|ID 418950||Root access is required to run script that installs cloud components on AWS-deployed BIG-IP devices, but AWS deployment does not support access with a root password.||There are two ways to work around this issue: Option 1. Establish SSH trust between the BIG-IQ Cloud and each BIG-IP device that you have deployed using AWS. Once this trust is established, the script that installs cloud components does not prompt for root authentication. Option 2. Temporarily set up root account access on each BIG-IP device that you have deployed with AWS. Use the root password when you are prompted for it while running the script.|
|ID 419935||The BIG-IQ system does not currently support Device Service Clustering (DSC) on managed BIG-IP devices. Changes made to a BIG-IP configuration are not automatically synchronized with its peers.||To work around this issue, use the BIG-IQ system to deploy a configuration to one of the BIG-IP devices in a cluster, then log in to that device and synchronize the configuration with the rest of its peers.|
|ID 419796||Device Service Clustering (DSC) settings display in the BIG-IQ Cloud user interface, but DSC is currently not supported.||Do not configure DSC for BIG-IQ Cloud version 4.0.0.|
For additional information, please visit http://www.f5.com.
You can find additional support resources and technical documentation through a variety of sources.
Free self-service tools give you 24x7 access to a wealth of knowledge and technical support. Whether it is providing quick answers to questions, training your staff, or handling entire implementations from design to deployment, F5 services teams are ready to ensure that you get the most from your F5 technology.
AskF5 is your storehouse for thousands of solutions to help you manage your F5 products more effectively. Whether you want to search the knowledge base periodically to research a solution, or you need the most recent news about your F5 products, AskF5 is your source.
The F5 DevCentral community helps you get more from F5 products and technologies. You can connect with user groups, learn about the latest F5 tools, and discuss F5 products and technology.