BIG-IQ CM Release Information

Version: 7.0.0.1
Build: 6.0

NOTE: This release DOES NOT include fixes for the Spectre vulnerabilities (CVE-2017-5715, CVE-2017-5753).
F5 is currently developing fixes which will be released in a future version. Please see K91229003 for current Spectre and Meltdown information.

Known Issues in BIG-IQ CM v7.0.x

Functional Change Fixes

None

Cumulative fix details for BIG-IQ CM v7.0.0.1 that are included in this release

BIG-IQ Local Traffic & Management Fixes

BIG-IQ Application Management Fixes

Cumulative fix details for BIG-IQ CM v7.0.0.1 that are included in this release

819005 (parent): Upgrade from BIG-IQ v6.1.0 fails due to JS TypeError★

Component: BIG-IQ Application Management

Symptoms:
When the pool member in an AS3 application service is referencing an existing node on BIG-IP, upgrading from BIG-IQ v6.1.0 to BIG-IQ v7.0.0 fails and displays the following error: Waiting for BIG-IQ services ready' and logs a failure to JS TypeError in the /var/log/tokuupgrade.log file.

Conditions:
This happens when an AS3 application service exists with a pool member referencing an existing node on BIG-IP.

Impact:
Upgrade from BIG-IQ v6.1.0 to BIG-IQ v7.0.0 fails.

Fix:
The upgrade script now properly extracts the existing BIG-IP from the AS3 declaration as expected.

816637 (parent): Discovering BIG-IP devices with VLAN failsafe-action option set to failover

Component: BIG-IQ Local Traffic & Management

Symptoms:
After upgrading BIG-IQ from v6.1.0 to v7.0.0 and then discovering BIG-IP devices with the VLAN failsafe action option set to failover, BIG-IQ returns the following error:

Failed to copy configuration to working-config; reason: Failed copying from source to target: java.lang.IllegalArgumentException: failsafeAction failover Invalid state - 'failover'. Valid values are [reboot, restart-all, failover-restart-tm]

Error in Restjavad Logs:
Validation failure: java.lang.IllegalArgumentException: failsafeAction failover Invalid state - 'failover'. Valid values are [reboot, restart-all, failover-restart-tm]

Conditions:
This happens after upgrading from BIG-IQ v6.1. to v7.0.0 and you attempt to discover BIG-IP devices that have the LTM service's VLAN failsafe action option set to failover.

Impact:
Fails to discover the device

Workaround:
No viable workaround, EHF required.

Fix:
The values failover and failover-restart-tm have been added to VLAN failsafe action options so that import validation no longer fails.

Known Issues in BIG-IQ CM v7.0.x


BIG-IQ Configuration - Security - Shared Security Issues

BIG-IQ Device User Interface Issues

BIG-IQ Local Traffic & Management Issues

AppIQ Issues

Known Issue details for BIG-IQ CM v7.0.x

817761 : When filtering BIG-IP Devices list, statistics collection information is displays incorrectly

Component: BIG-IQ Device User Interface

Symptoms:
When viewing only a device group of BIG-IP devices on the BIG-IP Devices screen, the "Stats Collection Status" displays incorrectly as "Disabled" and the "Stats Last collection Date" column displays as blank, regardless of the actual state of the device's statistics collection information.

Conditions:
Navigate to the BIG-IP Devices screen and limit the BIG-IP devices displayed to groups only, rather than "All BIG-IP Devices".

Impact:
BIG-IQ cannot read the device statistics collection information when viewing only BIG-IP device groups.

Workaround:
Set the menu to "All BIG-IP Devices", then filter the text from the Filter box to view only the list of devices you want to see.

816637-1 : Discovering BIG-IP devices with VLAN failsafe-action option set to failover

Component: BIG-IQ Local Traffic & Management

Symptoms:
After upgrading BIG-IQ from v6.1.0 to v7.0.0 and then discovering BIG-IP devices with the VLAN failsafe action option set to failover, BIG-IQ returns the following error:

Failed to copy configuration to working-config; reason: Failed copying from source to target: java.lang.IllegalArgumentException: failsafeAction failover Invalid state - 'failover'. Valid values are [reboot, restart-all, failover-restart-tm]

Error in Restjavad Logs:
Validation failure: java.lang.IllegalArgumentException: failsafeAction failover Invalid state - 'failover'. Valid values are [reboot, restart-all, failover-restart-tm]

Conditions:
This happens after upgrading from BIG-IQ v6.1. to v7.0.0 and you attempt to discover BIG-IP devices that have the LTM service's VLAN failsafe action option set to failover.

Impact:
Fails to discover the device

Workaround:
No viable workaround, EHF required.

812717 : Some logging profiles do not display after upgrading to BIG-IQ v7.0.0

Component: BIG-IQ Configuration - Security - Shared Security

Symptoms:
After an upgrade from to BIG-IQ v7.0.0, some logging profiles do not display.

Conditions:
After upgrading to BIG-IQ v7.0.0.

Impact:
Some logging profiles do not display.

Workaround:
To work around this, from the BIG-IQ command line, run the following:


for item_id in 96a784ae-904c-340e-aa4b-700dd693e51b 9ac61bf5-cedf-3625-af0e-00f0a98a1cc0 d2a5fc31-d153-3fff-a8ea-97de03f95d97 f0a05642-f8ac-39e1-9f67-98fc6b8f4449 5ec7ef41-7938-384a-8489-f68df693c9b2; do restcurl -X PATCH /cm/security-shared/working-config/log-profiles/$item_id -d '{hidden:false}'; done

812065-1 : Pools & pool-member stats are not collected after upgrade

Component: AppIQ

Symptoms:
In some rare instances after upgrading to BIG-IQ version 7.0, BIG-IQ might not collect pool & pool-member statistics information.

Conditions:
When you upgrade from BIG-IQ version 6.x to 7.0.
To identify the presence of the issue, go to: Monitoring -> Dashboards -> Local Traffic -> Pools & Pool Members.
If stats are displayed - then the upgrade process was completed properly.

Impact:
Statistical information about pool and pool-member activities is not being collected and this information is not displayed in the corresponding dashboards.

Workaround:
The root cause of this problem is in ElasticSearch index mapping. To work around this issue, update the mapping manually:
1. unzip the attachment and place under /tmp on the CM.
2. run ./fix_es_mapping.sh


New mapping definitions take effect after the index is switched, so it can take up to 1 hour before BIG-IQ can collect statistis.