Original Publication Date: 03/04/2014
This release note documents version 4.2.0 of BIG-IQ Device.
As a network administrator, you can use BIG-IQ Device to centrally manage multiple physical and virtual BIG-IP devices. This management includes license management, software image installation, backing up and restoring UCS files, and backing up and restoring specific configuration files to one or more BIG-IP devices. BIG-IQ Device also helps you with device inventory tasks by keeping you apprised of every detail about you managed devices.
To properly display, the BIG-IQ system requires that your screen resolution is set to 1280x1024 or higher.
BIG-IQ Device supports the following browsers and versions:
For a comprehensive list of documentation that is relevant to this release, refer to the BIG-IQ 4.2.0 Documentation page.
For procedures about specifying network options and performing initial configuration, refer to the BIG-IQ System: Licensing and Initial Configuration guide.
Each BIG-IP device in your network contains SSL certificates. SSL certificates have a set expiry date, and do not automatically renew. Using BIG-IQ Device, you can centrally monitor the expiration dates for SSL certificates for all your managed devices, ensuring that traffic is not interrupted to your applications.
Using BIG-IQ Device to centrally manage the devices in your network means that you can deploy software images and configurations without having to log in to each individual BIG-IP device. You have a centralized view into the health of the BIG-IP devices, and if you see that a managed device has failed, but do not have the time to perform extensive troubleshooting, you have the option to immediately reformat the hard drive of the failed device and reload a stored configuration.
Centrally managing the BIG-IP devices with BIG-IQ Device provides you with the opportunity to easily assess the health and performance of your network.
You can manage resource usage in a dynamic application environment through the use of license pools. Each license pool is limited to a specific number of licenses. After you perform the initial license activation, BIG-IQ Device automatically grants and revokes licenses for the BIG-IP virtual edition systems as resource demands change. This gives you the flexibility to license devices only as needed, keeping your operating costs fixed. You can also use different license pools for different applications, allowing for flexible provisioning options.
|Issue||Description||Workaround (if available)|
|441274||The elasticity settings and pool license features introduced in this release do not support BIG-IP versions 11.4.1 and older.|
|441052||If two BIG-IQ systems in an active-standby high availability pair attempt to simultaneously manage the same BIG-IP device, only the BIG-IQ system that is the first to establish trust with the BIG-IP device can communicate with it. The peer BIG-IQ system will display SEVERE messages in its restjavad.0.log for the BIG-IP device.|
|441049||If you restart the BIG-IQ system, health statistics no longer display for the Device panel.||To recover and display the health statistics, re-discover managed BIG-IP devices.|
|440948||If you start manually activating a license pool and the process is interrupted (either by closing or navigating away from the screen), BIG-IQ Device saves the license pool in a partially complete state. To change the license pool's name, you must complete the license pool activation process, or delete the incomplete pool and start again.|
|440842||The time displayed in the pool licensing is in UTC, not local time.||Refer to the BIG-IQ System: Initial Setup and Configuration guide for instructions about setting the local time for the BIG-IQ system.|
|440531||If a query times out, the BIG-IQ user interface may become unresponsive.||To work around this issue, refresh your browser.|
|440333||If you delete a BIG-IQ peer from a high availability active-active pair, then add back the same BIG-IQ system, data between the devices no longer synchronized.||After you delete a BIG-IQ system from a high availability active-active pair, create a BIG-IQ system UCS backup for disaster recovery. Then reset the system to factory settings by typing the following command on that device: bigstart stop restjavad && rm -rf /var/config/rest && bigstart start restjavad You can add it back to a high availability pair and they will properly synchronize.|
|439026||The BIG-IQ system cannot search for addresses within a subnet. Queries for addresses contained within a subnet do not return complete results.||When searching for IPv6 addresses, you must specify explicit address ranges as a substitute for CIDR notation.|
|437741||If you have not configured an internal VLAN and an associated self IP address on the BIG-IQ system or a managed BIG-IP device, you receive the following message (logged to the BIG-IP restjavad.0.log) every minute for each system and device. [8100/shared/identified-devices IdentifiedDevicesWorker][failed] java.net.ProtocolException: Status code:401||You must configure an internal VLAN and self IP address for the BIG-IQ system and all managed devices.|
|434930||You cannot use a host name to add a device.||When you discover a new device, you must use its IP address.|
|431398||When booting the BIG-IQ system, it may display the following warning in the console or logs: SKIPPING unix_config_httpd: /defaults/config/templates/xui.tmpl doesn't exist!!! This message is benign and has no impact on the BIG-IQ system's functionality.||You can safely ignore this benign error message.|
|428071||When you install the required BIG-IQ system components on BIG-IP devices running on a VIPRION system with more than one blade, the components load only on the primary blade.||To install the required components on the remaining blades, for each blade, run the update_bigip.sh script then disable the blade through TMUI. After you run the script on all blades, re-enable them through TMUI.|
|428383||When you filter on a number or phrase when searching for a particular device, BIG-IQ Device may return unexpected results. This occurs because BIG-IQ Device filters on all fields, not just those displayed in the Devices panel.|
$ bigstart stop restjavad
$ bigstart stop msgbusd
mount -o remount,rw /usr
rpm -qa | grep f5-rest-java | xargs rpm -e --nodeps
rpm -qa | grep msgbusd | xargs rpm -e --nodeps
mount -o remount,ro /usr
This removes the BIG-IQ system components from the BIG-IP device, including the F5-contributed cloud connector iApp template (cloud_connector.tmpl).
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.